Hi @all,
maybe some of you guys could help me with my problem.
I updated my Hero to the Cronos 1.4 (I think) a month ago.
Last week, I recognized that the USB mass storage connection does not work anymore.
I tried it on another PC, but no connection.
I tried another Hero with my PC, usb connection worked.
I found this link to the modaco forum:
http://android.modaco.com/content-page/299174/no-adb-no-sd/page/80/
So I followed the instructions of the first post on page 5.
Everything worked till that point where I should flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe.
So, here is what I have done so far:
- created a goldcard (with another hero, a friend has one).
- extracted the rom.zip from HTC Hero RUU_Hero_HTC_WWE_2.73.405.5_WWE_release_signed_NoDriver.exe
- flashed it via fastboot
- then I wanted to try the fastboot oem eraseconfig, but like it's said in the post, the eraseconfig command is not included
- so I extracted the rom.zip from RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
- tried to flash it, downgrade should be possible because of the goldcard
- but I now get the error "INFOchecking main version... FAILED (remote: 43 main version check fail)"
What can I do?
Could I extract the hboot from the 1.76.405.1_R3 and replace the one of 2.73.405.5 just to have the eraseconfig command?
Every kind of help is appreciated.
Thanks
André
Goldcards are handset specific as it has something to do with the serial number.
This MIGHT be the issue.
Really? On another post I read that they are specific to the sd-card, as one has to identify the unique id of the sd card and not of the handset.
Here's the link to the thread:
http://forum.xda-developers.com/showthread.php?t=648102
You sure?..... Ask your pal to do the "cat /sys/class/mmc_host/mmc1/mmc1:*/cid" bit using two different SD cards (yours and his own one) to see if the code is the same of or not.
..... or backup the goldcard your pal done you,... then make a new one yourself using whatever guide your using at the mo,... along with this one,..... http://thatsbadass.com/android/tag/cid/ ... <--that guide shows how to get your CID without plugging your phone in.
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
EDA-One said:
I tried it with another card and its another code. So I think it depends on the sd-card.
So, I think I tried flashing before I created the goldcard and that process stopped at the very beginning, saying something like cid check failed or so and not with that "main version check fail" message.
Click to expand...
Click to collapse
Aha,... OK,... You must be right,... apologies.
.... Have you tried using flashrec already?....
If I remember correctly, you cannot flash this version directly since it is actually a downgrade. I don't remember clearly how I managed to bring it up, either it was thanks to a Goldcard (I did experiment with that), or it was enough to patch the custom recovery image (see http://android.modaco.com/content/h...android-modaco-com-index-phpshowtopic-292396/).
Click to expand...
Click to collapse
not yet. but i will try now.
But I don't know, what should I try to flash with flashrec.
A new recovery rom? I think flashrec only allows *.img, or am I missing something?
...
...
...
OK,that worked.
Now I will try to flash the RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed.
updating or rather downgrading with the cyanogen recovery does not work. it says: Can't open /sdcard/HEROIMG_.......release_signed.zip(bad).
so i will try flashing via fastboot
Did you get this resolved?
No, it doesn't work.
Now I even got no wifi. Could not activate it.
Does there exist a custom rom, that I could flash and that contains a newer hboot, which contains the eraseconfig command?
Hi,
I had exactly the same problem and used that post from modaco to get out of it. As I understand it, you have reflashed the first RUU, so you have SD access but still no USB, right?
When I got to that stage, I didn't use the 2nd RUU at all, I just reflashed the new SPL (update-hero-hboot-1.76.2007-signed.zip) which opened up the fastboot oem eraseconfig option. I was on 1.76.0007 already (check the S-OFF is displayed on the fastboot screen, that means the goldcard is working AFAIK)
Flashing that SPL was enough, I think the oem commands are in there rather than the ROM itself (since in fastboot mode, the SPL is the only thing that is running).
Hope that helps.
Where can I get this one?
OK, found it and will try it.
OK, i could update the SPL.
But eraseconfig does not make any change.
Now that I got the engineering SPL, I hopefully find a solution.
I will dive deep inside the forum and try to find a way to get my USB up and running.
Many thanks till now.
I can't find a solution, usb and adb still do not work.
What I've done:
- Tried "fastboot oem eraseconfig" --> no change
- "fastboot oem readconfig" gives:
INFOindex:0x0, value:0x0
INFOindex:0x1, value:0x0
INFOindex:0x2, value:0x0
INFOindex:0x3, value:0x0
INFOindex:0x4, value:0x0
INFOindex:0x5, value:0x0
INFOindex:0x6, value:0x0
INFOindex:0x7, value:0x0
INFOindex:0x8, value:0x0
INFOindex:0x9, value:0x0
OKAY [ 0.023s]
finished. total time: 0.023s
-"fastboot oem boot" gives:
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8F0841F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x1
INFOTAG:skuid 0x20800
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x3
INFODevice CID is not super CID
INFOCID is T-MOB101
INFOsetting.cid::T-MOB101
INFOserial number: HT97xxxxxxxx
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =350
INFOactive commandline: board_hero.disable_uart3=0 board_hero.us
INFOb_h2w_sw=0 board_hero.disable_sdcard=0 smisize=32 androidbo
INFOot.baseband=6.35.06.18 androidboot.cid=T-MOB101 androidboot.
INFOcarrier=TMD androidboot.mid=HERO10000 androidboot.keycaps=qw
INFOertz androidboot.mode=normal androidboot.serialno=HT97xxxxxxxx
INFO71 androidboot.bootloader=1.76.2007 no_console_suspend=1 con
INFOsole=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO0
INFO0
INFO69466957
INFO69784520
INFO69007473
INFO7473
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 6.158s
Hmm, all the uart_disable and sdcard_disable are set to 0, so it looks like the eraseconfig has done its job (in that sense).
Just throwing a few ideas around here.
Do you have access to the SD card now and/or wi-fi now? I guess we really need a way to get access to the logs, but without USB you might need to use a file manager and try to find them... you want the equivalent of adb logcat basically...
when you plug-in a USB cable to the device, do any of the notifications come up on the hero and what does it say under the charging info, is it charging(AC) or charging(USB)?
Could just be the PC drivers if the device is detecting USB now?
Charging works in both cases (AC/USB).
Still got no USB-Connection, no connection notification is coming up on the device.
On the device I can access the sdcard.
WiFi is not working anymore.
Just flashed Modaco 3.2 and WiFi works again.
Now i have root access with a file explorer.
OK, I installed that aLogcat-App that saves the log to SD. I will try to create some logs, plugging in the usb cable.
So, heres the log. There's something strange going on, I think.
See my comments
I connected the USB-cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 1
//--> unplugged = 1 ?!?!
D/dalvikvm( 234): GC freed 2834 objects / 153480 bytes in 138ms
D/dalvikvm( 183): GC freed 315 objects / 14504 bytes in 91ms
D/dalvikvm( 143): GC freed 215 objects / 8544 bytes in 133ms
D/KeyguardUpdateMonitor( 95): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 95): onRefreshBatteryInfo: 100
D/KeyguardViewMediator( 95): pokeWakelock(15000)
I/HtcLockScreen( 95): updateStatusViewByPriority
I disconnected the cable:
D/UsbConnectedReceiver( 248): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 248): unplugged = 0
//-> unplugged = 0 ?!?!
D/UsbConnectedReceiver( 248): USB Disconnected.
D/UsbConnectedReceiver( 248): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 248): ADB Enable = true
// --> enable adb on disconnect ?
D/UsbConnectedReceiver( 248): ADB StartByMe = false
D/UsbConnectedReceiver( 248): Try to stop PSService.
Here is the log of a friend that has the hero too:
D/StatusBarPolicy( 136): cable plugged, mPluggedBatteryLevel=58
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 1
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 2
D/UsbConnectedReceiver( 300): USB Connected.
D/UsbConnectedReceiver( 300): mObexServerStarted=true
D/UsbConnectedReceiver( 300): mAtCommandServerStarted=false
D/UsbConnectedReceiver( 300): Try to start ATCommandService.
D/PSService( 300): onStart()
D/UsbConnectedReceiver( 300): Show Notification...
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=1
D/UsbConnectedReceiver( 300): mObexServerStarted=true mAtCommandServerStarted=true
D/UsbConnectedReceiver( 300): Show Notification...
D/MountListener( 136): handleEvent ums_connected
D/dalvikvm( 2363): GC freed 1621 objects / 82560 bytes in 129ms
D/dalvikvm( 300): GC freed 3754 objects / 615400 bytes in 106ms
D/dalvikvm( 300): GC freed 4448 objects / 776848 bytes in 101ms
D/MountListener( 136): handleEvent ums_disabled
D/MountListener( 136): handleEvent ums_disconnected
D/KeyguardUpdateMonitor( 136): receive ACTION_BATTERY_CHANGED
D/HtcLockScreen( 136): onRefreshBatteryInfo: 33
D/KeyguardViewMediator( 136): pokeWakelock(15000)
I/HtcLockScreen( 136): updateStatusViewByPriority
D/UsbConnectedReceiver( 300): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 300): unplugged = 0
D/UsbConnectedReceiver( 300): USB Disconnected.
D/UsbConnectedReceiver( 300): Catch USB Disconnect Event, USB cable does really not exist.
D/UsbConnectedReceiver( 300): ADB Enable = true
D/UsbConnectedReceiver( 300): ADB StartByMe = false
D/UsbConnectedReceiver( 300): Try to stop PSService.
I/ActivityManager( 136): Stopping service: com.htc.android.psclient/.PSService
D/UsbConnectedReceiver( 300): Server Start Up. ServerType=1 ServerStatus=0
D/dalvikvm( 2318): GC freed 8615 objects / 518960 bytes in 121ms
D/dalvikvm( 383): GC freed 3095 objects / 170360 bytes in 112ms
D/dalvikvm( 206): GC freed 2271 objects / 398152 bytes in 140ms
Related
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
Hi,
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
anybody any ideas?
external hd drives, mouse, usb sticks etc all work fine
Cheers
B
berre said:
When I plug my canon powershot camera into the archos 101 usb, it recognises my camera (message "external camera connected" or something like that) but when I look into the folder, it's empty... it doesn't show my pictures stored on the camera's sd card
Click to expand...
Click to collapse
Most camera's have a setting to change the usb mode from PTP to USB STORAGE. Have you tried to change that?
I've went through the menu's of my camera but doesn't look like it has this setting...
cheers
B
berre said:
I've went through the menu's of my camera but doesn't look like it has this setting...
Click to expand...
Click to collapse
When You connect your camera to a computer what OS is the computer running?
How is the SD card in your camera formatted?
Are the photos take in RAW format and not JPG??? Your archos won't be able to view RAW, which is a shame...
OS is XP, pictures are jpeg format.
I'll see if I can find out how the SD is formatted tonight.
cheers
b
file system of the SD card is FAT
I've tried connecting a USB card reader to read the SD card but I get the same behaviour as when I try to connect my phone
see topic http://forum.xda-developers.com/showthread.php?t=1123491
so I'm kinda stuck on getting the images on my archos 101... a person in the other topic suggested installing urukdroid, would this help?
cheers
B
I have the same problem. It worked fine before, then one day I connected it and it wasn't working. Didn't change anything on the camera.
It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device
fzelle said:
It is sadly a known problem with the 101 that the USB breaks.
The only chance you have is to RMA the device
Click to expand...
Click to collapse
There's nothing in this thread that says hardware failure. Why would you say the only choice is to RMA it?
berre: You should do some testing mate. Install OSMonitor and use it to watch the dmesg output when you plug in the usb devices. Test a few USB Flash Drives, wireless mice, etc. As I've said, I certainly have trouble with some USB devices, but it's not an RMA situation.
As for getting the pictures on your 101, copy them to your PC, then copy over wifi, or connect the A101 to your PC, or use a microSD card in your camera with a microsd adapter, then you can just put it straight into the 101. Or move them to a usb flash drive if you can find a working one.
this is my alogcat
seems like it's discovering my camera (detects that it's a canon) but there's an error message "Parameter 'INTERFACE' not found"
anybody any idea what this means?
D/dalvikvm(12735): GC_FOR_MALLOC freed 3809 objects / 173920 bytes in 115ms
W/InputManagerService( 1319): Window already focused, ignoring focus gain of: [email protected]
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/cat ( 1174): <7>usb usb2: usb resume
I/cat ( 1174): <7>hub 2-0:1.0: hub_resume
I/cat ( 1174): <7>hub 2-0:1.0: port 1: status 0101 change 0001
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0002 evt 0000
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0101, change 0000, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: new high speed USB device using musb_hdrc and address 4
I/cat ( 1174): <7>usb 2-1: default language 0x0409
I/cat ( 1174): <6>usb 2-1: New USB device found, idVendor=04a9, idProduct=30fc
I/cat ( 1174): <6>usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
I/cat ( 1174): <6>usb 2-1: Product: Canon Digital Camera
I/cat ( 1174): <6>usb 2-1: Manufacturer: Canon Inc.
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/cat ( 1174): <7>usb 2-1: usb_probe_device
I/cat ( 1174): <6>usb 2-1: configuration #1 chosen from 1 choice
I/cat ( 1174): <7>usb 2-1: adding 2-1:1.0 (config #1, interface 0)
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/Vold ( 1223): Starting gphotofs
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=17302220 visible=true
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_MOUNTED dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver (has extras) }
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_MOUNTED
I/cat ( 1174): <7>/mnt/flash/releases/G8A/v2.3.25-r85838/arcbuild/linux/drivers/usb/core/inode.c: creating file '004'
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1 enable change, status 00000503
D/AosUpdate:MediaMountReceiver(12628): android.intent.action.MEDIA_MOUNTED / file:///mnt/storage/extcamera
D/dalvikvm(28664): GC_EXPLICIT freed 17329 objects / 1063424 bytes in 77ms
D/WifiService( 1319): ACTION_BATTERY_CHANGED pluggedType: 0
D/SiMiClock( 1717): onUpdate
I/ActivityManager( 1319): Starting activity: Intent { act=archos.intent.action.FILE_MANAGER dat=file:///mnt/storage/extcamera flg=0x10000000 cmp=com.archos.fm/.FileManager bnds=[0,58][980,122] }
V/alogcat (12735): save instance
V/alogcat (12735): paused
D/FileManager(12638): onResume: register the ActivityBackgroundResizer
D/ActivityBackgroundResizer(12638): onGlobalLayout
D/ActivityBackgroundResizer(12638): onGLobalLayout: 980x600
D/ActivityBackgroundResizer(12638): onGlobalLayout: no resizing required (980x600)
I/ActivityManager( 1319): Displayed activity com.archos.fm/.FileManager: 533 ms (total 533 ms)
D/alogcat (12735): stopping ...
D/alogcat (12735): stopped
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 3643 objects / 184896 bytes in 74ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 678 objects / 38768 bytes in 55ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 232 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 7 objects / 216 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 8 objects / 264 bytes in 27ms
D/dalvikvm(12638): GC_EXTERNAL_ALLOC freed 196 objects / 7064 bytes in 27ms
W/KeyCharacterMap(12638): No keyboard for id -1
W/KeyCharacterMap(12638): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/alogcat (12735): stopping ...
D/alogcat (12735): canceling periodic saves
V/alogcat (12735): started
V/alogcat (12735): resumed
D/alogcat (12735): starting ...
W/IInputConnectionWrapper(12638): showStatusIcon on inactive InputConnection
D/dalvikvm(31530): GC_FOR_MALLOC freed 310 objects / 443984 bytes in 124ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 222 objects / 439856 bytes in 75ms
D/SiMiClock( 1717): onUpdate
D/dalvikvm(31530): GC_FOR_MALLOC freed 167 objects / 435048 bytes in 38ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 73 objects / 430536 bytes in 76ms
D/dalvikvm(31530): GC_FOR_MALLOC freed 70 objects / 430424 bytes in 77ms
I/cat ( 1174): <7>hub 2-0:1.0: state 7 ports 1 chg 0000 evt 0002
I/cat ( 1174): <7>hub 2-0:1.0: port 1, status 0100, change 0001, 12 Mb/s
I/cat ( 1174): <6>usb 2-1: USB disconnect, address 4
I/cat ( 1174): <7>usb 2-1: unregistering device
I/cat ( 1174): <7>usb 2-1: usb_disable_device nuking all URBs
I/cat ( 1174): <7>usb 2-1: unregistering interface 2-1:1.0
I/Vold ( 1223): Stopping gphotofs
I/cat ( 1174): <7>usb 2-1:1.0: uevent
I/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}
D/VoldCmdListener( 1223): volume shared /mnt/storage ums
W/StorageNotification( 1319): setMediaStorageNotification type=4 icon=0 visible=false
D/MediaScannerReceiver( 4966): Just got intent Intent { act=android.intent.action.MEDIA_EJECT dat=file:///mnt/storage/extcamera cmp=com.android.providers.media/.MediaScannerReceiver }
E/NetlinkEvent( 1223): NetlinkEvent::FindParam(): Parameter 'INTERFACE' not found
I/Vold ( 1223): handleUsbEvent(): Missing property, ignoring event
I/cat ( 1174): <7>usb 2-1: uevent
I/BootReceiver( 6648): Got intent with action android.intent.action.MEDIA_EJECT
I/logwrapper(12750): /usr/bin/gphotofs terminated by exit(1)
I/cat ( 1174): <7>hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x100
I/cat ( 1174): <3>init: untracked pid 12770 exited
I/cat ( 1174): <7>hub 2-0:1.0: hub_suspend
I/cat ( 1174): <7>usb usb2: bus auto-suspend
D/dalvikvm( 4966): GC_EXPLICIT freed 1213 objects / 61504 bytes in 91ms
D/dalvikvm( 6648): GC_EXPLICIT freed 201 objects / 11520 bytes in 73ms
W/KeyCharacterMap(12735): No keyboard for id -1
W/KeyCharacterMap(12735): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
The (1223) shows that message is actually a different process, so I don't think that's related. Look at this line though:
/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {unmounted} -> {mounted}
Notice it says /mnt/storage/extcamera? And "state changed from unmounted to mounted"? Have you looked in that directory? I bet your pics are there.
nope, I think I checked that yesterday and folder was empty... I'll double-check tonight but unless there's a second extcamera folder, it was empty
cheers
b
confirmed, that directory is empty as well.
brgds
b
Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)
eagleofdeath13 said:
Maybe i'm wrong, but i think that this isn't the pictures folder, but the access to the camera, maybe Android want to use your camera as a camera (and not as a storage)
I don't really know, but, with my little linux knowledge i think that it's possible.
(In Linux everything is a file, even the hardware)
Click to expand...
Click to collapse
Everything is possible in Linux, but in this case, the mount is being handled by gphotofs, which is a PTP camera storage driver. It's supposed to mount PTP cameras as R/W filesystems, allowing you to access the stored photos. It's independently developed though, so I'm not sure where it got built in.
Gphotofs does not fully support Canon cameras, supposedly Canon locked their PTP to read only, and it's looks like development stopped in 2008, but it seems like it should still show the files though.
I know it's a big step, but I'd try Urukdroid. I don't have a Canon around to test with, but I'd be interested to see what happens. The 1.0 easy install can be done and set up in less than 10 minutes, with no linux or even windows knowledge needed.
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.
msticninja said:
One question though. In the log it shows the camera being disconnected and then gphotofs unmounts it. Does this happen immediately after mounting, or did you unplug the usb? If the log shows "/StorageNotification( 1319): Media {/mnt/storage/extcamera} state changed from {mounted} -> {unmounted}" before you actually disconnect the camera, then at least I know why the extcamera directory is empty. That would just leave overamping and canon PTP incompatibilty as the prime suspects.
Click to expand...
Click to collapse
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B
berre said:
I unplugged the usb so that's normal... first I'm gonna try another usb sd card reader as workaround
I'm not scared of urukdroid but a bit reluctant to void my warranty, especially seen the USB issue which seems to be quite common. I also want to see what the new firmware is all about (next week?)
But I think I might be going for urukdroid anyways as my storage for apps is running out
cheers
B
Click to expand...
Click to collapse
Hmm, I wonder about gphotofs then. If I get some time I'll research it. As far as Uruk, Archos trolls the forums. They've seen our firmware, and they can't really make a case for it doing any real damage. If you have to send it back for replacement, just reflash the original firmware. They don't bother asking, and so far everybody I know with the "SDE Watermark" has gotten a replacement without issue.
This is mostly a post about a specific problem with Google Play carrier billing.
Here is the problem:
I want to subscribe to a trial of Google Play Music All Access
I want to use carrier billing (with my Verizon Wireless phone)
When I select "Bill my Verizon Wireless account", I get a red message stating "Error processing your purchase"
Notes:
Carrier billing usually works for me with Verizon Wireless
I am NOT using WiFI while trying to make the purchase
I do not have blocks on messaging or web purchases with Verizon Wireless
Verizon Wireless support cannot find any reason why the purchase would fail
I am well below the $25/mo. cap for Verizon Wireless carrier billing (I've only spent $.99 this month so far)
Step by step:
I turned off WiFi on my android phone (mostly stock rooted Samsung Galaxy Nexus running JB 4.2.2 on VzW).
I plugged my phone into my PC with the USB cable.
USB debugging is on.
I fired up adb shell on my PC.
I used su to start a superuser shell in adb
I typed:
Code:
logcat | grep --color=auto -i -E 'play|market|store|carrier|billing|finsky|phonesky|vending'
I launched Play Music (version v5.0.1041J.689753)
I opened the menu (...)
I selected "Settings" from the menu
I selected "Try All Access for free" in settings
I was sent to a "Google play" screen titled "Try Google Play Music All Access"
I selected "Try it FREE"
A modal dialog box opened titled "Google Play Music All Access"
From logcat:
Code:
I/ActivityManager( 378): START u0 {act=com.android.vending.billing.PURCHASE cat=[android.intent.category.DEFAULT] pkg=com.android.vending cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity (has extras)} from pid 8403
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity: +121ms
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity (has extras)} from pid 1708
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.PurchaseActivity: +153ms
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I clicked "Free"
I clicked "Payment options"
I clicked "Bill my Verizon Wireless account"
From logcat:
Code:
I/ActivityManager( 378): START u0 {cmp=com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity (has extras)} from pid 1708
D/Finsky ( 1708): [1] SelfUpdateScheduler.checkForSelfUpdate: Skipping DFE self-update. Local Version [80210006] >= Server Version [-1]
I/ActivityManager( 378): Displayed com.android.vending/com.google.android.finsky.billing.lightpurchase.billingprofile.BillingProfileActivity: +140ms
D/PlayEventLogger( 1708): ActiveExperiments changed, sending with next LogEvent
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
E/Finsky ( 1708): [186] FileBasedKeyValueStore.delete: Attempt to delete 'params...' failed!
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
I/qtaguid ( 1708): Failed write_ctrl(u 41) res=-1 errno=22
I/qtaguid ( 1708): Untagging socket 41 failed errno=-22
W/NetworkManagementSocketTagger( 1708): untagSocket(41) failed with errno -22
D/Volley ( 1708): [155] BasicNetwork.logSlowRequests: HTTP response for request=<[ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133> [lifetime=14351], [size=7526], [rc=200], [retryCount=0]
D/Volley ( 1708): [1] Request.finish: 14363 ms: [ ] https://android.clients.google.com/fdfe/preparePurchase 0xe8d195d1 NORMAL 133
I get "Error processing your purchase." in red print
This line really got my attention:
D/Finsky ( 1708): [1] CarrierParamsAction.createCarrierBillingParameters: Carrier billing config is null. Device is not targeted for DCB 2.
I'm assuming "DCB" is "Direct Carrier Billing", and "DCB 2" might be something like a monthly subscription billed with carrier billing. I make purchases with carrier billling so I'm not sure why it would say "Carrier billing config is null."
To make sure carrier billing is working (still), I launched "Angry Bird Seasons", and went "shopping" for 80 power-up bundles for $4.99. I select the same options for "Payment Options" and "Bill my Verizon Wireless account" and "Buy" (bringing me to the "Confirm password" screen, where I canceled the purchase).
This line stood out from logcat:
Code:
D/Finsky ( 1708): [1] PurchaseFragment.runCompleteFlowAndContinue: Start complete flow for DCB3 instrument.
"DCB3" ???. Maybe another "Direct Carrier Billing" purchase type (for a one-time consumable purchase)?
Since Google Play is not open source, I have no way of looking at the code to see what these debug lines actually mean.
Can anybody give me any guidance on this?
Having the same problem with a rooted Droid RAZR. Does it on both the stock rom and CM10.1.
Edit: Called customer service. They are looking into it. Told me they should contact me back in 24/48 hours.
Hi,
Internation Pardus v15 image on rooted i9300, works very well except for this really odd USB connection error when connecting it to my Sony BT3900u car stereo, it was previously connecting without issue on the v15 Pardus build but for unknown reasons to myself now always presents an error.
Does anyone have any ideas as to what might be causing this issue? Any help would be greatly appreciated.
After getting this issue the first time, I ran through a full rebuild, wiped phone/cache/dalvick and error still persisted post rebuild.
Model:
GT-i9300
Android Version:
4.2.2
Baseband
I9300XXEMA5
Kernel version:
3.0.31-702147
Build Number:
Pardus HD Rom XV XXUDME7
Logcat:
E/MTPRx ( 8982): Read Error Came false
E/ ( 8982): read error [0] [Success]
E/MTPRx ( 8982): state from USB_STATE eventDISCONNECTED
E/MTPRx ( 8982): /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt: open failed: ENOENT (No such file or directory)
E/MTPRx ( 8982): stop observing and calling usbRemoved
E/MTPRx ( 8982): In usbRemoved Status bar enabled
E/MTPRx ( 8982): Sending Broadcast
E/MtpService( 8982): onDestroy.
E/MtpService( 8982): Unregister Mtp disable Receiver
E/MtpService( 8982): Receiver not registered: [email protected]
E/MtpService( 8982): unregistering mtpMediaReceiver in UnregisterAllIntent
E/MtpService( 8982): Receiver not registered: [email protected]
E/MTPJNIInterface( 8982): noti = 3
E/ ( 8982): ****** [mtp_usb_mtp_finalize] mtp_close_fd Calling
E/ ( 8982): [mtp_close_fd] fd = 50...
E/ ( 8982): [mtp_close_fd] USB endpoint [50] closed...
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Updating the gInitializeFlag Flag to FALSE
E/ ( 8982): ****** [mtp_usb_mtp_finalize] Calling mtp_stop_io
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input1/enabled: No such file or directory
E/SEC PowerHAL( 2447): sysfs_write : Error opening /sys/class/input/input8/enabled: No such file or directory
E/videowall-TranscodeReceiver(10572): broadcastMSG : android.intent.action.ACTION_POWER_DISCONNECTED
E/MTPRx (10600): In MtpReceiverandroid.hardware.usb.action.USB_STATE
E/MTPRx (10600): check value of boot_completed is1
E/MTPRx (10600): check booting is completed_sys.boot_completed
E/MTPRx (10600): Sd-Card path/storage/extSdCard
E/MTPRx (10600): Status for mount/Unmount :mounted
E/MTPRx (10600): SDcard is available
E/MTPRx (10600): The value of first_boot is 1
E/MTPRx (10600): [ 662] The value of first_boot is 1NORMAL SEQUENCE
E/MTPRx (10600): Received USB_STATE with sdCardLaunch = 0
E/MTPRx (10600): configured is false
I'm guessing this is the correct part of the log that pretains to the MTP/USB part. If not I have attached a full log.
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
xpmode said:
Try typing this in a terminal window or adb shell on your phone:
Code:
touch /data/data/com.samsung.android.MtpApplication/gadgetDisconnectAndConnect.txt
Or, make a txt file called gadgetDisconnectAndConnect and place it in /data/data/com.samsung.android.MtpApplication folder.
Click to expand...
Click to collapse
Hi, thanks for the reply.
I did that as quoted, nothing seems to have changed, What should I be looking for?
Thanks!
Hello everyone
I've managed to unlock and root my SGP312 (pollux_windy). Because I always liked AOKP, I tried to install this custom ROM. Here's what I did:
1) Flashed Little Kernel into /boot while in Sony's Fastboot Mode
2) Flashed extracted boot.img of AOKP into "boot" and newest TWRP recovery (v2.6.3) into "recovery" while in LK's Fastboot Mode
3) Rebooted into TWRP recovery, wiped data, cache and dalvik cache
4) Flashed newest AOKP version (jb-mr2 milestone #1 for pollux_windy)
5) Flashed gapps (gapps-jb-20130813-signed.zip)
And tada, the custom ROM booted and everything was fine... No force closes / crashes, no problems, everything worked like a charm.. except the god damn Play Store! Whenever I open the Play Store, it only says "No connection". Pressing retry doesn't help at all. Ofcourse I always search through some forums before posting an issue, so here's what I've already tried:
- Other custom ROM (CM 10.2 stable for pollux_windy)
- Other gapps package (pa_gapps-full-4.3-20131102-signed.zip)
- Force Google Play Store and Google Play Services to stop and delete their data
- Wiped cache and dalvik cache
- Tried a connection without native IPv6 (WLAN hotspot of my HTC One, going over mobile internet which is clearly IPv4 only)
- Checked /etc/hosts (only contains 127.0.0.1 localhost)
- Executed Shark for Root -> There is clearly some data activity going on, my tablet seems to send some data to the google servers but they return an empty response as it seems (see logcat down below)? Unfortunately I am not able to analyze the packets, thanks to SSL/HTTPS...
- Changed some build.prop settings to match an original installation (model=SGP312, device=SGP312 and so on...)
And none of these methods worked. I am totally clueless what else I could try? Here's a logcat snippet:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
My build.prop is now reverted to the original AOKP build.prop, which can be found here: dl.snapserv.net/build.prop.txt (Sorry, I am not allowed to post links yet...) Have you guys any idea? XDA is basically my last hope, otherwise it seems like I am doomed to use the stock ROM :/ Or did I do something wrong?
Thanks for reading and have a nice day!
Regards
NeoXiD
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
[/QUOTE]
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
bondcheg said:
Code:
D/Finsky ( 4435): [1] 12.onClick: b/5160617: Reinitialize account [00Z7aRpoYHPCeSI-XHfBz1uwqFI] on retry button click
D/Volley ( 4435): [221] DiskBasedCache.clear: Cache cleared.
D/Volley ( 4435): [225] DiskBasedCache.clear: Cache cleared.
I/qtaguid ( 4435): Failed write_ctrl(u 52) res=-1 errno=22
I/qtaguid ( 4435): Untagging socket 52 failed errno=-22
W/NetworkManagementSocketTagger( 4435): untagSocket(52) failed with errno -22
E/DfeApi ( 4435): [1] DfeRequest.deliverResponse: Null wrapper parsed for request=[[ ] https://android.clients.google.com/fdfe/toc 0xe8d195d1 NORMAL 21]
D/Finsky ( 4435): [1] ErrorStrings.get: No specific error message for: com.android.volley.ParseError: java.lang.RuntimeException: java.lang.NullPointerException: expected receiver of type com.google.android.finsky.protos.Response$Payload, but got null
W/NFC-LLC ( 1165): LLC length mis-match
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. (How I found that problem? I just went so far that I've intercepted the traffic to the google servers with a fake root certificate and Fiddler...) Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
NeoXiD said:
Same error on my Acer A500 TegraOwners Rom 4.3 MR2 v8t6. Cant find solution.
Click to expand...
Click to collapse
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD[/QUOTE]
I`m novice user and never conneced my device with adb and dont know how to do it.
bondcheg said:
In my case it was Little Kernel's fault. Little Kernel messed up the serial number, to the Google servers received "X-Device-ID: 0" instead of my serial number. Such requests will just get an empty answer, which triggers these logcat errors. If you connect your device with adb, do you see the correct serial or just some messed up unicode characters like yyyyyyy...?
Regards
NeoXiD
I`m novice user and never conneced my device with adb and dont know how to do it.
Click to expand...
Click to collapse
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
NeoXiD said:
Okay.. Then follow this guide here: http://forum.xda-developers.com/showthread.php?t=2141817 for installing ADB and execute the command "adb devices". Although, if you do not even know what adb is, you haven't probably flashed Little Kernel, so my solution might not be the right one. Have you tested any of my tries I've listened at the thread start?
Regards
NeoXiD
Click to expand...
Click to collapse
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
bondcheg said:
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
---------- Post added at 06:51 PM ---------- Previous post was at 06:46 PM ----------
A little bit hard for me. Try tomorror. But in windows the sireal number of my device looks like 000000m:.
Emm i done mostly all you listened at the thread start but nothing helps.
Only other ROMs works fine. In any other ROMs play market have no errors. But in case i done all as guides says why other people a500 with this ROM works fine but not mine?
Sry for my english.
Click to expand...
Click to collapse
That might be the fault then, because it might get interpreted as serial number '0', which might get rejected by Google. Did you flash any custom bootloader? Normally this should not occur... You can also drop me a PM so we do not spam this thread with a 4-eye-conversation.
Regards
NeoXiD