Develop Bugs

Two problems with ICS.

Well, maybe two and a half.
I was using FB17 on my old black ET (bought on launch week), before it was bricked.
GPS would not connect. Vlingo was very broken - would not work with a bt car kit unless you manually unlocked the screen.
It was very snappy in my testing though.
I now have a brand new white ET, and I tried FC14.
Exact same problems. None of those were fixed in the last 3 1/2 weeks.
Thank god someone has figured out that you can simply remove vlingo garbage and replace it with a number of dialing apps like google voicedialer. I don't know if it can be done on ICS, but it works very well in EL29 gb roms.
So, GPS is a deal breaker right now, possibly on two somewhat different versions of hardware (old black et vs white new et.) What the hell are the developers thinking not fixing gps?
Also, FC14 was noticeably choppier than both EL29 and FB17. Maybe it was because of the particular widgets/software I used, I don't know. Could be a problem too.
Anyway, any thoughts?

nabbed said:
Well, maybe two and a half.
I was using FB17 on my old black ET (bought on launch week), before it was bricked.
GPS would not connect. Vlingo was very broken - would not work with a bt car kit unless you manually unlocked the screen.
It was very snappy in my testing though.
I now have a brand new white ET, and I tried FC14.
Exact same problems. None of those were fixed in the last 3 1/2 weeks.
Thank god someone has figured out that you can simply remove vlingo garbage and replace it with a number of dialing apps like google voicedialer. I don't know if it can be done on ICS, but it works very well in EL29 gb roms.
So, GPS is a deal breaker right now, possibly on two somewhat different versions of hardware (old black et vs white new et.) What the hell are the developers thinking not fixing gps?
Also, FC14 was noticeably choppier than both EL29 and FB17. Maybe it was because of the particular widgets/software I used, I don't know. Could be a problem too.
Anyway, any thoughts?
Click to expand...
Click to collapse
When I started flashin ICS Roms...Couldn't get a lock or very spotty coverage...I tried all the Apps out there for GPS...None worked...What worked best has been used by many people on here...for me it worked the first time and I always get a lock...Here's the deal...
If you are willing to take the time to do it, this seems to work for everyone:
Odin one click back to Gingerbread
Odin flash kernel w/ recovery
Restore nandroid (optional)
Get GPS lock on Gingerbread and keep it on.
Boot to recovery and flash format all zip and ROM.
So Odin one click back to el29 GB...
get CWM there as well...Get your lock...leave it on...Go to CWM...restore your ICS Rom of choice...Reboot...ICS will open up and you will have GPS lock...works everytime...At least it has for me and a lot of people on here...
GPS was the Deal breaker for me as well...I use it a lot...Now I have an ICS Rom for my Daily Driver...

Well GPS hasn't been a strong point for Samsung in general. The devs your referring is Samsung, right? They have the necessary tools, like source code and non-gpl drivers. I'm pretty sure Samsung will get GPS better on ics at some point.
El29 is very refined. I would totally expect it to run smoother than any ics leak at this point.
I don't use any car/voice mode, so I cant comment on that.
Sent from my SPH-D710

ronny71 said:
When I started flashin ICS Roms...Couldn't get a lock or very spotty coverage...I tried all the Apps out there for GPS...None worked...What worked best has been used by many people on here...for me it worked the first time and I always get a lock...Here's the deal...
If you are willing to take the time to do it, this seems to work for everyone:
Odin one click back to Gingerbread
Odin flash kernel w/ recovery
Restore nandroid (optional)
Get GPS lock on Gingerbread and keep it on.
Boot to recovery and flash format all zip and ROM.
So Odin one click back to el29 GB...
get CWM there as well...Get your lock...leave it on...Go to CWM...restore your ICS Rom of choice...Reboot...ICS will open up and you will have GPS lock...works everytime...At least it has for me and a lot of people on here...
GPS was the Deal breaker for me as well...I use it a lot...Now I have an ICS Rom for my Daily Driver...
Click to expand...
Click to collapse
It works for a while. Then you lose gps again. It's too much trouble flashing and reflashing, whereas it should just work.
EL29 calks roms is very nice and smooth. Everything works, with a proper theme it looks a lot like ICS. It's just not worth it putting up with ICS bugs right now.
The only thing I'm really missing from ICS was the browser.

