I'm a total n00b to the rooting scene - going on almost a week with my rooted DInc - so apologies if this has been addressed (I can't find where its really been addressed definitively). Since I rooted (and only since), I'm occasionally having random reboots while my phone is sitting inactive on my desk. I've only used Sense ROMs (Virtuous, WarmZ, Nil's Business), and they all seem to have it. I have Nil's on now (love it so far!), and for two days, I thought the issue had gone away, but today it has rebooted twice in short order (about 30 minutes apart).
Some things I've observed about this:
- I haven't had it reboot yet while I was using my phone - only while sitting inactive on my desk at work.
- I do have pretty poor signal strength in my office - at rest, it usually shows just a bar, if that.
- The wifi connection I have available is also wonky (router issue, I think); I don't use it (or even have it remembered) because it will connect, but continuously drops and reconnects over and over (not a phone specific issue, used to happen to my BB Curve as well).
This doesn't rise anywhere close to a dealbreaker for me, as it reboots quickly and everything seems to return to normal, but I wanted to ask if anyone had a suggestion to remedy the problem.
Could be a lot of different things. Are you also using custom kernels? Some people will get random reboots when they overclock their processor, but since you say it happens when the device is idle, that sounds unlikely. There was a generation of GB kernels that would cause random reboots if the wi-fi policy allowed the wi-fi to sleep. Switching the wi-fi sleep policy to "never" was the workaround for these, but you are using Froyo and I'm not sure if this same bug ever affected any Froyo kernels.
I know when I ran lou's kernel (don't remember which version) I had a few massive lag moments where the phone was insanely slow and also a couple of random reboots (once was idle and screen off, other was during a phone call).
I didn't continue to run it for those reasons, actually only ran it for 2 days.
You may have better luck just flashing a different kernel with the same ROM you're on, I've had good luck with chad's sense incredikernel (25plusv) - that is, if you're looking for a suggestion for a kernel to flash
Run fix permissions in ROM Manager too.
Sent from my ADR6300 using XDA Premium App
Related
Hello all. Kinda new here, but I've been flashing my hero with roms from here for a while now. My latest attempt at a good rom is the VillainROM 12.0.0, this is my first time with a VillainROM, and I don't know if this bug exists in previous versions. In my opinion it is a very minor issue, but maybe not for someone else. I'm not a developer, so I don't know what could be causing it, and I don't know if I should be reporting bugs on the VillainROM site, or here, so I'm going to start here...
I downloaded the ROM from the VillainROM12.0.0 thread...
Install was flawless, worked perfectly.
The ROM runs extremely well in all functions, so no complaints there.
The only issue is a slight (10+ seconds) hang when I press the power button to turn on the screen to unlock it and the WiFi connection has timed out. Other ROMs I've used, including the stock ROM would come out of this sleep mode, and then try to reconnect to the WiFi, and they've done so with flawless success. However, this ROM does not, at least not for a minute or so.
This is how I can reproduce the problem, and it takes a while. I usually plug my phone into a charger at night and let it charge over night, and unplug it in the morning to head off to work or whatever. Once the screen turns on on its own after the external power source is disconnected (which all ROMs have done) the screen is unresponsive, and all buttons are unresponsive. The screen remains lit up on the lock screen stuck for at least 10 seconds, then goes black, then pressing the power button to turn the screen back on will restore the phone to an unlocked state (assuming it remembered the swipe action from when the screen was locked and stuck) but takes about another 5 seconds to come back on. This only happens if I have the WiFi radio on while the phone is sitting idle for an extended period of time (long enough for the radio to automatically go into its sleep mode perhaps?).
Here's the info from my phone...
Firmware Version: VillainROM9.0.0
Baseband Version: 63.18.55.06JU_6.35.09.26
Kernel Version: 2.6.29-ninpo-freqtwk{AT}titan-dirty-b7a296faninpo{AT}titan #39
Build Number: VillainROM12.0.0
Software Number: 3.32.405.1
Browser Version: 3.1
I'm not sure if this is just a fluke, if I should reflash and see if the problem persists. Anyone else able to reproduce this?
Again, if this is the wrong forum, please feel free to move it, and thanks XDA, this site is an awesome resource!
PS... I had to replace the at sign with {AT} in the Kernel Version due to Forum restrictions (It thinks it's an outside URL and I'm too green to be able to do that...)...
Are you running setCPU or OC Widget?
It look likes the lower CPU frequency is too low. Open SetCPU or Overclock Widget and increase it a little.
If you use profiles, in SetCPU:
> Check if you have a "Sleep Profile"
> Check if its frequences are too low.
> If yes, increase it.
It normaly happens when you have a 19Mhz - 2XXMhz on-demand sleep profile.
Increasing that 2XXMhz to 3XX or 4XX may solve the issue.
If not, try to reflash, or use VillainROM IRC at their website.
First your radio is a bit old. Try upgrading to the latest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
Second, especially regarding the wakeup issues, try my kernel for VR12 from here:
http://villainrom.co.uk/viewtopic.php?f=97&t=1928
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Turn up your minimum set cpu speed.
erasmux said:
It has no wake-up problems even @ 691/160 (what I used) as well as better battery life and performance....
Click to expand...
Click to collapse
Pulser has no problems waking up at 19MHz with my kernel. Stable Min/Max frequencies are unique to each phone it has nothing to do with the kernel.
In theory I agree with you completely. But in practice with each kernel I get a different wakeup "performance" using the exact same frequencies. I always prefer setting the min to 160Mhz, but like many many others, in most kernels - including your kernel which comes with VR12 I get heavy wakeup issues which disappear only @ min 480. In other kernels (such as those by Radu) these wakeup issues still exist but are less pronounced (very very rare).
For me and others which have given my kernel a shot there have been no wake up issues @ min 160Mhz. Battery life and responsiveness also improved according to those who have tried my kernel (and optimizations).
BTW "my" kernel is just the HTC official kernel release + OC enable, so its more HTC's kernel than mine.
Like you said it is device dependent, ROM dependent, user dependent, everything.... I am just saying that until now I have not gotten any negative feedback on my kernel, and I think people should give it a shot and decide for themselves. Hopefully they will also be kind enough to share their experiences with me, so if there are problems I can try to fix them.
Thank you all for the suggestions. I do not use any OC utilities, it's the ROM as it was when I downloaded it. Barely any applications installed (some games, auto task killer, handcent...).
I've updated the radio to a version I found in a SenseHero 2.1 thread, but that radio broke MMS and some other data network features. I am in the US, on AT&T (I know, no 3G, but I'm ok with that ), will the radios listed work propperly on this network?
I was also able to reproduce the hanging issue by turning on the WiFi, browsing around the Market, and then exiting the market and turing off the WiFi. It seems that during the switch to the mobile network from WiFi is when something funky happens. Is there a way to get logs to show what might be going on?
First of all try the newest radio from here:
http://villainrom.co.uk/viewtopic.php?f=24&t=323
If 6.35.15.14 does not work well for you, try either 6.35.15.11 or 6.35.15.01 - If I am not mistaken they are all from the latest HTC release from different parts of the world, so one of them should work well for you.
If you want to get a log for the problem, use the adb logcat. Another simpler option to try and isolate the problem is check if reflashing the ROM (after a backup and a full wipe) solves the problem. Also check if the problem exists in other ROMs.
I have flashed the radio with the latest from the site as suggested (6.35.15.01 was no good when I flashed with that one before, caused all kinds of problems with MMS/SMS, and other network fuctions, but I didn't try that radio with the VillainROM). MMS and such still work, so that is good. I'm going to try to reproduce the other issue tonight, but that may have fixed the issue... I'll update the thread with the results.
Looks like the new radio did not solve the problem. Is the next step the new Kernel?
Sorry for the long delay in response...
The problem is still happening. I have now flashed with a different ROM (Chronos Droid 2.1.2) and the problem persists. However, the lockup doesn't seem to be as bad... Am I the only one with this problem? Should I change my wireless network settings to GSM only? Or leave it on Auto? I'll play around with that and see what happens. It just seems that changing from the mobile network to the WiFi network (and vise versa) is when the problem happens...
Nope, that didn't help. When I went to GSM only, I had no data network connection, and when I went to WCDMA only I had no connection at all. On GSM/WCDMA Only I have both... I wonder if it is something with this phone and the .29 kernel? But then wouldn't everyone here have this problem?
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
I don't see this being a kernel issue, I have a feeling its just a wifi issue on the new rom bases.
m4rk84 said:
I have this issue too, using ninpo's kernel. I am going to increase my min freq but it's already at 3xx - fingers x'd
Click to expand...
Click to collapse
Please let me know what happens.
I did not have these problems using the SenseHero ROMs (older Kernel), only Villain and now Chronos... :S I don't use any OC apps, just leave it all stock from the ROM. If I use one and increase the speed at sleep, (probably an obvious answer) will this drain the battery faster?
Still hanging. Does this have anything to do with wifi's android default sleep behaviour?
I'm having all kinds of lag issues when network queries are starting, especially during MMS/SMS operations. Could be a Handcent update, but the default messager thinger is also quite slow. I'm tempted to go back to an older ROM, this is getting frustrating...
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Sorry, read too quickly your post.
usually is a radio problem that hang the kernel. try with different radio firmware.
I seem to get one of those about 1 or 2 hours after every kernel flash (that may just be a cooincidence though), and maybe once or twice a week as well.
I haven't been able to identify any app or other thing that might have caused it, as they usually happen when I haven't been using the phone for a while.
Info:
Kaiser 130, 23-11-10 l1q1d kernel, Fat Free Froyo RLS5
I thought it might be something to do with the screen turning on (ie wrong panel type), as when it "freezes", the keyboard lights still go on and off when you open the keyboard. I've never been sure if my Kaiser is panel 2 or 3, but it's happened to me on both panel 2 and panel 3 nbhs, so maybe it's unrelated.
That is a known issue with the .25 kernel did it give you backwards text too? What's weird is its only froyo that has that issue these freezes are also why dzo started porting the new one
Sent from my HERO200 using XDA App
I've never seen the backward text. I'll look at rebuilding with the .32 kernel. Interestingly, it doesn't seem to happen when plugged in (so far). It's only happened once today so I may let it roll for a few days and see what it's like.
I observed it too
Adomatic said:
I've tried several builds and am quite happy with each (getting better and better as I learn more and more). I've gotten newer and newer kernels and builds and am currently using Thoughlesskyle's not so super froyo and am really liking it.
The one deal-breaker issue that's keeping me from using this phone full time is something I'm calling a phone coma. The phone periodically refuses to wake up from sleep. I may have a flashing notification light that makes it look like the phone is sleeping but I am not receiving emails or phone calls when it's in this state. To wake it up, I have to press the reset button.
I think this may be related to battery (http://forum.xda-developers.com/showpost.php?p=9360324&postcount=7) and I'm going to try to debug this a bit but I was wondering if anyone else is seeing this. I don't think it's specifically related to any one build as I've seen this with DZO and Thoughlesskyle.
Just for completeness, I'm running a Kaiser with a 1 year old 1600mAh battery, a 2.6.25 kernel and, currently, both Sys and Data are on NAND.
Anyone experiencing anything like this?
Click to expand...
Click to collapse
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
have some patience guys, kernel .25 has this issues, and devs are working hard on kernel .32 to solve this problems, this is a linux kernel and has to mount the file system to read it and then unmount it on shutdown, but recently there have been some issues with the unmounting part on the shutdown (like when u just unplug the power cord on a PC and windows restart with the "blue screen") until devs find a solution, its wise to always keep on hand a recent /data backup. Another word of advice: read! i dont want to sound rude, but all this is commented extensively over the forum.... like l1qu1d would wisely suggest: use the search tool!
doghead said:
I have an almost identical setup: a HTC Kaiser with kernel 2.6.25 & thoughtlesskyle's fat free build RLS5, and I observed similar random freezes and reboots. Last night the phone was in standby mode before I went to bed, and in the morning I saw the boot splash screen. It missed the wake-up alarm! The battery was at about 50% level and the phone was not being charged overnight, if it matters. But I did experience random lock-up in the midst of dialing or playing a game when the battery was well-charged.
As much as I like the responsiveness of Android and rich apps, if the device/software is not stable, I may have no choice but go back to WM.
Click to expand...
Click to collapse
the old kernel only does this with froyo if you still want to use android use n eclair build or donut its not the latest and greatest but they are very stable though
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Adomatic said:
Thanks, I may give it a shot (or I may just buy a samsung captivate ). Your build is very good. Doesn't seem to be as quick as some of the others I've tried but yours has been really stable. I've been running it for about a week. The others
This problem doesn't seem to happen when plugged in - it's only when on battery. I've had some app freeze-ups but, in general, the phone has been really nice.
Click to expand...
Click to collapse
yea not so super is a little bloated if you dont mind a little work fat free is very snappy i just has a blue theme
So I hve been going nuts trying to figure out why my phone keeps rebooting. I'm in another country so getting a replacement isn't an option for me and it seems it hasn't helped some people anyways (After a while it comes back).
THe only constant I see is that the CPU usage after maybe 30 seconds after the phone comes on stays at 95-100% all the time. Only thing that makes sense is that the phone is shutting itself down before it melts down.
This kinda makes sense since it seems the more I try to do the more random the reboots become.....and battery life is beyond horrible. I did the steps to increase battery life and battery life is making this phone virtually unusable off AC power (EXample: Leaving from my Brother in laws apartment and travelling 10 floors down to my car results in 89% battery left. Phone is dead within the hour if i use it and 3 or 4 if leave it idling.
I tried killing all the tasks that te phone starts up with but nothing change the CPU usage. I thought maybe it was the kernel but I flashed the latest one from this thread: http://forum.xda-developers.com/show...RI+version+PRL [the undervolted version]. Not sure if that would help (THe info in this forums is so scattered and disorganized it makes my head spin.....and I'm a techie).
Also try flashing the combo package of the latest radio, PRI, NV etc and that doesn't work also....CPU usage is still through the roof.
I just got this a few days ago. I'm currently on:
HBoot 2.10 [s-off]
H/W 0004
Basband 2.15.00.11.19 [I was on this before I was rooted]
Kernel version 2.6.32.27-SBC-net-4.2.2-less-havs [email protected] #19 [Just flashed] ROM myn's Warm TwoPointTwo 9RLS 4)
Software: 3.3-.651.3
PRI Version: 1.90_0003
PRL Version: 60662
Can I get some help from people smarter then me. I'm at the end of my rope and I'm not convinced a handset swap is going to fix my issue esp. since this was BNIB straight from Sprint and other people who've had this issue and had a new phone seem to somehow have it later.
If i leave it alone it will reboot on its own eventually. If i switch from airport to turning on the cell data, reboot, turning on wifi......reboot, toggling 4g.......reboot, After a few web page searches......reboot, open up an application.....reboot.
This isn't temperature related as far as I can tell.....The app I have monitoring temp has seen this happen at 25 degrees and sometimes less.
PLEASE HELP
Ok.. firs tthings first..
when your phone is unstable and rebooting, dont use an undervolt kernel. Undervolt kernels provide less power to the CPU at set frequencies.
In my case, I discovered undervolting CAUSED reboots, because my phone couldnt handle anything under 950mv... there is such a range in the quality of the components that theres no way to always say yes, undervolting this much will work with every phone.
so 1: Use stock kernel ( for whatever rom your using.. also use a well established rom, not one of the 'hey, last night i got bored and made this' ones.. it may work, but it may be so buggy its what is causing your crash )
2: do a fresh install. run the phone with 0 apps added, see if it has the same issue. If it does, may be the phone itself. If it doesnt, its one of your apps.. install one at a time, and see if it improves.
and you made two posts why?
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.
Didn't know they would move it. Posted in the wrong forum and they moved it as well. lOL. My bad.
I've been on a stock kernel up until I started trying different kernels. I will try the other one then.
My CPU usage is the problem I think. I have both memoryusage and system monitor and both report the same thing.....95-100% usage constantly. If I could resolve that then maybe my phone would work properly.
i have searched but havent found what i feel that i am looking for. i got a replacement DInc about a month with no issues till about 10-12 days ago. I have started getting constant reboots running the nightly cm7 ROMS. decided to go back to try RC1 but getting them on it as well. i am even getting this running a bare ROM (ROM & GAPPS only installed) yet still get reboots but less often i will admit. the more of my settings/apps that are added back....the more reboots i get. occasionally i will get stretches that are great reliability but rarely. anyone else getting this? i am sincerely beginning to feel that i may have gotten a bad replacement device.
thanks in advance all.
make sure your cpu is set to 998 or if you wish to overclock it then make sure the wifi is set to never sleep.
setcpu is usually never higher than 1036 (occasionally 1075) cause havent had much need to OC the DInc. to be curious what does overclock and wifi sleep have to do with each other. these issue exist even with WiFi off, running on mobile network.
so I flashed the Nexus Rom as well as the newly updated 3.8 version with the battery % feature flashed on my phone. The entire procedure was done as instructed (restore/clear 3+ times on everything as instructed) and I waited well over 10 minutes upon a reboot. So all is set and almost everything is working flawlessly.
There are few issues, however, which I'm curious to know if I'm the only one experiencing this:
1. Battery Drain: Fully Charged at 100%, unplugged the cable at 6AM this morning. The phone has been on its battery power for roughly 7.5 hours now handling a total of 5 minutes of calls, roughly 30 text messages, 5 minutes of non-wifi internet usage, email is being pushed, and flashed 3.8. My display is set slightly below the mid section and I have zero widgets on my main screen except for the search bar. A total of 6 icons on my menu and that's it (only 1 page). My battery is at 40% right now. It's only been a day since I've had this flash and I just flashed on the 3.8 just few minutes ago.
2. From the Status Bar pull down menu, Shutdown and Reboot, Recovery option would hang and freeze the phone until I pull out the battery. I can only enter the Recovery mode manually by holding both +/- volume, power on, and releasing both once the 'samsung' logo appears.
3. Mobile HotSpot freezes for good 1-2 minutes. I cannot use my phone as a Hotspot at the moment.
I absolutely love the Nexus Rom from the looks, performance, looks to looks, but few of the glitches I've mentioned are quite irritating. If I'm the only person experiencing this, I'd want to continue on the search to remedy this issue. Please share some experience, ideas, or resolution if you have any!
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
icenight89 said:
1.) That's about right for battery. It's a leak so the battery life is still wanting compared to gb. If you thinks that's bad though, you should have seen uclc4
2.) Known bug. Even though its ucld2 the shutdown bug is still present for a few, and especially manifests itself as soon as you run fix permissions. Although the shutdown hang is "reportedly fixed" on ucld2 i'm running seanscreamz sky ics 4.2D-8 with ucld2 base and i have the same problem as well.
Suggestions, either use quickboot from google play, or reflash following op instructions and DO NOT fix permissions
3.) Hotspot doesn't really work all that well, even with the ultracfg fix. I recommend the "WiFi Tether 3.1-beta12" app, i'm using this instead and it works well.
Click to expand...
Click to collapse
Thanks for the input. I wish the battery life was better. I'll let it sink in for a few days to see if it'll improve. If not, I'll just have to keep searching for a rom with a better battery life. I've tried Beastmod, Juggnaut and many others which have yet to last for over 12 hours.
I read that the hotspot issue was fixed and with the 3.8 update, I presumed it to be completely polished. The shutdown bug, I can live with - hoping there's an upcoming fix in the works.
This ROM is the sickest looking ROM I've tried so far. I wouldn't call it the smoothest due to it's intermittent force closures and freezes, but when things improve down the road, I think this one will stay on my phone for awhile!
I've been using this rom for about a week and the battery has been working great, better than any stock rom I've had. I'll unplug it in the morning around 745 and it'll last until I go to bed around 11.
Sent from my SAMSUNG-SGH-T989 using xda premium
You should try Mr X' s tweaked Telus stock ROM. This ROM has the best battery life among T989 ROMs period. It is Canadian but works great on T-mobile network. It also does not have much bloatwares as T mobiles stock one. Just Make sure you have wifi sharing, wifi sharing manager and social hub frozen through titanium backup.
As for wireless hotspot, the stock one from Telus works well.
I get about 16 hours use. It may vary for you but battery lasts longest with this ROM.
Sent from my SGH-T989D using XDA