[ROM][official] AICP 13.1 - o8.1 - castor/_windy - Xperia Z2 Tablet Android Development

[ROM][official] AICP 13.1 - o8.1 - castor/_windy - Xperia Z2 Tablet Android Development

{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: https://dwnld.aicp-rom.com
Official builds will be deleted from our servers every month due to maintenance services. We advise everyone to keep at least the latest or best working build on their device as a backup. Maybe copy it to a cloud service or USB too.
Test version downloads Version 13.1
Download link castor_windy: https://basketbuild.com/devs/SpiritCroc/castor_windy/AICP-o8.1
Download link castor: https://basketbuild.com/devs/SpiritCroc/castor/AICP-o8.1
Google Apps
http://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico
Full Changelog link: https://dwnld.aicp-rom.com
You tell...
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the deivce, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/o8.1
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
rcstar6696
AdrianDC
All the other contributors to sony msm8974 platform
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 13.1 castor/_windy, ROM for the Sony Xperia Z2 Tablet
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: No Longer Updated
Created 2018-05-10
Last Updated 2020-10-18

Nice to see AICP again. Downloading now.

Well, i have been test driving this ROM for almost 2 full days. Must say very snappy and smooth so far. Have not had time to test everything but i am making my way through it. So far NO major issues which i have found. Camera, sensors, wifi, bt, all working as they should. Battery seems decent so far with continued use and reboots. No FC's on anything. All AICP extras are working as they should. Will be trying for another day then make the move to my DD.
AND YES EVERYONE.....QC IS WORKING. I AM GETTING AROUND 2400mA DURING CHARGING. NICE TO SEE>>>>>
Nice job SpiritCroc. :good::good:

_Sherrif said:
Well, i have been test driving this ROM for almost 2 full days. Must say very snappy and smooth so far. Have not had time to test everything but i am making my way through it. So far NO major issues which i have found. Camera, sensors, wifi, bt, all working as they should. Battery seems decent so far with continued use and reboots. No FC's on anything. All AICP extras are working as they should. Will be trying for another day then make the move to my DD.
AND YES EVERYONE.....QC IS WORKING. I AM GETTING AROUND 2400mA DURING CHARGING. NICE TO SEE>>>>>
Nice job SpiritCroc. :good::good:
Click to expand...
Click to collapse
hey _Sherrif, you reviews are the best & big thanks
is auto-rotate working? i got problems with LOS based 8.1 ;(
___________________________________
thank you SpiritCroc for your hard work!
_____________________________________

@smoschi,
yes auto-rotate is working fine for me. I have to say this is the smoothest working ROM i have tried in a while...tablet or phone. Very smooth and battery is great for me and i play alot of heavy graphics gaming on my tab i.e War Robots & Asphalt 8.
It is my daily driver for mt CW Tablet. It is well worth trying......

smoschi said:
hey _Sherrif, you reviews are the best & big thanks
is auto-rotate working? i got problems with LOS based 8.1 ;(
___________________________________
thank you SpiritCroc for your hard work!
_____________________________________
Click to expand...
Click to collapse
I had this problem on LOS 8.1, this solution sorted this problem for me.
Move this file (vendor/etc/sensor_def_qcomdev.conf) to system/etc and test Sensors again after a reboot.

_Sherrif said:
@smoschi,
yes auto-rotate is working fine for me. I have to say this is the smoothest working ROM i have tried in a while...tablet or phone. Very smooth and battery is great for me and i play alot of heavy graphics gaming on my tab i.e War Robots & Asphalt 8.
It is my daily driver for mt CW Tablet. It is well worth trying......
Click to expand...
Click to collapse
D**n, I finally find out an Oreo ROM with working QC but my windy just "dead". I let it drain almost 2 days, the good news is when plugged, the LED is now blinking red again, I hope after totally drained out, it will able to recharge and power on.
Thank for your quickly reviews and confirmation on QC, @_Sherrif
Btw, do you have any problems with the annoying system notifications (external sd card....)?
Edit: my bad, many thank @SpiritCroc for all of your hard work to keep supporting castor/windy

romeo_coi said:
Btw, do you have any problems with the annoying system notifications (external sd card....)?
Click to expand...
Click to collapse
Did you tap the SDCARD in the notification? It should allow you to set up as portable, name of storage may be wrong, but the top selection, then after selecting it should accept your card.
NOW, when my ex-sdcard was formatted as "EXT4", sometimes i would have problems getting the new ROM to accept my sdcard. The only way to get the new ROM to accept would be a full format of the exsdard. I was not going to do this for every new ROM install just like most of us.
Since i have re-formatted my ex-sdcard to "vfat" or fat32. Now i never have any problems regardless of the ROM i choose. If you decide to re-format of course be sure to back it up first, but that should be a gime. FYI - I have no issues running my exsd as VFAT formatted, actually it is smoother IMHO.
Hope this helps...

_Sherrif said:
Did you tap the SDCARD in the notification? It should allow you to set up as portable, name of storage may be wrong, but the top selection, then after selecting it should accept your card.
NOW, when my ex-sdcard was formatted as "EXT4", sometimes i would have problems getting the new ROM to accept my sdcard. The only way to get the new ROM to accept would be a full format of the exsdard. I was not going to do this for every new ROM install just like most of us.
Since i have re-formatted my ex-sdcard to "vfat" or fat32. Now i never have any problems regardless of the ROM i choose. If you decide to re-format of course be sure to back it up first, but that should be a gime. FYI - I have no issues running my exsd as VFAT formatted, actually it is smoother IMHO.
Hope this helps...
Click to expand...
Click to collapse
Thanks for your reply.
In my cases, I haven't tried to format external sd card to other format yet. The problem I meant is: after the first time I config my ext sd card (after finished set up new ROM), there's a system notification about a new card, and it'll be there no matter what I do.
My windy still blinking red when plugged in, may be tomorrow it will drain out to zero, then I will recharge it and try to re-format my card with this ROM and see what happens.

romeo_coi said:
SDCARD issue & My windy still blinking red when plugged in
Click to expand...
Click to collapse
Are u able to use and access your ex-sdcard? IF not, the system is not recognizing it for what ever reason. Maybe someone more versed can help with this issue. If you do decide to format the sdcard try vfat. I have been very happy with it so far and have been using for 7-8 months now. No storage issues or nandroid backup issues with the vfat format. Transfer rates seem a bit slower but i can live with that.
For the battery. Search the XDA forums and find the info to calibrate / re-calibrate your battery. Can't remember exactly what to do, but i did it with my HTC phone and it fixed my battery problem with not showing levels correctly. Maybe this will help with your battery issue as well.
From what i can remember you need to remove a file from a system folder, do a full charge with the tab off, etc. It may or may not help, but worth a try for sure.
I know it is not the answer you needed but it may help your battery situation. I

_Sherrif said:
Are u able to use and access your ex-sdcard? IF not, the system is not recognizing it for what ever reason. Maybe someone more versed can help with this issue. If you do decide to format the sdcard try vfat. I have been very happy with it so far and have been using for 7-8 months now. No storage issues or nandroid backup issues with the vfat format. Transfer rates seem a bit slower but i can live with that.
For the battery. Search the XDA forums and find the info to calibrate / re-calibrate your battery. Can't remember exactly what to do, but i did it with my HTC phone and it fixed my battery problem with not showing levels correctly. Maybe this will help with your battery issue as well.
From what i can remember you need to remove a file from a system folder, do a full charge with the tab off, etc. It may or may not help, but worth a try for sure.
I know it is not the answer you needed but it may help your battery situation. I
Click to expand...
Click to collapse
Thanks for your kindness, @_Sherrif
I did some research and realized a lot of other users had the same symthomp, so I think the problem isn't caused by battery but the tablet itself.
My windy finally drained out, after 1h recharged, I managed to boot into recovery and make a clean flash of AICP.
At first glance, everything such as bluetooth, wifi, gps, audio, touchscreen... are as smooth as you reviewed. The annoying notification doesn't exist in this ROM.
I was tested the QC but I only get 1200mA with a 3rd party QC3.0 charger, the original Sony charger is not at my office, I'll check it whe I'm home.

i luv this rom best ever i got! big thanks
 @SpiritCroc: is this your right paypal-donation-account?
Donate to
AICP-ROM
only problems with playstore, want install apps (hanging in downloading loop ........ ) ;(
deleted cache & data from google services & playstore. maybee wrong latest opengapps 8.1 (arm)?
maybee my external sd card buggy?
@_Sherrif: how you format your ex-sd-card from ext4 to vfat? in twrp? thx
thx guys

_Sherrif said:
AND YES EVERYONE.....QC IS WORKING. I AM GETTING AROUND 2400mA DURING CHARGING. NICE TO SEE
Click to expand...
Click to collapse
romeo_coi said:
I finally find out an Oreo ROM with working QC
Click to expand...
Click to collapse
Actually Carbon ROM should have working QC as well, since I'm following their device tree and have QC from them
smoschi said:
i luv this rom best ever i got! big thanks
@SpiritCroc: is this your right paypal-donation-account?
Donate to
AICP-ROM
Click to expand...
Click to collapse
I personally don't accept donations right now (makes me feel more free to not fix bugs/implement user requests when I'm busy otherwise), but I'm happy about donations to AICP, since this helps my team to cover server costs / pay less out of their own pockets. Great to hear you like AICP!

smoschi said:
i
only problems with playstore, want install apps (hanging in downloading loop ........ ) ;(
deleted cache & data from google services & playstore. maybee wrong latest opengapps 8.1 (arm)?
maybee my external sd card buggy?
@_Sherrif: how you format your ex-sd-card from ext4 to vfat? in twrp? thx
thx guys
Click to expand...
Click to collapse
I am having no issues with PlayStore downloading. I use GZR-Gapps ZERO and never have any issues. Very small Gapps package with just the bare bones of Google stuff. Like 60mb or so. If you want to try do a search on AFH for "GZR-Gapps" then select the flavor of your choice, but not arm64, for our device.
I do not format in TWRP, my exsd anyway. I use a partition manager, Mini-Partition Tool to format my sdcard cards and thumb drives and Hard Disks. Google for it. Very nice program. to use vfat format the card as fat32.
NOTE* You do not need Mini-Tool to do this, a quick format in windows with fat32 should work fine. Be sure to remove the sdcard from the device and place in either the s slot or a reader. Copy all of your data to a safe location, takes a while, format...reload the info to the newly formatted card and re-insert.
IMHO, I don't think the sdcard format will solve the Play problem though, but it may.
Hope this helps....

SpiritCroc said:
Actually Carbon ROM should have working QC as well, since I'm following their device tree and have QC from them
...!
Click to expand...
Click to collapse
I can confirm QC is not working with Carbon ROM, both official and rcstar's test builds . I'm working in a cellphone accessory chain stores so I tested it with several QC certified chargers: Anker, Aukey, Promate, Belkin.... and none of them worked. In my last test, QC in your build is working with a Promate QC3.0 charger @5V/~2.8A (FYI I came to your build directly from latest Carbon test build). Battery life seems to be better than Carbon with same scenario (I got about 8h onscreen).
The only problem I've got is sometimes SystemUI crashed but I think it caused by myself. Everything else is working flawlessly.:good:

Just pop in herevto say that everything is working well. Good job here

seriously QC is working
Finally, custom ROM with working quickcharge! Trust me, I tried them all, QC not working for me anywhere except original SONY ROM (I have original SONY QC charger)! So this is my new daily driver, and so far everything working as expected. Good job, thanx...

Hi, good work with the ROM... I am using the test ROM since I have an SGP521 (Xperia tablet Z2 LTE).
Few things I notice:
1) Netflix cannot be installed properly
2) There is no support for IR port
3) There are not the sony mini apps anymore, expecially the IR remote app which I find very useful
4) Magisk get stopped time to time
When do you plan a stable release for the SGP521?
Regards
Michael

