[Q] My newer evo seems to run a lot smoother - EVO 4G Q&A, Help & Troubleshooting

So... I got completely screwed over. I didn't know about this new hboot that's screwing people who want to root their phones. The glass on my phone cracked badly, so I used my insurance to get a new EVO. I kept on trying to use unrevoked on the new phone, then finally searches the forums to see the bad news; made me want to punch a baby.
Anyways, since the original sense is killing a part of my soul, I'm going to switch back to my old phone for the ten day grace period before I'm required to send it to the insurance company.
I did notice one thing however... This new phone is running really smooth! So I'm wondering if the phone got its hardware updated, or was it just my old device getting worn, or is my build what made my phone slower than this new phone. Any thoughts?
My old phone is running cm7.0.3.1, the latest bfs savages Zen kernel. Dunno... This new phone just runs like a dream.

Agree completely. I was on mikg 2.4 when I cracked the screen on mine. Got a new one and have no issues with speed or battery life.
If it weren't for screenshots and free wireless tether, not sure that id be anxiously waiting root.
Sent from my PC36100 using XDA App

Related

[Q] Insane Amounts Of Reboots (LONG post)

Ok this is a new problem for my phone. A couple weeks ago my phone started rebooting like crazy on CM7. I thought maybe it was the kernel so i switched it, that didnt work so i did a full wipe and installed the newest Nightly. That didnt work so i thought maybe it was Gingerbread (even though it ran it fine since it got cooked for the Inc) So i switched to an 2.2 AOSP ROM, that didnt work, so i switched to a Sense ROM. I have tried CM7, Skyraider, Magnolia, Business Sense Z, and now i am on Warm Z 2.2 and i am getting, no exageration, 15-20 reboots a day. No matter what ROM/Kernel combo i try. I also have the Battery Indicator widget in my notification bar that you can open and see what the battery temp is and i have never seen it hot. I can feel it rebooting in my pocket all the time. Phone calls make it reboot, music, navigation, all kinds of stuff. Sorry for being long winded, i just want to describe it the best i can. Does anyone know anything i can to to make it stop? Whenever i flash a new ROM i never restore Apps+Data, i only restore the APK's.
I called about a warranty replacement with the main reason being a blown external speaker, and they said they would do it. But here is why i havent. Somewhere along the lines VZW messed up something in my account and My Verizon online is telling me i am eligible for an upgrade even though im not. I called about it and she said i couldnt use my last NE2 untill Feb of 2012, then she checked the My Verizon and seen the same thing. She told me as long as i upgrade online or on my phone it will let me upgrade, but if i call in or go to the store it wont let me. Well i want the Thunderbolt with my upgrade, but i am afraid if i do a warranty swap it may affect my status on My Verizon somehow and not let me get that upgrade. I plan on selling the Inc after i get the Tbolt, but i dont want to sell it rebooting like crazy like this. Any input is appreciated.
I did the same with my HTC TP1 a week before i got my TP2 with the upgrade from VZW. I didn't have any problems.
Check setCPU or any app that would majorly change stuff on your phone. Such as ones that auto kill things. Turn all those off if you have any running.
You may just have bad hardware, in that case would suggest you going back to stock and advertising as such when you're selling.
Yeah i may end up taking a chance and doing a warranty claim.
I'am using CPU boost. You think that is causing it? It just started happening but i have been using the app for a while.
Sent from my Incredible using XDA App
Well I uninstalled CPU boost and that didn't help. Anything else to try?
Sent from my Incredible using XDA App
I've had this happen Verizon will replace it with a refurb. or at least they did for me...
Run the rru?
Sent from my LiquidLight using XDA App
Thanks for the suggestions guys. i think I'm going to take the chance on unrooting and getting a refurb for it. Hopefully it won't fix whatever error is in the my verizon system and take my upgrade away.
Sent from my Incredible using XDA App

[Q] How many are problem-free?