In the two days I've been running FC15 I've experienced none of what you mention. I think it's the luck of the draw with hardware/software and sprint service in your area. Are you updating your profile and PRL after flashing new modems?
FC15 is the smoothest build I've experienced since EL29 (which remains my goto version if the current ICS build doesn't do the job).
Did you do a complete wipe before installing? Did you make sure to flash the full rather than the nodata version if going from GB to ICS?
I'm certainly not insinuating you are incapable of knowing how to flash new builds but sometimes we overlook the simplest steps which leads to major complications.
If you've done all the above (including using Calkulin's format all) and still experience these issues then I'd definitely stick with EL29 for awhile longer.

My gps locks faster than ever. It's insane. I used gps all over CT, RI, and MA this weekend and was perfect. Didn't even get confused by 95 exchange in Providence.

Esoteric68 said:
In the two days I've been running FC15 I've experienced none of what you mention. I think it's the luck of the draw with hardware/software and sprint service in your area. Are you updating your profile and PRL after flashing new modems?
FC15 is the smoothest build I've experienced since EL29 (which remains my goto version if the current ICS build doesn't do the job).
Did you do a complete wipe before installing? Did you make sure to flash the full rather than the nodata version if going from GB to ICS?
I'm certainly not insinuating you are incapable of knowing how to flash new builds but sometimes we overlook the simplest steps which leads to major complications.
If you've done all the above (including using Calkulin's format all) and still experience these issues then I'd definitely stick with EL29 for awhile longer.
Click to expand...
Click to collapse
Yeah, I've done all those things and even more you never heard about.

nabbed said:
Well, maybe two and a half.
I was using FB17 on my old black ET (bought on launch week), before it was bricked.
GPS would not connect. Vlingo was very broken - would not work with a bt car kit unless you manually unlocked the screen.
It was very snappy in my testing though.
I now have a brand new white ET, and I tried FC14.
Exact same problems. None of those were fixed in the last 3 1/2 weeks.
Thank god someone has figured out that you can simply remove vlingo garbage and replace it with a number of dialing apps like google voicedialer. I don't know if it can be done on ICS, but it works very well in EL29 gb roms.
So, GPS is a deal breaker right now, possibly on two somewhat different versions of hardware (old black et vs white new et.) What the hell are the developers thinking not fixing gps?
Also, FC14 was noticeably choppier than both EL29 and FB17. Maybe it was because of the particular widgets/software I used, I don't know. Could be a problem too.
Anyway, any thoughts?
Click to expand...
Click to collapse
Of course el29 will be smoother it's an official release. It isn't the developers fault GPS is goofy on ics either they been working hard to fix it... maybe you should read the bug list before you flash anything. Nothing will be completely stable until an official release is out thank the devs they got us this far and at least we can use most ics roms as a daily driver... a couple months ago no one can even get ics to function now look were we Are.
Sent from my SPH-D710 using xda premium

musikalharmony said:
Of course el29 will be smoother it's an official release. It isn't the developers fault GPS is goofy on ics either they been working hard to fix it... maybe you should read the bug list before you flash anything. Nothing will be completely stable until an official release is out thank the devs they got us this far and at least we can use most ics roms as a daily driver... a couple months ago no one can even get ics to function now look were we Are.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I was talking about Samsung developers, not xda developers. Maybe I should have clarified. But I thought it was self-evident, since there's no source code for ICS available yet (and probably won't be for months.)
As for bug lists - ICS roms threads simply don't have them. So please don't patronize and act all butthurt for no reason.

nabbed said:
Yeah, I've done all those things and even more you never heard about.
Click to expand...
Click to collapse
Well if you've tried all those and many you 'assume' I've never heard of then I think you've answered your own question.
Stick with EL29 until the official ICS is available. With any luck we aren't far off.

Esoteric68 said:
Well if you've tried all those and many you 'assume' I've never heard of then I think you've answered your own question.
Stick with EL29 until the official ICS is available. With any luck we aren't far off.
Click to expand...
Click to collapse
It's hard.
The flashaholic in me wants to try fc15. I know gps wont work in it, from the review qbking77 posted. But maybe it will be as snappy as FB17 was...
BTW, when is the official Sprint ics release due?

