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.

Anyone here still using CM11?

Just got a bit tired of little bugs in the CM13 based roms and thinking about switching back to CM11. The only concern is the lack of security updates after the maintainers abandoned the projects for newer android versions.
Did anyone here try downgrading? Or maybe never upgraded? Is it wise to do so?
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue

LOL brother. I am still using CM 11 build 14/11/15 with Xcelerate kernel build 4/12/15.
I still used this OS as it gives me atleast 500+mb ram which I require a lot for gaming.
At battery 100%............(with airplane mode on)...wifi on After 3hrs of continuous wifi gaming my battery drops to around 20%.
So I guess battery life is good.......though i haven't activated any sim cards(that would be a different story)
I don't have any voice(call) related problem though. Only bug is HDR. Once a picture is clicked with HDR on, you have to exit camera to click again in HDR mode
I actually need a CM 13 rom which provide such performance.(I was thinking about Slim rom 0.4 by Aniket Lamba)
So if anyone can suggest me better rom then please let me know. For me stability & usability matters more than recent builds.
I always will appreciate any information whether good or bad

I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
amangupta53 said:
Some of my issues with CM13 based roms which have put me off:
Insane lag when reciving calls
Adopting Storage doesn't work half the time
Front Camera crashes
Mobile Data issues
Lock Screen Wallpaper Issue
Music suspend bug
Battery drain Issue
Click to expand...
Click to collapse
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...

NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
Hate towards KK is only because most of the apps are working great in >LP than in KK. If MIUI with LP is given then it can be easily a great choice for armani. MIUI ram issues have sorted out but only thing is standby time(wifi on) is low.

NightRaven49 said:
I used to like KK as it was last in the line of the Holo interface and it was the only 4.x available for our phone, so I used it for fairly long and didn't switch to LP until MM came around. Along with Xcelerate it was really good: decent battery life, smooth experience and fast charging. But now that I've grown to like the Material interface as well, I've been using MM more often these few months, especially Slim6, which I feel gives the same feel I used to get on KK: stability and smoothness.
KK is still one of my more favourite ROMs, but given that KK is mostly dead by now and there are more developments and features in LP and MM, I think I'll just stick to Slim6.
1) I don't get this
2) I don't use Adoptive Storage, heard it screws with WiFi
3) I don't get this (it has been fixed recently)
4) Depends on ROM
5) GravityBox (for AOSP MM), or this guide (which also works on CM13)
6) Disable MPDecision. Strangely when I downgraded to CM11 I was still getting the bug.
7) Depends on ROM
The issues I had with CM11 were generally the use of Apollo and the HDR issue as stated in the post before mine. And the music bug after downgrading. Apart from those I was happy with it, and I wouldn't mind a single bit to change back to it. I just don't understand the hate regarding KK, especially in the MIUI 8 thread...
Click to expand...
Click to collapse
The music bug persisting after the downgrade is what's keeping me back. I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.

slst said:
Hate towards KK is only because most of the apps are working great in >LP than in KK.
Click to expand...
Click to collapse
Funny when there was a time when apps couldn't run properly on ART...
amangupta53 said:
I, too, don't use Adoptive storage for all the bugs it brings - even on AOSP. But this means I'm running out of space by the end of the month because of necessary evils like WhatsCrap.
Click to expand...
Click to collapse
Adoptive Storage is a hassle to set up: you need to format your SD card (which meant I had to shift everything out before converting it), and TWRP has no way to read such encrypted storage, so I didn't use it after the first time I tried it. Also you could do with regular housekeeping of your phone's storage; usually I keep WhatsApp images for a year before deleting them (after keeping the important ones and archiving the rest).
amangupta53 said:
The gravitybox mod is good to know, although I don't use xposed, but really is simply a hassle to effectively change your wallpaper - especially when I'm changing them every other week.
Click to expand...
Click to collapse
Xposed is very helpful, but if you don't want to use it then I won't force you.
Generally in those CM12/13 ROMs if I wanted to switch between lockscreen wallpapers I would leave a couple of those wallpapers in the /data/system/users/0 folder, just renamed to let me know which file is which wallpaper. Whenever I wanted to change them I just renamed them to the proper filename.
amangupta53 said:
I've recently tried disabling MPDecision - the music seems to be playing fine but I can't help but notice sightly degraded performance all around.
Click to expand...
Click to collapse
You don't have to leave MPDecision off the whole time: just disable it when listening to music, and re-enable it afterward.

Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly

Dr. Joy Das said:
Thank you everyone for your valuable comments:good:. It seems I can finally move on to CM 13:fingers-crossed:.(mostly slim6 version)
Note: I don't have music stop bug in CM11 though( may be related to firmware version or kernel. don't know why different people have different bugs:silly
Click to expand...
Click to collapse
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug. This is probably the reason why downgrading back to CM11/12.1 doesn't seem to fix this issue.
Anyway, seems like I'll just stick with CM13 for now.

NightRaven49 said:
Funny when there was a time when apps couldn't run properly on ART...
Click to expand...
Click to collapse
Sorry my friend i think its past now.

amangupta53 said:
What I think is that the KK firmware/modem we all flashed for CM13 builds has something to do with the music suspend bug.
Click to expand...
Click to collapse
Well not really, as the same v7.0.5.0 is used for CM11, 12 and early 13 builds. It's most likely a kernel issue, given that disabling MPDecision fixes it somewhat.
slst said:
Sorry my friend i think its past now.
Click to expand...
Click to collapse
I totally didn't know that, like totally dude
/sarcasm

Paranoid Android 6.0.3 - AOSPA - Nextbit Robin

{
"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"
}
We are launching brand spanking fresh. All new features. New team members. New everything and we have made sure that everything that we are releasing has been polished to our best.
A lot went into this version of Paranoid Android, specially on the CAF side (Nextbit / OnePlus / Non-nexus devices). We ship with custom in-house kernels tweaked to provide the best power-battery combo, new functionalities and designs for hardware-specific options.
The main features and enhancements that you will probably end up noticing are our custom Quick Settings tile reordering functionality, floating window support, immersive mode, the new on-the-spot interface and CM Theme Engine. There's much more to come, so sit tight!
Feature highlights
Floating mode
Immersive mode
On-the-spot controls
Quick settings re-order
Paranoid OTA (Updates)
Battery styles
Advanced power dialog
Quick pull-down
Theme engine
CAF specifics
Enhanced kernel + control
Advanced buttons control
Advanced gesture control
Alert slider support
Fingerprint support
Ambient display support
Download
Get our latest Nextbit Robin build here.
Changelogs
As we're getting back into the thread game, keeping up with threads and updating them as per changelogs can be too hectic given our schedule. However, very detailed changelogs always go up on our Google+ page, follow us for constant updates!
Instructions & requirements
We highly recommend you to follow these instructions very carefully. Users usually tend to skip a few steps and eventually fall in trouble. Are you with me? Good. Let's get this train going.
Just a few things to keep in mind first -
If you're coming from another ROM / Stock, your system data (not internal storage) will have to be wiped. This includes apps, accounts, messages, call logs etc.
There's been some users complaining about different GAPPS variants messing up installs and causing a ton of issues. Upon investigating it seems OpenGapps Mini/Nano and Banks GAPPS work best.
Understand that Paranoid Android is a custom ROM and it might lead to addiction as it's relatively good. We shouldn't be accused of anything just incase your cat starts drinking wine. Things get a little woozy in the Paranoid World.
Some brain might be involved if things go wrong. Not a lot though, as much to solve what's 1+1.
Okay let's get to the main bit -
Once you have all the required files - boot into recovery and wipe the bananas out of your device. Get into the wipe menu and wipe data, system, cache and dalvik cache (basically everything except Internal Storage).
Once wiped, get into the "Install from zip" menu and select the ROM zip. (pa_robin_6.x...). Once added to the install queue, TWRP will ask you if you want to add more zips into the queue - Click on "add more zips" and select the GAPPS package.
Swipe the bar on the bottom to flash/install zips. Once both zips are done installing - Reboot into system and set-up your device, do not do anything else.
Once you're done setting up your device - well that's when you're done. One thing though - Make sure you DO NOT INSTALL any other zip in the same queue as the ROM & GAPPS. Meaning, do not flash anything like a kernel or a root package while installing the ROM. We recommend you do that AFTER you're done setting up your device.
Important / Useful links
OpenGapps / Banks GAPPS
SuperSU root package
Paranoid Android Community (G+)
Our kernel sauce (Robin)
As always, we listen to what you have to say. Help us make PA better by submitting good bug reports possibly with a log attached. Learn how to take logs here. Submit bug reports and we'll try to iron out issues as soon as possible - it really helps a lot.
Our device maintainers and CAF caretakers @TheCrazyLex, @xboxfanj and @thecrazyskull are right here at xda. Mention (@) them if you need some assistance and/or when reporting bugs.
Cheers and #StayParanoid!
XDA:DevDB Information
Paranoid Android 6.0.3 - AOSPA - Nextbit Robin, ROM for the Nextbit Robin
Contributors
TheCrazyLex, xboxfanj, arzbhatia, The whole PA Team
Source Code: https://github.com/AOSPA/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CAF
Version Information
Status: Stable
Created 2016-09-09
Last Updated 2016-09-09

