Related
I loved this phone! LOVED IT..
but now, two major functionality points that I use daily are dead.
i've reloaded the factory Google img and no change.
3 days too late to return to Verizon store (might try anyway)
and now i have to deal with Samsung it appears..
i've read this problem alot and have yet to see a fix
anyone have a fix or experience with this?
Take it to Verizon anyways for a replacement.
Sent from my Galaxy Nexus using xda premium
Haven't heard any news of an ota to the gsm devices. Are they not getting it or am I not? I run a custom kernel and are rooted... but I have seen no news of a galaxy nexus ota.
Sorry if I missed the thread.
Thanks.
Sent from my Galaxy Nexus using Tapatalk 2
It's out on Google's factory image site. You can easily manually flash it
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
Thanks!
Sent from my Galaxy Nexus using Tapatalk 2
The OTA hasn't started rolling for any GNex devices. There's an image if you're on takju, but no OTA.
Nexus S ota lower memory use! Much better performance.
Just installed Jelly 4.1.2 on Nexus S device last night. I'm posting here to provide my experience. This phone is running like a new, better device. It is using half, HALF the sys memory than before. So far just sweet goodness. I recommend this update to all. Absolutely no problems thus far. I've tried things it didn't like in the past and it just keeps chugging along. I swear, EveryThing is faster. Will test batt life today when I go out, then report. This is only a .01 update! WOW! Thank you Google. Thank you T-Mobile. F'in awesome job. That is all.
I found a cwm that flashed system a while back and used that to upgrade to this version.
Sent from my Galaxy Nexus using Tapatalk 2
rdmoore said:
Just installed Jelly 4.1.2 on Nexus S device last night. I'm posting here to provide my experience. This phone is running like a new, better device. It is using half, HALF the sys memory than before.
Click to expand...
Click to collapse
Where are you getting that system memory number from? It sounds a little suspect.
Ya it is true. I have update my galaxy nexus to 4.1.2 and its is slightly better than 4.1.1
Sent from my Galaxy Nexus using xda premium
tofmiller... Very Slight exaggeration : )
I understand. This thing has what 334mb avail for apps to RUN not store. Before OTA update, was using task managers and restarts to keep around 50-70 mb free. After update, without intervention, phone says around 100 mb free. I exaggerated a bit but not that much. I find, also, the system keeps things freed up. I have not killed any apps or cleared cache since I got the OTA last night. I got the update in the afternoon then went to my 27" iMac to try to get a feel of how well things were going for others.Things looked sort of OK, but not much info so I decided to pull the trigger last night around 8pm Pacific. Proceeded to run it ragged. Streaming movies to my Mac via Wi-Fi, no problem. Played the only 3 games I have installed right now, no problem. Checked mem, 92 mb free! Made sure all apps were not running, only Skifta. It's been over 12 hours, no prob.
So, for me, this old dog got a shot of steroids. I'm thinking this will probably be last u/d for this device.(but that's what I thought about 4.1.1). If some app devs stay cool, don't think I'll get new device 'till after my contract fully expires. Was thinking about upgrading handset at earliest time. Couple months before end. Now... i can get better deal from carrier. Or jump ship to Big Red. Just wanted to put some helpful info out there because it looked like most people were side-loading this thing.
Been trolling for some time. Finally found something worthy of this outstanding site. Usually-"I'M NOT WORTHY"
Started with Nexus 1(now wife's) Bought rebuilt Nexus S because of running out of memory all the time.Pulled the T-Mobile Sim out stuck it in here and it immediately started d/l 4.04. Wow Really didn't expect that, now this... NEXUS BABY-- ALL THE WAY. Tablet next! Hope I helped. usually -I'M NOT WORTHY-
I'm on stock GSM 4.1.1 and I'm a little concerned I haven't gotten 4.1.2 OTA yet. Any ideas?
I thought the manual flash from the website wipes your data.
Mr. ruggersvpunk ? I can't believe i'm gonna say this....
Hello ruggervpunk ?
I'm usually (or used to be) quite impatient about these sort of things. I've been using a Mac since 1986(not the same one : ) and had to have the latest greatest thing. Over time I've learned a tiny bit of patience. I've found in almost every case it's best to wait a bit.. Smarter to let those without some restraint be the guinea pigs. This has saved my ass in recent years. So, I guess I would advise you to wait for the OTA. Things can go wrong when loading from a website. I've done it(with my wife's phone) and once I thought i bricked it. If not for the Grace of God and this site, it would still be in that state.
So sir? Try to wait. 1 it's totally worth it , I don't know who your carrier is but if you've received an OTA before, you'll get it again. Just got mine yesterday from T-MOBILE. So far, everything works better. Much better than an unexpected .01 update. This has done as much or more in performance than 4.0.4 to 4.1.1. Really. Give it a couple of days. Good things come to those who wait. That's just a guy in S.F. who loves gadgets advice.
Good Luck
Richard
It rolls out in phases. The factory image will wipe data. But there is a cwm file that updates boot and system. Its essentially the ota except larger since its the entire system.
Sent from my Galaxy Nexus using Tapatalk 2
rdmoore said:
Hello ruggervpunk ?
I'm usually (or used to be) quite impatient about these sort of things. I've been using a Mac since 1986(not the same one : ) and had to have the latest greatest thing. Over time I've learned a tiny bit of patience. I've found in almost every case it's best to wait a bit.. Smarter to let those without some restraint be the guinea pigs. This has saved my ass in recent years. So, I guess I would advise you to wait for the OTA. Things can go wrong when loading from a website. I've done it(with my wife's phone) and once I thought i bricked it. If not for the Grace of God and this site, it would still be in that state.
So sir? Try to wait. 1 it's totally worth it , I don't know who your carrier is but if you've received an OTA before, you'll get it again. Just got mine yesterday from T-MOBILE. So far, everything works better. Much better than an unexpected .01 update. This has done as much or more in performance than 4.0.4 to 4.1.1. Really. Give it a couple of days. Good things come to those who wait. That's just a guy in S.F. who loves gadgets advice.
Good Luck
Richard
Click to expand...
Click to collapse
Go figure, I sent that on the way to the gym, and when I just got home now, the OTA came.
Thanks!
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
I bought an unlocked Note 2 in the summer of 2013.
I happily used it until Christmas when it 'disappeared' in our house. My toddler daughter had hidden it somewhere.
Despite turning the house upside down it was never found and I reluctantly moved backwards to older phones I already had.
Nearly 2 years later and a builder found it hidden away in our spare room.
I know have my phone back which has been in hibernation for 18 months. It is running 4.4.1 and my question is this.
Despite it now being old I would like to upgrade the firmware to the best I can for the device without it slowing down. Please can someone recommend an upgrade and where I can find it. Phone is not rooted so will I have to do this?
Thanks in advance for your time.
There is no 4.4.1 for the note?
Sent from my SM-N910C using XDA Free mobile app
tomhirvin said:
I bought an unlocked Note 2 in the summer of 2013.
I happily used it until Christmas when it 'disappeared' in our house. My toddler daughter had hidden it somewhere.
Despite turning the house upside down it was never found and I reluctantly moved backwards to older phones I already had.
Nearly 2 years later and a builder found it hidden away in our spare room.
I know have my phone back which has been in hibernation for 18 months. It is running 4.4.1 and my question is this.
Despite it now being old I would like to upgrade the firmware to the best I can for the device without it slowing down. Please can someone recommend an upgrade and where I can find it. Phone is not rooted so will I have to do this?
Thanks in advance for your time.
Click to expand...
Click to collapse
Good news that you found your phone. Probably your firmware is 4.1.1 and not 4.4.1 because 4.4.1 not exist and also you have to update this firmware immediately because of sds bug. If you don't know about it Google it. There are plenty of roms at forum and also plenty of instructions how to flash a custom rom and also how to update at latest official if you don't prefer custom.
Sent from my GT-N7100 using Tapatalk
Thanks for your reply Vagsvag. Just checked and it's running 4.4.2. I think it automatically upgraded something when I turned it on and logged in for the first time (sorry I'm not very savvy). In your opinion will this suffice or is there a newer platform I can safely download. I did a cursory bit of research on Google and it looks like 'Android L' is the last one offered for the Note 2, but I couldn't see if it was ever confirmed. I'll do some more research on here. I'd rather not load up a custom rom as when I did that to my last phone (S2 and the Lite'ning Rom) the phone became very glitchy. Perhaps things have improved in the last 5 years.
tomhirvin said:
Thanks for your reply Vagsvag. Just checked and it's running 4.4.2. I think it automatically upgraded something when I turned it on and logged in for the first time (sorry I'm not very savvy). In your opinion will this suffice or is there a newer platform I can safely download. I did a cursory bit of research on Google and it looks like 'Android L' is the last one offered for the Note 2, but I couldn't see if it was ever confirmed. I'll do some more research on here. I'd rather not load up a custom rom as when I did that to my last phone (S2 and the Lite'ning Rom) the phone became very glitchy. Perhaps things have improved in the last 5 years.
Click to expand...
Click to collapse
4.4.2 is the latest official, for newer version of Android you must go to custom rom, cm or aosp, there are also some roms transfered from official s3 firmware android version 4.4.4. My opinion is if you are ok with speed, response etc stay with this only root it to remove junk apps and block the ads. Now if you want something little bit more fresh you can try cm base, one of the more stable is Ivan_Meler's cm 12.1 at original android forum.
Sent from my GT-N7100 using Tapatalk
Thank you for all your help. I've rooted the phone which seems to make everything quicker. I'll stick with 4.4.2 for now but will have a look at CM12.1 at some point.
Ivan Meler CM 12.1, Best ROM so far. Whenever you plan to get in the CUSTOM ROM Zone !!!
I found this link to a class action lawsuit. I think that has to do with all the thread I have been reading about ever since my wife's Note 4 started to freeze, reboot and just die several times a day.
http://www.classlawdc.com/2017/04/25/investigation-samsung-galaxy-note-4-mmc_read-failed-defect/.
At first I thought it was a battery problem. When a fresh aftermarket battery and a factory reset didn't fix the problem, I thought it had to be the new OTA updated andriod 6.01. After reading many of the thread regarding the impossibility to downgrade from QG1 6.01 to any of stock older ROM on ATT SM-910A I resign to use the band-aid (wake-lock app) to keep us from buying a new phone. Then, out of curiosity, I sift through the Galaxy Note 4 forum and found this thread (https://forum.xda-developers.com/note-4/general/emmc-class-action-lawsuit-t3678249) and I now understand that this was a hardware problem that may have been intentional or at least overlooked manufacturing defact. That explains the reason this problem shows up different times beginning from late fall of last year to my problem last week. And why some of the people who took their phones to Samsung repair centers and had the motherboard replaced for about $70 had their phones fixed properly. I hope this answers many of the that was asked on many other thread.