Develop Bugs

[ROM] CarbonROM Linaro GCC 4.7/-O3 JB 4.2.2 Unofficial 8.03.13

As good a place as any to post this.
Pio-masaki.com is being shut down due to a Cease and Desist order sent against the host by Google and homeland security. I have no idea why, however until this is sorted out, and to avoid any possible or further legal issues, the site is down for a period of time that can be a day or forever. This includes any and all ROMs, kernels, gapps packages, for any and all devices, that were hosted on pio-masaki.com.
I apologize in advance for this as I know some ROMs are only available at pio-masaki.com, but it is out of my hands, the host has to consider their own safety, and has my 100% agreement and backing in taking down the site until the matter is resolved.
As this is a very large matter, and one that has us incredibly scared, I'm retreating from android for the time being, until I know what it was that I did that was illegal, and may return once this is cleared up and blows over.
After this is cleared up the hosting for pio-masaki.com may still remain offline as the hoster has some personal issues with me at this point and may or may not continue to host for me, should we resolve our differences it may return.
If by some chance Google or whoever sent the C&D notices this, I urge you to contact me as I was responsible for what was hosted, and would genuinely like to know what the issues are so we can get them resolved immediately.
I will be making similar postings or editings to any other ROM threads that link to pio-masaki.com.
What is CarbonROM?
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
1.6 is a pretty big update for us! Check out the changelog on our goo.im page for more, but here are the highlights:
-PIE
-HALO
-Floating Application windows (long press app in recent apps list)
-Lock screen rotation is back
-Dark Carbon! Huge props to Slim Roms for coming up with this unique and awesome feature.
-Lockscreen theming
-CM skinny battery is back!
-Volume key lock on silent mode option
-Backup tool - if you're flashing a new version of Carbon and already have the required version of gapps installed, it will be backed up and restored during install. This applies to system apps and custom host files as well. Please note that you should only dirty flash from Carbon to Carbon. It's ok if it's another version or a nightly - just not over other roms. Super handy for you crack flashers. Make sure you've got the most recent Gapps though, and if you're flashing from a factory reset, you'll still need to install it after install of course.
-Long pressing the "clear recents" button clears the cache
-AOKP's awesome new navbar settings
-NFC polling mode for when you want to keep your screen off and scan tags
-MMS and call "breathe" feature. Makes the notification icon fade in and out.
-Mute dings when changing volume
-Disable/enable CRT effect on screen on/off.
-3rd party keyboard bug fixed
-deodexed again
-stability and speed enhancements
-a million other little things as well - we basically don't even sleep anymore.
*not all features are available on the A100 tablet.
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users!
Who is Team Carbon?
andros11
BigShotRob
dg4prez
Kejar31
mattmanwrx
morfic
nocoast
pixeldotz
slick_rick
winner00​

Instructions:
Please clean flash this, there's so many extra settings that dirty flashing will likely cause problems. If you dirty flash, please don't report any issues until you flash clean and the issue occurs again!
Please use a proper 4.2.2 Gapps package, using inversed or any modded versions can and likely will cause issues, please use the current 4.2.2 from goo.im, if you use inverted or modded Gapps, please don't report issues until you clean flash with a proper package from goo.im!
Download the ROM
Download the current 4.2.2 Gapps from goo.im or pio-masaki.com
Place files someplace useful
Boot into recovery
This part assumes you know how to operate your installed recovery
Wipe system
Factory reset
Wipe dalvik
Flash CarbonROM
Flash Gapps
Reboot
Let settle for a few minutes after booting
Setup device as usual
If you have issues on first boot, flash the ROM only, then after it boots, reboot and flash Gapps then manually setup your device in settings.
Change Log
8.01.13-B1:
initial build for experimenting, didn't boot.
8.01.13-B2:
Next try, boots, SystemUI crash makes it unusable, no nav/status bars
8.02.13:
WiFi works, SystemUI persistent crashing still makes device unsable.
8.02.13-B2:
BT, WiFi, sound all work, persistent SystemUI crashes still occuring.
8.03.13:
All works, SystemUI crash fixed, PIE crashing, battery mods missing, Torch doesn't work.
8.03.13-B2:
All works, Torch works
8.03.13-B3:
Fixed PIE crashing, fixed missing battery mods. Rom is now fully operational.