Reserved

Reserved

Nice work!

SO much YASSSS!

No battery charging light, no way to disable notification light pulse while in DND.
Strange, there are apps that aren't showing up in "apps with usage access" greenify and screenwise meter require this on.
This rom makes the phone buttery smooth and fast! It's a whole new beast that's for sure.
Edit: attached is a general log. There's some quirkiness to the rom.

Best custom rom ever tried on the Robin. Totally lagfree, smooth and bugless.

Anyone else's speakerphone not working on calls

moosefist said:
Anyone else's speakerphone not working on calls
Click to expand...
Click to collapse
What do you mean? Explain better.
Btw working speakerphone here, like everything else. No bugs, maybe only floating peek have some issues.

XxXPachaXxX said:
What do you mean? Explain better.
Btw working speakerphone here, like everything else. No bugs, maybe only floating peek have some issues.
Click to expand...
Click to collapse
Yeah, it actually works after clearing my cache and dalvik + a reboot. Overall the rom is working pretty great now

Android wear bluetooth battery optimization
Morning all. I have been using this Rom for about 5 days now and I love everything about it except 2 things: Android Wear and Bluetooth optimization for it. I use the Huawei Watch and on the stock ROM, my phone battery lasts about a day and a half of light use with the watch connected at all times. And if I were to go into battery stats, everything would look normal. Since switching to PA, My battery lasts barely 4 hours when I'm not using it. When I look at the battery stats, it shows Bluetooth just draining it 99%. Are there some tweaks you plan on doing to this ROM in order for Smartwatch users to be able to use this as well? This ROM is awesome, but unless there is some sort of fix for this, I can't use it. Is anyone else having this issue? I am willing to provide logs as well, if someone can advise me how to take them.

dawg3476 said:
Morning all. I have been using this Rom for about 5 days now and I love everything about it except 2 things: Android Wear and Bluetooth optimization for it. I use the Huawei Watch and on the stock ROM, my phone battery lasts about a day and a half of light use with the watch connected at all times. And if I were to go into battery stats, everything would look normal. Since switching to PA, My battery lasts barely 4 hours when I'm not using it. When I look at the battery stats, it shows Bluetooth just draining it 99%. Are there some tweaks you plan on doing to this ROM in order for Smartwatch users to be able to use this as well? This ROM is awesome, but unless there is some sort of fix for this, I can't use it. Is anyone else having this issue? I am willing to provide logs as well, if someone can advise me how to take them.
Click to expand...
Click to collapse
Hey thanks for pointing this out! You can do an adb logcat, or download aLogcat to get the log: https://play.google.com/store/apps/details?id=org.jtb.alogcat&hl=en

