Develop Bugs

LoS with root

I've had my Epic Touch 4g for about 3 weeks now and I have noticed something outside the normal LoS threads I've seen lately. I only seem to get LoS when I flash kernels, mainly ones with CWM 4 or 5 or ones that are rooted.
The issue clears up as soon as I flash the stock EG30 rom. It's the same deal with either EG12 or EG30 modem.bin.
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App

I better hurry and comment before this one gets locked.
I've owned the phone for a little more then 2 weeks. I have had a total of 4 LOS events. 3 with a Zedomax kernel(all in the same day) and once with the latest lost kernel experimental. For the last week the lost kernel stable has had none. Can't comment on unrooted los because my phone was only stock for 15mins after unboxing.

haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol

playya said:
haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol
Click to expand...
Click to collapse
+1
10 char

alex6969 said:
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
As far as "here's my proof with evidence in anecdotal form" is concerned, that precedent has already been set.
The facts are this:
1.) Untouched stock units have had LOS (mine included).
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
3.) Kernels built from said source seem to exacerbate the problem
4.) You can have root AND the stock (pulled) kernel.
5.) Root binaries and/or busybox do not cause LOS.
6.) rooted+stock kernel installs seem to have the same occurance of LOS as bone stock, uninformed alarmist anecdotes notwithstanding.
7.) This has been covered in over 9000 threads already. Please search in the future.
8.) Samsung and Sprint are aware of the issue (in stock phones) and are issuing inconvenience credits if pressed and are supposedly working on a firmware to fix the issue.
Please pass this information on to the next student of science who presents his "proof" of this "discovery", as there will likely be more.

Now how do you like them apples ......my boys wicked smart .....
Good will hunting
But seriously please search and find the previous 50 threads that say the same uninformed thing ... If it was only a root thing would Samsung be fixing it ..... Hell no
Sent from my SPH-D710 using xda premium

I have had my phone since launch day and have only had LOS one time when it tried to go into roaming and never got back a signal. That was shortly after I rooted with a stock kernal. I have not had LOS since but I have never flashed a custom kernal or ROM. The phone has been mostly trouble free.

Where did you find the EG30 modem bin?

Ditto. WTF SamSprint?

daneurysm said:
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
Click to expand...
Click to collapse
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
daneurysm said:
3.) Kernels built from said source seem to exacerbate the problem
Click to expand...
Click to collapse
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?

mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
Thanks for the informative post.
I've been on Starburst+LoSTkernel for almost a week now with no problems. Before that I was strictly a pulled-stock kinda guy given my experiences. But I'll give that a shot and let you know. I get very infrequent LoS with stock kernel, though they do happen once every 2-3 weeks...usually a few times that one day. So, in a few days of very routine use (location/tower/times always the same, to a tee) I'll have a pretty good idea, assuming randomness doesn't factor into it as much as it could.

mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
I do get reboots after I get some texts, but, every other kernel (even stock) was doing this...I think it's the ROM...so, don't even worry about that. Later I'll nandroid back to my original stock install and flash this kernel on top and report back.

daneurysm said:
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
Click to expand...
Click to collapse
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.

mkasick said:
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.
Click to expand...
Click to collapse
Just to keep moral up I want to specify that "no more LOS than stock" means "stock rarely gets LOS and so far I have gotten absolutely none."
Good work man, thanks for the effort.

4.0.4 Data Drops Problem - Google doesn't care about this problem.

It is 20 days since we report a problem with drops after update to 4.0.4 . I judge that it is already too long and we should already have a fix. Now when all customs roms are using a new base, people who have this problem are forced to use an old 4.0.2 because with 4.0.4 phone useless. I think it would be good to start ask Google for any official statement because it is embarrassing for me that that they have such approach to theirs flagship phone.
This thread https://code.google.com/p/android/issues/detail?id=28133 shows that Google has completely no respect to us because there is now prove information that they even try to fix the problem.
Whats a shame Google.
Maybe should we start inform all gadget sites about this behavior?

Hey kid, stop being such a drama queen.
This is not how software development works. It takes time to iron out bugs. It takes time to first find out what causes the bug and then fix the bug and then it takes three times longer than that to make sure that the bug does not cause other bugs in the system.
Let's not forget how long 4.0.4 took to arrive in the first place. They originally released 4.0.3 and then discovered some bugs. Fixing those bugs apparently caused issues in 4.0.4 that no one saw coming, this means that the bug is not easy to find and is difficult to test for. They are doing it as fast as they can.
And let's not forget that not all devices are even affected. I've been on 4.0.4 ever since it was released and I've not experienced a single data drop. So it does not happen with all devices and may be region or carrier-specific. This makes it even more difficult to test for.

