[Q] State of 5.1 Lollipop in our Galaxy Nexus - Samsung Galaxy Nexus

Hello.
Well, I've been reading the threads of the ROMS with recent updates but to be frank there's some confusion and seriously too many pages to read and get the whole idea of the state of lollipop for our gramps nexus.
What I got from all the search and reading:
- Most roms have problems with offline charging and video recording (green lines?);
[Q] - Is this only happening in the Galaxy Nexus or is every device experiencing this (apart, obviously, from the officially supported ones)
- There's no f2fs support (or it is partially missing);
[Q] - Is f2fs really important performance wise? Has anyone tried to convert the roms and gave feedback? How is it?
I'm using kitkat with f2fs and I did notice some improvements over ext4 that's why I'm asking if it is the same with lollipop or it is now redundant.
Well, I know that those questions could be easily answered by testing all the roms and I am really wanting to do that but I'm using my nexus as my only phone and daily driver and I don't have a replacement phone in case something goes wrong so I can't really test and flash like crazy with roms that are still beta. That's why I'm asking this, I want to get into the lollipop world but I can only to that when lollipop reaches a somewhat stable state without major lags and no bugs (like kitkat has been since early last year).
I also would like to suggest a creation of a role thread for ROMs, making the threads graphically similar. That would help the developers and the users since the users would have the info they need in places they are used to search for, and developers wouldn't need to think of ways to put their info on, they could use the pre made model and just edit it with their info and links.
I would also suggest an update in the thread titles (rom ones) since there are some threads that don't have updated dates of "last build" or android version and it becomes confusing. I know that the developers have more important things to do but they don't need to do it themselves, I believe that there is many people here who can take care of that by editing it acording to the respective developer's standards or orders, I wouldn't mind to do it for example. And that could also incentivate the non developer guys to actively contribute to the forums organization.
Well, best regards and sorry if I was not so clear as I'm not used to long talk in english

Related

*Known Issues*

I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
chicmagnet2k4 said:
I was just thinking looking through all these new roms or just roms in general and it hard to determine which one on many levels. I just thought of an idea we should have a known issues for each rom or atleast the newer ones. I think it will be easier for people to address the problem or atleast see all the known issues with that rom. I think this would help out the developers alot too. This will save me 78 pages of looking through to see known problems. So it will just be there within a few pages.
Click to expand...
Click to collapse
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
jws3 said:
Most of the developers have a list of known issues and what is under development for the next revision at the beginning of their thread. There is no easy way to select a new ROM. I have narrowed my search for a Version 6.1 ROM to a couple of developers.
I also have been following the experiences of other users that have have a similar confirguration to mine. For example, same country and same service provider.
Click to expand...
Click to collapse
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
chicmagnet2k4 said:
I'm not meaning just known issues but people have alot of other minor or they dont know what to do issues ie battery drain sync keyboard or running application issues and when there hidden in between 56 pages its hard for people to see what some of the issues that might be problems with that certain rom or it harder for developers to have to go through 32 pages of stuff to find what they need to address or fix. It's just an idea maybe to implement with newer verison or newer roms.
Click to expand...
Click to collapse
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
larsuck said:
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
There is a lot of truth in what you say. ROMs on their own are usually ok; its the combination of software and install methods that leads to problems. The thing is no matter how hard you shout people always assume that its the ROM or the cook.
Case in point; I have been using Kin0kins ROMs for a little while now whilst I wait for Schaps to produce his killer ROM with the 21st century interface. K's roms are rock solid stable and fast and yet I had an instability problem after the last install.
Going through the painfull routine of "forensic investigation" of my install I discovered two things:
- I had inadvertently loaded up some software onto the SD card which had known instability problems if installed in this way. Once sorted, hey presto, one issue solved.
- 2nd issue was caused by a similar install but using software that was polled on a regular basis. Once the device went into hibernate mode it crashed, simply because the card could not wake up quickly enough to handle the software request.
Loading up old versions of software incompatible with WM6 is another popular one that tends to cause issues. Bottom line is there just is no substitute for rigour and research prior to software installs to ensure the good operation of a rom with the benefit of stability.
WB
larsuck said:
The developers here usually do a pretty good job in following their own ROM's thread so they know what trouble people are having. Incidentally, that's one of my benchmarks for a good ROM: a cook that watches his thread and responds to people in trouble.
The problem is that 9 out of 10 people with problems have either third-party software conflicts or hardware problems or are just plain ignorant. (To be fair, I have of course made my share of ignorant posts as well.) To say that these are ROM issues is a little unfair I think.
Click to expand...
Click to collapse
That is somewhat true but isnt all of my arguement I am a new member here and felt overwhelm when trying to look for a nice stable fast rom to flash and I thought about what made it hard for me. Which was there are tons of un needed comments so its like you have to go through 77 pages trying to see what this rom is about. Its overwhelming and crazy, if my way isnt all the way complete or just a bit too much it would be great for someone to think of a way to make it easier for a newbie or just people in general.

