Related
Issue: \data partititon become corrupt for no obvious reason.
Manifests itself through: Freezes followed eventually by (endless) reboots
When: Randomly when you install new apps (may be every day as it can happen only every other week/month), or setting up apps (like Twitter, mail, etc)
Temporary solution: Re-flash Samsung FW but lose ALL YOUR DATA. Attention: CWM restore will not fix the problem!
---- Here goes a link to the fabulous mskip's tutorial, you will find here everything you need to get it back up temporarily
I experienced this in 401, 402, 403 and 404, some were expecting better data integrity in 404... I confirm this is not the case
I would not go as far as saying that this is 100% the reason, but it looks like the NAND quality is craaaaaap! There is no external SD card, Android should be able to do a perfect job now at handling info and preserving quality of data.
I will contact Samsung and ask for a refund (if at all possible)... Disgusting thing to put such a piece of s''t on the market without proper testing and call it "flagship/pure Google experience". This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Any advice, I am inetersted, have tried pretty much everything so far and did not solve the problem...
DO YOU HAVE THE SAME ISSUE? Let your voice heard...
DO YOU HAVE THE SAME ISSUE?
Click to expand...
Click to collapse
No. Could it be possible you're overreacting?
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Agree as well ..seems more like rubbish
Sent from my Galaxy Nexus using xda premium
David Horn said:
No. Could it be possible you're overreacting?
Click to expand...
Click to collapse
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
KWKSLVR said:
Umm, sounds like you need a replacement phone.
Deep breath....deep breath.
Click to expand...
Click to collapse
Right While i'm catching my breath, found another thread pointing to the same issue IMHO (didn't not see it initially):
http://forum.xda-developers.com/showthread.php?t=1490815
Attempting to contact Samsung already...
vulpy said:
Thanks David, you're of great help :/
Overreacting? Glad you had a better sample, I bet you would "overreact" as well if you spent 500£ on a piece of junk losing all you data on a daily basis.
But hey, this is not happening to you, right ?
Community means lots of people, some are here to help, others just looking for a social life while trolling on this forum.
Sorry mate, I am trying to get through to the first category...
Click to expand...
Click to collapse
Your first post came across as a hysterical rant - this is the first I've heard of the problem so it's not affecting many phones, and ultimately Samsung are going to have the occasional dodgy NAND chip. Sounds like you got one.
If you'd had several phones and they'd all exhibited this problem you'd be right to be peeved, but it simply sounds like you've been unlucky and are pissed off about it. Have you even discussed it with Samsung's tech support or taken it back to the shop you bought it from?
And accusing an XDA recognised developer of trolling is not a great start to your time here.
I've not heard of other people having this problem with the Gnex? Who are these other people having this same problem? Maybe speak with them and see if a replacement phone might solve the problem. I really hope you can get this fixed and not give up on such a great platform.
Sent from my Galaxy Nexus using Tapatalk
vulpy said:
This is not an isolated issue, it happens to at least half of the people around and the others may have not seen it yet (it all depends on how often you manipulate data on the phone)...
Click to expand...
Click to collapse
The burden of evidence is on you bro. That is a pretty bold claim.
David Horn said:
...And accusing an XDA recognized developer of trolling is not a great start to your time here.
Click to expand...
Click to collapse
Respect for your dev background (haven't used any of your ROMs yet), in all fairness I'm far less impressed with your communication skills... I must agree though, my message may have come across as too abrupt and you're right again, I am going to sort it out with Samsung...
Did not mean to get people horrified, rather to blow the whistle on a worrying and annoying bug and smth people may consider if they come across or consider a purchase.
For having worked in the mobile comm semiconductors space for years, I know just what sets apart a serious company from a me-too profile. Surprised to see Samsung having this king of issues. Normally they are ironed out easily though SW regression tests and HW stress processes (at least at serious OEMs).
I will let one of the moderators judge if my crime is so serious, your ego will survive, I'm sure I will come back when/if issue solved (or in good progress).
yeah, mine is fine. If it was a widespread problem I would back your corner, but I seems rather isolated. Rather then cause mass hysteria I would say you need to return your handset
Sent from my Galaxy Nexus using XDA
This happened to mine. But only once.
Quite frustrating, as my phone is my alarm clock and it was bootlooping when I needed to go to sleep!
However, a reflash of the 4.0.2 stock images sorted it out, and no problems since. I'm pretty sure I caused it by pulling out the battery at some sensitive point in a reboot or something.
If this happens to you frequently, then you need to exchange your phone.
Also, I think this could be a pretty good resource as opposed to a rant if you put your mind to it. I'm not a developer, but I'm also not a total n00b, and it took me a little while to figure out how to fix the problem, when I had it. I'm sure there are people out there who would appreciate a guide.
In this thread, op is going through that time of the month, when was his own modification back fires in his face, his explosive emotions reek havoc on an online forum.
If you want to see a device with bad nand memory, see the HTC Desire S forum .
Also the reboots and freezes I used to experience on my device were application related. Device hasn't frozen, nor rebooted in about *looks at up time* .. 27 days .
adrynalyne said:
The burden of evidence is on you bro. That is a pretty bold claim.
Click to expand...
Click to collapse
... I was actually referring to a poll in another thread (link in this thread) concluding that half of the people who answered have experienced freezes and reboots... it may be biased somewhat by the fact that people who experienced the issue are more likely to vote than those who didn't... maybe an overstatement from me.
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
First I heard about this too. I've flashed tons of roms and mods and constantly installing uninstalling apps.
The GNex has been anything but non-stable. I think I've had to pull the battery once or twice since ownership. Never heard anyone complain about randomly losing all their data... especially not daily. Perhaps on a bad flash in CWM.
Maybe you should look into a super wipe that completely erases everything, deletes the partition tables and recreates everything from scratch. Maybe it'll help but it honestly sounds defective.
Sent from my Galaxy Nexus using xda premium
Thanks Player911... Interesting idea, was thinking as well to do a total wipe and sort of a sector-by-sector reformat, but could not find a way of doing it. Is there any tool that would allow me to do it? Maybe this will isolate bad sectors...
Will check shortly with Samsung folks, thanks mate! (what slows me down is the fact that I'm currently travelling to the US and the guarantee is only European and it's Sunday= hotline is closed in Europe).
daern said:
Get the odd reboot (Chrome seems to provoke, strangely) but zero data corruption in 3+ months of heavy use. (4.0.3 AOKP)
Sorry, no endemic fault that I can see here (from reading these forums) and if I were you I'd be looking for a warranty replacement. Refund will depend on your location and supplier and duration of ownership.
Daern
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Uhh, I don't believe my reboots are due to this. Just saying. That whole thread does not point to your theory as the issue. I'm gonna go ahead and call this myth busted and suggest you go get a replacement because this is just another extremist "my phone is busted but I refuse to get a new one" thread.
Sent from my Galaxy Nexus using xda premium
You've been Samsunged
Sent from my Galaxy Nexus using xda premium
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
Basically, I was wondering where we stand in terms of perfectly stable 4.4.2 AOSP builds. I have seen posts saying that there are issues with the LS980 variant in particular, and I am a bit uneasy where we will be down the road, not just for KitKat. Basically, will we get screwed and not be able to go further unofficially(because I fully expect LG to not update past 4.4.X, because it's LG)? I see builds being attempted with 4.4.2 source, but apparently the LS980 will not boot on the newer source. I am contemplating switching to a Nexus 5, as I find myself using AOSP exclusively, but the G2 is better in almost every conceivable way. It's been awkwardly silent for a couple weeks now, so any updates to report? I'm not looking for an ETA, just a possible confirmation of progress. I just want to know if I need to entertain the idea of getting a N5. :silly: Thanks!
Koopa777 said:
Basically, I was wondering where we stand in terms of perfectly stable 4.4.2 AOSP builds. I have seen posts saying that there are issues with the LS980 variant in particular, and I am a bit uneasy where we will be down the road, not just for KitKat. Basically, will we get screwed and not be able to go further unofficially(because I fully expect LG to not update past 4.4.X, because it's LG)? I see builds being attempted with 4.4.2 source, but apparently the LS980 will not boot on the newer source. I am contemplating switching to a Nexus 5, as I find myself using AOSP exclusively, but the G2 is better in almost every conceivable way. It's been awkwardly silent for a couple weeks now, so any updates to report? I'm not looking for an ETA, just a possible confirmation of progress. I just want to know if I need to entertain the idea of getting a N5. :silly: Thanks!
Click to expand...
Click to collapse
UMMMM what???? cm11 works great!
Robisgnarly said:
UMMMM what???? cm11 works great!
Click to expand...
Click to collapse
Sure, except for the poor audio quality, random reboots, system lockups, GPS issues, some apps not working with touchscreen, etc.....
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.
Koopa777 said:
Sure, except for the poor audio quality, random reboots, system lockups, GPS issues, some apps not working with touchscreen, etc.....
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.
Click to expand...
Click to collapse
had better audio quality on cm11 than stock 4.2.2, my phone never randomly rebooted, never locked up unless i caused it..... never had these issues.. so i guess i was one of the lucky ones?
Koopa777 said:
Sure, except for the poor audio quality
Click to expand...
Click to collapse
nope, sounds identical here.
Koopa777 said:
random reboots
Click to expand...
Click to collapse
once every two weeks or so when an app locks up is not "random reboots" and 100% not the fault of CM11
Koopa777 said:
system lockups
Click to expand...
Click to collapse
see above, 100% BS statement.
Koopa777 said:
GPS issues
Click to expand...
Click to collapse
already multiple solutions posted for that:
1: put it in 3g only mode
2: set it to "device only"
Koopa777 said:
some apps not working with touchscreen, etc.....
Click to expand...
Click to collapse
Got any proof of that? everything's been 100% working here. Even FM works great with Spirit 2.
Koopa777 said:
So yeah, except for all AOSP ROMs being completely unstable and borderline unusable, they're pretty solid.
Click to expand...
Click to collapse
Summary: go away troll, not unless you have proof of anything you say.
Fnord12 said:
nope, sounds identical here.
once every two weeks or so when an app locks up is not "random reboots" and 100% not the fault of CM11
see above, 100% BS statement.
already multiple solutions posted for that:
1: put it in 3g only mode
2: set it to "device only"
Got any proof of that? everything's been 100% working here. Even FM works great with Spirit 2.
Summary: go away troll, not unless you have proof of anything you say.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2474887
http://forum.xda-developers.com/showthread.php?t=2601467
http://forum.xda-developers.com/showthread.php?t=2630977
http://forum.xda-developers.com/showthread.php?t=2485088
http://forum.xda-developers.com/showthread.php?t=2677295
From a well-known dev:
"Like most kitkat roms actions from superuser / power up bluetooth *can* cause lag until you screen off and on.
D802 and VS980 have reboot issues like every other rom. Please do not report this or ask other users if they also get them, its a well known issue." - dr87
Audio issues can be found in literally every single ROM thread, I wasn't wasting more of my time finding quotes.
Every AOSP ROM has these issues, period. Whether or not you get them is a roll of the dice, but saying they don't exist shows how out-of-touch with the community you really are. Maybe try learning about the device you use, and know what you're talking about before you attack other members of the community. If I'm wrong fine, tell me I'm wrong, I'll respect and understand that. But when 5 minutes of searching generates all that "proof", much less what has been documented since August, it shows that you clearly would rather attack others than educate yourself.
Robisgnarly said:
had better audio quality on cm11 than stock 4.2.2, my phone never randomly rebooted, never locked up unless i caused it..... never had these issues.. so i guess i was one of the lucky ones?
Click to expand...
Click to collapse
It depends, LiquidSmooth has been stable for me recently, I got two freezes 2 weeks ago, but none since. Touch screen is borked for certain apps on all AOSP ROMs though, regardless. All ROMs have these issues, but it varies on the severity. I have personally never had stable GPS on ANY AOSP ROM since I got the phone on release day(November 8th), and I've tried every ROM available for the LS980.
These issues are supposed to be fixed in newer ROMs incorporating 4.4.2 kernel source, but the LS980 is struggling to boot said source, from what I understand. Check out houstonn's PA 4.0 or dr87's Mahdi, both are testing builds with newer source, and all these issues are apparently fixed. :good:
Koopa777 said:
http://forum.xda-developers.com/showthread.php?t=2474887
http://forum.xda-developers.com/showthread.php?t=2601467
http://forum.xda-developers.com/showthread.php?t=2630977
http://forum.xda-developers.com/showthread.php?t=2485088
http://forum.xda-developers.com/showthread.php?t=2677295
From a well-known dev:
"Like most kitkat roms actions from superuser / power up bluetooth *can* cause lag until you screen off and on.
D802 and VS980 have reboot issues like every other rom. Please do not report this or ask other users if they also get them, its a well known issue." - dr87
Audio issues can be found in literally every single ROM thread, I wasn't wasting more of my time finding quotes.
Every AOSP ROM has these issues, period. Whether or not you get them is a roll of the dice, but saying they don't exist shows how out-of-touch with the community you really are. Maybe try learning about the device you use, and know what you're talking about before you attack other members of the community. If I'm wrong fine, tell me I'm wrong, I'll respect and understand that. But when 5 minutes of searching generates all that "proof", much less what has been documented since August, it shows that you clearly would rather attack others than educate yourself.
Click to expand...
Click to collapse
lessee here:
link 1: not AOSP or CM11
link 2: an uber *tiny* minority that could just as easily not like 4.4.x
link 3: very old thread, doesn't reflect current CM11 roms
link 4: not relevant, this is the sprint section and I see almost no CM11/AOSP mentions there. Last AOSP mention was in December... aka: doubly not relevant
link 5: very not relevant as that's a VZW G2 and not a sprint one. (this is the SPRINT section afterall) Doubly not relevant due to mentions in the thread you linked to mentioning the vzw G2 is the crippled version.
aka: go away, troll.
Fnord12 said:
lessee here:
link 1: not AOSP or CM11
link 2: an uber *tiny* minority that could just as easily not like 4.4.x
link 3: very old thread, doesn't reflect current CM11 roms
link 4: not relevant, this is the sprint section and I see almost no CM11/AOSP mentions there. Last AOSP mention was in December... aka: doubly not relevant
link 5: very not relevant as that's a VZW G2 and not a sprint one. (this is the SPRINT section afterall) Doubly not relevant due to mentions in the thread you linked to mentioning the vzw G2 is the crippled version.
aka: go away, troll.
Click to expand...
Click to collapse
I was going to continue to defend, but then I thought, "why?" I'll leave you with something equally irrational.
"Walrus pancakes taste good with maple syrup."
Blocked.
Been using my phone consistently for 24 hours. No root. Set it down after a messenger message, and couple seconds later, random rebooted. When it came back up, the gesture pill was flashing. Rebooted properly, and no more flashing. Weird. Anyone been having this?
There are several threads on the topic, and yes it seems to be quite the widespread issue. Some where able to fix this by doing a factory reset WITHOUT a backup from another device, some (like me) needed a replacement device.
We still do not know if its a software or hardware issue, or if these are two separate issues that are similar in symptoms but differ in cause (hardware failure/bug caused reboot & software/backup problem).
I'd suggest you either contact Google and get a replacement immediately or try a factory reset and manual setup (I assume you copied over your files from another phone?).
Wow, that is unsettling. Yes, I copied from an S21U backup. I've only seen this once so far, how extreme does it get? I searched before posting but did not see any discussions. I will look more. Thank you.
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Have you tried a factory reset, then not restoring from backup (or if you did a cable backup/restore, try a cloud restore instead)?
I hate to suggest it because I restored my Note 10+ cloud backup with no issue, but enough other folks have suggested factory reset and not restoring a backup at all. Worth a shot. Good luck, whatever route you take.
pre4speed said:
Replacement device ordered. More issues arose beyond the reboots, slow charging (6 hours from dead!), apps crashing, settings crashing, wifi issues. I love the phone, but not these issues from a 1k phone!
Click to expand...
Click to collapse
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
Ugh, I am not liking hearing that. First pixel phone.
pre4speed said:
Ugh, I am not liking hearing that. First pixel phone.
Click to expand...
Click to collapse
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
TrustAugustus said:
That is some bad luck. Sorry to hear that. But the Packers won today so that's good
Click to expand...
Click to collapse
Is what it is. I should know better than to adopt a new release anything lol. And GO PACK GO!
Morgrain said:
Pretty sure that three of your problems are software/Android 12 based, but the reboot and wifi issues are probably not. Ergo a replacement should definitely suit you.
It's the old concern of Pixels - they act as beta tester devices for new Android version (and the new Pixels always get the newest Android...). Meaning that people always think "it's Pixel bug! Replace! Hate! Pitchfork!" - even though it's often "just" an Android (12) bug.
It is very difficult to differentiate between a "real" Pixel bug/problem and an Android one, since at the time where Pixels get released, there are no other stable versions of (the newest) Android out there.
Click to expand...
Click to collapse
I am on beta One UI 4 on my s21u currently, and the bugs on that are not the same bugs as the pixel, that's for sure. At least not the random reboots. But Samsung so heavily skins android, that is not a surprise. One of the main reasons I want to go pixel. Tired of Samsung putting their trash over vanilla Android
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
UPDATE:
I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Was it à regular updates from Honor ?
TotallydubbedHD said:
Just updated my Magic4 Pro to Android 13, Magic OS 7.1, Build number: 7.1.0.136 and I cannot switch between apps; the functionality is simply broken.
I've got a video demonstrating it on Twitter...would therefore suggest not upgrading until this is (and potentially other bugs) fixed.
Click to expand...
Click to collapse
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
marcox92 said:
Was it à regular updates from Honor ?
Click to expand...
Click to collapse
Yes it's a regular and official update.
Curious, didn't receive the update
nico97470 said:
I suggest you to perform a hard reset. I don't meet this issue. It's very strange!!!
Click to expand...
Click to collapse
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
marcox92 said:
Curious, didn't receive the update
Click to expand...
Click to collapse
You should tape in the three points upper in right in the app Honor Club( system update). Trying versions.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
nico97470 said:
I'm going to perform a hard reset because of draining battery and others bugs. I was before a beta tester. This update, too soon!!! Honor should have waited!!! I'm angry !
Click to expand...
Click to collapse
Agreed.
Doing a reset will solve it, I have not done it and it works fine, I have been lucky.
TotallydubbedHD said:
That's not something I'm prepared to do; don't want to be wasting my time having to do a full factory reset due to a broken feature that's been pushed through by the manufacturer.
And yes, regular and official update.
Click to expand...
Click to collapse
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
wolfaas12345 said:
Unfortunately you might just have to do a backup and do it when it comes to android in general not just honor platform updates tend to break things and only way to fix those bugs is to reset simple as that you can complain left and right but that's just how it is happens on ios mac os and Windows as well
Click to expand...
Click to collapse
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Ja5ka said:
It was very relieving to find this thread and make my phone usable again. It was horrible experience trying to use the phone without an ability to switch apps.
Click to expand...
Click to collapse
Sorry to hear that but glad I could help!
TotallydubbedHD said:
I used to flash ROMs and kernels weekly on my SGS1, but I can't ever recall one breaking basing navigation functionalities.
With that said, I've found the potential cause of said issue - it's linked with the launcher not being default. Switching it back to Honor Home, then re-selecting Nova launcher seems to have fixed the issue.
However, if I restart or power off the phone, the issue comes back, thus needing to do the above again.
Click to expand...
Click to collapse
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
wolfaas12345 said:
"It didn't happen before so it can't happen now" great logic also that was super long time ago lmao back in SGS1 days we only had 1 navigation type so it either fully worked or didn't there were no variables these days we have 2-3 so obvs stuff can break plus don't forget with a clean install there are 0 variables that's why bugs, if they happen, are caught by honor or whoever makes the update with apps and custom settings thrown in there's thousands of variables that can make stuff go haywire
Click to expand...
Click to collapse
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
No its garbage logic in fact yes its been in dev for 13 years it has also been adding features for 13 years changin things for 13 years for same 13 years its also been supporting over 20k+ devices and working on them bugs are about normal with majority phones we dont see a lot cuz devs squash them before they push the update but variables that i mentioned prevent devs from covering all scenarios so shenanigans happen my problem was not with bug itself my problem is people like you talking crap because they refuse to wipe or expect flawless experience every time nothing is perfect especially software
TotallydubbedHD said:
Indeed, it is great logic. Android has been in development for 13 years since the SGS1, so you'd expect fewer bugs and fundamental features not being broken. Remember, not everyone is a techie nor will come to XDA looking for the fix, and ultimately might be put off the brand altogether, which otherwise makes excellent phones (and I've owned Honor phones on/off since 2015).
Guess you're not thinking of the bigger picture here, anyway I digress.
Click to expand...
Click to collapse
I think you are an expert. Do you think it is possible to install Google Services Framework on Magic5pro? I have one but dunno how to do so. Thank you for your sharing.