you honestly think they are able to push another update to a fix in 20 days?

kara mustafa said:
I judge that it is already too long and we should already have a fix.
Click to expand...
Click to collapse
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?

Just started noticing I have this problem.
I just reboot and it fixes, a hassle, but whatever. reboots pretty fast lol and only happens rarely

luftrofl said:
You seriously think 20 days is too long to identify the problem that doesn't affect all devices, develop a fix, test the fix, and push it out?
Click to expand...
Click to collapse
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.

adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.

adrynalyne said:
You do, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
I do?

Same problem here, have to reboot to fix it, any alternative suggestion?
Sent from my Galaxy Nexus using XDA

To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium

luftrofl said:
I do?
Click to expand...
Click to collapse
Lol, he must have misunderstood you.

No, it was a typo and I corrected it.
I meant to say, apparently, you do not. As in, he believes it only takes 20 days to diagnose, text, and implement a fix, which is funny
No fix is diagnosed day 1.
There is time to needed to find the problem.
There is time needed to create a fix.
There is time needed to properly test it, else other bugs show up.
Developers do not work 7 days a week.
Not every Android developer will be assigned to the fix.
There is time needed to ramp up an OTA again in two flavors, ICL53FD_to_IMM76D, and IMM76D_to_whateverthebuildnamewillbe.

Jayrod1980 said:
To be honest I think it does affect all devices. I say this because I was away on business when 404 came out. Where I was I was in a lot of cinder block buildings and frequently without full signal. I had hspa and umts during that time but it wasn't a 21 or 42 mbps area like where I live. I often dropped signal on 404 that I didn't when I had 403 there. Now, after coming home back to my area that has a better coverage and such, I've not had one drop in signal. I really think its dependent on the towers and saturation whether you have the problem or not. I would still like to see a fix from Google. In the process of gaining battery life, I think they messed up smart reflex in respect to how it powers the antenna.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No it does not.
It does not affect CDMA devices, and I have found some GSM users on this forum it does not affect. Folks here just think that XDA is the hub of the world, and therefore if there is a large amount of issues being noted, it must be everyone. Because you know...everyone posts on XDA and other phone geek sites. I am not saying the bug isn't real, just that it isn't happening to EVERYONE.

Theshawty said:
The radio seems fine since I tried stock 4.0.2 with the XXLA02 radio (from the 4.0.4 package) and everything worked wonderfully.
Click to expand...
Click to collapse
It still could be the radios. There is a reason they change radios with each release.
For example, 4.0.4 by itself for CDMA users does not see a signal improvement. 4.0.4 radios on a 4.0.2 or 4.0.3 rom does not see signal improvements. However, 4.0.4 rom and 4.0.4 leaked radio firmware sees a signal improvement.

luftrofl said:
I do?
Click to expand...
Click to collapse
It was a typo, but you knew that.

Theshawty said:
Lol, he must have misunderstood you.
Click to expand...
Click to collapse
reading is difficult..

Some people have reported getting the IMM76I update starting about an hour ago, so for those with the issue, it may help you.

adrynalyne said:
You don't, apparently.
1. It does not affect all devices.
2. Lets rush a fix and not test it so other issues can occur?
3. If the issue is a radio problem, Samsung needs to fix it for Google to push it.
Even if developers worked 24/7 including weekends and holidays, that is pretty humorous to think that.
Re #3:
Samsung does nothing fast other than fatten their wallet. Yep, I said it, Google does not code radio firmware.
Click to expand...
Click to collapse
He was saying it with sarcasm. You should probably learn what that means before replying.

hotleadsingerguy said:
He was saying it with sarcasm. You should probably learn what that means before replying.
Click to expand...
Click to collapse
He wasn't being sarcastic. Nice try.

luftrofl said:
reading is difficult..
Click to expand...
Click to collapse
Sure is, considering I said several times it was a typo and you still didn't comprehend.

Has development for the glide gone belly up?

