Related
Still can't post in the dev. forum; been following closely. I was getting a ton of reboots on v17 & v19. I think it may have been because of (at least partially) SetCPU. I think I read that its worked into CM7, which would make sense why it's causing problems if installed on top of it. Although my wife has and Eris, running v19 and has only had 2 reboots (I had her on KF for a week, she decided she wanted the "newest", so I nand/flashed hooked her up). I'm running v. 22, and haven't had a reboot in a few weeks, and it only happens while I'm at work, not on wifi, not running pandora; and is likely caused by not locking the screen before shoving it in my pocket; OR from using my boss' BB charger, and unplugging it, then reboot :/
It is fast, and without Set cpu, I have better battery life; but I may have gotten a little crazy with the advanced settings on Set CPU.
I have set up CsipSimple with no problems (for "peak hours" - a test for when I lower my family plan min, so far so good). So I make free data calls with little lag.
I also took auto task killer off, which seems to have added some stability (could have been some widgets?!?).
I see a version as new as v26, and have been through v19, v20, and v21 before sticking with v22 (Though my compulsion to have the "newest" myself is hard to resist)
I ramble.... but if Pandora is the problem.... why use it??? I use T-torrent to down load all of my newly purchased music when I'm on the road, whole albums d/l faster than ripping and syncing, (of stuff that I already own.... I'm no pirate).
For a feature rich, 2.3.3 android (on an almost legacy phone!); I'd gladly give up the lag time between songs, and a limited ability to skip songs per hour. Tazz, my hat's off to you; I Still think it's the best Rom I've used, and don't plan on switching to anything but your newest (nope, not even going to try v25, even if you does have your name on it, it just doesn't feel right...)
Funny OT (again) my coworker bought a Nexus S , and (from his old g2/hero) and we ran some real time tests (him on 4g) that I smoked him at (v19)... granted all the bench mark tests said his phone was exponentially better; but in application- Tazz rocks.
Droid Eris is my first smart phone bought on ebay a month back , after experimenting with different roms for couple of of weeks, i settled on Ginger Tazz 22, now flashed to 27 ... Ginger Tazz rocks
i ran into a lot of issues initially flashing ginger tazz before i wiped my SD card. I wiped SD, wiped dalv, did a factory reset, and then flashed it. It seems to work fine after that.
OK, so I'm on GSB 3.4 (though this issue began with 3.3), and I'm having a problem with my phone rebooting (screen cuts off after about a second, and the phone immediately reboots to the skateboard screen) at the following times:
1. Whenever I attempt to wake the phone from sleep.
2. Whenever I hang up a phone call.
3. Whenever I get a phone call while the phone is asleep.
4. Whenever I plug the phone in to charge while the phone is asleep (be it a wall socket or PC) [see below].
These problems only occur when the phone is NOT plugged into a charging source; the problem appears to be nonexistent in this scenario. But as soon as I unplug, all 4 become auto-crash scenarios.
I tried going back to GSB 3.2, but no dice. I then resorted to the stock-ish XTRsense ROM, which fixed the issue, but going back to Froyo just was too big a downgrade for me.
Throughout this process, I full-wiped multiple times, hoping to track the issue to an app or setting, but even before restoring anything through TBU (I think I may have just let the phone go to sleep at the "Touch the Android" initial setup screen once), the problem persisted, eliminating apps, settings, or CM7 CPU modifications as possible culprits.
I've continued to play with CM7 CPU settings even up till now, but I'm not getting much of anywhere. I've now resorted to the "Caffeine" app, which just never lets the phone go to sleep, and I just turn the brightness down or activate the "Desk Clock" mode in the default Clock app to save battery.
HELP?
Have you tried Tazz's ROM or CondemnedSoul's ROM, just to see what happens with those? CS's ROM uses ADW as the default launcher (not sure about Tazz's) - perhaps it's something with LauncherPro?
Had this happen once
Sent from my Aosp Gin-Tazz using XDA App
My phones use to freeze on the unlock screen, it happened in multiple roms. i switched back to the "ondemand" governor and it hasn't happened since. not sure if it the same issue but it might help.
My last name is also Schultz ....
Sent from my Aosp-Gin-Tazz using XDA Premium App
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
scary alien said:
Guys, just thought I throw out the idea that it might an overclocking (i.e., hardware) issue?
I see that the Conap's CFS kernel that GSB 3.4 uses is max clocked at 604 MHz, but maybe that's too high for your particular phone?
I also think that schultzmd's comment about the ondemand governor helping might point to the clock stepping to a higher speed when coming out of sleep (and being related to clock speed). Maybe try running the phone at a lower speed just to see if its better behaved might prove instructive.
Just a thought...
Cheers!
Click to expand...
Click to collapse
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
I'll try the changing the max, but I know I've tried as low as 604 max (19 min) with the problem persisting, and as high as 710 or 768 before GSB 3.3 (when the problem started) with no major issues. And I had already been using Ondemand when the problem started, having stopped using Smartass when I thought it slowing the performance down a bit. Any other governors I should try?
And does the overclocking issue not apply when a phone is charging?
doogald said:
Sounds familiar: http://forum.xda-developers.com/showpost.php?p=14016867&postcount=5186
Click to expand...
Click to collapse
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
natemup said:
And does the overclocking issue not apply when a phone is charging?
Click to expand...
Click to collapse
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
scary alien said:
lol, doogald...I had no idea .
I should know better than to come in to any thread you've already weighed-in on and know that you've already exhausted all the possibilities.
I'll leave the Op to your very capable hands.
Cheers and thanks for keeping an eye out here on XDA and over at AF too (and probably six or seven other sites ).
Click to expand...
Click to collapse
You would have only seen that if you had seen the post in the GSB thread, of course.
I am still going to suggest trying Tazz or Condemned. From what the OP says, he should be able to see that it's having the same issue pretty quickly.
But, just to rule out the OC issue, you could try setting the max to stock 528 and see if it still happens.
doogald said:
You would have only seen that if you had seen the post in the GSB thread, of course.
Click to expand...
Click to collapse
lol...that post was on the 519th page of (currently) 530 pages! (I read the first page, does that count? )
Still crashing on 528 max / 19 min...
natemup said:
Still crashing on 528 max / 19 min...
Click to expand...
Click to collapse
How about on Tazz or Condemned? And, 19.2 is too slow for a minimum for this kernel. 245 should be the minimum.
scary alien said:
Well, you are introducing some extra heat into the equation while charging, which might be enough to tip the balance against you if it is indeed an overclock issue.
Click to expand...
Click to collapse
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
One more thing: if, right after the phone reboots itself, I unlock it before the screen goes off and manually put it to sleep and quickly wake it back up, the issue usually doesn't occur (and I can keep doing this, putting it to sleep and waking it back up again, with no issue). But if I unlock it and let it sit and reach the screen timeout itself (or never unlock it after it reboots, then let it sit for a while), the problem reoccurs.
natemup said:
I've full-wiped so many times in the last few days, I'm wary to just try a different Gingerbread ROM when GSB is (was, for me) so stable and full-featured. I'm trying my darnedest to just stick it out and charge-charge-charge to avoid the issue.
Click to expand...
Click to collapse
I have used both GSB and Condemned and you will not be missing anything. I stopped using GSB because I could not get market updates to stick reliably. I do not have that issue at all with Condemned.
Right now the only issue with the latest Condemned is apparently a GPS issue, so I would go with V6 or V7 rather than V8 for now until CondemnedSoul gets an update. Or, if you don't navigate, go ahead with V8. It's just fine.
You're obviously having a stability issue with GSB now, so you have nothing to lose but about 45 minutes of time and a Nandroid Restore to go back to GSB if you don't like it.
So, I had a minor issue that was fixed by switching to a different ROM. It's worth a try.
I wish you luck finding a solution.
natemup said:
I was inquiring as to why the issue DOESN'T happen when I'm charging. I'm not sure if that's what you were saying, but I have no issues while the phone is charging; it's weird, because CM7's CPU governor doesn't allow profiles for "screen-off", "charging", or anything like that. It just seems to make my problem more random and untraceable. It literally is happening on EVERY CPU setting, even 480 max (which to me, is just pointless to actually use)
Click to expand...
Click to collapse
Nate,
Sorry about that ...I was confused from where you asked in post #8 about whether or not overclocking was in effect while charging (it can/could be, depending on the overclocking monitor/govenor I suppose) and I had lost that point from your original post.
I would say take doogald's advice and switch to at least some other ROM since that would help indicate if it is indeed a software issue or a hardware issue. Its sounding like its not clock-speed related given the things you've already tried. If you've still got issues on other ROMs, that would tend to point to some hardware issue (our Erii are getting a little long in the tooth at this point, after all).
You could even flash back to stock and see if the phone is still stable there since you can always re-root and re-restore your Nandroid backups.
Good luck...I hope you figure something out.
Problem is alive and well on Condemned GB. *sigh*
XTRsense was fine and flawless, but going back to Froyo after months on gingerbread was just too depressing for me...
Sent from my ERIS using XDA App
I'm going to make one more suggestion - not sure if you have tried this yet, but try flashing GSB from a full wipe. When you go through the setup, DO NOT LOG IN TO YOUR GOOGLE ACCOUNT. After the launcher starts, go into the market, let it log you in to your Google account then, and then install all of your apps and change all of your settings from scratch.
When you log in with your Google account when installing a CM ROM, it tries to restore your apps and settings from your last CM ROM install. It may be that you have some weird setting or app that is causing this that you just keep reinstalling when you flash the ROM and log in with your account.
If you've already tried this, then try running xtrSENSE or xtrROM instead. They are both excellent ROMs and clearly your phone likes them better.
[edit] Oh, and try leaving your min at 245 MHz for a while. See if that helps your phone run better. It should, and it should have the exact same battery life as 19.2, as nonsensical as that sounds.
It is literally happening as soon as I boot the phone after a fresh GB install. I four-corner the Android setup screen, let the screen time out, and boom I'm screwed.
Whats up guys? First post here for a new guy. My Thunderbolt is rooted and I have been trying to find a good kernel that helped my battery life. Started with Das Bamf 1.6.3 remix but the Kernel that came with it was awful on battery life. Without using the phone at all the battery would die after 6 hours. I originally flashed this rom through Rom Manager. I then moved to Liquid Thundersense 1.5 and then flashed a kernel that was ok but not great. Did this through Rom Manager as well. Then I read thatit was best to flash through recovery in Clockwork mod. I did this and went back to Das Bamf. Same problems with the kernel that came with it. I then decided to try Imoseyons lean kernel. First tried the battery saver mode using the terminal emulator in the das bamf toolkit. That did not work at all. Then I tried option #1 for the normal mode. This kernel is INCREDIBLE! The battery barely moves at all and this seems to be the one I want to stay with. One problem.....every once in a while I turn the phone and and see that I used 10-15% of the battery while doing nothing. Every time this happens I see that my 3G icon at the top of my screen is showing data going in and out at all times and won't turn off. The only way to fix this problem is to reboot. Then the kernel is back to being amazing. Has anyone experienced these problems before? If so, is there a fix. With the way that I use the phone I should easily be able to go a full day and still have lots of battery left if I don't run into this problem. I would much rather not go with the fat extended battery. If this has been covered elsewhere I apologize. I tried reading through a bunch of threads but had no luck.
Nobody has anything???? I also noticed today that I had a random reboot. I was leaving a voicemail for my brother and I looked down to see that it was rebooting. The kernel is not extreme in the overclocking or the undervolting. I guess if no one has any ideas I will have to try some other kernels. Its a shame cause the battery life was incredible with this one.
I believe its a great kernel. Reboots could be caused by anything... Almost everyone is getting random Reboots with the tbolts. Your data issue is probably Rom related, I would personally reinstall after manually wipe on everything.
The vary life on this phone is not good, but my personal experience is that its my screen sucking down my batt! It's to much fun to play with.
Sent from my ADR6400L using XDA Premium App
The network could be the culprit, too. I have problems more often than I'd like in metro Atlanta. I've woken up twice since I've had the TB with the battery completely drained after 7 hours, so my alarm clock doesn't go off obviously. I've already dropped to 1X for a couple minutes this morning, so I'm sure the battery loves that.
That's probably Rom related as well. Something is sucking data when it shouldn't be.
My phone only uses around 1-2 % all night. But will drain quickly when I do some morning browsing.
Check your sync. It might be set wrong or you could have one of 1000 or issues.
Sent from my ADR6400L using XDA Premium App
Could be, but both times it happened actually before I rooted, which is interesting. I've only had this happen twice in over 2 months, so who knows.
At least I'm not getting random reboots.
ercDROID said:
Whats up guys? First post here for a new guy. My Thunderbolt is rooted and I have been trying to find a good kernel that helped my battery life. Started with Das Bamf 1.6.3 remix but the Kernel that came with it was awful on battery life. Without using the phone at all the battery would die after 6 hours. I originally flashed this rom through Rom Manager. I then moved to Liquid Thundersense 1.5 and then flashed a kernel that was ok but not great. Did this through Rom Manager as well. Then I read thatit was best to flash through recovery in Clockwork mod. I did this and went back to Das Bamf. Same problems with the kernel that came with it. I then decided to try Imoseyons lean kernel. First tried the battery saver mode using the terminal emulator in the das bamf toolkit. That did not work at all. Then I tried option #1 for the normal mode. This kernel is INCREDIBLE! The battery barely moves at all and this seems to be the one I want to stay with. One problem.....every once in a while I turn the phone and and see that I used 10-15% of the battery while doing nothing. Every time this happens I see that my 3G icon at the top of my screen is showing data going in and out at all times and won't turn off. The only way to fix this problem is to reboot. Then the kernel is back to being amazing. Has anyone experienced these problems before? If so, is there a fix. With the way that I use the phone I should easily be able to go a full day and still have lots of battery left if I don't run into this problem. I would much rather not go with the fat extended battery. If this has been covered elsewhere I apologize. I tried reading through a bunch of threads but had no luck.
Click to expand...
Click to collapse
If your worried about data using your battery when your not using the phone you should check out Juice Defender. Just set it up to turn off all data when your screen is off.
Heres your fix..
Ditch DBAMF 1.6.3 and go back to 1.6.1 with the lean kernel.. I get amazing battery life with 161 and 2.5.1 kernel.
I'll give that a try. I also didn't seem to have problems with Liquid Thundersense 1.5 so that may be another option.
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
The devs would say do a full format and flash and see if it still happens.
Sent from my LG-P500 using XDA App
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Try tuning down your overclock frequency... if you have overclocked it... it sometimes happens cuz of that... if you havent overclocked then theres some other problem...
Sent from my LG-P500 using xda premium
samrox144 said:
if you want to know what is happening install logcat from market and check for errors..
i used it to know why mms wont downlaoad and logcat showed that mms ip is wrong and changed it and it works
Click to expand...
Click to collapse
I've done that, but does logcat hold on to recent logs automatically, or do I have to turn on "save to sd card"?
I think I might be having this same issue. I left my phone on and plugged in to charge not even for a half hour or less then I came back to it later and pressed the power button to try to turn it back on but it wouldn't turn on. Then I pressed and held it a second and it wouldn't turn on. I unplugged the battery then plugged it back in then it powered up fine. I seem to be having this issue every once in awhile and I am not quite certain why it is doing this. Also it seems like it has an issue with charging on my computer. I plug it and it the computer is telling me that it can be connected to a higher speed port which makes no since as I have 2 usb 2.0 ports and 1 usb sata port. But basically I plug it in with a full charge and it has no problem keeping it charged but when it ends up going down to at least 50% the charge just keep deceasing and never charges. I just hope that I can make it stop this as it is getting quite annoying maybe it is just the battery or something but I can't see how as it isn't even 6 months old.
I've tried using Logcat but unless you set it to save the log every few seconds it doesn't help. If there's an error it doesn't get caught by Logcat because whatever it does, it turns off the whole phone.
What are you overclocked to?
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Oneiros42 said:
I'm not, unless CM7 comes already set to overclock. I don't play games on my phone so not much point overclocking for me.
Click to expand...
Click to collapse
Well then. I don't know. Have you tried reflashing the ROM?
Not yet. I was hoping Mik's CM7 6.6.1 would have been declared stable by now, but I guess I'll have to settle for 6.5.8.
Quick off-topic question: ADW Launcher always comes to a grinding halt immediately after a reboot, to the point it gives the force-close option window. Is that because there are widgets installed to the partition on the sdcard, thanks to app2sd? I checked under applications and it says they're installed to the phone, but I thought I heard that app2sd (I'm using Darktremor's, as suggested by Mik) effectively takes the option out of your hands, making it moot. If that's the case, how do I delete the partition, since I'll be doing a full wipe and reinstall when I flash the ROM again.
I don't play games 2
Dammit! Yesterday I did a complete wipe (return to factory, wipe dalvik), reformatted the sd card, and updated the ROM to 6.5.8 and it just shut down on its own again. I even saw it happen... while it was sleeping, I saw the buttons light up and blink once or twice, then it shut off. The screen stayed off.
I did a clean install and haven't touched the clock settings. I reinstalled my apps of course, but I don't have anything that runs constantly in the background that I'm aware of. I installed ADW Launcher EX, I don't know if that matters.
Does this mean it could have a physical fault somewhere? I'd really hate to have to go through the hassle of reloading the LG stock ROM and unrooting it (that's possible, right) to send it in for repair.
I had the same problem with gingerbread and the related roms.
But my problems were about the overclock frequencies. I used the italian rom GingerLoL 1.5.2 and I set the frequencies in this mode: 320-729 smartass v2. No more problems.
I don't know why I hadn't this problem with Froyo's rom...
I'm tempted to fiddle with the clock settings now that I know just reflashing the rom doesn't help. It seems by default CM7 is set to 245-600mhz, with the "smartass" governor. I figure I might as well bump the low end to 320, but where's the "v2" version of smartass you mention? It's not in the list.
I have exactly the same issue! Tried 3 different firmwares, 3 different roms and different kernels too, but it seems to reboot by itself and also really slow sometimes to scroll. Can't solve this... maybe some hardware troubles? some new defected cpu ? I sent this phone 1 month ago in warranty and they changed me the logic board, then when i got it back, it started to have this trouble. Before this, never had this trouble.
Oneiros42 said:
Hi all, I'm running Cyanogenmod 6.5.7 and in the last couple weeks I've picked up my phone only to find it was off, not sleeping. It still has plenty of charge left (I can't remember when my phone last went below 50%), and it boots back up without a problem. You wouldn't know there was anything wrong except for the fact that it sometimes turns off on its own.
My first problem is that I don't know where to look to see what could be the trouble. It's running ADWLauncher EX. Beyond that and the OS I don't know what could be relevant. I switched to CM7 last month, up to then I'd been running GingerLOL and I never had this issue.
Any help or advice is appreciated.
Click to expand...
Click to collapse
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
FPChaim said:
Make a full wipe and don't let your phone with low internal memory, it worked for me and i was having the same issue
Click to expand...
Click to collapse
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Oneiros42 said:
I have done a full wipe, but I don't understand your other suggestion. I'm using Darktremor's Apps2SD, so I'm pretty sure I'm not running low on ACTUAL internal memory.
As per my last comment, I bumped the low end of the governor to 320mhz and there was no trouble until two days ago when it turned off on its own again, making it the longest it went without the spontaneous shutdown. However, it then broke its record for SHORTEST time because it shutdown again five hours later.
Can anyone thing of anything else, or should I start looking for my warranty info?
Click to expand...
Click to collapse
I'm my case the phone boots and when it load all the aplications it reboots... but one time i quickly go to setting>applications>manage applications and there has less than 1 mb... so i think it was building something like caches... I wiped everything and my phone worked as usually... but i installed a lot of things again and it keeps rebooting and rebooting... i wiped everything again and installed just few things, leaving my phone to have high internal memory... it worked!(actually i have 42 mbs of free space and it never happened again)
Lately I have been observing lags/freeze-ups after just 1 day of use on my stock 351 streak!
(yeah- I do have tonnes of apps - but still!)
I mean I am observing the screen tilt ( after physical rotation ) is also sloww!
Only link I could find, that was- my restart interval was like 3 days or so.
I am restarting it once in 2 days now ( manually).
But, still - the lags/freeze-ups are getting more frequent!
I have case for the Streak- so its very annoying to open it all the time to pull out battery!
So- I have factory reset it now.
Will now check the performance. But- I am sure getting a feeling its getting slower
thought of checking here- whats the restart interval?
and
Are freeze-ups common? -- ( no much crashes though) just- freeze-ups.
Thanks,
Sony.
I never ran a stock rom long enough to find out. If you want to stick with Froyo, since it sounds like you want stability, go with either my Streakin' 354, or Simple Streak. I wents days, maybe even a week, without a restart and when I did it was because of theming or something that required me going into streakmod.
If you want to stick with stock, then you may just have to resign yourself to manually restarting once a day. I used to have a profile set up in Tasker to do just that, before I found a stable rom that I liked.
Odd. Other than a brief switch to StreakDroid 2.4.4, I've run stock ROMs and have had only one occasion where it was necessary to forcibly shut down and reboot the Streak.
For the most part I only reboot mine every once in a blue moon. Like Morph, I have to reboot for a new theme or boot animation. But I run my streak with minimal apps loaded besides stock ones from Rom. (Total including stock apps 102) Mine doesn't lag after a few days.
Each phone and User is different. Sounds like a cliche' but ask 100 Streakers, and you might get 100 different answers.
Once a week
I'm stock, rooted, 2.2.2
I reboot once a week, regardless of if it isn't causing a problem.
Sunday before bed, I just pop the back cover, take out the battery
and reboot it.
I haven't had any lock up's or anything, but I'm not into playing streaming
music/videos/games.
I use it mainly as a phone & for work. 20-25 emails per day, 5-10 text messages,
viewing PDF's, web pages etc.
I'm currently running StreakDroid 2.4.4 and have gotten up to 60+ hours of uptime. Even then I only needed to reboot cause I was tweakin' the thing.
I've found my stability MUCH better after installing SetCPU (245min, 998maz, ondemand) and autokiller (all advanced tweaks enabled with aggressive profile activated at bootup)
but like people have said, you have to play with settings, cpu governors... to get your Streak stable. They're all different. I'm currently on my fourth. The one I'm on now is rock solid but the one before was a MESS. It could NOT handle overclocking and constantly had wifi/sleep of death problems.
Just like a baby... keep trying things til something works!
Up until the latest Gingerbread ROMs I've always found stock to be the most stable and had it running for upwards of 2 weeks without reboot. I've since found the new GB ROMs to be super stable but with tweaking and running out of battery i've had no longer than a week of late. I've got abut 200 apps installed
I reboot mine all the time. Not necessarily because of any problem, just to freshen it up I guess. I have a widget on my home screen, and if I'm doing something CPU intensive, when I'm done I'll just hit the button and stick it back in my pocket. When I pull it out- fresh Streak!
Why not...
Sent from my Dell Streak using Tapatalk
I flashed 2.3 straight away and I have never had a lockup....
I didn't have a freeze with 2.4.4 either. The camera didn't work properly however (white screen) which is why I went back to stock. I haven't tried the other ROMs yet so....
Thanks!
Thanks to all for super-prompt replies!
And, I have just done a factory reset.
and, yeah- this was the only phone with me-- so I did not go for root/flash yet.
But- I have a spare fone now ( HTC P3400! my trusty old friend!--ROMs flashed like flash on a camera!)
I have read quite some information on flashing streaky dear-- just some catching up to do.
and, lordmorphous -- I am a fan already Simple Streak looks awesome
Strephon - yeah- I find it odd too! but now- lets see what happens-- I will test this |clean| stock rom for weeks time -and then jump to Simple streak.
Gregionis- I had similar number of apps on stock-- will check now.
All - thanks for the help!
Keep Streakin'
Sony.
Hi
I usea programme called fast reboot.Its great to clean ram up from various appliications.
Sent from my Dell Streak using XDA App
Fast Reboot is an excellent tool. I had it when I was using AdFree to implement the host file changes. After switching to AdAway, which has a full reboot routine included in the app, I still use Fast Reboot.
Weeks at a time
Hi!
I run simplestreak 1.3, before i used simplestreak 1.2. Cant remember any problems really. Now looking into 2.3 roms, mainly because its.. too stable and no thrills at all.
Maybe because i am alamoust religious when it comes to flashing. Going all trhe way all resets and wipes and all of it. Alaways.
Just a GRAND thanks to all!
Thanks to all - BIG time.
I took this problem forward- and got my Streak replaced!
and, now- this is really a fast one!!
I dont remember My streak being this fast in past 8 months!!
-- I guess, it is right! " No two streaks are the same!"
Now- I will check the uptime- but I already see the speed!
--
So, this is my 3rd streak in last 11 months!
But, I love this phone!!
CAnt wait to get on the flashing wagon now!!
In a weeks time
Thanks to all!!
Sony.
Gingerstreak 2.4.4 installed for around a month now I think. Not a single forced reboot and it hasn't frozen either.
I have rebooted manually a couple of times whilst sorting the battery meter out but this is the most stable the thing has been since I got it in July last year! I've previously had stock 1.6, 2.1, 2.2, Streakdroid 1.5.3, 1.8.1 and 1.9.1 and couldn't get it stable on any of them. Finally after nearly 18 months it works as it should!
It lives next to the bed overnight on standby and has woken up and sounded my alarms every day without fail since going to 2.4.4
The only thing I seem to be able to point to that i've done differently is SetCPU running 576/1113 lagfree. If I go higher it doesn't like it on previous builds (including 2.4.3) so i've not tried it on this one. Going lower seemed to cause issues for me too so maybe the various stability problems people experience are CPU / governor related? We know that they all have varying max clock speeds so I wonder if they have varying minimums too?