dawg3476 said:
Morning all. I have been using this Rom for about 5 days now and I love everything about it except 2 things: Android Wear and Bluetooth optimization for it. I use the Huawei Watch and on the stock ROM, my phone battery lasts about a day and a half of light use with the watch connected at all times. And if I were to go into battery stats, everything would look normal. Since switching to PA, My battery lasts barely 4 hours when I'm not using it. When I look at the battery stats, it shows Bluetooth just draining it 99%. Are there some tweaks you plan on doing to this ROM in order for Smartwatch users to be able to use this as well? This ROM is awesome, but unless there is some sort of fix for this, I can't use it. Is anyone else having this issue? I am willing to provide logs as well, if someone can advise me how to take them.
Click to expand...
Click to collapse
Thank you very much we will investigate the cause of the issue

I have the same issue with my Pebble, battery stats reported Bluetooth percentage 126%!!
As reported on Nextbit Community thread, I have several problems on phone calls, some freeze and reboots (the last one today, using Waze).
And a very huge battery drain, mainly on mobile network activities (not only for data, but for phone signal too).
With the Stock ROM, battery lasts more than a day; actually, I'm charging 2-3 times a day, when the main usage for me is on email (Gmail with Exchange working account).
Hope next version could work better on my Robin!

sauroz said:
I have the same issue with my Pebble, battery stats reported Bluetooth percentage 126%!!
As reported on Nextbit Community thread, I have several problems on phone calls, some freeze and reboots (the last one today, using Waze).
And a very huge battery drain, mainly on mobile network activities (not only for data, but for phone signal too).
With the Stock ROM, battery lasts more than a day; actually, I'm charging 2-3 times a day, when the main usage for me is on email (Gmail with Exchange working account).
Hope next version could work better on my Robin!
Click to expand...
Click to collapse
Can you provide a log? That would definitely help the team!

Bluetooth is weird. There is miscalculation on the battery usage.

dorupero said:
Bluetooth is weird. There is miscalculation on the battery usage.
Click to expand...
Click to collapse
I'm having the same issue. Also battery life really bad when I leave BT on

Has anyone gotten Viper4Android to work in this ROM? I placed the APK in priv-app to install it, but sound isn't processed.

Same (Bluetooth) battery issues
I'm having the same problems as others, so far. I have a Pebble watch with me at all time, which means bluetooth stays on at all times. My battery is less than optimal after flashing PA. Whenever I check the battery page, Bluetooth is the only thing that shows up. No Screen, or WiFi, or any other apps for that matter.
Don't know how to share screenshots here, but it's more or less identical. 80% battery left, battery page shows 20% of battery taken by Bluetooth.

I'm currently running CM but has the same problem. Amplify seems to have fixed this Bluetooth bug for me.
Sent from my Robin using XDA-Developers mobile app

Want to make sure before I buy this phone....

Hi All!
So I'm just about to get this phone after a loooong time with my HTC One m7.
I'm not a massive fan of google as a company and their tracking so for my HTC I did the following:
Rooted, installed cyanogen
Installed minimal gapps package
Installed Greenify to hibernate apps I don't use often
Used Privacy guard to limit permissions for apps
I also disabled google play and all sorts of other things.
Now I'm not expecting to install cyanogen on the 5t but what about all the other stuff? Are there better solutions 4 years later?
Ideally I'd like to get the 5t setup similarly to how I had the HTC.
I'd welcome any thoughts from those who know
Thanks!

SGSII_LEDnotify said:
Now I'm not expecting to install cyanogen on the 5t but what about all the other stuff? Are there better solutions 4 years later?
Click to expand...
Click to collapse
Because Cyanogen is gone. What was left of it became Lineage OS which is a continuation of Cyanogen, and it has Privacy Guard. Lineage OS for the 5t is currently in beta, but should be working soon.
https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-15-0-t3721193

Also, with battery optimization built into Android now, you probably don't need Greenify.
With Lineage (or any other custom ROM), you can forego Google apps or do a minimal install. Check out your options here: http://opengapps.org/

