Long thought to upload his own version of AOSP or not, but still decided.
So version of AOSP Pie with corrections in the device tree from Vartom.
Updated Selinux rules.
Added fixes to drm_hwcomposer.
Applied fixes preventing spam to the kernel log.
Saved device name as Pixel C.
drm_hwcomposer
Device tree
Download -r16
Changes
Corrections in wifi direct.
Cleaning the system from old libraries.
Download -r21
Changes:
-add aptx-hd codec.
Download -r34
Changes:
- Google security updates -> April 2019
- No kernel updates
Download -r35
Changes:
- Google security updates -> May 2019
- kernel updates
disabled kernel lowmemorykiller, enable MEMCG, switch lmkd to userspace.
Download -r39
Download -r42
Changes:
- Google security updates -> March 2020
- in kernel - battery fix/hack
Download AOSP 10-r32
Changes:
- Google security updates -> April 2020
- camera enable( but freeze after a minute of use).
- disabled touchbust for CPU and GPU.
Download AOSP 10-r33
AOSP updates will be in this thread
Full Treble and GSI system on the Dragon
Thanks but no gapps installation is allowed. Error text is about Android 7.1 which is installed.
Alex93917 said:
Thanks but no gapps installation is allowed. Error text is about Android 7.1 which is installed.
Click to expand...
Click to collapse
What gapps have you tried?
I did not have problems installing gapps.
Works great!!
Thank you!!
Mtp can export files ，but cannot import file
Good job
linzinan said:
Mtp can export files ，but cannot import file
Click to expand...
Click to collapse
Once again checked, everything works without errors.
If you have errors, make logs. syslog.
How is it going? Do you reccomend me to update from lineageos 15.1?
AlfreGarcia98 said:
How is it going? Do you reccomend me to update from lineageos 15.1?
Click to expand...
Click to collapse
I did not use lineageos 15.1/16.0, I used the official firmware all the time. After the first versions of Android 9 appeared, I use my versions of AOSP Pie firmware.
Vartom said:
I did not use lineageos 15.1/16.0, I used the official firmware all the time. After the first versions of Android 9 appeared, I use my versions of AOSP Pie firmware.
Click to expand...
Click to collapse
And what would you say? Is it better than stock? How is battery, multitasking going? I'm going to install pie but don't know what rom
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
AlfreGarcia98 said:
And what would you say? Is it better than stock? How is battery, multitasking going? I'm going to install pie but don't know what rom
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Click to expand...
Click to collapse
I wanted to say that I can not make the comparison proposed by you, because I did not use the firmware you specified.
In comparison with the official firmware, I did not find significant advantages for myself. Just an updated version of android. Autonomy in my opinion improved slightly by 1-1.5 hours. Multi-tasking remained at the same level.
thank you
+r34.
Vartom said:
+r34.
Click to expand...
Click to collapse
Thank you for keeping AOSP updated!!!
Sent from my Google Pixel 2 using XDA Labs
Amazing, thank you !!! Our Pixel C still updated
Sorry but I'm a bit lost. Wich one do you think is better, the discontinued pixel experience, this aosp or lineage? Thanks
Enviado desde mi Aquaris E5 mediante Tapatalk
thanks ! from nexus 9 to pixel c , i always use your ROM.
What this hwcomposer update in your OP relate to?
MrPhilo said:
What this hwcomposer update in your OP relate to?
Click to expand...
Click to collapse
I use a slightly modified updated https://github.com/vartom/android_external_drm_hwcomposer/commits/dragon-piev2
Vartom said:
I use a slightly modified updated https://github.com/vartom/android_external_drm_hwcomposer/commits/dragon-piev2
Click to expand...
Click to collapse
Thank you Vartom for your constant and important commitment for the development of Nexus 9 and Pixel C.
This AOSP rom is running really great.
However April version needs more time to load browser pages, Facebook pictures etc. compared to March rom and the previous one.
Maybe is better to perform a fresh install (i am running the rom since November)?
Someone know if restore wizard has been fixed in latest gapps?
Back in October-november you had to skip it and set everything from scratch.
Related
Hi all.
Compatibility:
Builds from r1 up to r12 are for Android 7.1.1 Nougat OxygenOS based roms only.
Builds from r13 are for Android 8.0.0 Oreo OxygenOS based roms only.
Builds starting with r18 work with Android 8.1.0 Custom roms.
Builds starting with r28 up to r32 work with OxygenOS 5.1.0 Android 8.1.0
Builds starting with r33 work with OxygenOS 5.1.5 Android 8.1.0
Builds starting with r40 are for OxygenOS 9.0 Android Pie.
Builds starting with r44 are also available for custom roms such as LineageOS.
Download:
https://francokernel.app
Installation:
Flash the zip in your recovery
or
Auto-flash from FK Kernel Manager app, it's magical
Changelog:
https://francokernel.app
Scroll down, choose your device & select the latest release to see the changelog.
Source:
https://github.com/franciscofranco/OP5-5T-unified
Follow me on socials for updates and interesting tidbits
Twitter[/URL
FK Kernel Manager video
[url]https://www.youtube.com/watch?v=ARdNqh71D0E
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!
Wow nice! For OOS?
As usual there's a large focus on battery life. F2FS is upstreamed to the latest version and I spent a couple days single picking useful commits from Qualcomm's repository with fixes and power consumption improvements.
You should see an improvement in battery life.
Beukhof1 said:
Wow nice! For OOS?
Click to expand...
Click to collapse
Yes.
wowww Franco is here!
25% off sale on FK Manager & Updater for the next 48 hours to celebrate adding One Plus 5 support
https://play.google.com/store/apps/details?id=com.franco.kernel
I'm wait this moment. Thanks FF!
@franciscofranco The king is here!!!!Tnx buddy!!
can it be flash over another custom kernel?
Thank you for supporting Oneplus 5! Using now and it's very smooth.
Just want to report also that the stock screen gestures (double tap to wake, draw O for camera etc) are not working yet
lohaanaa said:
can it be flash over another custom kernel?
Click to expand...
Click to collapse
Nope....first stock kernel...after custom one....
Great work Franco!
After a reboot, the phone boots to default color calibration and it takes like 10-20 seconds to switch to DCI-P3 or SRGB.
PS:Gestures are broken too.
The kernel is systemless?
Sent from ONEPLUS A5000 by Tapatalk
v7 said:
After a reboot, the phone boots to default color calibration and it takes like 10-20 seconds to switch to DCI-P3 or SRGB.
PS:Gestures are broken too.
Click to expand...
Click to collapse
Color calibration did not reset for me. Working fine. But Gestures don't work when screen is off.
I don't see the discount price for the Manager & Updater in the PlayStore.
Edit: price already updated in the store
@franciscofranco
fsync seems to be causing issues for me. With fsync disabled some apps fc after being cleared and some other work fine. After reenableing fsync everything returns to normal.
I´am running the latest stock rom with the only modificatiion being your kernel and magisk.
here is a short vid. of it in action: https://gfycat.com/MemorableMemorableCaecilian
logcat (sorry its quite huge ) https://www.dropbox.com/s/w2rbudldqw3ofvr/log.txt?dl=0
AlfalfaX said:
fsync seems to be causing issues for me. With fsync disabled some apps fc after being cleared and some other work fine. After reenableing fsync everything returns to normal.
I´am running the latest stock rom with the only modificatiion being your kernel and magisk.
here is a short vid. of it in action: https://gfycat.com/MemorableMemorableCaecilian
Click to expand...
Click to collapse
Grab a logcat.
Nice, I missed you (used Franco on my 3T). Already have the app, but nice for new users with discount :highfive:
Nice thanks
lohaanaa said:
can it be flash over another custom kernel?
Click to expand...
Click to collapse
Flash full zip. Let it boot. Boot back too twrp then flash kernel
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
Hey there,
good news for everyone who is missing the great JDC Nougat!
With smeroni68's authorization I'm offering you the latest version of the ROM, built from source, with some changes to keeping it up to date and maintained.
These changes are:
Latest security bulletins and changes from AOSPKernel upstreams from Linux StableUpdates from Code Aurora Forum (CAF)Some smallish modifications of standard apps or behavior
All credit goes to the JDC team!
(Check attachment for a list of team members).
They are the geniuses behind this awesome ROM and kernel, and I'm only making basic and minor modifications to it.
Besides a huge thanks to each member of the JDC team, thanks to Google, Lineage, Linux, CAF, Github & everyone else involved!
And many thanks also to DennySPB who helped me a lot with all the building stuff!
Have fun and enjoy!
Downloads
ROM / Kernel
Hashes
Recommended firmware
Last and latest Oreo firmware for our Mi 5:
8.11.22
ROM installation
Install latest TWRP
Make backups and store them externally
Wipe dalvik, cache, system, vendor, data
When coming from any android version other than Nougat 7.1.2:
Make external backups of your internal storage content
Format data (type "yes" way)
Reboot to recovery to access the data partition correctly again
Flash adequate firmware
No reboot in between the following and the optional steps
Flash ROM
Optionally:
Flash Gapps for 7.1.x arm64. I recommend OpenGapps Pico with additions (1) OR Stock with gapps-config.txt file (2):
(1) Flash Gapps additions (for example these by @Deltadroid)
(2) Check post_#128
Flash ThemeReady GApps package for Nougat arm64 (I don't)
Flash root (Latest Magisk is working fine for me)
After the first boot
Follow the gapps assistant (in case you installed gapps)
Wait 2 - 5 minutes to let everything settle in
Reboot to system
Kernel installation
You'll only wanna install the kernel separately when there's a kernel-only update later than the last ROM version!
Wipe dalvik and cache
Flash the kernel zip-file
Optionally: Re-flash root (if you were rooted before or now wanna be rooted)
GPL
All repos are forked from AOSP-JF-MM or LineageOS
Device tree source code:
https://github.com/PhilSmith31/platform_device_xiaomi_gemini/tree/aosp-7.1.2_r36
Kernel source code:
https://github.com/PhilSmith31/platform_kernel_xiaomi_msm8996/tree/bb
XDA:DevDB Information
AOSP, ROM for the Xiaomi Mi 5
Contributors
Phil_Smith
Source Code: https://github.com/PhilSmith31
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: 8.1.18
Based On: AOSP
Version Information
Status: Stable
Created 2018-08-28
Last Updated 2020-03-20
Changelogs
20.03.2020
March 2020 security updates from LineageOS
Synced Lineage repos
Kernel is up to date with relevant commits to android/common
02.03.2020
Security bulletins up to Februrary 2020 (no more source.android updates coming from here on)
Updated everything in aosp.xml to latest android tag r39
Updated HALs and all externals under CAF to tag LA.UM.5.5.c25-04600-8x96.0
Upstreamed kernel with all changes to android/common up to date
Merged LA.UM.5.5.c25-04600-8x96.0 into qcacld-2.0
Synced Lineage repos
Kicked opencv
Kernel compiled with latest Linaro toolchain 7.5.0
17.09.2019
ROM:
Security updates from August and September 2019
Merged in CAF tag LA.UM.5.5.c25-03100-8x96.0 into externals, hals, and some vendors
Synced system/gatekeeper with LOS
Kernel:
B--B-Kernel-N-[2019-09-17]-[20:17]-Mi5
From now on always also present in kernel_only folder
Cherry-picked all relevant aosp's kernel/common/android-3.18 commits up to date
Merged in security related changes from aosp
Merged CAF tag LA.UM.5.5.c25-03100-8x96.0 into qcacld-2.0
Wrote simple python script to filter out warnings from compile output
Check extract_warnings.py and changes to build_kernel.sh
Vendor/aosp:
Monitor changelog under Dropbox link only
all changelogs
.
FAQ
I'm having general problems with the ROM installation or don't know what steps to perform to move from x to y or to restore or undo z. What shall I do, Dr. Phil?
Dr. Dr. Phil said:
First read the intro and then see whether your problem is covered here:
Standard Installation Types
Still issues? Then feel free to post in this thread!
Click to expand...
Click to collapse
Gcam mod has green lines in portrait mode or even in general
Dr. Dr. Phil said:
Settings -> advanced -> Fix Camera API2 -> support level override
and set it to "Zsl reprocessing"
Click to expand...
Click to collapse
Gcam mod video recording is force closing all the time.
Dr. Dr. Phil said:
This problem is present in Arnova's cam versions > 8, while photo shooting is working fine with the support level override fix above. You could use stock camera for video recording or use Arnova's gcam mod in versions 7.9 till 8.
Click to expand...
Click to collapse
Proximity sensor lets the screen get black while making a phone call
Dr. Dr. Phil said:
Use the recommended firmware (Oreo 8.11.22).
If that doesn't help, here is a fix that I used once successfully when I had the same problem.
Thanks to Mi5 Arsenal!:
flash zcx twrp
make a backup of your persist partition (let's call that x)
store x externally in case the fix shouldn't work or make anything worse (which I don't believe, but still)
download this zip file and place it where x had been stored (replace x with it)
hit restore in twrp, and select the new backup file you just put in place where x was
reboot to system
You can switch to official twrp afterwards without any problem!
Click to expand...
Click to collapse
Xposed isn't working or producing issues, what to do?
Dr. Dr. Phil said:
In my experience, xposed is very powerful, but can produce all kinds of weird and untraceable behaviour.
I don't recommend using it if not completely nessecary, and cannot support it.
Click to expand...
Click to collapse
Reserved
Hi mate... thanks for your dedication on our work!
Inviato dal mio Xiaomi Mi5 utilizzando Tapatalk
This is exactly what I was looking for N Rom with latest patches:laugh: .Ty so much for your work, will try it soon. :laugh:
What is for boot.img?
XxFatiHxX said:
What is for boot.img?
Click to expand...
Click to collapse
Just so you could flash back stock kernel separately.
Nothing you need for the ROM installation.
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
ERRORR2 said:
Thanks for this great work! Can I dirty flash it on latest original JDC nougat? And can I flash B-B Kernel or better not to do this?
Click to expand...
Click to collapse
You should be able to dirty flash, although I think that a clean flash is advisable.
B-B-kernel should be working, but keep in mind that I am gonna keep updating the stock kernel and the B-B one is getting more and more outdated.
Edit:
This info is outdated!
B--B-kernel is even built into the ROM now!
The ol' but gold rom has waken up from long sleep
This rom is eas or hmp ?
Kyru said:
This rom is eas or hmp ?
Click to expand...
Click to collapse
EAS
Phil_Smith said:
EAS
Click to expand...
Click to collapse
Will it work with latest beta firmware ?
Will try soon
Kyru said:
Will it work with latest beta firmware ?
Click to expand...
Click to collapse
I would suggest Nougat-based firmware, but maybe on Oreo-based everything is working as well - can't say.
You need to try that out (on your own risk).
Thanks very much @Phil_Smith
Finally.. must try this one.. thanks @Phil_Smith
I can't believe this is perfect.
Can you add more status bar customizations?
Does alarm from switched off work with this rom?
Inviato dal mio MI 5 utilizzando Tapatalk
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Gemini forever alive!
Download:
TWRP with 4.4 kernel
LineageOS 17.1
Installation:
If you are on stock TWRP you need to flash 4.4 to avoid any problems like /data corruption!
You need to perform a factory reset (format /data)!
Flash rom, gapps/microG and optionally magisk.
Known bugs:
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Join Mi5 group on Telegram
Please consider donating to my hard work
https://paypal.me/xNombre
XDA:DevDB Information
Enchanted LineageOS 17.1 with 4.4 kernel, ROM for the Xiaomi Mi 5
Contributors
xNombre
Source Code: https://github.com/xNombre
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2020-01-06
Last Updated 2020-04-02
Reserved
Antutu Score
Reserved
¯\_(ツ)_/¯
Thanks for your hard work
hi
tanx 4 ur hard work
i want know about battery life plz..
install instruction?
and best frimware?
tanx
Can not change battery icon style it is stuck on Icon Portrait.
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
do we need jdc treble for this or what? since it "treble"
What about battery life?
can i flash other android 10 gsi based on this rom since it "treble"
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
nebik said:
Can not change battery icon style it is stuck on Icon Portrait.
Click to expand...
Click to collapse
It's LOS bug.
3V0LU710N said:
Hi @xNombre, just 2 quick questions regarding the the kernel used in your LOS release:
1- Does the kernel support HW Encryption? I remember on Havoc 2.9 (Android P) there was a port of 4.4 kernel with working HW crypto.
2- Will you release a standalone package of the infinity kernel in the future that can be used with other ROMs?
Thanks!
Click to expand...
Click to collapse
1. AFAIR not yet because it's not merged on LOS.
2. Probably no because there are too many custom changes made (dt & vendor) and I don't like listening to moaning that something is broken. I want to release more interesting ROMs some day (Syb... uhh ekh... eria).
shandianex1 said:
can i flash other android 10 gsi based on this rom since it "treble"
Click to expand...
Click to collapse
Hmmm, that's interesting question. I've only focused on making it fulfill all Android Q requirements concerning vendor separation (and such as APEX), not intended to make it GSI friendly. I guess there are still some incompabilities and you can't expect such and old device to be GSI friendly.
jackryder38 said:
What about battery life?
Click to expand...
Click to collapse
Test yourself, the biggest culprit about I can do nothing more is RIL. Maybe when Xiaomi releases Q for daisy, the blobs will make it better.
RmznDndr said:
immediately banned from telegram group right after joined. not even wrote a message or got a warning. interesting way to manage a community group.
i'll be around for feedbacks. thanks for your effort anyways.
Click to expand...
Click to collapse
The group is protected with antibot, I've checked your nickname and youre not banned for sure.
Enchanted LineageOS updated!
Changelog:
Merge latest kernel_common and CAF tag into kernel
Merge latest branch into qcacld driver
Use fq_codel queuing discipline, faster net
Update some blobs (those I have access to) from LA.UM.8.6.r1-02900-89xx.0
Remove unused move time data script
Add missing wifi mac generator
Fix USB tethering
Uprev Mapper to 2.1
Tweak Dalvik parameters accroding to new google configs
Go back to stock WiFi config and add some new Xiaomi edits - fixes connectivity problems
Rootdir updates
Minor cleanup
Fixup microG location
Massive overlay update from LA.UM.8.6.r1-02900-89xx.0
Selinux enforcing
Safetynet PASS!!!
Important LOS updates:
Fixed battery style
Updated to android 10.0 r23
Added survival script (magisk reflashes itself)
Repo sync all
Download via sf:
https://sourceforge.net/projects/xn...-17.1-20200119-UNOFFICIAL-gemini.zip/download
Please consider donating...
https://paypal.me/xNombre
xNombre said:
Enchanted LineageOS 17.1 with 4.4 Infinity EAS Kernel
Known bugs:
Speaker playing only left channel
5GHz hotspot
Camera hang in Snap when switching to HDR (click back button and open camera again, boom, it's working)
Click to expand...
Click to collapse
Fixed?
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
nebik said:
Camera still hangs on HDR on/off. 5Ghz Hotspot works and about speaker i do not know.
Click to expand...
Click to collapse
Use this Gcam
https://easyupload.io/5ms9tu
It's version 7.2 - optimized and working 100% on gemini
PavelPerm said:
Fixed?
Click to expand...
Click to collapse
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
xNombre said:
Not listed so not fixes, I thought it's clear.
New build could have some problems due to selinux change (dt2w or so) and I will push hotfix when I can.
Click to expand...
Click to collapse
I have problem with permission name (icon != Permission name)
I want to share the good news.
Some time ago, with the help of several "hacks", we managed to launch support for GSI ARM 64-bit, AB systems.
This solution works no worse than existing AOSP 10 or LOS17.1 firmware.
Images ARM 64-bit, AB system GSI can be found here. https://forum.xda-developers.com/project-treble
Tested several systems LOS 17.1, PIXEL 10.
Download Boot+vendor for GSI ver. 0501
Download Boot+vendor+system for GSI ver. 0501 + fingerprint
Download Boot+vendor+system for GSI ver. 0625 + camera fix
Download Boot+vendor+system for GSI ver. 0807 + Wi-Fi QR code
Download Boot+vendor+system for GSI ver. 1007
Installation:
Flash boot,
flash vendor,
flash GSI system,
Run.
Current developers
@Vartom, @michie.
If someone wants to connect to the project and help bring the project to perfection, write.
Links to the sources modified for the GSI.
drm_hwcomposer
Kernel
Device branch aosp-10GSI
P.S.
You can use any available Kernel for Pixel C.
If BT does not work or the phone application crashes constantly, install another GSI system.
You can update the system yourself without waiting for the release of an updated version of the vendor section. The vendor section containing drivers in our case has practically not been updated for several years.
Vartom said:
Perhaps in a hurry to create a topic, but I want to share the good news.
Some time ago, with the help of several hacks, we managed to launch support for GSI ARM 64-bit, AB systems.
This solution is not perfect yet.
Hw video acceleration does not work.
Images ARM 64-bit, AB system GSI can be found here. https://forum.xda-developers.com/project-treble
Tested several systems LOS 17.1, PIXEL.
Download Boot+vendor for GSI
Installation:
Flash boot,
flash vendor,
flash GSI system,
Run.
Current developers
@Vartom, @michie.
If someone wants to connect to the project and help bring the project to perfection, write.
Links to the sources modified for the GSI will be in the near future, since now they are still under development.
drm_hwcomposer
Kernel
Device
Click to expand...
Click to collapse
I work with michie or we playerd [emoji41].
i was the one asking you for kernel 4.9 porting for future build. Can we also work together on bringing Kernel 4.9 to smaug? Maybee we can use then newer blobs from cmshield?
Gesendet von meinem Pixel 2 XL mit Tapatalk
@vatom whitch vendor blobs you use? This from @followmsi or this on your github? Whitch branch?
Do you use your android_external_drmhwcomposer or michies modified one?
Is your device tree uptodate? No ld.config.vndk_lite.txt mount/bind in init.dragon.rc? Only this few treble settings in boardconfig.mk?
Why no cam shim lib needed?
Cheers
Thomas
Gesendet von meinem Pixel 2 XL mit Tapatalk
tschmid said:
@vatom whitch vendor blobs you use? This from @followmsi or this on your github? Whitch branch?
Do you use your android_external_drmhwcomposer or michies modified one?
Is your device tree uptodate? No ld.config.vndk_lite.txt mount/bind in init.dragon.rc? Only this few treble settings in boardconfig.mk?
Why no cam shim lib needed?
Cheers
Thomas
Gesendet von meinem Pixel 2 XL mit Tapatalk
Click to expand...
Click to collapse
whitch vendor blobs you use? I use a mixture of those that MoKee and followmsi have with my additions.
Do you use your android_external_drmhwcomposer or michies modified one? I use the branch that showed plus the addition of libsync to android.mk Updated branch
Is your device tree uptodate? Updated device branch
No ld.config.vndk_lite.txt mount/bind in init.dragon.rc? Bind is used.
Only this few treble settings in boardconfig.mk? Yes, there are only a few changes.
Why no cam shim lib needed? This is a hex editing library camera.
HW video acceleration fixed and working.
Download Boot+vendor for GSI ver. 0426
Vartom said:
HW video acceleration fixed and working.
Download Boot+vendor for GSI ver. 0426
Click to expand...
Click to collapse
Do you have any clue how to fix camera Fence part? Libshim doest work any more, and the fence Change was also in los16
Gesendet von meinem Pixel 2 XL mit Tapatalk
Ps. Do you have bluetooth working?
I can connect to headphone and keyboard with my built
PS2: do you know if magisk can work with Treble?
tschmid said:
Do you have any clue how to fix camera Fence part? Libshim doest work any more, and the fence Change was also in los16
Gesendet von meinem Pixel 2 XL mit Tapatalk
Ps. Do you have bluetooth working?
I can connect to headphone and keyboard with my built
PS2: do you know if magisk can work with Treble?
Click to expand...
Click to collapse
BT works, Magisk also works.
First time trying GSI ROMs... To be clear:
- first I had to wipe/factory reset from TWRP (for example)
- from bootloader flash vendor.img and boot.img
- then flash GSI ROM from bootloader?? I see AOSP in https://github.com/phhusson/treble_experimentations/releases for example system-quack-arm64-ab-gapps.img.xz
So I need to flash system from bootloader again and that's it?
Thank you for this work Vartom!
jolinnard said:
First time trying GSI ROMs... To be clear:
- first I had to wipe/factory reset from TWRP (for example)
- from bootloader flash vendor.img and boot.img
- then flash GSI ROM from bootloader?? I see AOSP in https://github.com/phhusson/treble_experimentations/releases for example system-quack-arm64-ab-gapps.img.xz
So I need to flash system from bootloader again and that's it?
Thank you for this work Vartom!
Click to expand...
Click to collapse
Yes that's right. You can also flash the system from twrp.
Do not forget to extract the system image from the archive.
Awesome work!
Sent from my Pixel 4 using Tapatalk
AptX fixed.
Download Boot+vendor for GSI ver. 0501
Vartom said:
AptX fixed.
Download Boot+vendor for GSI ver. 0501
Click to expand...
Click to collapse
Thanks @Vartom
Vartom said:
AptX fixed.
Download Boot+vendor for GSI ver. 0501
Click to expand...
Click to collapse
Thanks Vartom. Flashed today with phh's AOSP. All seems perfect. Great job!
Does the GSI image I choose set the default rotation?
For example are all the GSI portrait by default like phones are? I am hoping I can keep default landscape.
locuturus said:
Does the GSI image I choose set the default rotation?
For example are all the GSI portrait by default like phones are? I am hoping I can keep default landscape.
Click to expand...
Click to collapse
phh's AOSP is landscape. Don't know others.
I'm thinking of trying this. Is it simple to go back to a normal pixel c rom after? Just a case of re-flashing through twrp?
Thanks
narse said:
I'm thinking of trying this. Is it simple to go back to a normal pixel c rom after? Just a case of re-flashing through twrp?
Thanks
Click to expand...
Click to collapse
Yes, everything stays the same. You will see a message of android that your device has an error at start of the OS but you can just press ok and ignore it. This error comes on all devices with unofficial treble. Enjoy!
michie said:
Yes, everything stays the same. You will see a message of android that your device has an error at start of the OS but you can just press ok and ignore it. This error comes on all devices with unofficial treble. Enjoy!
Click to expand...
Click to collapse
Thanks, I tried 2 roms and installed using the following process:
Boot to TWRP
Factory Reset
Apply Boot image
Apply Vendor image
Apply System image (extracted from archive file)
Boot
I tried both the AOSP and the Lineage 17 and both boot and seem to work well. However I did find little issues with both that made me go back to the Pixel C Lineage 17.
The AOSP includes Gapps, but for some reason I couldn't use the Gmail app. It prompted me to specify my email login, but wouldn't use the Gmail account that was already being used for all the other Gapps.
The Lineage 17 rom again seemed really good, but I guess because the System partition is cut in half for AB, I couldn't install the Gapps using the installer in TWRP.
Finally, to confirm that going back to a "normal" rom was really easy, just factory reset and installed the rom from TWRP as usual.
Really impressed though, looking forward to development on the GSI roms.
Vartom said:
AptX fixed.
Download Boot+vendor for GSI ver. 0501
Click to expand...
Click to collapse
Pls push vendor sources too.
Thanks for (all) your work !
narse said:
The AOSP includes Gapps, but for some reason I couldn't use the Gmail app. It prompted me to specify my email login, but wouldn't use the Gmail account that was already being used for all the other Gapps.
Click to expand...
Click to collapse
That's because your device is not certified by Google. I tried to fix like I did with the previous AOSP ROM, but can't. I used the same script and tricks to change fingerprint to the last certified by Google...