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
I was just using the kitchen to do the port but that wasn't enough. I'm trying to learn just how to get a different rom to boot on the evo. I took the HTC Thunderbolt Gingerbread leak and the HTC Evo Gingerbread release.
So I used the kitchen first to take the kernel and everything it needed. Then I used Beyond compare to copy over information that differed between the 2 framework-res.apk files. I was able to boot to the Thunder Bolt screen w/ the lightning flashing. Then it went to the lock screen that said plug in your charger. A signal was never picked up. I dragged the lock screen down and that goes away but the screen doesn't change and is just froze with the battery lead flashing. This is the farthest I've gotten in weeks. I'm not sure where to go from here, I've never taken a crack at this before so I'm trying to learn.
JynxRD said:
I was just using the kitchen to do the port but that wasn't enough. I'm trying to learn just how to get a different rom to boot on the evo. I took the HTC Thunderbolt Gingerbread leak and the HTC Evo Gingerbread release.
So I used the kitchen first to take the kernel and everything it needed. Then I used Beyond compare to copy over information that differed between the 2 framework-res.apk files. I was able to boot to the Thunder Bolt screen w/ the lightning flashing. Then it went to the lock screen that said plug in your charger. A signal was never picked up. I dragged the lock screen down and that goes away but the screen doesn't change and is just froze with the battery lead flashing. This is the farthest I've gotten in weeks. I'm not sure where to go from here, I've never taken a crack at this before so I'm trying to learn.
Click to expand...
Click to collapse
I don't know because it could be hundreds of things wrong but start by running a logcat and take a look at what's wrong and troubleshoot from there.
Sounds like you've done the hard part and got it to boot, usually that's the part that people tend to have trouble getting done.
GOOD LUCK dude!
Hey I was just wondering if this was just me..but when i boot up the phone on the boot up animation as the colors are doing they're thing, it looks like the screen is a bit pixelated or as if it has oily blotches on the screen. I was wondering if that's normal with the phone or if like i should get it replaced. and than also with that..this is my second phone already..i exchanged my first one cause the usb connector wasnt working, would verizon exchange this one with no problem also?
Only in the boot animation? Are you sure it isn't supposed to look that way?
Yes, the boot animation is a bit rough-looking normally.
Sent from my Galaxy Nexus using XDA App
ah alright i wasnt sure if it was supposed to look that way or not..thanks for that merry christmas all!
it's normal, to made the boot animation smoother.
Hated to bump an old thread, but it seemed to be the closest hit.
Just got my GNex from Google Play today. When I turned on the phone for the first time, the animation discussed here appeared to be absolutely vivid and stunning - HD quality. It was quite impressive indeed.
However, after accepting the system update nag it appears grainy and closer to SD quality following the update. It's now feeding my paranoia about everything else I look at.
Other than that, I don't see any other screen issues other than the blue tinge when viewing from indirect angles.
Not sure what all the update did. Looks like I am running Android Version 4.04 and kernel version 3.0.8-gda6252b
Sound normal?
Rooted?
http://www.mediafire.com/?kfn1e6nvys663ar
Flash that.
If not...
You can open that .zip...find the bootanimation.zip
and adb push it to /data/local/bootanimation.zip
Jubakuba said:
Rooted?
Click to expand...
Click to collapse
Not rooted, but possibly heading in that direction. Just getting acquainted for now and making sure I don't need to send it back before I get too intimate with it.
Need to do some more forum searching and start sequencing out a plan. Thanks for your file link, I'll put it with my arsenal.
After flashing the file from the developement section, the NvCPLSvc.apk I noticed that the phone get very hot, specially the upper part of the phone.
Will see if the problem persist i will simply flash back to the original stock.
Anybody else notice this?
Cheers!
I can't say, I haven't done it.
Is the NvCPLSvc.apk something to do with Tegra 3 power management?
The-Last-Hylian said:
I can't say, I haven't done it.
Is the NvCPLSvc.apk something to do with Tegra 3 power management?
Click to expand...
Click to collapse
Yes that is correct I should have mentioned it before.
That was yesterday anyhow, will see how it behaves today kind of annoying that the new update is released today! Ahhhh! hehe, will do a comparison anyways.
Cheers.
First off the evo was officially released in june 2010. Only a few months till we are wishing our evo happy third birthday. Oh I have heard a rumor floating around that the Og Evo is one of the most active devices on XDA.
I have been a member here for a few years. I started with the cricket zio. Then the Og Evo, a 3vo for my girlfriend at the time, and then I fell victim to a boot loop of death. So back to my old a$$ Samsung Messenger II (I had already given the zio to my son as a music/media/911 device) till I could pick up another evo. Found a bad esn hybrid black front/white back og with no battery and seller stated vibration did not work. For $40 shipping paid. Thankfully I didn't sell my 3500 mA extended battery or mid-grade otter box case when I sold my first evo on ebay for $80. Remember it had bootloop of death and also a bad esn.
With some of our phones actually being three years old there are bound to be cataclysmic failures showing up. Over the past few weeks I have noticed a common problem spread out over the massive selection of roms we have. There was nothing really that the roms shared except for the fact that just this one person, never the same one that I can remember, would have this STATUS 7 ERROR during the flash causing the installer to abort. The first couple of times it came up I just passed it over as some wierd error due to something completely different than the real problem.
The following is from a the cm7 unchained thread.
Well with these problems popping up I have been thinking about implementing an old trick. You know about changing partion sizes. We can enlarge the boot and system partions and reduce the data size. We then use a2sd to make up for what we used on the other two. Now all I need to do is add the adjustment to the installer-script.
Although there is a side effect of this. When a different kernel is flashed it will not know how to read the partions. So then the user has to flash another script to change the partion parameters in the new kernel.
Now to shine a light on what the issue is that is causing what seems to be a random problem. The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Now with all rom flashing we do just takes another write cycle from the evos life. If we start digging further into the lives of our users we will notice two groups with issues. The older phones (from '10 or '11) and the addicted flashers/developers. Both of which have used up some of their lives testing and flashing.
True be told we can bandaid the evos memory with symlinks to the sdext till we only have the files needed to symlink everything else to the sdext. Only problem will be the transfer rate of sdcard.
Hope this was enlightening and informative. Also if you have not noticed I am working on the TNN Rom toolbox which will help everyone in finding a solving the problems as they pop up.
The thread is in general discussion but only gives highlights of what will be coming. I still have to write the install script to copy logcat automatically to the TNN folder and create a md5sum of the rom flashed. Now I will have to add in the partion adjustments and make a kernel fix script so different kernels can be flashed.
Peace,
Love, and
Happiness
Extra power for my development
Well I have recently lost my job which is why I have been able to get all the roms out so quickly and with very few if any bugs.
Then on a few days ago PlatinumPenguin tells me that he has a 3vo sitting unused in his desk drawer. He states that the Og Evo just sounds so much better than the 3vo on his headphones. Long story short he is packing up the 3vo and giving it to me. Talk about a nice guy. So I will move to the 3vo as my phone with service and have the Og completely free for developing purposes.
Then yesterday my buddy tells me that he has an Inspire that his wife wants to put back on att. The problem is that he dropped it and shattered the screen. Then got upset about it and threw it at the wall damaging the power button and volume keys. No power button no phone right. Well it just so happens that I know a trick or two. He hands me the phone and started to walk away. I quickly do my trick and power up the phone before he gets a few feet away. I tell him to watch this phone boot up. Trick is you take the battery out, connect the charger to phone and wall, and then reinsert the battery. B.I.N.G.O. Houston we have lift off.
Now he offers me his bad esn evo with shattered screen if I can replace the screen and get the buttons working on the Inspire. For those unfamiliar with the Inspire it is part of the evo family. It was an att phone almost exactly like the Thunderbolt except it has no ffc.
Now I have two Og Evo's to use for development purposes. Now I can flash two roms at the same time First I have to root the two new to me evos and an Inspire.
Then maybe I can get the TNN Toolbox written up on post 1. With a collection of other tips and tricks for our evo on post two.
Umm time to hit the rooting section of all three phone. It has been awhile since I have done the Og (hw003 latest update from sprint installed Nov '11) the second evo came rooted. I did the 3vo back around august of last year. It took me some time to figure out exactly how to do it. I didn't use the wire trick which had just come out for the 3vo.
Anyways stay tuned for more innovations from Team No Name. They will be coming to a server near you soon. Long live the Evo. Even if we end up running 90% of our roms from a symlinked sdext. Heck who needs internal storage anyways.
Peace,
Love, and
Happiness
Re: The State of the elderly Evo Hopefully help will be on the way.
Two
Look forward to this. Count me in to assist where I can. Still noobish as far as development but pretty savvy in regards to understanding how this works and a quick learner.
Sent from my Galaxy Nexus using xda premium
Re: The State of the elderly Evo Hopefully help will be on the way.
Oh wow I just powered up this bone stock evo 4.67.651.3. I am going to do a timed boot comparison but it sure looks like the stock one takes twice as long to boot.
It is kind of mind blowing to think that there really is that much difference between a stock and modded phone. They are both hw004 so I can use all my nands on both phones. Oh just so you know I had already booted my newly acquired evo a few time before I started both at the same time. No cheating since both already had a dc made.
Re: The State of the elderly Evo Hopefully help will be on the way.
This is almost like finding out my old EVO has cancer and the more I flash it the more the cancer spreads.
I've had my OG Evo since December 2010 (still stock and unrooted). I recently BOYD'd it over to Ting and bought my wife a used OG Evo off of Glyde. Hers I rooted (my first root ever) without issue and am running MBQsniper's Triple S. I am planning to root my device once I get all the bugs worked out of hers, get SMS copied over, etc.
So, needless to say, I've recommitted to the OG Evo at least until Sprint (and therefore Ting) kills wimax and maybe longer. I'm glad there are people around that are much more knowledgable than I that are still paying attention to this device. It's also funny how everyone seems to be from Texas...
jlmancuso said:
The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Click to expand...
Click to collapse
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..
NxNW said:
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..
Click to expand...
Click to collapse
True that. I had to go back to my original battery and it's stupid how bad battery life is.
As for the bad blocks, funny how 2 years ago, we believed you could write/re-write millions of times with no ill effects
Looks like you've been doing your homework brother,this looks to be promising.
Well actually most of the partition adjusting is old stuff. I just have to find a way to change the boot size. They were doing this back in the hero days.
Sent from my PC36100 using xda app-developers app
I am getting a status 7 error. Sucks, I loved my OG Evo
Sent from stock rooted Galaxy SIII
Status 7 error is a fail on installing boot image. I suggest removing the lines in the installer script for the boot.img and flashing a kernel separate. The use of a smaller kernel may solve the issue.
Sent from my PC36100 using xda app-developers app
Write cycles for NAND chips are in the order of 10k. Do we have fruity modders surpassing this number?!?
Wild!
0_o
Well lets look at it this way. 10,000 writes over 3 years (oldest evo) over 365 days and we have 9.13 writes a day. So while a 10k life sounds long it is over quicker than you think.
Hope this helped shine some light on the subject.
Sent from my PC36100 using xda app-developers app