the Doctor said:
Also, with battery optimization built into Android now, you probably don't need Greenify.
With Lineage (or any other custom ROM), you can forego Google apps or do a minimal install. Check out your options here: http://opengapps.org/
Click to expand...
Click to collapse
Thanks, so it sounds like it'll be a similar procedure then.
I'm hot on the trail, I found this page detailing how to remove google from a phone:
https://android.gadgethacks.com/how...-google-from-your-android-experience-0162547/
I didn't realize I could essentially get away with not even installing play store and the article shows some replacement apps for the stock things I use most like calendar, calculator, mail etc.
So I need Lineage if I want privacy guard, however I do see the way android handles permissions has changed:
https://www.howtogeek.com/230683/how-to-manage-app-permissions-on-android-6.0/
Just trying to form a plan of action really, for example on my paid apps (swype and nova launcher) can I simply copy across the apks?

I guess more pertinent questions would be:
Do I need Lineage in order to completely remove google from the phone?
Are there equivalents to privacy guard or are the controls in the stock rom enough?
Will Lineage use the OP features like slider control and camera app?
The stock rom seems pretty snappy and optimised for the device, can I get the benefits of Lineage whilst sticking with the original OS?

SGSII_LEDnotify said:
Just trying to form a plan of action really, for example on my paid apps (swype and nova launcher) can I simply copy across the apks?
Click to expand...
Click to collapse
Paid apps may depend on Google services for verification.

the Doctor said:
Because Cyanogen is gone. What was left of it became Lineage OS which is a continuation of Cyanogen, and it has Privacy Guard. Lineage OS for the 5t is currently in beta, but should be working soon.
https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-15-0-t3721193
Click to expand...
Click to collapse
Correct me if I'm wrong, but I didn't think Lineage 15 had Privacy manager in it yet? It is in Lineage 14.1.
As for the OP, as the 5T arrives, you can unlock it, root it, and remove what you don't want. You can disable (or remove) the Google apps, and the OnePlus services, as well as block them from Cell / Wifi connectivity if you wish. You have some of the privacy features that are built into the stock android, but not as fine as the privacy manager that was included in Lineage.
This is why I had hoped Lineage 14.1 would be worked on, it's also the only way we will get an official release right now (Especially with the similarities to the 5 which already has an official release). Unless Lineage 15.1 is close to release? Either way 15.1 is still missing several features from 14.1.

Thanks for this.
i've learnt a bit more since last posting about blobs and shims etc.
What I'm seeing is that there are tradeoffs for ROMs in terms of functionality and features, particularly in relation to the camera.
So like you said, rooting isn't an issue and then I can use titanium to remove google from the phone and replace with alternative apps. This would also give me the chance to access the playstore and copy over my paid apps. I'm not sure how 'completely' I can remove google this way, I assume completely, if there's no account on the phone and no apps then that's it isn't it?
So that looks like plan A for now, although that way I lose the Privacy Guard features I really like.
Plan B would be to go with Lineage to get PG but then I lose the OP camera app. I don't know if you get face unlock, slider control and other handset specific functions with this ROM.
I really like the 'per-permission' approach to Privacy Guard but you seem to lose a lot in the tradeoff.
Thanks again for the input.

SGSII_LEDnotify said:
What I'm seeing is that there are tradeoffs for ROMs in terms of functionality and features, particularly in relation to the camera.
Click to expand...
Click to collapse
There are, but it's getting there. You have to remember it's a new device. The 5T is first device I've bought that did not have official CM / Lineage support (or at least a fully working version) already out at my time of purchase. The only reason I bought it is because I know there will be a version at some point. I bought two 5Ts one for my wife, and one for myself. Mine sat in the box for a few weeks unopened as I really didn't think I would like it without Lineage.
So the Camera, quite frankly Snap in Lineage stinks on all devices. It takes pictures, and functions as a camera, but not a good one. On my Nexus 5X, I have to use a modded Google Camera, on my Wife's and son's old Honor 5X we use Open Camera. Even on the 5T you'll see in some situations some people are getting better pictures out of the modded Google Camera. Even on the OOS, I've been playing around with the Google Camera, and prefer it's pictures in some situations as well. They are still working out some bugs with it, however again a new device, they will get these bugs worked out. We are all still essentially "early adopters".
As for the privacy manager it's gone a little down hill in Lineage. See this Reddit Thread: Link Here.
I posted actual screenshots of the differences here. I posted these in a couple different threads here on XDA, but it didn't go anywhere.
As for what you can do in OOS, it's actually fairly similar to what's now available in Lineage. This is from the 5T in the latest 7.1.1 update:
{
"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"
}
Same thing, so I blocked Dolphin from being able to Change system settings:
All those pages are available for system apps as well. So if you want to block Play Services, or the Play store from the Internet you can. First thing I did was remove a lot of the Google apps from the phone, as well as the OnePlus stuff. Most of this stuff, I removed with TitaniumBackup, and I just removed it entirely rather than freezing it.
As for FaceUnlock / Slider control, that stuff I'm sure will get figured out. However, we're still just to close to launch, there will be stuff that won't work. Heck we don't even have a selection of brand name cases to choose from and people are wanting fully functional custom roms... Give it time, it will be sorted out.