Hey everyone... this phone has gotten excellent reviews, and I was psyched to replace my tired Diamond with it until I saw all the problems people have been having with it (LOS, battery drain, gaming, etc.), especially considering it's Samsung. Thinking of getting a photon or 3vo instead, or just waiting it out for something better (yeah, i know it's always around the corner). But of course the people who have issues are more likely to post than those who don't. So how many of you actually haven't had major problems? Is this thing worth the risk? And does anyone know if TEP would cover this if the problems laid low until after the 14 day trial period?
No issues here. I came from the 3vo and photon, do yourself a favor and get the epic.
I have had it since launch day, no problems, in fact this phone is the only one that I have had that I haven't insta rooted... because it's just bad ass, I'm in no rush
I had no problems for 6 days till I rooted, then I had LOS 4 times the first day. Went back to stock kernel and now 2 days in no problems.
blahzace said:
No issues here. I came from the 3vo and photon, do yourself a favor and get the epic.
Click to expand...
Click to collapse
+1 same here. Well said. Treat yourself to the best mobile experience available
sent from my DAMN phone!
No problems yet either. haven't rooted yet but thinking about it...
No problem here...loving it..
Sent from my SPH-D710 using xda premium
I have LOS issue at least once a day, but mine can be fixed by going into airplane mode and coming out of it. Don't believe all the hype, this phone DOES have issues, but it's still a great phone.
Also, I would mention check out sprint's forums and android central to get a good overall view of the connection issues on this phone. It seems Samsung has once again released a phone with buggy modem software. It will get ironed out, its just a matter of when, be it 1 month from now or 6 months from now.
Just as a personal example, I get 300-400kbps less on 3g than my girlfriend gets on her evo 4g in the same exact spot, using speedtest.net app at the same exact time. I have repeated this test multiple times at various spots in my city just to confirm.
I hate to be a naysayer, I love the phone and don't intend on returning it. But keep that in mind, you will be getting a phone that is less than perfect on day one. Once we get an actual update and ruu from Samsung, then the real Roms and Kernels will start rolling out. For now, we are just playing a waiting game it seems.
skyward01 said:
I had no problems for 6 days till I rooted, then I had LOS 4 times the first day. Went back to stock kernel and now 2 days in no problems.
Click to expand...
Click to collapse
My experience as well.... may just be coincidence, but no problems while unrooted.
I love it when people post " I was fine until I rooted and then all these problems, what's wrong with the phone." Well duh have you ever thought it was your rooting.
Have had it since day one. No real problems to speak of. Some people are just way too picky. Talk with a non-geek about the phone and there is nothing wrong, talk with a geek and there are all sorts of nit pick. Honestly some of these people are so anal it makes me wonder. The Epic 4G Touch is a great phone with a lot going for it. Had a Photon and that phone had a lot of issues that prevented it from fulfilling it's most basic purpose, to send and receive phone calls. *ugh*
Ive had this phone since day one, haven't had a single issue with it. No LOS, no gaming bugs, no force closes, nothing. Battery life is nothing short of stellar, and overall performace is pretty much without parallel in the mobile world. This is easily the best phone in the us market right now and you'll be extremely happy with it should you decide to get it. I had an EVO 3D for a month and absolutely HATED it. Get the ET4G, you won't be sorry.
Sent from my SPH-D710 using XDA App
I have had the phone for 8 days now, I am impressed with the battery life, I leave it on wifi all day long at work and the phone roams with 1 bar of signal. This building is terrible as far as cell service goes. Even so, I leave work and my battery is ~ 40-50%. I usually unplug it around 4:00am and leave work at 5:30pm. I did get the no smoking circle yesterday but I was in the basement of our library, I'm pretty sure that wsa legit and my signal came back when I walked outside. This phone is running phenominal for me, it is by far the best phone I have ever owned or played with.
I went from: POS Crackberry (Curve 8320), MyTouch 3g, Samsung Moment, Evo Shift, E4GT
have the phone since day one, no problems at all. first smartphone that has no issues for me. and its fast.
Same for me. Unrooted zero issues great battery life super fast.
Sent from my SPH-D710 using Tapatalk
No issues here since purchase on launch day. Not one single LOS, good signal strength in the areas I frequent here in San Diego, respectable 3G data speeds by Sprint standards, excellent battery life, no unexpected heat, nothing.
14 days is tomorrow, so I'm expecting the thing to completely friggin explode on Saturday. I've never had a smartphone run this well out of the box. I'm a bit floored to be honest.
Get it. I'm coming from Evo3D (Evo and NS4G before that). It it well worth it. I haven't had an issue with it at all. It is the only phone I have had that I have not felt the need to root....yet.
No issues here save for a WiFi connection that dies every now and then, but I think it's an issue with my router.
Otherwise it's by far the best phone I've ever used. It just works.
Still stock, haven't found an overwhelming reason to root.
I have to agree with everyone, i have had like 20 different phones this year and all have been rooted the day i got them except this one, its just so damn fast, but i expect that will change omce cm7 is out for it
I've yet to encounter a single problem with this phone. First time I haven't been rooted within days of buying one too. It really amazes me that I'm satisfied with a smart phone right out of the box.
This phone has worked perfectly out of the box. So well that there's almost no point in rooting or modding it. Battery, GPS, connectivity, everything...
In fact, I didn't have any issues until I rooted it and installed a modded ROM. After that random LOS after resuming from sleep. Guess what? Returning to stock eliminated that problem. So the issues people are facing are from messing around and modding things not from the hardware or the stock software.
Anyway, now I'm on the stock kernel with root access without issues and I'll probably stay this way for a while until a nice stable rom comes along