FAQS
If you didn't read the bugs list below, go down and read that now, asking the same questions over and over is a trademark of xda and I hate it, please read the change log and bug list before posting questions or reporting issues.
Q. I want to use this build(s) as a base for my ROM, or I want to host/re release it in another country/forum, can I?
A. You may, but only if you send me a PM about it first. I've had a bit of trouble with people taking credit for my work, and I'm getting sick of it. I don't mind sharing and whatnot, but taking my build, adding a build.prop tweak and releasing it on another forum with no mention of my name is not acceptable. As for re releasing on another forum, you may if you just shoot me a link to the post about it, I would rather you link directly to this thread if possible. For those posting in forums of other languages (I know some users might in Russia, for example, use my ROMs) feel free to post for your native languages, and please include a link here also.
Q. I want to report an issue, can I just post it in your thread without reading or doing any basic troubleshooting, googling, reading or wiping?
A. Well you CAN, you may be ignored or flamed for it. Please read above, and please read the Bugs and Change Log lists before reporting anything. Please flash a clean download, flash a clean wipe, and don't restore stuff from TiBu, thats basic troubleshooting, check if the issue persists, if it does, then feel free to post about it.
Q. Is this daily driver ready?
A. Can't answer that, what a person needs from their phone varies from person to person, what I may consider fine for my use may be 500 kinds of broken for another user. Example, I don't use my camera often, maybe once a month, and my BT has never been turned on for the last 5 devices, for me broken BT audio and camera doesn't make it a non daily driver ROM. Please read and decide for yourself if features included outweigh the broken, or if broken things are required for your comfortable use of your device.
Q. How can I build my own versions?
A. I'm not going to write a guide, I did write one for CM9 which is 99.99% still a working guide aside from source urls for updated jellybean. Otherwise there are plenty of very well written guides on how to build ROMs, individual questions about build it can be asked here if you wish as this is a development thread.
Q. Can I use -insert kernel name here-?
A. You can probably use any kernel you want, but WiFi and such won't work. If you don't mind no WiFi feel free to use any kernel that will boot.
Q. Your files all download as index.php!
A. This happens on certain browsers, namely the stock browser and Chrome. You can either use another browser (naked and dolphin don't do this) or simply rename the file to something useful, like "piostotallyepicawesomesaucedrizzledromthatrocksyo urass.zip"
Bugs:
MIC doesn't work
Camera crashes when you change resolutions
WiFi may not connect after being turned off, needing a reboot to come back up
Google Search doesn't work (no MIC)
Headset MIC also doesn't work
ROM may get stuck booting, powering off and on will have it boot again, not sure where this is coming from.
More, I'm sure.
Downloads:
Please visit http://pio-masaki.com for all my ROM builds
CARBON-JB-UNOFFICIAL-20130803-2330-a100.zip

WHOA BUNDY! This ROM is amazing! Finally some 4.2.2 action on the A100. Thanks!

This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.

MrCubbins said:
This looks very interesting indeed. Without MIC support it can't be my daily as I Skype alot, but a working 4.2.2 on this old tablet is amazing in itself! Great work as always Pio.
Click to expand...
Click to collapse
Actually, try a headset, or plug then unplug headphones, it works on the thrive for audio to get working properly, may work here too, they use the same audio system, drivers and libs.

Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!

MrCubbins said:
Well I didn't have time to play much last night but have had a proper look around the ROM today.
4.2.2 on A100 is FAST!! Very impressive. I noticed some issues so thought it might be helpful to catalogue them here.
MIC is definitely not working. Tried the headphone thing but nothing Voice Search force closes on launch and Recorder can't hear anything.
The Halo app (which I gather is one of the big draws in this ROM) force closes when you select it. Oddly, it's like it might be corrupted or something as the icon is showing as just a little droid and the app title is showing as HALO))).
Changing the camera resolution causes the camera to FC (front or rear camera) ... Afterwards a dialog box tells you that it "Can't connect to the camera". This was a problem in the older 4.1.2 ROMs as well but I believe Hardslog discovered a fix somehow so I am sure he will be able to give you the info.
If there is anything else I come across during my exploring I will let you know. I'm enjoying having new things to play with!
Click to expand...
Click to collapse
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol

pio_masaki said:
There's two parts of Halo))), the part you're talking about, doesn't matter unless you want a specific app always to be in Halo, otherwise HALO itself works just fine. The app itself isn't required or the "big draw" to the ROM, HALO can be managed just fine without it, and originally the app wasn't included, I hadn't noticed it was included now anyways lol
The camera issues are partly due to we're using camera parts from 5 versions of android ago, I'm sure it can be patched up again but it's getting annoying having to fix storage, audio, cameras, and kernels EVERY SINGLE MINOR UPDATE to android. We're not talking 4.1 to 5.0, its 4.1 to 4.2.
AFAIK it wasn't reported my 4.1.2 builds ever had camera issues, though. Keep in mind I was doing that blind, if no one told me I would never have known.
Google search doesn't force close for me, but it also doesn't hear anything, so that doesn't count for much lol
Click to expand...
Click to collapse
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?

MrCubbins said:
Does that mean I can safely remove the HALO))) apk without affecting the functionality of Halo itself?
I reported the camera res change issues quite awhile ago to hardslog, though I think at that point you had stopped development on the A100. I remember him saying he would look into a fix and I think awhile after he cured it. Can't remember if he listed on here what the actual cause of the problem is though.
This potential to customize how this ROM behaves is absolutely incredible. I spent the last couple of hours messing about with swipe bars and pop up menus and the various combinations possible... it really is clever stuff. Was rather confusing to figure out what is what at first. I've still not found a way to change the button size on the pie... any additional buttons added get squashed up at one end of it. Is there anywhere in the menu where this can be altered? Also, directly surrounding the pie buttons there is a thick bar which is partially blue... looks like a volume slider or something but I can't seem to get it to do anything??
All in all a very interesting ROM thank you Pio. Given that it is early days on 4.2.2 for the A100, do you think there is any chance that the MIC will be fixable in the future? Does it work ok on your Thrive?
Click to expand...
Click to collapse
Well as I said unless it was reported (to me) I wouldn't have known. Hardslog wasn't reporting issues or fixes to me so I never knew it happened or how it was fixed.
The mic should be fixable, and yes it works on the thrive, so its likely a minor routing issue on the vangogh vs Antares or Picasso boards. Sound is my weakest point though, I always have troubles with it for some reason.
As for pie, there's options for all kinda shiz in there, just gotta go through them all and restart systemui to make them active in some cases. That bar is, I think, just decoration, though.

Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:

AngryManMLS said:
Sad thing is I don't really use the camera features on the A100 so that's probably why I never tested them when going thru stuff on the recent CM10 builds. But yes I am getting the same issues MrCubbins has reported with changing resolutions FCing the camera app on this current CarbonROM build.
The only thing I am hoping for down the road is some kind of updated version Linuxsociety's Jelly Bean kernel that works on 4.2.2. I'm pretty sure the current build will not work on 4.2.2 ROMs due to there being enough differences between 4.1.x and 4.2.2. Love how that kernel worked in making things run just a bit smoother. :good:
Click to expand...
Click to collapse
I'm just curious why anyone
A: uses the crappy camera on these things for anything but Skype
B: bothers changing the resolution of the already low resolution cameras
The kernel included is already modified just hasn't had the juice turned on yet. I'm not a fan of his kernel for my personal device, it never got along with it. If you venture into its settings you'll notice it has some extras in governors and io, no longer stock CM.

Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.