Again, all valuable info, thanks.
So eventually everything will be sorted out? Is that a reasonable expectation or will there always be things that are 'compromises'?
I see that OP has no intention of releasing the camera 'blob'. I also saw the chinese ROM comes without gapps, maybe that's available somewhere with a language pack?
It's a world I only briefly dipped my toe into when I first did my HTC to get cyanogen so I don't keep up on all the latest news and developments so any and all advice is greatly appreciated. Bit worrying to see the lack of maintenance on PG in Lineage though, that's a red flag for me, basically PG is the only thing keeping it in the mix. From the videos I've seen custom ROMs are slower than stock too.

SGSII_LEDnotify said:
So eventually everything will be sorted out? Is that a reasonable expectation or will there always be things that are 'compromises'?
Click to expand...
Click to collapse
I think everything will be sorted out. It will take some time. It's still way too close to release date to expect things to be fully ironed out, but things are already moving at a good clip honestly.
SGSII_LEDnotify said:
I see that OP has no intention of releasing the camera 'blob'.
Click to expand...
Click to collapse
This is correct. Unless some mods the camera to work some how in a custom ROM you are out of luck. They already have Google camera partially working, taking better pictures in some instances with OOS and custom ROMs. Yes it still has some issues, like needing a separate app for front and rear cameras. Again it's still early we'll have to give it time. I don't see the OP camera coming to custom ROMs, I see a "third party solution" of some sort being a solution here.
SGSII_LEDnotify said:
I also saw the chinese ROM comes without gapps, maybe that's available somewhere with a language pack?
Click to expand...
Click to collapse
I don't know... You can pretty much remove what you want from OOS as well as block what you want from connecting to data / wifi this would make me happy enough until Lineage gets up and running. Once Lineage is released, as with all their builds, it will be without Gapps.
SGSII_LEDnotify said:
It's a world I only briefly dipped my toe into when I first did my HTC to get cyanogen so I don't keep up on all the latest news and developments so any and all advice is greatly appreciated. Bit worrying to see the lack of maintenance on PG in Lineage though, that's a red flag for me, basically PG is the only thing keeping it in the mix.
Click to expand...
Click to collapse
I agree. To me one of the biggest reasons to run Lineage is the privacy guard. I'm hoping they have just been shifting time and energy to get Lineage 15 ready.
SGSII_LEDnotify said:
From the videos I've seen custom ROMs are slower than stock too.
Click to expand...
Click to collapse
I would disagree with this. Custom roms for me have always been faster and had better battery life. Admittedly I typically run custom kernels as well and spend time tweaking things which can impact battery life. I also tend to strip unnecessary things out of the OS as well. It's just like a PC, if you have a bunch of stuff starting up at bootup and running in the background your performance will be slower. I guess everyone's mileage will vary though.

