Dear All,
I updated DS to 2.3.3 ROM and got it rooted with StreakMod+Supruser method. I'm facing frequent issue of high CPU usage by /system/bin/hidkbd. (100% total CUP; battery drains in 3-4 hrs). This happens once in two or three days or so. I can't figure out the triggering event although I tried. I tried looking up for the issue, but couldn't find any pointers. Currently, I use OS Monitor to kill the process.
What's hidkbd? Is it a keyboard process? Anyone have some idea about how to fix the issue?
Thanks
I took log for this process using OS Monitor app and I'm pasting it below.
Code:
01/27/2012 03:11:25 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 03:11:25 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 03:11:25 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 03:11:25 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 03:13:34 [WARNING] PrintK(102) k[114]p[1]
01/27/2012 03:13:35 [WARNING] PrintK(102) k[114]p[1]
01/27/2012 03:13:35 [WARNING] PrintK(102) k[114]p[0]
01/27/2012 03:13:35 [WARNING] PrintK(102) k[114]p[1]
01/27/2012 03:13:35 [WARNING] PrintK(102) k[114]p[0]
01/27/2012 03:13:36 [WARNING] PrintK(102) k[115]p[1]
01/27/2012 03:13:36 [WARNING] PrintK(102) k[115]p[0]
01/27/2012 03:13:36 [WARNING] PrintK(102) k[115]p[1]
01/27/2012 03:13:36 [WARNING] PrintK(102) k[115]p[0]
01/27/2012 04:14:24 [VERBOSE] PrintK(102) <7>kevent_trigger: queue event work
01/27/2012 06:28:08 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 06:28:08 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
01/27/2012 06:28:08 [DEBUG] PrintK(102) <6>AUO_TOUCH: ts_irqHandler: before disable_irq()
Have you tried flashing DSC rom again and doing a factory reset?
Thanks cdzo72 for your reply. I've the Dell official Olleh 2.3.3 407 ROM installed on my DS. Since I already setup and customized everything, I would prefer not to factory reset and do all over again. Also I would like to get to the root cause of this issue so that I can avoid it in future.
I just came to know about this DSC ROM. Is it better than the original Dell ROM?
Do you know what is this hidkbd process? Do you know from where I can learn more about all the system processes in DS (or any Android device in general)?
techieNetizen said:
Thanks cdzo72 for your reply. I've the Dell official Olleh 2.3.3 407 ROM installed on my DS. Since I already setup and customized everything, I would prefer not to factory reset and do all over again. Also I would like to get to the root cause of this issue so that I can avoid it in future.
I just came to know about this DSC ROM. Is it better than the original Dell ROM?
Do you know what is this hidkbd process? Do you know from where I can learn more about all the system processes in DS (or any Android device in general)?
Click to expand...
Click to collapse
Unfortunately I don't have any info on what that process is for, but I can tell you that more than likely the only way to fix it is gonna be to do a factory reset. You don't know enough about your own system to read logcats and such so you got in a little over your head, you don't have much choice
Since the issue is not so critical, I'll see how far I can trace it; at least for some fun may be. It is possible that if I do factory reset followed by re-installing all the same apps, the issue can come back. At least if I get a hint on the culprit app, I can avoid it in the future. Anyway, thanks for you input.
Same problems here with /system/bin/hidkbd !!!
Dear all,
I can confirm the problem with this service also not only with DSC 1.4 - 1.5 rom also with original one from Dell (407 Olleh).
I tried different DSC installations, formatting the sd-card - nothing helps. Killing the process with OS Monitor triggers a system reboot.
Higher nice value helps a lot, but don't change nothing the fact that the battery is drained within a few hours.
Renaming hidkbd (or deleting) forces permanent system reboots: normal boot up to unlock screen (unlock slider don't work) then crash.
Any idea, how to fix this behavior? I attached hidkbd from my running system (It can be partially read by a hex capable text editor like midnight commander).
Best regards
xdakum said:
Dear all,
I can confirm the problem with this service also not only with DSC 1.4 - 1.5 rom also with original one from Dell (407 Olleh).
I tried different DSC installations, formatting the sd-card - nothing helps. Killing the process with OS Monitor triggers a system reboot.
Higher nice value helps a lot, but don't change nothing the fact that the battery is drained within a few hours.
Renaming hidkbd (or deleting) forces permanent system reboots: normal boot up to unlock screen (unlock slider don't work) then crash.
Any idea, how to fix this behavior? I attached hidkbd from my running system (It can be partially read by a hex capable text editor like midnight commander).
Best regards
Click to expand...
Click to collapse
Interesting.
hidkbd socket is used internally in framework by Dell (and me ).
Dell: dhcp renew (can patch the wifi service)
Me: wifi fixer (disable wifi fixer to identify is it the problem)
xdakum said:
Dear all,
I can confirm the problem with this service also not only with DSC 1.4 - 1.5 rom also with original one from Dell (407 Olleh).
I tried different DSC installations, formatting the sd-card - nothing helps. Killing the process with OS Monitor triggers a system reboot.
Higher nice value helps a lot, but don't change nothing the fact that the battery is drained within a few hours.
Renaming hidkbd (or deleting) forces permanent system reboots: normal boot up to unlock screen (unlock slider don't work) then crash.
Any idea, how to fix this behavior? I attached hidkbd from my running system (It can be partially read by a hex capable text editor like midnight commander).
Best regards
Click to expand...
Click to collapse
Sorry to hear that you too have the same problem. Now this issue has become part of my Dell Streak usage. I have Dell official (407 Olleh) installed and the Dell launcher replaced with Launcher Pro. Fortunately, I don't get reboots when killing the hidkbd process. Which launcher do you use? Only issue when I kill it is the clock time change. Do you have any wi-fi wake apps installed? Advanced Wi-Fi lock or something like that?
I don't know whether it would help, but my hidkbd file is attached. On comparison with npp editor, they are exactly same. Could someone without this issue upload their /system/bin/hidkbd file? May be I'll just swap the file and see whether it will work.
Most people who can't trace the issue to processes like hidkbd will see the symptom as "Dell Streak 5 heats up and battery drain in a few hrs" or "poor battery life" problem.
~techN
I had such report even when 351 hidkbd was used.
I suggest setting a crond job for that.
Hi all, I have searched the forum and the Web and found no solution, this is the only place that even has reference to my problem.
So, I'm also having an issue with 100% cpu load with hidkbd.
I'm using DSC 2.3.3 such a good ROM, seems to happen randomly whether being used or asleep,
I restored to factory, happened again that evening, and then updated to 2.2 from 1.7 with no luck.
Has anyone figured out what could be causing it, or has found a remedy?
Thanks
Dave
I addressed this issue in 2.2.
hidkbd is checked twice per hour and if high load detected - it's restarted.
Related
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
h2o pete said:
Had a wi-fi problem on my htc desire for a while now..
One time I went to turn wi-fi on and it just said "Unable to start wi-fi". It had worked totally fine up until that point.
I've tried doing a factory reset, rooted, updated rom but it's still not working.
When the problem happened I had not rooted the phone or changed anything really.. it just happened.
In logcat it says:
flg=0x10200000 cmp=com.android.settings/.wifi.WifiSettings bnds=[124,404][236,531] }
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
W/SyncAllWidget( 151): activeSynch is null false
I/ActivityManager( 79): Displayed activity com.android.settings/.wifi.WifiSettings: 495 ms (total 495 ms)
I/WifiHW ( 79): wifi_load_driver enter
D/SettingsWifiEnabler( 548): Received wifi state changed from Unknown to Enabling
D/dalvikvm( 1805): GC freed 3806 objects / 257536 bytes in 97ms
D/NetworkLocationProvider( 79): onCellLocationChanged [1363,22890]
I/WifiHW ( 79): wifi_load_driver end error 2
E/WifiService( 79): Failed to load Wi-Fi driver.
D/SettingsWifiEnabler( 548): Received wifi state changed from Enabling to Unknown
Anyone got any ideas on how to fix this?
Click to expand...
Click to collapse
I have the same problem on a ROM i have made... That's just for Tattoo not Desire... But it's the same logcat... So can somebody help us??
Yeah I'm pretty stuck on what to do :/.
Added some information about my software to the first post.
i have same problem on my htc dream
BUMP...
-------------------------------------
Sent from my übercharged HTC Tattoo
Fixed it by setting a static IP address.
Wi-Fi > Menu Button > Advanced > Use static IP
i had yesterday the same problem on my desire,
i fixxed this with flash a "older" stock rom and update it with the build-in updater....
same problem with my desire. how to fix it?
It's broke again. Setting a static IP doesn't fix it any more. Any ideas?
got the same problem here
can any one help???
Bump
Sent from my HTC Desire using XDA App
seems like wlan.ko is not available in /system/lib/modules/
I've had similar problems in the past, but was unable to solve them. You can check several things though.
1) wlan.ko in /system/lib.modules <-- has to match up with the kernel that you are using
2) any entries for wifi and/or dhcp in the init.rc and init.devicenamehere.rc files that are in the ramdisk in the boot.img
3) wifi settings in the build.prop
4) files in /system/etc/wifi
5) I'm not sure about this one, but even some of the files in /system/etc/firmware might have something to do with wifi.
6) files in /system/etc/dhcpd
7) any files in /system/bin and/or /system/xbin that are called by *.rc from #2.
Just take a working ROM (stock is usually what I use), and compare the files with the corresponding files in your build. I use either WinMerge or N-way Folder Compare or just plain old 'diff' in Linux.
I had the same issue.
Flashed a new ROM with full wipe etc. Wifi OK.
Flashed a kernel update on top of the ROM. Wifi broken. Turning wifi on it would error and turn off again.
The only way I could fix it was to flash a full ROM and make sure I wiped everything from the recovery.
Any more info you can provide? Current ROM +version +any other mods applied like status bar or OC kernels?
Did anyone fix this?? I am stuck here, G1 Dream
CM 5.0.8 DS
Please help!!!
Are you getting the same error in logcat as others have? If so, I think .mak fixed it, but he never let us know how.
Same Issues...
Ive tried Reverting to CM 5.07, 5.07 and now the beta 6.0 and all have yet to fix the wifi issue. I also tried switching between the radio's and doing a full format/partition and wipe. Any fix to this yet?
That was Lovely Bro...Really Useful...I got my DESIRE today and could connect to WIFI but was unable to browse...This tip helped me...Thx a lot... Keep up the good work..
Trying to replace bcm4329.ko
I did the OTA update for my Desire today, and of course have the wi-fi problem.
However, when I enable wi-fi, I see the following appear at the end of dmesg:
Code:
<3>[ 8197.511535] bcm4329: version magic '2.6.32.15-g6a358a9 preempt mod_unload
ARMv7 ' should be '2.6.32.15-gf9c0527 preempt mod_unload ARMv7 '
The update zip (via thread 778852) contains a bsdiff patch file patch/system/lib/modules/bcm4329.ko.p... and from some examination of that file it appears just to patch the vermagic field of the .ko file.
I tried to use a hex editor to 'fix' bcm4329 and used adb pull/push to replace it, but I get
Code:
failed to copy 'bcm4329.ko.fix' to '/system/lib/modules/bcm4329.ko': Read-only
file system
Can anyone help me with this?
Update: I am a fool. I was using the wrong goldcard! Once I put the right goldcard in, then sdcard:update.zip applied correctly and wi-fi started working again.
@dleonard, could you please make step by step instructions of how to fix this wifi issue?
thanks
Mixu
I bought a new Samsung GT-S5570 (stock ROM: Android 2.2.1, baseband S5570XXKB2, kernel 2.6.32.9-perf root(at)DELL106 #1, build FROYO.XIKF1).
I set the Wi-Fi sleep policy to Never, to keep it always on, I installed a few very popular apps from the Market and used the phone normally.
After a random number of hours (10-20 or so) the phone hangs: black screen, no response to keypresses, no ringing if I call from another phone (but at the other phone I hear the normal ringback tone). The only thing I can do is press the power button for 10 seconds to restart the phone.
Sometimes if I just wait for one hour or so the phone starts working again, but the wi-fi doesn't work anymore until I reboot.
I tried it with a different access point and it was the same.
I brought the phone back to the store and they gave me another GT-S5570.. it was exactly the same.
The last time, when the phone woke up, I could read the following kernel messages repeated many times per second:
Code:
09/26/2011 01:00:23 [ALERT] Debug Assert Caught, File /SRC/S5570_MAIN_WORKING/Android/kernel/../system/wlan/atheros/AR6kSDK.3.0/host/os/linux/../../hif/sdio/linux_sdio/src/hif.c, Line: 848, Test:status == A_OK || status == A_ECANCELED
09/26/2011 01:00:23 [ERROR] mmc1: Data CRC error
09/26/2011 01:00:23 [ERROR] msmsdcc_data_err: opcode 0x00000035
09/26/2011 01:00:23 [ERROR] msmsdcc_data_err: blksz 24, blocks
09/26/2011 01:00:23 [INFORMATION] mmc1: Controller has been reset
09/26/2011 01:00:23 [WARNING] pc_clk_set_rate id : 21, rate : 144000
09/26/2011 01:00:23 [WARNING] pc_clk_set_rate id : 0, rate : 144000
09/26/2011 01:00:23 [WARNING] , rc : 0
09/26/2011 01:00:23 [ALERT] AR6000: SDIO bus operation failed! MMC stack returned : -84
Logcat only showed a one hour long black hole:
Code:
09/25/2011 22:59:33 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 22:59:35 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 23:00:33 [DEBUG] WifiService(177) [mPersistState] : On
09/25/2011 23:00:34 [DEBUG] WifiService(177) [mPersistState] : On
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) onWakeKeyWhenKeyguardShowing(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) wakeWhenReadyLocked(3)
09/26/2011 01:00:26 [DEBUG] KeyguardViewMediator(177) handleWakeWhenReady(3)
09/26/2011 01:00:26 [ERROR] power(177) *** set_screen_state 1
How can this be possible? Hardware fault? Buggy driver? Are all the GT-S5570s affected?
Thank you
I brought this second defective phone to the store and they gave me another GT-S5570 (different colour this time! ).
On this third phone I did not install any of the apps I had installed on the previous ones and I didn't even put my SIM card in. I just configured a wi-fi connection and set the Wi-Fi sleep policy to Never.
Here we are again. I just found it like this: black screen, no response to keypresses, completely dead until I press the power button for 10 seconds.
Is the Samsung Galaxy Next/Mini GT-S5570 a broken phone? Am I missing something?
Hi, if you have warranty just change your phone but I believe you are having problem with your OS I mean is a soft problem
Enviado desde mi GT-S5570 usando XDA Premium App
I did it. I already changed three different GT-S5570s and they all had the same problem. They all had the stock OS.
I tried with two (very different) wi-fi access points. In the last phone I did not install any app.
are you successfully using the wi-fi connection always on for many hours?
Yes I am I'm using emanon rom and I'm not having any problem
Sent from my GT-S5570 using xda premium
jacopoL said:
I bought a new Samsung GT-S5570 (stock ROM: Android 2.2.1, baseband S5570XXKB2, kernel 2.6.32.9-perf root(at)DELL106 #1, build FROYO.XIKF1).
I set the Wi-Fi sleep policy to Never, to keep it always on, I installed a few very popular apps from the Market and used the phone normally.
Click to expand...
Click to collapse
Jacopol, you made my day. My phone used to crash the same. I stopped setting the wifi-policy to "Never" and it does not crash any more! Thanks for a great workaround.
The ar6000/ar6k does not look reliable in Gingerbread Galaxy; you can find plenty of other people on the web complaining about it. I personally have experienced another problem with it: sometimes it just refuses to load. When trying to enable wifi the on-screen button turns green for a split second and then grey again. alogcat displays: "INFO: ar6000.ko failed to load" (yes, at the "INFO" level...)
It was incredible for me to find a hardware/driver problem like this in a production device from a quite big brand. I tested three different phones and they were all affected: no always-on wi-fi connection was possible.
I ended up asking for my money back and I bought another phone.
skew4 said:
Jacopol, you made my day. My phone used to crash the same. I stopped setting the wifi-policy to "Never" and it does not crash any more! Thanks for a great workaround.
Click to expand...
Click to collapse
I unfortunately have to take some of that back. Thanks to this workaround it crashes... LESS OFTEN
It also seems to be highly environment/AP-dependent, roaming across APs making it worse.
jacopoL said:
It was incredible for me to find a hardware/driver problem like this in a production device from a quite big brand.
Click to expand...
Click to collapse
I guess many people are not affected.
Looks like gingerbread fixed this... crossing fingers.
Hi Galaxy SII gurus
I run "intratech" 'official stock firmware' with corresponding
"cf-root", I have done so for various gingerbread and I am doing now
for various ICS.
currently
GT-I9100_XEN_I9100XWLPD_I9100XXLPW_I9100XENLP5.tar.md5
CF-Root-SGS2_XX_NEE_LPD-v5.5-CWM5.zip
Once system is stable it runs stable for days/weeks, -but-, my
problem (as also mentioned in xda thread 1635302) is that, when I boot
(this problem has been there with gingerbread and is still there with
ICS):
- system_server uses CPU (load and temperature rise)
- watchdog kills android processes (linux kernel stays up)
and, this goes on in a loop, often for hours. I need to power off and
try again (say, next day when battery again charged and temperature
dropped).
Only with -much- luck it happens that the system boots to a cam
state. and then I can use the phone normally. In fact, it works
perfectly then.
Recently this problem seems to become more prevalent and I have not
been able to use the phone for several days (each time I boot it goes
into, and, not out of, the watchdog loop). In practice, what happens
is that
- all applications (including launcher die)
- system goes back to the animated samsung logo
this loop goes on.
I searched a bit and it seems other people have reported this too but
I don't find a solution. Any help is appreciated.
'top', right after boot
Mem: 824396K used, 26136K free, 0K shrd, 36632K buff, 250616K cached
CPU: 53.1% usr 0.9% sys 0.0% nic 45.7% idle 0.0% io 0.0% irq 0.0% sirq
Load average: 2.84 1.85 0.74 2/1595 6055
PID PPID USER STAT VSZ %MEM CPU %CPU COMMAND
2082 1830 system S 401m 48.2 0 52.4 system_server
5628 1830 app_208 R 297m 35.8 0 0.5 berserker.android.apps.sshdroidpro
...
I use ssh and rsync to backup to a linux server, so I have a some
files that may be of interest (note that ssh and rsync are not killed
so I can incrementally backup).
/data/log/ contains a file
-rw------- 1 1000 1000 677553 Jun 5 06:07 dumpstate_sys_watchdog.txt.gz
/data/system/dropbox/ -many- files (presumably one per loop)
-rw------- 1 1000 1000 14416 Jun 5 06:07 [email protected]
-rw------- 1 1000 1000 0 Jun 5 06:08 [email protected]
-rw------- 1 1000 1000 261 Jun 5 06:08 [email protected]
for example, I have these files 58 times on 'Jun 5 ' only.
I have captured dmesg and logcat in a file screenlog.txt as follows
- freshly booted phone
- do a first 'dmesg'
- start 'logcat'
- start google play market app and update 2 apps
**** watchdog ****
- wait a bit
- do another 'dmesg'
The information is somewhat overwhelming but one can 'grep' for
watchdog, temperature and system_server processes 2082 and 7102, and
what else..., like, it seems cpu1 turns off/on all the time after
watchdog. Also, sorting the logs gives nice view per category.
Again any help is appreciated!
Thanks
Hi everybody
I feel a bit ashamed to reply my own post, but, here is what I can say
about progress:
I have (in approximately one week) once been able to get a 100% stable
system, but then, after some hours/day of playing around, time came to
reboot, and, since then, I am in the same system_server watchdog loop
for days now: I can do a little bit of work (I am configuring apex
GIU) and then: 'the watchdog barks'.
Searching Google does not tell me enough about this system_server
watchdog boot loop situation, so I hope for rescue here.
Note that I use stock rom with just cf-root.
have a good weekend
ok then, hate to reply again ...
seems a cwm wipe of dalvik cache and regular cache can do wonders:
I booted into stable system again
spoke too soon :-( android boot loop again
here is my guess: I think SD card might have errors ...
final verdict: only complete wipe and reinstall works, (and it works)
however, having literally wiped and formatted nearly everything, ...
only heimdall could flash (others did no longer recognise GSII).
all runs well now (albeit with less apps and less data)
Hi!
I am currently working on a CM 7.2 port for the Dell Streak 5, which I want to share soon (I can't post this in the dev forum because I don't have enough posts written just yet). Currently I am trying to find a fix or a workaround for the following problem:
Sometimes, the Streak immediately reboots and shows the Dell logo. It just shows the following kernel logs (also written to LogCat):
Code:
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:09.348 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:09.348 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-03 19:13:10.430 W/PrintK ( 83): smd_diag, smem: DIAG ''
07-03 19:13:10.430 W/PrintK ( 83): ARM9 has CRASHED
07-0
When I searched the kernel source, it seems that the following lines in arch/arm/mach-msm/smd.c are responsible for this log output (ommitting the parts that are not compiled):
Code:
#if defined (CONFIG_QSD_ARM9_CRASH_FUNCTION)
void smd_diag(void)
{
char *x;
x = smem_find(ID_DIAG_ERR_MSG, SZ_DIAG_ERR_MSG);
if (x != 0)
{
SMD_CRASH_LOG( "%s, smem: DIAG '%s'\n", __func__, x);
queue_work(crash_work_queue, &smd_crash_worker);
}
}
#else /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
/* ommitted (not compiled) */
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
static void handle_modem_crash(void)
{
SMD_CRASH_LOG( "ARM9 has CRASHED\n");
smd_diag();
/* hard reboot if possible FIXME
if (msm_reset_hook)
msm_reset_hook();
*/
/* in this case the modem or watchdog should reboot us */
#ifndef CONFIG_QSD_ARM9_CRASH_FUNCTION /* return imediately for kernel to do something */
for (;;)
#endif /* CONFIG_QSD_ARM9_CRASH_FUNCTION */
;
}
It seems that the modem is crashing and forces the device to reboot. The severe problem is that sometimes the device ends up rebooting again and again, suddenly stuck in the Dell logo - so maybe the reboot performed by the modem is not correct. But in the optimal case the device should just reset the modem, and not reboot the entire device.
As the radio drivers are only available in binary form (of course) and the device already is EOL, I really need help to find a good workaround. Does anybody have a solution to this problem?
I discovered that there is a kernel driver available in arch/arm/mach-msm/reset_modem.c that sounds interesting. It should be able to reset the modem by writing the appropriate command to a kernel device, and which is compiled as a kernel module in the default Dell Streak kernel config. Has anybody tried this out yet?
Thanks in advance & regards
Marc
PS: I am using the Phoenix kernel by the DSC Team, added with some patches by _n0p_.
Hi Marc!
How severe this problem is?
Hi _n0p_!
It's very severe to me - I have a couple of these devices here, and it's really critical if they turn off during operation (and some of them don't even come back up again afterwards).
It would be better if the radio was reset on failure - I can afford that the devices do not have a radio connection for a couple of seconds. Or at least this is what I hope.
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
_n0p_ said:
There's a "System Type -> Reset Modem Driver" module option in kernel.
May sound dumb, but maybe it needs it?
Click to expand...
Click to collapse
I recompiled the kernel with this module built-in, but from what I read from the source code it's just providing a device /dev/reset_modem to enable users to reset the modem from userspace (as root). However, this will not be possible entirely if the kernel itself is rebooting already, leaving no chance to any userspace commands. I believe this has to be fixed in the kernel itself. Right now I am looking at the method smsm_reset_modem in the file smd.c which sounds quite interesting. Maybe I can deactivate the code for rebooting the device there and instead run code to reset the modem. Interestingly, setting CONFIG_QSD_ARM9_CRASH_FUNCTION to 'n' in the config leads to kernel compilation errors - so the Streak was never intented to resolve modem problems the better way...
By the way, a few minutes ago I was able to log a modem restart during the reboot loop with LogCat:
pastebin.com/9U3XPxdK (yay, I can not post links yet :/ )
This looks really ugly - but it could help during debugging the problem. It would be much nicer to know what actually forces the modem to restart... (is it possible to get the stack trace during runtime, maybe by using a special macro?)
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
deysmacro said:
cant you check on the build based on the cm7.2 that already at the dev section? if it is not all, at least some of it would help...
Click to expand...
Click to collapse
I don't know exactly what triggers the problem - maybe the devices run fine for a long time, but crash when using GPS + network in some odd way, or when the network type switched from 2G to 3G or back - I really can't tell.
As for CM 7.2, I had to build from the sources (both Kernel and CM) in order to do fixes to the ROM etc. Maybe I could try out the CM 7.2 build, but even if the problem would (not) exist there, too, I would be back to the start.
At least yesterday I tried out the reset_modem kernel module and tried all commands I could find in the source on the device /dev/reset_modem - it just crashed the modem and the device all the time, instead of one command which was effectively doing nothing. So back to the start... :-(
man... that does sucks... well... i wish you all the best nonetheless... :good:
Where's an interesting module param:
msm_smd_debug_mask
--
Also, according to:
Code:
#define MODEM_CRASH_NOTIFY_USER
extern void qi2ccapkybd_set_led(unsigned int light);
#define MODEM_CRASH_NOTIFY_USER_0 do {qi2ccapkybd_set_led(0x0);} while(0)
#define MODEM_CRASH_NOTIFY_USER_1 do {qi2ccapkybd_set_led(0xFFFFFF);} while(0)
It should blink leds on going to reboot.
--
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
_n0p_ said:
Marc, thank you! While looking at SMD i found the code that blinks leds on AMSS mismatch (finally!)
Click to expand...
Click to collapse
wow...! a discovery... ! :victory:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
_n0p_ said:
This actually leads me to think that we now free of "Blinking LEDs problem" and maybe, just maybe changing AMSS (BB) might help with modem reset problem.
I'm currently using 366 (manics told that it has good voice quality).
Click to expand...
Click to collapse
last time i downgraded from rom based on 407 to 366 and although the blinking led happens.. but phone continue to work like normal... :laugh:
and yeah... 366 does have a good voice quality... and not mention excellent cell tower reception... it is proven since i have been in the building where reception is pretty much poor.. but with 366... somehow it almost always full...
but since nobody make a custom ROM based on 366, i had to sadly use other ROM...
As it's a bit offtopic, let's continue here:
http://forum.xda-developers.com/showpost.php?p=28318630&postcount=4374
Hey _n0p_!
Yeah, that seems to be the code that leads to blinking LED sensor keys on wrong AMSS!
As for the AMSS/DSP1 partitions, I currently use the newest from the original Streak 407 firmware, which I flashed via 'fastboot flash amss amss.mbn' and 'fastboot flash dsp1 dsp1.mbn'. Maybe that leads to the problems.
So you would recommend downgrading to amss 366? Although it does not match the kernel version and Android version? Isn't this a bad idea in general?
And for the DSP1, which version do you recommend - also from 366? Or the complete 366 update.pkg?
I am currently testing the image I flashed after initially flashing the 407 package the correct way - maybe this fixes the problems. Otherwise I will try 366.
By the way: Is there a good overview available what all the other files do, e.g. fsbl.mbn, osbl.mbn, dbl.mbn and appsboot.mbn?
From what I know, DT.img is the bootloader, amss the baseband software and dsp1 the DSP software for audio. And I know it's dangerous to flash the files individually, as I was able to completely brick a device by just flashing one of these special partitions...
Well, i'm using 366 right now. Too early to tell a conclusion, but it seems like default audio output is lower then in 4062 BB.
So far no glitches.
And i'm using only AMSS.
--
AFAIK DT.mbn is firmware updater, but I might be wrong.
Also DSP also works for video processing as well.
--
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
_n0p_ said:
Almost forgot: it seems simple to disable bb error reboot.
Maybe it's worth giving a test?
Click to expand...
Click to collapse
Do you mean disabling CONFIG_QSD_ARM9_CRASH_FUNCTION in the kernel config? I did this, recompiled (had to fix a small include error after that, too) and tried it out - so far it crashed again after some time of usage.
BTW, how did you disable the AMSS version check? I guess you disabled the option CONFIG_QSD_OEM_RPC_VERSION_CHECK - but it's good to know.
I thought of simply trimming that rpc probe proc.
And you are right, that's the conf value plus needs ifdefing undeclared version check (in this case), variable.
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Hey n0p!
_n0p_ said:
Marc, it seems like
#if 0
//#ifdef CONFIG_BUILDTYPE_SHIP
SMD_CRASH_LOG( "%s: restart system\n", __func__);
queue_delayed_work(restart_work_queue, &smd_crash_restart_worker,
MODEM_CRASH_RESTART_TIMEOUT);
#endif /* CONFIG_BUILDTYPE_SHIP */
would reboot device only if modem in reset state and camera button is pressed.
Click to expand...
Click to collapse
I tried your code, as well as some other fixes. It always led to a kernel loop and the modem didn't come back, so in the end I just included a solution to detect the problem and continue to reboot the device.
From what I learned in the last few weeks, it seems the complete ARM processor goes down with the modem. In the end, it seems to be a hardware problem, because I noticed the following facts:
Even if I completely re-flash a device that shows an error, it still occurs - especially when the network is used.
Some devices do not show this problem and can run for a long time. Other devices that had this problem always continue to have this problem. Even after re-flashing and even using different amss/dsp1 versions and on the original software.
What's more: I also had the problem on a new device that never had a custom ROM on it. Yeah, using the original firmware.
So in the end everyone should be better off to throw away his device if this problem occurs.
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
EDIT: maybe it was related to Maps since I installed maps 7.x I don't see that process anymore!
moly82 said:
hi guys, I hope you can help.. I really googled a lot about this, and also made many tests on my phone and waste a lot of time, but couldn't find a solution yet.. also this seems to be affecting many other people, so I don't understand how is possible nobody found a fix for that until now..
(I'm posting in general section because this seems to affect any kind of phones running cm10.1 + gapps)
the problem is that if I go to manage apps > running apps, I see Media process (DownloadService) always running! that could drain my battery and/or download data, in any case I don't see a point in having it always running, so I would like to get rid of it!
what I discovered so far is that the process is related to both gapps and Downloadprovider.apk package included in any CM10.1 build, in fact:
1. the process starts appearing only after installing the gapps (I use a very minimal 4.2 gapps package, about 10mb only)
2. if I delete Downloadprovider.apk package from /System/App, the process doesn't appear anymore
The problem is that if I delete the Downloadprovider.apk package then I start getting gapps related FC's and phone becomes unstable (and very probably will not be possible to download anymore things from the browser and/or play store)!
So what could I do to safely get rid of that process? Maybe disable or freeze some other apps/processes? But I wouldn't know what to disable exactly..
guys please help me I am really getting crazy with that! also that could help many other people :good:
thanks a lot in advance
Click to expand...
Click to collapse
Maybe you have some program/app installed which uses the download manager? Some app trying to download an update outside of the regular mechanism? I don't see DownloadService running on my phone unless I instructed it to download something. Do you notice anything downloadmanager/media related in logcat? If in doubt, attach the phone to a PC, run the following commands and attach the resulting file ('attach_me.txt') here:
Code:
adb shell 'ps; echo -----------;logcat -v time -b main -b system -b events -d;echo -----------;dumpsys;' > attach_me.txt
Use the full path to adb if you need to.
This shows the currently running processes (ps), the contents of the main, system and event logs (logcat) and a snapshot of the current state of your phone (dumpsys). If there is anything there you don't want to show to the whole world edit the resulting file before attaching it here.
thanks a lot for the reply my friend
tonight at home I think I will be able to run the adb command you suggested me (in my home computer I have sdk installed)
so far I checked logcat in terminal ("logcat |grep edia" and "logcat |grep ownload") and this is what I got:
$ su
# logcat |grep edia
D/Vold ( 1197): Volume sdcard state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 1197): Volume sdcard state changing 0 (No-Media) -> 2 (Pending)
W/PackageParser( 1626): No actions in intent filter at /data/app/org.wikipedia-1.apk Binary XML file line #39
I/ActivityManager( 1626): Start proc android.process.media for broadcast com.android.providers.media/.MtpReceiver: pid=1765 uid=10011 gids={50011, 1015, 1023, 1024, 1028, 2001, 3003, 3007}
V/ActivityThread( 1765): android.process.media white listed for hwui
D/SystemUIService( 1701): loading: class com.android.systemui.media.RingtonePlayer
D/SystemUIService( 1701): running: [email protected]
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothHeadset.:273 android.bluetooth.BluetoothAdapter.getProfileProxy:1155 android.media.AudioService.getBluetoothHeadset:2198 android.media.AudioService.access$2800:104
W/ContextImpl( 1626): Calling a method in the system process without a qualified user: android.app.ContextImpl.bindService:1458 android.bluetooth.BluetoothA2dp.:160 android.bluetooth.BluetoothAdapter.getProfileProxy:1158 android.media.AudioService$AudioServiceBroadcastReceiver.onReceive:4087 android.app.LoadedApk$ReceiverDispatcher$Args.run:758
$ su
# logcat|grep ownload
I/ActivityManager( 1624): Start proc com.google.android.youtube for broadcast com.google.android.youtube/.core.transfer.DownloadService$BootReceiver: pid=2305 uid=10050 gids={50050, 3003, 1015, 1006, 1028}
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
W/ActivityManager( 1624): No content provider found for permission revoke: file:///data/data/com.android.providers.downloads/cache/downloadfile.apk
I'm attaching also screenshots of the process I'm talking about
EDIT: I reinstalled everyting from scratch as a new build by quarx came out.. it seems that installing only cm build + minimal gapps, that process doesn't show up. Later after I installed back all my apps (via app2zip flashable zip) the process showed up again.. so probably you are right and there is a certain app using that process.. but how can I understand which one has relation with that service? maybe YouTube as i see it mentioned in logcat?
delete
i could generate the logs you asked without using the pc but using the phone terminal and multiple commands.. i'm uploading them to my dropbox links are below thanks in advance..
http://db.tt/gJLBYeT7
http://db.tt/OahQ8Zf7
http://db.tt/KPUTy4et
YAFU what happened to you?
it seems to me after I installed latest maps 7.x the media > download process is not appearing anymore in running processes.. maybe it was related to sh*tty maps??? :fingers-crossed: