[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Fingerprint on J6+
Sim slots
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+/J6+ [j4primelte & j6primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-01-29
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-25
Last Updated 2020-01-29
Changelogs :
Stable version 1 - 29/01/2020 :
Now we are building vendor too. Goodbye OneUI vendor.
Happy news to J6+ users: my builds are now supporting j6primelte.
NFC is fixed on NFC variants.
Keystore is now fixed and got rid of aosp's software implementation. You don't need any hacks or tricks to make it work on GSIs.
SIM count detection added, single sim users won't have annoying second sim.
Previous build had dead flashlight sometimes. Fixed.
Removed Samsung's bloatwares.
RIL working delay after boot fixed.
And so much more that I did in past couple of months that I don't remember.
Public Beta 4 - 18/08/2019 :
MTP totally fixed.
Added FM Radio.
NFC should work now on FN users (Current device I have isn't NFC variant. I am not sure).
Public Beta 3 - 27/06/2019 :
Added USB and Bluetooth tethering.
Public Beta 2 - 26/06/2019 :
Lockscreen password fixed.
Audio on camcorder(video recording) fixed.
Autobrightness fixed.
Hotspot fixed.
MTP fixed.
Second SIM Slot fixed.
Public Beta 1 - 25/06/2019 :
First release.
Thanks to abhishek987 for thread template.
Screenshots on attachment.
Note(s) :
Send me logs if you've find any bug.
Reserved for just-in-case.
Please give me credits while building roms and sharing with my sources.
By hitting thanks button and following me on GitHub you can make me happy. Have fun!
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Andhika24kd said:
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Click to expand...
Click to collapse
Yes.
New update released. Enjoy.
ataberkozen said:
New update released. Enjoy.
Click to expand...
Click to collapse
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
rudi021 said:
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
Click to expand...
Click to collapse
Are you also building a ROM?
Geckyn said:
Are you also building a ROM?
Click to expand...
Click to collapse
yes.i build roms.i build also few gsi for j4+ just for test.but mostly for mtk devices.is my first samsung device.is my hobby. i have 55 years.
ataberkozen said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), 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.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Flash RMM Bypass and forceencrypt disabler from TWRP thread.
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Optional: Flash magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-26
Last Updated 2019-06-25
Click to expand...
Click to collapse
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Necrosis Virus said:
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Click to expand...
Click to collapse
Some notes and bugs encountered by me on J415F:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Andhika24kd said:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Click to expand...
Click to collapse
1-) OpenGApps telegram group aware of this problem, wait for them.
2-) Prepaid doesn't show for me too, but others shows.
3-) I'll disable it later.
4-) Send logs from telegram.
5-) I forgot to add lineage livedisplay while creating tree. I'll add next update.
6-) SkiaGL problematic on sd425, 425 phones are using opengl. I had to choose between fixing lags and other ui problems or working screenshot. I choose first one.
7-) You said yourself, removing system apps causes bootloop.
I'll fix it later.
9-) IDK is it problem or not but i am pretty sure isn't bcz of me.
10-) Same 9.
11-) I didn't faced problem while sending mp3, but if u you can send logs i'll check.
12-) Not my problem.
13-) Not bcz of me.
14-) I didn't faced but it's app bug really not my problem.
15-) Not my problem 2.
16-) You said yourself install gboard.
17-) Accent colors is overlay based. Bug isn't from my side.
1 App feature missing or buggy. Idk java I cannot fix.
19-) It's not problem by me, even official devices same.
20-) I am aware of this problem. I need to find a way to change it to rssi.
21-) Isn't this point of DND ? I am busy don't send me any notifications ?
22-) Set ro.lcd.density to 280 with build.prop editor and report back.
Sorry I'm quiet busy nowadays (and I'm sure you are). I will upload the log (you mean logcat, right?) when I have time. Yeah, some of these bugs are actually features on AOSP/LineageOS, I'm just informing other users in case it's their first time switching from Samsung ROM to LineageOS or AOSP based ROM.
11) I didn't use the Bluetooth directly, Google Play Games used it to find a match with nearby player on the game "Bowmasters", will send logcat later.
16) Installing Gboard doesn't help, I already tried that 3-4 days ago.
19) Yes, I'm just informing the others in case they never tried LineageOS/AOSP before. However some unofficial LineageOS have that. Of course I'm not asking you to make/merge it, I don't care about themes.
22) Setting it to 280 doesn't help so far, but I think I need more time to see if it works or not.
Andhika24kd said:
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
Click to expand...
Click to collapse
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
breversa said:
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
Click to expand...
Click to collapse
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
ataberkozen said:
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Click to expand...
Click to collapse
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
breversa said:
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
Click to expand...
Click to collapse
MTP fails while copying from phone to pc.
Related
{
"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.
Hi,
{
"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"
}
Android Open Source Project 9.0 Pie for Huawei Mate 10 Lite
*** Beta Version ***
About
Code:
[CENTER]Android is an open source software stack created for a wide array of devices with different form factors. The primary purposes of Android are to create an open software platform available for carriers, OEMs, and developers to make their innovative ideas a reality and to introduce a successful, real-world product that improves the mobile experience for users.
[/CENTER]
Warning
Code:
[CENTER] * 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.[/CENTER]
Working
Code:
[CENTER]* Boot
* Touchscreen
* Adb
* Audio
* Bluetooth
* Camera
* Internal/External storage
* Sensors
* Wifi
* RIL
* NFC
* Almost everything
[/CENTER]
Not Working
Code:
[CENTER]
* Hotspot Wifi
maybe there are some minor issues !
[/CENTER]
Note: At first boot maybe you will get a bootloop to bootanimation but after it your device will boot up.
Installation
Code:
[CENTER]* you must also have this recovery version installed : TWRP(make sure you got latest version installed!)
* go to TWRP and do format data and then a full wipe (system, data, cache, dalvik/art cache) !
* install AOSP rom
* flash gapps and root (optional)
* reboot to system
* Enjoy !!![/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/askucciodevelopment/files/ROM/Aosp-Pie9.0/aosp-9-20180822-hi6250-askuccio.zip/download"]aosp-9-20180822-hi6250-askuccio.zip[/URL]
[URL="https://github.com/ianmacd/MagiskBuilds"]Magisk Builds for Huawei/Honor[/URL]
[URL="https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141"]Unofficial OpenGapps[/URL]
[/CENTER]
NOTE: These gapps are unofficial and are in beta stage so you can maybe face a lot of crases. It is recommended to install it after first boot and once installed you need to unistall Setup wizard because it will crash a lot !
Credits
@Askuccio_DROID
@flex1911
@phhusson
@haky 86 @Dil3mm4
Kernel GPL policy: We are not violating kernel gps policy because we are making a treble based rom, so it is just a system image. Kernel is the default one provided by Huawei in Emui 8.x
I don' t have the device for testing, if you want faster releases please contribute for buying it. Thanks
DONATIONS
Regards !
XDA:DevDB Information
Android Open Source Project, ROM for the Huawei Mate 10
Contributors
DarkJoker360
Source Code: [url]https://github.com/DarkJoker360[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 9.0
Beta Release Date: 2018-08-26
Created 2018-08-26
Last Updated 2018-08-27
Reserved
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
You could send screenshots of the rom? Please
@connnor kenway, Of course Here are some screenshots, as you wish. They're mostly done after I backed up stuff, so the wallpaper isn't the same and there are a lot of apps installed already At first, there are only apps that provide basic functionality of the phone such as clock, camera, gallery, file manager, music, calc, dialer, messages etc. but there's no browser, only WebView Shell. If you need any other screenshots, just tell me, I'll attach
What's the most exciting for me is that Digital Wellbeing Magisk module works here so it's great Fingerprint scanner works seamlessly as well, better than on stock EMUI ROM And it boots faster too! It's visible for the first sight, but I also tested it vs other Mate 10 Lite with stock EMUI without root, with locked bootloader etc. and the difference was really noticeable, not miliseconds, but seconds. Over 5 seconds less, I suppose.
Also, for me, official Magisk 16.7 works too, so I guess it's not necessary to use ianmacd builds?
I have two things to ask tho. Front camera has native 9.7 Mpix 18:9 option, but the rear one does not (only 2.1 Mpix and 0.9 Mpix are available I believe). Is there possibility to include one? Also, will there be any kernel with possibility to change SELinux to permissive?
From bugs, there are a few I have noticed, but they're rather minor. I'll leave a list here:
- Wi-Fi HotSpot is not working [known]
- USB options are greyed out [known, I guess]
- while transfering big files through USB OTG, USB stick disconnects and reconnects after a second
- sometimes white line between navigation bar and black-themes apps (such as YT Vanced)
- sometimes camera randomly doesn't work after reboot
- Viper4FX always needs to reinstall driver (idk if ROM's issue, but had everything running well on other phones)
- Magisk Manager crashes when checking SafetyNet status got fixed, probably issue of Magisk Manager rather than OS itself
SevenUp9 said:
@connnor kenway, Of course Here are some screenshots, as you wish. They're mostly done after I backed up stuff, so the wallpaper isn't the same and there are a lot of apps installed already At first, there are only apps that provide basic functionality of the phone such as clock, camera, gallery, file manager, music, calc, dialer, messages etc. but there's no browser, only WebView Shell. If you need any other screenshots, just tell me, I'll attach
What's the most exciting for me is that Digital Wellbeing Magisk module works here so it's great Fingerprint scanner works seamlessly as well, better than on stock EMUI ROM And it boots faster too! It's visible for the first sight, but I also tested it vs other Mate 10 Lite with stock EMUI without root, with locked bootloader etc. and the difference was really noticeable, not miliseconds, but seconds. Over 5 seconds less, I suppose.
Also, for me, official Magisk 16.7 works too, so I guess it's not necessary to use ianmacd builds?
I have one thing to ask tho. Front camera has native 9.7 Mpix 18:9 option, but rear does not (only 2.1 Mpix and 0.9 Mpix I believe). Is there possibility to include one?
From bugs, there are a few I have noticed, but they're rather minor. I'll leave a list here:
- Wi-Fi HotSpot is not working [known]
- USB options are greyed out [known, I guess]
- while transfering big files through USB OTG, USB stick disconnects and reconnects after a second
- sometimes white line between navigation bar and black-themes apps (such as YT Vanced)
- sometimes camera randomly doesn't work after reboot
- Viper4FX always needs to reinstall driver (idk if ROM's issue, but had everything running well on other phones)
- Magisk Manager crashes when checking SafetyNet status
Click to expand...
Click to collapse
Did you install it on a stock ROM? What recovery did you use?
Hi I just install This ROM, I've noticed that when I open setting text texture has low quality. Sometimes blurry.
connnor kenway said:
Did you install it on a stock ROM? What recovery did you use?
Click to expand...
Click to collapse
Yes, I installed it on stock EMUI 8.0.0.334. I used CATUVA21's TWRP.
Allan C. E said:
Hi I just install This ROM, I've noticed that when I open setting text texture has low quality. Sometimes blurry.
Click to expand...
Click to collapse
Didn't notice such bug... Or if you mean some weirdly satisfying "shadow" glitch in apps section then yes, but this gets fixed after all the apps' size gets calculated.
Also noticed that blur all over the ROM right now, with some exceptions such as homescreen, notification bar rolled down or typing. I checked "Disable HW overlays" in Developer options and it fixed the issue, everything is sharp right now. Cheers!
SevenUp9 said:
Didn't notice such bug... Or if you mean some weirdly satisfying "shadow" glitch in apps section then yes, but this gets fixed after all the apps' size gets calculated.
Also noticed that blur all over the ROM right now, with some exceptions such as homescreen, notification bar rolled down or typing. I checked "Disable HW overlays" in Developer options and it fixed the issue, everything is sharp right now. Cheers!
Click to expand...
Click to collapse
Disabling HW overlays fixed my issued. Thanks for info bro. Now I can fully enjoy android pie ?
SevenUp9 said:
Yes, I installed it on stock EMUI 8.0.0.334. I used CATUVA21's TWRP.
Click to expand...
Click to collapse
What modules do you have installed bro?
I've got a question to other users - could you please check SafetyNet status with Magisk Hide enabled and Core mode (to avoid module interference)? For me both basicIntegrity and CTSprofile are false, but idk if it's ROM or rather something with my previous EMUI install (had a few situations where I had corrupt installs that would not pass SafetyNet, I guess).
About modules... These are the modules I use, but keep in mind I don't know if GPU Turbo works and Unified Hosts Adblock downloads hosts, but does not block ads.
SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
Hi! How do you solve the problem with the setup, i check the gps but keep showing the message.
Thx for any help:laugh:
@EeN4, simply check all the permissions for Google Play Services and Pixel Setup in settings and reboot, it should do the trick and the setup should begin shortly.
SevenUp9 said:
@EeN4, simply check all the permissions for Google Play Services and Pixel Setup in settings and reboot, it should do the trick and the setup should begin shortly.
Click to expand...
Click to collapse
I tried the solution you gave me but it doesn't work , i'm gonna reflash the rom and see if that work.
wish me luck hehehe.
thx for the help.
SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
camera just dont start at my device. i installed like instructions, what can i do?
@richmaster1o2, try to reboot your phone a few times and if it doesn't work, maybe reinstall the ROM. I experienced 3 times when camera simply would not work after rebooting and I had to reboot one more time. Maybe that's the case
Any update?
can i installed it at locked bootloader?
Sent from my RNE-L21 using Tapatalk
vip.bnda said:
can i installed it at locked bootloader?
Click to expand...
Click to collapse
No, you can't
{
"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, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
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 based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Builds
- TWRP : Get here
Bugs
You tell me
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
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.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
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. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
XDA:DevDB Information
LineageOS, ROM for the Moto G6 Plus
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Stable
Created 2018-10-22
Last Updated 2018-12-28
Copy Partition- Initial Setup
Flash the attachement via TWRP
Fantastic, can't wait to try this! :good: The copy-partition zip seems to be missing though? :crying:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Daniel47833 said:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Click to expand...
Click to collapse
Yes.
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Mara-X said:
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Click to expand...
Click to collapse
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
RokCruz said:
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
Click to expand...
Click to collapse
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
Try with opengapps nano package
Sent from my g(6) plus using XDA Labs
Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
? The data transfer tool and Pixel set up both require notification access. Should solve the issue. ??
ksk35695 said:
The data transfer tool and Pixel set up both require notification access. Should solve the issue.
Click to expand...
Click to collapse
Hello, how can I give notification access to the pixel set up? I can't find the option
Daniel47833 said:
Hello, how can I give notification access to the pixel set up? I can't find the option
Click to expand...
Click to collapse
Goto Apps & notifications, scroll down to Special app access, There's the noticfication access around the middle of the list.
Always has worked for me in this senario. Good luck.
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
weazie said:
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
Click to expand...
Click to collapse
I'm not going to test emergency services.
Moto actions do work-and this is why you don't see a navbar on setup. Fingerprint gestures, swipe right to left to go back,tap for home, left to right for recent, long press for assistant.
Copy partions- this should let you dual boot roms. So los15.1 on slot a and slot b can have Los16. The twrp reboot screen can allow you to choose your boot slot.
Gapps-you can use any gapps really just be sure to flash them if you flash a rom update. I like opengapps arm64 nano builds myself. Then install Google apps from play store.
Twrp- we have to wait for devs to deal with this. It will be fixed in time if it's not fixed with the new official twrp(I haven't tested it yet). It only applies to internal storage. SD card won't be scrambled.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Moto actions do work-and this is why you don't see a navbar on setup.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Click to expand...
Click to collapse
Great, thanks for clarifying
My post above is written as I go through the setup, therefore a mess.
External SD resides at /mnt/media_rw/(sd_card_name).
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Just to clear up something the reason mavnar isn't shown is you need to use fingerprint gestures. Swipe left to right for recent, tap for home, swipe left to right to go back. Then you can activate navbar in settings after set up.
Sent from my Moto G6 Plus using XDA Labs
weazie said:
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Click to expand...
Click to collapse
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Alpetrus said:
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Click to expand...
Click to collapse
yes, it seems so. I asked this question in Adobe Support, but didn't get a satisfactory answer.
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
DocFallingApart said:
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
Click to expand...
Click to collapse
Have you enabled microphone permissions from settings - apps?
{
"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 an UNOFFICIAL build.of LineageOS 18.1 based on Android 11 for the OnePlus 7T Pro 5G Mclaren. Some LOS specific features haven't been re-imported yet so, just be aware. I did NOT create this ROM, it is an Open Source project by the community for the community and has many many contributors , some from this very thread!. thanks to all who have contributed to CyanogenMod/LineageOS over the years.
Supported device: OnePlus 7T Pro 5G McLaren (hotdogg)
Click to expand...
Click to collapse
Code:
[B]IMPORTANT[/B]
* Builds are done when they are done, and not a second sooner. Please no build begging.
* Do NOT be rude.
* If you don't get a reply from me in a timely manner about your bug, sorry i do this in my spare time
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
Built from latest LineageOS/Android 11 source
Service
Text
Data
Call
VoLTE/WiFI Calling/IMS/5G]
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Video recording
NFC
Standalone 5G
??? You tell me
Unlock Warning:
By unlocking a OnePlus phone, you can loose permanent functionality in fingerprint scanner and OTAs for Stock ROMS if improper steps are taken.
Please see 2rd post for backup instructions BEFORE flashing this or ANY custom ROMs
Join our Telegram Chat for added support
PAY ATTENTION!! DIFFERENT THEN MOST DEVICES! CURRENTLY TWRP DOESNT SUPPORT OUR DEVICE SO FASTBOOT MUST BE USED INSTEAD! GAPPS IS ALSO INCLUDED IN THE BUILD DUE TO SAME LACK OF TWRP!
(if you are comfortable with fastboot just run the following commands from fastbootd, if you are unsure of the procedure please read on IT IS DIFFERENT THEN TWRP!
Code:
(boot to bootloader)
fastboot reboot fastboot
fastboot -w
fastboot update lineage-18.0-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Boot to bootloader
from terminal/command prompt: fastboot reboot fastboot
(Don't forget the above step! This will bring us into fastbootd mode. Regular bootloader/fastboot doesn't have access to all needed partitions for flashing. You will see 'partition not found' errors)
Note: In order to access fastbootd mode, we must have stock recovery flashed until TWRP is fixed
if you are coming from a different rom wipe userdata by typing fastboot -w
now type fastboot update filename.zip where filename is the name of the downloaded zip. (e.g, lineage-18.0-20200723-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip)
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Devs
@mjevange
@omariscal1019
@OC'D
Me
Not expected by any means but always brings a smile to my face when I see it, If anyone wants to Paypal me a couple bucks my way it would really help cuver all the coffee and smokes i go through debugging stuff haha
Thanks and happy flashing!
[*] See Post 3
[*] See Post 3
XDA:DevDB Information
LineageOS 18.0 | Android 11 for OnePlus 7T Pro McLaren (hotdogg), ROM for the OnePlus 7T Pro McLaren
Contributors
albinoman887
Source Code: http://github.com/Team-Hydra
ROM OS Version: Android 11
ROM Firmware Required: Must be on 10.0.39 Modem or higher for full support
Based On: LineageOS
Reserved
Unlock Warning:
- This matters only if you ever want to revert to OnePlus ROMs or a fully stock phone
- Choose a method below to get backups BEFORE unlocking to prevent this
- persist.img and reserve.img are most important, but get full dump/backup to be safe
- If you need help, join our Telegram Chat
Getting your phone into EDL mode
Code:
- While holding {Vol+} & {Vol-}, insert USB
- Your screen will remain blank, you will immediately be in EDL mode
- You will have 10 seconds to interact with EDL mode, or the phone will restart into Charging mode
- If an EDL mode interaction fails, you will need to first reboot into fastboot by holding {Vol+} & {Vol-} & {Power} for 10 seconds
MSM Readback (Windows Only)
Download Tool
Grab any MSM Tool version
Obtain Backup
- Launch tool
- Select Target 'TMO'
- Press F8 (password is 'oneplus')
- Select Partitions & Hit OK
(persist.img and reserve.img are very important, but can't hurt to have a copy of everything, use Ctrl-A to select all)
- Put phone in EDL mode (SEE NOTE)
- Enumerate device
- Click Readback & Wait
EDL Tool Backup (Linux Only)
Obtain the tool
Use GIT:
Code:
~$ git clone [email protected]:bkerler/edl.git
—or—
Download ZIP: https://github.com/bkerler/edl/archive/master.zip
Prep
Use the included README for required packages / setup
Pay attention to UDEV rules, python, and pip
Backup
In the edl folder:
- Create folder named dumps
- Put phone in EDL mode (SEE NOTE)
- Use edl.py:
Code:
~$ ./edl.py rl dumps/ --memory=ufs --genxml --skip=userdata
Mar 3
* Major Release, do a full wipe if you have problems. I actually STRONGLY recommend a full wipe anyways.
* For all intents and purposes this is a Stable release. I've done extensive testing and everything has worked as it should or above and beyond. Now on to the updates
* A lot of just under the hood optimization and cleanup. There some configuration options that weren't exactly optimized for our device, dalvik config is a good example.
* 5G support is on par with stock ROM, if not better.
* Auto brightness has been improved
* Some cosmetic issues have been addressed like status bar padding and FOD icon centering.
* Fixed a wakelock issue when using Always on Display
* Adjustable display refresh rate code has been improved.
* Updated vendor libs from hotdog Android R OB2 to allow full use of Android 11 Display HAL
* Added Stereo in call recording support
* Various audio fixups, including increasing volume steps from 7 to 15 and raising the max volume level to be on par with stock OOS
* Optimized Always on Display: fixed wakelock issue, lowed default AOD brightness, as well as enabled auto brightness when on AOD if enabled by user within settings
* Many upstream changes, fixes, and improvments.
** This will most likely be my final release as i have moved on to the Snapdragon variant of the Note 20 Ultra 5G. Thanks for the support guys and I hope you enjoy my work. Hopefully someone will pick up where I left off.
Dec 26
* Merry Christmas!
* Updated ROM base to lineage-18.1
* Notification pull-down menu now shows 3 rows of tiles as expected
* Added "Minimum Refresh Rate" settings option in Settings > Display instead of hard-coding to 90htz always. With this new option choosing 90htz will (obviously) make it always 90htz , and choosing 60htz is similar to the "Dynamic" option in stock OOS where it decides based on what app your using.
* (With version 18.1 most, if not all of the expected LineageOS features have been merged)
* Fixed "choppy" display frame rate that would happen from time to time
* Fingerprint recognition speed improvement.
* Fixed excessive battery drain when Always On Display is active
* Update dalvik configs (they were configured for an 8GB RAM devices, we have 12)
* UI: Enabled blur
* Fixed IMS from spamming system logs
* Fixed booting with SELinux Enforcing on "user" build types
* Enabled SELinux enforcing
Nov 20
* Fixed up all the small bugs from test build
* Standalone 5G (NR SA) support, requires being on 10.0.39 or newer modem. Also be aware the signal icon will show no bars when connected to NR SA, this is just a cosmetic bug.
* Updated audio configs to to match OOS 10.0.39
* Added audio volume policy , should fix the lower then normal volume when below 50%
* SELinux is currently set to "Permissive" until I work out all the sepolicy errors
Oct 14
* Initial internal test Release
[ROM]: lineage-18.1-20210303-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Gapps: TEMP INCLUDED WITH ROM IMG UNTIL ITS FLASHABLE VIA CUSTOM RECOVERY
[Download Archive]: All ROMs
https://github.com/LineageOS
https://github.com/Team-Hydra/android_device_oneplus_sm8150-common
https://github.com/Team-Hydra/android_device_oneplus_hotdogg
https://github.com/Team-Hydra/android_kernel_oneplus_sm8150
https://github.com/Team-Hydra/proprietary_vendor_oneplus
Thank you
90hz not showing in display or anywhere else?
Thanks man, just showed my appreciation via PayPal. Happy Thanksgiving! This build rocks. Passes safetynet with props module spoofing a Oneplus 8. Or you wouldn't be getting that stuffing! Stable as hell, everything working for me so far. Happy Holidays to all
when tryping fastboot reboot fastboot it says "fastboot: usage: unknown reboot target fastboot"
Is there any chance this would work on the Sprint OnePlus 7 Pro 5G? If not are there any roms that do currently work for Sprints model
Globel said:
when tryping fastboot reboot fastboot it says "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
your using an outdated fastboot binary on your pc. download latest version
skyrmion said:
Thanks man, just showed my appreciation via PayPal. Happy Thanksgiving! This build rocks. Passes safetynet with props module spoofing a Oneplus 8. Or you wouldn't be getting that stuffing! Stable as hell, everything working for me so far. Happy Holidays to all
Click to expand...
Click to collapse
Thanks so much man that meant a lot to me
New build uploaded. I recommend everyone to update to it as it addresses the last few bugs i'm aware of and all the LOS specific features are fully merged
I got this installed and it's fantastic. For some reason my camera is capped at 12mp, even on other camera apps. Is there anything I can do about that?
333severs said:
I got this installed and it's fantastic. For some reason my camera is capped at 12mp, even on other camera apps. Is there anything I can do about that?
Click to expand...
Click to collapse
That's normal,even on OOS
First time installing a custom ROM but when I run "fastboot update lineage-18.1-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip" I get an error reading "Fastboot: error: failed to open zip file 'lineage-18.0-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip': I/O error
EDIT: I got it working
I've installed the latest build (18.1, build 12/26), but I can't change notification, ringtone, or alarm through settings. Clicking on any of those restarts the settings app.
EDIT: I tried to do a workaround through tasker, but when I go to choose the sound I get the following popup:
Error: android.content.ActivityNotFoundException: No Activity found to handle intent { act=android.intent.action.RINGTONE_PICKER (has extras) }.
I wasn't able to find a working solution through google. I tried clearing the cache for settings and restarting, but it didn't fix anything. I also can't use the default launcher as it just continually crashes, but the pixel launcher works fine.
factorion said:
I've installed the latest build (18.1, build 12/26), but I can't change notification, ringtone, or alarm through settings. Clicking on any of those restarts the settings app.
EDIT: I tried to do a workaround through tasker, but when I go to choose the sound I get the following popup:
Error: android.content.ActivityNotFoundException: No Activity found to handle intent { act=android.intent.action.RINGTONE_PICKER (has extras) }.
I wasn't able to find a working solution through google. I tried clearing the cache for settings and restarting, but it didn't fix anything. I also can't use the default launcher as it just continually crashes, but the pixel launcher works fine.
Click to expand...
Click to collapse
hmmm. i'll take a look. tbh i restored stock like a week back to get updated libs and then my ISP was having all types of issues , one thing lead to another. blah blah blah.. i'm back now though
does this have pocket mode? or check proximity sensor before wakeup?N im happy your back
Also I dont seem to get the same signal as on aosip or oos not sure why switched it to global and im on the new sim
Great ROM so far! Just got one thing to add. Anyone seeing low WiFi signal? My house isn't big at all but when I'm in the kitchen, which is about 20 ft away form the router, it'll keep switching between data and wifi because it says the signal is poor. My gf's stock pixel is at full bars in the kitchen. Any thoughts? Also, I reflashed and still same issue.
I've been watching this therad ever since you released it, and it looks to keep getting better,, so kudos to you man! I have the T-Mobile variant on the Mint netowork, so I'm always afraid to try anything but I haven't done much research on if you can flash it to a T-Mobile device. Let me know, thanks!
Dopewaffles said:
I've been watching this therad ever since you released it, and it looks to keep getting better,, so kudos to you man! I have the T-Mobile variant on the Mint netowork, so I'm always afraid to try anything but I haven't done much research on if you can flash it to a T-Mobile device. Let me know, thanks!
Click to expand...
Click to collapse
I have the same phone, also went from t-mobile to mint. You have to get oneplus to unlock the bootloader, and then you can follow the flash instructions for the rom (Probably want to do the backup as well, although that wouldn't work for me). If you try it, hopefully you don't have the issues I had with notifications/ringtones.
{
"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