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.
Related
While in my pocket my Ginger Tazz v19 (and v16 v17) kept going into a bootloop. I could not figure out why, and was never able to duplicate the issues while I was looking at it; although I suspected it was either custom ringtones, exchange syncing issues, or over-clocked to much for my poor little Eris (729 using Set CPU, but with advanced setting to battery bias). SO! I wiped (and wiped and wiped and wiped), waited for everything to sync, set the CM gov to 729, and sure enough, booted in my pocket again- repeat the wipe flash reinstall, left it alone, stable for 24 hours, noticed battery life was not ideal, but had no boot in pocket issues. Reinstalled SETcpu, went a little more conservative in my profiles and main profiles, and I've been stable for 2 days now- but I haven't set any custom ringtones yet either; oh and I did have an issues after using SongBird (uninstalled). I can't post on the DEV. forum, just wanted to give my .02 for anyone who LOVE GINGERTAZZ as much as I do, and can't seem to figure out why it's not running like it seems to for 75% of the posters......
Thanks again TAZZ! Hope you're feeling better BTW!
So I've had less than stellar luck with this phone. I purchased it and rooted it pretty much on day 1, (this was back in early May) and immediately started seeing some pretty awful rebooting. I switched kernels from Das Bamf's to Imoseyon's, which helped it go from mind-numbing to merely bad (used to reboot EVERY TIME the screen was slept and turned back on, went to happening maybe once an hour)
I switched back to stock, same problem, rebooting literally once an hour. I called Verizon for troubleshooting help and they immediately had me switch it out for a Hardware version 2.0 phone, which I've now had since May 15th. It does work a lot better, but it's still pretty bad. Here's the timeline:
Ran stock for about a week, was seeing 1 reboot every other day, decided to root. Installed BAMF remix 1.7 with the .7/.6 CDMA/LTE radio, which left it pretty much the same, rebooting every 30 hours or so. It's particularly likely to do it when using Navigation or on phone calls. It's not a stress thing, I can run Linpack, quadrant, make calls and surf, whatever, it runs fine at stock speeds, 1.92, 1.92x... and will do so for hours without rebooting (until it does)
Switched to 2.0 w/ the MR2 radio, and the reboots were even worse. Now more like 1-2 times a day. Thinking this was not a radio issue now, I eased down the clock speed (I was running 1.92x kernel) down to stock speeds, no affect. Upped the voltage by switching to 1.92, still no affect, reboots a couple of times day, ALSO with a few random shutdowns thrown in for fun. I tried Standard as well, letting it top out at 1.4, still having the issue.
MR2.5 came out, switched to that, and it became unuseable. Reboots literally every 5-10 minutes, and I tried running it that way for the better part of a day, thinking it was maybe the kernel settling or whatever, but it stayed that bad. I switched back to 2.0 and kept seeing the reboots a couple of times a day, so since they were worse on GB I figured I'd go back to Froyo.
Loaded 1.8 Remix, and the reboots are still happening a few times day. At my wit's end, I decided to go straight back to stock, no root. It ran fine that way for about a day, then randomly shutdown again. It has seemed good so far today, but the random shutdown happening makes me assume it's still not stable.
I really don't think it's a problem with 2 phones in a row, and there's thousands of posts of people experiencing similar problems, so it's not something weird I'm particularly doing. There seems to be no rhyme or reason to it, as some people are rock solid with Froyo with the .7 radios, or the .6/.7 combo, or some are fine with Gingerbread MR2, or even 2.5. Me, I have no luck with ANYTHING.
Should I start another ticket with Verizon for another dud phone, or is the promised OTA update really going to do something magical that MR 2 or 2.5 haven't already tried to do to fix this thing?
If it were me Id be screaming at somebody at Verizon. If your sure that nothing u did rooting or flashing roms caused the reboots then get a new phone. Rumors say that gingerbread is coming tomorrow but you can't out to much stock in that and even if it does I doubt there is any miracle code written in that's gonna help you.
Sent from my ADR6400L using XDA App
Some people have had random reboots on stock rom. But since you were on stock for less than a day, it's impossible to determine whether the reboots are due to a defective phone or something that happened during/after you flashed the custom rom. You obviously know your way around various roms, radios & kernel/cpu tweaks, and nothing seems to help. If you have the patience, go to the IRC channel for more suggestions. If no one there can help, I would restore to stock & exchange the phone. You may have a defective device that will never work right.
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?
I'm posting this here because I hope some devs might be able to get a handle on the problem. I think it has something to do with the launcher.
Since I upgraded my phone to a 2.3.4 ROM, I've had constant problems with its randomly rebooting, or occasionally just freezing. (I say "rebooting", but it always gets stuck in a boot loop, and so it might as well be frozen.) The first ROM was Synergy, but I've had the same trouble on Warm, and with three or four different kernels (OC'ed and not OC'ed) on each of those ROM's. In some configurations it's better, and in some it's worse, but I've nearly always had the reboots happen at least once a day. Sometimes it happens while charging, sometimes while it's not; sometimes it happens while I'm touching it, and sometimes when I haven't touched it in hours (kind of annoying when it's my alarm clock--I missed a meeting last week). There's not a lot of consistency in when it happens, though I should say, for the record, that I've been using Launcher Pro the whole time.
Obviously, I'm not the only one with this problem: for some, like me, it started with 2.3.4 (including, in many cases, the stock OTA); for others, it started when the phone was first released; while for others, it's never happened at all. The fact that some people haven't experienced it at all may mean hardware has something to do with it, and I even read one account of a guy who took five different phones back to Sprint for replacements before finding one that worked right.
After searching high and low, I found a thread on the Sprint Community forums that suggested editing the data.prop file to keep the launcher in memory constantly (Look here and scroll down to post #9.). I tried this a couple of days ago, and it hasn't fixed the problem, but it did dramatically reduce it: I went from rebooting every two hours to rebooting once or twice a day.
I've noticed one other interesting thing: a couple of months ago, I started playing Godville, and I've been propping the phone up next to me and letting it idle with the screen on (while on USB), so that I can glance over every once in a while to see if anything is happening in the game. I've noticed that, every few minutes, the home screen wallpaper briefly replaces the app I have open; it happens so fast that I can't tell for sure if the whole launcher is coming up, but I suspect it is. I wonder if this constant yanking of the launcher into the foreground might be the source of the instability.
my mind is like..... blowwwwn
---------- Post added at 01:37 AM ---------- Previous post was at 01:28 AM ----------
no but on a serious note man... many people have had problems with reboots since the launch of the 3D, which was 2.3.3 based. I doubt that was the issue (launcher, your update, your games... gnomes...)
i would say flash the RPM PGIMG86423million update whatever that number is for the bootloader update.zip, and see if that rids you from the reboots.
for me, i fixed my reboots by getting a new SD card... i had the same issue when i first got my 3D late in july. Did it both on 2.3.3 base, and 2.3.4... it occurred to me one day that a bad disk would cause system reboots... and not being able to change out the one built into the phone... i opted for the SD card because it was cheap and i wanted a better one anyways. reboots went away immediately.
it also never occurred to me initially that my SD had been bad for a long time... not just when i had my 3D.. on my previous phone (samsung moment with froyo), whenever i would move apps to the SD card, i would always get some kind of error message. trying to move them a couple times would always successfully move the app(s) to the SD card.. i figured this was a problem with the rom i was on (speaking of my samsung moment)...
then when i transferred my card to my 3D, same problem, along with the reboots, and a light clicked on in my brain and said "***k-tard, your SD card is bad. derp."
haven't had a single reboot since then. i even wonder if the paramount number of people having reboot issues on the 3D was due to HTC possibly shipping them with defective SD cards...
just something to mix around in your brain for a bit...
Yeah, I considered the SD card as a problem, but the reboots happen even when the SD card is mounted as a USB drive. Also, a bad SD card wouldn't explain why keeping the launcher in memory dramatically reduces the problem.
I'll be giving it a try.
Just a side note. I've been using the stock kernel lately and havn't had a single reeboot. I'm on synergy rom and since he put back in the stock kernel w/ no OC I've had no issues.
I may try that, but it would be sad to not to able to OC a rooted phone. I'm starting to wonder if it's a bad internal flash drive, though.
You should try a stock ROM to see if that solves your issue if that's doesn't work maybe you have defective phone
Sent from my PG86100 using xda premium
All my problems went away when I used Senseless ROM. I think the kernel in the ROM is stock. It's been over two weeks since my phone has frozen on me and no more random reboots.
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
I'm having the same reboot issues. I've noticed a few things:
1. Doesn't matter what sd card or how new, my phone reboots unexpectedly
2. Phone ONLY reboots RIGHT when the screen times out. Only on Android 2.3.4 w/ sense! It does not matter what kernel. Whatever I do, all reboots are directly related to sense on 2.3.4.
3. The only solution I have found is to deactivate the screen time out or gut HTC proprietary sense from the ROM.
P.s. I DO NOT have problemswith any ota based off 2.3.3
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Click to expand...
Click to collapse
Tiamat isn't stable for me.
MTKnife said:
Tiamat isn't stable for me.
Click to expand...
Click to collapse
Nor for me. It causes daily hard lockups that require a battery pull on my phone. Tiamat exhibited this on multiple ROMs for me.
I think trying a largely stock rom is a must as a start to tracing your problem. So is incremental additions of apps, tweaks, etc. Basic debugging and defect isolation stuff.
bloodrain954 said:
Only stable kernels are tiamat and stock. All the others cause bootloops thanks to tryin to remove ciq
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
What about bcblend by mwalt? Senseless rom has been using that for quite some time and I haven't had any issues. When it was switched to tiamat for a short time (2.5 & 2.6, i believe) I had problems with lockups and reboots. Reboots would occur when the screen timed out every once in a while.
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Tiamat has not been stable for me either. I tried many different rom and kernel combos and am still having the issue. I noticed it is mostly happeneing when the phone is plugged in. but it also happens sometimes when im on a call. So there has to be more than one issue one being the proximity sensor and i cant figure out the other ive hset charging profiles to 384max and 198 min and other low clock speeds to see if it would help. Also set a temp profile to underclock when its over 38.0 celsius. Right now im running olympus trinity xe titan i ran it for a few days with mild anthrax and it only froze/rebooted a few times a day. I tried the anthrax kernel and it rebooted twice the first half hour so i flashed tiamat last night. Im trying to give it time to settle in but it just rebooted again when i plugged into pc. I bought my phone used and rooted before i even activated it so i dont know if this is something kernel/rom related. I started another thread a few days ago about this and the few responses i got were people running stock romand kernel not rooted. So i guess all we can hope for is the devs to figure it out or sprint to give us an ota that fixes it since im starting to belive its a hardware issue.
If you're on titan freezas is recommended.
Sent from my PG86100
I saw a few people talking about that but I thought they were talking about for when he released Hades. I'm gonna find the dl link now thanks.
Sent from my PG86100 using XDA App
Cabe24i said:
Just curious OP - have you tried the phone on a newly installed rom without installing any side apps for a day or so and seeing if you have any problems? Back on my old nexus S 4g i had issues with a particular battery app that would give similar problems to what you are experiencing.
Click to expand...
Click to collapse
Not for that long a period, no--unfortunately, I haven't been in a position where I could give up most of the use of my phone for that long. Once I have grades submitted next Monday, I can probably do more methodical testing.
I'm still freaked out by the way the launcher pops up every few minutes, though--has anyone else ever seen anything like that?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums
Moving to General
One of my favorite rom and kernel combo's is infected eternity with anthrax but random reboots are common for me with any sense based rom. I run MIUI with whatever aosp kernel and everything is flawless. Other than experimenting with kernels to find battery life, MIUI is the most stable rom I have used so far and is my new daily driver!
Sent from my HTC EVO 3D using xda premium
My evo also reboots and i havent rooted my phone at all. I did get a new SD card and that reduced the amounts of reboots i get! . Although, i still get a few every week.
hope sprint/person finds a fix for this soon.
Mine did it stock / rooted stock and viper ROM I an on fresh and so far smooth as butter ... Stock rooted was awful every time it would time out bam reboot
Sent from my PG86100 using XDA App
So, I have one of the first Vibrants to hit the store. I'm running Neobuddy ICS Passion V8. Before the *****ing begins I want to say that I love this rom.
I followed the install instructions to a "T".
I used antutu cpu master to overclock to 1.3 because I read that other people were doing it and didn't see any complaints. When my phone booted to the point where the message that cpu master had superuser privileges came up, it froze and the display changed colors getting lighter and washed out looking. That scared the crap out of me and I thought I had just cooked my cpu. I pulled the battery and rebooted then tried to open the app and change the settings before it froze and failed, rebooting 6 times, battery pull each time. I finally relented and did a factory reset. Previous to this adventure I had it clocked at 1Ghz max and 100 min and was experiencing no lag. I just got greedy. I only changed it at all because I was getting 16 hours of battery life and thought I could trade some battery for speed. I have it running at 1.2 now and it's fine. So this is not so much a question but an answer to anyone who might be asking themselves if they should overclock to 1.3.
Bugs
mute/unmute necessary for incoming call audio
automatic brightness not responsive
complaints
contacts app doesn't match the rest of the theme
no text button next to phone button on contact
no long press functionality on contact
When it comes to Vibrants, all our phones are different. Some users will be able to run at 1.3 from now until our Zombie overlords take over and we're forced into indentured servitude. Others, like you and I will be lucky to run a mild OC without freezes.
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
What he said!
younix258 said:
I used to oc to 1.6 ghz on cm7
sent from the xda app on my android smartphone.
Click to expand...
Click to collapse
My first Vibrant T959, manufactured prior to Oct 2010, used to fly, and overclock like there wasn't any tomorrow, and would flash anything! Was the most cooperative phone I ever had! Wish my wife was like that. LOL
Then I unfortunately got into a true HardBrick with it, and stupidly, instead of JTAGing it, got T-Mobile to exchange it, for a same model, but with a manufacturing date on it of 8-2011!
And this replacement phone, hasn't even ever performed as well as the old one, despite how I set it up, And at first it was stuburn as hell to get it to cooperate with flashing, until I unlocked it, and it calmed down alot, even though that makes no sense at all, but nun the less, it is what it is!
Point is, that each week, month or quarter, the phones aren't consistent in manufacturing qualities or how they run and perform, or the components they use. I had a Thoroughbred in the beginning, and now I how a plow horse, yes she still works well, but needs alot of coaxing, I had to re-do the GPS contacts right so there was firm pressure, and the SW flashes were a ***** in the beginning!
But I believe when this phone first came out, there was better quality of manufacturing and they used the same consistent components, until they shifted their focus on other models to push onto the market!
So again, what Billy Bobs got going with his, Isn't what it ll be with yours!!