[ROM][BETA] LineageOS 19.1 for the Xperia Z5 Premium - Xperia Z5 Premium Android Development

[ROM][BETA] LineageOS 19.1 for the Xperia Z5 Premium - Xperia Z5 Premium Android Development

LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
{
"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"
}
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host | 7bf6035f8cca0560e6ec14d7b2a41621
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220912
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-09-12

Change-logs:
20220912:
- Upstream lineage 19.1 changes.
- September 2022 security patches.
- Camera fixes by tarkzim.
- sepolicy updates by Berni-0815.
20220425:
- Upstream lineage 19.1 changes.
- Performance improvements in UI.
- April 2022 security patches.
20220320:
- Initial Release

Joel16 said:
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
View attachment 5566809
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host: ROM | d33aa8b4928652220f65b459f061aa27
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220320
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-03-20
Click to expand...
Click to collapse
What a Great surprise ! Thanks a lot for the work. Will flash today and let you know about the bugs in a few days

Joel16 said:
LineageOS is a free and open-source operating system for various devices, based on the Android mobile platform.
Disclaimer:
It is your decision to install this software on your device. Neither LineageOS developers nor I take any responsibility for any damage that may occur from installing this software on your device.
View attachment 5566809
Notes:
This rom does not come pre-rooted or bundled with any modifications or apps.
Download:
Android File Host: ROM | d33aa8b4928652220f65b459f061aa27
Prerequisites:
- Make sure you're coming from firmware 32.4.A.1.54 before flashing this rom.
- Bootloader needs to be unlocked.
- Ensure that you have the latest version of TWRP recovery from here.
Install:
1) Reboot into TWRP Recovery.
2) Select Wipe -> Swipe to factory reset -> Advanced Wipe -> Dalvik /ART Cache, System, Cache and Data -> Swipe to Wipe.
3) Go back to TWRP's main menu -> Select Install -> Locate and choose lineage-19.1-202XXXXX-UNOFFICIAL-satsuki.zip file -> Swipe to confirm flash.
Bugs/Not Working:
- Camera
- Torch
- Touch vibration can sometimes be delayed.
- Please let me know if there is anything else.
If you encounter any other bug that are not mentioned in this list please provide a logcat and the steps necessary to reproduce the bug in detail (if necessary).
Sources:
Device Tree (Satsuki | kitakami-common/kernel/vendor)
XDA:DevDB Information
LineageOS 19.1, ROM for the Sony Xperia Z5 Premium
Contributors
Joel16, tarkzim, Berni-0815
ROM OS Version: Android 12
ROM Kernel: Linux 3.10.x
Version Information
Status: Beta
Current Beta Version: 20220320
Beta Release Date: 2022-03-20
Created 2022-03-20
Last Updated 2022-03-20
Click to expand...
Click to collapse
Ok i have flashed the rom and these are the things i have noticed so far:
- Selecting different choices for themes section depending on the extracted ones from Wallpaper does not exist which is probably LOS launcher's fault. (Couldn't flash any Pixel launcher mod as those i have tested caused launcher FC problem)
-There is a lag in Quick panel when editing, sliding it down or even pressing power button in Quick panel.
-When you wake the screen after being off, sometime the screen is blank, but if you power the screen off and turn it on again it will be fine.
-Sim detection takes a bit of a time like 1 or 2 mins after the phone boots sometimes(You can test maybe it's related to my signal, but i was fine in 18.1 or 17.1 which i was using just recently)
-Even tho vibration is disabled is settings, still some apps do have the vibration feedback with touch, like entering number in telegram or even AOSP's default keyboard.
-low volume on Mic when recording voice messeges in Telegram, WhatsApp (existed in your previous projects as well).
-Heating is fine, BUT you have restricted CPUs a lot in kernel side and i can't change those settings using kernel manager apps. This probably has effect on overall performance and will lead into lags in ui which i am facing now a bit sometimes (this was also the case with your latest 17.1 update)
-Battery icon in status bar is a bit too far from the edges of screen which i even noticed from your Screenshots as well (Not an important problem tho)
-unlocking animation for FP should start from the side power button but uses pixel 4 animation from the back FP sensor (again nothing very major lol)
In general functions for Daily driving this ROM is fine except for the camera you mentioned.
Thanks a lot for the new ROM. I know fixing these will take a while or some may not even get fixed. Take your time

alkh301180 said:
Ok i have flashed the rom and these are the things i have noticed so far:
- Selecting different choices for themes section depending on the extracted ones from Wallpaper does not exist which is probably LOS launcher's fault. (Couldn't flash any Pixel launcher mod as those i have tested caused launcher FC problem)
-There is a lag in Quick panel when editing, sliding it down or even pressing power button in Quick panel.
-When you wake the screen after being off, sometime the screen is blank, but if you power the screen off and turn it on again it will be fine.
-Sim detection takes a bit of a time like 1 or 2 mins after the phone boots sometimes(You can test maybe it's related to my signal, but i was fine in 18.1 or 17.1 which i was using just recently)
-Even tho vibration is disabled is settings, still some apps do have the vibration feedback with touch, like entering number in telegram or even AOSP's default keyboard.
-low volume on Mic when recording voice messeges in Telegram, WhatsApp (existed in your previous projects as well).
-Heating is fine, BUT you have restricted CPUs a lot in kernel side and i can't change those settings using kernel manager apps. This probably has effect on overall performance and will lead into lags in ui which i am facing now a bit sometimes (this was also the case with your latest 17.1 update)
-Battery icon in status bar is a bit too far from the edges of screen which i even noticed from your Screenshots as well (Not an important problem tho)
-unlocking animation for FP should start from the side power button but uses pixel 4 animation from the back FP sensor (again nothing very major lol)
In general functions for Daily driving this ROM is fine except for the camera you mentioned.
Thanks a lot for the new ROM. I know fixing these will take a while or some may not even get fixed. Take your time
Click to expand...
Click to collapse
Just so you know some of these are bugs from upstream, and will most likely be fixed by upstream lineage changes (not device tree related), others on the other hand will require some work whenever time avails.

Joel16 said:
Just so you know some of these are bugs from upstream, and will most likely be fixed by upstream lineage changes (not device tree related), others on the other hand will require some work whenever time avails.
Click to expand...
Click to collapse
Yes, for instance I know thet monet theme engine is LOS source related. But that device tree is pretty hard to work on.
Btw why don't you switch to OSS vendor?
I assume OSS can bring more stability and better overall performance. Even may fix some of the current bugs

flashed the rom, lets see what bugs we can find
thanks for another great work

alkh301180 said:
Yes, for instance I know thet monet theme engine is LOS source related. But that device tree is pretty hard to work on.
Btw why don't you switch to OSS vendor?
I assume OSS can bring more stability and better overall performance. Even may fix some of the current bugs
Click to expand...
Click to collapse
I'm all for open source but which ones are you referring to? I am testing lineage-17.1 with Sony's open source thermal manager. This rom however currently doesn't. Camera won't be easy, because there's too many Sony specific blobs that fails to communicate with any open source camera Hals. (Even with the Sony's OSS camera hal -- probably because our device wasn't initially targeted)

Joel16 said:
I'm all for open source but which ones are you referring to? I am testing lineage-17.1 with Sony's open source thermal manager. This room however currently doesn't. Camera won't be easy, because there's too many Sony specific blobs that fails to communicate with any open source camera Hals. (Even with the Sony's OSS camera hal -- probably because our device wasn't initially targeted)
Click to expand...
Click to collapse
I mostly meant LOS 19.1 and hmm, i didn't know you were using Sony's open source stuff
Well thanks for the info.

Thank u for maintaining this device for such a long period!

Thanks a lot

tnx for ur hard work
here geekbench result
highest multicore score of all z5p roms

niceeee

Nice work... waiting for the updated...bugs as mentioned

How to get into recovery

sanjuxox said:
Which gapps to be flashed?
Click to expand...
Click to collapse
opengapps

alisadeghian said:
How to get into recovery
Click to expand...
Click to collapse
unlock bootloader // flash twrp // power btn + vol down

newbiez5p said:
unlock bootloader // flash twrp // power btn + vol down
Click to expand...
Click to collapse
Recovery doesn't work with this rom.
I flashed this rom and after reboot i went to flash gapps, but
Can't go to recovery, got error while i tried to open it.
How to flash gapps

newbiez5p said:
opengapps
Click to expand...
Click to collapse
opengapps doesnt have android 12

Related

[GearCM][i9500][6.0.x] Optimized CyanogenMod 13.0 for Samsung Galaxy S4 [20161203]

Use this thread =>http://goo.gl/6kTvJu for questions or discussions.
Only Bug Reports & Feedbacks are allowed here. Penalty: Post Removal by Moderators
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0.x (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
ROM Downloads
All not-working RenderServer hosted files can be found here: https://androidfilehost.com/user/?w=settings-dev-files&flid=50874
<< Stable >>
20161203 Build: https://www.androidfilehost.com/?fid=601300970940399905
<< Misc. (Modem & Recovery) >>
GearRecovery (based on TWRP Recovery) 20160220: https://www.androidfilehost.com/?fid=24421527759883765 <= Highly Recommended
I9500XXUHOD4 LL Modem: https://basketbuild.com/filedl/devs...s And Bootloaders/I9500-XXUHOD4-MODEM_CWM.zip <= Russian Modem, Recommended
I9500DDUHOA1 LL Modem: http://forum.xda-developers.com/attachment.php?attachmentid=3165311&d=1423927137 <= Indian Modem, use it if you're experiencing problems with Russian variant
Previous Releases:
20160828 Build: https://www.androidfilehost.com/?fid=24591000424960632
20160711 Build: https://www.androidfilehost.com/?fid=24591000424946159
20160710 Build: https://www.androidfilehost.com/?fid=24591000424945760
GearRecovery (based on TWRP Recovery) 20151003: https://www.androidfilehost.com/?fid=24052804347828835 <= Highly Recommended
<< Beta >>
20160502 Build: https://www.androidfilehost.com/?fid=24531172553916653
<< Alpha >>
20160101 Build: https://www.androidfilehost.com/?fid=24352994023703667
Google Apps (add-on)
http://opengapps.org/ <== Recommended <> Micro/Mini Modular Package. Do not choose Stock
Installation
3-button-combo = "Volume Up/+" + "Home/Center" + "Power/Lock"
- First time flashing GearCM 13.0 to your Galaxy S4 (or coming from TouchWiz/Stock Based ROMs)?
Root your device and install latest GearRecovery
Reboot into Recovery using 3-button-combo
Do a Backup!
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from internal/external sdcard
Optionally install Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from Official CM10.2/CM11/CM12/CM12.1 or GearCM 11/12/12.1?
Reboot into Recovery using 3-button-combo
Do a Backup!
Install latest GearRecovery
Reboot into new Recovery using 3-button-combo (if needed)
WIPE (wipe data/factory reset + wipe cache partition + format /system partition)
Install the ROM from internal/external sdcard
Optionally install the Google Addon
Done! You can now reboot the phone to enjoy the rom
- Upgrading from another build of GearCM 13.0?
Reboot into Recovery using 3-button-combo
Do a Backup!
Install latest GearRecovery
Reboot into new Recovery using 3-button-combo (if needed)
Install the ROM from internal/external sdcard
WIPE Dalvik/ART Cache (wipe cache partition + wipe dalvik cache)
Done! You can now reboot the phone to enjoy the rom
Known Issues (regarding latest available build)
Please do not report bugs if it is already listen in the list of known issues
Audio HAL isn't working correctly, causing VOIP issues, HDMI audio instabilities and mixer paths conflicts
STK Toolkit isn't working yet, SMSs aren't properly sent (RIL issue)
SELinux policies are almost complete, with just some minor missing rules
Wireless Display (or Miracast if you like) stream is corrupted, buffer issues
Adoptable Storage isn't stable, crashes while encrypting the external storage (Kernel Panic). Read Here: http://goo.gl/0w6DPt
Device Encryption isn't stable for the same issue that affects Adoptable Storage
Reporting Bugs
First of all, read this: http://www.chiark.greenend.org.uk/~sgtatham/bugs
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
REPORT BUGS IN THIS THREAD ONLY
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 /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your--
Phone model:
Radio (baseband) version:
GearCM version:
GearCM download url:
Google Apps version:
Did you--
wipe data/factory reset:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance Settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Changelog
20161203:
Updated CM Sources
All missing features (that i have accidentally removed in the previous build) are back
Some Audio HAL stability improvements
Removed that dangerous Soft Reboot option
KERNEL: some updates here and there
Check my GearCM Github for more information
Previous Releases:
20160828:
Updated CM Sources (nice improvements are here)
Added new features for Screen Power Saving, play with LiveDisplay settings!
Enabled HDMI CEC support
Wireless Display & Screen Recording should work better now, but nothing guaranteed
20160711:
Updated CM Sources
Improved built-in Camera Latency with Flashlight
KERNEL: Fixed Battery Capacity
20160710:
Switched to Stable Release
Updated CM Sources
Fixed Wireless Display (even if not completely)
Fixed random Graphics Glitches
Fixed WiFi issues
Fixed Battery Drain
Fixed Camera Instabilities (no more crashes)
SELinux is now enabled, but on permissive mode.
DRM-dependent apps should be working fine now
Maxed Out ART Runtime Performance
OTA Updates are back, but with download links (AndroidFileHost limit)
Adoptable Storage is now working, but unstable. "Known Issues" explains why
Optimized Network Performance (WiFI & 3G)
Restored Android Marshmallow Doze Mode (power-saving)
Using latest INU OK2 proprietaries
KERNEL: switched to a whole new, and stabler, kernel
KERNEL: using latest INU OK2 kernel sources
KERNEL: enabled all features that might be required by some apps
20160502:
No Changelog provided yet, will be added soon.
20160101:
First Release (Alpha)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
[GearCM][i9500][6.0.x] Optimized CyanogenMod 13.0 for Samsung Galaxy S4, ROM for the Samsung Galaxy S4
Contributors
Alberto96, NBruderman, intervigil, codeworkx
Source Code: https://github.com/GearCM
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Latest Modem, TWRP or GearRecovery, and a working brain to manage GearCM features
Based On: CyanogenMod
Version Information
Status: Stable
Current Stable Version: 20161203
Stable Release Date: 2016-12-03
Current Beta Version: 20160502
Beta Release Date: 2016-05-02
Created 2016-01-01
Last Updated 2016-12-03

Reserved
Important! Read this before any other question/doubt.
If someone doesn't like my ROMs, or doesn't like me, or even better, doesn't want to like/appreciate my works, then you can just go ahead and use/follow someone else works. Easy, not against XDA rules, and smart.
I'm not here for "fame" (or "glory" as someone in this forum said) unlike someone else, neither this is my job. I'm working on this device just because TW is far than usable (at least for me) on every Samsung device, not because someone else requested me to do it.
Click to expand...
Click to collapse
Differences between GearCM (Optimized CyanogenMod) and Official CyanogenMod (NIGHTLY):
Degrated Shadow said:
Enough of those dumb questions..
The Official CM rom is maintained by @Alberto96 and @intervigil
He makes the very recent changes here relating to performance...which are then in time pushed (even if partially) to CM Official Sources. The kernel is different because it has seLinux disabled and few minor tweaks you might not even notice...this GearCM ROM will have more performance. But CM will have their updated base changes which are included here with each update.
What I mean is you probably wont even notice what's different in terms of user interface. GearCM will have more performance. Official CM will have updated sources. But it will include GearCM's changes in time as @Alberto96 pushes them to CM
You can decide by a simple choice..more performance and not-nightly updated sources or similar/worse performance (improving with nightly updates) with updated sources. I would choose GearCM because of the reasons i mentioned above. Do what you will...and let this be a note to everybody who ask this again and again and again. Don't spam the thread with same question in every alternate page...because there are other people who might have different problems they need to ask. Read at least 15 previous pages and the first post Changelog before asking the question. Reading most of the times will give you a solution and if not most of the info you will read will help you anyway.
Click to expand...
Click to collapse

Reserved
FAQ (Frequently asked questions)
If there a procedure that i should follow in order to have a clean base to start from?
Yes, follow this procedure and you shouldn't have any issue.
Flash latest Stock ROM Odin package | http://www.sammobile.com/firmwares/download/55812/I9500XXUHOH7_I9500MBCHOF1_MBC | using latest Odin3 Flasher | http://forum.xda-developers.com/attachment.php?attachmentid=3446301&d=1440131361 | and Standard (not Chinese) .pit file. | http://forum.xda-developers.com/attachment.php?attachmentid=2343320&d=1382462885 |
After First Boot, Shutdown your device and Boot into recovery mode using 3 buttons combo (Volume +, Home, Power)
Wipe Data/Factory Reset using Volume Keys and Power Button (on Stock Recovery)
Flash latest TWRP 2.8.7.0 | https://dl.twrp.me/i9500/twrp-2.8.7.0-i9500.img.tar | using Odin3 | previously linked | (Untick Auto Reboot to avoid any issue)
Shutdown your device (pull off your battery)
Boot into recovery mode using 3 buttons combo | Volume +, Home, Power | (TWRP will boot now)
Flash latest GearRecovery (on TWRP)
Reboot into recovery mode using TWRP on-screen buttons | Home => Reboot => Recovery | (GearRecovery will boot now)
Clean completely your device (Format Data and Wipe All Partitions)
Reboot into recovery mode as did before (GearRecovery will boot again now)
Flash latest GearCM ROM
Home => Reboot => System
Where is "Developer Options" category?
To activate 'Developer Options' category in Settings you need to tap 7 times on 'Build number' located into Settings -> About Phone.
What can i do to fix VOIP audio calls?
There's not a real fix yet, so i found this useful workaround that could help you.
If you need to make a VOIP call:
1) Play something using stock music player (also third-party music players SHOULD be fine)
2) Do not pause audio playback
3) Make a call using your preferred VOIP app.
Or you can just use a Wired Headphone/Headset | BT Headphone/Headset.
This workaround should work also for incoming VOIP calls.
How can i solve problems with Hebrew language?
Go to "Developer Options" in Settings and check "Force RTL layout direction".
What can i do to reduce the "echo effect" while in-call?
Try to reduce in-call earpiece volume (if possible). Shouldn't be required on latest builds.
I'm having problems with battery life, what can i do?
1) Use "Greenify" to hibernate all apps with a "little cloud + 'Gcm' word inside" on the right of each app's name. Donation version is recommended because it allows deeper hibernation of apps
2) Disable "Location" or set it to mode "Battery Saving" (Settings -> Location)
3) Make sure that your 2G/3G mobile network signal level isn't always low or unstable
4) Deny "Wake Up" and "Keep Awake" permissions to Google and third-party apps. (Settings -> Privacy -> Privacy Guard -> Press menu button and check "Show built-in apps" -> Press menu button again and go to Advanced -> Horizontal Scroll to Device)
5) Disable "Sync" or sync only useful stuff like Contacts
6) Disable "Auto-rotate screen" (Settings -> Display & lights -> Rotation)
7) Use one of the latest Modem/Baseband listed on first post.
8) Disable Ambient Display
9) Install Xposed Framework and configure Amplify
If this isn't enough then replace your battery and/or reduce your phone usage. :silly:
Is GearCM OTA supported?
Yes (Since 20150707 Build)
Why is my phone over-heating while playing heavy-games or running heavy-apps?
Use a bit your brain to explain why. High CPU and GPU usage = high heat production. Your phone will automatically throttle CPU when needed so don't worry, it is safe and normal.
Can I use another kernel instead of the one included in the zip?
No. Only use the included kernel for 100% compatibility, bug reports with non-standard kernel will be ignored.
Can i disable S-View cover features (lock/unlock)?
Not yet.
*** IR Remote app isn't working anymore/was working on previous builds/causes my phone to crash, what can i do?
Contact *** IR Remote app developer.