redoracle said:
Hi, good work with the ROM... I am using the test ROM since I have an SGP521 (Xperia tablet Z2 LTE).
Few things I notice:
1) Netflix cannot be installed properly
2) There is no support for IR port
3) There are not the sony mini apps anymore, expecially the IR remote app which I find very useful
4) Magisk get stopped time to time
When do you plan a stable release for the SGP521?
Regards
Michael
Click to expand...
Click to collapse
1) Netflix might have problems because of custom ROMs or root I think
2) Sony's IR solution on z2 tablet is proprietary and not so easy to get to work on custom ROMs unfortunately
3) Yeah it's not stock ROM
4) Probably Magisk related and not ROM related
I'm planning on starting official builds for castor (LTE) soon, just waiting for some confirmation that everything (especially mobile network related, due to differences castor/castor_windy) is working fine

Many thanks for your reply... Looking forward to..

Related

[ROM][4.4.4][KTU84Q][DISCONTINUED][SlimKat - Hercules][OFFICIAL+Weeklies]

SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
SlimKat is the project name for SlimRoms based on Android 4.4 and offers the following original features:
The Real Dark Slim
Full system-wide dark interfaces. - If you like it smooth and classy.
Custom Shortcuts. Everywhere.
Hardware keys, Navigation Ring, Navigation Bar, Lockscreen, Tiles, Notifications etc. - We've got you covered.
System-Wide Keyboard Controls
Rotation, cursor control, optional emoticions, etc. - You'll be tapping away to your heart's content.
SlimCenter
Downloads, contact information, system app removal. - More fun than you can shake a stick at.
Camera Features
Trueview, Smart Capture. - Capture life moments with ease.
Important links:
slimroms.net - The official webpage where you will find everything you need to know about SlimRoms.
Slim Downloads - Download the ROM, GApps and other Addons.
Installation instructions - Follow these steps to the letter if you're about to install SlimRoms on your device.
Latest Changelog - Read here if you want information on changes in latest build.
FAQ - The most frequently asked questions with answers.
Kernel Source - The source of your device's kernel.
See Post #2 for Known Issues and Installation Notes.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Forum
Special thanks to (in no particular order):
The Slim Team
CyanogenMod
prbassplayer
wantowan2
kintwofan
Disclaimer: SlimRoms are not responsible for any damages to your device.