[Q] Hi! T-mobile GS III Question

i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
o-k said:
i am a super omega ultimate noob lv. -99. i am wondering how to check on the latest status of the GSIII stable roms. i would like to know if/when CM will get the roms first or if xda gets them first. i like stable roms because i am a noob. my noobness knows no bounds. please help. i do dontate. thank you.
Click to expand...
Click to collapse
Xda is just an outlet where people choose to post roms.
To check on the latest status of roms, you need to open the threads and read the OP. You also need to spend at least ten minutes reading each thread, That will tell you how stable each rom is and what kind of results people are having.
Sent from my SGH-T999 using xda premium
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
shrimants said:
Is there a place for specific roms that we can see a list of all known bugs? I've been trying to check on, for example, CM10, paranoid android, and AOKP in particular and havent been able to find any bug trackers at all. Without knowing what bugs there are and what will/wont affect me, I'm too hesitant to try any of the roms and have been suffering through t-mobile's dual "update ready" and "update needed" constant un-clearable notifications. I cant even apply the stock updates because I debloated and applying the update fails because I dont have the apps that the update is attempting to update. Updating would involve doing a full factory reset back to stock and THEN updating, which means i'm probably better off simply waiting for samsung's official JB update to roll out in the first place
Click to expand...
Click to collapse
Actually that would be a great idea. It would help out the entire community.
Right now the way things exist, you pretty much have to read through an entire rom thread to determine the benefits/bugs of any given rom.
You could, for example, start a list for any particular rom.. read the entire thread, then make your own thread detailing current known bugs and post it in the same forum. Then the OP of the rom thread could post your link in the first post making it easy for everyone to find.
That would serve two purposes - you would learn the information you're seeking and also become an instantly appreciated contributor to the site.
Sent from my SGH-T999 using xda premium
I'm surprised the rom developers dont already have a system in place, though. The scope of the projects are presumably gargantuan collaborative works. i kind of assumed that they must have some sort of a bug tracking thing that they use between them. That bug tracking thing is what i've been venturing to find. There are a ton of user-specific bugs that I have no problem digging through the forums and figuring out myself, but what i'd love to see with roms is a list of "this is what we know isnt working yet. dont talk to us about this. we are working on it." or at the very least, "when you flash this rom, if you would like to help, run this command and upload the output HERE so we can fix some bugs we know about".
I'm coming from a linux world and it is very disconcerting to me to flash a rom, encounter a bug/error, and not be able to look at any sort of an error message or do anything to fix the problem except reboot/wipe/reflash and hope for the best. thats a very windows-y mentality to the whole thing, and i feel like if we're running linux on the phones we should be able to get a bit more involved in fixing our own problems a bit better too.
I guess what i'm trying to say is, i'd like to help and i have no clue where to even begin. with archlinux theres a beginners guide but with these roms its more of a "watch this youtube video and follow this tutorial but god help you if anyone thinks you are complaining about what people are doing for you for FREE".
EDIT: I found CM10's issue tracker, but there isnt anything specific for the GS3 there. The flicker and picasa sync issues arent even mentioned. Obviously Paranoid Android and Kang will have the same bugs as CM10, but im assuming that they'll have their own bugs introduced after they add in their own features and such.
ok.
ingenious247 said:
Right now, CM10 nightly 25 is working great
26 has exhibited a few irritating bugs but I haven't had any problems with nightly 25
Give it a run, it's phenomenal IMO
Click to expand...
Click to collapse
thanks! will it be on the CM website or here?
o-k said:
thanks! will it be on the CM website or here?
Click to expand...
Click to collapse
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
i have a question
ingenious247 said:
Two things - one, if you're going to do a lot of flashing, and especially with CM10, you will want to install ROM Manager from the Google Play Store. It will make managing your updates/downloads easier
Two, there is a dedicated thread to CM10 in the "T-Mobile Galaxy S III Original Android Development" forum here:
http://forum.xda-developers.com/showthread.php?t=1778217
Read a lot first - before you do anything.. unless you are a very experienced user.
If you have specific questions I will be happy to help
Click to expand...
Click to collapse
i've downloaded the CWM pro and the TB pro. i was wondering what exact ROMS i can use. There is also the difficulty of understanding which rom is exactly which. Is there a way to view the Change log? i'm a super noob. i'm really sorry.
Changelogs won't do you much good.
I recommend flashing everything through CWM (make sure you have 6.0.1.2 Touch - in my signature if not). I wouldn't use ROM Manager at all. Having automated tools is great, but learning how to do it yourself is even better. Plus, if you break something, knowning what you are doing makes it easier to fix. Automated tools hurt more than they help.
As for roms, your options pretty much are as follows:
CyanogenMod: AOSP, the closest thing we have to the stock Google firmware.
AOKP: Pretty much CyanogenMod with some extra options. Nothing extraordinary about those extra options, just some nice things like center clock, swagger toggles, and unicorns.
MIUI: iPhone look for Android.
ParanoidAndroid: Scalable - for tablets (imo).
Then you have the neverending amount of customized stock (TouchWiz) roms.
They are all under constant development. If you want "stable", stay on your stock firmware. All of the roms listed above are stable enough to use as a daily driver. They all have threads in the two Dev forums. But if you don't know what to pick, use CyanogenMod.
I still think ROM Manager is a great tool, it's how I started years ago and I still managed to learn what I needed to over time flashing manually
Sent from my SGH-T999 using xda premium