nabbed said:
It's hard.
The flashaholic in me wants to try fc15. I know gps wont work in it, from the review qbking77 posted. But maybe it will be as snappy as FB17 was...
BTW, when is the official Sprint ics release due?
Click to expand...
Click to collapse
FC15 gps does work. I'm getting a lock right now on 8 satellites.

The Root said:
FC15 gps does work. I'm getting a lock right now on 8 satellites.
Click to expand...
Click to collapse
It doesn't work for qbking77, so I assumed it won't work for me.

nabbed said:
It's hard.
The flashaholic in me wants to try fc15. I know gps wont work in it, from the review qbking77 posted. But maybe it will be as snappy as FB17 was...
BTW, when is the official Sprint ics release due?
Click to expand...
Click to collapse
It is hard to not flash and I'm only a recent flashaholic (boy do I wish I'd paid more attention to XDA when I had my EVO 4G, would've saved me the mistake of buying the POS 3D).
After FC07 I was going to stick with EL29 until the official release came out but then the 13, 14 and 15 leaked builds came out with overall good reviews so I dove in again and so far I haven't regretted it.
Official release date, who knows, this is Sprint after all but with the leaks coming fast and furious common sense would dictate it can't be too far off (at least we hope).

nabbed said:
It doesn't work for qbking77, so I assumed it won't work for me.
Click to expand...
Click to collapse
Believe me mine works...EveryTime...Im runnin on FC14 at the moment ...didn't think there is a need to update to 15 since 14 is runnin fine...Everything runs on My Rom...But like I told ya if GPS didn't work Id be back on GB...Right now Im runnin an EL29 Modem on MIJJz BLEND ICS "THE GOODNESS" 2.3...IMO its the hottest ICS Rom out there hands down...Its smooth quick snappy...uou name it...With functioning GPS for me...But if you think you'll be happy with GB go back...Im stickin with the ICS leaks till the final and I think they are Damn close...

nabbed said:
I was talking about Samsung developers, not xda developers. Maybe I should have clarified. But I thought it was self-evident, since there's no source code for ICS available yet (and probably won't be for months.)
As for bug lists - ICS roms threads simply don't have them. So please don't patronize and act all butthurt for no reason.
Click to expand...
Click to collapse
You are aware of the difference between "unknown dev-state leaks" versus "official releases", right? Also that devs post leaks for us to test and report back bugs, of which there are multiple threads containing these lists, right? The issues you report have been answered in several threads, several times.

My gps has worked in every FC ICS build so far. (Lucky me I guess)
Few things that don't work, error out.
Accuweather daemon sometimes FC's.
Moving apps to SD card a bit wonkey. Currently doesn't move them to the ACTUAL SD but to "usb storage" on the phone. FC15 only.
A handful of apps still aren't compatible with ICS. (NOT the rom fault).
Signal bar info isn't correct on any build pre FC15.
Market sometimes takes awhile to actually start downloading apps.
GPS sometimes doesn't turn OFF. <- eating your battery VERY quickly.

Toleraen said:
You are aware of the difference between "unknown dev-state leaks" versus "official releases", right? Also that devs post leaks for us to test and report back bugs, of which there are multiple threads containing these lists, right? The issues you report have been answered in several threads, several times.
Click to expand...
Click to collapse
I wasn't reporting anything. I was just reflecting on how in 3.5 weeks of my absence, the most blatant deal breaker bugs have not been fixed.

I've never flashed an ICS rom but I use FC15 modem with blazer 4.0 and It's possibly the best modem I've used with this phone. Smooth as can be and what seems to be better data speeds than the other modems.

I_FLY_Z3R0 said:
I've never flashed an ICS rom but I use FC15 modem with blazer 4.0 and It's possibly the best modem I've used with this phone. Smooth as can be and what seems to be better data speeds than the other modems.
Click to expand...
Click to collapse
Im on an ICS Rom...just flashed FC15 for test run...
I see 17 and 19 are due out soon...

Best ICS Rom

Look Im seeing A LOT of people complaining about the new update, I want to know which ROM is the best to use without the problems, I prefer to use ODIN and was wondering if the one click full restore for FF18 is having those problems or should I just wait for them to fix this problem before doing a system restore. I just got my phone back from samsung and was waiting to root for the update to come out but if there is problems with it I just prefer to wait.

Just do the one click full restore ff18. There is absolutely nothing wrong with ICS. Don't let anyone tell you there is.
Sent from my SPH-D710 using Tapatalk 2

revamper said:
Just do the one click full restore ff18. There is absolutely nothing wrong with ICS. Don't let anyone tell you there is.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
+1 the ICS is fine. It is different and I think that is causing most of the issues for people.

tFF18 from Agat
AKush1279 said:
Look Im seeing A LOT of people complaining about the new update, I want to know which ROM is the best to use without the problems, I prefer to use ODIN and was wondering if the one click full restore for FF18 is having those problems or should I just wait for them to fix this problem before doing a system restore. I just got my phone back from samsung and was waiting to root for the update to come out but if there is problems with it I just prefer to wait.
Click to expand...
Click to collapse
I used the stock leaks for quite a while, then tried out the tFF18 ROM (plus his custom kernal) from Agat. It seems like my battery life may have dropped slightly but overall loving it. There is nothing wrong with stock FF18, it is great also. When I upgraded to tFF18 I didn't wipe the phone and all my apps / settings worked fine still, because it's based on the stock ROM.

Gingerbread is definitely smoother as far as scrolling goes...
Other than that, the improvements in ICS seem to be to my liking. Google is definitely taking after cyanogen and putting in some stuff that more people want to see on the greatest OS Android!
Sent from my Super Galaxy'd SPH-D710

ICS
yeah dude, dont let anyione tell you that you get ****ty battery life, scrolling is like a crazy whore running after crack, the buttons sometimes dont work, the settings crash, facebook doesnt sync, exchange has problems. also
* Roaming Guard now ignores settings and alerts you continuously to improve your awareness.
* Adds a cool stuttering effect to chrome browser just in case you missed it the first time.
* Allows you to better focus on your phone while running or driving by not taking commands from a Bluetooth headphone set while the screen is of.
* Allows you to scroll from top to bottom of a list in .02 seconds even when you dont mean to for faster navigation.
* And many more!
It's all a small base of about 60% of the users that are experiencing this. And even thou our devs are great its hard to make a diamond out of ****.
Just saying FF18 should have just been a leak. Nothing more. There's a lot of really cool features ICS brings, but all the ICS roms that are there now are just themed versions of stock with different launchers. Just saying... 14 roms with all different colors... wtf?
This update, of course, does nothing to fix Sprint's horrid network. So, if you have a crumby data connection now you'll have one after as well =)

alexpatcas said:
yeah dude, dont let anyione tell you that you get ****ty battery life, scrolling is like a crazy whore running after crack, the buttons sometimes dont work, the settings crash, facebook doesnt sync, exchange has problems.
It's all a small base of about 60% of the users that are experiencing this. And even thou our devs are great its hard to make a diamond out of ****.
Just saying FF18 should have just been a leak. Nothing more. There's a lot of really cool features ICS brings, but all the ICS roms that are there now are just themed versions of stock with different launchers. Just saying... 14 roms with all different colors... wtf?
Click to expand...
Click to collapse
Just because you have issues does not mean there are issues. I can have a ferrari that does not run right, that does not mean that ferrari's are bad. I sync exchange with no issues, never had bad battery, and settings do not crash. I would check your own setup and not blame ICS.

rujelus22 said:
Just because you have issues does not mean there are issues. I can have a ferrari that does not run right, that does not mean that ferrari's are bad. I sync exchange with no issues, never had bad battery, and settings do not crash. I would check your own setup and not blame ICS.
Click to expand...
Click to collapse
yeah its stock.
and funny thing theres a **** load of forums that have these problems. people that dont want to root. look on sprints forums.
btw funny ears...lol

alexpatcas said:
yeah its stock.
and funny thing theres a **** load of forums that have these problems. people that dont want to root. look on sprints forums.
btw funny ears...lol
Click to expand...
Click to collapse
Stock does not really mean anything, It could be apps your running in the background. I have used the leaks since day 1 and have my own ROM, and the only one I can say is an issue is scrolling.