I do not own the SGH-T989, but I do have 3 SGH-i727 Skyrockets, and the Hercules is almost identical. My time is limited, but due to several requests for this, I wanted to share. Please help each other out, and keep the thread friendly and informative.
Installation:
Install a 4.4 compatible recovery, and reboot to recovery afterwards.
Format /system, /data and /dalvik cache.
Flash a compatible radio (see below).
Flash the ROM.
Flash GApps.
Reboot and enjoy!
Known Issues:
Power-off charging animation not working.
You tell me...
Reporting Issues:
Do NOT report issues here if you're running a non-stock kernel, Xposed and/or modules, or any other non-stock mods.
For bug reporting (stock Slim ROM/kernel/GApps only), please use the Slim Bugreport tool, accessible through Settings > SlimCenter > Bugreport to produce a zip file in the phone's storage which you then can upload to the SlimROMs Hercules Subforum for review. Please see Reporting Bugs on the Slim web site for more information.
Any issues please explain with specific details, how to reproduce the problem, and provide a Slim Bug Report (preferred, in the ROM), or a logcat. Good feedback is ESSENTIAL.
Installation Notes:
Radios: Make sure you are running a JellyBean radio or newer (T989: UVMC6 | T989D: TLMC4), and follow the installation instructions linked to in post #1. A thread for flashable radios is here.
Recovery: Recommended recovery: CWM or TWRP.
Superuser: The Slim Team has made it so the Superuser App is not enabled by default, requiring users to intentionally turn on Root access. To enable it, navigate to Settings > Developer Options > Root Access and choose Apps and ADB (even though it may appear selected). For this to work, you need to first go to Settings > About Phone and tap on Build Number several times to gain access to the Developer Options.
Also see here: http://slimroms.net/faq/slimbean/441-how-do-i-enable-root
Kernel: The kernel is based on the Moretz CM-11.0 kernel, but overclocking has been disabled to enhance stability. For sweep2wake, fast charge, and CPU freq/governor control features, I'd recommend [ROOT] Kernel Tweaker from the Play store.
Wi-Fi: Wi-Fi connection dropping issues? Check your region code in Settings > Wi-Fi > (menu key) > Advanced > Wi-Fi region code. It may be set to Europe by default, which uses a different set of Wi-Fi channels than the United States or Canada.
DPI: For information on changing the screen DPI, see here: How to change the screen density (DPI). Beware that some apps may not play nice with custom values, although normally the Slim GApps are modified to tell the Play Store and a couple of other apps that the phone's DPI is always 240.
Enjoy!

(reserved)

Initial test build: http://www.androidfilehost.com/?fid=23578570567714111

Welcome to the Hercules forum and thanks for bringing this ROM back to us. I will be testing this later this evening after work. Also I will get the word out on G+.

big fan of slim cant wait to see what this brings

Initial Impressions
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.

ArtfulDodger said:
OK after a few hours of testing, here is what I found:
First of all, the instruction to not change the governor on the stock kernel apparently applies to Wild! V6 as well. After installation, boot was just fine. Thinking I could change the governor because this was a custom kernel, I changed the governor to Intellidemand. No problem then either, but after a reboot the phone boot looped. Re-installing the kernel fixed that, but then it happened again. Also the wi-fi setting was not saving my password either. So after getting the phone to boot up (had to install the kernel once more), I set the governor to Interactive. No more boot loops after three reboots. So that was taken care of.
The other issues I encountered were extremely slow charging (only 1% charge in about a 45 minute time frame) and Google Now FCd every time I tried to open it (even after I wiped data & cache). Upon those problems I had to restore my nandroid for now. I do also want to mention some positives. The ROM really does fly, and with Slim mini gapps over 200mb of free ROM space is available so the ROM lives up to its name of "less is more". Video recording was perfect and without any delay. I have been out of the loop for a bit on changelogs, but for those who don't know the new theme engine is still not included in this ROM as of yet. The real dark Slim does work though.
Bottom line this is not yet ready for a DD IMHO, but with tweaking, could be the fastest ROM we have available. I really was almost willing to deal with the bugs because I was so impressed with the speed. The screen wake lag that plagues all the other ROMs did not happen for me here. Thanks again @NoSpamDan, I'll be happy to try future builds as well.
Click to expand...
Click to collapse
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!