[Q] Boot loop problem

Hi, I have a few questions I hope you can help me with?
My wife has a galaxy nexus, stock and unrooted. It is only around 6 weeks old and last week it started crashing, turning off then getting stuck in a boot loop just displaying the starting colours. I understand this is a known problem, she has software version 4.0.2 and it says her phone is up to date.
I "fixed" her phone once with a factory reset however this time she is away with work till Friday and now has no use of her phone or contractual minuets or data ect.
To make things worst she was planning on using the sat nav and wireless tethering to her laptop. It is the second time this has happened and she has lost all faith in her phone. She can maybe upgrade the software by downloading the 4.0.4 software but she/I don't see why she should have too. She just wants a phones that does what it says on the tin without needing to mod or mess around with it.
My questions are...
Is this problem enough for her to exchange the phone for another phone all together, she fancies a One X. Has anyone here managed to exchange the phone for this reason?
If not will updating the software to 4.0.4 fix the issue for sure? She really needs a reliable phone. Maybe it will be best to send it back under the warranty but we are afraid she will get another GNex with the same issue.
Any advice will be much appreciated
Sorry for the long post and thanks for reading,
Oliver
I would just try updating it and then wipe it. If that doesn't fix the issue it's most likely a hardware issue and I would warranty the phone.
Sent from my Galaxy Nexus using xda premium
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
omricn said:
Hey there,
Well first I would suggest calming down and not reverting to hardware issues just yet, Bootloops are pretty common, especially when using phones which were meant for the (a bit) more advanced user, it's advantage is also it's flaw, being a modding monster that it is..
And this is by no means a flame - but I wouldn't want my wife to have a GN for that exact same reason, yes - she knows about flashing roms and stuff, but she needs a reliable phone, that will work and do what she needs it to do and nothing more, as opposed to me, I like to mess around a bit with my phones (also not that much, I plan to stay stock with my GN).
To your question, I don't have any experience with RMA's but it maybe worth a try.
You also mentioned she fancies the one-x.. that means she wasn't really keen on buying the GN in the first place (I believe).. and also - and don't take this the wrong way - I think she\you don't really know what the GN is all about, this isn't a phone for everybody, I mean - it is, but it's a shame to see it fall into hands that do not appreciate it for what it is, think of it as a nice new Ferrari, sure - it'll get your wife to work But she is not going to the Nurborgring to time her laps with it.. she'll complain that once in a while the clutch is too sensitive and that she cannot count on the car to take her to work every day, and that she really fancies the new Volkswagen beetle... you get my drift
Also - I believe that flashing to the 4.0.4 will sort the bootloops, which usually has everything to do with the kenrel.
Best of luck!
p.s. All of the above is said in a humoristic way!
Click to expand...
Click to collapse
Thanks for your post.
My wife wanted to upgrade her htc desire to a faster phone with bigger screen, she loves android and Google products and the Google nexus seemed like the best choice at the time (b4 the one X was released) she loved the phone till now.
The phone has twice randomly gone into a boot loop and twice we managed to get it working again both times within the week. This has caused her to lose faith in the phone. I guess the update should fix the issue but it doesn't seem to be available on her phone just yet.
A basic phone would not be enough 4 my wife, as I said in my first post she uses it to connect her laptop to the Internet and as a satnav. Also she watches youtube videos (720p screen is handy here) and for facebook.
We never had any such issues with our desires. When my wife returns home we will update her phone via pc if it doesn't void warranty (I'm sure it won't ) and hopefully the issue will be fixed for good.
Sent from my HTC One X using xda premium
Sounds like our wives can get along my wify loves her htc desire hd! and to be honest, in my opinion in many ways it's much better than the sensation I had (stock).
And by what you described, if I was your wife (lol ) I'd also go for the GN.. I trust you know how to upgrade to 4.0.4, if you need any help just say so and I'll be more than happy to help
Also - from what I know upgrading will not void you warranty, you can simply lock the bootloader once you're done upgrading if you wish.
I really wish the bootloops will stop and that you wife will continue to enjoy her GN!
Hi again
I unlocked, rooted and installed Android Revelution HD 3.0.0 (based on 4.0.4) by mike1986 on her phone.
She is happy with her phone again.
Now it's rooted she likes the extra apps she can now install like AdFree.
I have a quick noob question though..
After installing the new rom her phone it said their is an update available. I understand that she should NOT accept over the air updates now she has a custom rom, and is that right?
Cheers, Oliver
Sent from my HTC One X using xda premium
Hey Oliver, sorry.. seems I didn't get subscription notifications on your reply...
anyway, she "can" download the update, but it will not install, it will simply give an error upon installation, the reason is the original files that the update needs to update are not there anymore, or they are but have changed, so it will just give an installation error.. that's the only downside to having a custom rom. me personally - I like mine stock at the moment
Just a quick update, I rooted, s- offed and install Arhd rom on my wife's gnex.
She says her phone is running faster/smoother than ever and has not restarted since. It's running great and she is happy again
Sent from my HTC One X using xda premium

I am currently Evo LTE coming to SGIII

I have been a EVO users for (2) years making the change to SGIII. I hope I am making the right decision. Couple of questions:
S-off obtainable?
Bootloader Y/N?
Battery Life?
Good Stable Rom?
Tell me what you guys think.
We don't need some soff because Samsung usually isn't a ****
Everything else hell yeah
Some things even hit this phone first
Hell I'm testing something for a guy that will be one of a kind once he shows it off
Sent from my SPH-L710 using Tapatalk 2
The bootloader on the SGIII is not locked (so the equivalent of S-OFF on the HTC bootloaders does not apply). You simply use the Samsung Odin tool to flash a custom recovery so that you can then root or install a custom ROM. It is very easy to do.
The battery life has been good in the two weeks that I have had the phone but of course it depends on phone usage. I can burn the battery down if I am using the phone constantly but with my normal usage it lasts considerably longer than my Evo did.
When I look around I do find some other ROMs around but I have not made that leap yet. I am just running rooted stock. There is enough of an adjustment for me coming from Gingerbread Sense to Samsung ICS. I have not felt the need to do anything other than simple mods at this time.
I came to the SGIII after being on the Evo 4G for two years... I was torn between the Evo LTE and the Galaxy SIII. The things that drove me to the SIII were: replaceable battery, 2GB RAM, USB OTG...
m20120 said:
The bootloader on the SGIII is not locked (so the equivalent of S-OFF on the HTC bootloaders does not apply). You simply use the Samsung Odin tool to flash a custom recovery so that you can then root or install a custom ROM. It is very easy to do.
The battery life has been good in the two weeks that I have had the phone but of course it depends on phone usage. I can burn the battery down if I am using the phone constantly but with my normal usage it lasts considerably longer than my Evo did.
When I look around I do find some other ROMs around but I have not made that leap yet. I am just running rooted stock. There is enough of an adjustment for me coming from Gingerbread Sense to Samsung ICS. I have not felt the need to do anything other than simple mods at this time.
I came to the SGIII after being on the Evo 4G for two years... I was torn between the Evo LTE and the Galaxy SIII. The things that drove me to the SIII were: replaceable battery, 2GB RAM, USB OTG...
Click to expand...
Click to collapse
Thanks for the update. I came for OG EVO to EVO LTE which I currently have but many problems have pushed me away. I did an (OTA) and brick my first EVO LTE. One thing that drives me nuts when i am in a call screen goes black. Non removable battery not a big fan either.
I will see tomorrow when I get my SGIII!!
S-off obtainable?
Samsung doesn't have S-On and S-Off but instead Locked and Unlocked. Unlike HTC's ****ty unlock, the samsung unlock fully unlocks your phone.
Bootloader Y/N?
There's a bootloader, but the place where you flash stuff like radio, recovery, etc. is in something called Download Mode. You can use an official samsung tool called ODIN to flash the stuff really easily.
Also every computer has a bootloader. A bootloader is what checks if all your hardware is working and initializes it when you start the device.
Battery Life?
Excellent. I can get 5 hours of screen on time. Similar to the Evo LTE.
Good Stable Rom?
All of the touchwiz ROMs are stable and good. They are all pretty similar so I'd recommend Blazer or FreeGS3.
If you want AOSP, Cyanogenmod nightlies are the best in terms of stability but AOKP and Paranoidandroid are still pretty stable. Keep in mind that none of the AOSP ROMs are stable, but are good enough for a daily driver. If you need stability, use touchwiz.
Wont regret it, my wife has an Evo LTE which i rooted (what a pain in the ass to get s-off) and the Gs3 feels way superior. Dev support for evo lte is not even close to the GS3. My previous phone was an EVO 3d and after having this phone no way im going back to HTC.
Sent from my GS3 on the **** network
That is exactly want I was hoping to hear. I am unrooting LTE as we speak and taking it back later today.
Thanks
Welcome to lag free world.
Sent from my SPH-L710 using Tapatalk 2
Derekao said:
That is exactly want I was hoping to hear. I am unrooting LTE as we speak and taking it back later today.
Thanks
Click to expand...
Click to collapse
I think you'll be a happy camper. Just make sure you don't root it the second you get it out of the box. Make sure you provision everything first and make sure your 3G connection is working. I jumped too quick and didn't have any data and had to call Sprint.
Check the Dev sub forum and you'll find videos by qbking that will guide you step-by-step on how to root your phone. It's a simple process if you have any knowledge in the subject at all.
Yep... I think if HTC wants to survive, they need to take a few lessons from Samsung. They need to give up on the control thing. They are gaining nothing by doing that.
edufur said:
Yep... I think if HTC wants to survive, they need to take a few lessons from Samsung. They need to give up on the control thing. They are gaining nothing by doing that.
Click to expand...
Click to collapse
I never thought I'd ever hear anyone say this! Back when I was suffering through my T-Mobile Vibrant (Samsung Galaxy S) days, I was firmly in the #neveragain camp. I couldn't wait to jump to HTC. Then sometime around a year or so ago, things started changing. First, I guess because of the success of the galaxy line in general, a lot of devs started working on the Samsung phones. The Vibrant still suffered, because it had horrendous GPS (still does to some extent) locks and Samsung wouldn't release either the source code or updates. But the open source community worked wonders. I think the Vibrant was possibly amongst the first phones with an ICS ROM - working ICS ROM. I have been using ICS since December on my Vibrant. It got the JB ROM almost 2 months ago - a stable daily driver JB ROM.
Even so, this was all the open source community with Samsung doing Jack. When I saw the specs for the HTC One X, I was sure I was switching to HTC. Then Samsung hired Steve Kondik and I'm sure he's had something to do with this, but Samsung suddenly started releasing source codes left right and center. As others have said, they never locked the boot loader in the first place and now with the same device on millions of phones (with very minor changes), they have the best of both worlds. But I was still determined to get the One X - especially when Sprint added a SD Card, a kickstand and a dedicated camera button. The display is phenomenal (the one place it totally kicks the S3's butt), but the non removable battery was giving me some pause. I spent some time in the HTC EVO LTE forums and started seeing the multi tasking problems and decided that with the 2GB RAM and the removable battery and the developer community, I was better off with the S3. On top of that, I think HTC went in the other direction. From a nudge-nudge-wink-wink co-inhabitation with the open source community, they went with locked boot loaders, slower releases of the source code.
I finally pulled the plug and decided to go with the S3 - although I must say, I did debate for 5 minutes whether I should wait for the Note 2.
I don't anticipate running any custom ROMS yet on the S3 that I'll be getting next week. But I'll definitely be rooting it and installing Nova launcher. If Samsung hasn't released JB by next month, I'll probably be using CM10. It's already very stable on my Vibrant. It's sure to be stable on the S3 in a month's time.
I wish HTC well and hope they come out with a good phone the next time I'm in the market for a phone.
Made the switch myself today after my 4th defective evolution lte..
Sent from my SPH-L710 using xda app-developers app
I had the evo lte for 3 days and could not get a 4g lte signal in my house. I never loose lte in my house with the s3
Sent from my bad ass Odexed Blue SIII
When I was due for an upgrade, well a line was eligible on my account, I was looking at going with the HTC LTE and decided that I wanted to be able to pull my battery so I didn't give it another thought. I upgraded from the S II to the S III, it was a good move. I had the phone for about 4 hours before I decided to root it and about a day and a half before I decided to put a custom ROM on it
I chose Team Sonic-FreeGS3 mainly because it has the same look and feel as the original stock with added tweaks.
I unplug my phone at around 7 am each morning and use my phone for email and text mainly while at work with some phone calls peppered in, when I get home usually around 530pm, I will have 75% battery life left. I'm very impressed with this ROM and it continues to get better and better. It's very stable and I haven't run into any issues with this ROM
You should check Motorola's policy. No single way to unlock bootloader :crying:
Next phone...definitely Samsung, maybe from Nexus line
Hey Derek, I came from the originals evo also. This has some keyboard lag at random times, and very minor issues, but hardly noticeable. Better than the new evo, compared to the old evo, this is heaven. Look at this, just from texting all day, kik, facebook, xda, and some web browsing and YouTube a little. But one thing I must warn you about, when you get it, at first battery life will seem to suck but it doesn't. You just happen to be going crazy with it not putting it down XD and downloading stuff and personalizing and all that. Screen on in the screen shot is total time on.
I sold my EVO 4G LTE and got a S3. Couldn't be happier.
Sent from my SPH-L710 using xda app-developers app
james33440 said:
I sold my EVO 4G LTE and got a S3. Couldn't be happier.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
why sell it? Its so new you can go back to sprint and ask to return it for the S3? XD
after reading this thread, glad I'm getting a s3 over the evo 4g lte!
ReapersDeath said:
why sell it? Its so new you can go back to sprint and ask to return it for the S3? XD
Click to expand...
Click to collapse
I used my upgrade for the iPhone 4S is why. Bought the EVO new for $549.95 from Sprint.
Sold the iPhone for $450 on eBay 2 weeks prior to the EVO release. I pre-ordered two. Sold one EVO for $350 and bought the S3 for $360 with an otterbox case of eBay. Couldn't pass that deal.
Sent from my SPH-L710 using xda app-developers app

Help is on the way. The State of our elderly Evo :(

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

Categories

Resources