Thanks, like you said, I guess it's still early days but hopefully we'll get some really comprehensive ROMs with good workarounds (like the googlecam app). I appreciate this is a lot of hard work with a lot of trial and error for the devs.
Looks like rooting and 'optimizing' the stock software is plan A for now. I'll investigate replacements for PG, if there are any.
I'm the same, I always tear a windows install apart, disabling services and optimizing the rest of the OS as needed. I was surprised to see the ROMs performing slower than stock (in terms of opening apps at least) but those were the videos I saw. I expect with time everything will fall in to place and patience is the key for now.
I guess I'm just excited to finally get a new phone after 4 and half years
OhioYJ said:
I think everything will be sorted out. It will take some time. It's still way too close to release date to expect things to be fully ironed out, but things are already moving at a good clip honestly.
This is correct. Unless some mods the camera to work some how in a custom ROM you are out of luck. They already have Google camera partially working, taking better pictures in some instances with OOS and custom ROMs. Yes it still has some issues, like needing a separate app for front and rear cameras. Again it's still early we'll have to give it time. I don't see the OP camera coming to custom ROMs, I see a "third party solution" of some sort being a solution here.
I don't know... You can pretty much remove what you want from OOS as well as block what you want from connecting to data / wifi this would make me happy enough until Lineage gets up and running. Once Lineage is released, as with all their builds, it will be without Gapps.
I agree. To me one of the biggest reasons to run Lineage is the privacy guard. I'm hoping they have just been shifting time and energy to get Lineage 15 ready.
I would disagree with this. Custom roms for me have always been faster and had better battery life. Admittedly I typically run custom kernels as well and spend time tweaking things which can impact battery life. I also tend to strip unnecessary things out of the OS as well. It's just like a PC, if you have a bunch of stuff starting up at bootup and running in the background your performance will be slower. I guess everyone's mileage will vary though.
Click to expand...
Click to collapse

Btw, I'd be interested in a heads up on the BIB. Again, it's not a world I'm familiar with so if you could point me towards some knowledge it would be appreciated
OhioYJ said:
I would disagree with this. Custom roms for me have always been faster and had better battery life. Admittedly I typically run custom kernels as well and spend time tweaking things which can impact battery life. I also tend to strip unnecessary things out of the OS as well. It's just like a PC, if you have a bunch of stuff starting up at bootup and running in the background your performance will be slower. I guess everyone's mileage will vary though.
Click to expand...
Click to collapse

SGSII_LEDnotify said:
Btw, I'd be interested in a heads up on the BIB. Again, it's not a world I'm familiar with so if you could point me towards some knowledge it would be appreciated
Click to expand...
Click to collapse
On most of my current devices I've been using the ElementalX kernel and the EX Kernel Manager. It's what I'm using on my 5T as well, although I'm still tweaking the settings.
This is what I used on my Nexus 5X, Irrelevant for the 5T, but sort of will give you an idea of what I changed, and things I tested?
I know so far on all my devices, including my Nexus 5X (which supported fast charging, OEM charger was a 3 amp charger) my battery always lasted longer on each charge being slow charged (0.35 - 0.5 amp) so this is generally what I charge all my devices at. I haven't even used my "dash charger" yet. Although I guess I should try it for a few cycles and see if the same does apply to this device.

Question Any Custom ROM with AOD, dt2w and pocket detection working properly?

Hey! So, I've tried some AOSP ROMs and I encountered with the same problem in all of them. AOD, dt2w and pocket detection are BATTERY KILLERS. Specially AOD, because, when it's activated, the device doesn't enter into deep sleep.
Don't get me wrong, they work as they should, maybe pocket detection with better results in some ROMs than other.
You can easily say "Turn them off" and yeah, I disabled them and the battery drain is almost nothing, no matter what ROM I'm into.
But, I really like having AOD, enjoy my AMOLED panel and squeeze as much as I can, but not in behalf of HUGE battery drain.
And it sucks, because, in MIUI you can have them enabled and working with less battery draining, but I don't like MIUI like many of us here.
I use BBS app to check the draining, and there is Wakelock named PowerManage.SuspendLockout, that is always active when I have AOD enabled, to consider...
Is it related to Xiaomi not releasing the code or whatever is call, or some hardware issue, or maybe a poor ROM optimization?
Have you find any ROM where these features, specially AOD, are not battery killers?
PS: In every ROM I do a clean install, no backup restore, and almost 0% background apps consumption, so, no, it's no a setting or app related issue...

DotOS 5.12