AngryManMLS said:
Yeah I'm not really much of a fan of cams on tablets myself. Yet I've seen people using their tablets for taking pictures so what do I (and you) know, right?
I wasn't aware of what was going on with the kernel that you have in use. The Linuxsociety kernel or at least the one that was in hardslog's ROMs ran very well on mine. That's using Linuxsociety's kernel with mods done wasn't it? Then again we all know that you probably can have two A100's next to each other one will run the kernel perfectly yet the other one will have issues with it... so yeah.
Click to expand...
Click to collapse
I think he used ezterrys kernel, why he chose to over the godmachine kernel you'll need to ask him about lol. It was a nice kernel for sure, but my a100 just didn't like it. My thrive kernels love mine but hate some others, such is electronics I guess.
I'm still testing the kernel for when the juice is turned on so its a pretty basic kernel otherwise, bit it should wake up real nice when its let loose.

Looking over the notes from several of hardslog's ROMs he's mentioned they have used godmachine kernels (or as I mistakenly called them "Linuxsociety"). No idea on the latest ROM that he's released since there's no mention. Let me know if you need to me to test any kernels here. My A100 is ready.

Well the kernel has some odd issues, for one lulzactive seems to just stay at top speed, it doesn't seem to scale at all. In the overclock enabled builds anychanges to min/max speeds will result in no deep sleep, the kernel stays awake at all times. Not sure whats causing either of those, lulzactive can be gone over but why the speed change locks the system awake I have no clue.
I really wish I knew what I was doing with kernels lol
Edit:
Vote, who thinks I should just update the linux society/god machine kernel to 4.2 and leave it at that? lol

I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?

AngryManMLS said:
I was totally not aware about the deep sleep issue since I normally turn the tablet off when it's not in use. Does the ezterry kernel have the same issue? If not then maybe updating that to 4.2 might be better in the long run. As far as scaling I never seemed to have the issue at least from what SetCPU shows me. I'm about to go to my CYANOSAKI_FLEX_V2.0 backup and will let you know what I'm seeing as that I believe is using a godmachine kernel.
Also just noticed something weird. When I tried to backup the current CarbonROM build using TWRP 2.6.0.0 it shows 0MB in cache is used. Could there be something wrong with the routing/paths/etc on cache use on CarbonROM?
Click to expand...
Click to collapse
The deep sleep issues are only on the overclock enabled kernel that I use, it shouldn't appear in the released build, it only shows up if min/max speeds are changed from stock. Scaling issues appear only in lulzactive, its defaulted to interactive so unless you change it, its scaling properly.
I'm not using the ezterry or god machine kernels, so its a problem unique to mine I think.
It uses cache or it wouldn't be booting at all, and you shouldn't back that up anyways I think twrp has some bugs no one ironed out and its causing oddness with older devices.

Oops. I thought you meant godmachine's kernel had those issues. My bad. I should read better next time. :laugh:
Also checking CYANOSAKI_FLEX_V2.0 the kernel it's using believe it or not is by ezterry. SetCPU defaults to interactive on this for me as well running at 1.5 ghz max speed, 312 mhz minimum. No idea if hardslog has done any mods/changes to the kernel however. Run perfectly fine on my A100. :good:
And you are right about cache let alone the TWRP bug. Just finished wiping and restoring my CarbonROM backup by the way. Successful swapping from 4.2.2 to 4.1.2 and back via TWRP backups.

Ugh I hate kernels, and I hate working IN them even more. But, it's coming along. It'll basically be the GM kernel all over again when I'm done lol.
So far vs the source I began with:
GPU/CPU/system speeds are tuned a little more, voltages tuned a little more
Adding in those missing governors, like Smartass and lagfree.
Converted/updated to BCMDHD from BCM4329
OC up to 1.5, UC to 216
I'm building this to include with my 4.2 builds, and I suppose I could just release a flashable version, it may even work on 4.1, who knows.

ParanoidAndroid 3.69

Hi. I'm actually on pa.2.55. Going to 3.69 but can't seem to find the latest gapps for it. pa_d2att.
Thx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

ugo.alexandre said:
Hi. I'm actually on pa.2.55. Going to 3.69 but can't seem to find the latest gapps for it. pa_d2att.
Thx
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Here is the link from goo.im. this is the gapps package for 3.69 (4.2.2)
http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-full-4.2-20130719-signed.zip
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Hi there,
Was hoping to get a response from Ayysir or Gideonx, but not sure if they're monitoring this thread (obviously everybody's expertise is welcome!). I've been having a bit of a problem with 3.69 (and had the same problem with 3.68). After a clean install on 3.69, including only a very few data restores from TiBU (and none on the apps that are giving me trouble), I've been consistently getting random but inevitable freezes on nearly all the games I play on my phone, sometimes to the point that the phone actually reboots. I get a screen flicker, and then progress slows to an absolute crawl and I even see frames flickering back and forth at times (i.e., the unicorn in RUA2 moves back and forth a frame or two on screen). When I can fully close the app, it usually reboots fine, but then freezes eventually as before. Everything else about the ROM is absolutely rock solid - I actually just commented to my wife that, other than the freeze up issue, I've never had such a clean ROM on my phone, awesome battery life, smooth as silk, etc.
I've tried pretty much all the kernel options available, in addition to stock, to no avail - the problem persists. No undervolting at all in any case, and the highest CPU temperature I've seen recorded through trickster has been 54 degrees, which shouldn't (I think) be enough to trigger heat-related issues should it? The CPU is generally sitting around 42 degrees under load, which seems great to me.
Anyways, if you have any thoughts about what could be causing the issue, I'd appreciate it. I'm assuming it's ROM-related because of the steps I've taken to eliminate it, but who knows, maybe the issue is hardware related and there's nothing to be done but replace the GPU or something.
Thanks,
--Rob
EDIT: Should also say that this is the second clean install I've done and the problem has continued in both cases (i.e., doesn't seem to be a bad install).

