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
Related
Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03
Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545
Future FAQ if necessary (let's hope not).
Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.
gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.
build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?
Flounder still isn't listed just lunch it anyway
Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse
belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.
Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.
gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.
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!
Hi OnePlus 5 peeps!
Today (June 27th), I graduated from high school!
In more important news, I finished upstreaming the OnePlus 5 kernel to the latest stable kernel version...
Whoa, what is this?
This is my personal kernel that I run as the OnePlus 5 is my daily driver.
I will not claim my work as the best at anything, but just know that I would not do anything to this kernel that could potentially ruin my own device.
Additionally, this is the kernel that comes built into CarbonROM.
There are three versions of this kernel:
AOSP aka AOSP/LOS build - Flash this on any source built custom ROM except for CarbonROM
CR-5.1 aka CarbonROM build - Flash this on CarbonROM
OOS aka OxygenOS build - Flash this version on OxygenOS
Main features:
Upstreamed Linux kernel version, went from v4.4.21 -> v4.4.79
Backported random driver from Linux v4.12 (latest and greatest)
Backported scheduler from Linux v4.9 (latest android kernel branch)
Upstreamed F2FS driver from f2fs-stable/linux-4.4.y
KGSL driver improvements
MDSS driver improvements
SOC driver improvements
Built using Optimization Level 2
Added maple io scheduler (default) by frap129
Added adreno idler by arter97 with tweaks from frap129
Vibrator motor control by flar2
Kcal control driver from EX kernel
Many wakelocks disabled
Switched to power efficient workqueues across the kernel
Built with Google's latest stable gcc-4.9
Anykernel 2.0 by osm0sis! Compatible with all OxygenOS based roms
Download:
Latest builds
OxygenOS boot.img
How to install:
1. Reboot into the latest stable TWRP build
2. Download kernel zip and make sure it is in your internal storage (/sdcard)
3. Reboot into TWRP
4. Double check here to see if you require any additional instructions
5a. Install -> Install image -> select oxygen-4.x.x-boot.img -> swipe to install
5b. Install -> select CarboniteKERNEL-XXX-Rx-OP5-N.zip -> swipe to install
6. Reboot
DISCLAIMER!
If you don't understand my instructions, that's too bad >
If you are unsure about what this thing is, I highly advise you do some research before going through with installing...
Updates will come as regular as I want them to, don't ask me when I'll release cause you'll know when it comes out >:'D
XDA:DevDB Information
CarboniteKERNEL for the OnePlus 5, Kernel for the OnePlus 5
Contributors
adinkwok, nathanchance, flar2, Lord Boeffla, osm0sis, etc
Source Code: https://github.com/adinkwok/oneplus5-kernel
Kernel Special Features: One of Taylor Swift's exes should write a song called "Maybe You're the Problem"
Version Information
Status: Testing
Created 2017-06-28
Last Updated 2017-08-02
While this reserved post is not being used, enjoy this video! (Find me at 0:50s and twice at 2:54 :silly
For OxygenOS users:
Code:
[B]If you are on OxygenOS and are coming from another custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before flashing the kernel!
[B]If you are on OxygenOS are switching to a different custom kernel:[/B]
Download the latest stock.4.X.X-boot.img
You [B]must[/B] flash the boot.img before switching kernels!
For AOSP/LOS/RR/etc users:
Code:
[B]If you are coming from another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing this kernel!
[B]If you are on AOSP/LOS/RR/etc and are switching to another custom kernel:[/B]
You [B]must[/B] reflash your ROM build before flashing another kernel!
Why is it like this?
I have included some ramdisk modifications that set the default settings for this kernel. When you come from a different custom kernel, the ramdisk changes from that kernel may conflict with the changes I intend to have. Likewise when you switch to a different kernel; my ramdisk changes may conflict with the changes they intend to have. When you flash the stock boot.img, it replaces the modified ramdisk with a clean one, removing these conflicts.
And it's here, get it while it's hot folks! First upstreamed kernel for the OP5
Thanks for joining the party :highfive:
Sent from my OnePlus5 using XDA Labs
gz on graduating! and thx for the kernel :=
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
congratulations! awesome... so smart!!!!!!!
rav101 said:
Congratulations on the graduation buddy,
Just flashed and I had charging cycling on and off (using dash charger in car on freedom v1.1). Flashed EX and charging is fine. Need charge ATM but maybe a little later I can help you get a log.
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
What an amazing day for you (Congratulations!) and the OP5 community!
I was really loving and enyoing all your efforts you did for the OPO (Pure Nexus port) and the amazing Carbon ROM.
adinkwok said:
Hmmm never noticed this... I guess the graduation drinks are getting to me. I'll re-upload a stable build without upstreaming as that's definitely the culprit.
Click to expand...
Click to collapse
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Sent from my OnePlus5 using XDA Labs
rav101 said:
I'm the first to report so let's see if anyone else has the same issue. I will also try for logs later on though I do have a lot on today (so might be this evening).
I didn't actually reboot or get to try a different charger to help diagnose so don't want you doing more work that you need to for what could me my issue
Click to expand...
Click to collapse
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
adinkwok said:
I can confirm the issue because while I was bringing up the upstream branch I ran into this issue with dash charging and I thought I solved it. Time to debug!
Edit: link updated without the upstreaming, everything else still stands though
Click to expand...
Click to collapse
No problem buddy,
Be good once it's all resolved and we have the benefits of upstream kernel code as well!! Your time and effort is appreciated!
Sent from my OnePlus5 using XDA Labs
@rav101 happy to see u around buddy
dukat0s said:
@rav101 happy to see u around buddy
Click to expand...
Click to collapse
For sure my friend.
How you finding the OP5?
Sent from my OnePlus5 using XDA Labs
rav101 said:
For sure my friend.
How you finding the OP5?
Click to expand...
Click to collapse
Cool my friend !like it.just got rid of my s8+. Was bored
Is DT2W working for you guys?
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
Seems to be a problem among a few custom built kernels, we're looking into it.
bartelamo said:
Is DT2W working for you guys?
Click to expand...
Click to collapse
adinkwok said:
Seems to be a problem among a few custom built kernels, we're looking into it.
Click to expand...
Click to collapse
It's because OOS has a hal that already uses a switch for dt2w.
New update, still looking into the gestures issue.
However, Dash Charging is fixed on the upstream kernel so here it finally is! I also added a bunch of sched patches, a thermal patch, and some other misc stuff from the latest CAF branch.
Adin-Kernel-R2-OP5-OOS-N.zip
OmniROM
[#KITKAT]
for Samsung Galaxy Nexus (Unified)
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
Specials added on top of Official OmniRom Source
All in One Animation Control
Battery Saver mode
On-The-Go mode
Implement App circle sidebar
follow dark 4.4 UI
Those features have never been ready for official Omni, but people spend a lot of time writing those features and i really like those.
I am trying to release an security update monthly after google publish android security bulletins.
Support development
[#DONATETOME]
XDA:DevDB Information
[unified][4.4.4] OmniROM, ROM for the Samsung Galaxy Nexus
Contributors
Android-Andi, Ziyan
Source Code: https://github.com/omni-security
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Current Stable Version: Final Build availabl
Created 2017-08-12
Last Updated 2017-08-18
Hello everyone, first of all, great work @Android-Andi thank you to take the time to support our old device !
And then sorry for my noob questions but :
- I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
- What is the main difference between Omni 4.4, Omni 6.0 or Slim 6.0? I want to use one of those but I don't know which one I think Omni 4.4 is the closest from what I had with the official Jelly Bean ROM and the 2 others are optimized version of Marshmallow. And is Slim 6.0 faster than Omni 6.0?
Thank you again
Radder124 said:
I didn't quite understand the difference between device specific and unified builds and I don't want to make a mistake flashing the wrong one.
Click to expand...
Click to collapse
Unified builts are for all types of tuna: Maguro, Toro, Toro+. When booting only the needed (device specific) drivers are loaded, but the drivers fir all supported devices are on board...
Unified works on all tuna variants: maguro, toro and toroplus at same time. It detects your variant on first boot and places needed files. That's the one I'll compile in future too.
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Android-Andi said:
Which rom is the best? Use the power of your TWRP and try it out. Test one, check if it fits your needs. If not, make a backup and try a different rom.
Click to expand...
Click to collapse
I can ask you a different question With all the new ROMs, I don't know which ROM you would like to receive bug reports from. Crash logs, etc. I know there is no point giving you CM12.1 crash logs. Which ROM would you like us testing and reporting bugs from?
Thank you for providing this ROM! I finally found a ROM with a working camera for the Gnex with security patches (from 2017-07).
...anyone gotten Xposed Framework installed/working with this? Halp
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
There's somewhere an updated version flying around on XDA, maybe you'll find it (i don't have it anymore)
JLsoft said:
...anyone gotten Xposed Framework installed/working with this? Halp
Click to expand...
Click to collapse
try this
@Android-Andi is it possible to use this ROM with F2FS file system? Which DDK version is included in this ROM? Thank you for your contribution.
Those who are on 4.4:
AOSP Browser was removed for security reasons. Most lightweight Browser use KitKats webview which isn't up to date any more and there's ATM no proper way to update it.
You should use a browser which has its own webview implementation like Chrome, Firefox or Chromium.
From what I have tested Chromium seems to be a good solution. Here's my self compiled Chromium:
https://github.com/andi34/prebuilt_chromium/raw/master/ChromePublic.apk
(It's only missing h264 encoder for legal reasons...H.264 is not a free codec and I don't have the license for distributing)
For Android 5+
https://github.com/andi34/prebuilt_chromium/raw/master/ChromeModernPublic.apk
For Android 7+
https://github.com/andi34/prebuilt_chromium/raw/master/MonochromePublic.apk
New builds are up.
Switched to default libion, thx to @Ziyan and @amaces !
Note: don't flash any custom kernel on this build (also AnyKernel isn't compatible ATM)!
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
madspeed said:
I've been away from the scene for a while so please catch me up. Does this rom bypass carrier limitations when using usb tether?
Click to expand...
Click to collapse
Yep, these custom ROMs have nothing to do with carriers
March update is online. Enjoy!
Dear developer,
firstable many thanks for your Rom
I was using OMNI 4.4.4 dated 2015 but I was living issue with GMAIL, HANGOUT and GDRIVE
Today I discovered your product and Installed it on my MAGURO with a clean installation
Unfortunately after few hours I am suffering reboot
The system boots well but after few seconds it reboots itself ... continuosly ...
I am using omni_tuna-4.4.4-20180311-1556
I used GAPPS open_gapps-arm-4.4-pico-20180427
I rooted with SUperSU 2.82 R5
I tried to wipe cache, dalvik-cache, system and reinstall the rom and the gapps wo success
I tried to remove root wo success
HAve you some idea to help me ?
Thanks
Paolo
[EDIT]
I wiped all (clean installation) and installed the older version of rom (omni_tuna-4.4.4-20180128-0005)
[I noted that this version is bigger than the newer of around 30MB ...)
Same GAPPS af above
Same root of above
It runs well now ... cross the fingers and stay tuned
People having issues on latest build could try https://forum.xda-developers.com/showpost.php?p=76429699&postcount=188
The request from root was one of my suspect
Do you suggest to flash new kernel after last updated ROM, gapps and root and so before the first boot ?
Do you confirm that this workaround is not necessary with the previous version ?
Are you able to identify which version needs and which didn't ?
For instance I am using the January version .... Did I need to flash new kernel ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Android-Andi said:
It could be it's needed on all KK roms since end of last year. But only works for latest builds using default libion.
Click to expand...
Click to collapse
Excuse my noob ... What does it mean default libion ?
Inviato dal mio Galaxy Nexus utilizzando Tapatalk
This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.
Does this support signature spoofing?
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS
ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom
EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No
TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.
ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.
Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.
Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources
Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?