Like the topic says, I'm finding the Nexus S a cracking bit of kit but I feel like I'm sat waiting for a time bomb to go off!
The phone is supposed to be a pure Google dev phone we can mess with. I'm up for rooting and replacing the rom / kernel and tweaking to get it just how I want it. The problem is, I darent!
The reason I daren't flash another rom to this phone or do anything other than intended with the stock rom is the infamous freezing issue that so many are experiencing.
There are many threads about the matter but this is the one that's made me consider getting rid:
http://forum.xda-developers.com/showthread.php?t=993403
I'm not happy at paying out for something that could go wrong at any minute through no fault of my own. Seems a common problem and neither Samsung or Google are acknowledging this issue.
I'm undecided but my Nexus may be eBay bound!
I will say the only time I witnessed freezing on my device was when I was running 2.3.2 XXKB3 radio, and voodoo kernel .. I upgraded to 2.3.3 and didn't like it, soo I wiped my phone completely, went back to 2.3.2 >netarchy kernel>xxkb3 radio and now I have no problems at all..
I was also experiencing the ringtone issue where the ringtone would all the sudden change themselves. I noticed that it happened to me right after using amazon mp3 EVERYTIME. So far after the write and starting fresh, I'm running smooth with neither problems!!
Id give rooting a chance. I doubt you'll have a hard time, just remember to make a nandroid backup and youll be fine.
Sent from my Nexus S using XDA App
Thanks for this, it's good to know there are people out there not experiencing this problem!
My fear with rooting IS the nandroid backup as in many cases it appears to be this that's breaking the internal storage leading to freezing problems.
My Nexus S was supplied with 2.3.3 as standard and that's the way it's remained since I've had it. I do note that Google seem to have pulled the update though according to some threads here.
My dilemma is whether to root and flash custom rom and kernel or leave well alone as every case of freezing has been reported only after flashing / updating has ttaken place in some way.
That said, if I did not want to tinker and flash different roms I would never have bought the Nexus S so not doing so defeats the object!
You just answered your own question.
I went back to stock with a nandroid ( http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/ ) and it worked fine. Got bored and rooted again. After SuperAosp I don't think I could ever go back to stock.
Nexus SuperAosp
xspyda said:
Thanks for this, it's good to know there are people out there not experiencing this problem!
My fear with rooting IS the nandroid backup as in many cases it appears to be this that's breaking the internal storage leading to freezing problems.
My Nexus S was supplied with 2.3.3 as standard and that's the way it's remained since I've had it. I do note that Google seem to have pulled the update though according to some threads here.
My dilemma is whether to root and flash custom rom and kernel or leave well alone as every case of freezing has been reported only after flashing / updating has ttaken place in some way.
That said, if I did not want to tinker and flash different roms I would never have bought the Nexus S so not doing so defeats the object!
Click to expand...
Click to collapse
There are ways of returning to stock without flashing a downloaded nandroid backup. You can always just flash the Google OTA update.zip. I personally prefer that method, I don't feel comfortable restoring a nandroid backup from another device on my phone.
i9023 user here, my phone was only on the stock 2.3.3 for less than 3 hours before the bootloader gets unlocked and CWM recovery flashed, CM7 was put in there right away. I've been flashing the CM7 nightly almost every other night whenever there is a release. Freezing and reboots do occur sometimes on those not-so-stable builds, but well, these are part of the fun (of flashing ROMs) isn't it? Nandroid backups will always save the day. if everything else fails, use ODIN! It will put your phone back to the state when it just came out of the box
My Nexus has been rooted since day 1 and have never regretted it. Really up to you though, if you're running a stable rom*, which there are plenty now, you won't be experiencing any "freezes" that you wouldn't have had on the stock already imo.
Thanks for the reassurance guys, I think the problem is getting a little confused though. My concern is not really about the rom flashes and yes I expect problems with new roms and to a certain extent yes that is part of the fun.
However, my concern is the irreversible freezing issue that many are experiencing after flashing an update of any kind - the freezing issue / unresponsive screen problem that cannot be resolved with a nandroid restore or an Odin flash. Many experiencing the problem have tried all.methods available and got nowhere, in fact the only fix for that seems to be returning the phone to Samsung where they either replace the phone or the hardware inside.
I have no doubt that the custom roms out there are far better than stock and that the kernels available now can improve battery life, my problem is not with rooting or flashing per se, more the irreversible damage often caused during the process. If there was a known fix for this I'd feel MUCH happier with my Nexus S, that's all I'm trying to get across.
It seems like a 'relatively' small percentage are experiencing this issue. Also seems like a hardware defect( browsed through the Google thread and read that Samsung have replaced PBA and/or BGA boards for the faulty phones) to begin with. There's not much you can do about a faulty device save send it back.
Nexus SuperAosp
Got my NS 2.3.1 and didn't have any freezing what so ever.. rootbeck, unlock bootloader, currently running MIUI with no freezing also... i'm about to switch to CM7 to see if i like it lol and if not i'm just going to go back to MIUI... however i plan to change my kernel to get the old screen colors back... i hate the 2.3.3 yellow feel... my phone is just less vibrant
deejaylobo said:
It seems like a 'relatively' small percentage are experiencing this issue.
Click to expand...
Click to collapse
Too many for my liking all the same. You'll no doubt have see this thread. Many previously happy users experiencing the problems after some time.
http://forum.xda-developers.com/showthread.php?t=993403
Never ever had an issue with freezing, I have hopped from 2.3.1 to 2.3.2 to Cyanogenmod nightlies(before RC), then to 2.3.3 then to Cyanogenmod 7.0.0 then to 7.0.1 and finally to now 7.0.2
nothing has ever happened.
I have never regretted rooting my Nexus S, I thought I wouldn't do it because there are no roms, but interestingly there seems to be a lot to do with it.
Good luck sir, may god be with you every time you access a black menu on your Nexus S.
Related
Hello-
First off, please excuse my n00bness - I'm from the world of Windows Mobile hacking, and this Android stuff is really confusing me.
I've been tolerating stock for a while, but the slowness is really getting to me - today I clocked my Hero at 12 seconds to wake up from standby, which is just unacceptable. I'd like to know if there are any significant speed benefits to going from stock to the latest MoDaCo rom? Are there any downsides? I read the post over at modaco.com, but couldn't see any "known issues".
Thanks for any input,
TM
Take the plunge.
I went from stock to Fresh and overlayed Modaco. My uptime shot to 90%, 80% and stuck at 70%.
I reflashed to Stock then back to Modaco. I am now at around 15% uptime. I removed the bloatware from Sprint and LOVE the speed of this phone now. Its what I expected when I bought it.
I have no doubt that you'll see a speed increase with Modaco. Especially if you remove the sprint apps once you load Modaco.
Thanks for all the replies. One more question though, are there any big known issues with the latest MoDaCo? I thought I read something about BT not working, or something to that extent.
it's worth it to switch to any custom rom. bluetooth is just something thats messed up with our 1.5 builds.
ffolkes said:
Thanks for all the replies. One more question though, are there any big known issues with the latest MoDaCo? I thought I read something about BT not working, or something to that extent.
Click to expand...
Click to collapse
you will notice a big difference switching to modaco 2.2... and im not experiencing any BT issues at all... matter or fact, im not experiencing ANY issues with anything using this rom...
Heck, anything is better than stock.
especially since we have a custom kernel now its definitely worth it to go to any custom rom, especially modaco 2.2
Im using fresh. I used the kitchen to root my phone and installed 1.1. No problems so far except that the voice recorder app keep crashing for some reason. I did an upgrade without wiping though so that might be my problem.
Its a lot faster and the tether app is awesome!
Ok, so far so good. Got everything flashed, but how do I get rid of things like Stocks/Sprint TV/NFL/etc? Just follow the generic guide (for any rooted Hero) I saw?
I ran stok for about 6 hours and decided that I didnt pay that much money for a smart phone that was that slow.
I flashed Fresh 1.0 to start and I have tried just about all the roms that are out there. Including modaco 2.2 and it may just be that I started with fresh but I always seem to go back to it over the rest, and add onto that the modaco kernel with compcache and then doing the config tweak found here my phone just flies now.
I now have it set to where I feel a phone at this price point should be to start.
edit: to remove the apps follow the instructions found here
ffolkes said:
Ok, so far so good. Got everything flashed, but how do I get rid of things like Stocks/Sprint TV/NFL/etc? Just follow the generic guide (for any rooted Hero) I saw?
Click to expand...
Click to collapse
Use the Fresh Kitchen to pull any you don't want.
You know what? I've flashed MoDaCo's ROM before, but it was just too much like stock (except for the obvious speed increases). I flashed Fresh 1.1, and loved it because it had the speed of MoDaCo's, plus the Espresso UI. Then I recently flashed Gumbo Kernel to my phone, and omgwtfzorz my phone is RIDICULOUSLY fast. Not noticeably, but RIDICULOUSLY. I can't believe you've been living with stock for this long >.< Custom ROM's and kernels are necessary for this phone haha.
Been lurking on here for a while, great site, helped me get my phone rooted and more useful than stock. My phone is however starting to give me some sass...
Got the Sprint CDMA Hero back in Feb. Loved it for about a week, then hated it.. Started to run REALLY slow (like 1-2 sec to flip between homescreens), so I took it back and got a new one. Again worked great for about a week then it slowed down slightly- said screw it and rooted it.
Wow. Loaded up Fresh 1.1 with the Gumbo Kernel (2.6.27), and SetCPU. Occasional force close aside, it became the phone I thought it should. When the official 2.1 update dropped, I looked back into the custom ROM to take advantage.
Familiar with Fresh's stuff, I decided to try out his stock ROM. After updated the RA, I loaded the ROM- then everything went downhill...
It was Slower than my stock 1.5 was, and force closed constantly. The phone was unusable. So I decided to load FreshToast. Wouldn't load- would get stuck on the HTC logo as it booted, like it would just freeze there. So I reverted back to my fresh 1.1 backup.
I then tried a few other ROMs, none of them would work either. Only ones I remember were iZEN: got the same HTC boot loop, and DAMAGE ROM: which worked for about 3 days before constant force closes.
Ultimately I went back to fresh 1.1 frustrated. That was a few weeks ago, now my fresh 1.1 is starting to wig out on me! Constant force closes of SenseUI, apps are unstable, and Wi-Fi tethering crashes my phone.
I really want to run FreshToast, or at least give it a go, but I don't know what to do at this point. Begining to think something is wrong with my phone (I have heard from many people personally that the CDMA hero is just generall unstable)
Please any suggestions would be appreciated.
Lots of things going on here, first I would say in my own personal experience my heroCDMA has been very stable, even overclocked to 768. I never get FCs unless I did something wrong messing with an APK or something.
Are you using Apps2sd? If so is your EXT 2 upgraded to EXT 3? And is your dalvik on internal memory or SDcard? Any particular program thats FCing on you, or just completely random? Are you wiping between roms(data, dalvik, EXT)?
I would give Fresh Rom 2.1.2 a go, and if you can get it stable and really want overclocking, flash an overclocked kernel over it. such as...
http://forum.xda-developers.com/showthread.php?t=705074
I've also had nothing but a stable platform out of this phone. Granted, pokey compared to current offerings, but definitely stable. My phone also started out as 1.5 from Sprint, but after getting tired of waiting for the official 2.1, I rooted, loaded RA 1.62, and have been rom-hopping ever since.
Just to rule out anything basic, you haven't applied the official Sprint 2.1 update or OTA patch, right?
I tried a few rooms from here and had stability issues as well. Try going to android central forums and flashing the honeybun rom. I have iced honeybun lite with the overclock kernel and overclock widget set to 710. It is very smooth and stable.
-------------------------------------
Sent via the XDA Tapatalk App
Not running Apps2SD. I perform a nandroid backup, then wipe everything it will let me every time I try a new ROM. Running RA 1.62.
FCs are mainly random. I'm ok with one once in a while, not a big deal. But SenseUI, or Fresh itself will FC at least twice a day. No official Sprint patch/updates have been performed since rooting it.
I guess I should clarify the "unstable" comment I made. I know 6 people with the CDMA Hero, Only 2 of them haven't had any trouble. The rest of them have had at least 2 phones because it was practically unusable slow (very similar to what I mentioned with mine), one of them has gone through 5 of them- everyone has crashed. Maybe they just send us the bad batches here in the Midwest lol.
So those personal testimonies have always had me frustrated when it runs slow, cause everyone on the net doesn't seem to have these problems. I do have the "with Google" version, not sure if that impacts anything at all.
Is there any hard wipe I can do to start from scratch? It is Very possible I tweaked something wrong early on and it's just catching up with me. When I get a chance I'll try that honeybun ROM, Fazulka.
Thanks for the replies!
Aloysius 2.1 LWP (not overclocked) has been fast and rock solid. Some Hero's (like mine) have issues with the OC'ing so it might just be that. Try using a non overclocked ROM.
I have the same exact phone you do and I can testify that there is performance issues with these phones. ....I've personally been through 2 of these phones and I've got this one rooted running buufed 2.1.6 which runs okay although the older buufed roms Were way better.. not much u can do with the force closes..I'd boot back to stock and see how it responds...leaving it rooted on stock software should let u know if u messed anything up.. then try a rom like buufed 2.1.2..that's a good stable version but it doesn't come with sprint voicemail and work from there
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
DownloaderZ said:
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
Click to expand...
Click to collapse
I love it right now.. before it was bloated and totally incomplete and now they got it working pretty darn good you asked at a good time! but for some users.. still causing issues. For some like myself it is perfect right now absolutely no problems I took a while to stick with GB because of all the problems with CM7 I had an htc magic which was pretty similar to the dream and I understand most the problems you probably faced. I've tried a bajillion cooked rooms myself and ever since I moved to the nexus one I just stick with a few (I tried so many on the magic it was my first android and wasted so much time -_-) I would suggest you give this one a try it still has extra features but most of which I find useful
It makes it noticeably snappier and battery life is better. 99% win (wireless LAN reception is a bit worse). I went from stock 2.3.4 to CM7 and am kicking myself for not doing it 16 months ago lol. Maybe there were issues with cooked Roms earlier but the n1 is a mature platform and I haven't noticed any major issues with cyanogen 7.03, of course YMMV
Sent from my GT-P1000 using Tapatalk
I have been running the nightlies for weeks and they have been very stable for me. I have not had any significant problems and really like using them. #85 put the permissions blocking in yesterday and I tried it with a few apps. Seems to work fine. I liked stock rom, but personally could not do without trackball wake and lots of other wonderful features in cm.
Once you go custom you wont ever go back to stock.
Make sure you understand how to flash a custom recovery and how to get to it first.
he said he had cm on his hero so he must now about custom roms..
i think it is currently very stable and good apart from the wonk issue.
CM7 Nightlies have been gold for me. Except couple bootloops. I'm on #83 now with data throttle removed. I love my Dinc
Sent from my ADR6300 using XDA App
I have been running CM7 since shortly after the official Froyo was released from Google. I had to send my phone back for the powerbutton and so I rooted it right before and tried out one of the CM6 nightlies. It was amazing. The features in every subsequent version have only built on the quality of CyanogenMod. I have been a nightly user ever since (although I only flash nightlies every week or so).
It has been extremely stable for me and I have converted a few friends (most recently a friend with the Desire HD) and they don't know how they dealt with the stock crap for so long.
So in short, give it a shot. Do a nandroid beforehand if you are worried, as then you can go right back if you don't like it.
You can only control the permissions on cm7 nightlies. That feature isn't available in the stable release I believe.
Sent from my Xoom using XDA Premium App
cyanogen 7 starting at nightly #74 has introduced some new bug fixes which greatly improve standby battery life, so that now idle current with screen off is 3-4mA. its so good now, that you can leave your phone unplugged over night for 8 hours and only lose like 3% battery. and this is WITH wifi and email accounts turned on and syncing.
this makes the nexus one like a brand new phone and turned it into a proper normal device in the sense that you can now rely on superb battery life. you know that when you arent using it and the screen is off, when you come back to it you will have the same battery percentage as when you left it.
its a no brainer to use the nightly just because of this alone.
Ever since the 2.3.4, I've been happy with the battery life and fixes with the GPS. Currently my uptime is 190+ hours without the usual sluggish response that requires a restart.
Running CM7 I found more random issues from the call quality being distorted and random reboots, to other random bugs that I need something stable.
Sent from my Nexus One
i often go 550 hours between reboots on cyanogen.
Whether it's a Gingerbread ROM, or just pre-rooted GB Motorola ROM, I am not stable. I get random freezes sometimes, but more often I just can't turn the screen on. It turns on, but is completely black (but you can tell it's on) and I have to do a battery pull. Liberty GB (all versions) do this as well. No GB ROM in existence is stable. I go back to .340 stock Froyo SBF or back to some other Froyo-based ROM, everything is fine. The problem never happens once.
HOW ARE YOU GUYS HAVING STABLE GINGERBREAD ON THE DX?
Ugh. Rant over. If it was a hardware problem, it'd happen at least occasionally on Froyo.
My next phone is so going to be an HTC or Samsung.
Absolutely no problems at all using Apex 2.0 RC2. Gingerbread AOSP.
No problems on prerooted GB. I was having that issue with rooted Froyo towards the end before I upgraded. It would mainly happen when I used Maps and as far as I could tell it was the GPS screwing up because when I turned off GPS my phone worked fine. I have yet to turn on GPS on GB, food for thought.
Sent from my DROIDX using XDA App
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
try cyanogen its pretty fukin awesome. only bugs so far are vieo camera and hdmi. other than that its fast n stable...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk
Cyph' said:
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
Click to expand...
Click to collapse
I don't think it's Win7 64bit causing the issue, I'm running it at home and work and I haven't had any issues connecting or disconnecting my phone. I would really recommend SBF'ing back to Froyo, clearing data and cache a few times, and starting with a fresh ROM. And if you have TB backing up any system data, don't restore that, just apps + data.
I love how people say they will switch to a different device manufacturer as if they expect that device to be 100% flawless.
I use prerooted GB .588 and I don't have any freezes and the random reboots stopped after I did a factory reset.
I,ve been running 596 deodexed since the first day it came out with no issues. Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Sent from my DROIDX using XDA Premium App
.596 rooted deodexed. Perfectly stable. Are you overclocked?
The only time mine froze was when I went from having it underclocked at 800 MHz to overclocking at 1.4 GHz. But I expected that to happen lol
Sent from my DROIDX using XDA App
Liberty is working great for me. I have had one freeze up since may.
Sent from my Xoom using XDA Premium App
My Verizon Droid X works great with GB. Even pushed it with Netflix and Hulu. I burn about 2200 min a month of cell time on avg. No issues.
I am running the latest DarkSlideX on my DX. It's flashed on top of TBH's 2-part 596. It's fast, stable, and has pretty good battery life, too. I had a reboot issue the first day with it, but a couple reboots and it hasn't hiccuped in over a week.
My DroidX Thrives on the DarkSlide!!
I have had about 1 of the problems you've discribed: The lockscreen blackout but that only happened once.
The problem is that you are probably deleting necessary files with Titanium backup. The crappy thing about GB is that half of the apps on the system that moto puts in there are interconnected with everything else so if you kill one app it'll make your phone die. I have never had the random freezing; but If I were you I'd delete WInzip if you have it on your phone. This is the main reason for a lot of my gingerbread issues. I now use ProPlayer: you can either get it free somewhere online, or off the market[place for like 3 bucks.
Everything is now working great.
Massgainer said:
Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Click to expand...
Click to collapse
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
BBJohnnyT said:
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
Click to expand...
Click to collapse
After SBF'ing, I've always had to (so far) wipe data and cache to stop it from bootlooping anyways, which is basically the same thing as doing a factory reset.
Roland Deschain said:
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
Click to expand...
Click to collapse
Nothing to add, just wanted to say "Hile, Gunslinger!" (just finished the audiobook version of DT 7).
So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
I've flashed a number of custom ROM's that speed up the phone significantly and drastically improve battery life. The only problem is after a few days of use I almost always start to get intermittent problems like random reboots, force closes and texts not going through etc.
I always follow the install instructions to a "t" and I still get problems. I must be missing a step somewhere along the way or not fully understand the cons of running custom ROM's or something.
I'm at my wits end. At one time I thought it must be the phone so I swapped with Sprint but I still have the same problems.
Currently I am running Scrambled EGgs22 V7 and I love it (when it works). I've tried bonsai, urban roms, you name it. Its the same results with every one. They work fantastic at first and then slowly become unusable.
Is there anybody out there who has experienced something similar to this and can help me remedy?
Having journaling enabled does help with data corruption if you find yourself having to start over a lot due to force closes.
Are you under/overclocking and/or undervolting at all? IIRC, stock speeds are ~400/1000Mhz.
Sounds like journaling is youjr answer. Make sure it is enabled and never pull the battery without shutting the phone completely down..after the vibration.
Sent from my SPH-D700 using XDA App
Kafluke said:
So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
I've flashed a number of custom ROM's that speed up the phone significantly and drastically improve battery life. The only problem is after a few days of use I almost always start to get intermittent problems like random reboots, force closes and texts not going through etc.
I always follow the install instructions to a "t" and I still get problems. I must be missing a step somewhere along the way or not fully understand the cons of running custom ROM's or something.
I'm at my wits end. At one time I thought it must be the phone so I swapped with Sprint but I still have the same problems.
Currently I am running Scrambled EGgs22 V7 and I love it (when it works). I've tried bonsai, urban roms, you name it. Its the same results with every one. They work fantastic at first and then slowly become unusable.
Is there anybody out there who has experienced something similar to this and can help me remedy?
Click to expand...
Click to collapse
Kafluke said:
So I'm really struggling here. I hate using stock ROM's because the battery life really blows and they are slow.
That's about the biggest lie over stock.. I started with a custom rom and it sucked the world's biggest donkey balls on battery life. It can last me the whole day on EC05. Just gotta learn how to optimize bro.
SchizioPunk's Epic Experience 2.1 Eclair -> Odin to EC05 Froyo. Rooted. Bloatware Removed. Voodoo Sound V9 Module Loaded. TouchWiz4. Enjoying my Customized Stock Experience.
Click to expand...
Click to collapse
Run 'Fix Permissions' from Rom Manager. That has solved FC problems for me in the past.
Have you tried reformatting your SD card? If it has gotten mucked up, I imagine that could start causing issues.
justppc said:
Run 'Fix Permissions' from Rom Manager. That has solved FC problems for me in the past.
Click to expand...
Click to collapse
Dont forget clearing dalvik and cache does also. I'm assuming people think that'll erase their stuff but It doesn't.
Sent from my Epix 4G using XDA
So how do I turn on journaling exactly?
Kafluke said:
So how do I turn on journaling exactly?
Click to expand...
Click to collapse
Edit: there should be a zip file that came with Epicurean to enable journaling.
There I a zip file that you can flash. I'll look for it
Posted by Mr. Z's Epic 4G.
I can't win. I enabled Journaling and my performance and speed went to crap. I guess I either have to suffer through the crappy stock rom or deal with force closes and random crapiness with a custom rom.
Kafluke said:
I can't win. I enabled Journaling and my performance and speed went to crap. I guess I either have to suffer through the crappy stock rom or deal with force closes and random crapiness with a custom rom.
Click to expand...
Click to collapse
If you want to disable journaling then just make sure to never shutdown your phone improperly or drop it and keep good backups to restore from. I like to do a nand every 3 or 4 days then I can always do a restore advanced data only.
Sent from my SPH-D700 using XDA App
kennyglass123 said:
If you want to disable journaling then just make sure to never shutdown your phone improperly or drop it and keep good backups to restore from. I like to do a nand every 3 or 4 days then I can always do a restore advanced data only.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Did you try the stock EG22 leak? Thats what I use, deodexed from decadence with the plus kernal from chris41g. It performs well and is the best battery life I ever had.
Kafluke said:
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Click to expand...
Click to collapse
True, that is why your $400 device comes with stock ROMs that are RFS so none of these FCs happen unless a third party app is written poorly. If you run custom ROMs these are the chances and prices you pay.
A $2000 computer still requires regular backups for the very same reason.
Kafluke said:
Are you serious? I don't ever drop my phone or shut it down improperly. I shouldn't have to back up my phone and restore twice a week in order to have a working device.I should be able to use this 400 dollar device without restoring it every fourth day or charging it twice a day.
Click to expand...
Click to collapse
BUT! Your forgetting something: you paid $400 for a phone
which Sammy provided to you via the vender of your choice with a STOCK ROM preloaded which works that way they have wanted.
Now from the moment you came over to the dark side and preloaded a rom there are good things and bad things that come with the package and you can't blame sammy for them.
Also, this is the world of trial and error: what may work fine for 500 phones will not work sometimes with yours. Every part of your phone though it could of been made the same day and from the same batch of my phone, are different and this will make you have different results.
Keep that in mind, your in a world that pose much risk to your device, but that's the fun part! Taking the risk and rolling with it!
Sent from an Epic with 4G
I am running SFR 1.2 with journaling on and can get all day with 3 to 4 hours screen on time , no force closes or any problems and all the smooth and fast goodness that comes with the rom.
Sent from my SPH-D700 using XDA App
megabiteg said:
BUT! Your forgetting something: you paid $400 for a phone
which Sammy provided to you via the vender of your choice with a STOCK ROM preloaded which works that way they have wanted.
Now from the moment you came over to the dark side and preloaded a rom there are good things and bad things that come with the package and you can't blame sammy for them.
Also, this is the world of trial and error: what may work fine for 500 phones will not work sometimes with yours. Every part of your phone though it could of been made the same day and from the same batch of my phone, are different and this will make you have different results.
Keep that in mind, your in a world that pose much risk to your device, but that's the fun part! Taking the risk and rolling with it!
Sent from an Epic with 4G
Click to expand...
Click to collapse
I don't have any problems with the stock rom. I'd love to have a stock rom that doesn't blow on battery life.
I understand that there are risks and pros and cons with custom roms but I can't seem to get a custom rom that is stable in any way shape or form. I assume that its my fault because I don't see anybody else having the same problems.
I guess I'm just looking for some help in getting a "half decent" custom rom experience but I can't even get that far. Without fail, every time I load a custom rom I get force closes and random issues. Then I go back to stock rom and I'm charging after two hours of use. I can't win.
@mark8503 I'll give that stock EG22 leak a shot and see what happens.
Thank you for everyone's help!
@mark8503
I assuming this is the stock rom you speak of:
http://forum.xda-developers.com/showthread.php?t=1183558
and this is the kernel:
http://forum.xda-developers.com/showthread.php?t=1185221
Please confirm.
IMO, if turning journaling on slowed down your phone enough for you to notice, something went wrong
I've run the on and off zips, and the difference is hard to see
Also, since RFS has a journal feature, I can't see how EXT4 with journaling on would be slower, all other factors being the same
You want stable and solid, ODIN an EC05 modem, install SRF 1.2, do you voltage setting, and call it a day
If you want the bleeding edge, you just have to accept you need precautions, as on the edge, **** happens.
Pick your poison and go with it
This Epic post as brought to you via Tapatalk
5:50 pm and battery is awesome! So far so good, this deodexed stock EG22 is running great, no FC's, no random reboots and battery life is excellent with chris41gs kernel. I just hope I didn't jinx it.
I'll report back after a few days of use.