woooww .. new topic .. good luck

30 Minutes left to the end of the upload (and don't worry, this isn't a placeholder)
Known Bugs:
- Camera
- Compass (untested)
- Synapse (not supported)
- OTA Updates (support will be added later)

GearCM 13 Alpha Build is up!
Enjoy

Alberto96 said:
GearCM 13 Alpha Build is up!
Enjoy
Click to expand...
Click to collapse
Thank you for your effort, downloading now , hope camera is fixed soon

Great job man thank you downloading now

can i dirty flash or must i clean install @Alberto96?

Bilal_503 said:
can i dirty flash or must i clean install @Alberto96?
Click to expand...
Click to collapse
You know that i'll always answer with two simple words: "CLEAN FLASH".

Thanks Alberto..
YOU ARE AMAZING!!!

Alberto96 said:
30 Minutes left to the end of the upload (and don't worry, this isn't a placeholder)
Known Bugs:
- Camera
- Compass (untested)
- Synapse (not supported)
- OTA Updates (support will be added later)
Click to expand...
Click to collapse
The Synapse 0.44 added support to Android M.
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
Alberto96 said:
GearCM 13 Alpha Build is up!
Enjoy
Click to expand...
Click to collapse
Best New Year's gift!

treborbr said:
The Synapse 0.44 added support to Android M.
Click to expand...
Click to collapse
CM13 isn't using anymore Busybox so it isn't compatible for real. I need to compare Busybox & Toybox to check the differences.