NoSpamDan said:
Thanks, I appreciate the testing and feedback!
Let me first say that details are everything, especially when I don't have a test phone available...
I am looking for bugs that exist in the as-built ROM, and therefore I am unable to provide any support for 3rd party kernels... This could have caused most of the issues you experienced.
Was there a problem with the stock CM-11.0 kernel bundled into the ROM, aside from the known governor switching issue? If so, the built-in Slim Bug Report tool (Settings > SlimCenter > Bugreport) will produce a zip file you can upload here for the time being for review. Please see Reporting Bugs on the Slim web site for more information.
For random reboots (RR's), you can also try using Bootlog Uptime to automatically dump /proc/last_kmsg for you to review/upload.
The Google Now issue shouldn't have anything to do with the ROM itself, that is in GApps. And if you were using the mini-gapps package, did you install Google Search separately? According to the TRDS GApps thread, it's not included in the mini package, and you could have been missing some key library files from the GApps package.
What version of KK4.4 GApps did you install? You said mini, but was it v155, v157, v160?
For now, I would recommend using the beta GApps with Unofficial builds until an Official ROM version is released. Please bear in mind that @dankoman has been producing new beta TRDS GApps versions quite often. His discussion thread is here.
What I really need are bug reports and logs using only the stock Slim ROM/kernel/GApps... Unfortunately, without these, I won't be able to provide effective support to try and make this ROM better, much less try to get the Hercules officially supported on the Slim site.
Thanks again!
Click to expand...
Click to collapse
Yeah I was afraid you might bring the logs up, and rightfully so. Reason that I did not use the built in kernel is that I have NEVER had good experiences with stock kernels from CM. Plus with the limited governor availability, I was hoping Wild! would eliminate that problem. I was also unaware of Bootlog Uptime or I would have used it to help with this situation.
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup. After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.

ArtfulDodger said:
On Gapps, I used these from the Slim ROMs web site: http://slimroms.net/index.php/downloads/dlsearch/viewdownload/1150-addons4-4/12060-slim-mini-gapps-4-4-4-build-6-112
Google Now wasn't included so I restored it via Titanium Backup.
Click to expand...
Click to collapse
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
After the FCs, I wiped the data. Still no luck. I tried to uninstall it but when I checked settings/apps, it was still showing as installed. I should have just fresh installed it from Play or better yet, used the Banks Gapps I already had. At any rate, I know I could have fixed that problem if I had tried other things.
Click to expand...
Click to collapse
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Any idea what might have caused the slow charging? I've had that happen on official CM as well.
Click to expand...
Click to collapse
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.

NoSpamDan said:
Yeah, those GApps are pretty outdated, but should still work. TiBu on the other hand, can be pure evil sometimes...
OK. Now (Quicksearchbox.apk) is a System App, so yeah, I can see trouble with it if restored.
Not off-hand. I take it you've tried different chargers/cables...? There's an app on XDA here called Skyrocket Charger Test that, while it's labeled 'Skyrocket', based on what it queries for information, might work on the Herc to check the charging rate and type. I believe it also works on the Note 1 SGH-i717... Worth a shot to test chargers and cables for issues. It's saved me many times.
Click to expand...
Click to collapse
Well thing is, on other ROMs like PA or Beanstalk 4.4 builds I get about 40% an hour charge. I use two different chargers at home & work, both Samsung with no issues. The slow charging issue is one I've only encountered with official CM (especially 4.4 nightlies), an old Beanstalk 4.3 ROM and unofficial Carbon 4.2 build back from last fall.
On TB it really is both a blessing and a curse sometimes!

Only issue is found is SD card usage. I don't have external SD card btw
{
"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"
}

smokenbiskits said:
Only issue is found is SD card usage. I don't have external SD card btw
View attachment 2858649
Click to expand...
Click to collapse
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...

NoSpamDan said:
Thanks for the report.
I take it you did wipe /data or perform a factory reset upon installation? This will not wipe your internal SD card (music/photos/etc)...
Sometimes just a dalvik and cache wipe from recovery fixes this. A log/bugreport might help. Did you try clicking on that SDCard entry to see what app or process it says is running? Do you have Outlook installed or Exchange mail configured?
And I couldn't help but notice, are you running Juice Defender? FYI many have reported worse battery life on KitKat with that... I purchased the full version myself back when I switched from GB to ICS, but ended up ditching it when JB came along, and never looked back.
Everyone's usage/situation is different...
Click to expand...
Click to collapse
Yes to wipe everything except internal SD.
I will try a dalvik/cache wipe/battery stats and see if it helps.
Don't have either of those email clients installed.
Clicking on SD card entry in battery just shows cpu uptime for SD Card, not specific process.
I'll remove juice defender after the wipes above work/don't work, don't want too many variables changing while trying to troubleshoot. :angel:

LOL, yes, one step at a time is good. else you can end up with no clue at all

Oh, I just saw "battery stats"... and wiping those has no effect in Android 4.4. Google debunked that some time ago. See here. Recharging the device will reset the battery usage stats in Settings > Battery.
I used to wipe the battery stats myself, and I honestly didn't know there were still recoveries that still had that built in (TWRP maybe) since I've been on PhilZ Touch CWM recovery myself for a long time. No Fix Permissions either, wouldn't you know (not a bad thing, actually)...
I sure did like my placebo effect, though. I still miss it, lol.

The Dalvik/cache wipe fixed SD card issue... Thanks

First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work

ive been on this all day today without any problems! slims as good it was before

HipHopAnonymous3 said:
First, thanks for helping us all out and working on bringing us this ROM. Tried it out today and was impressed by how fast it booted and its responsiveness. Flashed through TWRP 2.7.1.0 along with newest beta slim mini gapps. Full wipe/clean install. A few things I noticed:
1) Native superuser doesn't function. Tried going into settings>advanced options>superuser and auto-allowing apps permissions...no go. Unable to create logcat/bugreport for this issue as they both require root. Fixed by flashing Chainfires SuperSU zip through TWRP
2) Battery charge speed seemed normal here
3) I live in US and wifi region code was set to Europe after install.
4) In your OP you mention radios not related to our model. The newest radio for T989 is T989UVMC6
5) Something not specific to your ROM, but with all recent ROMs (CM related?) stock messaging app no longer turns data on to send/receive MMS messages. Again, nothing on your end, just felt the need to bring attention to it.
Thanks again for your work
Click to expand...
Click to collapse
Thank you much for the feedback.
1) You have to enable Superuser through Developer options. See installation notes in post #2, with a link to Slim's FAQ on it.
2) Good!
3) I've seen this before, and will look into it, although as you said, if you drill into the Wifi > Advanced > Region code settings, you can change it to whatever. So, low priority.
4) I'll look at the assert script for the radio version. Can you link the radio thread please?
5) I haven't heard of this. I don't believe it affects the Skyrocket...? Does this happen on the recommended radios?
I have a new build compiling with a "stock-ish" version of the Moretz kernel (no over clock/undervolting).
It has sweep2wake, fast charge, more governors, and reportedly better Bluetooth support (with SR users).
I'll post it for testing when it's ready for those interested...
I don't have any volunteers for testing (yet). . If you want to volunteer, you should be able and willing to clean flash at times 3-4 builds in a day, be able to capture logs and send them. Normal testing would be occasional builds, unless there was a major issue.
Looking for 3 or so testers to help possibly get this into the Slim weekly cycle.
Cheers!

[ROM] [7.1.x] [OMS] [EAS] ibrokemyLINEAGE [20170807]

