THE SCROLLS IDENTITY CRISIS

[Mitre]

Hi all
just thought i would start a thread on the scroll and excel identity criss all android devices are given an id code for device recognition the id has two parts one id's the manufacturer the other id's the model
dell------------413c
samsung-----04e8 galaxys2------6860 = so a galaxyS2 will show up as 04e8:6860

google------18d1
Huawei-----12d1 ideos------1038
im shure you get the picture anyway the scroll7" resistive is showing as ---18d1:deed
the excel is showing as ----------------------------------------------------------------18d1:0002
so what i am saying is that the scroll has been given an id to make it work on market if we could change the id it may open up the unavailable apps on market
also i think the scrolls have been given a US id which may account for no tesco app
i found this out trying to mount the scroll to my ubunto pc and could not identify the device

a way to get your scroll ID connect it to another android device( Linux machone) make shure they are boyh switched on on second device open terminal and type lsusb(you dont need root)

[Mitre]

Reserved

[Charlie]

im shure you get the picture anyway the scroll7" resistive is showing as ---18d1:deed

Yes, this is interesting, from what I remember (for the 7" resistive) that code 18d1:deed was to do with getting the device recognised as a usb device on a pc - not sure if this affects the market tho'

[Mitre]

@ charlie can you check your excel lsusb values just to put my mind at rest that CWM5 didnt change the ID
and whats the build number

[Charlie]

@ charlie can you check your excel lusb values just to put my mind at rest that CWM5 didnt change the ID
and whats the build number

Will do ASAP - please remind me if I have not done it by end of the weekend - I am still charging up the excel at the mo.

[Charlie]

The Excel id is 18d1:0002 - so CWM5 was not changed that

Can anyone help, I added this into the android_winusb.inf

Code: Select all

;Scroll Excel
%SingleAdbInterface%       = USB_Install, USB\VID_18D1&PID_0002 
%CompositeAdbInterface%    = USB_Install, USB\VID_18D1&PID_0002&MI_01

Because we believe the id is 18d1:0002 - but I can not get the android composite adb interface driver to work.

It's driving me crazy!

[Mitre]

have you updated the drivers in the sdk
just pluged my excell into a windows pc typed
adb devices at the cmnd prompt and it showed up

[Charlie]

have you updated the drivers in the sdk
just pluged my excell int windows pc typed
adb devices at the cmnd prompt and it showed up

That's good to know it working for you

I am just waiting for a fresh install of SDK to finish (forgot how long it takes)

PS - what did adb list it as ?

[Mitre]

forgot now i unplugged it i'll re check

[Charlie]

Cheers Mitre I owe you a beer,

With what you posted previously made me look closer at a folder in the sdk kit and realised that the .dll and some other files were missing - once those where put back - the driver installed on the 2nd attempt

Cheers mate