I download and I've tested. sound problem resolved but could be better. not disturbin
thanks alberto. I hope to be much more beautiful

Downloading and gonna dual boot! Thanks a lot @Alberto96

Wow, that's what I had been looking for in the past months. Thank you for your hard work, and happy new year! :laugh:

Thanks man, I have been waiting for this for so long.

Does it support f2fs ?
Just to make sure there is no compatibility issues..
---------- Post added at 01:03 AM ---------- Previous post was at 12:27 AM ----------
After testing for 2 ours.. I can say there are no major bugs in the rom
Everything is working except for camera and it's much smoother than cm12.1

Is this latest build booting?
Sent from my GT-I9500 using Tapatalk

Mo0s said:
Is this latest build booting?
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
Yes, indeed.. That's why this thread..!
Sent from my GT-I9500 using Tapatalk

[ROM] [ 8.0.0 ] Official madOS - Oukitel K6000 Plus [MT6750]

{
"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 Oreo ) for Oukitel K6000 Plus with MTK 6750 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 from xda DevDB
Download OpenGapps nano or pico from OpenGapps
(choose Arm64 and Android 8.0 )
Backup
Unlock Bootloader Bootloader unlock
Flash new mandatory new Oreo 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)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors (including fingerprint)
Lights; HW Keys
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Not working:
nothing known
XDA:DevDB Information
madOS_O_K6KP, ROM for all devices (see above for details)
Contributors
DerTeufel1980, superdragonpt, fire855
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: bootloader unlocked, twrp
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 1
Stable Release Date: 2017-11-19
Created 2017-11-19
Last Updated 2017-12-31