[ROM] [7.1.x] [OMS] [EAS] ibrokemyLINEAGE [LOS] [20170807]
{
"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"
}
Code:
*** Disclamer
no legal responsibility taken for anything.
use at own risk.
install with full knowledge that this //could// make your phone 100% unusable and out of warrantee.
INTRODUCTION
This is a personal LineageOS build, based upon 14.1. I pull in changes as I see them, and sometimes this breaks things. I will upload builds as I build them, as long as they pass brief personal testing (eg they boot)
Posting this as a seperate thread mainly because it may take a different direction to others, and is not meant to just be a LOS nightly, I will be pulling changes at my discretion, this ROM is being built by me, for me, and I just happen to be sharing it.
Feel free to contribute, recommendations and (new) bug reports are always very welcome.
Click to expand...
Click to collapse
SPECIAL FEATURES
At the moment this may seem a little bland, but the point is not to become a new big rom, but simply to be a LineageOS based rom with the latest little addons, which at the moment include:
@tabp0le Kernel built with rom (Source)
FULL Energy Aware Scheduler support
FULL ROOTLESS Substratum theme engine support with ThemeInterfacer and OMS7
Substratum app pre-included with app store updates
SU_ENABLED by default (builtin root manager from CyanogenMod)
FULLY compatible with both firmwares (MM and N)
Supports F2FS
SELinux ENFORCING
ForceEncrypt DISABLED
Click to expand...
Click to collapse
INSTRUCTIONS
Download the rom, check the hash and flash it and ARM64 7.1 GAPPS (Dynamic/Beansgapps recommended) through TWRP.
For updates, dirty flash of ROM only should do, if you have played around with system apps then perhaps clean the dalvik and cache, just to be safe.
Click to expand...
Click to collapse
BUGS
None known
Click to expand...
Click to collapse
DOWNLOADS
LATEST:
20170807
older versions:
20170502
20173003
20170903
20170131
20170131
20161218
20161215
20161215
Click to expand...
Click to collapse
CHANGELOG
Code:
Rebuild on latest sources
Update OMS
Update themeinterfacer
Fixed sdcard issues
Fixed USB OTG issues
Older changelogs:
Code:
Remove snap camera
Add google camera
UBERTC
Snapdragon LLVM
Update OMS commits
Add substratum as system app
Substratum verification
Rebase of sources upon tabp0le's eas
Fix SD issues
Add back software nav bar
EAS config changes
Improved hardware blobs
Updated power config
Updated hardware overlays
LOS upstream changes
Kernel upstream changes
WLAN wakelocks toggleable
Improved battery usage
Removed some redundant dev settings
Update some drivers/configs for camera and display
Adds Qualcomm Snap Camera
Add OMS7 rootless commits
Fix inclusion of Substratum app (604)
Replace masquerade with ThemeInterfacer (v50)
Compiled with UberTC and Snapdragon LLVM
Tabp0le kernel 1.03
Updated vendor files
Pre odex enabled (faster first boot)
GPS config updated
fix fingerprint sensor
update from upstream
include bluetooth aptx support
new vendor blobs
Rebrand to ibrokemyLINEAGE
Switch from Elite Kernel to Tabp0le Kernel
Better OMS7 integration
FINGERPRINT SENSOR works on both firmwares without need for patches
Substratum app now updates correctly from store
EAS support enabled by default, Kernel and Ramdisk support out of box.
Rebase on CAF sources
Latest patches/fixes
GPS fixes
WiFi stability improvements
WITH_SU set to true
Forceencrypt disabled again
Rebase on LineageOS 14.1
Update kernel
Refactor OMS changes
General cleanups
Latest source from upstream.
OMS7/Masquerade, the backend for the new SUBSTRATUM theme engine. Simply download the substratum app from the play store to use it!
FINALLY a working subwoofer (bottom speaker)
innumerable misc patches
other misc perf changes
Revert breaking audio commits. - https://github.com/ibrokemypie/android_device_htc_pme/commit/928c5e1674571fac980d2e730983c4c59c55f412
Build with Elite Kernel, thanks @buckmarble! - https://github.com/ibrokemypie/android_device_htc_pme/commit/6df6a1b650336bd9f97bed756dc397f1a2862d50
Click to expand...
Click to collapse
Thanks To/Credits
Code:
rc420head, Mahdi786, crpalmer, leedroid, buckmarble and tabp0le
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2016-12-15
Last Updated 2017-03-29
XDA:DevDB Information
ibrokemyLINEAGE 14.1.x, ROM for the HTC 10
Contributors
ibrokemypie, rc420head, Mahdi786, crpalmer, leedroid, buckmarble, tabp0le
Source Code: https://github.com/ibrokemypie/android_device_htc_pme/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Stable
Current Beta Version: ibrokemypie
Created 2016-12-15
Last Updated 2017-08-10

Reserved

I shall give this a try. Thanks @ibrokemypie!

Yup me too, I will also try it. I tested the RR Android N this morning with ZERO issues coming from BadBoys (Sprint HTC 10). I remained on the MM kernel so even TWRP worked with no issues. VERY excited and glad to see N is coming to the HTC 10!

Thanks for contributing! I wish I had the knowledge to contribute .

Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.

This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!

GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
What about the speaker problem?

GROOVYJOSHCLARK said:
This is amazing! EVERYTHING works (except GPS), I did a GPS lock in the Sense OS but still cannot see the satellites but this is OK, I know it will come in time! I am coming from Sprint HTC 10 (BadBoys/official), wiped everything full/clean and installed this with PICO GAPPs, data works, TXT/MMS works, cellular works, no issues with anything except GPS. VERY WELL DONE! Speed test shows BLAZING LTE so I know its seeing the basebands correctly, etc., so all is good from my side, very happy! FINALLY a working N AOSP for my Sprint HTC!!
Click to expand...
Click to collapse
Did you flash the N firmware?

mcwups1 said:
Did you flash the N firmware?
Click to expand...
Click to collapse
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.

Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!

pickandrew said:
Hello, the codename "pme" which version of HTC 10 corresponds?
All these.. perfume_uhl, perfume_whl and perfume_ul?! Thanks!
Click to expand...
Click to collapse
those are the country codes are they not? pme is perfume in general

Stephen said:
Moderator Warning,
Thread cleaned. Flaming users is not acceptable on XDA. If you have an issue with a post, report it and move on.
Click to expand...
Click to collapse
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.

twinnfamous said:
Edit: only quoted you because the post I was replying to got erased.
Thanks for following rules. Sorry if I'm breaking them.
BUT
As far as I'm concerned flaming should be done if source is not public on github and someone hacked your private github account. But sharing is caring
And It benefits us all.
I didn't Flame when I asked in a thread if anybody was working on cm-14.1 and when I started work on it I didn't even write what the commit was that I added but somehow cm-14.1 still came and all the work I done was used. IT REALLY WASNT USED. as there is plenty of github sources to give ideas and plenty of code changes. We as developers need more developers as the code game is big. If someone is contributing to a worthy cause let them. Do any of you developers out there like having sleepless nights trying to figure out code? I don't think so. And me I don't know **** but I can figure it out hahahaha.
This post is just a general post so report me but let people learn dammit. And a guide doesn't teach you how to fix building errors so guides don't help. Going through code of familiar devices does.
Click to expand...
Click to collapse
Hey, I didnt see your post from before, this whole thing, I really didn't mean to offend or steal, I just wanted to make the progress accessible to people who dont have the time or resources to build the code themselves, even if it is mostly just following a guide. Beside from that, the point of open source is for people to take something and make it do what they want, without restrictions, and to be able to give and take if they can. I am not simply taking the work of others and packaging it as my own, I am trying to make contributions, even if I am not a super great programmer like @crpalmer, who is putting together the pieces to make this work for us all. I am not taking the work of others and claiming ti was mine. That was not my intention at all and I am sorry it may have seemed as such.

GROOVYJOSHCLARK said:
Nope, stayed with MM, and I had speaker, no issues with sound, maybe I am lucky, IDK but TWRP worked, and everything I need from my daily driver except GPS.
Click to expand...
Click to collapse
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.

Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs

ibrokemypie said:
Hey, about to start properly looking into GPS as I was able to repro the problem, however GPS satellites are being detected, and certain bits are working, so I feel fixing it should be within my capabilities, however for the moment I am working on including theming through Substratum, with full implementation with the inclusion of Masquerade backend (OMS) which should be build ready in a little while.
Click to expand...
Click to collapse
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10