cyanogenmod-10.1-is-not-perfect

does anyone know, or have a reason, or encounted in a problem with CM 10.1 cuz i recently installed CM 10.1 stable on my ATT S3 and it keeps restarting itself after 20/30 minutes tops, maybe longer but once in a while it randomly restarts itself
installed everything perfectly, no reason to be acting crazy since its from CYANOGENMOD TEAM but ROMS are not perfect or as good as STOCK ROMS (that come pre-installed on your device)
any issues, bugs, any kind of thing you have noticed with cm 10.1 yu can post it here
new upcoming features, fixes, what should be there or shouldnt be there, whats missing everything
HELPING EACH OTHER SOLVE SIMPLE/SERIOUS with CM 10.1 and above ISSUES
am currently running Synergy ROM 4.1.2 Stock rom with ZIGGY KERNEL (clocked at 1.3 Ghz) and its pretty sweet, stable, good battery, perfomance is top notch for a stock based rom that come with all samsung boatload
SO DUMP ALL THE PROBLEMS/SOLUTIONS IN THIS NEW THREAD FOR CM 10.1 AND ABOVE - ATT S3 I747
ANYTHING YU THINK IS COOL/AWSOME ABUT CM 10.1 ON YOUR AWSOME S3 GET IT HERE
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Domoo said:
Or just post them in this thread which already gets developer support.
http://forum.xda-developers.com/showthread.php?t=1778270
Not all phones are created equal. You should try the newer nightlies since they're just as stable. I haven't had any issues with Cyanogenmod. The reboot bug has been squashed a couple of months ago for me.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4 Beta
Click to expand...
Click to collapse
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
winosxbuntu said:
thanks for that, but this thread is based on everything to do with cyanogenmod 10.1 and above, clearly i am not a fan of nightlies as to do with updating my phone every second (thats a hustle for me cuz i gotta backup everything/reinstall everything again) and not to mention i have better things to do than just updating to a new bulds everyday or trying new roms
ihave too much variable things on my phone to delete for reasons like nightlies
THE REBOOT BUG STILL exists quite suprisingly for me as you dont have problems with nightlies or the reboot bug too
the thread yu mentioned is helpful but new ideas, new thoughts, easy to find a solution for a problem/question and navigate easly without having to dig it up tens of pages, a new thread with new people/same but fast replies, nice to workaround with.
am not trying to break any XDA rules/regulations or whatsoever by posting/asking a question or starting a thread thats already there(content and information that i need) but a new thread thats clean, new ideas about the rom, new problems/solutions is what this thread is all about
PHONES COULD BE EQAUL BUT ROMS ARE NOT SAME/DONT WORK SAME ON XXXXX PHONE
Click to expand...
Click to collapse
First and foremost, no OS or software, including android, is perfect. Secondly starting a new thread does not mean it will not get "cluttered" either. The ROM thread for CM is not as bad as you make it out to be. The idea is that the newest material covers the most recent nightlies. It is not that difficult to go to the end and work backwards. In regards to you random reboots, look on JIRA as it exists for this very reason. Take a logcat and report on JIRA if not already covered. JIRA gives you all the bugs reported and their current status towards a fix. This is a wasted thread for this very reason.
As far as ROMs being different...that is the point. Each developer(s) put their own spin on it. That is what makes these development threads so great. You can look for a ROM that you like best. Some ROMs are more universal (but you still need your device specific version), such as CM, while others are device specific.
And phones are not created equal. They may look the same, have the same hardware specs, and all else seemingly equal, but slight manufacturing imperfections make them different. Two people can have the exact same phone from the same carrier, manufactured on the same day, but due to some ever so slight differences from imperfections, ROMs will work differently on each. For instance, in your case CM reboots randomly. For others, such as myself, this is no longer an issue. However, it is possible that another ROM will work great on your phone but not on mine.
While you say CM is not perfect like the stock rom, the stock rom is not perfect either. I have AT&T and the stock rom has several issues. The lockscreen securities can be bypassed, the alarm likes to not work at random times (software bug), and every now and then I get a battery plummet after a phone call when the phone switches between 4G and 4G LTE. Others may or may not have these issues but they seem to be rather common (the security bypass affects all S3 phones that were on 4.1.1 that I am aware of). For this reason I stick to custom roms because I do not have these problems which I personally view as severe for me (Aside from protecting my data and enjoying battery life, I rely on my phone as an alarm clock). Now that 4.2.2 has come as far as it has, it is stable enough that I can use it as a daily driver. I knowingly accept any bugs that are there because typically the ones that exist do not have a large affect on me, if at all, unlike the stock rom.

