Oreo - Mission impossible? [8.1.0_r46][6Oct2018] OmniROM-8.1 - K3 Note Original Android Development

Oreo - Mission impossible?
I started studying "O" in early August. All I got were the O-preview3 factory images for qcom and tegra devices which I don't have. Built it out and made it boot wouldn't be too hard but everything seemed different. It took me some time to figure out the flow of the new frameworks. At that time, only the RIL and Graphics sources were really "O". The most devastated situation would be the RIL. Seemed dead end at that time. That was the first time I feel impossible. The source from MTK's RIL made things even worse. All the .c functions are buried inside prebuilt static libraries. Frankly, up to this moment, I'm still not fully understand the workflow of MTK's RIL...
While I was struggling with the RIL, "O" - Oreo was launched. The most helpful info. were also released in source.android.com. Sadly, I can't access this website no more... Never take it for granted for anything. You can loose anything/anyone for no reason. The sources were then completed and took me some times to made it boot "again".
Eventually, I can make the RIL almost fully working recently. Yes!:victory: All I can say is, we are lucky. Our RIL blobs only experience a few crashes which I can managed. I had tried five or six sets of blobs for different MTK chips. Each had different crashes so there is no guarantee that all MTK devices might work...
Last week, I finally figure out how to made the camera work. Seems not "impossible" now so I start this new thread.
I can't start a DevDB now. The response from XDA official is "They can't think of obvious reason". Anyway, I pay for ad-free and still the status shows connection to axx.amazon-adsystem.com. It just hang there for minutes (until timeout I suppose). However, I can start a normal thread (after minutes of delay) and that's not a problem to me. I already learnt to live with so many obstructions now. :cyclops:
There were just too many distractions and ridiculous people out there. I don't want to waste time arguing so I would make it short this time. I rather spend time on something I'm good at.
For those who want help, no matter its ROM related or about development, please don't use PM. There are many limitations with PM. Do it formally. Start a thread in Q/A or post with all the details you can get (log, kmsg, screenshot, etc.). It's no harm for more opinions. Hiding in the dark doesn't help.
Current Status
KERNEL
Patch: Binder and sdcardfs update are required and essential for Oreo.
See commits in my github for detail
AUDIO
Recording: Working
Playback: Working
Patch: Load a copy of the struct instead of the pointer to address.
BLUETOOTH
Working
Issue: Workflow issue in BTIF driver.
Patch: New driver and HAL build from source.
CAMERA
Flash/Torch: Working
Capture: Working
Issue: User handle is required in GetMemory. MTK blobs return null.
Patch: Save a copy of the user handle. Don't know if other devices might work or not. It's better to rebuild a few blobs but I don't have the source for my device...
Issue: Oreo use a ring buffer of native_handles and no more ANativeWindowBuffer.
Patch: A wrapper is required for the libcam.client. (The better way would be rebuild it but again no source...)
HDR: Working with Snap in LOS-15.1
Video recording: Working
Issue: Oreo doesn't support GRALLOC (or I don't know how). The old HAL1 implementation doesn't work too.
In short, need to find a way for the metadata that our old blobs can handled.
Patch:
1. Add libcamera_parameters_mtk for the MTK extra parameters
2. Add another mode to handle Gralloc in stragefright.
3. Patch the OMXNode to handle Gralloc mode.
4. patch the OMXClient to use mediaserver
5. Patch the hardware interface to handle Gralloc Metadata and work with the new OMX interface.
DISPLAY/TOUCH SCREEN
DT2W: Working
FM RADIO
Working
GPS
AGPS: Working
GPS & BEIDOU: Working
GLONASS: Enabled by default
GRAPHIS
HWC: Working
Issue: Android platform changed
Patch: A simple patch in libgui_ext (might use shim if timestamp proved no use)
OpenGL: Working
LED
Notifications: Working
Charging: Working
Low power: Not Working
See Post #806 for detail. Haven't study why --pending
MEDIA
Video Playback: Working
Hardware decoder: Working
Issue: crashed
Patch: A small patch in minijail use Asan.
POWER
Power off charging: Working
RIL
Phone calls: Working
Mobile Data: Working
SMS: Working
Dual SIM: Working
Issue: Completely new approach in Oreo with interface/services. No more sockets. AND all .c libraries are proprietaries.
Patches:
1. Replace the MTK RIL daemon with AOSP patching for MTK
2. Wrap (eventually replaced) the libril from MTK with AOSP patching for MTK
3. Patch the RIL interface/service to work with the MTK vendor library.
Some more detail can be found in post #65 and post #806
SENSORS
All sensors are Working
Patch: Lower the requirement from 1.3 to 1.0
WIFI
ap,p2p: Working
Miracast: Working
Noted: only work on 2.4G as before
Hotspot: Working
Hidden SSID: Not support
No idea why yet. --pending
Sources
Github
Download :highfive:
Experimental: AndroidFileHost
OmniROM: AndroidFileHost, 百度网盘
LineageOS-15.1: AndroidFileHost, 百度网盘
Install :fingers-crossed:
Flash with the latest TWRP
1. Factory reset
2. Flash ROM
3. Flash SuperSU (tested ver.2.82)
4. Reboot and setup wifi
5. Flash Gapps (tested opengapps 8.1)
Change Log
Code:
[B][COLOR="Blue"]2018/10/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r46 (OPM4.171019.030.K1)
- New build enviornment
- Security patch Sep. 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/8/11[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r42 (OPM4.171019.021.Y1)
- OmniLib is updated
- Security patch Aug. 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/7/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r36 (OPM2.171026.006.H1)
- SELinux Enforcing
- Security patch July 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/6/26[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r30 (OPM2.171026.006.C1)
- SELinux Enforcing
- Add/Fix SEPolicy rules for GPS, camera, Video, etc.
- Security patch June 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/6/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r32 (OPM4.171019.021.E1)
- OmniLib is updated
- A few bug fix in Omni Apps
- Security patch June 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/5/18[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r28 (OPM4.171019.029.B1)
- Security patch May 5, 2018
- chromium-webview update[/INDENT]
[B][COLOR="Blue"]2018/5/11[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r26 (OPM2.171019.029.B1)
- Security patch May 5, 2018[/INDENT]
[B][COLOR="Blue"]2018/4/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- fix vendor image mismatch warning
- fix a few security issues in reading NVRam
- chromium-webview update[/INDENT]
[B][COLOR="Blue"]2018/4/13[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- Security patch Apr. 5, 2018
- adjust some memory defaults
- handle the build flags for MTK devices (to live with other devices in the same source)[/INDENT]
[B][COLOR="Blue"]2018/4/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r20 (OPM2.171019.029)
- Security patch Apr. 5, 2018
- HDR broken in this build. Check [URL="https://forum.xda-developers.com/showpost.php?p=76174760&postcount=612"]post #612[/URL] for the fix patch[/INDENT]
[B][COLOR="Blue"]2018/3/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r15 (OPM1.171019.021)
- Add Device Features support in OmniGears
- Device Features: Display Color Adjustment is added[/INDENT]
[B][COLOR="Blue"]2018/3/9[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r15 (OPM1.171019.021)
- Workaround for Proximity sensor in InCall screen
- Settings: LiveDisplay is supported now[/INDENT]
[B][COLOR="Blue"]2018/3/2[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- The patch for codec and power off charging animation included
- Workaround for Proximity sensor in InCall screen
- HDR support with Snap porting to OmniROM[/INDENT]
[B][COLOR="Blue"]2018/2/21[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR] 15.1[/B]
[INDENT]- The latest LineageOS 15.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- All previous fixes in Omni-8.1
- HDR support with Snap port
- Patch for MTK soft codec[/INDENT]
[B][COLOR="Blue"]2018/2/16[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r11 (OPM1.171019.018)
- Fix Lockscreen settings
- Minor patch in video recording to make it more stable
- update codec conifg
- check [URL="https://forum.xda-developers.com/showpost.php?p=75609953&postcount=338"]post 338[/URL] for the codec and power off charging animation patch[/INDENT]
[B][COLOR="Blue"]2018/2/6[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Source is sync to the latest Omni-8.1
- userdebug build.
- Native Video recording is fixed. [COLOR="Red"][B]Edit[/B][/COLOR]: check [URL="https://forum.xda-developers.com/showpost.php?p=75488295&postcount=273"]post #273[/URL] for the camera patch
- Phonograph and equalizer are also fixed.
- MP3 and FLAC can be played now.
- GPS: Enable GLONASS by default [/INDENT]
[B][COLOR="Blue"]2018/1/21[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Security patch Jan. 5, 2018
- Add Messaging apk
- Add FM radio apk
- Add the forgotten vibration support
- RIL: Fix a bug in carrier info.
- Clean up the internal log I added. [/INDENT]
[B][COLOR="Blue"]2018/1/7[/COLOR] - [COLOR="YellowGreen"]OmniROM[/COLOR] 8.1[/B]
[INDENT]- The latest OmniROM 8.1 source, Android-8.1.0_r7 (OPM3.171019.013)
- Initial release
- Security patch Jan. 5, 2018
- New Bluetooth driver and HAL.
- Kerenl: a few minor patches[/INDENT]
[B][COLOR="Blue"]2017/12/30[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.1[/B]
[INDENT]- The latest Carbon CR-6.1 source, Android-8.1.0_r1 (OPM1.171019.011)
- Cumulated patches from LOS-15.0
- Security patch Dec. 5, 2017[/INDENT]
[B][COLOR="Blue"]2017/12/22[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
[INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
- libsuspend: add earlysuspend support
- Kernel: tidy up lenovo features source
- DT2W: working now[/INDENT]
[B][COLOR="Blue"]2017/11/20[/COLOR] - [COLOR="Teal"]LineageOS[/COLOR]-15.0[/B]
[INDENT]- The latest LOS-15.0 source, Android-8.0.0_r30 (OPR3.170623.013)
- Kernel: remove obsolete Lenovo features
- Mediaplayer: fix video playback
- Camera: Add mode to handle MetaDataGralloc in video recording. (only audio working now...) WIP[/INDENT]
[B][COLOR="Blue"]2017/10/23[/COLOR] - [COLOR="Black"]CarbonROM[/COLOR] CR-6.0[/B]
[INDENT]- The latest Carbon CR-6.0 source, Android-8.0.0_r15 (OPR3.170623.008)
- Alpha test build[/INDENT]
Known Issues
- May be a few...​
Donations :angel:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Huge respect.

Subscribed to this thread. I am unable to provide any help for now and will start using the Oreo build as soon as it can do the basic stuff for daily use (despite the bugs).
I appreciate all your efforts bro. Many people are reading you. When you release something that can be a buggy daily version I can start giving feedback. For now I will just read because my K3 is my only device.

Huge respect.
bugs-deep sleep mode,proximite-Vanillamusic not work,JetAudio-work

Any Mission is possible with you :laugh:

Thank You for developing. Please provide us a stable rom ASAP

Thanks
Daniel, you're one of the hardest working developers I've ever encountered. Many would perceive this device as a dead device but you're the one who gives a new life to this, keep up your amazing work and if you need anything we're all here for you.

Updated
@daniel_hk
The carbon is SICK man!
I can report that apart from the known issues, there's:
1. Unable to install apps when rooted. Solved by flashing magisk in TWRP, then clearing Data, Cache and Dalvik. Also dirty flashing from nougat will recovery-loop your phone!! . Always clean flash your rom guys
2. Some mp4s can be played yet some shows "can't play this video" error. I can't be sure whether it's the decoder or just the mp4 s.
3. All tried mp3s can be played only after flashing the codec you provided here :silly:
4. Camera can perform photo taking and very poor video recording using 3rd party apps. Maybe the handling of the 3rd party apps enabled them to connect to the sensor.
5. After flashing GApps, there are two Android Shared Library 1 as system apps . No force close or conflict encountered though.
6. Battery drain just a little too fast. Didn't encounter that before with android 7 but maybe it's the kernel or Oreo policies itself.
7. Proximity sensor is nonexistent. Used sensor box to check with no avail. It said that the phone's hardware does not support the sensor.
8. Used google camera's HDR+ feature with successfull result, sort of. Snap and stock camera freezes right after snapping HDR with no avail.
I made this post to help those who are trying to learn and appreciate Oreo.
I'm new to this community. Hope to help as best as I can. Overall, the rom is enough for me as daily drive for now :good:. If I find anything more I'll be sure to share them here. Maybe just need to figure out the deep sleep bug for now.

How to install this rom. can anyone pls tell me the procedure how to install this rom, so that i don't find my phone in bootloop.

Why Oero, not Oreo? ?

bedoedeyne said:
Why Oero, not Oreo? ?
Click to expand...
Click to collapse
Brother, I know he done typo mistake but we are respectful to him because he is working hard to give us Oreo update. You can show his typo mistake without laughing on him.

Ashwinrg said:
Brother, I know he done typo mistake but we are respectful to him because he is working hard to give us Oreo update. You can show his typo mistake without laughing on him.
Click to expand...
Click to collapse
Oh no bro. I always respect him :fingers-crossed:
But you can look at his avatar and that word. It made me smile

sudip_55 said:
How to install this rom. can anyone pls tell me the procedure how to install this rom, so that i don't find my phone in bootloop.
Click to expand...
Click to collapse
You should rather go to @daniel_hk 's thread for Nougat. He said if you aren't familiar with the procedure, you aren't ready for this and I wouldn't recommend trying to install it if you are afraid of breaking your phone.
- Aresmo

Updated bug and workarounds
Hey guys I've updated my list of bugs and workarounds here. Be sure to read it before installing this ROM just so you don't brick your phone :silly: .
I created the post to help those who want to learn and appreciate Oreo

Arjunism said:
Hey guys I've updated my list of bugs and workarounds here. Be sure to read it before installing this ROM just so you don't brick your phone :silly: .
I created the post to help those who want to learn and appreciate Oreo
Click to expand...
Click to collapse
Hi arjun thanks for the bug list and apart from that can you please tell me the installation steps how to install this rom in the phone so that the phone doesn't go into bootloop.

sudip_55 said:
Hi arjun thanks for the bug list and apart from that can you please tell me the installation steps how to install this rom in the phone so that the phone doesn't go into bootloop.
Click to expand...
Click to collapse
Go to custom recovery (TWRP Recommanded) click on wipe and advanced wipe. Tick on dalvik/art cache, cache, data and system and swipe to format. Click on install and navigate to rom zip that you want to install. Select and swipe to flash.

Hey guys I am in need of stable ROM for few days ..
I always flash the latest ROM available but I have to go for holidays any feature pack ROM that you can you guys can recommend please

Go for aosp 4.6 official from blitzfire.
For Oreo video recording use camu app its working

Hi daniel
No any new thing about O

Very much looking forward to android O Coming .
thanks your hard work!

Related

[ROM] [ 8.0.0 | 8.1.0 ] Official madOS - Jiayu S3 [MT6752]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Official Build of madOS ( based on AOSP 8.1.0 Oreo ) for Jiayu S3 (Adv./Basic/Pro) with MTK 6752 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Installation Instructions:
Download ROM from M.A.D. Facebook
OR via xda DevDB
Download madOS Unofficial OpenGapps nano or pico from Download Page
(We had built, pico and nano 8.1.0 GAPPS only )
Backup
Flash new mandatory new Oreo 8.1.0 TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Reboot System
DO NOT: Flash any rooting zips (SuperSU or Magisk) on the first flash, together with rom
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth (calls, media, file transfer, etc)
FM Radio
All Sensors
Lights; HW Keys
Both storages & MTP
HW de/encoding
Camera (photos only)
GPS & aGPS
Audio
NFC ( available only on the advance/PRO versions)
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
Native Video Recording
---> However works just fine with camera apps that use SW de/en coding (i.e.: Footej Camera available at PLAY)
XDA:DevDB Information
[ROM] [ 8.0.0 | 8.1.0 ] Official madOS - Jiayu S3 [MT6752], ROM for the JiaYu S3
Contributors
superdragonpt, DerTeufel1980, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Oreo TWRP / LP layout
Based On: madOS
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-11-18
Created 2017-11-18
Last Updated 2017-12-24
FAQ
General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
(edit April 2018)
A: Latest M.A.D. TWRP 3.2.1-0 recovery for the Jiayu s3 OREO 8.1.0
--> Check xda Download Section
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file (LP rom layout)
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: New TWRP fails on wiping, why ?
A: You need to go TWRP Settings> Select the option
"Use rm -rf instead of formating"
Update madOS April 2018:
New TWRP is fully working now, no more need of this workaround
Native wiping of both ext4/f2fs is working and twrp is faster then ever
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
You can only use f2fs on cache & data (backup your stuff, as it'll be all erased)
Q: is the Data connection issue of going to / from 4G still present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixs
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: My Jiayu s3 Basic (the 2GB RAM Version), shows "NFC has stopped"
A: The 2GB version, doesn't have NFC, however in the last NFC updates we did, this is now showing, as an workaround:
Go to TWRP:
Mount /system
Go advance>file manager
Navigate to /system/app/ and delete the NFC app, this should fix your NFC service force closing while on boot
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 )
NOTE: magisk v15, v16 aren't working (don't spam me, im not the magisk developer
2: Super SU ( v2.82 onwards)
NOTE: v2.82 or even latest beta of 2.82 will work fine
after flashing it, you need to go on the SuperSU.zip and install the management app
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo on the Jiayu?
A: Pretty awesome
Q: Does this build support Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A:OpenGapps arm64 nano/mini
Since there's no Official GAPPS for 8.1.0 just yet...
... we had built OpenGapps nano and pico versions
--> Check Download Section
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...
Changelogs / madOS Features
Changelogs
[Stable] Build [8.0.0] 20171118
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.10.108 ( Oreo branch)
[Stable] Build [8.1.0] 20171224
First Release of Oreo 8.1.0
madOS version: 2.1 (O 8.1.0 )
Patch Level: 8.1.0 [OPM1] 2017-12-05,
Between the new Oreo 8.1.0 & madOS bug fixs & device fixs , there is an huge changelog,
... so im narrowing this to bare minimum this time
main changes:
All mad extras stuff is now fixed (fastcharge/ weather/ sensors calibration, performance settings, etc, etc)
Theme engine:
This started as an feature from AOSPA on Nougat (and has been depricated ever since... )
* We forward port to Oreo 8.0.0, and now to 8.1.0
* We extended theme engine to per-apps (currently madLauncher; messaging, etc)
* And added way too many fixs on top of it
exfat and ntfs are now properly supported
Bluetooth Calls fixed
New Sensors HAL
New RIL
Playback fixed (Youtube, whatsApp, etc)
---> ETC
MARRY XMAS !
[Stable] Build [8.1.0] 20171230
Audio: Fix couple issues introduced by me, on last build
Audio "media bug": work was made on this matter, hopefully it's gone
UI / UX : improvements
HWC / SF: many fixs & Enhanced for 8.1.0
Video / Playback: More Video Playback improvements
FM Radio: couple issues adressed
Mem Leaks adressed (introduced on 8.1.0)
Flashlight : some issues where adressed
Bluetooth: more work done on A2DP & car-BT
NFC: better compatibility with TAG reading & MTK protocols & device specific FW
Other small things: Update APNs, etc ...
madOS color Engine:
Rebased & Many improvements on the engine
Extended / better support per-apps (messaging; Launcher,etc)
Extended /better support to theme PowerMenu
Better support on theming Quick Settings
Option to override default Google 8.1.0 QS theming
Easy reset button to get back to default
"MAD Mode" If you use Live Wallpapers... this is awesome ;p
Other stuff..
[Stable] Build [8.1.0] 20180417
Android 8.1.0 release 20
Patch level April 2018
madOS version: 2.1.3
Doze / Ambient settings:
Hand-Wave Gesture
ambient lockscreen weather, etc
New hardware settings (some functions are WIP for 6752)
Custom header image provider improvements
powermenu: cleanup and fix
expanded desktop settings
visualizer settings
increase default maximum password length
option to toggle torch by longpressing power button (with screen off)
Optimize multithread installation for apps
Removed Chromium in favor of Jelly
(to allow future costumizations, also way less space)
JNINativeMethod improvemensts
HWCAdapter Improvements ( Google you suck!)
Tight up security by requiring unlocking to access tiles
hide sensitive information while locked by default
Bring back less notification sounds
Weather update & fixs
dual-sim ringtone support
Setting: increasing ringtone
Settings: unlink notification volume is back
Settings : Option to enable searchpanel, including Navigation Ring Targets
OMS: fixs , upstream
Disable persistent Mobile data by default
AppOps: is back
screenrecord is here
Slim Recents: Fixed & updated to v3.0
smartwake fixs
fling and velocity settingsSettings
poor man battery style tweaks
carrierlable settings fixs
searchpanel: properly implement switches
Settings : Slimified CM Navigation Ring Targets
Fix up secure lockscreen (pattern, pin, etc)
Keyguard: Forward port lockscreen quick unlock
Secure Settings: Option to scramble pin layout on unlocking
Quick settings revamped:
Quick settings background: allow changing alpha
tiles
new features
etc
New usb settings:
deny_new_usb setting
usb configuration
USB default config
colorengine:
colorengine: fix tinting of unruly dashboard icons
colorengine: fix themed conditions and suggestions
color engine: add adv settings fragment
color engine per-apps extended ( messaging, madlauncher, etc)
wallpaper based theme switch
other stuff
AndroidRuntime crashs fixs, etc
madOS: Our cookie is finnaly here !!!
Add support for page theme color to WebView and WebChromeClient
New rebuilt modem baseband ( hybrid ) feedback is welcome
Bluetooth fixs
NFC: rebuilt proprietary mtk blobs from upstream
Ril improvements
many other stuff...
TWRP:
Updated to v 3.2.1-0
Fixed native format
many other improvements
Twrp will be auto-updated during the rom flashing
[Stable] Build [8.1.0] 20180422
Audio: Fully rebuilt & sound is now max out (max values supported by the device)
Media Bug: New approach (hopefully this is fully fixed now)
Some frameworks and some other small fixs
Changes added since previous build (forgot to add on the already huge changelog)
Camera: Improved quality ( photos )
madWallpapers added ( pics from FB contest winners)
[Stable] Build [8.1.0] 20190722
Fixed critical bug where device would enter in infinite bootloop to twrp
secure lock screen improvements
Media codec improvement
RIL ( telephony) improvements
increase Magisk compatibility
General clean up
Reserved
Can I flash with f2fs or must format as ext4?
We can almost see it, you can almost touch it, in a very short time we can all install it
Thanks for your work.
Link to TWRP is fine,
Waiting for the Rom link, active and downloading...
Marc
All up
bb
it is UP yeaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaahhhhhhh thanks mad installing
finally
Have fun!
Yeahhhhh Thank you dragon, thank you MAD
Today is a historical day. :silly:
When a 2015's phone receive Android 8.
Neither OnePlus 5T came with 8 in time xD
Lez gooo!
Thank you all MAD people, it's flashing time
fantastic work phone runs too fast too smooth great. that team aproove that everything can become. the only mad feature that i miss or i cant find it is the quick unlock when correct pin ented well done team i think that is time for us to donate that team
edit also there is not battery settings in statusbar icon/text...
sokolataki said:
fantastic work phone runs too fast too smooth great. that team aproove that everything can become. the only mad feature that i miss or i cant find it is the quick unlock when correct pin ented well done team i think that is time for us to donate that team
Click to expand...
Click to collapse
@fire855: you should have merged this [emoji14]
Sent from my uhans h5000, running Android 8.0.0
Thank you mad team...
I'm trying to install it but I have some problems.
First I installed new Recovery but version is the same as previous: 3.1.1-0 ¿¿??
Then, when trying to wipe all partitions I get the following errors:
mke2fs -t ext4 -m 0 /dev/block/mmcblk0p18 process ended with signal: 6
Unable to wipe Cache
Unable to wipe /cache​
If I try to flash the ROM, then I get these errors:
E1001: Failed to update system image
Updater process ended with ERROR: 7​
Some idea?
Thks
Try to flash the new twrp first, but after choosing the image I have to fill in a partition.
What have I to choose there for flashing the new twrp
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
I'm so happy for the moment with many gin tonic intus
chabula said:
Try to flash the new twrp first, but after choosing the image I have to fill in a partition.
What have I to choose there for flashing the new twrp
Click to expand...
Click to collapse
Could you please elaborate your answer?
What do you mean when saying 'I have to fill in a partition' ?

[Treble][ARM64][AOSP][J701X]Project_Spaget X

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X​
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed. or github issues section. as those are not mine to fix. i only provide the vendor and kernel that allows GSIs to run on.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Spaget. Treble ARM64 Vendor, ROM for the Samsung Galaxy J7
Contributors
ananjaser1211, corsicanu, Astrako
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-07-31
Last Updated 2020-01-13
Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8
F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J701 device
Very nice job as always, keep up the good work
Error
ananjaser1211 said:
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J701 device
Click to expand...
Click to collapse
After flashing create vendor file I flash Exynos7870_ProjectSpaget_V3.0. Zip file it shows symlink fail and error 7 . So I cannot flash any rom or gsi image plz help me ..... please make a correct vendor for j7 nxt and solve symlink error or also tell how to download gsi in j7 nxt step by step.......... please please . I download A64_A_20191205.img gsi for this process.... plz solve this isssue
---------- Post added at 05:29 PM ---------- Previous post was at 05:11 PM ----------
Technical Star09 said:
After flashing create vendor file I flash Exynos7870_ProjectSpaget_V3.0. Zip file it shows symlink fail and error 7 . So I cannot flash any rom or gsi image plz help me ..... please make a correct vendor for j7 nxt and solve symlink error or also tell how to download gsi in j7 nxt step by step.......... please please . I download A64_A_20191205.img gsi for this process.... plz solve this isssue
Click to expand...
Click to collapse
And tell me which rom I use for gsi
Technical Star09 said:
After flashing create vendor file I flash Exynos7870_ProjectSpaget_V3.0. Zip file it shows symlink fail and error 7 . So I cannot flash any rom or gsi image plz help me ..... please make a correct vendor for j7 nxt and solve symlink error or also tell how to download gsi in j7 nxt step by step.......... please please . I download A64_A_20191205.img gsi for this process.... plz solve this isssue
---------- Post added at 05:29 PM ---------- Previous post was at 05:11 PM ----------
And tell me which rom I use for gsi
Click to expand...
Click to collapse
because you flashed a rom before that changed your partitions, H ROM or so. you need to revert to stock partitions using pit file. instructions on how to do that are written in the documentation and our group
i use pixel experience
Request
ananjaser1211 said:
because you flashed a rom before that changed your partitions, H ROM or so. you need to revert to stock partitions using pit file. instructions on how to do that are written in the documentation and our group
i use pixel experience
Click to expand...
Click to collapse
Give me chat link and pit file link plz I cannot install any gsi ....
I did the steps that you wrote, all was well but when i try to boot, it stucks at black screen. What should i do now?
Error
I have error
I am flash exynos 7870 vendor creador but afther apear
Can't mount vendor partition afther flashing project spaget v3 :crying:
Using j701m device, some solution or something i'm wrong
which version of trwp should you use,something additional must be installed
Sorry for bad english, GSI file is compatible
How to match device requirements?
ananjaser1211 said:
Q: Device requirements ?
A : you MUST be on an OREO Bootloader and Modem, otherwise you will have trouble
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : Any GSI that is ARM64_AONLY is supported [8/9/10]
Click to expand...
Click to collapse
How do I get the oreo bootloader and modem. I did the steps mentioned in the 1st thread and I was able to boot the different gsi roms I tried but after a few seconds after boot I got System IU errors and the phone frozen. maybe is the bootloader. Thanks.
Pixel Experience not working mic
Jukmisael said:
Pixel Experience not working mic
Click to expand...
Click to collapse
Very good work, thank you.Can't install Xposed,it's not supported?
I'm on oreo aosip rom
Can i use this project without pit file?
Dialer and video not working in any gsi
Camera aslo not working in mostly gsi roms
Qorgeous project, I trudge.Thank the Creator!!!
When will the camera be fixed?
Getting error msg after booting fr the first time!!
I have used "pixel experience" gsi on my sm-j701f . After first boot of this rom i getting error msg frm several apps like "Messenger is not responding" . The rom feels too much laggy for my device. I have no idea about the reason of this prblm. Any solution for this????? i have also used other gsis like aosp and havoc os. None of them worked fr me. Getting error messages on this rom too.
Give me solution please???
Recovery
Best Project Great Job
Great project, thanks to the Creator, but there is one serious question: Footej Camera the weakest link(constantly defocused when shooting video, it's just annoying) is it possible to adapt some other camera, such as Open Camera?

[ROM][unlocked][douglas] Lineage-12.1 [5 SEP 2020]

Disclaimer:
Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
LineageOS needs no introductions. This version of LineageOS-12.1 is a highly customised version solely for the Amazon Fire HD8 2017
WARNING: You need to be unlocked: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846
LineageOS 14.1 thread: https://forum.xda-developers.com/hd8-hd10/orig-development/unlocked-lineage-14-1-t4195349
Known Issues:
- Video recording
Installation:
- Boot to TWRP
- Format data
- Wipe data, system, cache
- Install the ROM
- Install G-APPS (optional)
- Reboot
- Enjoy the ROM
Prerequisites:
- Unlocked BL
- TWRP
Downloads:
Lineage-12.1 for the Amazon Fire HD8 2017
Source Code:
Device tree: https://github.com/CM12-1-Douglas/android_device_amazon_douglas
ROM Source: https://github.com/cm12-amami
Kernel: https://github.com/douglas-development/android_kernel_amazon_douglas/tree/cm-12.1
Thanks to:
- @MSe1969 for the up to date cm-12.1 sources
- @k4y0z and @xyz` for the bootloader hack
- yos-two for the mt8163 proprietary libs
- LineageOS
XDA:DevDB Information
LineageOS 12.1 Amazon Fire HD8 2017, ROM for the Amazon Fire HD 8 and HD 10
Contributors
Rortiz2, t0x1cSH, beefy1986, Kaijones23, k4y0z, ggow, xyz
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Fire OS
Based On: Cyanogenmod
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2019-09-13
Created 2019-09-13
Last Updated 2020-09-13
Changelog
2020-09-05
Updated Security Patches to August 2020.
Synced with LineageOS sources (cm-12.1 amami).
2020-05-14
Update security patches to May 2020.
Updated Vendor Blobs to the latest FireOS release (update-kindle-50.6.5.4_user_654620520.bin).
Enable USB Dock in the Kernel (thanks @novatillo).
Synced with LineageOS sources (cm-12.1 amami).
Switch back to default fingerprint.
Fixed MicroG signature spoofing.
2020-03-27
Update security patches to March 2020
Fix md32 data path (Should improve battery life)
Fix EGL_BAD_DISPLAY.
Some Unity Games seems to be working on this build (Monument Valley 2, etc)
Synced with LineageOS 12.1 sources (cm-12.1 amami)
2020-03-15
Fixed low memory killer in the kernel. Fixes the lag. (Thanks @novatillo)!
Synced with cm-12.1 amami sources.
Switched to Google Nexus 10 fingerprint. (SafetyNet).
2020-02-27
Fixed crash on some games (Mostly based on unity. Donut Maker, Toca Kitchen, etc...).
Synced with cm-12.1 amami sources.
Security patches of February.
Updated blobs to 5.3.7.0.
Reworked vendor tree.
2020-01-10
Sync with LineageOS (cm-12.1 amami) sources.
Fixed headphones. Thanks to @spelcheck and @t0x1cSH.
Kernel built with GCC 9.
2019-12-14
Added MicroG compatibility
December Security Patches.
LineageOS Updates.
Upstream to 3.18.140. (Thanks to @novatillo)
2019-10-26
Fixed webview crash
2019-10-22
October security patches.
2019-10-11
Fix swapped volume keys.
Upstream to 3.18.32.
Switch to latest fingerprint from Amazon FW.
2019-09-14
Build memtrack from MTK Sources.
Build lights from MTK Sources.
Upstream to 3.18.21+.
Enable lz4 compression in kernel.
2019-09-13
Initial Release
Reserved!
Reserved
Excellent work guys!! I am so excited to finally have stock android on my tablet. I have been following the root progress ever since I got in when it was brand new. Can't wait to install this!
EDIT: Just installed it. I love it so far! It's very nice having a stock android experience on this wonderful tablet. IMHO it seems speeder but it may just be because there's not as many apps because I had allot, but overall, great work!
other than the stuff outlined above everything else works right?
and is it possible that the headphones are an easy fix
Working perfect thanks for your work, and for anyone wondering what Gapps to flash use arm64-5.1-nano
Works fantastic. Thank you!!
i tried it and its fine but its really slow with 5g internet and magisk's hide feature doesn't work
is it possible to return it to stock?
This is great! Thank you very much! I've been waiting for this since I bought this tablet
mileyrock said:
other than the stuff outlined above everything else works right?
and is it possible that the headphones are an easy fix
Click to expand...
Click to collapse
Wired headphones is a known bug in mt81xx amazon based tablets. It needs modifications in kernel source so it's not really easy to fix, it can take some time.
Also we tested the ROM and we only noticed that issues but there can be more.
Regards.
mileyrock said:
is it possible to return it to stock?
Click to expand...
Click to collapse
You should be able to return to FireOS by flashing update.bin tought TWRP.
Regards.
Thank you, I'm very happy and surprised to see this!
qbikashgurung said:
Thank you, I'm very happy and surprised to see this!
Click to expand...
Click to collapse
Remember that @t0x1cSH fixed almost all the bugs so give him tanks too.
Glad that you enjoy the ROM.
Crosby87mvp said:
Working perfect thanks for your work, and for anyone wondering what Gapps to flash use arm64-5.1-nano
Click to expand...
Click to collapse
@Rortiz2 congratz on getting it to work. I don't have my tablet for a few days, but am looking to forward to trying it out.
Also based on the above quote, the ROM is 64 bit?!? That's awesome.
Is there a plan to make the Karnak ROM 64 bit in the future?
Kctucka said:
@Rortiz2 congratz on getting it to work. I don't have my tablet for a few days, but am looking to forward to trying it out.
Also based on the above quote, the ROM is 64 bit?!? That's awesome.
Is there a plan to make the Karnak ROM 64 bit in the future?
Click to expand...
Click to collapse
The ROM is 64 bit because stock FireOS is it too.
No, it's impossible to boot a 64 bit OS on a device without proprietary 64 libs.
Regards.
New build is up
Build memtrack from source for get rid of logcat spam.
Build lights from source.
Upstreamed kernel to 3.18.21+.
Added lz4 compression to kernel.
Rortiz2 said:
Build memtrack from source for get rid of logcat spam.
Build lights from source.
Upstreamed kernel to 3.18.21+.
Added lz4 compression to kernel.
Click to expand...
Click to collapse
@Rortiz2 Are you working on the Headphone Issue? How long it will take? It's the only thing that's keeping me away from the Rom. I consume a lot of media using wired headphones.
Anyway, thanks for your hard work!
Just finished installing it, no issue encountered, thanks to you all

[SAR][Vendor][10][A530F/A530W/A730F] Vendor Quack V2.5 For Galaxy A8/A8+ 2018

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here​ If you appreciate the work i have done, and want me to continue working on this projet, Feel free to buy me a cup of coffee @paypal
Introducing Quack Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F​
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
After a battle that took months on end, we have finally Stabled - Vendor Quack for our beloved Galaxy A8/A8+. Ive taken my time With this project and spent more time trying to improve the experience as much as possible.
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
Our device don't have Official ANDROID 10 Support, So this is first ever ANDROID 10 implementation to support AOSP GSI's. This is a fully featured System-as-Root VENDOR and KERNEL designed for this device to support ANDROID 10. Changelog listed below !
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Bluetooth
GPS
Camera
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Device By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Quack.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A/B_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to System
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
None
Credits:
- @TaifAljaloo , @somadsul and @soulr344 for tons of contribution on this project
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Vendor Quack For Galaxy A8/A8+ 2018, ROM for the Samsung Galaxy A8 (2018)
Kernel Sources: https://github.com/prashantpaddune/android_kernel_samsung_jackpotlte
Contributors
prashantp01
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Current Stable Version: v2.5
Current Beta Version: V1
Created 2020-09-02
Last Updated 2020-10-06
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Vendor Quack V2.6 [LATEST] - AOSP GSI
Vendor Quack v2.6 : Gdrive
Generic System Image (list) : Github
Vendor Quack V2.5 - AOSP GSI
Vendor Quack v2.5 : Gdrive
Vendor Quack V2.0 - AOSP GSI
Vendor Quack v2 : Gdrive
Vendor Quack V1.0 - ONEUI / AOSP GSI
Vendor Quack v1 : Gdrive
---------------------------------------------------------------
V2.6
- Fixed Double-tab-to-wake on AOD, thnx to @VDavid003
V2.5
- Fixed Auto-Brightness
- Fixed Always on Display
- Updated Wireless Drivers
- Improved Wifi Mac randomisation
- Fix issues with exFat/vFat Sdcards
- Many other overlay fixes
Quantum Quack v1.0
- Upstreamed Linux 4.4.177
- WireGuard Support
- OC Little to 1.7Ghz
- UC big/Little to 200/500MHz
- DriveDriod Support
- Multi CPU Governors
- Multi I/O Schedulers
- Multi TCP Algorithms
- Wakelock Blocker v1.1
- Power Efficient Workqueue
- Disabled Modules
- Disabled Audit
- Disabled TRACE_PRINTK
- Improved fingerprint wake performance
- Updated new Wakelock list
- Fixed Bluetooth issues on GSI
- StateNotifier
- Fsync Toggle on/off
- Cpumask for BIG and LITTLE CPU clusters
- Security Related Features disabled
and many more....
V2.0
- Fixed Camera
- No longer supports ONEUI
- Supports Android 11 GSI
V1.0
-initial release
F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Do it support Android 11 GSI ?
A : Yes, make sure you download arm64-A/B-vndklite GSI
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, just be sure to wipe vendor when switching to non treble roms
Q : Can i flash any GSIs ?
A : No, only A/B_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above
Hope we see cam fix soon...
Thanks for evolutionary release before Sammy...
This deserves a GGWP. Keep up guys!
thanks for your hard work!
Hey, great effort!
One question. Right now I have to install A-only arm64 ROMs but to install this Quack ONE UI ROM I the install A/B arm64 variant?
Does that mean that I have to install the SaR patch and kernel for Pie Vendor ?
Tnks for this rom .Plz fix cam
mementomorinl said:
One question. Right now I have to install A-only arm64 ROMs but to install this Quack ONE UI ROM I the install A/B arm64 variant?
Click to expand...
Click to collapse
After installing this vendor, you'll need A/B (well, not really a/b but it's labelled like that) GSIs.
mementomorinl said:
Does that mean that I have to install the SaR patch and kernel for Pie Vendor ?
Click to expand...
Click to collapse
No, that's for the Pie vendor.
mementomorinl said:
Hey, great effort!
One question. Right now I have to install A-only arm64 ROMs but to install this Quack ONE UI ROM I the install A/B arm64 variant?
Does that mean that I have to install the SaR patch and kernel for Pie Vendor ?
Click to expand...
Click to collapse
No, you have to use only the files which are there on this thread
prashantp01 said:
If you appreciate the work i have done, and want me to continue working on this projet, Feel free to buy me a cup of coffee @paypal
Click to expand...
Click to collapse
hishem said:
Tnks for this rom .Plz fix cam
Click to expand...
Click to collapse
Thanks for your work ! I'll try asap
Very nice job!
:good: Respect! Just a question, does Volte and Vowifi work like on stock Pie rom?
theleogetz said:
:good: Respect! Just a question, does Volte and Vowifi work like on stock Pie rom?
Click to expand...
Click to collapse
Nope!
Thanks!
Unfotunatelly, Volte will be important in the future as a lot of carrier will stop or already stopped to provide mobilenet on 3G, only voice... So if somebody calls somebody then no internet during calls (sometimes it is needed like Waze)... But a solution could be Viber, Whatsapp etc...)
theleogetz said:
Unfotunatelly, Volte will be important in the future as a lot of carrier will stop or already stopped to provide mobilenet on 3G, only voice... So if somebody calls somebody then no internet during calls (sometimes it is needed like Waze)... But a solution could be Viber, Whatsapp etc...)
Click to expand...
Click to collapse
4g works, just enable LTE from network settings, VoLTE related stuffs will never work on AOSP, as we have exynos
To prashantp01
Man, I wanna work on the project too. We have to steal some kernel extensions from the A-only GSI Vendor as OpenGL, Vulkan are somewhat broken and camera is not working. The OneUI 2.0 GSI does see the phone as a Galaxy M20 and therefore not allowing for Always On Display, a feature that can't be missing, and that is the case due to the Galaxy M20 being a TFT LCD phone, not a OLED one... I don't quite know what you did, since I cannot boot with modified build.prop, to report the right phone model, the right hardware version, and the right CPU, since there is Exynos 7885 in the A8, and not the Exynos 7904. Anyway, I would like to work on the project. Maybe we get OneUI 2.5 on this thing and get the OpenGL (which is buggy - runs Minecraft @18fPS when it should exceed 50, and Dolphin crashes instantly) and Vulkan (which is not supported at all in this vendor) to work properly.
dosdoktor said:
Man, I wanna work on the project too. We have to steal some kernel extensions from the A-only GSI Vendor as OpenGL, Vulkan are somewhat broken and camera is not working. The OneUI 2.0 GSI does see the phone as a Galaxy M20 and therefore not allowing for Always On Display, a feature that can't be missing, and that is the case due to the Galaxy M20 being a TFT LCD phone, not a OLED one... I don't quite know what you did, since I cannot boot with modified build.prop, to report the right phone model, the right hardware version, and the right CPU, since there is Exynos 7885 in the A8, and not the Exynos 7904. Anyway, I would like to work on the project. Maybe we get OneUI 2.5 on this thing and get the OpenGL (which is buggy - runs Minecraft @18fPS when it should exceed 50, and Dolphin crashes instantly) and Vulkan (which is not supported at all in this vendor) to work properly.
Click to expand...
Click to collapse
Well i have fixed everything, even camera will release when i'm free NO ETA
Waiting eagerly...
How much will we have to wait? Is there anything we can do ourselves?
I don't quite like to see one doing the whole work by himself, so I would like to help. What's left to do? I have a linux machine set up and a phone to test modifications step by step. All I need is to know which modifications to add to current vendor build (I really need the good OpenGL+ Vulkan libraries).

[ROM] [13.0] [davinci] LineageOS 20 [UNOFFICIAL][OTA]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS 20 is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on AOSP with contributions from many people within the Android community. It can be used without any need to have any Google application installed. If needed you can install any GApps package available for T.
LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for LineageOS is available at GitHub. And if you would like to contribute to Lineage OS, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
make a FULL backup first from your actual system and data;
before installing make sure you are running the latest firmware for your region;
Clean install:
download the latest ROM zip and GApps (optional) from the downloads section below;
wipe system, cache, dalvik and do a factory reset in recovery if coming from another AOSP based rom (including other LineageOS 19/20)
install ROM zip + add install more zip's and flash also GApps (optional), thus you get best integration of vanilla LineageOS with GApps;
install as recovery the latest fbev1 TWRP recovery [twrp_13.img];
format /data (from wipe option) - the option which requires you to type "yes";
this is required due to encryption changes.
reboot to system and enjoy latest LineageOS 20 [Android 13] on your Redmi K20 / Xiaomi Mi 9T.
Note: if you enable Lineage recovery option during setup you will lose TWRP (overwrite by Lineage recovery app)
Upgrade [dirty flash]:
download the latest ROM zip from the downloads section below;
install ROM zip;
wipe cache, dalvik - optional;
reboot to system;
Downloads:
rom: LineageOS 20
gapps: MindTheGapps or NikGapps
recovery: TWRP
Reporting bugs:
Bug reports without a complete description of the issue and a logcat will be ignored!
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Credits:
ArianK16a for initial DT & Kernel
LineageOS Team & Contributors
Code Aurora Forum
Redmi K20 / Xiaomi Mi 9T contributors
GPL compliance: Kernel source
XDA: DevDB Information
[ROM] [13.0] [davinci] LineageOS 20 [UNOFFICIAL] ROM for Redmi K20 / Xiaomi Mi 9T
Contributors:
raul16
Donations:
donations are not mandatory but very welcomed
if you like my work and want to support development or buy me a coffee PayPal Donate
ROM OS Version: Android 13.0.0_r20
ROM Kernel: Linux 4.14.x
ROM Firmware Required: V12.5.2.0.RFJCNXM / V12.1.4.0.RFJMIXM / V12.1.4.0.RFJINXM
Based On: LineageOS 20
Version Information
Status: Stable
Created on 2023-01-12
Last Updated 2023-06-22
Screeshots:
Spoiler: LineageOS 20 davinci changelog
Redmi K20 | Xiaomi Mi 9T
Changelog:
**********************
June 20, 2023
**********************
- June 2023 Security patch + QPR3
- LOS upgrade to A13_r52 build TQ3A.230605.012
**********************
June 14, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.318)
- Add kernel vibration control support
**********************
June 9, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.317)
- Fix GPS build warnings/errors
- Implement xtra-daemon control via property
- Remove all permissions from 'serial_number'
- Add Lineage Charging Control
**********************
June 5, 2023
**********************
- Add no_sehash_xattr mount option
- Apply ASB-2023-06-05 Qualcomm CVE-2023-21656, CVE-2023-21657
- Optimize & cleanup device code
**********************
May 31, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.316) (ASB-2023-06-05)
- Update architecture
**********************
May 18, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.315)
- Enable VDP on IMS
**********************
May 4, 2023
**********************
- May 2023 Security patch
- LOS upgrade to A13_r43 build TQ2A.230505.002
- optimize blur in framework
- Merge tags 'LA.UM.9.1.r1-13500-SMxxx0.QSSI13.0'
**********************
Apr 27, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.314)
- Add power menu blurs
- Improve prop utils spoof for CTS
**********************
Apr 26, 2023
**********************
- Add Transparent QS feature
- Enable blurs
- Add hotword enrollment [OKGoogle]
- Drop Soundtrigger
**********************
Apr 21, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.313)
- Import missing ADSP modules
- Adress sepolicy denials
- Fixup wpa supplicant service init
- Patch ims.apk from sweet V14.0.1.0.TKFMIXM
**********************
Apr 19, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.312)
- Device add vendor missing OMX blobs
- Device add vendor missing IMS blob
- Build OMX missing libs
- Enable media player wave/shimmering effects
**********************
Apr 16, 2023
**********************
- April 2023 Security patch
- LOS upgrade to A13_r41 build TQ2A.230405.003.E1
- Update Adreno from LA.UM.9.14.r1-21000-LAHAINA.QSSI13.0
**********************
Apr 15, 2023
**********************
- Upstream kernel to android-4.14-stable
- Device vendor fixes
**********************
Apr 11, 2023
**********************
- Upstream kernel to android-4.14-stable
- Various device clean-ups & fixes
- Enable 24 bit audio output
**********************
Apr 6, 2023
**********************
- Upstream kernel to android-4.14-stable (ASB-2023-04-05_4.14-stable)
- Merge tags 'LA.UM.9.1.r1-13400-SMxxx0.QSSI12.0'
- Merge tags 'LA.UM.9.1.r1-13100-SMxxx0.QSSI13.0'
**********************
Mar 30, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.311)
**********************
Mar 26, 2023
**********************
- Bring back Lineage fonts, icon pack & shape customizations
- Drop 2-button navigation [switched to 3-button navigation automatically]
- Various system fixes / optimizations after AOSP QPR2 merge
- Require unlocking to use sensitive QS tiles
- Enable LTE+ icon
- Add burnin protection
**********************
Mar 17, 2023
**********************
- March 2023 Security patch
- Android 13 QPR2
- LOS upgrade to A13_r35 build TQ2A.230305.008.C1
**********************
Mar 14, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.309)
**********************
Mar 8, 2023
**********************
- Update vendor blobs from V14.0.2.0.TKFEUXM
- Revert to Lights HIDL [fix notification LED]
- Specify kernel FCM version
**********************
Feb 26, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.307) (ASB-2023-03-05_4.14-stable)
- device fixes
**********************
Feb 23, 2023
**********************
- Upstream kernel to android-4.14-stable (tag 4.14.306)
- Set default USB, BT & hotspot SSID based on ro.boot.hwc
- Add three-fingers-swipe screenshot
**********************
Feb 13, 2023
**********************
- Update vendor blobs from V14.0.1.0.TKFEUXM
- Update vendor SPL to Feb 01, 2023
**********************
Feb 9, 2023
**********************
- Make CTS/Play Integrity pass again
**********************
Feb 8, 2023
**********************
- February 2023 Security patch
- LOS upgrade to A13_r30 build TQ1A.230205.002
- apply ASB-2023-02-05_4.14-stable
- upstream kernel to android-4.14-stable (tag 4.14.305)
**********************
Feb 7, 2023
**********************
- Update Adreno from LA.UM.9.14.r1-20200-LAHAINA.QSSI13.0
- Add Snapdragon Computer Vision Engine stack
- Add Neural Networks stack
- Update Adreno from LA.UM.9.14.r1-19300-LAHAINA.QSSI12.0
**********************
Feb 2, 2023
**********************
- enable OTA for davinci
- enable suspend to RAM
- add touch improvements props
- various device optimizations
**********************
Jan 31, 2023
**********************
- update vendor security patch level
- upstream kernel to android-4.14-stable (tag 4.14.304)
- merge tags 'LA.UM.9.1.r1-13000-SMxxx0.QSSI13.0'
**********************
Jan 27, 2023
**********************
- uprev manifests to level 5
- uprev various HAL's
- move Lights, DRM to AIDL
- enable SafetyNet pass
- fix wifi overlays
- various device optimizations
- enable VoWIFI in airplane mode
- fix ViLTE camera
- device cleanup & optimize for A13
- update vendor blobs to V13.0.15.0.SKFMIXM
**********************
Jan 12, 2023
**********************
- January 2023 Security patch
- LOS upgrade to A13_r20 build TQ1A.230105.001.A2
- lineage davinci initial build
👨‍🔧️ maintainer: raul16
build: monthly
🍦️ type: vanilla
📱️ version: lineage-20
solved. thanks!
After successfully installing the system and gapps everything seems to work fine except google play store stops installing any app. Tried clearing cache, rebooting etc. Had to switch to different rom as thats a deal breaker. Other than that nice and smooth.
angeltomik said:
After successfully installing the system and gapps everything seems to work fine except google play store stops installing any app. Tried clearing cache, rebooting etc. Had to switch to different rom as thats a deal breaker. Other than that nice and smooth.
Click to expand...
Click to collapse
What TWRP have you used to flash ?
raul16 said:
View attachment 5822893
LineageOS 20 is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
Disclaimer:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on AOSP with contributions from many people within the Android community. It can be used without any need to have any Google application installed. If needed you can install any GApps package available for T.
LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for LineageOS is available at GitHub. And if you would like to contribute to Lineage OS, please visit Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
make a FULL backup first from your actual system and data;
before installing make sure you are running the latest firmware for your region;
Clean install:
download the latest ROM zip and GApps (optional) from the downloads section below;
wipe system, cache, dalvik and do a factory reset in recovery if coming from another AOSP based rom (including other LineageOS 19/20)
install ROM zip + add install more zip's and flash also GApps (optional), thus you get best integration of vanilla LineageOS with GApps;
install as recovery the latest fbev1 TWRP recovery [twrp_13.img];
format /data (from wipe option) - the option which requires you to type "yes";
this is required due to encryption changes.
reboot to system and enjoy latest LineageOS 20 [Android 13] on your Redmi K20 / Xiaomi Mi 9T.
Note: if you enable Lineage recovery option during setup you will lose TWRP (overwrite by Lineage recovery app)
Upgrade [dirty flash]:
download the latest ROM zip from the downloads section below;
install ROM zip;
wipe cache, dalvik - optional;
reboot to system;
Downloads:
rom: LineageOS 20
gapps: MindTheGapps or NikGapps
recovery: TWRP
Reporting bugs:
Bug reports without a complete description of the issue and a logcat will be ignored!
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Credits:
ArianK16a for initial DT & Kernel
LineageOS Team & Contributors
Code Aurora Forum
Redmi K20 / Xiaomi Mi 9T contributors
GPL compliance: Kernel source
XDA: DevDB Information
[ROM] [13.0] [davinci] LineageOS 20 [UNOFFICIAL] ROM for Redmi K20 / Xiaomi Mi 9T
Contributors:
raul16
Donations:
donations are not mandatory but very welcomed
if you like my work and want to support development or buy me a coffee PayPal Donate
ROM OS Version: Android 13.0.0_r20
ROM Kernel: Linux 4.14.x
ROM Firmware Required: V12.5.2.0.RFJCNXM / V12.1.4.0.RFJMIXM / V12.1.4.0.RFJINXM
Based On: LineageOS 20
Version Information
Status: Stable
Created on 2023-01-12
Last Updated 2023-01-27
Click to expand...
Click to collapse
Dear Raul,
Thanks for this LOS 20 ROM. After reading the Clean Flash instructions, wanted to know (1) if we don't need to Wipe Data along with Dalvik, Cache & System. and (2) if we need to flash the latest global stable firmware of Redmi K20 or not. Since in all other ROMs, this needs to be done. Kindly clarify soon since want to try your ROM soon. Thanks again.
Msharu73 said:
Dear Raul,
Thanks for this LOS 20 ROM. After reading the Clean Flash instructions, wanted to know (1) if we don't need to Wipe Data along with Dalvik, Cache & System. and (2) if we need to flash the latest global stable firmware of Redmi K20 or not. Since in all other ROMs, this needs to be done. Kindly clarify soon since want to try your ROM soon. Thanks again.
Click to expand...
Click to collapse
(1) for clean install you must format data not wipe, after flash ROM, before you boot to system;
(2) you have to be on latest firmware for your region
all these are stated in the Instruction section
new build lineage-20.0-20230209-UNOFFICIAL-davinci.zip
February 2023 Security patch
Make CTS/Play Integrity pass again
LOS upgrade to A13_r30 build TQ1A.230205.002
apply ASB-2023-02-05_4.14-stable
upstream kernel to android-4.14-stable (tag 4.14.305)
Update Adreno from LA.UM.9.14.r1-20200-LAHAINA.QSSI13.0
Add Snapdragon Computer Vision Engine stack
Add Neural Networks stack
Update Adreno from LA.UM.9.14.r1-19300-LAHAINA.QSSI12.0
enable OTA for davinci
enable suspend to RAM
add touch improvements props
various device optimizations
Note: OTA enabled will notify & upload starting next release.
THX @raul16 for your work here.
I need MicroG. Is it possible to install microG with your LOS 20 rom? Would it survive a ota-update?
I_did_it_just_tmrrow said:
THX @raul16 for your work here.
I need MicroG. Is it possible to install microG with your LOS 20 rom? Would it survive a ota-update?
Click to expand...
Click to collapse
no support for microG included.
it is vanilla LineageOS + patches to pass SN when recommended GMS is installed so bank apps & wallet works OK.
raul16 said:
no support for microG included.
it is vanilla LineageOS + patches to pass SN when recommended GMS is installed so bank apps & wallet works OK.
Click to expand...
Click to collapse
Okay, I will checkout https://forum.xda-developers.com/t/...ied-tirimbino-stable-official-microg.4557455/ for now.
microG had this repo for building it. Can I use your sourcecode with it to build my own microG-LOS20 or did miss something? https://github.com/lineageos4microg/docker-lineage-cicd
I_did_it_just_tmrrow said:
microG had this repo for building it. Can I use your sourcecode with it to build my own microG-LOS20 or did miss something? https://github.com/lineageos4microg/docker-lineage-cicd
Click to expand...
Click to collapse
sources are open so glhf; idk about microG.
I will back up my phone and give it a try. My phone is actually running the latest arian vanilla build for the Mi 9T with MindTheGapps and Magisk installed. Therefore I am hoping to successfully try dirty flashing that thing
Dirty flash worked flawlessly coming from vanilla arian 20.0, many thanks, have a coffee good sir looking forward to real OTA updates again
@raul16 It seems like Arian released another update for davinci LOS20. Do you integrate his latest changes in your next release, too? What's your plan?
sffoxy said:
@raul16 It seems like Arian released another update for davinci LOS20. Do you integrate his latest changes in your next release, too? What's your plan?
Click to expand...
Click to collapse
actually they were already included in the current build from 230209.
next build, once AOSP ASB March will become available, will contain even more goodies - under test now - picked from other distributions. Like '3 finger swipe for screen shot" option taken from MIUI (!) and others that will be announced when version released.
also all vendor blobs updated to latest Xiaomi release 14.0.2.0.TKFEUXM.
I'm building LOS20 for Davinci to my personal flavor/use and share it for anyone to use it if want/like.
Sounds nice!
But to be precise I meant the current and latest changes:
https://raw.githubusercontent.com/arian-ota/changelog/lineage-20/davinci_gms.txt
They seem to be newer than the february build could have included.
sffoxy said:
Sounds nice!
But to be precise I meant the current and latest changes:
https://raw.githubusercontent.com/arian-ota/changelog/lineage-20/davinci_gms.txt
They seem to be newer than the february build could have included.
Click to expand...
Click to collapse
i meant the same. you can check the trees and commits code content from repo's.
Thank you for your work. I have given it a try and it works perfectly.
I did notice two drawbacks:
- There is no or I can't find the option to use facial recognition as an unlock system.
- The battery drains very quickly when the phone is idle.
Is there any way to correct these two drawbacks?
Thank you.
Martinsio said:
- There is no or I can't find the option to use facial recognition as an unlock system.
- The battery drains very quickly when the phone is idle.
Click to expand...
Click to collapse
- not implemented in Lineage OS / not available; with motor front camera i see it as a risk and in my view is more secure with fingerprint;
- no drain here at all while idle. check your settings - like turn off pocket mode;

Categories

Resources