I've loved this phone since I got it, and was terribly excited when it was successfully rooted. Many roms sprung up by a few devs, such as dman, and thegreatergood. But now, dman is prioritizing his daily driver, which is fine. Thegreatergood has disappeared due to personal reasons, which is also fine. I don't demand updates or anything, however it seems all the other smaller devs abandoned the device. Thegreatergood has 5 jellybean roms in the dev forum, and sadly none of them have been touched by anyone in almost a month. I'm starting to see issues with every 4.2.2 rom spontaneously fast booting, and there is no mention of any updates on Jelly Bean.
Basically, what I'm trying to ask is, is anyone out there working on something? I know asking for ETA's is a no-no, but I'm just asking if anyone has adopted development for this device? I use this phone for everything, and I'm not able to change to some of the more "preferred" devices such as the Nexus series. Is there anyone who knows of anything coming soon?
Sorry for the little wall of text, I'm just kinda sad that the glide seems to be dying off.

Worried about this too, the DEV section of forum seems to be totally dead.
AT&T seems to abandon this device too, since hasnt release a proper ICS ROM (It was like "Oh, ICS didnt work, lets leave it on GB").
Have to stay at GB because of that

dman with do what he can, I am sure. Other than that, I think development is dead.
Sent from my SGH-i927 using Tapatalk 2

Moving off from rhis phone onto something nnewer
Sent from my SGH-I927 using xda app-developers app

Are there any decent QWERTY phones out there or any coming up this year?
I love this phone and it seems like there is no suitable replacement out there.

i would have to say that development isnt exactly dead... but its dying quickly... this phone isnt the main focus of the devs that hash out roms and tweaks for it anymore (for some not sure it ever was)... its an older phone now, there are bigger better phones out there (have been for a while). granted this is probably still the best qwerty phone, the interest to develop full time for it isnt.
i am sure here soon dman will put out whatever he is working on.... eventually...
in my opinion dont expect a 100% fully functional custom rom that isnt based on the stock ics... the only one i could say that is there is literom... all others out there arent even close.... we wont ever see 100% working JB...

Yeah, for a while I was checking in daily and flashing some patch, mod or rom like once a week! I am still happier on CM 10.1 than I was on GB or even the very nice ICS literom, but it would be great to see the list of fixes get worked on like they were.
I guess we are being put out to pasture, but I sure appreciate all the Devs did to help keep this phone feel great as long as it did!
Sent from my SGH-I927 using xda app-developers app

I'm part of the Covenant Team as well as a co-dev for the IcePop rom. All I can say. Is that I know most of the other devs are either spending more time with their families with the near stable roms having been released, and maybe a few are back in school for the spring semester. I personally looked into the graphical and appearance of the roms, not as much of the coding due to computer technical issues and spacial issues with my hard drive. But don't give up hope just yet! Our glide may have a comeback soon. who knows. There are still a ton of we glide users in this community that are working behind the scenes to push out either patches or completely new roms.

Nevermind.

You are kidding right? The dev forum is full of different roms for all tastes, ICS, JB, the like. As far as I am aware, nobody got a "free phone" as you say. People just donated to dman (who paid for his Cappy out of his own pocket), and rightfully so because he and thegreatergood put our phone on the map again with great ROMs and updates.

Vanilla Rootbox has been my DD for a while now. The 4.2.2 roms have very few issues and none of those affect me fortunately.
Sent from my SGH-i927

braintweaker said:
Worried about this too, the DEV section of forum seems to be totally dead.
AT&T seems to abandon this device too, since hasnt release a proper ICS ROM (It was like "Oh, ICS didnt work, lets leave it on GB").
Have to stay at GB because of that
Click to expand...
Click to collapse
Hmm, I don't think this is true. I got the busted ICS update for these devices when it was out before it was pulled. It was then posted a few weeks later again with the proper fix. You have to go through Kies, but you should have an ICS update for your device, at least to 4.0.4..

Really hope it hasn't died but at this point I am considering moving back to ICS just so my sound works properly. Sucks. If my VOIP calling worked correctly, CM10 is exactly what I want. Its so smooth and less bloated than the official ICS ROMs. I wouldn't even be considering a new device this year if we could get the sound issues fixed. But its gone on so long now that I would just like a straight answer from the few devs we have - is this issue ever going to be addressed?
I'm as happy as anyone to have any sort of development for the Glide and none of the developers owe us a thing. But this has been an issue for so long now, I wish we could just get a straight answer. Working on it, can't be fixed or they just don't care. Any answer is better than nothing at this point.

I really like the glide, because a like the tegra graphics for games, but, i like switch roms too. I hope that someone come to help us. Maybe we must wait a little more

Hi to all. I've tryed different roms till now. Im a noob still regarding android development, but i'm trying to learn a bit. I would definately love to have the VOIP calling enabled, photosphere less lag at wakeup for 4.2.2 and no lag for voice calls. Regarding photosphere, i've tryed it with every rom available i set permissions and everything. As far as what i observed is on 4.2.2 I can get 1 photo and then the app simply close. On ICS i can take up to 7 - 8 pics and after that the app close.