Reserved
How-To unlock Bootloader and install TWRP
ATTENTION: This is voiding your warrenty
Install minimal adb and fastboo to your PCt: Minimal ADB and Fastboot
On the smartphone: Go to Settings --> About Phone and hit 'build Number' seven times, to enable 'Developer Options'
Go to Settings --> Developer Options, and allow usb-debugging and allow OEM-unlocking (For bootloader unlock)
Connect the smartphone to the pc. On the smartphone accepts the adb connection with the pc
Start 'Minimal adb and Fastboot' at Pc. In the command window, type: "adb reboot bootloader" and press Enter (this is restarting the smartphone into the bootloader)
WARNING: This step deletes all data from the smartphone, returns it to the factory setting and leads to the loss of the warranty! In the command window, type "fastboot oem unlock" and press Enter (to unlock the bootloader). You probably need to press some button of the phone to confirm (check the display for this)
Download the Twrp image: Oukitel K6000 Plus TWRP, and copy the recovery.img file to the installation folder of 'minimal adb and fastboot'
In the command window, type "fastboot flash recovery recovery.img" and press Enter. After successful flash, enter "fastboot reboot" in the command window, press 'Enter'. Then immediately press and hold 'volume up key' on the smartphone (Until a small menu appears)
3 options appear on the smartphone: Recovery, Fastboot, Normal. You can navigate with 'volume up key' and confirm your selection with 'volume down'. Navigate to Recovery and press the volume down key to confirm (Smartphone starts now the Installed TWRP Recovery)