http://community.sprint.com/baw/com...nes-and-devices/samsung/samsung_epic_4g_touch - check this **** out
see how applauded the update is.

Do you even know what you are talking about? Obviously not. Had you actually installed one of the '14 different colors' you would realize there are significant differences between custom roms. These devs spend vast amounts of time making these roms, various tweaks for battery life and performance , custom interfaces, and a ton of added features you will not see on any stock device. There is a hell of a lot more to it than choosing that perfect shade of blue. Don't discredit others hard work when you obviously have not made the slightest effort to educate yourself beyond looking at a couple of screen shots.

To answer the OP most of the roms are good, try them for yourself everybody has a different style. Start with a few of the Team Venum roms and go from there.

OP, if i were u, try out a few cuatom ics roms to see how u feel about them. I myself tried 2 - supernova and blu kuban. I ditched supernova bc it was laggy and slower than calkulin's v3.0 gb rom. But it was stable for me. I ditched blu kuban bc it wouldnt let kakaotalk work correctly and some apps would crash a few times. Otherwise, i loved it and wished i could've kept it on my phone. For now, i'm back with calkulin and just waiting for an ics setup that can meet and/or exceed the calkulin 3.0.

Ravaged Pheonix said:
Do you even know what you are talking about? Obviously not. Had you actually installed one of the '14 different colors' you would realize there are significant differences between custom roms. These devs spend vast amounts of time making these roms, various tweaks for battery life and performance , custom interfaces, and a ton of added features you will not see on any stock device. There is a hell of a lot more to it than choosing that perfect shade of blue. Don't discredit others hard work when you obviously have not made the slightest effort to educate yourself beyond looking at a couple of screen shots.
Click to expand...
Click to collapse
did you just get mad? chill out bro. and as i said before is not the devs fault. It's hard to make the ff18 into anything slightly functional, sprint just threw **** at us.
I'm working on a rom with a dev right now, i haven't released a rom since the days of the diamond, so i wanna test it all the way. I'm leaving the rest to the public.

apatcas said:
did you just get mad? chill out bro. and as i said before is not the devs fault. It's hard to make the ff18 into anything slightly functional, sprint just threw **** at us.
I'm working on a rom with a dev right now, i haven't released a rom since the days of the diamond, so i wanna test it all the way. I'm leaving the rest to the public.
Click to expand...
Click to collapse
It is not hard and FF18 is not crap. Just my opinion.

FF18 plays nice on some devices, bad for other devices since the FF builds. I'm running the calk 1.6 ICS ROM with agats custom kernel and I honestly couldn't be any happier... I can keep my captive button lights on and haptic feedback on. It's a dream. On stock ff18 or custom ROMs, it all goes wrong out of no where with issues like captive buttons not working sometimes unless I turn off screen and on or hit the vol button. I guess its a 50/50 chance.
I haven't tried the blu k ROM simply because it is over themed for my usage... maybe if there was a non themed version I would.

I just find it funny people have been begging for ics since forever.. Now it's here and people like "aww man f*ck ics.. It's not all that"... Don't let anybody steer you from going to ICS.. I was using GB since forever and like ics better &haven't had bad battery life.. Actually been better... People Also need to take in consideration what they run and have more realistic standards for battery life... It may take a while to find a set up you like but it's possible
Sent from my SPH-D710 using Tapatalk 2

so...what ics roms do you guys like?
i'm using super galaxy

noahsarky said:
so...what ics roms do you guys like?
i'm using super galaxy
Click to expand...
Click to collapse
I love Calks 1.6 ICS ROM with agats new kernel built from source sadly a game I love isn't that friendly with ICS so I might go back to Blazer 4.1 till some game devs learn to update their games for new OS updates lol

noahsarky said:
so...what ics roms do you guys like?
i'm using super galaxy
Click to expand...
Click to collapse
I'm using the blu kuban rom.. I love the rom, all the features, battery life, and stability.. He put a lot of attention and hard work into the rom & supports it constantly...My only regret is not trying it sooner but I was still a noob and stock on GB (haven't had this phone long)
Sent from my SPH-D710 using Tapatalk 2