rav101 said:
Hey @ibrokemypie,
Out of curiosity, are you duel booting Linux, using a VM Linux environment or just generally using Linux as your OS and building Cyanogenmod from there? Also how much space have you got allocated for building Cyanogenmod. I'm trying to figure out if I have the capability to do it on my MacBook Pro if I clear out some space.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.

GROOVYJOSHCLARK said:
That's awesome, I really appreciate it! This is the only thing keeping me from fully committing to this as my daily runner. I use GPS pretty much every day so I need it. I've always ran with AOSP on all of my androids and this is usually an issue across the board in the initial releases so I get it and appreciate your hard work!
sent from my HTC 10
Click to expand...
Click to collapse
hey, just as a test, could you try setting your location to device only, open up google maps and tap the little icon to go to your location? I think it will ask you to allow it access to enable wifi/cell location, so deny that and tap it again, and you should see your location as a grey dot. If this works, can you then tap it once more, and take your device somewhere? There is a chance gps is wokring after all, just not reporting itself as suck to anything...

ibrokemypie said:
Well, initially I tried just building on my macbook, but ran out of space verrrry quickly. Do not recommend even trying unless you have a MINIMUM of 150gb that you can dedicate it, wasted a whole two days with this.
Tried building on a ****ty laptop too, but discovered that you really can't build at all unless you also have at the very least 8gb of ram, so ended up taking the drive out of that and sticking it in my gaming rig with 16gb ram.
Building on an arch linux install, mostly just via ssh with a tmux session to reduce overhead.
Click to expand...
Click to collapse
Yeah I think it's gonna be a no go for me then as my MacBook Pro only has 256gb in total and im currently using 60gb for Windows 10.
If I were to get a build PC together, what components are most required for building Android? After having at least 8gb of ram, is it all processor or a mix of processor and gpu?
Trying to think if I can make an Intel NUC type PC with the built in graphics card or if I need to be getting discrete graphics card as well.
Sent from my HTC 10 using XDA Labs

[ROM][8.1.0][OFFICIAL] LineageOS 15.1 for Find7a/s

Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended TWRP recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on find7
Download link:
LineageOS Downloads
Recommended Google Apps package:
Open GApps (choose the variant you want. Recommended nano package)
Official root addon
LineageOS Extras
Changelog:
Changes for find7
Bug reports:
How to submit a bug report
LineageOS JIRA
Donate to support development:
Donate via PayPal to mikeioannina
Donate via PayPal to LineageOS
XDA:DevDB Information
Official LineageOS 15.1 for Find7a/s, ROM for the Oppo Find 7
Contributors
mikeioannina
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Any version of ColorOS. Unified storage not supported.
Based On: LineageOS
Version Information
Status: Nightly
Created 2018-07-09
Last Updated 2018-11-15

Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...

Am having problem of cold start gps. Takes about 8-10 mins before locking in. However, once lock in,everything work perfectly.
Updated on 18july.now everything is perfect. Even the battery life got better.

thank you???

luckywang95 said:
Just curious. Are there any way for find 7 to install nano gapps? I keep on getting insufficient storage... Sad...
Click to expand...
Click to collapse
You can delete the storage check in the installer script. Did it before and worked fine. I'm gonna try it tonight with this build.
Update: Stucked in bootloop. Gonna try tommorow again.
Update#2: Here is my working solution:
1. Flashing rom
2. Flashing addonsu
3. Flashing openGapps micro

Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!

Zoltan-X said:
Whats the perception about the Lineage<color>Accent.apks ?
They seemed to compromise my device and after removing these system aps
my find7 starts twice as fast as before.
In Settings->Apps they are all active but do nothing and their names are renamed like kakao lavendel kirsche carbon...
I'dont know whats this about,
but I feel Hacked and compromised by these apks!
Please explain what these apks are good for
and why it is stated in Settings->Apps that they do nothing else as being in background active
nor is anything protokollised from their activity!
I did a clean fresh install with these Custom Rom,
wiping all partitions and installing them with TWRP 3.2.2.0
With best regards Zoltan-X
P.S.: Find7 works better without these and no Errors are caused in usage so far!!!
Click to expand...
Click to collapse
Are you serious? These are just simple apks for the styles you can change from display settings.
If you are so curious about "being hacked" look at the source: https://github.com/LineageOS/android_packages_overlays_Lineage

Curios i've had in those app a data collecting folder structure,
like db, files, and more, maybe a rootkit on my device???
I don't know, since i removed those my find7 works again really well,
what it didn't do since a long time in this year....
With best regards
Code looks fine and i'll recheck if the image was compromised or not or how, but later these days.
thank you for the quick hint to those files!
P.S.: I've dirty reflashed the image i used to install lineageOS, after the expected remove, and no these nightly seems not been compromised,
Sorry for the alert,
but in the last days many hacks occured in my private relationships with my dearest, so I was a little curios, but seems now clean on my device!
Thank You verry much,
and Kudos Kudos Kudos to your quick hint reply.

I just installed lineage-15.1-20180806-nightly-find7-signed.zip to replace my stock Oppo Find7 firmware on the weekend and after a few days with it, so far so good! I had to lose the LVM unfortunately, but I'd rather have an up to date OS.
The battery life seems shorter than the stock firmware. I can still get through the day, but down to 40 or 50% or less by 6PM instead of much more with the stock Oppo FW. I haven't tried tweaking any battery life settings yet though.
Two minor things with the install compared to the LineageOS howto - the SD card path was different to what was documented ( /internal_sd not /sdcard) , and I had to install open_gapps-arm-8.1-pico-20180812.zip (pico instead of the documented nano version)... but this was minor stuff and I got where I wanted to go.

Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?

hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.

knusto said:
Video recording is now working on latest AOKP Rom for Find 7. Google is your friend.
Click to expand...
Click to collapse
Wooot ! They have nougat builds for find 7

hexplor said:
Awesome. Thanks for this release. Everything (almost) works great. Feels like a new phone. Only video recording does not work. Any ideas ?
Click to expand...
Click to collapse
It will be fixed in next build.

mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Thank you so much. Can't wait

hexplor said:
Wooot ! They have nougat builds for find 7
Click to expand...
Click to collapse
AOKP is now on Oreo for Find 7

mikeioannina said:
It will be fixed in next build.
Click to expand...
Click to collapse
Got the latest build. All fine Thanks

Allthough its not supported i've got unified working. not reliable tho. the only way i got it working when flashing los and direct rebooting into recovery again and then flashing the cm-13.0-find7-unified-storage-patch.zip from the according thread. cuz the original link is dead incl mirror i got my copy uploaded to gdrive here. https://drive.google.com/file/d/1sZ72qUD5P7qL4tsIF3MB-cQk9x9pamRR/view?usp=sharing
only drawback being you cant reboot anymore cuz that will somehow give you the your-sdcard-is-****ed message. havent found a reasonable routine so i guess you'll have to try your luck yourself and maybe give feedback?

Hi, could you disable CABC(Content Adaptive Brightness Control) or provide a way to disable it? The hardware of Find 7 use it and it really makes some troubles, brightness, color. Really thanks if you have that time