F.A.Q
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: Where to report bugs ?
A: madOS issue tracker
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP recovery
--> Download Section
Q: How do i flash a new recovery or new boot from previous TWRP?
A:
1: You can flash it with a scatter file
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select RECOVERY or BOOT image file > Select "Recovery" or "Boot" as partition to flash.
Reboot
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: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire, where f2fs might be faster
Q: is the Data connection issue of going to / from 4G 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)
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: 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 Magisk v14 onwards.
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
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
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.
Pure Nexus
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
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)

one more
reserved

DerTeufel1980 said:
Changelogs
[Stable] Build [8.0.0] 20171119
First Release
Patch Level: 8.0.0 [OPR1] November 6, 2017
Kernel: 3.18.80( Oreo branch)
Click to expand...
Click to collapse
Hi guys,
Thanks for your incredible work for the K6000 Plus!
I have a Doogee Y6. It uses the same kernel as K6000 plus. So, I've been trying to compile the k6000 plus kernel in order to work on my phone (I have made the necessary adjustments regarding my device's specific drivers such as LCM, Touchscreen, fingerprint etc.)
But I am running into errors. The compiler complains about not finding some files like: mt_gpufreq.h, cmdq_engine.h etc.
Can you assist me with this?
Thank you.

Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
3. Phone freeze sometimes for a sec.

Eselter said:
Great ROM! Many thanks for your work M.A.D team
I found one bug in camera. When you turn on HDR mode and after taking picture camera force close with toast: "Media server died, closing camera." but photo still save so not big deal
--- edit ---
More bugs:
1. I can't change cpu governor
2. WiFi icon and battery icon in statusbar are always black: - bug gone after restart
View attachment 4337841
3. Phone freeze sometimes for a sec.
Click to expand...
Click to collapse
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0

I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?

DerTeufel1980 said:
Thx for your feedback. I'll take a look.... Changing CPU governors is more than less just a left over from older phones... We may just remove this option. There aren't actually useful governors to switch to.
In which situations did it freeze?
Sent from my uhans h5000, running Android 8.0.0
Click to expand...
Click to collapse
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.

xasdfx_ said:
I dont know why, but when i trying to boot in new TWRP recovery, the phone's screen just glows gray.
Can u help me with this? Firmware v23, bootloader unlocked. What's wrong?
Click to expand...
Click to collapse
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Eselter said:
Most often while scrolling (ex in app drawer or browser) and click on some button (ex keyboard). I think it can be releated to CPU hotplug.
Click to expand...
Click to collapse
OK. I'll try to reproduce it
Sent from my uhans h5000, running Android 8.0.0

And one more minor bug. In quick settings on weather tile button more settings don't work. If someone wonder it can be adjusted in madOS extras.

DerTeufel1980 said:
You flashed the recovery from the download section, right?
Does it show the twrp logo in the beginning?
Click to expand...
Click to collapse
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?

Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.

xasdfx_ said:
Yes, of course.
Nope., it doesnt show anything. Oukitel logo - gray sreen. I changed the display on my phone(the old one cracked), maybe the reason is this?
Click to expand...
Click to collapse
****... Unfortunately I have no idea how to fix it then... We can only use the drivers shared by oukitel. If there's something missing, we're out of luck...
Eselter said:
Next two minor bugs:
1. Changing implementation of webview don't work. Phone always using chromium engine.
2. Normal reboot freeze phone. Soft and reboot to recovery works fine.
BTW: do you have some bug tracker ?
And one more:
Battery capacity are wrongly reported.
Click to expand...
Click to collapse
Webview implementation... We'll check as well, but that's not very important.
Does it always freeze? And where/when? During the new boot, or before shutting down?
In which situations/apps is the battery capacity reported wrong?
Sent from my uhans h5000, running Android 8.0.0

DerTeufel1980 said:
Does it always freeze? And where/when? During the new boot, or before shutting down?
Click to expand...
Click to collapse
Until now always (I try more than 10 times) before shutting down on message rebooting, but now is working fine (magic ;>).
DerTeufel1980 said:
In which situations/apps is the battery capacity reported wrong?
Click to expand...
Click to collapse
In apps: CPU Info and AccuBattery. I don't know if this have impact on battery status in system?

And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823

Eselter said:
And one glitch very paintful for me :/
Android Auto has problem with displaying on car screen (and Android Studio):
View attachment 4338823
Click to expand...
Click to collapse
I'll try to check this. We unfortunately don't own a car which supports this
Sent from my uhans h5000, running Android 8.0.0

