Related
Hello people!
This is a clean ROM for Galaxy Nexus built from the AOSP source code.
Why this is a different AOSP-based ROM
The main goal is to reach a perfect configuration maintaining the stock interface and the stock kernel without compromising the stability of the pure Google AOSP ROM.
For this reason I deleted a lot of files which I repute not necessary for a smartphone like the Galaxy Nexus.
Less apps are loaded by Android system, more battery is available for you!
This is the main/daily ROM for my smartphone and its purpose is to be stable and to not drain battery.
I recommend to use the stock kernel for this reason and to maintain the same configuration.
If you want a more customized ROM, please look for CyanogenMod or AOKP based ROMs, they are the best and safe way to obtain the best usage from the Android System.
But if you agreed with me, if you want to really use a smartphone for working purpose, if you want to use the Galaxy Nexus to call people and if you don't need to "amaze" your Apple-funboys with Live Wallpapers, Swipe gestures on keyboard, Photosphere and other stuffs (please let me kid a little), then you are welcome to my work.
Features
- Compiled against Android 4.3.1 AOSP branch android-4.3.1_r1 (JLS36I);
- Fully disabled bugreports in kernel and ramdisk;
- Persistent root with su binary;
- Added the rotation toggle in Quick Settings;
- Disabled the Select Input Method notification when the keyboard is on;
- Minimal set of Google Apps;
- Flash Player support;
- Enabled Location Provider support;
- Blocked ads with custom hosts file;
- Busybox;
- init.d folder;
- Compiled with new binary files;
- Optimized audio quality;
- Added compatibility for TouchControl PGM (slide to unlock gesture);
- Added the Clear All button on recent apps;
- Added H+ icon support for HSPA+ network type;
- Support for AOSP browser bookmarks sync;
- Changed WiFi Tile behavior in Quick Settings (one click ON/OFF toggle);
- Changed Mobile Data behavior in Quick Settings (one click ON/OFF toggle);
- Changed Bluetooth Tile behavior in Quick Settings (one click ON/OFF toggle);
- One finger pulls down the Quick Settings if no notifications in status bar;
Download from Google Code
If you liked my work, please hit the Thanks button and consider a free donation, thank you
kalo86
thanks OP, this is just a pure aosp rom without any tweaks and customizations?
Sent from my Galaxy Nexus
allen oddest said:
thanks OP, this is just a pure aosp rom without any tweaks and customizations?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Hi, this is a pure AOSP ROM, zero tweaks and zero customizations.
Regards
kalo86 said:
Hi, this is a pure AOSP ROM, zero tweaks and zero customizations.
Regards
Click to expand...
Click to collapse
Will it stay that way? I would love to have a pure ROM to run which is kept up to date with AOSP. Most of the OTA apps, etc aren't available in my country, so this makes more sense to me.
It is rooted though, right?
rickbosch said:
Will it stay that way? I would love to have a pure ROM to run which is kept up to date with AOSP. Most of the OTA apps, etc aren't available in my country, so this makes more sense to me.
It is rooted though, right?
Click to expand...
Click to collapse
Yes, the compilation of AOSP source code has been inizialized with the "full maguro userdebug", that is to say that the ROM is rooted.
kalo86 said:
Hi, this is a pure AOSP ROM, zero tweaks and zero customizations.
Regards
Click to expand...
Click to collapse
what about root and deodex? more useful for us
Sent from my Galaxy Nexus
allen oddest said:
what about root and deodex? more useful for us
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
It's rooted and deodexed like every AOSP ROM.
That's a good work. It's a great base that you can modify as you want. :good:
HTCDevil said:
That's a good work. It's a great base that you can modify as you want. :good:
Click to expand...
Click to collapse
+1 thanks for a clean base AOSP ROM!
Language?
The filename for the donwload includes the word "eng". Is it an english or multi-language ROM?
clapele said:
The filename for the donwload includes the word "eng". Is it an english or multi-language ROM?
Click to expand...
Click to collapse
Probably stands for engineer which is an option while compiling aosp to have root r:good:
It's a WWE ROM.
SuperSU can't update its binaries anyone else?
clapele said:
The filename for the donwload includes the word "eng". Is it an english or multi-language ROM?
Click to expand...
Click to collapse
Of course multi-language!
gianton said:
It's a WWE ROM.
SuperSU can't update its binaries anyone else?
Click to expand...
Click to collapse
Failed with SuperSU and Superuser as well. Any solution?
Please read this post
clapele said:
Failed with SuperSU and Superuser as well. Any solution?
Click to expand...
Click to collapse
At the moment my Galaxy Nexus is in warranty for repair.
When I will get it, I'll try to help you.
Since I cannot test/install my build, is someone so gentle to express a feedback?
Is the ROM working fine? Any issue at the moment?
Please write here your feedback.
Thank you always for collaboration.
Regards,
kalo
I keep getting FCs with Skype and Gtalk, but those are the only issues I can find. SuperSU binaries update fine for me.
Flash ROM, the gapps, then SuperSU zip, reboot, update binaries and install busybox for good measure and it should work fine.
Sent from my Nexus Prime
rickbosch said:
I keep getting FCs with Skype and Gtalk, but those are the only issues I can find. SuperSU binaries update fine for me.
Flash ROM, the gapps, then SuperSU zip, reboot, update binaries and install busybox for good measure and it should work fine.
Sent from my Nexus Prime
Click to expand...
Click to collapse
Thank You for your post!
The AOSP code is the stock one of the repo, the ROM is original, not modded.
I hope to solve the FCs as soon as possible.
Regards,
kalo
No worries at all man, other than that it's certainly super fast, but I use both of those regularly, so can't run it until they're fixed, but once they are I'll definitely give it another go. (I did clear their data, etc)
Love the idea of just clean AOSP.
Sent from my Nexus Prime
rickbosch said:
No worries at all man, other than that it's certainly super fast, but I use both of those regularly, so can't run it until they're fixed, but once they are I'll definitely give it another go. (I did clear their data, etc)
Love the idea of just clean AOSP.
Sent from my Nexus Prime
Click to expand...
Click to collapse
Do you think that is a problem of Skype and Google Talk or a ROM issue?
NEWS: I'm uploading a new release, stay tuned!
I can only assume it's a ROM issue, bizarre as it seems because they work fine on everything else I've run.
When I have a chance I'll restore the backup I made and grab some logs/dmesgs and we can try figure it out.
Sent from my Nexus Prime
Hi all.
Compatibility:
It should work on any rom by following this logic:
Builds from r1 to r23 are Android 6.0.1 Marshmallow only (up until June's security patches)
Builds from r24 are for Android 6.0.1 Marshmallow only from July's security patch up to the r28.
Builds from r29 are for Android 7.0 Nougat.
Builds from r40 up to r49 are for Android 7.1.1 Nougat only.
Builds from r50 up to r55 are for Android 7.1.2 Nougat.
Builds from r56 up to r64 are for Android 8.0.0 Oreo.
Builds from r65 are for Android 8.1.0 Oreo.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from Franco Kernel Updater app
Features:
1 - Legendary battery life
2 - Flash & forget
3 - Typical interfaces like display adjustments, sound control, vibration control, and all that boring stuff
4 - Bypasses the verified boot flag for Android Pay compatibility (root still breaks Android Pay but that's your own problem)
5 - Idle power consumption reduced to the absolute minimum (if you have wakelocks from 3rd party apps you're obviously on your own)
6 - Support for FKUpdater's Performance Profiles
7 - Magical support, I'm here every day, checking posts almost hourly, ready to help anytime (well, unless you fail to read the OP, which contains most info you need)
8 - Seemless integration with my app FKUpdater
9 - No crap placebo patches, or "magical" optimizations
10 - Probably more, check my github for all the details - the code speaks for itself
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/angler
Power Profiles
https://forum.xda-developers.com/nexus-6p/general/power-profiles-francokernel-kernel-t3742799
Follow me on the interwebs
Google+
Twitter
Google+ FK community
https://plus.google.com/u/0/communities/117966512071636110546
Kernel Manager for Franco Kernel
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Yes it's about time!
FKUpdater users from previous phones: support for this device will be added as soon as realistically possible.
My main focus on r1 release was to improve battery life as much as possible. I'm very happy with it.
If you want a detailed change-log check my git.
I'm sure you're going to love it.
Yayyyy!! Franco is here!
r1 is only for 6.0.1, don't flash if you're not using it. Also you must use the new system-less SuperSu, 2.60 or newer.
YESSSSSSSSSSSSSS. . Been waiting for this..
Great to see your kernel here! Your kernels are always battery sippers!
giant22000 said:
Great to see your kernel here! Your kernels are always battery sippers!
Click to expand...
Click to collapse
I'm sure you'll find the same with this one Just make sure you're on 6.0.1 before flashing.
franciscofranco said:
I'm sure you'll find the same with this one Just make sure you're on 6.0.1 before flashing.
Click to expand...
Click to collapse
10-4
Already on 6.0.1
Thank you so much Franco! I'm sure I speak for the majority when I say WE LOVE YOUR KERNELS! Rock on! +1
xReaper7x said:
Thank you so much Franco! I'm sure I speak for the majority when I say WE LOVE YOUR KERNELS! Rock on! +1
Click to expand...
Click to collapse
You're ****ing welcome
Woohoo, the thread lives. Been testing the kernel for the past couple of days prior to r1 and it's been a pretty good experience in battery and performance.
Definitely recommended
franciscofranco said:
r1 is only for 6.0.1, don't flash if you're not using it. Also you must use the new system-less SuperSu, 2.60 or newer.
Click to expand...
Click to collapse
Why do we have to use the system-less? Will normal system root not play well with the kernel?
Fair enough to assume we should reflash SuperSU 2.61 after the flash of a zip?
Sent from my Nexus 6P using Tapatalk
Thanks Franco your kernels are to notch. Flashed thanks for your work!
Neverendingxsin said:
Why do we have to use the system-less? Will normal system root not play well with the kernel?
Click to expand...
Click to collapse
Yes will traditional root not work with this Kernel
Sent from my Nexus 6P using XDA Free mobile app
Neverendingxsin said:
Why do we have to use the system-less? Will normal system root not play well with the kernel?
Click to expand...
Click to collapse
Because for 2.52 to work it needs a different sepolicy bin, and I can't use the old 6.0 binary from CF's initial Nexuses pre-rooted boot.img. And because system-less SuperSu is the future and it will let you flash OTAs on your device without wiping or extra cleaning.
hajabooja said:
Fair enough to assume we should reflash SuperSU 2.61 after the flash of a zip?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes.
trlash said:
Thanks Franco your kernels are to notch. Flashed thanks for your work!
Click to expand...
Click to collapse
You're ****ing welcome
franciscofranco said:
Because for 2.52 to work it needs a different sepolicy bin, and I can't use the old 6.0 binary from CF's initial Nexuses pre-rooted boot.img. And because system-less SuperSu is the future and it will let you flash OTAs on your device without wiping or extra cleaning.
Click to expand...
Click to collapse
Thanks for the quick response. Where can I find information on how to go from system to systemless root, can't seem to find it on XDA (or i'm completely missing something).
Franco kernels
This is the best development (pun intended) of the day! Thanks Franco!
krexus_7.1.1-170309-flounder.zip - https://www.androidfilehost.com/?w=files&flid=144667 March security updates & Rootless Substratum
THINGS TO READ BEFORE ASKING:
Use N4F26T Vendor Image for 03/09.2017 build.
Stock kernel does not force encryption.
Not prerooted.
Built for the Nexus 9 Wifi (but it works on Nexus 9 LTE too. Flash latest volantisg vendor IMG and manually set APN)
Originally Posted by @KreAch3R
Krexus was born out of a simple necessity. The latest releases of stock Android (namely lollipop and marshmallow) were pretty close to my idea of a perfect android ROM, yet missing some elements, which are meant to be included in stock Android, at least for me. Starting from a clean AOSP environment, only specific features and fixes are included, which are personally tested ON HAMMERHEAD, with one goal in mind. To create a stock like android ROM, "as it should be".
This means, and I mean it, a ROM like how stock nexus image should be, for me.
This isn't going to get bloated. Most UI "features" are already there.
This isn't going to start picking commits relentlessly, I will test them personally and only add things that 1) work like they should 2) would fit in a stock ROM.
This isn't going to be updated very quickly. Only security and bug fixes will be pushed out ASAP.
This is going to follow Google's & AOSP guidelines as closely as I can.
And lastly, this is first and foremost a ROM about Nexus 5 (hammerhead). This is my personal device, this is where I test the ROM. angler, bullhead, flo, mako, shamu builds are provided AS-IS, and bugs/missing stuff/features especially for them will be put on the lowest priority and will depend on my free time. I will only guarantee the nexus 5 ROM and its abilities.
That said, welcome aboard!
Click to expand...
Click to collapse
Google+ Community
PushBullet Channel
DOWNLOAD LINKS:
KREXUS on AndroidFileHost
Previous Builds
CHANGELOG
Source Code: https://github.com/krexus
When @KreAch3R started building this ROM for shamu in 2015, I jumped on board right away. I've got Krexus running on every Nexus in my family: mako, hammerhead, shamu, grouper, and NOW flounder.
It runs beautifully on flounder and I hope you enjoy it too.
I am extremely grateful to @KreAch3R for all of his help and support.
IMPORTANT POINTS:
You have to flash GApps (Open or BaNks recommended)
ROM is not rooted, flash stable SuperSu for root
Busybox is included
Included kernel is stock no-force-encrypt
Flash newest factory vendor.img (I had Layers issues with stock selinux enforcing kernel on an older vendor version. Newest vendor.img works perfectly with stock kernel enforcing and layers)
F.A.Q.
a.k.a questions you shouldn't repost
Check the always updated F.A.Q.:
https://plus.google.com/+GeorgeGian/posts/f9m7zmi42Gy
OR
https://docs.google.com/document/d/1hMX-lQ2iUiNsrhszMIlp0Wwj1tSHWvsaEQ_yT4pD_eE/edit?usp=sharing?
BELIEVE ME, THE QUESTION YOU HAVE IS PROBABLY ANSWERED THERE.
Thank you for supporting the building for flounder, @buffal0b1ll!
For the next build, I will try to make Layers work with the default google kernel, and fix the processor info.
I want to specifically thank @BeansTown106, which device trees and blobs I used for this bringup.
Enjoy Krexus!
Another more conspicuous link for the Krexus G+ community.
https://plus.google.com/communities/117603046007221302455/
You will want to join this community if you like Krexus. It's very beneficial to hear user and developer advice/feedback and experiences across all supported devices.
Firsties!
Sent from my Motorola Nexus 6 using XDA Labs
Finally, we are starting to get some more quality ROM builds for this device. This is just awesome.
KreAch3R said:
For the next build, I will try to make Layers work with the default google kernel
Click to expand...
Click to collapse
Layers actually works fine with the default kernel and SELinux enforcing. An up to date vendor.img flash was all I needed to fix that.
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
Try the purenexus version of fire & ice
Sent from my Nexus 9 using XDA-Developers mobile app
dictionary said:
Is charging extremely slow for anyone else? Latest Fire&Ice kernel.
Click to expand...
Click to collapse
I'm still using fire-ice 10.2.2 and haven't noticed slow charging. In 18 minutes I went from 27 to 35% just now. Ampere has me charging at 1460 mAh
Thanks for a great rom! Will it work with LTE version?
maelfilk said:
Thanks for a great rom! Will it work with LTE version?
Click to expand...
Click to collapse
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
KreAch3R said:
I'm glad you like it! I don't know, as I don't have either device. Are the ROMs interchangeable on these two variants? For reference, the device tree is highly based on PureNexus' excellent tree (both based on AOSP with very few commits). The kernel is the default google kernel for flounder.
Click to expand...
Click to collapse
Will try it out on the weekend and report
Works great with LTE version!:good:
maelfilk said:
Works great with LTE version!:good:
Click to expand...
Click to collapse
That's awesome! Any hoops you had to jump thru?
buffal0b1ll said:
That's awesome! Any hoops you had to jump thru?
Click to expand...
Click to collapse
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
maelfilk said:
Nope, just flashed the rom and mobile data works right away. Corresponding section in settings and mobile data tile are also there.
Click to expand...
Click to collapse
Sweet. Not even a vendor fingerprint mismatch?
buffal0b1ll said:
Sweet. Not even a vendor fingerprint mismatch?
Click to expand...
Click to collapse
I always flash vendorfix in twrp to 100% avoid this error so can't tell
maelfilk said:
I always flash vendorfix in twrp to 100% avoid this error so can't tell
Click to expand...
Click to collapse
Got it. FYI I'd been manually vendor fixing the fingerprint since December on the Wi-Fi flounder and had layers issues on the stock enforcing kernel. Fire ice made it work with the old hacked vendor partition. To make layers work with stock kernel i updated to may factory vendor.img
Welcome everyone!
This thread has been created for extreme newbies/noobs and for their benefit. Not only noobs, but everyone is free to post questions and also give answers to those questions. Any type of question is allowed as long as it is related about the device. No off-topic discussions are allowed!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Will the lineageOS look same as CM or there will some certain other UI or features? Also there will be Theme engine like CM? And Audio fx?
chetan_1215 said:
Will the lineageOS look same as CM or there will some certain other UI or features? Also there will be Theme engine like CM? And Audio fx?
Click to expand...
Click to collapse
currently, lineage os is cyanogenmod only with a different name. But we don't know what they'll do in the future.
Will we be able to dirty flash the first Lineage OS builds over a current CM build or will it require a wipe?
brb lol said:
Will we be able to dirty flash the first Lineage OS builds over a current CM build or will it require a wipe?
Click to expand...
Click to collapse
you can dirty flash but you'll need to wipe system partition in TWRP (wipe, advance wipe, system and cache) and after you flash the ROM, reflash GAPPS
Will the new Lineage OS builds fix old bugs inherent in the old CM14.1 nightlies? Since the first CM14.1 build for my phone (HTC one m8), fellow Canadian users have reported that turning on location services resulted in bootloops (this did not occur with CM13). The problem was never fully fixed, and it didn't seem like anybody was working on a solution. It would be great if the new Lineage OS builds would have these old issues resolved.
Why is it that noone wants to support a device with an exynos based proccessor, and will it ever happen? For example noone is developing any AOSP roms for the galaxy s6 edge...
What will happen to those devices which didn't had any maintainer in CM? Eg ZUK Z1!
I would like to ask if Lineage OS will be available on the Huawei P8 Lite
DolDrum said:
I would like to ask if Lineage OS will be available on the Huawei P8 Lite
Click to expand...
Click to collapse
Mostly all devices that had support for official CM13 and CM14 will get Lineage OS. MOSTLY!!!! But no worries, newer devices will have official support too. Just we'll have to wait till the official support list comes up!
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
Will lineageOS have it on theme engine thank you for your help
Sent from my Nexus 6 using Tapatalk
galaxyman4g said:
Will lineageOS have it on theme engine thank you for your help
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes, I think so..... CM Theme Engine is one of the best things CM gave us so, obviously, they're not gonna remove it. If they do, I hope they'll add at least some theme engine or substratum.
Hit Thanks if I Helped You!!!
Regards,
PoseidonKing
RandomUsername02 said:
Why is it that noone wants to support a device with an exynos based proccessor, and will it ever happen? For example noone is developing any AOSP roms for the galaxy s6 edge...
Click to expand...
Click to collapse
Samsung makes the Exynos processors and doesn't release the processor source, and it is very difficult to develop on processors when there is no processor sources. Samsung stopped releasing the processor source code after the whole brickbug fiasco.
Additionally, they make it more difficult to develop on Exynos devices by, violating the GPL, (which the kernel is licenced under) by holding back parts of the kernel source code, to where what they provides rarely is enough to create a booting kernel, as is required. This makes it to where we can't really see how they make it work and reverse engineer a working kernel.
Maybe one of the s6 developers will port LineageOS to the S6's.
akc47 said:
Will the new Lineage OS builds fix old bugs inherent in the old CM14.1 nightlies? Since the first CM14.1 build for my phone (HTC one m8), fellow Canadian users have reported that turning on location services resulted in bootloops (this did not occur with CM13). The problem was never fully fixed, and it didn't seem like anybody was working on a solution. It would be great if the new Lineage OS builds would have these old issues resolved.
Click to expand...
Click to collapse
Lineage os = cyanogenMOD yes eventually they will fix it but lineage os is cyanogen so they will have the exactly the same everything except for name. Big and everything will be carried over.
Sent from my htc_m8 using XDA Labs
how can you ask for features to be added in lineageos? will the listen to their users better than cm did?
yakie996 said:
how can you ask for features to be added in lineageos? will the listen to their users better than cm did?
Click to expand...
Click to collapse
OMG how much time do I need to explain this? Lineage=cm every in cm is in lineage. All lineage stuff IS cm. Lineage is just a different name of cm
Sent from my htc_m8 using XDA Labs
justinchao740 said:
OMG how much time do I need to explain this? Lineage=cm every in cm is in lineage. All lineage stuff IS cm. Lineage is just a different name of cm
Sent from my htc_m8 using XDA Labs
Click to expand...
Click to collapse
yeah but other peoples with other ideas/mindset?
yakie996 said:
yeah but other peoples with other ideas/mindset?
Click to expand...
Click to collapse
You can post it on the lineage os main thread and hope it gets read.
Sent from my htc_m8 using XDA Labs
justinchao740 said:
You can post it on the lineage os main thread and hope it gets read.
Sent from my htc_m8 using XDA Labs
Click to expand...
Click to collapse
thats not how it should work, should it? I'll try
Bump
Sent from my Motorola XT1080 using XDA Labs
Hi everyone!
I have my OP 5t (8/128) since release date and it is still my favourite phone!
I'm thinking about future update policy from OP... Still running OOS 9.0.4, but how many updates will we get in the future?
Is it better to switch to a Custom Rom for better and longer support in the future? If yes - what Custom Rom do you prefer and why?
stefan.irmen said:
Hi everyone!
I have my OP 5t (8/128) since release date and it is still my favourite phone!
I'm thinking about future update policy from OP... Still running OOS 9.0.4, but how many updates will we get in the future?
Is it better to switch to a Custom Rom for better and longer support in the future? If yes - what Custom Rom do you prefer and why?
Click to expand...
Click to collapse
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
Hope it helps...
Sent from my OnePlus 5T using XDA Labs
Thanks a lot for your opinion!
I tried different Custom Roms, but all have one or two bugs, so i turned back to stock OOS... The most stable and bugfree Custom Rom for me was Pixel Experience!
Hope we will get a few updates in the future for our OP 5t
gsser said:
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
What's your top pick in Kernel?
Click to expand...
Click to collapse
VirginPancake said:
gsser said:
Pretty sure they will update 5t to q, dont know what will happen after that.
As for custom roms, try anything you want and see what suits your taste. Resurrection remix is a good example for customizations (or aex, havoc, coltos etc)
Omni Treskmod is kinda a flash and use style of rom. It is almost like Pixel Experience. You can also try diffrent kernel-rom combinations. You can try HMP and EAS based kernels. EAS is the one google have in their phones. You can google it up.
At the moment im trying DerpFest. My top 5 roms are;
1.Aex-Krieg(love krieg aex kernel)
2.ColtOS(Reminds me miui cause of it's diffrent recents style)
3.DerpFest(love it's boot animation and wallpapers)
4.Omni Treskmod(simple custom rom that you will never have a headache with but lacks customization)
5.CrDroid(enough customizations and overall stability.)
Some of the roms have problems with camera2api with WhatsApp and Instagram. I have asked many devs and thankfuly thry have fixed those problems. I would stay close with roms that have active telegram groups as you might need to troubleshoot if you find a bug.
Some roms have outdated xda threads such as ViperOS(saw a comment),ResurrectionRemix(latest builds in their sourceforge). So be sure to check their websites(if they have one) for latest builds before you download an older one.
What's your top pick in Kernel?
Click to expand...
Click to collapse
Overall performance - battery = Aex Krieg
Best battery life = Mad Kernel
Best performance = Weeb Kernel
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
gsser said:
VirginPancake said:
Overall performance - battery = Aex Krieg
Best battery life = Mad Kernel
Best performance = Weeb Kernel
Sent from my OnePlus 5T using XDA Labs
Click to expand...
Click to collapse
What's your opinion about RenderZenith or Weeb kernel? Those two are EAS right? Also franco kernel?
Click to expand...
Click to collapse
VirginPancake said:
gsser said:
What's your opinion about RenderZenith or Weeb kernel? Those two are EAS right? Also franco kernel?
Click to expand...
Click to collapse
Franco kernel and app feels like too complicated for me. RenderZenith is good if you want only eas and no other custom stuff(it will give you a little bit better results compared to stock kernel.). It is best for people who want to flash and use. Weeb also got better with it's beta versions but still, i would use it if i was playing heavy graphical games. If you want battery and stuff you can set manually go for Aex-Krieg kernel.
If you want pure HMP kernel that is focused on battery i would suggest Mad Kernel. Eas is not really best for battery, it is best for balanced
Dont get me wrong, franco kernel might be good but it doesnt suit me and i really didnt get use to it.
Click to expand...
Click to collapse