i did update ota and the phone works great for first day maybe 1 or 2 random reeboots, (not installing apps on day 1)
common symptoms
1 i seem to experience is wifi losing connection and having to restart wifi
2 random reboots often more than normal
i have tried everything to make these symptoms stop, factory reset i even did a fresh download of ics and fxz thinking maybe the phone did not update properly ota, i admit after i did this performance was improved with less bugs, but i still have the 2 issues i have listed, i just want to know if this is a common issue with these phone, i have heard there could be an issue with the radio i would just like to hear what other people think and maybe others with similar issues and if there is a way to data log information on phone to narrow down the probable causes.
All apps currently installed on phone including Stock Apps
(Root App Delete, accounts, alarm and timer app cache cleaner Avast mobile browser, calculator valendar, camera, cinex player, contact picture sync, downloads, email, emergency alerts, facebook, files, FM Radio, Gmail, Google+, Help center, local, Maps, Messenger, Mobile hotspot, My Gallery, My Music, Navigation, News and Weather, No-frills cpu control, People Phone, Play Books, Play Movies, PLay Music, Play Store Quick Office, QuickPic, Reboot Logger, Scan, G Search, Settings, Smart Actionsm Social Location, Stabiity Test v2.5 Superuser, Talk, Tasks, Text Messages, Titanium Backup, Usaa, Voice Commands, Voxer, XDA, Youtube, ZumoCast.)
The Apps Im using to log info are No-Frills Cpu Control to underclock to test reliability, Stability test v2.5 to stress cpu and ram, and Reboot Logger
Test 1
Max Clock Freq. 1.0GHz
Min. Clock Freq. 300MHz
Governor : Performance
I/O Scheduler : Deadline
Bat% : 50
StabilityTest V2.5 Settings/Info
Classic Stability Tests
Time Duration 10 minute Run
Max Batt. Temp Reached 31.0 c
Core 1 Successful Runs: 8
Core 2 Successful Runs:9
Ram Successful Runs: 58
After 5.5 minutes Core 1 slowed down with 5 runs and core 2 with 6 with bat temp at 30.0c
i stopped test after 10 minutes as it seemingly was stable even switching between apps during testing trying to freeze phone but it did have moments of hesitation but it did not reboot in test 1
Nerwork issue with Vodafone
I am facing network issue with Vodafone. Network is going off and coming back for few seconds. Sometimes its working fine but not sure when it will go off. I changed my service provider to Vodafone after I bought the phone and facing this issue with Vodafone only. For all other networks, there is no issue. Dont know how to tackle this. Is there any solution for this known issue, Or I have to change my network or phone ? Please help
At tarani, this is the second post I have seen you post in with a question that is completely unrelated to the thread itself. PLEASE don't do this. Search for your answer. A LOT. And I if you don't find it then create a new thread.
Sent from my SAMSUNG-SGH-I727 using xda premium
---------- Post added at 07:09 PM ---------- Previous post was at 07:08 PM ----------
darkowler said:
i did update ota and the phone works great for first day maybe 1 or 2 random reeboots, (not installing apps on day 1)
common symptoms
1 i seem to experience is wifi losing connection and having to restart wifi
2 random reboots often more than normal
i have tried everything to make these symptoms stop, factory reset i even did a fresh download of ics and fxz thinking maybe the phone did not update properly ota, i admit after i did this performance was improved with less bugs, but i still have the 2 issues i have listed, i just want to know if this is a common issue with these phone, i have heard there could be an issue with the radio i would just like to hear what other people think and maybe others with similar issues and if there is a way to data log information on phone to narrow down the probable causes.
Click to expand...
Click to collapse
Try a factory reset man. It has helped many with random issues like this.
Sent from my SAMSUNG-SGH-I727 using xda premium
Fall of Enosis said:
At tarani, this is the second post I have seen you post in with a question that is completely unrelated to the thread itself. PLEASE don't do this. Search for your answer. A LOT. And I if you don't find it then create a new thread.
Sent from my SAMSUNG-SGH-I727 using xda premium
---------- Post added at 07:09 PM ---------- Previous post was at 07:08 PM ----------
Try a factory reset man. It has helped many with random issues like this.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
i have already tried that as i stated, i personally found it is a problem with the Kernel, there isnt 1 solution i havent tried to fix these issues, you can't quick fix buggy software, i have been data logging my phone device and it seems that when the phone hits certain frequencies on cpu it restarts, usually mid to high cpu usage, that is why i believe it is a kernel issue, its not something that can be fixed by clearing cache, factory reset, Fresh ICS FXZ, not insatlling any apps, i have tried all of these things and i resorted to data logging to narrow down issues, i only started this thread in the hopes of more people would data log there devices and check it so often to see statistics after random reboots and verify causes
darkowler said:
i have already tried that as i stated, i personally found it is a problem with the Kernel, there isnt 1 solution i havent tried to fix these issues, you can't quick fix buggy software, i have been data logging my phone device and it seems that when the phone hits certain frequencies on cpu it restarts, usually mid to high cpu usage, that is why i believe it is a kernel issue, its not something that can be fixed by clearing cache, factory reset, Fresh ICS FXZ, not insatlling any apps, i have tried all of these things and i resorted to data logging to narrow down issues, i only started this thread in the hopes of more people would data log there devices and check it so often to see statistics after random reboots and verify causes
Click to expand...
Click to collapse
Have you tried underclocking to see if that takes some stress off the CPU?
Sent from my MB865 running a beastly CM10
Actually im currently under clocking it to see if there are any reliability improvements, ill post feedback after i finish stress testing different clock settings
Sent from my MB865 using xda app-developers app
I am Currently starting test 2
darkowler said:
I am Currently starting test 2
Click to expand...
Click to collapse
Sweet I hope it works out for you bro.
Sent from my MB865 running a beastly CM10
Axis_Drummer said:
Sweet I hope it works out for you bro.
Sent from my MB865 running a beastly CM10
Click to expand...
Click to collapse
Anyone having a random reboot problem.. REMOVE YOUR MICROSD CARD, GO TO AN AT&T RETAIL STORE AND REQUEST A NEW SIM CARD. See if that solves your problem. Im sure it will. My logs showing a "modem kernel panic" were right.. it was a SIM Card that gave up the ghost, causing this intermittent ANNOYing reboot problem. I am now unlocked and rooted and it works perfectly fine.
03-16 01:42:35.604 1485 1586 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-16 01:42:35.607 1485 1586 E mdm_panicd: connection broken - recreate socket
03-16 01:42:35.607 1485 1586 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-16 01:42:35.607 1485 1586 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-16 01:42:35.607 1485 1586 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, got 0
03-16 01:42:35.607 1485 1586 D mdm_panicd: Unsolicited thread finished
03-16 01:42:35.607 1485 1485 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-16 01:42:35.607 1485 1485 E mdm_panicd: Modem reset detected (BP_STATUS 0). Reboot system!
03-14 10:51:56.041 1545 1560 E RDS : RdsReadSvrMsg: READ HEADER FAIL 0
03-14 10:51:56.041 1545 1560 E mdm_panicd: connection broken - recreate socket
03-14 10:51:56.041 1545 1560 I mdm_panicd: Subscribed to RDS_MSG_ID_UNSOL_IPC_FAILURE
03-14 10:51:56.041 1545 1560 I mdm_panicd: RDS Socket resd something on gUnsolicitedFd = 4
03-14 10:51:56.041 1545 1560 E mdm_panicd: Unsolicited message too short: expected at least 32 bytes, g
ot 0
03-14 10:51:56.041 1545 1560 D mdm_panicd: Unsolicited thread finished
03-14 10:51:56.047 1545 1545 E mdm_panicd: /data/panicreports/mdm_panicd.log created successfully!
03-14 10:51:56.047 1545 1545 E mdm_panicd: Modem power down detected (BP_RESOUT). Reboot system!
Related
I've been getting occasional random reboots EI22, and I've seen reports in the general forum of the same.
There seem to be two main causes of reboots:
WIFI Related (bcm4329 DHD Bus Module TX Queue overflow)The reboots always happen when WIFI is on. The system will freeze up hard for about 10-15 seconds and then just reset. The LAST_KMSG file shows 60KB of nothing but the following:
Code:
[ 5315.816399] dhd_bus_txdata: out of bus->txq !!!
[ 5315.820979] dhd_bus_txdata: out of bus->txq !!!
[ 5315.825411] dhd_bus_txdata: out of bus->txq !!!
[ 5315.829922] dhd_bus_txdata: out of bus->txq !!!
[ 5315.834499] dhd_bus_txdata: out of bus->txq !!!
[ 5315.838929] dhd_bus_txdata: out of bus->txq !!!
[ 5315.843505] dhd_bus_txdata: out of bus->txq !!!
OneDram driver related reboots
After patching the WIFI related bugs I started to get these more often. Here is an example of the log leading up to the reboot.
Code:
[ 13.319028] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
[ 13.339579] [OneDram] dpram_drop_data, head: 319, tail: 319
[ 13.351715] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
[ 13.366965] [OneDram] dpram_drop_data, head: 319, tail: 319
[ 13.379178] [OneDRAM](dpram_write) Failed to get a Semaphore. sem:0, PHONE_ACTIVE:HIGH, fail_cnt:1
Another log sample from a reboot, right before it restarts...
Code:
[ 11.585629]
[ 11.585665] dpram_shutdown !!!!!!!!!!!!!!!!!!!!!
[ 11.590957]
[ 11.590986] dpram_shutdown ret : 0
[ 11.598695] Restarting system.
[ 11.600629] KERNEL:magic_number=0 CLEAR_UPLOAD_MAGIC_NUMBER
[ 11.608974] arch_reset: attempting watchdog reset
For the WIFI issue, I searched and found a set of patches on the linux driver project mailing list that address this issue.
See: http://driverdev.linuxdriverproject.org/pipermail/devel/2011-March/012948.html
After applying the patch verbatim I still got the WIFI related reboots, so I slowly pushed the TXQLEN values up until the reboots stopped. Here is the commit from my github that contains the patch that seems to have done the trick.
As for the OneDRAM related reboots, I think I may have found the solution to these too. The problem seems to have gone away when I switched the specific ARM toolchain that is mentioned in the Samsung kernel source README. Previously I was using the 4.4.x toolchain from Googles repo. Thanks to Earthbound for working with me on this one. Aside from Earthbound (he uses the recommended Codesourcery one), I don't know what toolchains others use, but I do know that I have not had one reboot in the four days since switching to the CodeSourcery toolchain.
Here is a kernel (source) with the WIFI fix that was compiled with the 2009-q3-68 toolchain. Aside from the WIFI fix, the kernel contains the following features:
root/su/busybox
init.d script support
bootanimation.zip support
overclock to 1.4/voltage control
keyboard delay fix
ext4/rfs support
CWM5/ROM Manager support (reboot bml8 recovery)
If you are having WIFI or dpram/onedram related reboots, you might want to give this kernel a try and report back.
NOTE: If you overclock or over/under volt please stop doing so if you want to test this kernel and post logs.
Interesting I'll have to try it out, thanks for this!
Sent from my SPH-D700 using XDA Premium App
Thanks for this. Just need an EI22 branch now hehe.
Sent from my Epic 4G
I've experienced a few ramdom freezes and reboots lately even when overclocked to previously stable frequencies- ever since I successful ran with 1.5ghz enabled for two minutes.
I gave this a go, and overclocked to 1.4 and my phone went into a reboot loop- the rom booted up, but would freeze and reboot shortly afterwards.
I'm stable again now after running the VC cwm zip to restore settings to 1ghz.
Is there any useful feedback I could provide? Some sort of log or something?
Sent from my secret underground bunker
I just got another reboot...same issue.
So much for that!!
This bug is defintely causing the reboots though.
mjben said:
Is there any useful feedback I could provide? Some sort of log or something?
Click to expand...
Click to collapse
The system keeps logs in /data/system/dropbox
After a reboot the file with a name like " [email protected]" will contain a copy of the last system log buffer before your phone restarted.
But like I said I just got another reboot. I ran a speedtest over wifi using the speedtest.net app just before my last two reboots so I might be onto a way of triggering the bug.
I'm going to continue working on this. I'm experimenting with larger and smaller TXQLEN values.
Right now running with a TXQLEN of 4096 instead of 2048. It may be that larger is not better; that I needed to go smaller.
I'll keep my github updated.
So how was this different then froyo? Or did the tab ever have reboots?
sent from my always aosp epic
Excellent work!
I'd jump all over this but I stopped getting them after IAP 1.0.5+.
If they start up again I will report back.
the only time i have experienced this particular reboot concerning wifi, was having wifi + 4g enabled at home after a dalvik cache wipe (where the phone starts up, 4g starts first, then wifi simultaneously gets on LAN - both icons are showing, locks up - then reboot) once it restarts, it's all ok, wifi starts first, and doesn't happen again.
(running IAP samurai 1.0.4)
darkierawr said:
Excellent work!
I'd jump all over this but I stopped getting them after IAP 1.0.5+.
If they start up again I will report back.
Click to expand...
Click to collapse
AFAIK, the Earthbound is only mucking around with frequencies and voltages in his kernel. Of course I'm basing this on the only source he has posted, which was from two or three versions of his kernel back. He hasn't posted the source for any of this new builds, so apparently he still views GPL compliance as optional.
The reboots don't happen that often. I've gone many days without a single reboot and then gotten them multiple times in one day.
SenseiSimple said:
the only time i have experienced this particular reboot concerning wifi, was having wifi + 4g enabled at home after a dalvik cache wipe (where the phone starts up, 4g starts first, then wifi simultaneously gets on LAN - both icons are showing, locks up - then reboot) once it restarts, it's all ok, wifi starts first, and doesn't happen again.
(running IAP samurai 1.0.4)
Click to expand...
Click to collapse
No 4G service for me within 40 miles, so I never turn it on, but now that you mention it the lockups I've had have seemed to happen during that split second when both 3G data and Wifi icons show up in the top bar.
toadlife said:
No 4G service for me within 40 miles, so I never turn it on, but now that you mention it the lockups I've had have seemed to happen during that split second when both 3G data and Wifi icons show up in the top bar.
Click to expand...
Click to collapse
yeah maybe something about having two sources of internet... being assigned two addresses, no idea...
earthbound is stuck on the frequency tuning, but i think it's so stable because of the trunks he started with.
SenseiSimple said:
yeah maybe something about having two sources of internet... being assigned two addresses, no idea...
earthbound is stuck on the frequency tuning, but i think it's so stable because of the trunks he started with.
Click to expand...
Click to collapse
What trunk did he start from? He's got no history in github.
I'm assuming nubecoder's since his initial kernels had nubecoders broken video recording. I took a quick look a nubecoder's tree and nothing network related is touched there.
Anyhow in the general and Q&A forums have two reports reboots with Samauri 1.04, so that kernel is definitely not immune.
toadlife said:
What trunk did he start from? He's got no history in github.
I'm assuming nubecoder's since his initial kernels had nubecoders broken video recording. I took a quick look a nubecoder's tree and nothing network related is touched there.
Anyhow in the general and Q&A forums have two reports reboots with Samauri 1.04, so that kernel is definitely not immune.
Click to expand...
Click to collapse
yeah it's not immune, as i said it's happened to me, but it's appeared to me he started picking and choosing from nubernel into rodderick's clean kernel, and as he's said in his OP for samurai, there are elements of Genocide and other forerunners.. i forgot which, he's since removed the part where he says where his mods come from... he did at one point put in a fix for wifi issues, i'm not sure if it's in relation to the same issue (i think it was a general connectivity thing).
i have a short list of todo's for a kernel and have made headway but i really have no desire to compete with the 4 (including yours) on here.
SenseiSimple said:
i have a short list of todo's for a kernel and have made headway but i really have no desire to compete with the 4 (including yours) on here.
Click to expand...
Click to collapse
We are not competing. I just want my phone to be stable. Collaboration is what makes open source work. If you have ideas on how to make our kernels better share them.
@ toad
Iv'e been using your rom for over week and the e122 modem and have not had any reboots.
I do not overclock
I use 4g when i drive in a certain area to stream pandora faster and then it connect and reconnect to 4g
Ive connected wifi and 3g at the same time for picture mail and charging to my sprint account and still no reboot
Dangg.. I had no idea ppl had random reboots on ei22.. I've not seen one.
ksmullins88 said:
Dangg.. I had no idea ppl had random reboots on ei22.. I've not seen one.
Click to expand...
Click to collapse
I just had another one. This time it was the OneDRAM driver triggering a `reboot now`
CAn anyone explain what the OneDRAM driver does?
Toad,
Running your Kernel and Clean GB I had WiFi reboots every 3 to 4 minutes. WiFi would drop and go to the router for DHCP to hand out the IP again. I figured I would give you a chance to work on it and run rooted stock for a few days before trying Clean GB again as I like it! This same issue was even worse for me with ACS ICS v4.
Running rooted stock is a different story all together! I don't get the random WiFi drops, instead I get Android reboots with the freezing that's mentioned. Things run great for awhile before I get stuck in a loop of reboots. I noticed this last time that touchwiz lost all the bar icons besides the applications drawer icon. the bar also doubled in size along with the icon. Very strange!
Anyway, I was able to drop the default home between reboots this last time. The next reboot I launched ADW instead of TW. ADW instantly crashed and offered to email a bug report, So I did. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's really happening.
Anyway, I hope this long story may be of some help in tracking this issue down. It looks like quite a few people are having it, and I myself don't want to go back to Froyo
Cheers,
Dave
---------- Post added at 02:02 AM ---------- Previous post was at 01:53 AM ----------
Here is a copy of the stack trace I mentioned...
Stack :
=======
java.lang.RuntimeException: Package manager has died
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2062)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
... 7 more
Cause :
=======
java.lang.RuntimeException: Package manager has died
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2062)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
Caused by: android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
... 7 more
android.os.DeadObjectException
at android.os.BinderProxy.transact(Native Method)
at android.content.pm.IPackageManager$Stub$Proxy.getApplicationInfo(IPackageManager.java:1280)
at android.app.ContextImpl$ApplicationPackageManager.getApplicationInfo(ContextImpl.java:2057)
at android.app.ContextImpl$ApplicationPackageManager.getResourcesForApplication(ContextImpl.java:2554)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.b(Unknown Source)
at org.adwfreak.launcher.LauncherModel.a(Unknown Source)
at org.adwfreak.launcher.ck.run(Unknown Source)
at java.lang.Thread.run(Thread.java:1019)
**** End of current Report ***
Hello,
Although my post count will show I am totally new here. I am quite comfortable with flashing/etc.
I have been running the Synergy rom since 1.4 and I absolutely love it.
(full wipe of the phone)
I recently installed the R67 nightly (wiped cache/dalvik)
After R67, I noticed that my browser would not load pages completely. It would show about 90% on the status bar and it just stops.
I have had the problem before on my HTC Incredible so I went through the normal motions.
Tested Wifi/3g/4g....all show the same behavior.
Cleared "data" for the app...
Cleared app cache....
Wiped system cache...
Force closed the app...
This was all still showing the same result.
I installed Chrome...same result?
That kinda threw me...I was expecting it to be limited to the stock browser.
I installed Firefox...eureka! it is working now....for about 4 pages...now the same thing is happning to it.
I hate to even appear to be calling out the Synergy guys. I think they have a great ROM, but it is the last thing to change on my phone. So I am reaching.
I did go through a few recommendations from other phone models, remove proxy from APN settings..etc..
I can not seem to figure it out.
Anyone else on R67 seeing this? Is it something more fundamental to the phone itself?
120 views and no reply...
I am assuming I am the only one with this issue?
iamxero said:
120 views and no reply...
I am assuming I am the only one with this issue?
Click to expand...
Click to collapse
Love your opening line, I am in the same boat in regards to post count!
Have you flashed over the latest R68? I did not use 67 at all, infact started at 64, played with some JB developments, and came back to the most current 68 (with a darkhorse rises awesome theme!). I did not have any browser issues on the 64 build, and have "none" on the 68 build - well sort of: I have noticed that when I have been on wifi for a while, when disabling wifi, the data connection (which shows in the status bar as ok) seams to freeze up. Similar symptoms of what you described. What I had to do was disable the auto wifi connect, open an instant data drawing app (play store), close it, re-open it once or twice and boom! 4g data as advertised snaps back into action without any issues until I start using wifi again for a long period. This freeze appears to only happen when the auto wifi connect is enabled (need to verify that a bit). I would flash the current nightly and test. Chrome also seams to work a bit better than the stock browser, as it should. Stick with the rom, as you know its great. Hope that helps.
Hello,
the forum rules do not allow to post in "Development" section, so I am posting here.
I've installed CM 7.2 ROM for ChaCha from this Thread. (Build date: 20120824).
After reboot everything looked normal, there were minor lags, but since this was my first custom ROM, I assumed that it could be related to my performance settings (Governor: conservative CPU: 245 - 800Mhz). I've switched off all data connections (gps, mobile network, wifi) and disabled all animations to see how much battery it will consume in first 24 hours. To my surprise, the phone was off and battery was completely empty in the next morning.
I've installed CPU+Temp system widget to monitor CPU load. The widget showed that on idle system CPU usage was 98%-100% on maximum allowed frequency. After reboot the idle system CPU was normal - 1-10% on 245Mhz. Then I switched on Wifi and noticed that CPUusage started to increase. I've disabled wifi but CPU usage was up to maximum and didn't drop until reboot. I found that the same problem occurs with mobile network connection.
I opened Terminal and typed "top -m 6" to see which process is using the CPU. I found that system_server.so was taking up to 90% of CPU when the problem occured. "top -m 6 -t" showed that GPSLocationProvider thread of system_server.so was using all the CPU, in despite that GPS was always off.
I've started to search the solution of this problem and found this thread, which described that the problem is that librpc.so is not compatible with HTC gps drivers.
Then I've tried SuperOSR ROM and CM9 ROM. Both did not have this problem, which was interesting since SuperOSR is very similar to CM7.2. I've returned to CM7.2 and tried to solve the problem.
I updated the HTC drivers to the latest level (gps.chacha.so and others from the latest stock rom), but it did not affected the problem.
Then I did the binary compare of /lib/*.so between CM7.2 and SuperOSR and found that just a few libs was different. One of them was above mentioned librpc.so. I've installed librpc.so from SuperOSR to CM7.2 and the problem was gone.
The CPU usage now is 0%-4% when system is idle.
I hope that it will help others which is affected by this problem and I also wish that this bug could be solved in CM7.2.
can we use this metode for CM9?
HTC Chacha with CM9
This problem is not reproduceable on CM9 on my device. I believe you have different problem with similar symptoms. If you are experiencing 100% CPU load on idle device, open terminal and run "top -m 6" to find which process is using CPU and "top -m 6 -t" to find specific thread.
More likely you are running some widget which causes hang.
Thanks for the info! CPU usage was fixed to %100 before I did what you said! Thanks again :cyclops:
I'm relatively new here...and to rooting... I do a heckuva lot more reading than posting here...and searching this problem brings a wide variety of other people's similar experiences and the solutions they've tried...but most of them are not exactly what I'm experiencing. The one case that matches exactly, never found a solution...
So here's my case... Every time I reboot my phone, it boots normally...and 3-7 minutes later, system_server begins hogging up CPU%...freezes...then reboots the phone. This cycle goes on forever. I have successfully used several different solutions, but the fix is not repeatable...it works once, but if I need to use the fix again, it won't work...
My current setup: Inspire 4g, Viper 1.2.3, BeastMode v0.5, oc 1497 interactive gov. (set on boot NOT checked)(no additional CPU or voltage tweaks)...I also had this problem with TrickDroid, before I ever tried overclocking...although my gut tells me the problem is related to oc, it occurs whether or not max speed is the stock 1024 or faster...
Here's what I've tried that has worked at least once, but failed to work ever since:
Turn off data and wifi connections
Turn off data, wifi, autosync, gps
Wipe cache and dalvic
Wipe cache, dalvic, fix permissions
Wipe cache, dalvic, dirty flash rom
Turn off data, wifi, autosync, gps, autorotate
Wipe data, cache, dalvic
Wipe data from setCPU and uninstall it
Install kernel BeastMode v. 0.5
And the only solution that works every time is....full wipe, reflash rom...once I do this and system is stable, I can build everything back up....flash BeastMode kernel, restore apps and home screens, even overclock...everything stays stable and works perfectly...
...but, you know... It's impossible to resist the urge to tweak something, flash something...or do SOMETHING that requires a reboot...and that's when the problem occurs...
Every. Single. Time.
Is there anyone here that can share some knowledge, or point me to some buried thread I haven't found after weeks of searching??
One more bit of info that may or may not be related...I dunno... I've tried overclocking with both setCPU and Juice Defender Ultimate...set on boot is always left UNCHECKED...however, the settings seem to stick anyway...randomly...sometimes it does, sometimes not...
Please...if you can help me, or educate me, or point me in the right direction, or have any thoughts or some personal experience with this bug...post here... I'm very interested in your ideas...
Sent from my Inspire 4G using xda-developer's app
This sucks...
Here's a possible solution...but it sounds complicated... I guess setCPU changes something...
http://forum.xda-developers.com/showthread.php?t=983524&page=2
I'm probably just going to screw up the phone if I go trying to edit files...if I can even find this file.
*frustrated*
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
RuggedHunter said:
I've reset permissions to 700 for /sys/devices/system/0cpu/cpu/cpufreq/stats/time_in_state... My phone stayed stable for about the same amount of time...4 days...then it rebooted and went into the boot loop again.
Nothing fixes anymore except fullwipe/reflash...but I can restore my tweaks settings, overclock, restore apps and homescreens, etc pretty quick now, and it stays stable for a few days...so once every four or five days isn't THAT bad I guess...
Sent from my Inspire 4G using xda-developer's app
Click to expand...
Click to collapse
Just for ****z and grinz, have you tried wiping and just installing a plane Jane ROM and not tweaking anything other than installing most used apps? My suspicion is that the kernel you are using or one of your power/super teaks are messing with your hardware and causing the issue. Try just using a base ROM for a week and resist tweaking it during that time. Then add addition tweaks on a weekly bases till it becomes unstable again. The you know what is causing it. I suspect the kernel since it is according to you used on all your ROM installs. Might try a different kernel if you must tweak from the get go.
Thanks man, that's great advice! I've had this problem with TrickDroid (and whatever kernel that came with), Viper 1.2.3 (and whatever kernel that came with), and same Viper with BeastMode v0.5 kernel. I haven't tried any other roms, but I don't think I can blame this on the rom...
I've tried a lot of things that I haven't posted yet, and I think I have it pretty much 100% narrowed down to overclocking...this problem never started until I started using JuiceDefender to overclock...then SetCPU...
Through process of elimination I've been able to rule out just about everything else...after a fullwipe, I can reflash the rom and let it settle...then reboot, and it does not loop...then flash new kernel, no bootloop...retweak some personalization stuff, still no loop...then restore all apps, still no loop...open SetCPU and set max speed to ANY speed...if I reboot it'll loop...if I just leave it alone, it'll stay stable for days...when it reboots, while watching Diagnosis I see system_server running at 65-95% CPU for about 90 seconds and the phone severely lags or freezes, then hot reboots...
Also, in the past, before I had this bootloop problem but after I started overclocking...I could still reboot my phone and everything would be fine, but the maxspeed was still set to oc, even though 'Set On Boot' was not checked and no profiles were used. This was true with all 3 kernels and both roms, and the app I used to overclock made no difference...SetCPU or JuiceDefender...even setting everything back to original settings before uninstalling both apps...oc settings always stick...
Last week, I read about someone thinking this issue was related to something about the relationship between mbuffer and time_in_state...one is 256 bytes, and the other 280 which recreates the problem...someone found a solution by changing the permissions of time_in_state back from 777 to 700...my phone rebooted and looped on Thursday, so that didn't work...
I've downloaded another rom to try, so when my phone goes on the fritz again in a couple days and I have to wipe anyways, I'll try a couple out and see if a different rom/kernels work...Thanks!
Sent from my Inspire 4G using xda-developer's app
Well, I got another random reboot then loop last Sunday, so I switched things up and flashed Pipeliner's cm10 on jellybean. So far, so good... I've overclocked with the rom's internal settings instead of setcpu, and I can reboot normally every time...
Thanks again for the help...
*edit* for... not get...
Sent from my Inspire 4G using xda-developer's app
Hey guys,
I am getting random reboots on my Nexus 5. It doesn't happen too often. Maybe twice a week or so. It may be happening more often when Im not looking at it, so maybe Im not noticing it sometimes. I haven't been able to pinpoint the cause. Im sure it's some app that is causing it (at least I hope it's not hardware related).
Has anyone else experienced this? Any suggestions on how to find the culprit? Thanks.
I am getting random reboots as well. I enabled generating a bug report with the power button in the developer options. Create a bug report the next time it reboots and share it to your Google Drive or Gmail so you can open the bug report.
Look for "Last boot reason" I was getting Kernel Panics with this error or very similar L1 / TLB Error detected on CPU 2!
[ 7370.931283] I-cache data parity error
[ 7370.931458] I-side CESYNR = 0x00201e01
[ 7370.931557] Kernel panic - not syncing: L1 recoverable error detected
Seems to be bad hardware. I am doing an RMA now ugh.
Hope that helps.
I agree that'd it's bad hardware. There have been some others who have had the same issue
Whenever I get a device. I don't ever restart it for a long time to see if its stable. Because ive had my original gnex random reboot every 24hrs and it was hardware related.
Sent from my Nexus 5 using XDA Premium 4 mobile app