{
"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"
}
Hi everyone, i am currently building a weekly version (or monthly, depending on CyanogenMod fixes and patches) of CyanogenMod 12.1 for a while now, i thought i could share it with you, because falcon cm-12.1 branch is no longer supported by CyanogenMod.
I made some little modifications to the framework, the device tree and the kernel, which you cand find in the source section.
For those who don't read at those stuffs, the changes are:
- Restored Ambient Display (and tuned a bit) and MotoDoze (wake gestures etc.), since the black screens have been fixed a while ago, this feature is now working correctly here on CM12.1
- Status bar date customizations
- Ability to hide SU icon on status bar (developer settings)
- KCAL support (adjust color contrast and saturation with this app: http://downloads.codefi.re/savoca/kcal)
- Proximity check on wake (disabled by default, you can enable it in Settings/Display), prevents accidental wake ups
- Dexpreopted
- Cyanogenmod's Screencast app from cm-13.0 branch
- Kernel security fixes from cm-13.0 branch
- PowerHAL updates from cm-13.0 branch
- General device tree updates from cm-13.0 branch
- LuK1337 gently found a fix for the GPS bug that forced you to erase modemst1 and modemst2 to make GPS work, so you won't need to do that anymore
- Updated all the libraries and apk/jar's from latest 5.1 build
- Updated Adreno libraries to 5.1 (Motorola is still using 5.0 ones on their 5.1 build)
- CyanogenMod fixed the soft reboots due to strictmode violations (https://github.com/CyanogenMod/andr...mmit/1e60f9b9ae10d46d028c19c90cf0f52d40ca620a), so this fix is of course included here, but is not included in the latest public snapshot for falcon on the CyanogenMod site, so this can be a reason of switching from that snapshot to this build.
- CM12.1 branch is pretty stable right now, so you shouldn't have any major problem
DOWNLOAD
CHANGELOG [06/02/2016]
CHANGELOG [24/02/2016]
CHANGELOG [09/03/2016]
CHANGELOG [16/03/2016]
CHANGELOG [25/03/2016]
CHANGELOG [05/04/2016]
CHANGELOG [12/05/2016]
CHANGELOG [15/06/2016]
CHANGELOG [09/07/2016]
CHANGELOG [10/08/2016]
CHANGELOG [14/10/2016]
READ POST #2 IF YOU HAVE ANY TROUBLE WITH THE ROM, IF IT'S A COMMON PROBLEM, IT WILL BE THERE
CUSTOM KERNELS AND/OR XPOSED OR ANY OTHER MOD ARE HIGHLY UNSUPPORTED
Credits:
- LuK1337
- luca020400
- Gabriele M
- hurtsky
- savoca
- matmutant (for the logo xD)
- Motorola and all the CyanogenMod contributors
XDA:DevDB Information
CyanogenMod, ROM for the Moto G
Contributors
fonz93
Source Code: https://github.com/MotoG-2013
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 41.18+ Bootloader version
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2016-10-14
Created 2016-01-29
Last Updated 2018-02-08
NOTE:
- Reported bugs without any useful logcat and/or Xposed installed will just be trashed
- If you flash any CM12.1 custom kernel, you must flash this package: https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
in order to downgrade your camera blobs from 5.1 to 5.0, if you don't this, the camera won't work ***
-- If, for any reason, you decide to go back to the kernel included in this ROM, you have to install again 5.1 camera blobs, the easiest way to do that is flashing the ROM .zip.
*** I updated camera blobs from the latest Motorola factory image, a kernel update was needed in order to make camera work after updating the blobs (that's not an hack, is a regular update from Motorola), but CyanogenMod dropped CM12.1 nightlies before doing this, so any CM12.1 based kernel doesn't contain that kernel update, that's why you need to downgrade camera blobs to 5.0.
I have to remind you that installing a custom kernel will break any future support by me
great job! looked for something like this before moving from my snapshot 12.1 ROM which was the first custom ROM I put on this phone. Running identity crisis nowas I need to have a stable NO Root ROM for my corporate email to work but Ill be downloading this rom for sure.
slds,
Very nice! Thanks! I missed long time is Ambient Display, so It´s back!!!
The only thing I would like to have in this rom is an option to remove the #RootSymbol in the status bar
lfuentes said:
Very nice! Thanks! I missed long time is Ambient Display, so It´s back!!!
The only thing I would like to have in this rom is an option to remove the #RootSymbol in the status bar
Click to expand...
Click to collapse
A new build with the feature you've requested is up, you can find the switch in developer settings
(Note: the build informations shows 28-01 and not 30-01, that's because i didn't make a full clean build, i just did a build on top of the old one, there was no reason to make a new clean one, because the "Hide SU icon" feature is the only thing that changed since 28-01 in the source code, so don't worry)
fonz93 said:
A new build with the feature you've requested is up, you can find the switch in developer settings
(Note: the build informations shows 28-01 and not 30-01, that's because i didn't make a full clean build, i just did a build on top of the old one, there was no reason to make a new clean one, because the "Hide SU icon" feature is the only thing that changed since 28-01 in the source code, so don't worry)
Click to expand...
Click to collapse
Great! I´ve noticed that "inconsistency" in dates, and has no importance
I've uploaded a new clean build, just to be sure it doesn't bother anyone (no difference from the previous one, it's just a clean build)
excellent ROM. superb thanks for cm 12.1 continue.
pls keep updating .
only one bug though I don't use that is show weather toggle not working and weather not showing in notification drawer.
thanks
drgopi1234 said:
only one bug though I don't use that is show weather toggle not working and weather not showing in notification drawer.
Click to expand...
Click to collapse
It works here, i think the problem it's the location, somehow cLock doesn't take it "instantly", try to add the widget, update it and delete it, now it should work (that's what i did right now)
OK now it works thanks.
Nice rom man... keep up the good work.
There's a little problem here though, I have tried some CM 12.1 kernels(HurtSky and Optimus) and they seem to break camera. Is it a bug or I should be using CM 13 custom kernels instead cause I really need some features outta them ?
hamzaalijoiyah said:
Nice rom man... keep up the good work.
There's a little problem here though, I have tried some CM 12.1 kernels(HurtSky and Optimus) and they seem to break camera. Is it a bug or I should be using CM 13 custom kernels instead cause I really need some features outta them ?
Click to expand...
Click to collapse
After updating camera blobs to 5.1, the kernel needs an extra patch too: https://github.com/fonz93/android_k...mmit/17be9afb1bd6fa1737e8365a9f959c9ad5a32e74, that patch is probably missing on every kernel made for the older versions of CM12.1 (or ROMs based on it), this because they use 5.0 camera blobs and they didn't need to merge that kernel patch, this patch is of course included on CM13, but you can't use CM13 kernels, because they use a different ramdisk and selinux policies.
The easiest way to workaround this, it's to flash 5.0 camera blobs and your preferred kernel, i have to remind you that if you flash a custom kernel, i can't give you support in case some bugs shows up, because i will not be able to reproduce or fix them.
Now, you can flash this file, to get 5.0 "camera.msm8226.so": https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
It should fix your problem, let me know if it works. In case it doesn't, i will provide you a different package with all the 5.0 camera libraries (it will get more time).
fonz93 said:
After updating camera blobs to 5.1, the kernel needs an extra patch too: https://github.com/fonz93/android_k...mmit/17be9afb1bd6fa1737e8365a9f959c9ad5a32e74, that patch is probably missing on every kernel made for the older versions of CM12.1 (or ROMs based on it), this because they use 5.0 camera blobs and they didn't need to merge that kernel patch, this patch is of course included on CM13, but you can't use CM13 kernels, because they use a different ramdisk and selinux policies.
The easiest way to workaround this, it's to flash 5.0 camera blobs and your preferred kernel, i have to remind you that if you flash a custom kernel, i can't give you support in case some bugs shows up, because i will not be able to reproduce or fix them.
Now, you can flash this file, to get 5.0 "camera.msm8226.so": https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
It should fix your problem, let me know if it works. In case it doesn't, i will provide you a different package with all the 5.0 camera libraries (it will get more time).
Click to expand...
Click to collapse
Thanks man for your time and help. But installing this didn't work either. But thats not a big issue I will stick to the stock kernel.
BTW any chance you can odd those 5.1 blobs to Hurtsky or Optimus kernel. Just for curiosity !!!
hamzaalijoiyah said:
Thanks man for your time and help. But installing this didn't work either
Click to expand...
Click to collapse
Try again with this package (same folder link):
https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
hamzaalijoiyah said:
BTW any chance you can odd those 5.1 blobs to Hurtsky or Optimus kernel. Just for curiosity !!!
Click to expand...
Click to collapse
In the kernel part they can only add the patch i mentioned before, but then they will break compatibility for all the other 5.1.x ROMs on xda because those ROMs use old blobs, on the other hand adding 5.1 blobs in the kernel flashable .zip is possible, but can't be done, because of this:
- User "A" installs custom kernel that applied the patch and includes 5.1.x blobs in its package, it will work with all 5.1.x ROMs
- User "A" doesn't want to use that kernel anymore, he installs a different custom kernel, that one doesn't include the kernel patch, but you have 5.1.x blobs in your ROM that have been extracted with the previous kernel installation.
- The camera of user "A" is now broken, if he is not skilled enough, he won't know why and he will probably think his installation is broken, then people will start suggesting him a full wipe and a fresh install without a legit reason.
This could be done only 2 or 3 months ago, when the Lollipop developing was still active and all the developers could update their ROMs/Kernels, but with the current situation, it can't be done.
hamzaalijoiyah said:
Is it a bug or I should be using CM 13 custom kernels instead cause I really need some features outta them ?
Click to expand...
Click to collapse
Can you mention the features you need from custom kernels? if they're not too much invasive i will consider a kernel update
fonz93 said:
Can you mention the features you need from custom kernels? if they're not too much invasive i will consider a kernel update
Click to expand...
Click to collapse
Only the ability to change Screen Saturation and Contrast. I just like them a bit higher than normal. That's all. None of those funky advanced features.
hamzaalijoiyah said:
Only the ability to change Screen Saturation and Contrast. I just like them a bit higher than normal. That's all. None of those funky advanced features.
Click to expand...
Click to collapse
Do you mean the KCAL?
fonz93 said:
Try again with this package (same folder link):
https://drive.google.com/folderview?id=0B-xonQbKq2U2NEtIbXZaaEdCemM&usp=sharing
Click to expand...
Click to collapse
Sorry didn't tried these before, they work with CM 12.1 custom kernels.
But anyways having those options baked in the rom (I mean kernel ofcourse) would be very nice. And thanks a lot man for your help.:good:
hamzaalijoiyah said:
Only the ability to change Screen Saturation and Contrast. I just like them a bit higher than normal. That's all. None of those funky advanced features.
Click to expand...
Click to collapse
i've made a new kernel build with KCAL support, flash this in recovery:
https://drive.google.com/folderview?id=0B-xonQbKq2U2bW5nR3FXa1o1TDA&usp=sharing
Now, because you probably have 5.0 camera blobs in your ROM, to restore 5.1 ones, flash the whole ROM .zip, then you can flash the kernel update
fonz93 said:
i've made a new kernel build with KCAL support, flash this in recovery:
https://drive.google.com/folderview?id=0B-xonQbKq2U2bW5nR3FXa1o1TDA&usp=sharing
Now, because you probably have 5.0 camera blobs in your ROM, to restore 5.1 ones, flash the whole ROM .zip, then you can flash the kernel update
Click to expand...
Click to collapse
I really am very thankful to you for this... And sorry too of course for bothering you....
Its working like charm...
Original cyanogen build has a bug...after a few hours of usage the navigation bar and the status bar get distorted! This happens only in landscape mode! Can anyone pls confirm if the same problem is there or nt in this version? I want to switch if it's not because it's very much annoying as only a reboot solves that!! Thanks.
Related
{
"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"
}
LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave!
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device.
We ask that you do your part to know your device and know how to recover from problems before you flash!
Installation instructions:
Make sure you are on latest TWRP
Download ROM
Full Wipe (only when coming from other ROM)
Flash ROM and Gapps
I am in no way responsible for anything that may happen to your phone! Flashing this is at your own risk.
Offcourse all credits for this ROM go to Team LiquidSmooth and Cyanogenmod for making this possible.
Features:
There's no official changelog. Check Liquidsmooth Gerrit for merged changes.
GERRIT
SCREENSHOTS
XDA:DevDB Information
LiquidSmooth 4.1 Lollipop Unofficial [2.15], ROM for the HTC One S
Contributors
mikronac.ns, Rapier
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Created 2015-03-29
Last Updated 2015-06-13
One more. Old thread is discontinue and maybe it needs to be locked.
2.16 builds will not be supported this time. If you want Ls on your phone, downgrade to 2.15.
Something seems to be wrong with this build. I have no sound at all. Means no ringtones, no notifications, no music (using player pro, I get something like "audio format not supported by player pro").
derkleinebroicher said:
Something seems to be wrong with this build. I have no sound at all. Means no ringtones, no notifications, no music (using player pro, I get something like "audio format not supported by player pro").
Click to expand...
Click to collapse
Yes, @Rapier told me that. But, I cant do anything here. Wait until LS team fix it.
OK so for now there's no sound due to some commits. @mikronac.ns is trying to get a new build working, meanwhile I've made a patch for this build to have sound working and enjoy LS. You just have to flash it in recovery after you've flashed the ROM. (let me know if it's not working, for me it worked)
Instructions:
1. Download V2 Patch HERE
2. flash in recovery AFTER you've flashed the ROM
3. flash additional files you want (GAPPS, custom kernels, ...)
4. reboot
Now that we have the ROM working there are a couple of things (I've also added some screenshots to the OP)
- [NEW]Expanded Volume Panel
- [NEW]main Settings layout changed to include On/Off switches for Wi-Fi, BT...
- the included Layers Manager app is still the old version (3.0). To install the latest version from Play Store (3.4) you must first delete (using a root file explorer) the Layers folder/app from /system/app and reboot. (screenshot in OP is for Layers Manager 3.4)
- the build has "enforcing" selinux permissions. It is recommended to use SElinux Mode Changer to set it to "permissive". This is required for example if you intend to use Viper4Android or other apps that have issues with enforcing
- even if not officially recommended, custom kernels works, I've tested latest IceCode and I had no issues (still this is subjective and it is very much depending on each user's phone usage)
- Xposed works as well, thanks to @Loreane Van Daal, I've found that Xposed module that solves one of the memory leaks in android 5.0.x and there is an improvement. Anyone can install Xposed from official thread HERE, then install the module from Xposed repository (just search for "lollipop memory leak")
NOTE: Theme used in screenshots is Gryffindor Layers theme
Happy flashing...
This is new build. It is not tested, I don't know if it solves problem with sound.
https://www.androidfilehost.com/?fid=95916177934548094
mikronac.ns said:
This is new build. It is not tested, I don't know if it solves problem with sound.
https://www.androidfilehost.com/?fid=95916177934548094
Click to expand...
Click to collapse
ok will test this out guys
mikronac.ns said:
This is new build. It is not tested, I don't know if it solves problem with sound.
https://www.androidfilehost.com/?fid=95916177934548094
Click to expand...
Click to collapse
Unfortunately it is still not having sound...
https://www.androidfilehost.com/?fid=95916177934548412 - new build
mikronac.ns said:
https://www.androidfilehost.com/?fid=95916177934548412 - new build
Click to expand...
Click to collapse
Still no sound but the patch worked so I'm using it. Hope the issue will be somehow solved by LS cause Sean Hoyt replied to me on G+ page and he said he has no clue what happened. Maybe at next build, if it's still without sound I'll pull a logcat and we could find something there
Rapier said:
Still no sound but the patch worked so I'm using it. Hope the issue will be somehow solved by LS cause Sean Hoyt replied to me on G+ page and he said he has no clue what happened. Maybe at next build, if it's still without sound I'll pull a logcat and we could find something there
Click to expand...
Click to collapse
So you use the Patch from first site ( https://www.androidfilehost.com/?fid=95916177934548040 ) of this thread with the current rom ( https://www.androidfilehost.com/?fid=95916177934548412 )???
And it worked. Because he (the patch guy, sorry I am on mobile actually) says that we should use this patch with the rom Version from 29.03.2015.
Greetings by Idijt
I_did_it_just_tmrrow said:
So you use the Patch from first site ( https://www.androidfilehost.com/?fid=95916177934548040 ) of this thread with the current rom ( https://www.androidfilehost.com/?fid=95916177934548412 )???
And it worked. Because he (the patch guy, sorry I am on mobile actually) says that we should use this patch with the rom Version from 29.03.2015.
Greetings by Idijt
Click to expand...
Click to collapse
I am the "patch guy" and the patch is working for this last version too. In fact it'll work on all builds untill there will be a major change in the libs.
Anyway, I'll test each build and I'll specify if the patch works or not after each one.
Sent from nowhere over the air...
Build bot starts new build every day at 10am. About 1pm am checking afh to see if it is uploaded. If yes, that's great, if not - wait next day.
Okay, I just flashed yesterday but I need some days to know definitely that there are no mobile connection problems. As you can see here I hab no rom until now that had no problems: http://forum.xda-developers.com/showthread.php?p=59659091
I hope your rom give me no hangoff or connection (mobile phone call connection) problems and they should have, I hope that you guys know how to read my catlog's. I guess you two guys are fit! Thumb up.
Greetings by Idijt
new build is up...
still no sound without the patch.
drawer settings don't work,just like slim.(launch count).
gone back too cm12.
Hm, download statistic for LS builds is pain for my eyes.
mikronac.ns said:
Hm, download statistic for LS builds is pain for my eyes.
Click to expand...
Click to collapse
You mean there are too few downloads? Well this could be due to the "no sound" issue or because many users are still more comfortable with CM based ROMs...RRO/Layers might have scared some people also. Still LS is one of the best LP ROMs and has options that work without adding Xposed (like Ambient Display for ex). I'm downloading now today's build. Have you tried the 5.1 branch of LS? Is it buildable?
EDIT: Last build as of 02.03.2015 still has no sound. The good news is that I've looked more inside the patch I've made and managed to cut it's size from 85 MB to only 10 MB. So for now you can use the new LiquidSoundPatcher_V2 for getting sound on LS. I'll delete the previous patch and put a link to this post instead
Rapier said:
You mean there are too few downloads? Well this could be due to the "no sound" issue or because many users are still more comfortable with CM based ROMs...RRO/Layers might have scared some people also. Still LS is one of the best LP ROMs and has options that work without adding Xposed (like Ambient Display for ex). I'm downloading now today's build. Have you tried the 5.1 branch of LS? Is it buildable?
EDIT: Last build as of 02.03.2015 still has no sound. The good news is that I've looked more inside the patch I've made and managed to cut it's size from 85 MB to only 10 MB. So for now you can use the new LiquidSoundPatcher_V2 for getting sound on LS. I'll delete the previous patch and put a link to this post instead
Click to expand...
Click to collapse
Yes, every build has <10 downloads. I will configure jenkins to count commits or something like that. Maybe I should build it every 2 or 3 days.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We’re really excited to announce that we are releasing our Nougat flavour of Paranoid Android. We have a lot in store - with a mix of both features & improvements.
First & foremost, we have moved our code base to be fully CAF based. This brings many improvements to your device. The key improvement here is that Qualcomm hardware is better tuned on the CAF base and with our additional optimizations we can provide a smooth and fluid user experience that will let you enjoy using your device without any lags.
On first launch you’ll notice a clean setup with a beautiful wallpaper from Hampus Olsson who’s teamed up with us again and created several beautiful pieces of artwork. For those of you who don’t know, Hampus is a multi-disciplinary artist whose work stands itself and we’re glad to have him onboard. We have also added several new features and made improvements to the UI of the system that we believe would enhance the overall experience.
Pie
We’ve been working hard on redesigning this key feature of our portfolio and we’re really happy with how it has turned out. The whole design has been reworked and it fits in well with the overall feel of Google’s Material Design. This gives you the opportunity to use more gesture based control for navigating, rather than using the standard Navigation Bar at the bottom of your screen. Expect improvements and additions in the future.
Color Engine
We’re proud to announce our newest feature - Color Engine. Color Engine allows you to seamlessly change the colors of your device to be in Light, Dark (Pixel) and Black modes with a variety of accent colors to choose from. This makes changing the theme of your device really quick without having to install any extra packages on your device.
Pocket Lock
This feature prevents any form of accidental input when your device is in your pocket by disabling input sources. You can simply release Pocket Lock by long pressing the power button as highlighted by the minimal UI incase of any sort of obstruction or dust on the sensors.
Accidental Touch
Accidental Touch is a feature useful for many, especially the gamers out there. It prevents any sort of accidental touch on hardware buttons while the touchscreen is in use. This means you won’t experience any unexpected behaviour while playing games, web browsing or even when attempting to reach your finger out to the edge of that humongous display.
Major Feature
- Reworked Pie
- Color engine
- Pocket lock
- Immersive mode
- Buttons customization (including navigation bar)
- On the spot controls (OTS)
Minor Features
- SafetyNet Compatibility
- Battery/Notification LED control
- Recent tasks locking
- Battery icon customization
- Google now page in default launcher
- Accidental touch
- Three finger swipe Screenshot
- Substratum (OMS) support (Color engine will be deactivated if you use Substratum)
- Quick pulldown
- Various performance and battery improvements
- Display Burn-in protection (for OLED screens)
- More to explore
Download
AOSPA OTUS Build
instructions And Requirements
Reboot into TWRP
Wipe system,data,cache and art/dalvik cache
Flash ROM and Gapps
Flash latest SuperSu if you want root
Reboot to system
Known Bugs
RIL (Now Resolved on letest update)
Credits
AOSPA TEAM
Open Community
Cheers And #StayParanoid
XDA:DevDB Information
AOSPA for OTUS, ROM for the Moto E 2015
Contributors
Kuck7610
Source Code: https://github.com/AOSPA
Device Tree: https://github.com/Kukun7610/device_motorola_otus
Kernel : https://github.com/Kukun7610/android_kernel_motorola_msm8610
PaVendor: https://github.com/Kukun7610/android_vendor_pa
Motorola Vendor: https://github.com/TheMuppets/proprietary_vendor_motorola
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlock Bootloader
Based On: AOSP
Version Information
Status: Testing
Current Beta Version: 7.3.0-Dev
Beta Release Date: 2017-10-26
Created 2017-10-26
Last Updated 2017-10-28
Frequently asked questions (FAQ)
F.A.Q :
Q - Why you mustn't quote the hole post ?
A - As you are killing us dude !
Q - Why mustn't I ask for ETA ?
A - Simply , we are students and colleges so we are busy with our studying and other life problems !
Q - Why mustn't you Spam ?
A -As Organization Is the key to achieve the impossible !
Q - I have faced some issues, which is not mentioned in the 'Not Working' list........?
A - For bug reports, the least we can expect from you is a logcat taken during the issue. Or atleast, you could tell us how and when did you face the bug, how can we reproduce the bug to fix it. Reports without any of these will be ignored.
Q - Can I use your ROM/any part of ROM and modify it and release it separately?
A - Yes you can. But please mention proper credits.
Bug reporting
How to report a bug?
First off all, check the 'not working' list and see if the bug you are facing is already mentioned or not. If it is, stop right away because the concerned people working on the ROM are aware of the issue.
If the bug/issue is not mentioned in 'not working' list, check the Frequently Asked Question (F.A.Q) and see if issue is resolved already.
If the issue you face is not in FAQ either, you would probably post a reply in this forum, and not PM anyone, about the bug.
Attach a logcat.
If not possible, mention a proper way how you encountered the bug.
Also mention any 3rd party stuff you installed. (Like mods, themes, kernels etc)
Following things WILL NOT be considered as bugs. So please do not post such bug reports, they will be ignored.
Low benchmark scores. Even if Stock results better.
Poor performance in gaming. Even if Stock results better.
High RAM usage/low RAM available.
Various kernel control app crashes.
Crashes of various UI elements when a custom theme/mod is applied.
Random reboots, and other issues caused by flashing custom kernel.
Thank You!!!!
Reserved
Broken Link Fixed
Thanks @Kuck7610 it was a great ROM thanks For Supporting OTUS
Thank you for developing for Otus! Would love to try out asap! Will report soon..
Thanks Buddy, really appreciate your work :highfive:
Thanks for the pure CAF Beauty
Has RIL been fixed in today's build?
Final AOSPA-7.1.3-DEV
The final bugfix update( pa_otus-7.3.0-dev-20171028 ) release on 28 Oct 2017,
Thank You every one!!!
Cheers And #StayParanoid
Huse Thanks
Kuck7610 said:
The final bugfix update( pa_otus-7.3.0-dev-20171028 ) release on 28 Oct 2017,
Thank You every one!!!
Cheers And #StayParanoid
Click to expand...
Click to collapse
Thank you for everything , finally we got fully working AOSPA
Kuck7610 said:
The final bugfix update( pa_otus-7.3.0-dev-20171028 ) release on 28 Oct 2017,
Thank You every one!!!
Cheers And #StayParanoid
Click to expand...
Click to collapse
I am not able to flash even pico gapps with this rom. Its strange because i have flashed larger roms with larger gapps on this device but now its showing me memory space error. iam doing a clean flash.
And what is that backup tool for and what backup is it making and restoring.Is it causing space error?
UPDATE: i tried to boot it without gapps and now its just sitting at boot logo(not bootanimation), does this rom has a boot animation? coz for me its just siiting at bootlogo for past 10 mins. @Kuck7610
UPDATE-1:I am able to flash Lineage os with nano gapps(larger than pico), so i think its rom specific bug.Kindly look into it.I will try to provide you with logs soon.
UltimateBlade said:
I am not able to flash even pico gapps with this rom. Its strange because i have flashed larger roms with larger gapps on this device but now its showing me memory space error. iam doing a clean flash.
And what is that backup tool for and what backup is it making and restoring.Is it causing space error?
UPDATE: i tried to boot it without gapps and now its just sitting at boot logo(not bootanimation), does this rom has a boot animation? coz for me its just siiting at bootlogo for past 10 mins. @Kuck7610
Click to expand...
Click to collapse
Really? Are you on 28th build? I thought this build was supposed to fix bugs.
Can you try to clean flash again with maybe different GApps ? Please report back as even I was thinking of flashing this build
rpravenclaw said:
Really? Are you on 28th build? I thought this build was supposed to fix bugs.
Can you try to clean flash again with maybe different GApps ? Please report back as even I was thinking of flashing this build
Click to expand...
Click to collapse
i tried 6 times but nothing.
UltimateBlade said:
i tried 6 times but nothing.
Click to expand...
Click to collapse
Maybe download again?
rpravenclaw said:
Maybe download again?
Click to expand...
Click to collapse
Only if u or anyone else confirm that rom is working fine because i dont have anu problem in "flashing" rom. its just the boot and gapps thing.
i knewed you were working on this XD i saw it on github kuck you rock
UltimateBlade said:
I am not able to flash even pico gapps with this rom. Its strange because i have flashed larger roms with larger gapps on this device but now its showing me memory space error. iam doing a clean flash.
And what is that backup tool for and what backup is it making and restoring.Is it causing space error?
UPDATE: i tried to boot it without gapps and now its just sitting at boot logo(not bootanimation), does this rom has a boot animation? coz for me its just siiting at bootlogo for past 10 mins. @Kuck7610
UPDATE-1:I am able to flash Lineage os with nano gapps(larger than pico), so i think its rom specific bug.Kindly look into it.I will try to provide you with logs soon.
Click to expand...
Click to collapse
In all of @Kuck7610 roms, you need to repair file system in order to flash gapps....
rpravenclaw said:
Really? Are you on 28th build? I thought this build was supposed to fix bugs.
Can you try to clean flash again with maybe different GApps ? Please report back as even I was thinking of flashing this build
Click to expand...
Click to collapse
About the booting issue, it has been confirmed by a few other people including me, but a few others were able to boot so idk why it's happening, but just wait till @Kuck7610 tells us something more...
Dev_Mashru said:
In all of @Kuck7610 roms, you need to repair file system in order to flash gapps....
About the booting issue, it has been confirmed by a few other people including me, but a few others were able to boot so idk why it's happening, but just wait till @Kuck7610 tells us something more...
Click to expand...
Click to collapse
Repair file system as if? Changing it to f2fs ? As far as I know repairing will format all data of that partition right?
UltimateBlade said:
I am not able to flash even pico gapps with this rom. Its strange because i have flashed larger roms with larger gapps on this device but now its showing me memory space error. iam doing a clean flash.
And what is that backup tool for and what backup is it making and restoring.Is it causing space error?
UPDATE: i tried to boot it without gapps and now its just sitting at boot logo(not bootanimation), does this rom has a boot animation? coz for me its just siiting at bootlogo for past 10 mins. @Kuck7610
UPDATE-1:I am able to flash Lineage os with nano gapps(larger than pico), so i think its rom specific bug.Kindly look into it.I will try to provide you with logs soon.
Click to expand...
Click to collapse
Yes same problem with me
Hey , as u know that paranoid 7.3.1 is out now , so can u please try to fix all those issues that were in previous release with this final release of paranoif nougat rom.
Thanks for your contribution towards this device @Kuck7610
UltimateBlade said:
Repair file system as if? Changing it to f2fs ? As far as I know repairing will format all data of that partition right?
Click to expand...
Click to collapse
Sorry for replying late...I didn't get any notification of quote,nor did I bother to read my mails so sorry for that....
I meant you had to resize the partition using repair the filesystem option in twrp. Sorry for the confusion..
Update
UltimateBlade said:
Hey , as u know that paranoid 7.3.1 is out now , so can u please try to fix all those issues that were in previous release with this final release of paranoif nougat rom.
Thanks for your contribution towards this device @Kuck7610
Click to expand...
Click to collapse
Hello !!!
I understand your concern , Some of users get Black screen issues now m investigate this things where i did wrong and how can i fix this thing and also i lost my device so it take hell lot of time to figure it out what's wrong on it . Now m simple request all of user's plz do some patient about this thing if i get anything +ve or -ve sign then I'll post things up here!!
Thank you
{
"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"
}
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned.
[ROM][AOKP 8.1/OREO][HLTE] AOKP Oreo for Galaxy Note 3 (Unified) Beta Builds
These are beta builds!!! Stuff may be broken/missing/jank!!! You have been warned. Again.
Code:
*** Disclaimer***
Your warranty is now void!
I am not responsible for damages caused by this ROM
YOU are choosing to install it!
If you have any concerns about potential issues or features with this ROM, do your research!
If you accuse me of causing problems with your device, you WILL be ridiculed!
Read the above warnings again! These are BETA builds!
They are [B]NOT[/B] feature-complete, nor are they guaranteed to run!
By installing them, [B]YOU[/B] are assuming the risk of any potential problems!
Introduction
AOKP is a ROM developed by TeamKang, based on AOSP with magical unicorn bytes (awesome features) baked right in!
hlte builds are for hltexx/hltespr (SM-N9005/SM-N900P)
hltechn builds are for hltezm (SM-N9008V)
hltekor builds are for hltektt/hltelgt/hlteskt (SM-N900K/SM-N900L/SM-N9005 (SK Telecom ONLY))
hltetmo builds are for hlteusc/hltetmo/hltevzw/hltecan (SM-N900R4/SM-N900T/SM-N900V/SM-N900W8)
Features
Android 8.1 Oreo
OMS/Substratum Support - Theming baked right in
SU baked in - No need for SuperSU/Magisk (Unless you want them!)
ROMControl App - A centralized place to manage all almost all the cool features Magical unicorn Bytes!!
More features coming soon! (P.S. Asking for ETA's is bad, unless you like NOT getting new features! )
Click to expand...
Click to collapse
Known Issues
Bluetooth does not work with some devices - This is a known issue that also affects LineageOS-15.1 Fixed?
You tell me! I have limited testing time, so the more reports I get the better. Please see below for proper issue reporting!
Click to expand...
Click to collapse
Proper Issue Reporting
Make sure you are seeing the issue on a CLEAN install! If the problem pops up after a dirty flash, wipe data/factory reset and see if it still happens before reporting it
Make sure you have not flashed anything extra, such as 3rd party kernels, SuperSU, Magisk, Xposed, etc. These extra packages can cause their own issues. As above, try a full wipe and then only flash the ROM package and Gapps package, and see if the issue persists before reporting
In your report please include the following:
Issue you are seeing, and how to recreate it
Logcat/kmesg from right after the issue if possible
Build date of ROM you are running
Gapps package you have installed
Click to expand...
Click to collapse
Installation instructions
Backup your data! (nandroid, TiBu, etc.)
Wipe Data/Factory Reset (You did backup, right?)
Flash ROM
Flash GAPPS
Wipe Cache/Dalvik Cache
Reboot
Click to expand...
Click to collapse
Download
shane87 AndroidFileHost page:
shane87's AFH page for hlte Oreo Builds (BETA)
shane87's AFH page for hltechn Oreo Builds (BETA)
shane87's AFH page for hltekor Oreo Builds (BETA)
shane87's AFH page for hltetmo Oreo Builds (BETA)
Source:
AOKP Source
Click to expand...
Click to collapse
Changelog
Code:
[B][U]Detailed changelogs between each version can be found at download link[/U][/B]
[B][U]Current changelog: 07/21/2019[/U][/B]
*[fix]BT bug fixed......again......maybe? lol
*[update]Latest AOSP/LOS upstream changes (No AOKP changes since last build - We are all focused on Pie, when we have time!)
[B][U]Changelog: 07/06/2019[/U][/B]
*[fix]BT bug finally squashed! - I hope anyway, let me know guys!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 12/09/2018[/U][/B]
*[fix?]Changes in hardware/samsung (6 commits) - MAY fix BT issues!
*[update]Latest AOSP/AOKP/LOS upstream changes
[B][U]Changelog: 11/18/2018[/U][/B]
*[fix?]Set proper WBS sample rate - MAY fix BT issues!
*[update]Update to Android 8.1_r50 base
*[update]All upstream changes since 09/16
[B][U]Changelog: 09/16/2018[/U][/B]
*[update]Update to Android 8.1_r46 base
*[new/update]Add SystemProfiles QS Tiles
*[fix]Fix some QS tiles, remove some deprecated QS Tile code
*[fix?]Fix spacing in bluetooth_vnd.txt, [i]possible[/i] BT issue fix?
*Full changelog available at download link
[B][U]Changelog: 08/19/2018[/U][/B]
*[fix]Remove reference to mIsTap and Handler in absListViewWidgets.java (frameworks/base) - Fixes ListView mod widget issue
*[fix]Camera regression from 08/12 build fixed - No clue what happened, but everything is working again.
*[update]Add QS animation options to ROM Control
*[update]Add QS title hide option to ROM Control
*[update]Add AOKP logo on status bar option to ROM Control
*Full changelog available at download link
[B][U]Changelog: 08/12/2018[/U][/B]
*[fix]su issues from previous build fixed
*[update]Revert soundboost to stop speaker distortion [update]SoundBoost mods available at dl links!
*Full changelog available at download link
[B][U]Changelog: 07/31/2018[/U][/B]
*[update/fix?]Remove CarrierConfigs from hlte/hltetmo device trees; CarrierConfigs was duplicated in msm8974-common
*[update/fix]Remove vendor security patch level from device trees, move to common tree
*Full changelog available at download link
[B][U]Changelog: 06/24/2018[/U][/B]
*[update]Use mpdecision from G900FXXU1CRA2_G900FOXA1CRA2_BTU
*[update]Drop lib_cutils_atomic shim (was only needed for old mpdecision)
*[fix?]Changing mpdecision and dropping the shim [B][U]SEEMS[/U][/B] to have fixed rotation on LOS, hopefully fixed for us
*Full changelog available at download link
[B][U]Changelog: 06/03/2018[/U][/B]
*[fix]Boost sound levels across all devices
*Full changelog available at download link
[B][U]Changelog: 05/14/2018[/U][/B]
*[fix?]Commit pulled in from AOKP source to fix camera recording issues.
*[update]Latest changes from AOKP source
*Full changelog available at download link
[B][U]Changelog: 05/06/2018[/U][/B]
*[update]Minor changes to QS header images support
*[new]Scrollable QS tiles
*[new]Add builds for hltechn/hltekor/hltetmo
*Full changelog available at download link
[B][U]Changelog: 4/30/18[/U][/B]
*[fix?]Changes to phone call audio routing, may help BT phone audio issues
*[fix?]New overlay that may help with auto-rotation bug
*[new]Customizable header images
*Full changelog available at download link
[B][U]Changelog: 4/23/2018[/U][/B]
*[new]Initial AOKP Oreo Beta release for hlte
Thanks To/Credits
TeamKang
tdm
LineageOS
@stonedead - For finding sensor batching overlay; a potential rotation bug fix!
PayPal Donations and thanks are always appreciated!
XDA:DevDB Information
Oreo Android Open Kang Project for Samsung Galaxy Note 3 (HLTE), ROM for the Samsung Galaxy Note 3
Contributors
shane87
Source Code: http://aokp.co/source/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.2.1-1
Based On: AOKP
Version Information
Status: Beta
Current Beta Version: 2019-07-21
Beta Release Date: 2019-07-21
Created 2018-04-24
Last Updated 2019-07-21
Reserved
As far as an update schedule goes, I will TRY to do weekly builds with the latest commits. I will also TRY to pull in pending commits when possible, assuming I can get them to build.
Nice.. Keep it up :good:
Sorry, can you tell me if the NFC and Bluetooth calls work? Thank you
Ottobrerosso1977 said:
Sorry, can you tell me if the NFC and Bluetooth calls work? Thank you
Click to expand...
Click to collapse
I don't know about nfc, as I never use nfc, but I can confirm that Bluetooth calls work, at least for some Bluetooth devices. I have a Plantronics Legend bt headset, and I can make Bluetooth calls on it. With that being said, I have received reports of some bt devices not working, so ymmv
Button backlight, just as in Nougat AOKP, doesn't work at all. Only in the button settings menu does it come on. They work fine on RRO or LA15.1.
That's what i've found so far.
I'm testing your build to see if the infamous rotation bug from LA15.1 and RRO is present in AOKP and so far it looks good but i need more time to test it.
Running clean install of AOKP with internal root and 23-04 GApps Mini FYI.
Imprezzion said:
Button backlight, just as in Nougat AOKP, doesn't work at all. Only in the button settings menu does it come on. They work fine on RRO or LA15.1.
That's what i've found so far.
I'm testing your build to see if the infamous rotation bug from LA15.1 and RRO is present in AOKP and so far it looks good but i need more time to test it.
Running clean install of AOKP with internal root and 23-04 GApps Mini FYI.
Click to expand...
Click to collapse
Thanks for the report! I'm aware of the button backlight issue as well, I didn't include it in the know issues since it was a carryover from Nougat. I have had a report of rotation issues from Oreo builds, not sure if it affects everyone or just some people, but I am looking into a fix by trader418 that was mentioned to me. By LA15.1, are you referring to LineageOS 15.1? I'll see if I can dig something up on the button backlight issue.
[Edit]
Also, the GApps Mini you are running, is it from OpenGApps?
[/Edit]
shane87 said:
Thanks for the report! I'm aware of the button backlight issue as well, I didn't include it in the know issues since it was a carryover from Nougat. I have had a report of rotation issues from Oreo builds, not sure if it affects everyone or just some people, but I am looking into a fix by trader418 that was mentioned to me. By LA15.1, are you referring to LineageOS 15.1? I'll see if I can dig something up on the button backlight issue.
[Edit]
Also, the GApps Mini you are running, is it from OpenGApps?
[/Edit]
Click to expand...
Click to collapse
Yup OpenGApps Mini. And yeah i meant Lineage. It for some reason always autocorrects a single letter L to LA..
I don't know what the rotation issue is. I mean, some people have it a lot, like me, and some people like vidwhal himself cannot for the life of them recreate it. It has something to do with the accelerometer that just stops giving any values. And so far, it seems that your AOKP build is the most stable so far in terms of rotation. I'm going to continue to set up the ROM with my apps and preferences and i'll see if it keeps working.
Edit: Blast it.. it looked so promising.. didn't have any rotation issues for hours.. and suddenly out of nowhere it stopped working again completely and accelerometer has once again stopped giving any values in Sensors Mutlitool...
Ok, what did i do.. ehm.. installed some apps like chrome, and substratum.. customized my homescreen with the shortcuts i use.. loaded up BigBlu in substratum (works perfectly with AOSP mode btw.) installed adaway (root), used titanium backup (root) to restore my Steam app (so that I don't have to re-activate the steam authenticator), loaded up adaway and thats when i noticed chrome had stopped rotating when i wanted to test adaway..
Was about to reboot into recovery to install xposed v90 beta3 and Gravitybox O so i can center my clock in the statusbar and rebind the back button long press to flashlight but i guess that doesn't really make much sense now that it has stopped working..
Funny thing is, not even a full reboot will fix it. Once it stops working.. it's just done for. With a full power off and reboot it will work for a few seconds after boot but that stops again.
I do have to add on a positive note, i have never had a Oreo rom THIS ridiculously smooth and quick. This ROM runs amazing.. And it has VERY low battery drain when in use. It drains even slower when just using the web or installing stuff than even the best TW6.0 ROMs do.. Incredible. It easily rivals or beats RRN 5.8.5 in terms of smoothness and responsiveness.
Congrats on your new thread bro. It's getting into a right direction now @shane87. So glad to woke up from sleep and seeing the auto rotation still works.
Usually the auto rotation failed within minutes after fiddling with google maps on previous test build and on other oreo rom. Will see it further, hopefully the issue is gone for good now.
Thanks..
Edit: really a one crazy bug this sensor issue. It happening again after a reboot ?
Now that you mentioned it.. I did also reboot before it happened again. It was fine for hours even after maps and setting up the entire ROM but after I applied my substratum theme I rebooted to make sure it applied to all open apps as well and that's when it started again..
I did make a full nandroid of the failed system.. So if you want me to test something I can just put that back.
You guys with the rotation bug, I'm looking in to a possible fix by trader418 that was mentioned by another one of my testers. I have to do some digging and see if I can find how he fixed it. It's so odd. On Nougat, my wife's Note 3 (my only test device) never had the rotation bug. I haven't ran Oreo on it enough to see if it has the rotation bug on Oreo, though I may do that this weekend.
One question for those experiencing the rotation bug: what model is your Note 3?
shane87 said:
You guys with the rotation bug, I'm looking in to a possible fix by trader418 that was mentioned by another one of my testers. I have to do some digging and see if I can find how he fixed it. It's so odd. On Nougat, my wife's Note 3 (my only test device) never had the rotation bug. I haven't ran Oreo on it enough to see if it has the rotation bug on Oreo, though I may do that this weekend.
One question for those experiencing the rotation bug: what model is your Note 3?
Click to expand...
Click to collapse
N9005 here..
I have zero issues on any Nougat ROM as well. That's what makes it frustrating to fix.
Mines also a N9005.
I cannot flash the patched zip file by dual boot patcher
It gives this error logs attched
Im using latest twrp 3.2. thanks
Kalhan said:
I cannot flash the patched zip file by dual boot patcher
It gives this error logs attched
Im using latest twrp 3.2. thanks
Click to expand...
Click to collapse
From the errors given in the log, the multiboot patcher did not patch the zip file correctly. All of the errors were from the zip file being corrupted. So either the file was corrupted during download, or during patching.
With all of that being said, I can't help with issues on dualboot setups. I have never used any of the dualboot setups. Any issues with dualboot need to be taken to the dualboot thread.
thanks good as a daily driver already
Works with N900T?
Par.10 said:
Works with N900T?
Click to expand...
Click to collapse
No, N900T has it's own device tree and separate builds. This is for hlte devices, N9005 and N900P
Alright guys, I have been doing some digging into @trader418 and I can't find anything in particular that helps the rotation bug. In his unofficial Lineage 14 thread, he mentions some cm/los updates that fixed the rotation issues, but doesn't mention the exact commit. Also, it sounds like those changes should already be in these builds, since AOKP's hlte device trees, and kernel source, are forked from LineageOS trees. And I do make sure to pull in the latest LOS changes. So I am still stumped on the rotation bug. On to better news. I have just finished a new build, with the latest AOKP changes synced in. I also pulled in some open commits that add customizable header image support. Along with a few open commits from LOS, mostly to do with phone call audio, so hopefully that may help with BT issues. I am going to do some personal testing before I upload, so be patient, new goodies are on their way!
{
"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"
}
TeamHorizon's XenonHD rom builds for Xiaomi Redmi Note 6 Pro (tulip)
[url]http://www.xenonhd.com/[/URL]
XenonHD is a custom firmware aka ROM for various Android devices. It is based on LineageOS 16.0 with additional features, performance and battery life improvements.
The idea behind XenonHD is to give users a ROM that is "blazing fast, rock stable and buttery smooth".
Device Source:
android_device_xiaomi_tulip
android_kernel_xiaomi_tulip
android_vendor_xiaomi_tulip
Download Links:
ROM: Experimental
IMPORTANT! Required firmware (flash before ROM): see post #4
Gapps: opengapps.org
Changelog: see post #3
Flashing Instructions:
To install this ROM you will need to have a latest custom Recovery such as TWRP installed.
Copy the downloaded ROM to your phone.
Boot into your recovery
Back up your ROM
Make a full wipe (system, data, cache, dalvik)
Install the ROM
Install GAPPS package
Reboot - the first boot can take up to 5 minutes
Installing updates:
Copy the downloaded update to your phone.
Boot into your recovery
Back up your ROM
Install the update
Optionally wipe caches
Reboot
Other Links:
Github
Google+
Telegram
Credits:
- @Pavanpatel for base device tree
- @rama982 for kernel and vendor sources
XDA:DevDB Information
XenonHD, ROM for the Xiaomi Redmi Note 6 Pro
Contributors
geekon
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Experimental
Firmware required: see post #4
Created 2019-03-19
Last Updated 2019-03-20
Screenshots
--
Changelog
20.03.2019:
XenonHD upstream
updated translations and fixed some XenonHub translations
updated kernel with rama's changes
kernel: added KCAL control, disabled some battery-eating wakelocks; added support for lower CPU frequency
improved battery life
NoCutoutOverlay improvements; added overlay for masking the notch
updated f2fs mount flags
fixed manual network selection
updated statusbar height
enabled Wi-Fi MAC address randomization
improved network signal strength
updated blobs from Pie: device tree & vendor blobs changes
updated trustzone version; Pie firmware required to flash
VERY IMPORTANT! Pie Firmware is now required to flash the ROM! (see post #4)
Also, there were lots of changes under the hood as well as updated ROM with latest Pie blobs so it is HIGHLY RECOMMENDED to clean flash the build if coming from earlier build!
Required Firmware
Since second Xenon build (20.03.2019) we use newer trustzone version & new Pie blobs that's why Pie Firmware is now required to flash the ROM.
Download: here
Great work.
Pavanpatel said:
Great work.
Click to expand...
Click to collapse
Thanks man.
New update available! [20.03.2019]
Changelog
20.03.2019:
XenonHD upstream
updated translations and fixed some XenonHub translations
updated kernel with rama's changes
kernel: added KCAL control, disabled some battery-eating wakelocks; added support for lower CPU frequency
improved battery life
NoCutoutOverlay improvements; added overlay for masking the notch
updated f2fs mount flags
fixed manual network selection
updated statusbar height
enabled Wi-Fi MAC address randomization
improved network signal strength
updated blobs from Pie: device tree & vendor blobs changes
updated trustzone version; Pie firmware required to flash
Download: here
VERY IMPORTANT! Pie Firmware is now required to flash the ROM! (see post #4)
Also, there were lots of changes under the hood as well as updated ROM with latest Pie blobs so it is HIGHLY RECOMMENDED to clean flash the build if coming from earlier build!
Great rom, thanks.
About updates interval...
Will try to keep the ROM updated weekly every Saturday.
After releasing few builds and having ensured the ROM is stable for daily use, will also make my effort to make the ROM Official.
Cheers,
geekon
thanks for your hard work.
one question, it is the phone call recording fixture working in this ROM regardless of the SIM card mobile country code.
for what I have been reading lineage OS call recording is controlled by the Sim card country code, witch can be bypass modifying the
android_packages_apps_Dialer/java/com/android/dialer/callrecord/res/
the source code is here
https://github.com/LineageOS/androi...e-16.0/java/com/android/dialer/callrecord/res
and can be modified.
would be great if you can compile the changes.
hidroela said:
thanks for your hard work.
one question, it is the phone call recording fixture working in this ROM regardless of the SIM card mobile country code.
for what I have been reading lineage OS call recording is controlled by the Sim card country code, witch can be bypass modifying the
android_packages_apps_Dialer/java/com/android/dialer/callrecord/res/
the source code is here
https://github.com/LineageOS/androi...e-16.0/java/com/android/dialer/callrecord/res
and can be modified.
would be great if you can compile the changes.
Click to expand...
Click to collapse
Sorry man but TeamHorizon dropped callrecording feature since Pie (Oreo had this feature).
You can see our Dialer sources here: https://github.com/TeamHorizon/android_packages_apps_Dialer/tree/p/java/com/android/dialer
Since tulip isn't official yet and I'm not TeamHorizon member I can't do anything for now. Maybe in the future coz I'm planning to make this ROM official after fixing SELinux stuff.
so this ROM don't use lineage dialer :crying:
What camera app is this rom has? Is MIUI cam available?
WakBagasi said:
What camera app is this rom has? Is MIUI cam available?
Click to expand...
Click to collapse
Camera2
hidroela said:
so this ROM don't use lineage dialer :crying:
Click to expand...
Click to collapse
No, it uses Lineage Dialer but with some small modifications - removed call recording, enabled wallpaper as a background and a few more.
@hidroela From what I have found out we now use complete paths to LineageOS repo that's why the Dialer app is completely synced with all LOS commits. Call recording also should be there if your country allows it. Any other hacks not present and rather won't be.
geekon said:
@hidroela From what I have found out we now use complete paths to LineageOS repo that's why the Dialer app is completely synced with all LOS commits. Call recording also should be there if your country allows it. Any other hacks not present and rather won't be.
Click to expand...
Click to collapse
ok thanks for letting me know about this. not a big deal I am pretty happy with miui the only thing that I am missing is the smart Lock fixture. good luck with your development brother.
geekon said:
Will try to keep the ROM updated weekly every Saturday.
After releasing few builds and having ensured the ROM is stable for daily use, will also make my effort to make the ROM Official.
Cheers,
geekon
Click to expand...
Click to collapse
Enough to give a try to this rom, thanks
Hey, i love the ROM so far. Smooth and stable as Hell. One thing tho... My Pixelmod camera stopped working. Any tips on modded camera apks?
How is the SOT of this rom?
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.
Code:
/* *** Disclaimer
* 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 KERNEL
* 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.
* BOOM goes the Dynamite
*/
Working
Same as PixelExperience
Broken
Same as PixelExperience
Difference between stock lineageos 17
Stripped ART debugging
Bionic improvements from AOSPA
Remove some debugging from framework_base
device tree changes
zram 1gb -> 512mb
lazytime support for EX4 (enabled by default)
custom dalvik props:
dalvik.vm.heapstartsize=8m -> 16m
dalvik.vm.heapminfree=512k -> 2m
lMemory Optimizations (am.reschedule_service & sys.fw.bservice_enable both enabled)
Simplified version of GlassCannon interactive profile
Tune sched parameters
Cpuset tweaks
kernel changes (pop kernel):
see second post
DOWNLOAD ROM
DOWNLOAD KERNEL
Installation:
Make full wipe (Format data and also normal wipe)
Flash rom
Flash GApps if needed
Flash Magisk if needed
Flash kernel
reboot
Telegram group
Credits:
All devs that did the ten bringup,
@theandroid02 for the device tree and vendor,
@mr.ace for his shadow kernel,
Many others
XDA:DevDB Information
UNOFFICIAL OPTIMIZED LineageOS 17.1, ROM for the LG Nexus 5X
Contributors
linckandrea
Source Code: https://github.com/linckandrea
ROM OS Version: 10.x Q
Version Information
Status: Beta
Created 2020-09-15
Last Updated 2020-09-15
Features
-based on the latest shadow kernel
-Cpu governors: electron,chill,relaxed,blu_active + all stocks
-Ioscheds: maple,bfq + all stocks
-dsync
-adreno idler (disabled by default)
-cpuboost optimization
-touchboost disabled (msm_performance module)
-wakelock blocker by boeffla
-wake gestures
-many other check source
NOTE: the kernel is compatible with oreo-pie-ten so it can be flashed in other roms
reserved 2
Hey,
thanks for your ROM and kernel! I am looking forward to test it.
You say everything works like PE ROM, great.
Has someone confirmed that VoLTE and more importantly to me is Google Camera with encryption enabled actually working?
[edit] Clarified that it is a question if someone has tested if Google Camera is working is encryption enabled.
That is great, thank you!
Just flashed the kernel on my Nexus ROM and seems very smooth, maybe I'll try also the ROM!
Just to know, does your kernel ha voltage control enabled, making undervolting possible?
I ask because the section and the values appears inside Ex Kernel Manager, but I can't edit them.
RelentlesS747 said:
Hey,
thanks for your ROM and kernel! I am looking forward to test it.
You say everything works like PE ROM, great.
Has someone confirmed that VoLTE and more importantly to me Google Camera with encryption enabled is actually working.
Click to expand...
Click to collapse
Unfortunately my provider doesn't support VoLTE so i can't test it however if it works on PE i don't see why it shouldn't work here
Punkiderma said:
That is great, thank you!
Just flashed the kernel on my Nexus ROM and seems very smooth, maybe I'll try also the ROM!
Just to know, does your kernel ha voltage control enabled, making undervolting possible?
I ask because the section and the values appears inside Ex Kernel Manager, but I can't edit them.
Click to expand...
Click to collapse
Undervolting/Overvolting is not possible since kernel sysf provide only the information about voltages
i tried manual undervolting on ether(nextbit robin msm8992) and it was very unstable so it should be the same with bullhead
Can you test if Google Camera is working with encyption enabled because svlogs LOS17.1 ROM does not work for me in that regard.
Nice ROM and nice kernel.
I installed this ROM on LineageOS 17.1 by equlog and it works very well. Thank for your great work
linckandrea said:
Undervolting/Overvolting is not possible since kernel sysf provide only the information about voltages
i tried manual undervolting on ether(nextbit robin msm8992) and it was very unstable so it should be the same with bullhead
Click to expand...
Click to collapse
Sphinx kernel had working voltage control but it was never updated to support android Q.
I used it for a long time under Oreo and after finding the right values the device remained very stable.
Can this be a useful source to get voltage control working also under android Q or there are other issue that makes this not possible? I'm not a dev so sorry if this is a silly question
EDIT: I noticed that live display stops working if i flash this kernel, and also if I flash shadow kernel, so maybe there's a bug in the base. I'm on nexus rom.
GPS Problems
linckandrea said:
Installation:
Make full wipe (Format data and also normal wipe)
Flash rom
Flash GApps if needed
Flash Magisk if needed
Flash kernel
reboot
Click to expand...
Click to collapse
Hello again
I moved from NexusROM to your ROM and kernel. Encryption and Google Camera is working fine and switching from mobile data to WiFi and back is also working good (I had problems with that in the past). Thank you very much!
GPS Problems:
However I cannot get GPS working. It just never picks up a signal to locate me. Attached you can find a looong logcat log file. I think it has some gnss, Loc_hal_worker, Gps, LocSvc_eng errors in it. I suggest you start taking a look from the end of the log file. I had to split the file into two because of a 512kB *.txt file size limit.
Punkiderma said:
Sphinx kernel had working voltage control but it was never updated to support android Q.
I used it for a long time under Oreo and after finding the right values the device remained very stable.
Can this be a useful source to get voltage control working also under android Q or there are other issue that makes this not possible? I'm not a dev so sorry if this is a silly question
EDIT: I noticed that live display stops working if i flash this kernel, and also if I flash shadow kernel, so maybe there's a bug in the base. I'm on nexus rom.
Click to expand...
Click to collapse
this kernel doesn't support lineage livedisplay, in futures release i will implement klapse...
RelentlesS747 said:
Hello again
I moved from NexusROM to your ROM and kernel. Encryption and Google Camera is working fine and switching from mobile data to WiFi and back is also working good (I had problems with that in the past). Thank you very much!
GPS Problems:
However I cannot get GPS working. It just never picks up a signal to locate me. Attached you can find a looong logcat log file. I think it has some gnss, Loc_hal_worker, Gps, LocSvc_eng errors in it. I suggest you start taking a look from the end of the log file. I had to split the file into two because of a 512kB *.txt file size limit.
Click to expand...
Click to collapse
i see, thank you for the logs.. using this should fix the issue
https://github.com/LiteApplication/hardware_qcom_gps
linckandrea said:
i see, thank you for the logs.. using this should fix the issue
https://github.com/LiteApplication/hardware_qcom_gps
Click to expand...
Click to collapse
cool
I also have lots of stability issues with Google Camera.
Crashes after two Pictures or so.
RelentlesS747 said:
cool
I also have lots of stability issues with Google Camera.
Crashes after two Pictures or so.
Click to expand...
Click to collapse
i have the same issues with the google play store version, on other phones
camera NX works without problems if is installed as system app
in fact the next build i will include it by default
linckandrea said:
i have the same issues with the google play store version, on other phones
camera NX works without problems if is installed as system app
in fact the next build i will include it by default
Click to expand...
Click to collapse
Nice, do you plan to maintain this for some time?
For Volte question: there was a specific patch on PE10 for that in the device tree. i.e.: https://github.com/PixelExperience-...ackages/apps/CarrierConfig/res/xml/vendor.xml
Have you merged that changes?
linckandrea said:
this kernel doesn't support lineage livedisplay, in futures release i will implement klapse...
i see, thank you for the logs.. using this should fix the issue
Click to expand...
Click to collapse
How do you install the GPS fix? Install zip from TWRP?
Nice one! Thanks for keeping this device alive!
@linckandrea
have you found some time and passion to tackle the GPS and / or Camera Problems?
no stress, i am just wondering
@linckandrea I wonder does this ROM include live caption since I am deaf and need those feature. let me know. thanks
Updated: Ignore my asking question, i got it working and thanks
New update
download links are updated in the first post
Rom changes
Some bionic improvements from AOSPA
Stripped out some debugs in framework_base
device tree changes
radio power saving
sensors: Don't wake on significant motion
kernel changes
see this github history
i can't test the gps since... well you know the lockdown
anyway i created a telegram group where i will release early my rom/kernel builds
linckandrea said:
New update
download links are updated in the first post
Rom changes
Some bionic improvements from AOSPA
Stripped out some debugs in framework_base
device tree changes
radio power saving
sensors: Don't wake on significant motion
kernel changes
see this github history
i can't test the gps since... well you know the lockdown
anyway i created a telegram group where i will release early my rom/kernel builds
Click to expand...
Click to collapse
I just mentiond you in the other thread. I will try your build and report back about the GPS.
I'm curious if my banking apps work with your updated rom, because they don't with @berom his build and also don't work with PixelExperience