Related
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
I found this ROM:
http://www.gearengine.it/?page_id=2
...and would LOVE to run it on my AT&T GSIII but it says they're running it on the international version. I was planning on giving it a shot anyway but, while I'm working on rooting, I'd ask a few questions.
Think it'd work on the AT&T version?
If not, is there an equivalent ROM that will?
I want to keep ALL the stock functionality...camera wise, hardware wise (NFC, Bluetooth, etc) yet still getting the customization that that ROM afforded (I loved the Aroma installer, the inverted apps, etc) while running an overclock/undervolt kernel so I can juice this thing!
What are you guys running?!
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
CamFlawless said:
One word of advice would be not to flash an international ROM on your AT&T device. I think that would lead to a brick.
Do some reading in the development sections to familiarize yourself with the basics.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have to agree. I actually just commented in a thread before coming across this one: http://forum.xda-developers.com/showthread.php?t=2056655
Foxhound was flashed to their device, and their device was hard bricked. Please do not flash i9300 ROMs to US device variants.
I am currently running cm10.0.0 stable. It runs like a dream, not one issue with it so far. I would not recommend the new cm10.1 nightly builds until the data problem is fixed however.
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
rmp5s said:
LOL!!!
Well...this website was down for a few and I though ah hell, why not.
smh
Never actually heard of anyone hard bricking a phone. Awesome. This rounds out my Android experience nicely. Just as dude says, it doesn't do a damn thing. No power, not light, no vibration, nothing.
I can't believe there's no way to fix something like this. I'm all around amazed...I must say.
But yea...so...AT&T I go in the morning to test my acting skills I guess. *shrug*
And the Aroma installer was SO COOL!!!! What a shame...
Had I known the consequences could be so dire...
Click to expand...
Click to collapse
Very sorry to hear your luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =) My hard brick came from a CWM flash when I was inexperienced at flashing. (I came from an iPhone... bleh). I had used a terminal emulator and used some commands to install CWM. Big mistake. I then followed Cyanogenmod's WIKI on installing CWM and it worked like a charm. =)
Of course, in my opinion, nothing beats TWRP recovery installation... Step 1: Download Goo Manager from the PlayStore. Step 2: Click menu and "Install OpenRecovery Script" Step 3: Wait for your phone to reboot into recovery =)
Well now that I'm done with my tangent, I think I'm heading to bed for the night lol. Good luck at the AT&T store tomorrow! ...and have a Happy Holiday! =)
RPelham said:
Very sorry to hear you luck =( Good luck at AT&T... Don't let this deter you from future ROM flashes, just make sure you are flashing the correct GS3 variant. If you are on AT&T your device is model# i747 and the codename is d2att when flashing ROMs.
I didn't need too many acting skills, I just told them I woke up in the morning and my phone would no longer turn on. They swapped it out pretty quickly =)
Again, good luck, and have a Happy Holiday!
Click to expand...
Click to collapse
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
rmp5s said:
Hey...it's all good man. I've been in the Android game since the G1 and STILL I'm getting firsts. LOL!!! I will ALWAYS hack, tinker and tweak. That's the fun of it...this included.
I KNEW it was the wrong version. However...what I DIDN'T know was the likely outcome! Had no idea. Only ever heard of hard bricks as a mythical monster-like sorta thing. Through my G1 days, GS days, HTC Doubleshot, HTC One S and AAAAAAAAAAALL the devices I've rooted and ROM'd in between (my tablets and who knows how many friend's devices), I've never seen or had a true hard brick happen. Had a close call sorta with the ex-wife's GS, but I fixed it.
Honestly didn't think this was something that could ACTUALLY happen!!!
We'll see what happens.
Thanks everyone!!
Click to expand...
Click to collapse
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
cjranucci said:
I have been with Android through the GS1, GS2, and now GS3. I totally agree with you. I have done some really stupid stuff, but have always been able to fix the problem, mostly from help from this forum.
It may be just me, but it seems that it is a lot easier to brick the GS3 than its predecessors. Not from personal experience (knock on wood), but from reading through these forums.
Let us know what happens at the AT&T store. As an aside, does anyone ever know what happens in the long run when you turn in a hard brick to AT&T and get it replaced? I would imagine that once they JTAG it they would see that it was flashed. Could they charge you for the device?
Click to expand...
Click to collapse
That is a fantastic question. I was concerned about that myself the first time it happened. From my experience I was never charged when I went into the store to do the exchange. No bills came later in regards to it either. I think its pretty safe, but I wouldn't make any guarantees.
I also agree with you in that the GS3 seems a lot easier to brick than other phones I've dealt with.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Well...they gave me another one. Couldn't get another red one like I wanted since they didn't have any in stock which kinda sucks so I got the blurple one. Looks cool.
Obviously, I can't agree with the comments on the GSIII's resistance to bricking since I had something happen with this device that I've never seen or even HEARD of anyone doing. lol But it's all good. Time to start tinkering again.
Think I'm going to go the CM10 route since that is apparently a good ROM. However...does everything work with it? NFC and all? And...is there an OC/UV kernel that is compatible with that ROM?
As far as what they do with it after, I don't really know. I had to take it back to Best Buy since that's where I got it and it was so soon after getting it. I only had the thing...for...like...4 hrs when it got killed. lol I would imagine that they have the resources to easily fix a device that has had this happen. If they didn't replace it, I was just going to make a JIG for it (http://www.androidnova.org/unbrick-your-hard-bricked-smartphone/).
Thanks for all the help, guys!!!
Well...I didn't kill it. lol
So...first setup I tried:
ROM - http://forum.xda-developers.com/showthread.php?t=1766684
Kernel - http://forum.xda-developers.com/showthread.php?t=1756776
My ratings, out of 10?
Look and feel: 7...I only give it so low since it's EXACTLY the same as the HTC One S ROM I was running. This is usually a good thing but I was wanting something different.
Functionality: 4...every time I send a text, the damn thing says it didn't send! But it does! Very strange, very annoying, very unusable.
Customizability: 12...it's an AOKP ROM...with the Nova launcher...there are a mind bending number of options. I love it!
Quadrant score: 3...What the hell is an overclocked, current gen phone juiced to over 2.1GHZ doing getting ~3600 pts in quadrant? EXTREMELY disappointing.
Final words: Running Android 4.2...awesome. I love being cutting edge, but there isn't anything really awe-inspiring about it aside from the Jelly Bean 4.2 but the text messaging problem is just insurmountable.
Next is going to be this one:
http://forum.xda-developers.com/showthread.php?t=1949025
Going to keep the kernel and we'll see what happens! I'll let you know!
Glad it worked out. =) Just a heads up 4.2 has a lot of common bugs with it being so new. That texting problem is among many. Bluetooth issues, USB MTP issues, internal/external storage swapped, mobile data and WiFi issues to name a few.. I'd recommend sticking to 4.1 unless you don't mind the above annoyances. =p They will get ironed out soon enough I'm sure. =)
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
rmp5s said:
That ROM flat out didn't work...it booted and everything but the keyboard kept giving me an FC. No bueno.
Back to the other I go!
Can anyone recommend a ROM that is as customizable as the AWESOME AOKP ROMs but still retain a bit of the Samsung-ness? Like...I like having the burst shot in the camera, the cool gesture and motion stuff they have, etc. Is there a middle ground?
Click to expand...
Click to collapse
Checkout NexusMOD in the development forum. Its a touchwiz ROM with AOSP messaging and email. You can still run Nova Launcher if you want, and holo locker if you don't want the TW lock screen.
I'm still tinkering and trying different ROMs. Downloading LiquidSmooth right now, can't find the NexusMOD one mentioned and I just tryed to flash an AOKP ROM and it wouldn't flash.
I SO BADLY want the 4.2 to work. I LOVE it!!! The Camera (wish it had HDR and multi shot modes, though), the stock messenger, LOCK SCREEN WIDGETS...it's just awesome.
I'm with you all the way rmp5s(except the bricking part), I want this ROM sooo bad. It's stockish which I like, yet has a lot of mods, any word yet on it coming to I747?
My LG Optimus G had a bad start ever aince day one. I love this guy but he gives me headaches at times. Anyhow, before I bricked it in the beginning, truth be told this thing sucked. Videos would play and stop with "buffering" every 15 seconds, website would load up slow, etc. I bricked it to the point where it will never be FULLY stock ever again. I flashed a few different roms like AOKP 4.2.2, etc. All roms I actually tried made wifi worse. AOKP actually had my wifi to one bar (really a dot) and really slow downloads. So I flashed the rom provided by AdriVelazquez here http://forum.xda-developers.com/showthread.php?t=2178297 since stock was better than anything else, (again, NEVER CAN GO BACK TO FULLY STOCK) and believe it or not this rom has actually made this thing better than any other rom and the original factory stock ZVB i had before. Downloads are fast, wifi bars are good, and the videos play without ever buffering!!! Now enough blabbering and to my point. Why is that? I would love to have different looks on my LS970. I mean sure the stock looks HD and all, but I'm constantly changing roms on every android I have. Does anyone else have a similar issue/issues when your on a different rom? Is there any other way to get it to work good while on another rom? This is just a informational post, not a "help me I think my device is dying post," so feel free to voice opinions. Thanks in advanced
Sent from my LG-LS970 using xda app-developers app
Buddy you are in the wrong forum. This one here is for the international (e975) version. You should better ask people with same phone model, maybe there are some ppl with same issue.
Had no idea. Thanks alot I'll look for that section
Sent from my LG-LS970 using xda app-developers app
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.
Hey guys,
So I'm trying to figure out why my HTC One is having camera issues all of the sudden. It seems to take video fine, but it has major issues focusing on anything more then a foot away. So this is making it very hard to take pictures of anything. I'm going to attach a picture of my car, and I can tell you that I clicked all over the screen trying to get it to focus on anything at all.
Some important info, I'm on the latest official firmware and on a ported version of Sense 7 (see my sig). I am starting to wonder if the issue started with the first 5.0.1 Lollipop build I tried, because I don't recall the issue when I was on the last KitKat build. Could it be possible the new lollipop software is not playing nice with the older M7 hardware? I asked in the ROM thread to see if anyone else was having the issue, but it did not seem to be an issue with other users.
So that leads me to my next idea, could the hardware have gone bad? But then why would the video camera be taking clear and focused video? It does not have any crazy colors like the known issue is with our cameras, but it just will not focus.
Let me know if you have any ideas for me to try, I would really appreciate it.
@Ahowe125
Have you tried going back to KitKat?
Typically when you try something that has been ported over, there will be at least one broken feature. For me, its always the camera. For someone else, its always the bluetooth. Everything else works fine for me.
im_high_tech said:
@Ahowe125
Have you tried going back to KitKat?
Typically when you try something that has been ported over, there will be at least one broken feature. For me, its always the camera. For someone else, its always the bluetooth. Everything else works fine for me.
Click to expand...
Click to collapse
As of right now, No I have not. I didn't make a backup of my old kitkat rom when switching to 5.0.1 so I'll have to go re-download and install it. Maybe It may not be a bad idea to try that, and then if the camera works try and install a fresh version of lollipop again.
Thanks for the idea, I'll try that later tonight.
Ahowe125 said:
As of right now, No I have not. I didn't make a backup of my old kitkat rom when switching to 5.0.1 so I'll have to go re-download and install it. Maybe It may not be a bad idea to try that, and then if the camera works try and install a fresh version of lollipop again.
Thanks for the idea, I'll try that later tonight.
Click to expand...
Click to collapse
I personally don't think flashing KitKat and going back to Lollipop is going to fix your issue, at least in my experience it has not. It's just this modified port. Once HTC put the official Sense 7 code out there, then maybe it'll fix it. But that's still going to be a m9 port. If there was an official Sense 7 lollipop for m7 then I can almost guarantee it'll work.
You can trying use HD or HDR mod for your camera
ewew43 said:
You can trying use HD or HDR mod for your camera
Click to expand...
Click to collapse
Thanks for the idea, I just tried this today and still no luck. Its like the focus is broken. I have not had time to switch back to KitKat. Hopefully I can hold out until April until LP firmware is slated to be released for our M7.
Also, just for the sake of trying, I downloaded the Google Camera from the play store, and it also is having issues with focusing on just about anything. More then a foot away it will not make a clear focus on.
So just a quick update, I tried all the different camera settings and it still won't focus.
Also, I finally had time to install a kitkat rom that I had previously used and knew the camera worked on. My phone has the latest stock kitkat firmware and my camera will still not focus.
It seems like its trying, as it will adjust for distance and I can see the mechanism moving inside the camera, but I for the life of me don't understand why it won't focus like it use to.
After that test I flashed the newest version of my favorite ROM and I'm not sure what to do/try now. Should I try to contact HTC? Would it even be something they would warranty or fix on this old of a phone?
Thanks for your ideas.
Well... I think this phone just might be showing its age or something. In the year or better I have had it, its been perfect. Now this week the top speaker decided to crap out on me. Its more then likely blown, as it makes a horrible rattling noise when any loud sounds are played. I tried cleaning it out and blowing with compressed air with no luck.
I guess maybe its time to upgrade to an M9. But this phone has been so awesome... decisions decisions.
Ahowe125 said:
Well... I think this phone just might be showing its age or something. In the year or better I have had it, its been perfect. Now this week the top speaker decided to crap out on me. Its more then likely blown, as it makes a horrible rattling noise when any loud sounds are played. I tried cleaning it out and blowing with compressed air with no luck.
I guess maybe its time to upgrade to an M9. But this phone has been so awesome... decisions decisions.
Click to expand...
Click to collapse
I was hoping you had a fix for this since my mothers phone just starting doing this as well. I have no idea whats causing it.
For the camera, I have tried reflashing the firmware, installed new versions of both lollipop and kitkat OS and even tried different camera applications. I'm almost sure it has to be hardware related.
As far as the speaker goes, its almost always hardware as I've blown car audio speakers that had the same horrible noise. Not much I can do there. I did try the cleaning method with a toothbrush and compressed air with no change.
I also wish I had a fix because I bought this phone brand new and it's been amazing. I can't upgrade right now and don't want to foot the price for an M9. So I bought what looked like a very clean m8 from @tonyb81 on swappa. Should be here tomorrow and then I have to figure out what to do with this broken m7.
Ahowe125 said:
For the camera, I have tried reflashing the firmware, installed new versions of both lollipop and kitkat OS and even tried different camera applications. I'm almost sure it has to be hardware related.
As far as the speaker goes, its almost always hardware as I've blown car audio speakers that had the same horrible noise. Not much I can do there. I did try the cleaning method with a toothbrush and compressed air with no change.
I also wish I had a fix because I bought this phone brand new and it's been amazing. I can't upgrade right now and don't want to foot the price for an M9. So I bought what looked like a very clean m8 from @tonyb81 on swappa. Should be here tomorrow and then I have to figure out what to do with this broken m7.
Click to expand...
Click to collapse
Yea I understand and i meant to say that she only has the camera problem and not the speaker problem. I have the same phone but have neither problem. I am thinking it is hardware problem as well since she uses her camera a lot more than I do.
yojoe600 said:
Yea I understand and i meant to say that she only has the camera problem and not the speaker problem. I have the same phone but have neither problem. I am thinking it is hardware problem as well since she uses her camera a lot more than I do.
Click to expand...
Click to collapse
It's really strange too, because it just stopped working one day. It wasn't intermittent or anything. One day it just wouldn't focus and I thought maybe I was doing something wrong or a setting was messed up. But nothing I tried worked.
I wondered if I should contact HTC about it and still might. But it doesn't help its been s-off and unlocked since before my activation. Once I get the M8 I think I'm going to try a few more things and maybe put it all back to totally stock.
If nothing else I might sell it as a parts phone or keep as a backup.
Ahowe125 said:
It's really strange too, because it just stopped working one day. It wasn't intermittent or anything. One day it just wouldn't focus and I thought maybe I was doing something wrong or a setting was messed up. But nothing I tried worked.
I wondered if I should contact HTC about it and still might. But it doesn't help its been s-off and unlocked since before my activation. Once I get the M8 I think I'm going to try a few more things and maybe put it all back to totally stock.
If nothing else I might sell it as a parts phone or keep as a backup.
Click to expand...
Click to collapse
I googled the problem and it seems a few other have had the problem as well. So far they all seem to had to get new phones.
Sent from my only One.
The camera and speaker problems are both hardware related. The camera is known for having the issues that both of you have run into and the only fix is getting the phone replaced. I had heard that HTC extended the warranty for phones with the camera issue but I don't know if this is true.
disconnecktie said:
The camera and speaker problems are both hardware related. The camera is known for having the issues that both of you have run into and the only fix is getting the phone replaced. I had heard that HTC extended the warranty for phones with the camera issue but I don't know if this is true.
Click to expand...
Click to collapse
Good info, I'll have to check into that then. Thanks
Sent from my Nexus 7 using Tapatalk