[Q] Good day XDA Community

I'd like to introduce myself being both a new XDA community member as well as a relatively new android owner, having recently purchased a Galaxy Tab 3. I had been referred to this site through my cousin having been interested in rooting my device. I have had some prior experience with installing custom software etc, on other devices (none of which were android) so I came here looking for information.
Now I've read your forum rules about searching and I did as such before proceeding with this thread, so please bear with me. I still however have some questions that I would like the community to answer or point me to the relevant thread(s). Any assistance is greatly appreciated.
To begin the device I'm using is the Galaxy Tab 3 SM-T210R US version. I've seen threads about flashing the device with a ClockWorkMod using the Odin software, which i found in this thread and this thread about the custom Crash Rom.
Is there a difference between a ROM and the OS or are they one in the same? I understood it as being the custom firmware/OS for the device, henceforth replacing the Official OS, mine being 4.1.2 Jelly bean. Correct me if I'm wrong here.
Probably should have asked this first but, for anyone with the Tab 3 device, I understand it has a lot of unnecessary apps (at least from my perspective) which can't be removed, only reset to their factory installation. I understand that rooting means that I would be the superuser of the device and I would have complete control over what affects my device. The question i pose is about RAM usage and background applications. Currently, having 1GB ram, I average around 697/833MB of ram usage. The 833MB i assumed was the max allowed to other applications and the remainder for system applications? Again correct me if I'm wrong. When clearing background processes through task manager, the highest i've removed was around 31 applications (so it says) which reduced the usage to about 497MB/833MB.
So the final overall question here is, would rooting my device be worth it and if so, how is it beneficial? Like i said, I've read a few threads before coming here, but i still long for a little direct feedback, be it from current users of the same device or anyone else. I was also going to contact the thread owners of the two threads posted above but went along with this first just to see how it goes.
Thank you for your time and consideration. I apologise for the wall of text but I tried to get what I was a little edgy about into one thread.
For me I rooted because of being able to use certain backup programs and adaway. I do like looking at the system files and exploring (hacking) game files for fun.
Sent from my SM-T210 using XDA Premium 4 mobile app
After rooting you'd be able to uninstall basically any app you choose (although some are necessary for the system to function), thus having more free memory and a faster/smoother system. Also there are a lot of apps that require root.
You could say that the ROMs are the OS (Android) + apps. Basically every ROM (including the offcial one from your device) is customized, I think only Google's devices have clean AOSP.
After you install CWM you can make a backup of your current ROM and install a different one, if you don't like it you can just restore the backup.
Thanks for the responses and sorry for my late one. I can say i understand the processes a lot more in depth as opposed to when i wrote this thread, courtesy of a lot of research lol.
But thanks again.

Galaxy Note 2 N7100 and CM12 and some general question

Hi,
I'm new to the forum so I wasn't allowed to post my comment/question directly to http://forum.xda-developers.com/galaxy-note-2/orig-development/cyanogenmod-12-alpha-1-n7100-t2949644
I'm having a Galaxy Note 2 (N7100) which currently runs Cyanogenmod 11 directly from cyanogenmod.org. I'm quite happy with, but I would still like to move on to 5.0 or 5.1.
The post I mentioned above looks really promising but with more then 800 pages of discussion, it is a bit hard to really get a understanding about the state of the build.
Is there also some kind of overview page which tells me what works and what (maybe) don't work. I want to be sure that I don't install a CM versions and then some important parts doesn't work. If such overview page exists, it would be great if someone could point me to it. If not maybe someone can give a summary about the current state and if it can be used on a productive phone on a day-to-day basis or not.
Additionally I have two more general question.
1. I seems like a lot of work happens here to develop newer Cyanogenmod versions for the N7100, at the same time the development at cyanogenmod.org seems to be stalled for this device. Why all this great work happens outside of the official Cyanogenmod community and why people don't take over the development at cyanogenmod.org instead of building their ROMs here at xda-developers? I just want to understand how all this is related to each other because from a user perspective this can be quite confusing.
2. for my CM version from cyanogenmod.org I get updates automatically when they are released over their release channels. How does it works if I install a version from here? Will I get notifications or updates if they are available? Or will I have to look for it manually and install it every time again manually?
Thanks a lot for reading my question and for the answers!

Categories

Resources