I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?

Manas1796 said:
I read that the problem of heavy games crashing on Bacon (Oneplus One) was resolved recently with this commit https://review.lineageos.org/#/c/LineageOS/android_device_oneplus_bacon/+/218799/
I have the same problem with the Oppo Find 7/s (i.e. heavy games are crashing). As this device has the same processor and RAM as that of the Bacon, is it possible to get the same fix for Find 7 as well?
Click to expand...
Click to collapse
That commit has already been applied for Find7 - https://github.com/LineageOS/androi...mmit/80e1e7e5ffca2c69730eecc8c498423c2ea48463

[9][OFFICIAL][WEEKLY] CarbonROM | cr-7.0 [maple]

Downloading,I will feedback

Sorry for my bad english
But I found some problems:
1. NFC is not working, I cant open NFC
2.Fingerprint sensor is insensitive,
when I try to create my fingerprint,the system says "It has stains on sensor." but I have cleaned already
Sorry it seems that is my problem , please ignore it.
3.Style Cover Stand SCSG10 is working inappropriate (same problem on early oreo builds)
when i covered up, xzp couldn't sleep
4.Mobile data cant work
others seems work perfectly
My firmware is 47.2.A.10.107
---
Edit:
I changed firmware to 47.1.A.16.20, NFC can work now
SCSG10 still works inappropriately, and Mobile data doesn't work. (only calls / sms)
But now the system says "your vendor doesn't match to your system".

1,NFC is dead
2,G8142 card 2 can't be recognized
3,Network not available
（basic on .107）
other things working Great！！！
how about make Camera Switch available？

I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Edit: found the cause for the mobile data, must've removed that by accident during a cleanup. A working build will be released later today
EDIT2: Build is running right now and will appear on the download page once done.

Can anyone confirm camera2api and gcam hdr+ support?

Thanks for fixing Mobile data and now it works.
NFC is also working, but need reboot after gapps setup wizard or first boot, I dont know if this is a problem.
(Just clean flash 47.2.A.10.107, I dont know why i cant open nfc in my first try. I clean flashed before...)
Incrovantilist said:
Can anyone confirm camera2api and gcam hdr+ support?
Click to expand...
Click to collapse
No, this rom blobs are based stock, so no level3 support.

Just flashed the rom and its smooth and awesome. So far everything working except dt2w.
For some reason with Magisk 19.3, ctsProfile is returning false. It didnt fail in any of the other SODPs or the latest stock rom. Anyone facing same issue?

Myself5 said:
I'm coming from a fully clean install of 47.2.A.10.107.
NFC is working fine, however I can confirm the mobile data issue, which is very weird as this was working flawless before. I'm looking into it.
Click to expand...
Click to collapse
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Myself5 said:
As for DualSIM support: I released a build in the 6.1 thread a few days ago, which no DualSIM user provided any feedback to, so I went ahead and released these builds with the Single SIM device in mind. Unless I find a way to unify the devices (like I did in Oreo, which apparently doesn't work anymore because thats what this build uses) I'm not going to support the DualSIM variants.
If anyone is willing to help me debugging this issue on the DualSIM variants by flashing testbuilds and getting logs etc, hit me up.
Click to expand...
Click to collapse
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.

LSS4181 said:
It seems Carbon's kernel tree is almost identical to cryptomilk's.
I recall I can't turn on NFC when using cryptomilk's kernel tree to build my own ROMs, either. However, NFC works fine with Sjll's kernel tree, despite being a few days older.
Not sure about the exact cause of this, but it's possible that something in 47.2.A.10.107 might be needed. My phone is currently still based on 47.2.A.10.80 as the .107 build for my region is not out. If the older stock base is indeed the cause of the issue, I'll consider flashing a current stock ROM of different region.
Click to expand...
Click to collapse
Given it works on both my phones that were on .107 before and that the blobs are from .107, this could be the cause. If you flash the latest stock ROM make sure to fully boot into it at least once because the stock ROM sometimes also upgrades the NFC Firmware on the chip itself.
P.S. The kernel is the same as cryptomilks.
LSS4181 said:
Does SD card functionality still work on G8142? I haven't tested the new CarbonROM build, but personally I had positive results with SD card on other ROMs/kernels that were targeting G8141.
Click to expand...
Click to collapse
Oh cmon man you literally quoted a message of me saying that I don't have the Dual SIM variant nor any testers for it (yet). I have quite a few ideas on how I could fix it, but without any testers I'm just not gonna touch it at all.

I have G8142 and I can say, "Yes, SD card still works on G8142."
But I dont have 2nd sim card so i cant test if dualsim works

.107 clean installation, there were also problems with NFC, after rebooting it was fixed.

The Smart Cover function does not work, the screen continues to light after closing the cover, or the action of the magnetic cover (by the Hall sensor), I do not know how it should, but it does not work ..

So far stable enough to be daily driver except issues with magisk. Magisk keeps getting uninstalled on its own and have to be reinstalled in twrp every now and then. And after it gets installed, the rom stutters and doesn't open any apps or the settings and have to be restarted a few times for it to go back to normal.
Also a feature to modify charging led settings would be awesome. (I tried to find and modify it in root but couldn't find the charging led settings in /sys/class/leds)
Camera is frickin awesome. It's sooo much better than stock even without lvl3 camera2api. For anyone trying to find a decent camera app, try using opencamera with camera2api enabled in settings. Except for hdr(doesn't work, will force close), it's able to take really good images. If only somehow able to shoot 960fps slomo .

Magisk 19.3 - there were no problems with self-removal, there is a delay when starting up applications with a white screen after a reboot, it holds the battery well 2% per night.

I spent some time working with @haiha2001 on the XZ1 Dual today. Along the road we came across a few things but it's not working yet. HOWEVER, the XZ1 seems to have a different/more advanced issue than the XZ Premium. Whereas the XZ Premium has SIM1 working, the XZ1 doesn't have any SIM working at all.
That brings me to the following:
There was a fairly obvious flaw (thank Sony for that for not having unity of system property locations across Single/Dual SIM) which could explain why only one SIM is working on the XZ Premium. I've fixed it in the linked boot.img. If someone with two SIM Cards and the Dual SIM variant could try and let me know how it's doing on maple_dsds I'd be very happy.
https://dl.myself5.de/maple/.fwafwafwafo/boot.img
flash it via fastboot with
Code:
fastboot flash boot boot.img
on top of the latest weekly.

Just flashed your boot.IMG
I'll put in the wife's sim and see

Myself5 said:
I spent some time working with @haiha2001 on the XZ1 Dual today.
Click to expand...
Click to collapse
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.

Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
Because I see the XZ1 seems to be less supported by programmers for this device while the XZ Premium has quite a lot, while I know that the XZ Premium is not too different from the off-screen XZ1, so I'm willing to support the programmers to check the rom or mod version for XZ1, if they have an idea I will help my best ?
Sent from my Sony G8342 using XDA Labs

beammer335d said:
Just flashed your boot.IMG
I'll put in the wife's sim and see
Click to expand...
Click to collapse
Did she voluntarily gave it to you yet or do we need to send armed troops to make her ? First screenshot looks promising already.
also, in case you're rooted, please get me the output of the following:
Code:
adb shell
then enter
Code:
su
(Accept Magisk request on the phone)
and then run
Code:
cat /cache/modem/modem_switcher_status
cat /cache/modem/modem_switcher_report
And send me the output.
Alternatively you can run it via terminal emulator starting at the "su" part.
Beetle84 said:
Off-topic but @haiha2001 is a great guy! He also tests aroma zip files and other zips for me, to do with another rom.
Click to expand...
Click to collapse
+1

[ROM][9.0][Oct] Android Ice Cold Project 14.0 Unofficial [15.10.19]

Nothing would be possible without the work of @MrColdbird and the help of @Franssen
{
"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"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP and we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@Maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Firmware Version 9.9.3
Download link: https://drive.google.com/open?id=142PC3GNCnfrp4h5RGGSn-qV9aSZFE5M0
Latest Stable Release Version 14.0
Download link: https://mega.nz/#!C1tDyIBB!-2cpzfdKYDA05U6-SfQHqXpnzGgyHqqsbtopZjQntTY
Mirror: https://drive.google.com/open?id=1BJ1QtmPNF8Rqx80xsw_IUfKjHq0yOy0_
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet released for Pie, however you can try to use edxposed .
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Pie. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the FIRMWARE then ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work) and Magisk (root).
6. Reboot and set up your device,
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 17.2 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
Kernel source:
https://github.com/rr-mario/msm-4.4./stable
Device tree source:
https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
Vendor source:
https://github.com/Black-Seraph/vendor_xiaomi_nitrogen/pie
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds[/B]
Contributors:
@MrColdbird @Franssen @Mario_R and my testers (Gryphon_D)
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP, ROM for the Xiaomi Mi Max 3
Contributors
Skyllery, MrColdbird, Franssen
Source Code: https://github.com/Skyllery/device_xiaomi_nitrogen/tree/aicp-pie
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.9.3
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 14.0
Stable Release Date: 2019-09-21
Created 2019-09-21
Last Updated 2019-10-17

Finally, AICP is out.

Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect

rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Currently best ROM? Please explain why..

GEoMaNTiK said:
Currently best ROM? Please explain why..
Click to expand...
Click to collapse
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.

rudiratlos57 said:
Great job, currently best Rom, it would be nice if you could change the icons
for Accu, Wlan, Mobile Data and Clock and Provider Color, then the Rom would
be absolutely perfect
Click to expand...
Click to collapse
Sorry but didn't understand what you mean. BTW i'm mostly a builder and modding AICP source code is far from my knowledge.
Regards

eloyho said:
The other roms Like Aoisp, havoc, Fest, lineage and the rest of it, always after a couple hours of usage, always start lagging to open apps and other. This one i have 24 Hrs, and still strong whit no problem. Don't ask me why but, for me right now, its perfect.
Click to expand...
Click to collapse
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!

GEoMaNTiK said:
I'm using Revenge and it's as snappy as I've found... I've also underclocked my CPU and its quick!!!
Click to expand...
Click to collapse
Remember we use the same device tree to build everything, GismoBe, Me, etc. It's mostly rom reputation and usage. There's no best or worst, we build as anyone can find what works for him.
Regards

@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:

shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards

Skyllery said:
It's because Revenge OS is not build by me ^^ It's Franssen (GismoBe on Telegram) but he's not much on XDA these days. I already tell him why there's not all their ROMS (AOSMP, Revange, etc) but he don't have much time.
Not tried it already .. open beta seems to be on 27th. I think i'll wait to xiaomi.eu or try to go on 10 gsi to see how it is. (Didn't look at this for the moment)
Regards
Click to expand...
Click to collapse
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta

