Related
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?
Everytime i boot my photon it stays on the word "now" for 30 seconds? Is this ok?
Sent from my MB855 using xda premium
Sadly I believe it is normal. My photon (which is rooted) takes 45s-1min to boot up which is quite pathetic I believe. I can't even show off my phone because most people start making fun of my phone when they see the word now for 30 seconds :/
cm 7.2 boots up for me pretty quickly defenitaly faster then the other roms i have played with
I guess i have to ask... 1) why would you turn your phone off before showing it to someone?
2) how often do you reboot where boot time is an issue? i reboot once a month tops. (unless i find myself having to switch batteries, which is also rare)
now i am just guessing here but i bet he wants to show off a custom boot animatiion.
Change your initial boot image, that way they aren't staring at the word now. its a cheap solution, but I did it and it beats the default.
On a side note, I don't like how long it sits on that screen, either.
Sent from my 1.3 OC'd CM7.2 Electrify.
I found out why it takes so long to boot... this is because it loads security platforms, features, applications, firewalls, etc. + it's just slow in plain english.
Sent from my Epic Touch running Blazer Rom via xda premium
Blur has a lot of services that start on boot. Significantly more than android source and as such takes a little longer to boot. As someone else said CM boots fast and that's due the less work to do on boot. I made myself a blur rom that was stripped of services and apps I don't use then deodexed, zipaligned for better ram usage, PNG optimized the system and framework to reduce the overhead and the end result was my phone wouldn't make it through the stock boot animation before it started painting the screen.
My goal was to just see how certain blur services played with others but it didn't take long for me to notice I had inadvertently increased boot time significantly over stock.
Cm7 and cm9 are rockets, fly and boot quickly!
Sent from my MB855 using xda premium
I'm stock S-on rooted and have frozen some bloat. However the phone takes about 4 min. To boot up. What can I do to speed up the boot?
Select fastboot and that should help, it's under settings > power options I believe.
zetsumeikuro said:
Select fastboot and that should help, it's under settings > power options I believe.
Click to expand...
Click to collapse
I've already got that set. Any thing else I can try?
Stop clearing the cache on boot?
Sent from my ADR6425LVW using Tapatalk 2
It is odd that the phone boots so slow. My old original droid booted faster.
My phone boots extremely fast even with fastboot off. It is usable in about 25 seconds from pushing power.
yeah idk why yours is so slow, because mines relatively quick as well... and i never use fast boot.
Sent from my HTC Rezound using Tapatalk 2
superchilpil said:
Stop clearing the cache on boot?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Where's the setting for that? I'm pretty sure that I don't have that set.
jayochs said:
yeah idk why yours is so slow, because mines relatively quick as well... and i never use fast boot.
Sent from my HTC Rezound using Tapatalk 2
Click to expand...
Click to collapse
Takes mine a solid 1.5-2 minutes to boot(without fastboot checked). Do you guys have any frozen bloat? Wondering if something there could be causing it. Stock OS or ICS?
Mine boots in less than 30 seconds.
esheesle said:
Takes mine a solid 1.5-2 minutes to boot(without fastboot checked). Do you guys have any frozen bloat? Wondering if something there could be causing it. Stock OS or ICS?
Click to expand...
Click to collapse
crazy man..then again, you said you're stock right? i'm running a custom rom. but still, even stock i remember being like, wow this boots quick. and yeah, i froze ALL bloat lol
jayochs said:
crazy man..then again, you said you're stock right? i'm running a custom rom. but still, even stock i remember being like, wow this boots quick. and yeah, i froze ALL bloat lol
Click to expand...
Click to collapse
And fastboot was unchecked? Mine boots that fast with fastboot, but not when unchecked.
I remember stock with many apps booting fast. But with like forty taking forever.
ReZound
I'm stock, S-On and rooted. I have frozen some bloat apps, but nothing that should affect boot.
During the boot process it stays at the 4G LTE scteen for the majority of the time.
Once it passrs that it is quick. Whay would cause it to hang at that point?
same here
I call BS on anyone that says their rezound boots in 30 seconds from a power off with fastboot unchecked. Post a video showing it after pulling the battery.
Even all the customs I've run boot slow, and even once the screen is on, it still has to connect to the radio, mount the sd, etc. ICS boots faster than GB.
My HD7 booted in 25 seconds, which was kind of a waste because I only had to reboot it once in 9 months.
Mine takes for freaking ever. Makes my ancient Palm Pre look like a speed demon. Rebooting is a walk away and get a snack affair.
Mine takes about 4-5 minutes to boot the first time after clearing the dalvik cache and cache partition, but every subsequent boot takes like 30 seconds or so and I have fast boot disabled.
My girlfriends myTouch Q takes about 10 minutes to boot though, so don't be too worried about a couple minutes.
One thing that I do know is that the more apps you have on your device, the longer it will take to start up. It apparently does some sort of "optimization" on all the apps at each boot, making it take extremely long if you have a bunch of stuff on there.
There is definitely a difference between restarting and powering on/off. I have fast boot on and if I restart the phone it takes a few minutes, but if i power off then back on it is quicker.
Sent from my ADR6425LVW using xda app-developers app
nrfitchett4 said:
I call BS on anyone that says their rezound boots in 30 seconds from a power off with fastboot unchecked. Post a video showing it after pulling the battery.
Even all the customs I've run boot slow, and even once the screen is on, it still has to connect to the radio, mount the sd, etc. ICS boots faster than GB.
My HD7 booted in 25 seconds, which was kind of a waste because I only had to reboot it once in 9 months.
Click to expand...
Click to collapse
I read your comment and decided to try. I am running Newt's one xxx with fastboot enabled. I timed from the time I pushed the power button to when the x disappeared from the signal bars, which meant radio was connected: exactly 1mn 5 sec. Not as fast as the 25-30 sec that some claim, but a lot faster than the 4 minutes the OP is experiencing. Sorry, I don't have regular standalone camera to make a video. My rezound's camera is good enough for me
I have a nook tablet 16gb 1.4.0 (OTA fixed) rooted for a while now.
It is mainly used by my 7 years old son, so it has hundreds of apps, games and the like.
My question is to know if anybody is having booting time (since you power on the nook tablet till it gaves you the home screen) about 5 minutes.
I've tried a couple of programs that claim to speed up booting times and/or android performance, but did not get andy results.... the boot time is still the same.
Could you recommend me anything else?
By the way, i have a bootable SD card with CM7, and it boots really fast (less than a miunute, about 40 seconds) with also a lot of apps, games and the like.
The boot time on stock ROM always took a really long time for me too. O would say 1.5 to 2 minutes every time. An actual 5 minutes does seem a little long to me though.
My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
On the battery does it show what apps are consuning most battery? Did this barely start? Maybe it's an app that is constantly gathering info from online. I know my Hotmail app use to drain my battery so I had to go stock email
Sent from my GT-I9300 using xda premium
This is all the info it shows for battery info. And I'm not sure how it could be an app. The tablet is powered off completely. Shut Down.
It's really very strange.
Sent from my DROID RAZR using Tapatalk 2
Unfortunately it sounds like the battery might physically be going bad. How long have you had it and does it spend a lot of time plugged in while in use?
Sent from my Galaxy S III using Xda Premium
It's a JB thing. This happens as well on my Nexus 4. It's not a battery drain problem, but more so battery reporting is a little messed up. At least that's what I've read in the N4 section.
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
This issue has been discussed before. It is not necissarily a defective battery and in some cases is just simply a case of how the TP is being "shutdown" it was noted over at webos nation that in some cases the TP was failing to FULLY powering down...perhaps due to some location reliant apps that maybe continued scanning if shut down from within android...This AFAIK has never been confirmed however the issue has now been Solved for some users over at http://forums.webosnation.com/hp-to...tery-drains-when-off-webos-3-0-5-problem.html
Try the "fix" on page 6 to see if it solves your issue.. Hope it helps
Pickens said:
My touchpad has been draining battery even when off. You can see in the picture attached represented by the blank sections. The first blank section represents about a day of the device being off without use. And when I say off, I mean powered down through the menu, not just in sleep mode.
Anyone else seen this? Seems to be something that has recently started happening.
A little background, I was running one of the cm9 camera enabled nightlies, but wanted to try JC CM10 so used ACME Uninstaller to completely remove android. Then installed cm10 using ACME installer 3. Played with it for a few days then wiped and restored a cm9 backup instead to go back to ICS until cm10 battery is better. Since then, this battery drain has been happening even when off.
I didn't know something could be sucking battery even when device is off. Any ideas? Maybe I need to use unistaller again and start android install fresh again.
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
zaqq1 said:
I had this issue for months and decided to do some research to rectify the problem. My touch pad would lose charge from 100% to zero within ten days even when the device was turned off. Doesnt matter of i shutdown from cm or webos or moboot.
Here's what I did.
Basically I did a full clear reinstall of cm9 / cm10
1. Backup all apps and system data
2. Remove cm by using acmeuninstaller
3. Remove all folders (format) the hard drive
4. Restore webos to 3.0.0 using webos doctor
5. Reinstall cm
6. Restore backup data.
Afterwards I made some tests
Turned off touch pad at 100 percent each time from moboot cm and webos. Check back 4 days later. All good
Click to expand...
Click to collapse
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
synchron50 said:
Boot into Webos, get Dr. Battery app from preware and read what the health is. Mine is at 93%, I've had it for a little over a year and brand new it read 95%. If you're losing juice even when its completley off, I'd expect your percentage to be much lower. There's also not much that can be done about it since you can't recalibrate a TP battery.
Click to expand...
Click to collapse
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Pickens said:
Before I did all the wiping, I checked this and health is at 94%. So it shouldn't be a bad battery. I'll update on the results of the full CM and WebOS wipe.
Click to expand...
Click to collapse
Mine has been doing the same thing. When I turn it off and leave it for a day or so, I have battery loss. I thank it started when the camera was added to CM9.
I am looking forward to seeing your results.
Pickens said:
Thanks for the reply. Here is what I have done to get a start fresh.
1. Remove cm by using acmeuninstaller
2. In WebOS, installed "Remove Android" from Preware to wipe remaining Android boot stuff.
3. Followed this guide to repartition and restore 3.0.0 WebOS. http://forum.xda-developers.com/showthread.php?t=1426244
4. Factory reset to wipe everything again.
5. Performed system update to WebOS 3.0.5 (tried to upgrade through WebOS doctor 3.0.5, but would not boot. Restored back to 3.0.0 and went through System Update, and that worked fine).
What I plan to do this afternoon (didn't have time last night):
6. Install Preware, UberKernal, and GovNah (I like my WebOS to be at its fastest before a CM install, even if I never use WebOS)
7. Reinstall cm10 (JC Sullins 12/16), moboot 3.8.0, new CWM, and gapps using ACMEInstaller3.
8. Install apps fresh (don't really have anything where I need to restore data).
Once I do this, I'll run some tests where I leave it off for a couple days. I'll post back with results. Hopefully getting a fresh start will fix things like it did in your case.
Click to expand...
Click to collapse
I have three touchpads and did exactly as you. Afew of my observations:
1. the 94% does not appeared to be measured. It is the current Voltage (expressed as mA's)/manufactorers hard coded spec, (6612mAh). If in Android, (I'm onCM 10+camera+gyro), using Battery Monitor Widget, I can adjust the actual to 6100, (or anything else), and get 6039/6100=99%
2. My discharge rate on WebOS in Airplane mode was arround -613 to -850mA. Screen on, (brightness affects this).
3. My discharge rate on CM10 in Airplane mode is about -520mA!!
4. A PC's USB port puts out 500mA's!!!
5. On the touchstone, (doesn't seem to matter if WiFi is on or off), with screen on 1/3 brightness + Battery Monito Widget = +853 to 945mA
6. On HP charger & cable, same as above = +1,377mA
What suprised me was the greater drain in WebOS.
I've had this issue since the beginning of installing Android on both my TP. Really annoying but I always assumed it was because of Android since I had no problems with WebOS.
I get battery drain when leaving the device unused, but it's significantly lower than it used to be in early stages of cm9 and cm10 development. I find it to drain slightly faster than WebOS but you have to remember this device was not designed around android.
This has not been a discussion of power loss in an unused state. It is power loss in an "off" state. Powered down with neither WebOS or Android running.
Sent from my DROID RAZR using Tapatalk 2
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Pickens said:
After doing all the wipes listed above, I ended up just putting the newest CM9 nightly (with GAPPS) and moboot 035 back on instead.
Results. I believe these wipes have fixed my problem. Here are some of my results:
Turned off at 96% for 18 hours, still at 96 when I booted up.
Turned off at 77% for 12 hours, still at 76 when I booted up.
Turned off at 56% for 12 hours, still at 55 when booted up.
Before I would have lost about 10-15% over these same time periods. Not seeing the drop at all now. And all of these power downs were on the Android side so don't believe the hype about Android power-down being the problem.
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
I restarted from scratch and it worked. I turned my TP off for 2 days and the battery read 100% after boot. Thanks for the help.
Checking back after a few weeks, glad to see that the fresh install solved the issue for some of u guys
battery health 91 % DR battery
so this means my battey is going bad
had my tp for over a year now
is that normal ?
anyone ?
Not sure how you got that from this thread. Some people suggested it might be a bad battery, but I think our results with restoring our touchpads would show that wasn't the case.
Follow the steps in post 9 and everything should be good to go. Worked for me. No more battery drain issues while the device is off. I've even returned to CM10 and still no problems.
Sent from my DROID RAZR using Tapatalk 2