https://developer.android.com/training/auto/testing/index.html
@DerTeufel1980 my screenshot was made from above tool for devs but in car it look exactly the same
So you can use it to reproduce and debug the glitch.

One more thing related to car. Calls via car speakers not working. Music, call log, contacts working fine via Bluetooth but calls always switch to phone speakers/microphone.

[ROM] [ 8.1.0 ] Official madOS - Vernee Apollo Lite & X [MT6797]

{
"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 ) for Vernee Apollo Lite & X with MTK 6797 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:
The latest 7.1.2 build must be flashed in SPFT with firmware upgrade mode before this ROM can be flashed (Downloads: VAL, VAX)
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download 8.1 GApps from xda devdb (Mirror)
Backup
Flash new mandatory new Oreo 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)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Fingerprint
Lights
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Bugs:
-
XDA:DevDB Information
madOS_O_VAL_VAX, ROM for all devices (see above for details)
Contributors
fire855, DerTeufel1980, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-12-25
Created 2017-12-25
Last Updated 2018-01-13

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?
A: Latest M.A.D. TWRP 3.2.1-0 recovery
--> 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: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
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)
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: 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 onwards.)
2: Super SU ( v2.82 onwards)
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?
A: Pretty awesome
Q: Does this build support Vulkan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: Does 4k video recording work?
A: Yes, but not every phone supports it. If 4k worked in the stock rom, it will work in madOS too.
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
[Stable] Build [8.1.0] 20171225
First Release
madOS version: 2.1
Patch Level: 8.1.0 [OPM1] December 5, 2017
Kernel: 3.18.89 (o-8.1.0 branch)
[Stable] Build [8.1.0] 20180102
madOS version: 2.1.1
Fixed UI lags / hangs
Fixed deepsleep
Fixed screen recording
Fixed video playback issues
Updated graphics system
Improved GSM/LTE signal handling
Fixed alarms
Fixed FMRadio
Fixed wallpaper scrolling setting in madLauncher
Fixed 5GHz hotspot issues
Improvements in bluetooth for A2DP
Updated included APNs list
madOS color Engine:
Rebased & many improvements on the engine
Better support on theming Quick Settings
New option to override default Google 8.1 QS theming
New reset button to get back to default 8.1 theming
New MAD mode

Merry Christmas !!

Thanks. Merry Christmas.
The computer died. I will not make the sd card backup.

Marry Xmas to all.

Wow.... Oreo release and directly 8.1 weeeeeeeeeeee!
Didn't expect this before the new year, what a surprise.
Thanx you @fire855
Thank you MAD-team

Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you

Should we come from the last 7.1.2 build (which has different partitions from stock)?

I really appreciate the work, but it's somewhat unflashable. New recovery is not stable, it gets stuck sometimes. Also I didn't manage to bring 8.1 to run with Gapps yet.
€: To provide somewhat more information: System crashes when running playstore.
€2: Full wipe made, advanced wipe and wiped every partition. It gets stuck coincidential, there's no proper reason for it, it got stuck once when I flashed MadOS itself, second time it got stuck flashing gapps, so I hope I get it run that night...
€3: Recovery freezes and after 30 seconds (approx) phone reboots.
€4: Nope, I don't get it to work, goddamnit. It freezes almost immediately after I enter my pin.

Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...

TJFA81 said:
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
Click to expand...
Click to collapse
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.

Xorianator said:
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Click to expand...
Click to collapse
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???

TJFA81 said:
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
Click to expand...
Click to collapse
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps

Xorianator said:
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Click to expand...
Click to collapse
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery

TJFA81 said:
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
Click to expand...
Click to collapse
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
€5: Nope, didn't fix a thing. So well, at least I could capture this "sack down" thing:
The red line is where the display ends. As you can see the symbols are still in place. The blue line marks where the activity "sack down" and if this happens (which happens just on coincidence) nothing will happen any further, system's frozen and it reboots afterwards.

TJFA81 said:
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Click to expand...
Click to collapse
TWRP

Xorianator said:
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
Click to expand...
Click to collapse
Thank you, already did it... reflash recovery.img but by spflashtool. Now im inside twrp3.2.1...
Now its time to try install oreo and gapps

cedricboquiren said:
Should we come from the last 7.1.2 build (which has different partitions from stock)?
Click to expand...
Click to collapse
Yes, the latest 7.1.2 is mandatory. Added this to the first post now too.

I tried to install the new rom, after I installed the new twrp, the phone is still restarting, I tried to return to 7.1.2 with spft but no success even does not connect with the laptop, what I could do they do?