Gizmokid2005 said:
Hmm, I don't think this is true. I got the busted ICS update for these devices when it was out before it was pulled. It was then posted a few weeks later again with the proper fix. You have to go through Kies, but you should have an ICS update for your device, at least to 4.0.4..
Click to expand...
Click to collapse
I would be happy to be wrong, but as far as I know ATT has released ICS with much errors, after that released the GB again to roll everyone back.
Also, all the versions of ICS have the deep sleep issue, so they are totally unusable as a phone itself.
People that asked ATT support for a solution had unacceptable answer like "Reboot your phone once a day".
As for Kies, my phone is not recognized with any rom to update so I do everything manually.

braintweaker said:
I would be happy to be wrong, but as far as I know ATT has released ICS with much errors, after that released the GB again to roll everyone back.
Also, all the versions of ICS have the deep sleep issue, so they are totally unusable as a phone itself.
People that asked ATT support for a solution had unacceptable answer like "Reboot your phone once a day".
As for Kies, my phone is not recognized with any rom to update so I do everything manually.
Click to expand...
Click to collapse
The best answer I can give... Actually read the development section for our device...
ICS IcePop Rom -modded UCLJ3)
UCLJ3 rooted (ICS -the fixed one-)
you guys complaining about ICS need to read up through the development forum before coming here to complain...
as for JB users (including myself)
Liquid Smooth (has working panorama, video (with sound), sound recording, and skype like apps work)

To be honest, liquid smooth i dont try it a lot, but in the issues say, that skype doesnt work

Rawr0w0 said:
you guys complaining about ICS need to read up through the development forum before coming here to complain..
Click to expand...
Click to collapse
Lol, and what?
I've mainly been reading the dev section for all the time, and tried most of the roms availible there.
Stock and modified 4.0.4 has problems with the GSM deep sleep issue, so do all the roms above 4.0.4 (4.1 and 4.2). All this makes a good toy out of the phone, but looses the main purpose - recieve calls and sms on time.
And yes, I've already tested the 4.2.2 version of liquid smooth, but skype and bluetooth are not working, as stated in OP.

braintweaker said:
Lol, and what?
I've mainly been reading the dev section for all the time, and tried most of the roms availible there.
Stock and modified 4.0.4 has problems with the GSM deep sleep issue, so do all the roms above 4.0.4 (4.1 and 4.2). All this makes a good toy out of the phone, but looses the main purpose - recieve calls and sms on time.
And yes, I've already tested the 4.2.2 version of liquid smooth, but skype and bluetooth are not working, as stated in OP.
Click to expand...
Click to collapse
use Wake My Android Pro < for the deep sleep. it's a free app and it works on everything from GB + and it works

[Q] CM Roms / Call Quality

Is anyone else experiencing an extremely muffled in call mic with CM roms? I have tried several different CM/CM based roms and all are doing the same thing. Both 4.3 and 4.4 roms. Wife started complaining that she couldn't hear me soon after I flashed a CM rom, so I left myself a voicemail, flashed back to a stock based rom, and left another voicemail. Difference is night and day. I have tried reflashing the stock radio over top of the CM flash, but no noticeable difference.
Anyone else experiencing this, or have any ideas on how to fix? This is very annoying, but not enough to make me give up Kit Kat. I usually just talk louder into the phone.

Are you on T-Mobile?
Sent from my LG-E988 using Tapatalk 4

Sorry. I should have included that in the original post. E980 on AT&T

argolfermd said:
Sorry. I should have included that in the original post. E980 on AT&T
Click to expand...
Click to collapse
It's a known issue with no fix in sight. What's worse is using the speakerphone. There's a huge amount of ocho.
After struggling with this device for some weeks, I finally sold it, and honestly, do regret that. Even with stock ROM, it was a great value for the money, but I'm sorta hoping for something similar in the future.
IF the LGOG Pro had an unlocked bootloader and was as fully supported and functional as other devices by CM/AOSP, it would probably have been the last device I ever bought until it literally could not power on anymore.
It's such a shame that LG has abandoned it the way that they have, but if you've ever wondered why LG is getting their ass handed to them in the smartphone market by Samdung, this lazy attitude toward supporting fantastic hardware is a good example to illustrate why.
Their solution is to simply leave the market and put their focus elsewhere.
So sad.
Where's the company that understands how powerfully they could position themselves in the market by being friendly with the Open Source community?
They don't exist.

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