I tested only 3 AOSP roms (crdroid, havoc and evoX) and they all have this issue. The MIUI didn't. I'm also wondering why that is and I would really like to use AOD. As you said, we have an AMOLED panel and not being able to use it fully kinda sucks no matter if is is just a gimmick. Not sure if it's a kernel issue or a rom issue but it definitely isn't a hardware issue since it's working without flaws on MIUI. Would be great to hear from some rom maintainers about this.
Can someone confirm if it's really working with deep sleep on DotOS? I won't flash it, even if that's true but maybe the maintainer can share the fix with the other roms?

REDOTHELLO said:
DotOS 5.12
Click to expand...
Click to collapse
Have you tried? Does this ROM solve this issue?

I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher

REDOTHELLO said:
I am not using AOD and pocket mode and dt2w is on statusbar DotOS use pixel launcher
Click to expand...
Click to collapse
So, how can you recommend the ROM if you are not using what I need? xD

Oxnap said:
So, how can you recommend the ROM if you are not using what I need? xD
Click to expand...
Click to collapse
I tried so many kernels and specific fixes that claims to fix the issue all ended up in failure, like you I love to have AOD but not at the expense of huge battery loss.

Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.

maybe we need a special Kernel for the best result between AOD and Battery

I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers

-GREY said:
Just my opinion. I think there is nothing we can do about the battery. Its a hardware/quality issue. I mean, the battery of poco f3/mi 11x is not good as you see from other giant brand like samsung.
Click to expand...
Click to collapse
You trolling, for sure. My battery is great, better or the same as s21++++

LiNe1771 said:
You trolling, for sure. My battery is great, better or the same as s21++++
Click to expand...
Click to collapse
I could not agree more, I never get less than 10 hours SOD, usually I charge my phone once every 50 hours. Best battery on a Smart phone I have ever had.

Barracuda77777 said:
I did a clean flash of my own Lineage rom as something got screwed while trying fixes for AOD, this is a week ago, brightness was being reset to lowest on each wake up.
So, I decided to try AOD just now to see if it works, and it does!
For the first time the cpu goes to deep sleep even though AOD is switched on.
I have built and flashed no less than 80 builds, It pays to do a clean flash once all source code have settled.
This is the Commit that I believe fixed the issue:
alioth: Enable config_powerDecoupleAutoSuspendModeFromDisplay · AliothDevelopment/[email protected]
Contribute to AliothDevelopment/android_device_xiaomi_alioth development by creating an account on GitHub.
github.com
As I said above, I dirty flashed with the commit above and still with AOD on no sleep, so only after a clean flash it is working perfectly, Clean flashing is important if you have flashed many builds with many changes in the Kernel/device trees.
cheers
Click to expand...
Click to collapse
Cool, did you make your own LOS ROM?

Oxnap said:
Cool, did you make your own LOS ROM?
Click to expand...
Click to collapse
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic

Barracuda77777 said:
Yes, I have been since i got the phone more than two month ago.
I am an open source advocate/fanatic
Click to expand...
Click to collapse
Why don't you start your own ROM thread? Maybe I could help you on testing

Oxnap said:
Why don't you start your own ROM thread? Maybe I could help you on testing
Click to expand...
Click to collapse
I am not sure many would like the fact that mine runs on MicroG, I have many of the apps that usually comes with the ROM taken out and replaced with other better open source alternatives.
Gallery, messages, music to name a few
As I am 100% self dependent on my services, I don't rely on anyone else:
I run and maintain. The following services:
1) XMPP secure and fully encrypted chat server (prosody) for family and friends)
2) run my own VPN server when out of the house.
3) run my own email servers since 2008
4) Run my own password manager server (Bitwarden)
5) run Synching server to keep all my Linux servers, Linus PCs and Android Live Backed up.
6) Run my Own Cloud Server ( NextCloud)
7) My own Music personal server I use Gelli (open Source) to listen.
8) my own open source router (pfsense)
9) my own DNS server ( Pihole )
I also build most of the apps I use :-]
Everyone needs differ than others, my sources for building my ROM are here, feel free to download, use or fork.
barracuda777 - Repositories
barracuda777 has 116 repositories available. Follow their code on GitHub.
github.com
Happy building.