Related
one thing i've been curious about and haven't seen a thing on in any of the numerous impression/review articles i've read is a note on the the speed of the handset's boot up time.
i've got a droid now, and i absolutely hate how long it takes to transition from powered-off to operational. i go off and do something else, and it takes long enough where i've forgotten about it by the time it turns fully on.
so how long is the EVO's?
Probably because almost everybody leaves their phone on...and don't care how long it takes really...
1 minute or 5 minutes really don't bother most people including me, so thats why it isn't really said in reviews.
I think I saw somewhere where they said it was kind of long. I assume because of the startup animations. I don't know anything about rooting but from what i've gathered you might be able to disable some of those.
Bowhuntr11 said:
Probably because almost everybody leaves their phone on...and don't care how long it takes really...
1 minute or 5 minutes really don't bother most people including me, so thats why it isn't really said in reviews.
Click to expand...
Click to collapse
ok?
...and your point posting in this thread was? i don't care how many people leave their phone on, or the time frame that a phone needs to turn on in so not to bother people; i was asking how long the EVO takes to boot up. so thanks a lot.
In answer to your question... fast! Most boots seem to take about 20 to 30 seconds for me but one boot did take a minute. Regardless, it's faster than any Sense phone I have ever seen. throw AOSP on here and it should boot even faster.
awesome - appreciate the answer.
and yeah, i could imagine it powering up a bit faster with some tuning from xda.
I seen one IO user say his boot time on the Evo was less than a minute but I assume it also is a bare, non-custom, no extra apps device.
Boot time is definitely less than a minute, I'm using the HelixLauncher2 so everything comes up real fast after boot.
It's night and day compared to my old Hero.
I was just going to ask about this...
From fully OFF to the second I can see my lock screen(note, not fully operational yet, but can see the lockscreen), takes 1 minute and 20 seconds. Thats running Fresh 3.3 with whatever kernel comes with that Rom. A kid I go to school with, he has the same rom and kernel, his boots up to fully operational in about 45 seconds.
Just wondering if I can shorten that somehow.
Also, wondering if music and pictures have anything to do with it? Having to load all of that from the sd card might cause the delay?
Holy thread resurrection, Batman!
chazglenn3 said:
Holy thread resurrection, Batman!
Click to expand...
Click to collapse
Quick, to the archives Robin!!
Alright, I'm sorry lol. But you cant be THAT upset with me, I searched before posting. Just didnt take note of the dates. sorry!
jasongthang said:
Alright, I'm sorry lol. But you cant be THAT upset with me, I searched before posting. Just didnt take note of the dates. sorry!
Click to expand...
Click to collapse
I was just having fun and not neccessarily really teasing. At least you searched and this was the result so nothing too serious really
Same here...I wasn't busting your chops...just thought it was funny that you searched that deep...kudos on the search!
It's all good.
That, my lads, may have been epic.
Sent from my PC36100 using XDA App
Mine takes around....a minute and a half. This is with a 32GB microSD card, Apps2SD (with virtually every app I use, including most of the stock apps installed on my microSD, and dalvik on the cache partition.)
TheMagicalSock said:
That, my lads, may have been epic.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
ok... lad.. lol
freeza said:
Mine takes around....a minute and a half. This is with a 32GB microSD card, Apps2SD (with virtually every app I use, including most of the stock apps installed on my microSD, and dalvik on the cache partition.)
Click to expand...
Click to collapse
Where did yoou get your 32GB card from?
klbjr said:
Where did yoou get your 32GB card from?
Click to expand...
Click to collapse
Verizonwireless.com
My name is John (not really)... and I have a problem
I am a flashaholic....
Ok, but seriously, I would flash a different ROM every couple of hours if I could... but I've seen some people saying that it takes the phone a certain amount of time to "get used to" a new ROM/kernel....
So my question is this... If I flash a ROM and learn that there is something that I really cant live with.. battery life, UI, anything... how long should I give it in order to really know how it will be on my phone?... And yeah, I understand that there's not an actual number like "Wait 37.9 hours".. but can some of those people that talk about their phone gettin used to a ROM elucidate?\
And in the mean time.. I think I'll give CM7 a try...
I would say give it 37.9 hours. Any less than that and you don't give the ROM enough time to cozy up with your phone and if you wait any longer you run the risk of causing a nuclear holocaust.
_MetalHead_ said:
I would say give it 37.9 hours. Any less than that and you don't give the ROM enough time to cozy up with your phone and if you wait any longer you run the risk of causing a nuclear holocaust.
Click to expand...
Click to collapse
Has anyone told you that you're awesome today? cuz you are lol
Seriously, just wait 24 hours. After a reboot or 2, it'll settle. It also may be laggy at first, as it gets used to it.
elegantai said:
Has anyone told you that you're awesome today? cuz you are lol
Click to expand...
Click to collapse
You would be the first. For that, I tip my hat to you.
thanks, guys... you've been extremely helpful... really
nybdy else have a real answer... so as to help me avoid causing a nuclear holocaust?
Once all your apps are installed,synced, rebooted, and you've gone a full battery cycle or three. It should be as settled in as its gonna get.
Swyped from a galaxy far far away......
thanks....
I noticed that there would sometimes (50% chance) that there will be a noticeable 1 second delay when pushing the power button and when the display actually turns on. It's annoying because sometimes i'll want to check the time, and i'll push the button as i'm taking it out of my pocket only to be met with a black display still.
i tried turning off the pattern lock thinkng that was it but still having the same problem.
i'm completely stock.
No delay here...when I press the power button, my display comes on instantly.
tracerit said:
I noticed that there would sometimes (50% chance) that there will be a noticeable 1 second delay when pushing the power button and when the display actually turns on. It's annoying because sometimes i'll want to check the time, and i'll push the button as i'm taking it out of my pocket only to be met with a black display still.
i tried turning off the pattern lock thinkng that was it but still having the same problem.
i'm completely stock.
Click to expand...
Click to collapse
This had already been discussed id you remove your sdcard the delay will go away.
Sent from my SPH-D710 using Tapatalk
***** here about the 2 second loss of time in your life.. http://forum.xda-developers.com/showthread.php?t=1265716
Did you really just say 1 sec???? Lol really. If your Checking the time I doubt 1 sec is that annoying!
Sent from my SPH-D710 using xda premium
alnova1 said:
***** here about the 2 second loss of time in your life..
Click to expand...
Click to collapse
Still thread ****ting on every topic about the delay?
Its obvious why the delay doesn't bother you; you already have too much time on your hands.
Otherwise, it's an obvious flaw in the phone. Why don't you let other people worry about their own lives and how many seconds are wasted.
craigbailey1986 said:
Did you really just say 1 sec???? Lol really. If your Checking the time I doubt 1 sec is that annoying!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
1 second is annoying when YOU'RE used to the display coming on instantly.
thanks for the link, i'll check it out.
yes its terrible anyone have a fix to this yet
If it's because of the SD card, trying increasing the SD Card Read Ahead Buffer. It can be built into the kernel or changed with a few market apps, or even a script. It'll also make photos/videos/anything from the SD card load faster.
fadetobolivia said:
Still thread ****ting on every topic about the delay?
Its obvious why the delay doesn't bother you; you already have too much time on your hands.
Otherwise, it's an obvious flaw in the phone. Why don't you let other people worry about their own lives and how many seconds are wasted.
Click to expand...
Click to collapse
Aren't we touchy! As long as people keep making threads about it , yes I will still state my opinion on the matter just like you are...have a good day sir.
alnova1 said:
***** here about the 2 second loss of time in your life.. http://forum.xda-developers.com/showthread.php?t=1265716
Click to expand...
Click to collapse
That's what I was thinking, who cares. Now that I check mine has the same thing, I never noticed and I really don't give a **** to try and "fix" this.. lol
Sean-El said:
That's what I was thinking, who cares. Now that I check mine has the same thing, I never noticed and I really don't give a **** to try and "fix" this.. lol
Click to expand...
Click to collapse
Amen brother...
Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.
Sycobob said:
Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.
Click to expand...
Click to collapse
Agreed, especially since it's a 32GB card and it's transferable between phones...
Screen lags reminds me of pre-pay gas purchases.
The last 2cents always take forever to complete.
Sycobob said:
Isn't this forum built for people who want to get the most of their devices? If everyone just decided things were 'good enough' you wouldn't have devs here writing custom kernels and ROMs. If the issue doesn't bother you then don't bother posting in the thread. And if you absolutely must, don't be a douche about it.
OT: I noticed it too. This is my first smartphone, but it stood out. I assumed it was normal. It's not huge, but I definitely wouldn't mind a fix that didn't require abandoning my SD card.
Click to expand...
Click to collapse
This is your first smartphone and it stood out to you? I have had 15 smartphones and would have never noticed it until someone mentioned it. Like I said, I don't see this as an issue so I will speak my peace as you can to..we agree to disagree and just because we don't see it your way doesn't make us a douche....sorry for the loss of time in your life I'm...oh ****!...I missed the Andy Rooney farewell on 60 minutes because I couldn't get the time on my phone because it came up 2 seconds too late!
alnova1 said:
This is your first smartphone and it stood out to you? I have had 15 smartphones and would have never noticed it until someone mentioned it. Like I said, I don't see this as an issue so I will speak my peace as you can to..we agree to disagree and just because we don't see it your way doesn't make us a douche....sorry for the loss of time in your life I'm...oh ****!...I missed the Andy Rooney farewell on 60 minutes because I couldn't get the time on my phone because it came up 2 seconds too late!
Click to expand...
Click to collapse
It's not a HUGE issue, but it is something that should be fixed.
In fact, just to move things forward, I tried increasing the SD Read Ahead Buffer with an app "SD Card Booster" or some name like that, which doesn't decrease the speed of the screen coming on, but does drastically cause photos and other things to load faster when you, say, open the Gallery. That was expected though. We used to increase it on the OG Evo.
Ive owned a few smartphones noticed ET lag after 3rd wake up.
First thing I thought of was Sprint Blackberry curve 8330-M.
It did the same thing drove me crazy lol
I tell you what...take your phone back to Sprint and tell them you have a 2 second lag and see what they say...maybe you can get a new phone...its obviously a defect...
alnova1 said:
I tell you what...take your phone back to Sprint and tell them you have a 2 second lag and see what they say...maybe you can get a new phone...its obviously a defect...
Click to expand...
Click to collapse
Its not hardware defect....its software related thus Sprint will push you out the door no new phone in hand with chuckles from rep.
Will update to fix issue come?
Never! so those that think samsung gives a care you better think twice.
Oh I forgot,
My HP Ipaq 6515 had wake up lag with SD card as well
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
When you rooted did you NANDROID backup ? If not go into recovery and clear cache and then go into advanced and wipe delvik cache. reboot
If that fails go back into recovery and do a factory reset and you should be ok.
touchdownadrian said:
Well i think it is. I rooted my phone last night and installed the beats drivers from the Play Store. Shortly, it froze and went straight to the Samsung logo. I can still go into both recovery and download mode, but what do I do after that? I've heard about Odin....but how do i exactly put the custom roms into my phone, and which ones? And if any one can point me to a guide or tutorial, ill be extremely relieved. I'm new to the website as well as android, so if anyone could please help me out, thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1727401
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
I disagree as long as you are willing to learn from the mistake all is good. I had a Samsung Exhibit II and deleted touch wiz launched (I was using go launcher) later I would do a factory reset and well... learned that system files do not get restored when you do a factory reset...oops
Sent from my SGH-T999 using xda premium
I agree, we all were NOOBS at some point. That's the one thing I love about XDA is that with patience and the help of the users any noob can learn how to mod their devices. One piece of advice that I can offer is before you do any type of modding is READ and keep on READING. I have bricked the first device I ever rooted because I did not READ the forums as they are meant to be read.
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
not fair
z0phi3l said:
This is why noobs shouldn't be rooting, hell I'm on my 4th android phone and I'm still holding off on rooting it. And I was constantly popping new ROMS on my Vibrant, never bricked any phone
Click to expand...
Click to collapse
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
touchdownadrian said:
Thanks guys, it worked. And my bad for not reading alot, im kinda new to this lol
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
TheSeanTeam said:
It's not the noobs who shouldn't be rooting... It's the lazy and careless who should stick to stock. If you are careful and diligent, rooting and all the good stuff that comes with it is easy and rewarding.
Click to expand...
Click to collapse
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
lordazoroth said:
I whole-heartily agree, I was a freshman noob August 1st this year, by August 4th I was flashing like a pro. Left and right, ROMs, Kernels, Modifying system files, you name it. I wanted to streamline my phone and future proof it somewhat by overclocking. I spent 3 days researching and educating myself, finding the best ROMs, weighing pros and cons, and when it came time to flash, I was on my PC all day making sure whatever I did wouldn't brick me. I carefully analyzed and learned about virtually all methods of flashing by watching tons of videos and reading a bunch of tutorials by several sources. I MD5 checksum'd every zip to be flashed on my phone using an app (to ensure download and transfer was successful). I must have verified that the files I was preparing to flash were indeed for my device make and model about a dozen times before ever touching a button. When I went to flash over my first custom Kernel (even though I had already flashed 2 custom ROMs shortly before that), on that last button my hands were literally shaking, I could not afford a second Galaxy S III. Everything went beautifully, all of my careful planning and hours of invested research payed off. I had done everything right and was rewarded with better battery life (about +50% on heavy load and +500% on idle) and performance (+25%).
My girlfriend also has a Galaxy s3 and she wanted the same performance I was getting. I flashed the exact same software to her device I had to mine, no changes.
Total time invested in flash on my device: 36 hours, at least
Total time invested in flash on her device: 1 hour... if that
The bottom line is yes, if you're not willing to put forth the effort and educate yourself first, you probably shouldn't be doing this. There are guides and tutorials out there for noobs and I would recommend you go there first until you know your way around your device. That way at least you have a little experience on your belt before you start doing anything too advanced (I did this when I was rooting my device for the first time).
As a side note, I know there are a lot of people out there worried about doing anything that could potentially brick their device. That is always a real possibility, I'm not going to lie to you, it happens more often than you think. However in just about every case of bricking you'll ever hear about, it's usually someone flashing something they're not suppose to, like a ROM designed for a different make and model of device, or something experimental that wasn't ready yet. Do all your homework (from multiple corroborating sources) before you undergo a flash and as long as you do everything "by the book" (so to speak) and don't rush through things by being lazy, you should be fine. Some even flash nightlies (yeah they're called that for a reason, updated versions of the ROM they currently have) EVERY NIGHT!!! In the end when you have an android device, you have an open source platform at your fingertips and you should take advantage of that, it would be a waste not to. If not, your next device might as well be an iPhone. They're great for noobs and as long as you're ok drinking whatever punch Apple gives you, they're pretty much impossible to brick since you can't do a whole lot with them. Apple will be happy to take your money and stiff you with closed source for it.
Click to expand...
Click to collapse
Same here. It took me months of researching on my vibrant before flashing my first rom (bionix 1.6 by teamwhiskey). As I progressed, I did brick left and right but I always managed to bring it back to life with my prior knowledge. Now I'm eagerly waiting for my computer to be done downloading the root files and get started.
Sent from my SGH-T999 using xda app-developers app
Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Cr vibe said:
Dude the vibrant is bullet proof . Now HTC that's a mother.
:silly:
Click to expand...
Click to collapse
+++++++1 on that.... DAMN talk about headaches....
dmarco said:
Yea, not cool dude..remember that WE were all NOOBS at some point in time, therefore we should support and help one another. As for what to do next, follow "Saldebot's" instructions and you should be fine. Sounds like it's only a soft brick. Just keep reading and learning as much as you can bud.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
:good::good:
Yeah one of the only other IMPORTANT thinks i could add would be always do a factory reset before flashing roms.. some people like to flash "dirty" i wouldnt recommend it cause you will ALWAYS have issues maybe not in a hour but guaranteed you will... but knowledge is power dude.. i two read for about 36 hours before rooting my phone.. i rooted my wifes phone days after a rooted mine back in the day it only took like 15 mins.. another thing let phone sit 10 mins before ya play with it... gotta let the cache settle... the ten min wait is well worth it.. ive been doing it that way since the vibrant bro.. happy flashing and welcome..
I read constantly things change hourly like when that new leaked kernels came out for sgs2 and the emmc was trashed never to come back from a brick again. To anyone that cares if you love your phone read more than just the root and flash stuff learn what makes your phone tick from the factory hardware software and added crap from your carrier it all play's a part in the end result. Its as easy as you make it.
Sent from my SGH-T999 using Tapatalk 2
Nabeel10 said:
Omg I LOVED THE VIBRANT! Restoring it from a brick was a piece of cake
Sent from my SGH-T999
Click to expand...
Click to collapse
Ive passed down two vibrants (both rooted) to my sons so they can learn to flash roms and everything else that comes from the joys of root.
Sent from my SGH-T999 using xda app-developers app
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
On ParanoidAndroid 2.54 + franco.kernel r300. None of the problems you mentioned are present or has ever happened with me. Perhaps if you didn't mod your phone so much as to NOT be able to pinpoint a problem is where you went wrong.
Who knows? I surely don't. Don't know you but I don't think I'll be noticing your absence. Good luck with everything!
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Thats cool, you already tried your fair share of roms, if none of them worked for you the stock is the best with unsurpassed stability. Despite whats advertised about the nexus, the stock android firmware is excellent too, specially when you want something that just plain works.
Sent from my Galaxy Nexus using Tapatalk 2
Great story brother. Thanks for sharing.
Sent from my i9250
bk201doesntexist said:
Great story brother. Thanks for sharing.
Sent from my i9250
Click to expand...
Click to collapse
Keep coming..it works if you work it
Sent from my Galaxy Nexus
goodbye person ive never seen post before. hope you figure out your problems
Stock is the way to go, but you don't have to leave the xda because you no longer run a custom ROM. there is a lot of useful information that is shared here that doesn't necessarily apply to custom ROM.
I am also running stock rom from now on.
Sent from my Nexus 7 using xda premium
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I hope you really didn't write all of this from your nexus lol. But just go to stock...simple :thumbup:
Sent from my Galaxy Nexus using xda premium
I see how you feel abouyt this. I have had issues as well. It really stems from what Roms are and what we expect from them. The term Night lies have lost a little bit of its worry recently because they are fairly bug free. But that doesn't mean that little tweaks and mods aren't killing battery life and deteriorate over time due to bad patches and coding.
That said I would highly recommend checking out BuglessBeast. They are not night lies by any means. They are highly stable AOSP Roms that perform much better then anything else on the market. He has few commits aside from under the hood tweaks. Reboot menu, emoji and a slight few other things are it. I have never had an issue with them and recommend checking them out. Also they are pretty much the only VZW app compatible ROM. Peter has been building BuglessBeast since Eclair on the Droid1 (almost 3 years now). Always providing an excellent experience.
spjetrovic said:
Keep coming..it works if you work it
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Flashaholics anonymous?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Stock + root is the way to go for me on Nexus phones. On my last non Nexus (SGS3) I was always flashing new roms trying to look for something that just works, but I am tired of it. On my Nexus S and GNexus, stock rom is amazing, I don't need anything else.
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my frustrations with the Gnex. I unlocked and rooted on the first day and even though there wasn't much in the way of custom Roms with 4.0 I was excited to try all the different mods that were slowly flooding XDA and RootzWiki.
This wasn't my 1st experience with root either. I owned the Dinc and loved the idea of tinkering with my device. I learned a lot. Mainly that you should ALWAYS MAKE A BACKUP. and take the extra minute to wipe everything. I don't even use TI backup anymore because I wanted to start over from scratch any time I flashed a new ROM.
I say this because I know there are ppl in the forums that are smarter than I when it comes to Android. There are also some of those same ppl that will assume that I made some sort of noob mistake and I should try "wiping data" or something. Trust me, I've tried that and it doesn't fix it.
My main issues have been:
*losing data connection for no reason and eventually having to reboot in order to restore data.
*Weak network/WiFi.
Now I know there is a thread on rootz that addresses the bars and how inaccurate they are. But when two identical devices sit down in the same place and run speed test. My Gnex can slow to a snails pace at times. The wierdest thing about this is that it only seems to do it sporadically, which makes recreating it almost impossible. Although it seems most frequent at work, but that maybe because I spend an ungodly amount of time at my office.
*Lag/freezes
I know its not gonna work perfectly all the time and sometimes you have to reboot your phone just to give it a chance to reset itself and that's cool but when you do that and it doesn't fix the sluggishness of the phone then I feel there is a problem.
* problems with certain system functions like Bluetooth or GPS
Now this may be only an issue with particular Roms which may be known to have problems with certain aspects of the system. For instance, it seems pretty common from what I've seen on the forums that GPS is an issue for some on 4.2. I was actually on 4.2 this morning until I went to punch in an address from a text msg to Navigation and it wouldn't lock on my location. I got frustrated and decided to wipe and install the AOKP milestone I had saved and when I set everything back up guess what? Navigation still wouldn't lock on. I ended up having to bail out on some guys because I could find there house. I got home and found a stock ROM online. I wiped, flashed and setup my phone for the second time today. I downloaded Maps and immediately went to find the address and it was insane how fast it locked on a location.
There are other issues but I'm becoming long winded so I'll try to wrap it up.
Now I'm not one to dismiss my own part in my problems. I've certainly tried to address them when/if they arise with what little knowledge I have and the ability to learn what I can. I e emailed devs amd talked to others and sometimes it helps, but sometimes like this morning you just want things to work when you need them to without wasting your time having to revert to a nandroid or doing some other wizardry.
"Well, why don't you just go buy an iPhone then?" you might say
I've actually contemplated it but I do really like android, Google Maps are the **** (I depend on Navigation a lot )and I like to be able to customize. And I also don't really want to pay the money to terminate my contract so I'm kinda just stuck. But I thought about doing one thing.
A couple weeks ago, I unrooted and relocked my phone and flashed stock images for JB on CDMA and from there all I did was unlock and root keeping it stock and I tell you I glad I did because all my problems no longer seem to exist. My battery life might not be what I was getting on 4.2 these last couple days but I think I'm willing to stick with this for now until Verizon gets off their ass and pushes an update to us.
I'm not trying to rant to the Dev community or complain that y'all aren't living up to my satisfaction. Hell, maybe somebody might have a solution I haven't tried yet. I'm just putting this out there in case someone was having the same trouble and could get some help.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.
This phone runs very well with Stock+Root. I normally root devices because of different apps I like to use, and the ability to make custom backups...but I dont normally try anything bleeding edge...lol.
Partly because of my experience on an HTC phone...hated Sense and bought the GNex because of the AOSP.
akira02rex said:
I'm with this guy as well... I upgraded to a stock 4.2 rom (with root, but not a custom build).. and I have been smooth sailing since. It seems with all these custom roms and kernels there are nothing but issues. Sure, they're a TAD faster or offer little tweaks but when you need to use your device in the real world and it f*cking reboots while navigating somewhere because of a stupid tweak you made.. well, I can't see why it's even needed.
Click to expand...
Click to collapse
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2
negrobembon said:
No need to bash the custom roms that some devs here work so hard to make, i agree that stock is amazing but android would be a boring scene without the custom roms out there
We would just be like Ios, Wp and blackberry users, stuck with what we've got
Others wouldnt even have the chance to use a newer OS version because their phone has been abandoned by official support.
Or many of u guys would have crappy colors or other issues that custom roms and kernels DID fix
I use stock but i love the fact that there are custom roms around
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
No I get that, it's good to see support for older devices but c'mon have you counted the amount of 4.1.2 roms that are available for the gnex? If I build android I'm automatically called a developer? Because that's the way it seems here...
I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
I don't know why people keep bringing up the so crappy colors. In reality, the crappy colors are the ones custom ROM offer.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
its the kernels that offer the colors(the kernels that the ROM developers include too). of all the kernels available, only a very few distinguish themselves from the stock crappy colors.
This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium
automaddux said:
I've suspected for a long time that custom ROMs have been the source of all my...
Blah blah blah.....
Click to expand...
Click to collapse
No, please stay! We'll never survive without you! [/SARCASM]
GhoXt said:
This is ridiculous... who obligated you to install a custom ROM? F*cking emos.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Alright Captain, you keep Franco deep in your throat.
Sent from my Galaxy Nexus using xda premium