[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10

Reserved

Reserved

Awesome! Keep up the great work and thank you for keeping this devices development alive

JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911

oh yeah maga
make android great again

Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?

DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.

Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !

gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?

ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course

To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.

Thx!
Will test this ROM!

yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.

Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?

hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.

ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.

Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?

The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.

hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.

[ROM][UNOFFICIAL][10.0] LineageOS 17.1 for UMIDIGI F1 and F1 PLAY

{
"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"
}

Code:
* 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.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Not Working
VoLTE (and will not be fixed due to MTK's proprietary extensions)
Selinux is permissive
FM Radio is Working But No Sound
Sudden Shutdown
Instructions :
Flash your phone with the latest stock rom version (20190903 download link )
Boot your F1 Play to the official OS.
Go to `Settings > About phone`, tap `build number` several times to enable developer settings.
Go to `Settings > System > Developer Settings`, enable `OEM unlocking` and `ADB debugging`.
Connect your phone to your PC and open a terminal or a command line window.
Run `adb reboot bootloader` on your PC (there is no way to enter bootloader directly, only possible through adb).
Run `fastboot flashing unlock` and comfirm unlock on device (THIS WILL WIPE ALL DATA!).
Run `fastboot reboot` to reboot your device and now you should see an unlocked warning during boot screen with orange state.
Download the latest build and gapps
Power off
Press on Power+Volume up button to boot up to Fastboot
Execute "fastboot flash recovery TWRP 3.X.X_F1(or Play).img"
Wait to Finish And Execute "fastboot reboot recovery"
Wipe Data,System,Cache
Flash the latest build
Flash gapps(optional)
Flash Magisk(optional)
Reboot
Downloads :
F1 : https://www.mediafire.com/file/ff5pab2m47wm20g/lineage-17.1-20220515-UNOFFICIAL-F1.zip/file
F1 Play : https://www.mediafire.com/file/d5e8apmil5qpeo7/lineage-17.1-20220515-UNOFFICIAL-F1_EEA.zip/file
Gapps : https://opengapps.org/
TWRP 3.6.1 Recovery for F1 Play : https://www.mediafire.com/file/dn8mzk8bpulvqig/TWRP_3.6.1-F1_Play.img/file
TWRP 3.6.1 Recovery for F1 : https://www.mediafire.com/file/91k98oii8ab7j1l/TWRP_3.6.1-F1.img/file
TWRP 3.3.1 Recovery for F1 Play : https://www.mediafire.com/file/okky2dmgd5zupql/TWRP-3.3.1-F1_Play.img/file
TWRP 3.3.1 Recovery for F1 : https://www.mediafire.com/file/ei83p1lwjupavdd/TWRP-3.3.1-F1.img/file
PBRP Recovery F1 Play : https://www.mediafire.com/file/sl2t7vdqy1ztfsi/PBRP-3.1.0-F1_Play.img/file
PBRP Recovery F1 : https://www.mediafire.com/file/1omqnnh0bvnbath/PBRP-3.1.0-F1.img/file
Magisk : https://github.com/topjohnwu/Magisk/releases/download/v24.3/Magisk-v24.3.apk
Reporting Bugs
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 /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Changelog:
- 07-02-2021 : Initial build
- 20-03-2021 :
*Fix display Lags
*Added Material Files and GoCamera
*Fix GoCamera Video Recording bug
*Added F1 Build
*Fix 'dev/fm' Permission Error
*Fix Incoming Call Bug
- 24-04-2021 :
*Fix Incoming call bug (now really fixed)
*Add LiveDisplay (but it not working cause of kernel)
*Back to LineageOS Charge Animation
*Fix Some Carriers does not Work
*Fix "Stuck at SIM Card Pin"
*Fix Random Reboot and recovery loop (I Think because of TWRP if you have this issue flash LineageOS Recovery)
*Add Face Unlock
*Add DT2W (double tap to wake)
*Fix Write Access to System partition (you need to flash LineageOS Recovery)
- 3-06-2021 :
Build TWRP 3.5.2 For both devices from scratch
- 17-07-2021 :
* Fix in call bug in F1 and F1 play (my mistake)
* Update some system Apps
* For NOW use TWRP 3.3.1 Cause it Works well with Data Encryption
- 28-07-2021 :
* Fix Recovery Loop on TWRP 3.3.1 on F1 and F1 Play (flash the newest recovery to fix recovery loop)
* For NOW use TWRP 3.3.1 Cause it Work well with Data Encryption
- 06-08-2021 :
- Fix FM Radio (finally)
- Add Chromuim instead of jelly
- Fix Video Encoding on Chromuim Based Browsers
- Disable LiveDisplay (not entirely there is in settings)
- Revert back to Snap ( LineageOS Camera) instead of Google Camera Go (to fix video recording issue)
- 10-08-2021 :
- Revert Back to Jelly Browser (Chromuim has some issues)
- Fix Sound Distortion via Besloudness Settings APP (you can still enable/disable Besloudness audio Feature)
- Use LineageOS NFC Stacks instead of Prebuilted One from Vendor (fix Random shutdown)
- 19-08-2021 :
- add support AOD (Always on Display)
- Remove LiveDisplay(now is removed from settings)
- add support Night Light and fix the flicker when enabled
- Add MiraVision(not working for now)
- Improve System Stability and performance
- Enable insecure ADB for debugging
21-8-2021 :
- Fix Besloudness Settings not found
- Fix low brightness is still not low
- Drop MiraVision Support(need a lot of mediatek properties that are closed source code)
25-4-2022 :
- April security updates included
- Add Treble gsi Patches for more stability
- release with TWRP 3.6.1 and PBRP 3.1.0
1-5-2022 :
- Hide DocumentsUI Icon (cause we have a file manager)
- Drop and disable LiveDisplay
- Revert and Enable Night Light (Work Well)
- fix playing video on Chrome will reboot the phone
- some other improvements i forgot
15-5-2022 :
- Fix an error in system property
- Use a bigger APN config to fix "service is unavailable"
- Update Material Files
Click to expand...
Click to collapse
For Donations:
Feel free to donate to support this project.
Credits:
UMIDIGI
PeterCxy [for his device tree for f1]
a-dead-trousers[For some code from his device tree]
XDAevDB Information
LineageOS 17.1 for UMIDIGI F1 and F1 Play, ROM for Miscellaneous Android Development
Contributors
Shadow Of Leaf
Source Code: https://github.com/Shadowofleaf/android_device_umidgi_f1_play
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2021-02-07
Last Updated 2022-05-15

Hey there, i do have a problem with setting up the rom. Wifi doesn't work for me. While in the google setup it doesn't show any networks and doesn't show my ip/mac below. When i skip the setup and try to activate wifi in the settings, it always intantly turns it off again.
LineageOS version:
17.1 20210205 Build
LineageOS Download url: https://www.mediafire.com/file/4flx8655kchinrt/lineage-17.1-20210205-UNOFFICIAL-F1_Play.zip/file
Gapps version:
ARM64 10.0 Pico 20210206 Build
wipe:
Coming from stock MT6771_20190515, did a full wipe (System/Data/Cache/Dalvik) and flashed above versions. No errors while flashing/booting.
restore with titanium backup:
/
reboot after having the issue:
No reboots/bootloops
No Modifications. Going back to stock Wifi works again.
Tried dirty flashing the rom a second time after the first boot up. Also tired flashing with/without Magisk 21.4.
i don't know how to get logs or if they would even be of importance here, if so let me know and i'll search up how to get them.

IvI97 said:
Hey there, i do have a problem with setting up the rom. Wifi doesn't work for me. While in the google setup it doesn't show any networks and doesn't show my ip/mac below. When i skip the setup and try to activate wifi in the settings, it always intantly turns it off again.
LineageOS version:
17.1 20210205 Build
LineageOS Download url: https://www.mediafire.com/file/4flx8655kchinrt/lineage-17.1-20210205-UNOFFICIAL-F1_Play.zip/file
Gapps version:
ARM64 10.0 Pico 20210206 Build
wipe:
Coming from stock MT6771_20190515, did a full wipe (System/Data/Cache/Dalvik) and flashed above versions. No errors while flashing/booting.
restore with titanium backup:
/
reboot after having the issue:
No reboots/bootloops
No Modifications. Going back to stock Wifi works again.
Tried dirty flashing the rom a second time after the first boot up. Also tired flashing with/without Magisk 21.4.
i don't know how to get logs or if they would even be of importance here, if so let me know and i'll search up how to get them.
Click to expand...
Click to collapse
the fact that wifi is not working is the vendor is old
try the latest stock rom 20190903
https://community.umidigi.com/forum.php?mod=viewthread&tid=18875&extra=page%3D1
flash it with sp flash tool and test again lineageos

new build for f1 play with fixed bugs and a lot of improvements
f1 build soon enough stay tune

Shadow Of Leaf said:
new build for f1 play with fixed bugs and a lot of improvements
f1 build soon enough stay tune
Click to expand...
Click to collapse
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.

soulfisher7 said:
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.
Click to expand...
Click to collapse
really soon i will upload it
stay tune

soulfisher7 said:
That's great!
Will be waiting for the next F1 (non play) next update here. I will flash it and let you know how it goes. Hopefully network signal is not extremely low as GSIs.
Click to expand...
Click to collapse
i upload the latest build for f1
try it out to see if you have that signal problem

Shadow Of Leaf said:
i upload the latest build for f1
try it out to see if you have that signal problem
Click to expand...
Click to collapse
Thanks for the quick upload.
- F1, latest international stock build, rooted.
- Removed root, flashed stock boot.img
- wiped system, data, cache, dalvik
- Flashed F1 LOS build: 17.1 - 20210424
- gapps: open_gapps-arm64-10.0-nano-20210424
- magisk: v21.4
- apps restored via swift backup
Issues: will update when/if I notice any.
Once again thank you for the ROM, much appreciated.

- Network signal is unreliable, similar to the GSI behavior. I am on the international stock version, and I assume it uses the same vendor image as the European. Is there a difference?
- Double tap to wake does not work.
- ram management is better than stock, but it's not as good as other GSIs, which is odd for LOS.

soulfisher7 said:
- Network signal is unreliable, similar to the GSI behavior. I am on the international stock version, and I assume it uses the same vendor image as the European. Is there a difference?
- Double tap to wake does not work.
- ram management is better than stock, but it's not as good as other GSIs, which is odd for LOS.
Click to expand...
Click to collapse
it work but not all the time and it related to kernel (is prebuilted)
for ram management i see what i can do

new TWRP 3.5.2 Build for UMIDIGI F1 and F1 Play
Test it out for bugs and for decryption if it work

Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)

Crhada17 said:
Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)
Click to expand...
Click to collapse
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP 3.5.2