Just to add to my previous post: I've been reading that some problem on Nexus 4 devices have been having problems running games built with the Unity engine since the upgrade to 4.2.2. Anyone have any thoughts on whether this could be the culprit?

Rob116 said:
Just to add to my previous post: I've been reading that some problem on Nexus 4 devices have been having problems running games built with the Unity engine since the upgrade to 4.2.2. Anyone have any thoughts on whether this could be the culprit?
Click to expand...
Click to collapse
You may want to try this... Goto Settings --> Developer Options --> and check Disable Hardware Overlays (I haven't seen this mess with Halo functioning) and Force GPU Rendering. I think there was another related setting you need to turn on.
I got a warranty replacement and haven't been able to switch back from TouchWiz due to a baseband upgrade... So I apologize if that isn't as thorough as I would have liked.
I turned these settings on and game performance went back to normal.
HTH.

DKaine said:
You may want to try this... Goto Settings --> Developer Options --> and check Disable Hardware Overlays (I haven't seen this mess with Halo functioning) and Force GPU Rendering. I think there was another related setting you need to turn on.
I got a warranty replacement and haven't been able to switch back from TouchWiz due to a baseband upgrade... So I apologize if that isn't as thorough as I would have liked.
I turned these settings on and game performance went back to normal.
HTH.
Click to expand...
Click to collapse
I'll give it a shot if it reappears - the problem hasn't occurred in two days now, after having been a very consistent issue since 3.68. All I've done in the meantime is some clean up of the file system via sd maid. Truly bizarre.
Thanks very much for the suggestion!
Sent from my s3 using Tapatalk 2

[Q] How stable and reliable are the Android 4.4 ROMs?

At the moment there is no stable and reliable Android 4.4 ROM yet, but I hope this will soon change.
Perhaps we can compare the different ROMs here. Please note that I am not asking for best performance or lowest RAM requirement. These are secondary issues. The most critical issue is reliability.
The Google ROMs have always been the most stable and reliable. They were never perfect, but at least we could expect them to run for a week or longer without any significant error and without rebooting. In my experience, other ROMs, like the admirable CyanogenMod, came close, but never quite reached that same level of reliability. Given that the CyanogenMod crew works for free and in their free time, the quality they delivered has been astounding and admirable.
Nonetheless, reliability remains the biggest issue among the third-party ROMs.
So, if you install any of the Android 4.4 ROMs on your Galaxy Nexus, please report what you find. Please try to judge whether that ROM can be recommended for general use or whether the newbies had better stand back and wait for the next version.
Another question is: How user-friendly is the install procedure? Can you keep your apps and app data?

It is very unfortunate that the gnex community is not supported anymore due to 'hardware issues' or the 18 month timeframe. It is true that the ROMs made these days are not so 'reliable' and they may be buggy and cause force closes on certain applications. The new roms may never support cleanly and as stable as stock factory images by Google but its all the Gnex community can rely on from now. Personally, I feel the slimkat 4.4 ROM is acceptable considering it is only about less than a week old. They have been fixing bugs such as GPS tracking and such. I will be using it as my daily driver from now and just hope that the developers can make it as stable as the stock android ROM.
Sent from my Galaxy Nexus using xda app-developers app

a taste of kitkat perfect aosp leaked rom
i''ve installed yesterday a taste of kitkat with mpokang 1080p kernel.. some glitches when rotate screen but only one reboot using google now (i don't use gnow so it's not a problem for me) and i've a crash only on fifa14... battery good performance, no lags, no problems, trickstermod overclock to 1.4ghz no problems, facebook, whatsapp, viber, tango, hangout, 3G, Wifi, Bluetooth, GPS alla working without problems.. and now i'm testing battery..

Toro Plus
For us sprint (or Ting) users the 4.4 ROMs are not even installable. There have been two threads started and each one was locked after it became apparent that the developers did not have booting builds. I appreciate all the work devs do, but this keeps getting my hopes up. Hopefully, someone will get one working soon and we won't have any more false starts.

They are just alpha builds, experimental builds. Most of them have some glitches. They are not for daily use.
If you do not have necessary knowledge and do not have time to report bug, then I suggest you should back out on those alpha builds.

They're not even a week old. Give time and reap miracles afterwards
Sent from Samsung Galaxy Nexus @ CM10.2

It's a Nexus device. Things will improve over time.

I've been running the most recent SlimKat alpha build and it's been pretty solid. Phone feels rejuvenated. It is my work phone and worked flawlessly all day. The only restarts were Hangouts last night and when I was fiddling around with wallpaper settings after work, and forgivable graphics glitch during screen rotation. Otherwise, it has has felt like a new-ish phone today.

Thanks for the good information!
I think, when the builds go from alpha to beta and there are no obvious glitches any more, then would be the time to do some more thorough testing, particularly:
GPS, including track recording with My Tracks, Locus, or a similar app
Cameras with all their functions
Compass, gravity, and other sensors
Tethering via USB, Wi-Fi, and Bluetooth
Radio functions, particularly LTE and the general behavior with a weak or frequently interrupted signal
OTG with USB mass storage device, keyboard, etc.
I would recommend to report all defects not only here, but also to the maker of the ROM.

For now, they are pretty unstable, but I would keep an eye out for linaro's builds as well:
http://www.cnx-software.com/2013/11/06/android-4-4-kitkat-on-galaxy-nexus-rom-linaro-and-petition/

idk what you're talking about OP. i've run these custom roms more tha n week and they've been good. only reason the counter will reset is because I flash a new rom or flash an update or a mod.
These ROMs are very stable.
4.4 ROMs. give it some time. it's amazing that in less than 24 hours after the release of 4.4, we got a semi daily usable ROM from people that don't even work for Google.

I've been on SlimKat for a couple hours now. Clearly a ton of the SlimRom features are missing but considering that its an Alpha its not that bad.

Other than some graphical glitches here and there, which are very rare actually, there arent any other instabilities that I can see. Everything works fine. I dont know who is starting this rumor about 4.4 being unstable. Some ROMs may work better than others but thats due to different developers working at different paces. Bottom line is, 4.4 is perfectly fine for a daily driver. It just needs some ironing out.

Yeah, I'm running the SlimKat ROM, and its beautiful
Sent from my Galaxy Nexus running the Forbidden Update using xda app-developers app

Running Shiny 4.4. Good taste of KitKat. Sounds crazy, but I'm using it to test stuff out before it goes on the N5.
Biggest glitch seems to be with graphics, in that overlays of menus and random black boxes over some text in gmail and Chrome, make things unreadable and useless. Not to mention the random reboots when you can tell something happened that the GNex doesn't like.
IMO, they are not ready for use on a primary device. As in, at the end of the day, when I'm home, I pop my simcard out of my MotoX and out it in my GNex/3.4 to tinker. No maps to crash at the wrong time, I have other devices at the low-ready to surf on and more time to tinker. My gf loves me for this routine I've made for myself

Definitely a good taste of KitKat. Considering today would mark 1 week since release, on an unsupported device - its actually pretty stable.

LCD Density
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?

xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
use rom toolbox, it worked for me
Inviato dal mio Nexus 7 con Tapatalk 4

xMoment said:
I'm on SlimKat and my old eyes can't deal w/ the tiny text - even when changing default system font to HUGE in the display settings. build.prop has a value of 240 but I can't edit in ES Explorer even though the file props say it's writable. Tried an app but it loops and doesn't make any changes. Any ideas?
Click to expand...
Click to collapse
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:

Thanks - I was rooted already and made sure root explorer was on. Tried to change permissions in terminal, didn't work. Booted into recovery and mounted system, rebooted and hung at the google logo...so flashed FML and the DPI is 320 so I'm fixed
joytsay said:
1.Root first using chainfire SuperSU v1.65
2.Install RE(Root Explorer)
3.Hit Mount R/W
4.Open build.prop and change density to 320.:highfive:
Click to expand...
Click to collapse

[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)

[#Intro]
Oh, and now there's these Lollipops I'm handing out. They are free as always, and they are very very delicious.
[#Why]
[#Info]
I need people testing and finding bugs if anything is going to be fixed. I might not have the Bluetooth devices you have, I might not use the camera as much as you, I might not use 4G LTE (or mobile data in general really) as much as you; you get the idea.
[#HowTo]
Latest Build​KitKat/Stable: N/A
KitKat/Beta: omni-4.4.4-20141015-toroplus-FML.zip (162.13 MB)
Lollipop/Beta: FML-AOSP-5.0-20150108-toroplus.zip (195.53 MB)
LOLLIPOP INFO:
USE THESE GAPPS: FML-GApps-5.0.x-20150101-tuna.zip (167.81 MB)
They are based on PA's GApps, huge thank you to them!
Known Issues
- Camera can be a little touchy, but it generally works.
Lollipop Changelogs can be found in the post below!
(KitKat) BETA INFO:
Beta builds are using updated GPU drivers (and an updated kernel to go with them) courtesy of @Ziyan, as well as being up to date with the latest stuff from OmniROM. NOTE: YOU CANNOT FLASH A DIFFERENT KERNEL WITH THESE BUILDS.
Currently broken with the new GPU drivers:
- Hardware Video Decoding FIXED 2014/10/06
- Hardware Video Encoding(?) FIXED 2014/10/08
- Camera (PARTIALLY) FIXED 2014/10/08
- The stock camera app (as well as Google Camera) has this weird quirk of crashing when pressing the shutter button to take a picture, however many different camera apps on the Play Store (in particular Camera ZOOM FX) work flawlessly. Video recording is generally OK, however I've been getting some reports of the audio and video being a little out of sync, so your mileage may vary...
See the Changelog post below for..... well..... changelogs.
[#GApps]
Known Issues​- The screenrecord command does not work directly, however it does work via the Power menu.
- There can be a slight (noticeable, but not huge) delay when pressing the Recents or Home button.
[#Thanks]
[#Donations]
XDA:DevDB Information
FML: Fork My Life, ROM for the Samsung Galaxy Nexus
Contributors
MWisBest
Source Code: https://github.com/MWisBest/
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2015-01-08
Created 2014-10-13
Last Updated 2015-01-08

Changelog, News, Etc.​
Lollipop Beta Changelogs:
- Updated the camera HAL.
This is going to be a little... fragile, at first, but in the long run it's needed. Stock camera app saves pictures now at least.
You may also notice that there's a 5.1MP resolution now (clear your camera app's data if you don't see it), despite our camera supposedly being 5.0MP all these years. Turns out the sensor's native resolution is indeed a whopping 16 pixels taller and 16 pixels wider than we've been using.
2015/01/04
- Added back some of the classic FML optimizations and more.
Built with -fstrict-aliasing flag, C++11, and the Linaro GCC 4.9 toolchain.
- Updated to AOSP "android-5.0.2_r1" tag.
As usual, the only real change was them bumping the version number.
- Improved flashing.
The speed of flashing the ROM zip is now much faster.
- Superuser is now built-in.
There's no need to flash SuperSU. You can find Superuser in the Settings app. You may have to enable the "Development Settings" menu to see it.
Some apps are a little sketchy with this Superuser though, most notably Titanium Backup. If you have issues, try flashing SuperSU.
- Video playback should be fixed.
YouTube in particular seems OK. If you have some weird format you're playing back locally I cannot make any guarantees though.
- The camera situation has improved and also regressed.
The stock camera is kinda back to the point of where it was with the KitKat Beta builds:
---- Preview works. Saving photos does not work. Video recording kinda works.
--- However:
---- The camera calibration is a little messed up. Long story, but it'll be fixed soon. So your white balance may look kinda funky, among other things.
- Audio quality is improved, with support for 192kHz FLAC as well.
This is possible thanks to a new audio resampler, which doesn't impose the same sample rate restrictions of the stock Android ones. It also has far better quality than the stock Android resamplers.
- WiiMotes can now be paired via Bluetooth.
I used to be a bit of a Wii hacking enthusiast... I think I still need to add some more stuff to make it useable as a gamepad or something, but yeah.
- Fixed location services issues.
- (toro) Fixed switching between 4G/LTE and 3G/CDMA network settings.
- Kernel changes:
Reclaimed 38MB of RAM from the carveout stuff.
Removed HDMI's framebuffer, saving an additional ~16MB of RAM. With Lollipop, MHL/HDMI out isn't working with our old HWComposer, so might as well save some RAM in the mean time.
Added overclocking support, as well as adjusted the stock frequencies a little.
Added the GPU kernel driver back into the kernel, rather than building it as a separate module.
Switched to LZO compression for the kernel. It results in a slightly larger size to the kernel, but it boots faster.
Added the "purple tint fix".
Added compiler flag to tune code for Cortex-A9 CPU.
Built with Linaro GCC 4.9 toolchain.
Older Builds:
2014/11/16
- Fixed the RIL.
(I think, still unsure of toroplus's status.)
There were a few things that went into this, and I can't really take much credit for it other than being persistent in trying to fix it.
1. rild needed a little fix-up to somewhat return it to pre-Lollipop form. Basically Google is forcing Qualcomm's junk upon the world. @dhiru1602 pointed me in the direction of some commits from rmcc to hardware/ril that fixed this part of the problem.
2. The kernel needed a commit to support some new junk related to networking in Lollipop. @Ziyan linked me to the change in question.
- Updated to AOSP "android-5.0.0_r6" tag.
Really the only change is that the build number is bumped to LRX21T.
- Switched out a couple small proprietary binaries with a reverse-engineered open-source version.
Thanks to @stargo who has really been killin' it for the Motorola OMAP devices recently, we now have a reverse-engineered pvrsrvinit binary (the executable that fires up the GPU drivers on boot-up). This is especially important because the proprietary pvrsrvinit wasn't compiled as PIE (position-independent executable). With Lollipop, they're forcing everything to be PIE, which is good because PIE is better from a security stand-point. Previously I had been adding a workaround to enable support for non-PIE, which I now don't need.
2014/11/11
- Switched back to the old OTA package format.
With Lollipop they're now, by default, flashing something similar to a system.img. I switched back to the old format. THIS IS CAUSING VERY LENGTHY FLASH TIMES NOW HOWEVER, I HOPE TO FIX THESE SOON.
- Changed the kernel to build with GCC 4.7.
With Lollipop, Google switched to GCC 4.8. GCC 4.8 has never been kind to the Galaxy Nexus kernel, I'm surprised it was booting at all in the first place.
- Added "Ambient Display".
Apparently I need to add a "pick-up" or "significant motion" sensor for it though, so it displays something when the phone is picked up.
- Fixed chromium crashing.
This fixes Browser crashing upon open, among other things. This fix has been in chromium itself for nearly 4 months now, I don't know what the heck Google is doing to AOSP to make it so FUBAR lately...
- Fixed lag in Recents menu.
Now it's smoother than KitKat's, in my opinion.
- Added back F2FS support.
F2FS is now supported again, HOWEVER, it is NOT supported on the /system partition. It really didn't do any good for /system anyway.
- Updated various icons.
The Dialer icon in particular was bothering me. Other things that aren't visible in the launcher, e.g. SettingsProvider, have been fixed as well.
- Fixed FLAC playback, among other media decoding issues.
Just needed a sync-up in the device tree with one thing that I think Google DID do a nice job of with Lollipop actually.
- Built the ROM with "WITH_DEXPREOPT := true" defined.
This basically has all the system apps compiled before flashing, to cut down on the initial boot-up time which is ridiculously long with ART.
- Changed the "Android is upgrading..." screen to prevent burn-in.
Instead of using the white Lollipop-like look, it now should show up as the old, darker theme.
KitKat Beta Changelogs:
2014/10/15
- Cleaned up the kernel.
Ziyan went over all his work not long ago and cleaned up the commit history and whatnot. He's letting me do the task of merging in the GPU driver stuff, so I'm currently just getting the kernel to a "clean slate" of sorts for other kernel devs to fork and build off of. Basically this should hopefully be the new "stock" or "Google" kernel. As a result, there's some bells and whistles missing from this build. It does however include some new audio updates that weren't in the previous kernel, which leads me to this...
- Changed audio sampling rate to 48kHz.
Previously the sampling rate has been 44.1kHz. The Galaxy Nexus supports 48kHz though! Here's what mainly sparked this change: since KitKat, the UI audio effects (e.x. touch sounds) have been switching over to 48kHz. With the Galaxy Nexus still using 44.1kHz, UI sound playback became kinda sluggish, and this was a big contributor to it. The UI sounds use the "fast track" audio path (where it tries to do as little processing as it can to the audio in order to play it with a minimum amount of latency), however a requirement of using this is that no resampling (e.g. converting 48kHz to 44.1kHz, like it has been doing currently with KitKat) can be required on the audio being played. Therefore the UI sounds were taking the "deep buffer" audio path, which has a delay to it. In switching to 48kHz, the "fast track" path is actually even faster now than it has ever been previously, and the Galaxy Nexus was already TOP OF THE LINE when it comes to audio latency believe it or not!
Another thing about this is that there is now support for playback of 96kHz audio files.
- Some updates to the camera HAL.
This hasn't fixed the situation of stock and stock-based camera apps crashing when taking a picture, but it's a start on it though.
NOTICE: Poweramp (and probably most other media players that use their own native code for audio playback rather than straight-up using the built-in Android APIs) is being pissy about the sampling rate change. If you experience issues with music playing, especially things like popping or crackling, please try Play Music or Apollo and see if your issue is still present. I know the UIs for Play Music and Apollo are pretty awful, but I can't write my own media player because I'm dealing with this camera stuff!
KitKat Stable Changelogs:
N/A

Reserved
Reserved.

Reserved
Reserved.

Finally got FML up for you toroplus guys! Sorry for the long delay.

Awesome...thank you very much MW!!!!!

Wonderful
Currently uploading this to my server and will seed until a stable version is uploaded, then I will replace it. Thank you so much for bringing life into an otherwise fading device. :crying:
Donation sent.

Downloading. Will be my second rom I try;

Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.

BennyDS said:
Beeing the beginner that I am, I have a Maguro so i couldn't install this one.
Sorry.
Click to expand...
Click to collapse
Maguro Build is Here.

I've always wondered about this rom as I saw it on the toro thread... will give it a whirl

MWisBest said:
Finally got FML up for you toroplus guys! Sorry for the long delay.
Click to expand...
Click to collapse
Running good so far! I dirty-flashed over the official Omni build I've been running. No problems to report outside of the expected camera weirdness. Play Store camera apps are all over the map in their behavior - CameraZoomFX works perfectly as you reported, Google Camera crashes like the stock camera, Focal doesn't have any display at all. Video recording works but the audio is a bit out of sync, playback is a little choppy on the phone but is smoother on my computer. VideoCam Illusion (which does its own video encoding via software) does not work at all. Video hangouts seem to work fine.
Also, I used the torch quite a bit today, and at one point it quit working and I had to reboot to get it back. It's a bit early to tell, but I'm suspicious that this ROM is affected by the same 'Camera quits working' bug as Ziyan's 'stable' OMAP kernel.
Anyway, thanks again for your amazing work!

I had the same Torch issue as stated above, fixed with a reboot. Im currently running on Ting/ a Sprint MVNO and they are known for having APN issues with 4.4.x roms. When switching to LTE in the settings, the dialer app would crash loop until I switched back to 3g/2g. Flashing an APN zip on their forum fixed the crashing, but havent been able to tell if 4g actually connects as its pretty shotty coverage in my area. But I thought Id share incase someone else is on Ting.
---------- Post added at 05:15 PM ---------- Previous post was at 05:04 PM ----------
Coming from CM 11 I guess I have been lucky as far as not having to do my own work as far as updating the Sprint Profile, and PRL as it was still within the system settings. I have been unable to figure out how to update Profile/PRL on my own as of yet. Any chance one of you may want to share this info? I'd greatly appreciate it.

New build is up.

The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.

bloopblah said:
The ROM is running smoothly with a few hiccups. I have ran into a few problems. Here's some of them that I have found so far:
1. I currently don't have root.
2. The options to "Uninstall/App info" is there but the texts aren't visible.
3. 3G to LTE switching isn't working on the 20141015 nightly build. It was on the 20141014 nightly build.
4. No Up/Down icon on the signal.
Click to expand...
Click to collapse
1. Root works here on FML. THe official build of OmniROM does not include superuser, you need to flash it yourself from recovery.
2. That's been a longstanding bug with Omni on toroplus for some reason.
3. There's no 20141014 build of FML for toroplus - are you using the Omni official build?
4. That's turned off by default - Settings/Bars/Activity Indicators.

Alright, another new build to try out! I will have a couple of ROMs to try on my GNex which is a good thing!
@MWisBest...hopefully you get some donations coming in as well as Musical_Chairs since you guys are putting time and effort into providing new goodies for us.
Hopefully you get some $$$ coming in. It's going to be about a week for me to donate. One thing people don't realize is that donations don't exactly flood in for devs. I released 4 Venum Ice ET4G ROMs and 2 fully inverted black and white Note 2 ROMs including icons, all inverted apps etc. I actually got over 1000 downloads on all 6 ROMs within the first 24 hours and had excellent feedback.... I received a total of 3 donations totaling $12! Lol. What you guys are doing is harder so hopefully some people who are still here show you guys some love for not making this a thread that got closed for inactivity.... Thanks again to both of you.
Sent from my Knox-Blocked P.O.S Tab 3 running same hardware as my GNex using Xparent Gray Tapatalk 2

Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.

cr08 said:
Wanted to give this rom a shot mainly due to the updated GPU drivers. So far a very smooth experience and pleased with it except for one major bug for my use case: Any video playback either Youtube, MX Player, etc.. after some uptime seems to fail entirely. In the case of YT it'll just sit at a black buffering screen. It'll buffer the data fine going by the progress bar as I've at times had about 1/4 of a 10-15 minute video buffer going by that indication with no playback. If I reboot the phone and give it another shot, it works.
Click to expand...
Click to collapse
That's the same issue as the torch issue mentioned above. It's a hard bug to track down because it takes so long to show up, and AFAIK nobody has found a reliable way to trigger it (other than just wait a day or two for it to show up). If somebody can figure out how to trigger it more quickly, I would like to try a git bisect on Ziyan's stable OMAP kernel (which is affected by the same bug) and see if I can pinpoint what is actually causing it. But without a reliable way to tell if a particular test kernel is good or not, a bisect is more or less useless.

Hi guys. How are you? I'm fantastic right now:
EDIT: Let me fix that a little...

[Q&A] [ROM][UNOFFICIAL]AOSPA-Legacy 5.0 ALPHA 1[d851 ONLY]

Q&A for [ROM][UNOFFICIAL]AOSPA-Legacy 5.0 ALPHA 1[d851 ONLY]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][UNOFFICIAL]AOSPA-Legacy 5.0 ALPHA 1[d851 ONLY]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

oh yeaaaaahhh
Oh hell yes .... I've been waiting on pa for the longest... I know when time comes... Pa features will really look nice with lollipop!

Yes!!yes yes!!
Pretty good...seems pretty stable..i see its running the cm12 kernel...hopefully i dont get any kernel crashes (blue screen demigod)... Evey LP rom so far has been doing that alot..

Works great...
No miscellaneous battery usage going on and the video camera works too! Running great so far and I think I finally found my CM12 daily driver.
The *one* thing (and this could be user error) is no "clear all" button in recent apps. Other than one little minor thing, I'm very excited.
EDIT: Used it for a while w/ no miscellaneous battery usage showing up and then it showed up out of nowhere.

jriv21 said:
No miscellaneous battery usage going on and the video camera works too! Running great so far and I think I finally found my CM12 daily driver.
The *one* thing (and this could be user error) is no "clear all" button in recent apps. Other than one little minor thing, I'm very excited.
EDIT: Used it for a while w/ no miscellaneous battery usage showing up and then it showed up out of nowhere.
Click to expand...
Click to collapse
I built this thing straight off the AOSPA-Legacy source -- which appears to be an odd fork of cm-12, but with specific d851 drivers (except for the audio drivers, which I had to take from cm).
The "clear all" button thing -- yeah, it's also missing advanced reboot options, and...pretty much everything. It feels to me like this was a fork from cm12 that hasn't been updated as much. We'll see what happens development-wise -- I expect it to pick up soon. Either that, or Ill cherry pick the improvements and build from there. Maybe. I'm not really interested in building another damned cm12. What I'm interested in is building and maintaining PA 5.0.
The "miscellaneous" battery usage thing WILL go away after a couple of charging cycles. That's Lollipop's battery management system learning your battery usage pattern -- or so I've been told.I haven't had it pop up on me yet, but I have seen it with other AOSP 5.0 builds, and it's gone away after a charging cycle or two.

CrusherJoe said:
I built this thing straight off the AOSPA-Legacy source -- which appears to be an odd fork of cm-12, but with specific d851 drivers (except for the audio drivers, which I had to take from cm).
The "clear all" button thing -- yeah, it's also missing advanced reboot options, and...pretty much everything. It feels to me like this was a fork from cm12 that hasn't been updated as much. We'll see what happens development-wise -- I expect it to pick up soon. Either that, or Ill cherry pick the improvements and build from there. Maybe. I'm not really interested in building another damned cm12. What I'm interested in is building and maintaining PA 5.0.
The "miscellaneous" battery usage thing WILL go away after a couple of charging cycles. That's Lollipop's battery management system learning your battery usage pattern -- or so I've been told.I haven't had it pop up on me yet, but I have seen it with other AOSP 5.0 builds, and it's gone away after a charging cycle or two.
Click to expand...
Click to collapse
Hey, I'm just glad this phone is getting some AOSPA love -- been waiting for this one to get it. Much appreciated!

Excellent stuff. Is there a way I can get back the Close All Recent Apps button in the recent apps window or was that just a CM feature?

ChuckleNuts said:
Excellent stuff. Is there a way I can get back the Close All Recent Apps button in the recent apps window or was that just a CM feature?
Click to expand...
Click to collapse
Mentioned just two posts above yours.

Anyone having any luck playing videos via the Instagram as well as the Vine app?
EDIT: Never mind. I did a quick dirty reflash and videos on Instagram and Vine (as well some mp4 videos on the web) started playing fine again.

Great ROM
Great ROM @CrusherJoe and other developpers.
Is it possible to have the following features:
- Advance booting/reboot ooptions (Reboot / Recovery, etc)
- Ability to change the DPI settings for those who love smaller icons.
Thanks.

No Reboot option
Haven't seen this one yet, any of you guys missing the reboot option? All I have is Power Off.

jeffmanh said:
Haven't seen this one yet, any of you guys missing the reboot option? All I have is Power Off.
Click to expand...
Click to collapse
The dev hasn't gotten around to adding the root feature, if he even decides too.
In the mean time download quick boot (reboot) from the market.

Dirty flashed the new build. Everything seems to be working great.

Mikey said:
The dev hasn't gotten around to adding the root feature, if he even decides too.
In the mean time download quick boot (reboot) from the market.
Click to expand...
Click to collapse
I actually tried to cherry-pick advanced reboot from CM-12.0 this afternoon. All conflicts resolved, no errors at compile-time, clean flashed the resultant build, and...
...the option for advanced reboot showed up in development options, and you could check the little box to activate it, but that's all it did. Long-press on the power button resulted in the exact same "Power Off" (lack of) choice as before.
Evidently, AOSPAL handles shutdown options differently than CM-12.0 (which may be why cm_strings.xml was missing from frameworks/base in my local repo, now that I think about it).
*sigh*
Hopefully I'll have time to delve into it this evening. I really miss advanced reboot, too, and it's kinda my "windmill" to get it ported/added to AOSPAL...

About the dialer
Well I have been using the build that was released on 11-30-14 and everything works. I use my phone daily due to my job and it hasn't crashed on me at all, and I use the dialer a minimum of 10 times a day.

I love this ROM! Thanks for all the work. BUT, any ideas as to why the streaming of music (Pandora) to my Kenwood car audio head unit doesn't work with later versions of this ROM? I have no problems syncing the following;
Kenwood - Voice Calls :good:
Kenwood - Live Traffic Updates to nav software :good:
Moto 360 :good:
When I clean flash the early 5.0 ROM, not a problem. If I clean flash 5.0.1, it fails. I've been currently using my phone with Kenwood head unit and this ROM but only when I clean flash 5.0 and dirty flash the later updates.
FYI, NONE of the other available LP roms allow me to stream from my LG G3 at all.
Thanks
JR
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Update: I dirty flashed the latest build and it BT sharing stopped and everything broke. That's a first. Thank goodness for Nandroid backups.