shingers5 said:
i am trying it now guess xiaomi.eu will translate.and release soon. i like it and.the changes are nice. not bad for forst beta
Click to expand...
Click to collapse
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Sim activation by sending a sms to china (paid)
Region limitation for community access and theme options..
Poor theming compared to custom ROMs.
But it looks promising will give it a chance.
Regards
Sent from my MI MAX 3 using XDA Labs

shingers5 said:
@Skyllery your Revenge OS is very good but i dont see a thread for it. also see mi max 3 Miui 11 beta leak is out so gonna try that. its on Telegram :good:
Click to expand...
Click to collapse
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.

Skyllery said:
On my side still on aex for the moment, in fact my preferred ROM builded by me. (Specially for battery backup)
Will try the beta tomorrow look promising .. but miui have some little things which kept me away to use it more than two days.
Click to expand...
Click to collapse
Tries AEX a few weeks back, it cannot run my banking apps, even with Magisk Hide. Malaysia Maybank and Singapore DBS, no choice but to give it up. Any changes since then? Any idea how to fix it? Thanks.

Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.

Wmateria said:
Where to find the beta leak, what is the telegram page? Oh wow XDA posted them all as twrp recovery files.
Click to expand...
Click to collapse
its a proper full flashable zip. its the Nitrogen Cloud telegrsm group. its Mi Max 3 specific.
https://t.me/NitrogenCloud/1879

GEoMaNTiK said:
Awesome ROM.. have been using for a little under 24hrs.
I had a problem with Revenge, out of the blue my Mi Max 3 went into a bootloop.. did nothing different and no idea why...
One thing I've noticed since going to AICP,, my 5GHz wirelsss network keeps coming up as Disabled, after it briefly connects. The 2.4GHz network is working without problems and stays connected.
Anyone else having this problem or can help with what it might be?
All other custom ROMs haven't had an issue with 5GHz.
Click to expand...
Click to collapse
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs

Skyllery said:
Yes got the same here
Regards
Sent from my MI MAX 3 using XDA Labs
Click to expand...
Click to collapse
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
Click to expand...
Click to collapse
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.

GEoMaNTiK said:
Okay I just tried something and so far it's working...
I deleted the 5GHz saved network from my phone, rebooted my wifi router, entered 5GHz network details again and no probs after about 30mins so far.
Will report back if it drops out again.
---------- Post added at 08:00 AM ---------- Previous post was at 07:41 AM ----------
Ohh damn, typed too soon ... The 5GHz connection just dropped out again and can't get it back on.
2.4GHz working without issue still.
Click to expand...
Click to collapse
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Sent from my MI MAX 3 using XDA Labs

Skyllery said:
You use correct firmware provided in op or some modded one ?
It didn't happen to me since a while. It's on every ROM but not so often. Or try to flash modem fix.ysl.zip on channel or group you'll find it. To restart modem.
Regards
Click to expand...
Click to collapse
Have just moved to the latest Xtended ROM and have no issues with 5GHz wifi, same as the previous Revenge ROM with no issues.
Very strange.

Develop Bugs

welcome