O
Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP 3.5.2
Click to expand...
Click to collapse
carrier network is shown at full ?
yes, there is no problem of not seeing the line connected to the operator network.
I can call others, but they cannot call me, the
person you are calling is not reachable.
did you found any bug related to new TWRP 3.5.2
I didn't see any problem, but it doesn't backup. I think this error appears because the device is encrypted.

Crhada17 said:
Hi, use Umidigi F1 Play and rom link: https://www.mediafire.com/file/n85cz0oyei5qvlv/lineage-17.1-20210416-UNOFFICIAL-F1_Play.zip/file
Gapps Version: open_gapps-arm64-10.0-pico-20210605
Still No Call Issue Continue and com.tek.ims.Application stopping error on installation screen. Please fix this problem. I don't want to return stock rom.
(I don't know English well, sorry if I said something wrong)
Click to expand...
Click to collapse
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
Crhada17 said:
O
carrier network is shown at full ?
yes, there is no problem of not seeing the line connected to the operator network.
I can call others, but they cannot call me, the
person you are calling is not reachable.
did you found any bug related to new TWRP 3.5.2
I didn't see any problem, but it doesn't backup. I think this error appears because the device is encrypted.
Click to expand...
Click to collapse
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
Good luck bro

Crhada17 said:
Good luck bro
Click to expand...
Click to collapse
thanks

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
bro when will you post the fixed version?
If other problems will take a long time, you can at least post a fixed version of the problem of not receiving calls.

Shadow Of Leaf said:
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
I've been waiting for a long time, any progress

Shadow Of Leaf said:
carrier network is shown at full ?
and i will look into this ims problem
thanks for the report
and did you found any bug related to new TWRP
thanks for report out
the call issue is my fault i forgot to use my fixed mtk-ril.so instead of the faulty one in vendor
for the com.tek.ims force application is just force closed the first time booting in lineageos is not big deal
i will fix the call issue and fm radio and build new one so stay tune
i think the big problem is the decryption in twrp i need to fix it
Click to expand...
Click to collapse
sorry bro i bothered you a bit but it's a really good rom but i can't use it because of incoming call problem can you spare some of your precious time
thank you

Database Info

welcome