Sorry but I may be leaving the root community for good

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

Is there an equivalent ROM?

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?

So Android 5 LOLLIPOP has been officially revealed...

...and will it come out to our GNex ? :3
The SDK is coming out on Oct 17 (Source: http://www.androidpolice.com/2014/10/15/the-android-5-0-lollipop-sdk-will-arrive-on-october-17th/)
I hope so, because of the new GPU drivers in the FML-ROM, we're "prepared" for it(?)

When the source code will come out I'm sure that the develepers will start do work on it

devil188 said:
...and will it come out to our GNex ? :3
The SDK is coming out on Oct 17 (Source: http://www.androidpolice.com/2014/10/15/the-android-5-0-lollipop-sdk-will-arrive-on-october-17th/)
I hope so, because of the new GPU drivers in the FML-ROM, we're "prepared" for it(?)
Click to expand...
Click to collapse
We are, but we wont port sdk, we will w8 to opensource dorp

does this mean that Samsung Galaxy Nexus will have a version of Lollipop developed for it?

blekm said:
does this mean that Samsung Galaxy Nexus will have a version of Lollipop developed for it?
Click to expand...
Click to collapse
not sure if didn't read other responses, or just being smart-aleck
lulz
but...
it is a POSSIBILITY
NOTHING can be CERTAIN until source drops AND someone TRIES, but I'd have to IMAGINE that SOMEONE will be trying hard as HELL to keep this device rolling in development no matter how old it gets, many people hold this device dear to their hearts, it was one of the first WIDELY released nexus devices on MULTIPLE carriers including cdma. and even though it's a pita sometimes, we still have love for this ol girl, but right now, at this very moment, NO ONE can tell you 100% if it WILL run lollipop %100 stable or even what many would consider daily driver type of builds.
have I answered the question yet that's been asked a couple times and answered already just not in as many words? I'm NOT trying to be a ****, I REALLY would like to know if anyone is still confused about this situation?

you've tried really hard to be a ****, though
I haven't read others, I don't frequent this forum often, I'm not into custom ROMS.
I was just passing by asking this info. On this post there was nothing that explained the situation as you did. And there were no info on the first page of the Galaxy Nexus forum.
Thanks, it's a bit more clear. I'll drop by in a few months to see what's happening

Android 4.4 wasn't officially supported by Galaxy Nexus, yet we have a plethora of ROMs to choose from. I believe that 5.0 will be no different. It will take more time to get it to work because of the changes from other iterations, but we will get it. Not officially. Google probably won't give a hoot that there is a new driver, and just leave the device for dead. There is no money to be made from the amount of work that would have to be done. If it DOES get officially released, I'd be incredibly surprised.

blekm said:
you've tried really hard to be a ****, though
I haven't read others, I don't frequent this forum often, I'm not into custom ROMS.
I was just passing by asking this info. On this post there was nothing that explained the situation as you did. And there were no info on the first page of the Galaxy Nexus forum.
Thanks, it's a bit more clear. I'll drop by in a few months to see what's happening
Click to expand...
Click to collapse
yep, that tends to happen when I go posting after a few beers, apologies, but hey, I cleared it up right? that was really my main intention

fxxk it. we didnt even get kikat. The lollipop isn't for Gnex and I doubt google is going to do it . if they really are this "generous", I will bang my head against the wall just to make sure I aint dreaming!

randy6644 said:
fxxk it. we didnt even get kikat. The lollipop isn't for Gnex and I doubt google is going to do it . if they really are this "generous", I will bang my head against the wall just to make sure I aint dreaming!
Click to expand...
Click to collapse
NO ONE has said that Google will push ANY kind of official L update to gnex, when source code drops, custom Rom development will undergo to try and bring 5.0 based aosp roms to the gnex, which isn't unfeasible.

ashclepdia said:
NO ONE has said that Google will push ANY kind of official L update to gnex, when source code drops, custom Rom development will undergo to try and bring 5.0 based aosp roms to the gnex, which isn't unfeasible.
Click to expand...
Click to collapse
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.

randy6644 said:
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.
Click to expand...
Click to collapse
I'm looking to go back to 4.3 as well. Is it as simple as doing the normal procedures and flash a 4.3 rom? I heard of some issues downgrading while using 4.4 bootloaders and problems with SD card memory. Just want to make sure if there were any extra precautions you had to take before going back to 4.3

randy6644 said:
I heard of CM is not going to support galaxy nexus with lollipop due to the lack of maintainers. Maybe teams like PA might keep on with their supports. But I don't expect Gnex would run well on L coz it doesn't even on Kitkat. every now and then I see stuters and bugs . When I thought Gnex was dying and apparently showing its age, I flashed back to the stock 4.3 . The magic just happened and my gnex was brought back to life . yes the scrolling isn't as smooth as that on others roms but everything is fast especially when it comes to multitasking, it's great.
with that said , I mean even gnex is going get supports from some devs , what we could do with it is simply have a look at that and that will by no means be a stable and pleasant daily driver.
Click to expand...
Click to collapse
just the toro and toroplus variants.
maguro still maintained
so for someone to build for toro/toroplus isn't too much to infer. I can't see NO ONE not building for gnex at Some point
whether EVERYTHING is FULLY working or not is another story, but I'm sure it'll be usable

Mikey503 said:
I'm looking to go back to 4.3 as well. Is it as simple as doing the normal procedures and flash a 4.3 rom? I heard of some issues downgrading while using 4.4 bootloaders and problems with SD card memory. Just want to make sure if there were any extra precautions you had to take before going back to 4.3
Click to expand...
Click to collapse
No, there's not a single problem that i've seen. I just downloaded the factory Image and flashed it in fastboot mode.
but that will erase everything so just make a backup for your apps.

Funny that you say 4.3 runs well on your gnex because I've been running stock 4.3 for quite a while because I was fed up with trying to find the best custom rom and dealing with kernels and stuff.
4.3 runs like complete **** on my gnex and it has since I put it on there. It seems to get worse as time goes on though. I was using the Aviate launcher for quite a while but just installed the Google Now one to try that out and it seems much, much worse than Aviate in the performance department. I can be in an app, press home button and it will be close to 10 seconds sometimes for it to load, even with no apps present in the multitask/app switch thing. Blows my mind. I don't know why the performance is so bad.
I want to go back to android 4.1.2 because it's the only time I remember my gnex being quick.....but im having a hard time making that decision because of feature reasons.

naossoan said:
Funny that you say 4.3 runs well on your gnex because I've been running stock 4.3 for quite a while because I was fed up with trying to find the best custom rom and dealing with kernels and stuff.
4.3 runs like complete **** on my gnex and it has since I put it on there. It seems to get worse as time goes on though. I was using the Aviate launcher for quite a while but just installed the Google Now one to try that out and it seems much, much worse than Aviate in the performance department. I can be in an app, press home button and it will be close to 10 seconds sometimes for it to load, even with no apps present in the multitask/app switch thing. Blows my mind. I don't know why the performance is so bad.
I want to go back to android 4.1.2 because it's the only time I remember my gnex being quick.....but im having a hard time making that decision because of feature reasons.
Click to expand...
Click to collapse
It gets worse because the Java garbage colector is not doing what it's suppose to do and you have memory leaks so the memory gets full without a way of emptying it... To get around this, you need to restart the phone to empty the memory(usually daily or even two times a day). This HUGE bug is present onward since 4.2 for GNex, excluding 4.4 builds. So 4.1.2 will be best in that department.
But there is no need to go back to 4.1.2 to get this fixed (I couldn't bare it). Instead CM 10.1 has managed to fix the leak and you would be on 4.2 which is pretty similar to 4.3 and even 4.4 from the user end

I think Android 5.0 unofficially will continue.
There will be no further support officially. I "travel" too in different kit kat roms but always there were a bit of lag.
I return to cm 10.2 and my phone was brilliant, pretty quick.
Until recently that I install liquidsmooth that gone very fast for kit kat version.
I think now the kit kat versions will be enough stable. For lollipop, we will have to wait a lot.
we will see.

Source code just been released, so anyone working on, thx

I want cm lolipop!!!

The moment is arrived! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
Sent from my Galaxy Nexus using XDA Free mobile app