{
"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.
*/
Status : ALPHA 5
This version is mainly for testers but anybody can flash it, since there is no more critical issues :victory:
This build is userdebug flavor. ADB and ROOT are disabled by default.
Installation instructions
First of all, update your Mate to EMUI 4.1 (that has the good kernel version)
Like always: BACKUP, BACKUP BACKUP !
Wipe every partitions (except your SD and your internal storage) See below.
You can flash GApps (see the frequently asked questions below).
Enjoy.
- NXT-AL10, NXT-L29 and NXT-L09 reported as booting
- Xposed reported as working
- Second SIM reported as working (NXT-L29)
Important note : L-09 variant is UNSTABLE for now.
Working
- Since Alpha 1
Partial and temporary GApps implementation
Launchers (Pixel/Google Now)
Themes (include animated)
- Since Alpha 2
RIL
Audio
Microphone
WiFi
Bluetooth
Security (Pin/Password/Pattern..)
GPS over data
Google Apps (include widgets and theme )
HiSuite full compatibility
- Since Alpha 3
SD Card
Tethering (WIFI + BT)
Offline charge
USB Access (MTP/PTP + MIDI input)
OTA Updates (by the built-in CM Updater)
Enhanced boot time (+/- 1min)
- Since Alpha 4
LCD Backlight adjustments
Notification Led
Enhanced boot caching
USB Tethering
Fix sensors
Fix ambiant display
Fix Sleep Of Death (thanks to XePeleato)
Fix FLP (location)
Fix GPS
- Since Alpha 5
RIL Signal
Bluetooth (now considered as stable)
Camera (Both, picture only)
Lineage skin/rebrand
Not Working
Camera (video mode)
Native cast
Fingerprint
Fast Charge
NFC
FM Radio
Known issues:
GPS module(fully working, available in the next release)
Another (ghost) SD Card is recognized and is incompatible with CM -> just ignore it for now. This entry will disappear with the next (OTA) update.
RIL working irregularly on AL-10 (unconfirmed) and L-09 devices
Offline charge not working (fixed, available in the next release)
You prefer to wait for a fully working ROM
You can follow the porting status here : https://github.com/PaulFasola/android_device_huawei_next/projects/1
Downloads
Current release, Alpha 5
Click here
Do a full wipe before installing this update or you could try the (risky) migration tool
Previous release, Alpha 4
Click here
Archives
Click here
Source Code
https://github.com/PaulFasola/android_device_huawei_next
You'll find the kernel and the vendor repos as well (check the readme)
Donators
android09
danywalkert
Azti Iluna
basimzanaty
drairoh
My dear tester Kingzak34
Many thanks to you guys !
Credits
* Nexolight for the useful advises
* Meticulus for the glitchy screen issue!
* Surdu_perdu's work for some ramdisk issues!
* _Ekko (freenode) for his help on the rild issues (symbols, symbols symbols...) and rild proper init
XDA:DevDB Information
[ROM][6.0.1][UNOFFICIAL] Lineage OS 13 Port, ROM for the Huawei Mate 8
Contributors
_skypol0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: No Longer Updated
Created 2016-12-05
Last Updated 2017-09-15
Reserved
Changelogs
Alpha 3.1 - OTA only
LCD Backlight (manual update, temporary disable adaptive brightness and sensors are still off-line)
Leds (charge/notification etc..)
Drastically reduce battery consumption
Better boot caching for apps optimization
Bases for enabling the sensors soon
Fix in-game latency for complex animations (like 3D transitions)
Alpha 5.1 - (Full)OTA / download
Link: click here
Fully fix the GPS (satellites acquisition, bad wakelocks...)
Fix offline charge (animation) and adjust the settings for a faster charge (rapid charge still In the to-do list).
Have the latest LineageOS 13 core changes
Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:
FREQUENTLY ASKED QUESTIONS
I come from EMUI 4.1, can I flash this ROM ?
Yes, but you will need to full wipe and follow the instructions in OP
I'm on EMUI 5.X or 4.0, can I flash this ROM ?
You should roll back to EMUI 4.1 then follow OP instructions
My phone is asking for a password on boot
The master key of the old EMUI is not known and that's why we had to wipe userdata (this remove encryption).
So, that means that your Data partition is not wiped, and you have to wipe it !
Flash the Cyanogenmod recovery (built with this ROM, located in the same folder) and do a full factory reset, this work everytime.
Once done, reboot and flash this custom TWRP that handle non-encrypted userdata. You will be able to open the SD Card, flash whatever you want and restore your backup.
NB : If you flash back the stock ROM, this last will re-encrypt /data and everything will work as always.
I've waited for 10 minutes and the Cyanogen boot animation is still here
Something is wrong and prevent CM to complete the boot sequence. This is an issue to report (see below).
This ROM does not contain GApps, what should I take ?
You can find GApps package on OpenGapps
You'll need to take for ARM64 and Android 6.0 and then choose the package you want.
Tested so far : Full, Stock, Nano
I've found an issue
First of all, thanks for helping @_skypol0 !
> Open a ticket here <
Check if there is not a similar issue before posting
Fill the issue (Your device infos (kernel version, last EMUI update version etc.) , What is the problem ?, how can we reproduce it ? etc. Please put as many information as possible)
Share a paste/haste/ghost/...bin of your logcat and dmesg
Wont use it but thanks for developing it (i dont like roms based on clean android). Might be a huge step in futrue development on Mate family.
Awesome!!
Man, you've convinced me not to sell my mate 8 anymore, It's great potential. I'm looking forward for the beta version of this!
Was going to sell my mate 8 also. But now will test once basic functions are ok.
khanem said:
Was going to sell my mate 8 also. But now will test once basic functions are ok.
Click to expand...
Click to collapse
RIL an audio should be fixed with the next release later this week
I'm excited for Alpha 2
UnchartedRd said:
Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:
Click to expand...
Click to collapse
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)
_skypol0 said:
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)
Click to expand...
Click to collapse
No problem, I'll post on github if I find anything else
You mean B320?
Thanks for your effort friend, I'll definitely be glad to test it once it gets a bit more stable.
Oh my god... it's really happening...
Once SD support works, I'll glady test this on my NXT-L09.
THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!
albertwesquer said:
THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!
Click to expand...
Click to collapse
Huawei hasn't released a stable build of nougat yet, its only been beta builds. Once Huawei releases nougat for M8, he can work on it.
And on the other side Cm14 is far from stable
Tapatalké depuis mon MEGA Mate 8 !
well i didnt know we had to have nougat in our mate 8 in order to have cm14, in that case cm13 should be ready since 6.0 have quite some time in our device! SO THERE'S HOPE!
Amazing I cant beileve im really seeing it
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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lolipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code:
device
kernel
vendor
Discussion thread -->
What's working:
so far i have tested:
RIL (Calls, SMS, Mobile Datal)
Display
Camera (photos, camcorder & panorama)
Audio and video
Wifi
Bluetooth
OpenGL rendering
Sensors (accelerometer,compass,light,proximity)
Sdcard
auto brightness
notification led
GPS
NFC
Wifi,Bluetooth and USB tethering
Not working/Tested:
offline charging somewhat working.
other everything is either untested or broken.
Note:
It's entirely possible that features not used by me (nor the people I've asked to test) are broken, but overall the device should be usable. You have been warned.
Because of art 1st boot take long time so don't panic and make post saying phone stuck on bootanim,
xperia m dual not support in cm12.0
This is BETA so don't treat this as stable version.
Download:
Nightly Builds: http://download.cyanogenmod.org/?device=nicki&type=nightly
Last nightly build mirror: Link
FXP CM12.0 Builds: http://fxpblog.co/cyanogenmod/cyanogenmod-12/
GAPPS: https://s.basketbuild.com/gapps
Note : CM-12.0 is only for 4.3 baseband. If you are on 4.1/4.2 baseband/firmware then Follow this instruction
Install instructions: (For 1st time only)
boot into fastboot (ignore if you coming any 4.4 rom)
flash boot.img from cm12.0 zip (ignore if you coming from any 4.4 rom)
boot into custom recovery
Wipe data and cache
Flash the CM12.0 and gapps zip
Reboot
Upgrading from earlier version of CyanogenMod 12.0:
Boot into Recovery
Flash CM12.0 zip
Reboot
Reporting bugs:
Before Reporting bugs make sure you
Read "note" section
Using stock kernel
Not installed any mods/tweaks - if you have installed mods like xposed you can't report bug
Not modified system files
Checked the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe (do this if mods like xposed is installed) and check if the bug is still there
provide logcat,kmsg. if you reporting radio problem then provide radio log.
Screenshots:
Credits.
Fxp team and all other developer who is working on sony
Code Aurora Forum
CyanogenMod Team
Cybojenix
And Special Thanks to All Donors
XDA:DevDB Information
CyanogenMod 12.0 for Xperia M, ROM for the Sony Xperia M
Contributors
PecanCM
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.3 Firmware
Version Information
Status: Nightly
Created 2014-11-21
Last Updated 2015-05-28
Changelog
BETA 3 23-01-2015
Android 5.0.2 (LRX22G)
Fixed problem with YouTube vidoes
Fixes for other video problems
Fixed baseband version
Fixed no bootanimation on 1st boot
Working mass storage and charging only modes
Enabled FM
Updated widevine(DRM) blobs to lollipop
Updated adreno Blobs to LA.AF.1.1(lollipop)
Updated Kernel and Prima Wlan to LA.AF.1.1_rb1.8
Addressed more selinux denials
General cleanup and fixes
Updated cm source
BETA 2 19-12-2014
Updated to Android 5.0.1 (LRX22C)
Misc fixes
Enabled apps2sd
Disabled lpa
- incompatible with NuPlayer
Using cm recovery now
Updated Adreno blobs
Update kernel and prima wlan to LA.AF.1.1_rb1.7 branch
Updated cm source
BETA 1 28-11-2014
Fixed gsm issue after rebooting phone
Enabled multiColor battery led
Enabled 1080p decoding
Updated kernel and wifi driver to LA.AF.1.1_rb1.6
Updated cm source
ALPHA 1 21-11-2014
Initial release
FAQ
Q: The 'Developer and Performance options' from 'settings' are gone. Where are they?
A: Touch the 'Build number' seven times in 'about phone'. Then they will appear.
Q: I'm coming from 4.1 and now i can't view my internal sd data, Why ?
A: Go to Data/media now move your all internal sd data to folder named 0 Means under /data/media/0 then you can view your internal sd data
What about GApps? We can use 4.4.4 for now?
kosmita1993 said:
What about GApps? We can use 4.4.4 for now?
Click to expand...
Click to collapse
added gapps link in 1st post use that,
First bot is very very long, for me it was about 7-10 minutes. Wifi/Bt isn't working for me, NFC probably works because it can read my smarttags.
Great job!
BTW are you planning aosp build too?
omg this interface is so fancy I'm so exited XD
Time to edit Discussion Thread !
Awesome, will try this as soon as wifi gets fixed
Great work PecanCM
I flashed this rom .... 1st it took very time to boot but it booted.
everything was working good but wifi and bluetooth are not working. Hope it gets fixed by @PecanCM in the next build.
I cannot use it now but will use when wifi and blutooth gets fixed
GSM detection came on the 1st boot so there ws no need to reboot
For now this is all .. Hope it gets BETA in the next build !!!!
Thank You !!!
@PecanCM , can I downgrade the ROM after flashing CM12 (like , 5.0 to 4.4.4 ) ?? or (CM12 to CM11) ??
EliXer9 said:
@PecanCM , can I downgrade the ROM after flashing CM12 (like , 5.0 to 4.4.4 ) ?? or (CM12 to CM11) ??
Click to expand...
Click to collapse
Yes
Sent from my C1904 using Tapatalk
Is WiFi working ? (Because it's included in both the sections. i.e , working as well as not working) ?? And sorry if it's a stupid question
EliXer9 said:
Is WiFi working ? (Because it's included in both the sections. i.e , working as well as not working) ?? And sorry if it's a stupid question
Click to expand...
Click to collapse
No, not yet.
iddu.daragah said:
I flashed this rom .... 1st it took very time to boot but it booted.
everything was working good but wifi and bluetooth are not working. Hope it gets fixed by @PecanCM in the next build.
I cannot use it now but will use when wifi and blutooth gets fixed
GSM detection came on the 1st boot so there ws no need to reboot
For now this is all .. Hope it gets BETA in the next build !!!!
Thank You !!!
Click to expand...
Click to collapse
strange both works fine for me
give me logs and if you are on pc then run following and upload audit.log file.
Code:
adb root
adb shell
cat /data/audit/audit.log > /sdcard/audit.log
GSM, BT and GSM not working on my C2004
expecting for the next release! :good:
iks8 said:
First bot is very very long, for me it was about 7-10 minutes. Wifi/Bt isn't working for me, NFC probably works because it can read my smarttags.
Great job!
BTW are you planning aosp build too?
omg this interface is so fancy I'm so exited XD
Click to expand...
Click to collapse
iddu.daragah said:
I flashed this rom .... 1st it took very time to boot but it booted.
everything was working good but wifi and bluetooth are not working. Hope it gets fixed by @PecanCM in the next build.
I cannot use it now but will use when wifi and blutooth gets fixed
GSM detection came on the 1st boot so there ws no need to reboot
For now this is all .. Hope it gets BETA in the next build !!!!
Thank You !!!
Click to expand...
Click to collapse
flash zip from recovery or boot.img from this zip via fastboot https://www.mediafire.com/?45dz5xd8edh7ydn i forgot to commit a change and later removed by git stash this can be the reason otherwise i'm going to need logs.
and no i'm not planning aosp atleast not for few weeks
jhuy said:
GSM, BT and GSM not working on my C2004
expecting for the next release! :good:
Click to expand...
Click to collapse
read note section in 1st post.
PecanCM said:
flash zip from recovery or boot.img from this zip via fastboot https://www.mediafire.com/?45dz5xd8edh7ydn i forgot to commit a change and later removed git stash this can be the reason otherwise i'm going to need logs.
and no i'm not planning aosp atleast not for few weeks
read note section in 1st post.
Click to expand...
Click to collapse
Yes! Now it is working, your perdictions was correct. Thanks a lot!
Thanks wifi and bluetooth working now
after flashing new_boot image
jhuy said:
GSM, BT and GSM not working on my C2004
expecting for the next release! :good:
Click to expand...
Click to collapse
Try to get root, then type this in terminal emulator.
su setprop persist.radio.multisim.config dsds
Sent from my C2005 using XDA Free mobile app
Someone can mirror it? I am not able to download from mediafire, it just restart the download each time.
Sent from my C1904 using Tapatalk
This rom is based on CodeAurora's Android Lollipop 5.1 source (AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.01.01.006.028).
I have only made changes that needed to support our device other then that it's pure CAF/AOSP. it has no custom features to provide you stock android experience.
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.
*/
Sources:
CodeAurora
Kernel
What's working:
Almost everything is working including the RIL, camera, audio/video, bluetooth/wifi, sensors, nfc and offline charging.
Know issue:
gps broken, if you find any more issue please report me with logs in this thread.
Note:
It's entirely possible that features not used by me (nor the people I've asked to test) are broken, but overall the device should be usable. You have been warned.
Because of art 1st boot take long time so don't panic and make post saying phone stuck on bootanim,
Dual sim somewhat works. xperia m dual users see this and this post
This is BETA so don't treat this as stable version.
CAF/AOSP is only for 4.3 baseband. If you are on 4.1/4.2 baseband/firmware then Follow this instruction
Download:
BETA 3: https://www.mediafire.com/?o4d0u6p70vqit36
Gapps: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
SuperSU: http://forum.xda-developers.com/showthread.php?t=1538053 (If you want to root your phone)
Install instructions:
Before you install make sure you are on 4.3 firmware 1st with your bootloader is Unlocked and a cwm/twrp recovery installed. if you haven't installed recovery then flash boot.img from this rom zip via fastboot. (note: this rom comes with twrp recovery)
boot into recovery
Wipe data and cache
Flash the rom and gapps zip
Reboot
Upgrading from earlier version:
Boot into Recovery
Flash the rom and gapps zip
Reboot
Reporting bugs:
Before Reporting bugs make sure you
Read "note" section
Using stock kernel
Not installed any mods/tweaks - if you have installed mods like xposed you can't report bug
Not modified system files
Checked the posts below for a solution / fix
Read the last 10 pages of this thread for a post with a similar problem
Backup, reflash with a full wipe (do this if mods like xposed is installed) and check if the bug is still there
provide logcat,kmsg. if you reporting radio problem then provide radio log.
Screenshots:
{
"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"
}
Credits:
Fxp team and all other developer who is working on sony
Code Aurora Forum
CyanogenMod
XDA:DevDB Information
AOSP/CAF 5.1 for Xperia M, ROM for the Sony Xperia M, ROM for the Sony Xperia M
Contributors
PecanCM
Source Code: https://www.codeaurora.org/cgit/quic/la
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Stock 4.3 Firmware
Based On: AOSP
Version Information
Status: Beta
Created 2015-05-22
Last Updated 2015-07-24
Changelog
Changelog:
BETA 3 22-07-2015
Fixed apps2sd
Fixed local language translations for few apps
few music app fixes from msm8916 branch
other misc fixes
Added qcom's file manager
Built with qualcomm's recommended performance patches
Updated proprietary blobs from lollipop
Updated vidc firmware to latest version
kernel synced with cm
BETA 2 20-06-2015
Updated platform source to CAF tag AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.01.01.006.028
Updated Kernel and Wlan source to CAF tag AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.01.01.006.028
Fixed can't send sms
Fixed offline charging
Fixed bootanimation take long time or sometimes never come
Fixed phone app crash for dual sim
Enabled reboot,airplane mode and sound options
Building missing gps hal and other gps updates - gps still not fully working
Removed FM TX
Updated some proprietary blobs
BETA 1 22-05-2015
Initial release based on AU_LINUX_ANDROID_LA.AF.1.1_RB1.05.01.00.006.027 tag
FAQ
Q: The 'Developer and Performance options' from 'settings' are gone. Where are they?
A: Touch the 'Build number' seven times in 'about phone'. Then they will appear.
Q: Why no root access?
A: This is AOSP rom, if you want root then flash supersu
Q: I'm coming from 4.1 and now i can't view my internal sd data, Why ?
A: Go to Data/media now move your all internal sd data to folder named 0 Means under /data/media/0 then you can view your internal sd data.
Is it using "5.1.1-r2" source or "5.1.1-r1"?
Just curious to know...
KHM90 said:
Is it using "5.1.1-r2" source or "5.1.1-r1"?
Just curious to know...
Click to expand...
Click to collapse
as thread title says android-5.1.1-r1
Flashed.
It's soooo smooth. Thanks for this ROM!
Only noticed, that offline charging broken: phone totally hangs on "Sony".
And bootanimtion not fit screen.
Hi All,
Found one really interesting Delta-gapps package, where you get option to choose which add-on you wanna install
(If you prefer to have app on system partition)
[4.4.4 / 5.0.x / 5.1]
http://forum.xda-developers.com/showthread.php?p=58047099
Omg ! So fast and Smooth ! Maybe battery life is better ...
CWM/TWRP recoveries
For those, who don't know or don't remember, here are CWM/TWRP recovery images. Needs to be flashed only once to work.
Sometimes no audio when calling (works for a while after reboot). Also when calling, a blank screen appears from the phone activity making the transition ugly. Bootscreen is a bit large too
Nice rom , thx for your work.
Seems here come with great respond from other, and now i want try to move it too
AOSP I'm coming!!!
and this rom isn't big like other cm or fxp build, is only 212 mb.
Bonoboo said:
Flashed.
It's soooo smooth. Thanks for this ROM!
Only noticed, that offline charging broken: phone totally hangs on "Sony".
And bootanimtion not fit screen.
Click to expand...
Click to collapse
ah totally forgot about offline charging will see.
Ydraulikos said:
Sometimes no audio when calling (works for a while after reboot). Also when calling, a blank screen appears from the phone activity making the transition ugly. Bootscreen is a bit large too
Nice rom , thx for your work.
Click to expand...
Click to collapse
no such issue here. can more users confirm sometimes no audio when calling ?
problem on bootanimation that not fit on screen, on first boot is only black, and after a few second android logo is out.
but isn't critical problem so far
some wifi icon connection state problem, this like icon connection state isn't fit on wifi icon
and for mobile connection data is always show 3g although my connection is HSDPA + when i check on sim information
that's first report from me
Just noticed a problem with location. While location is on and GPS seems to work it says "No apps have requested location". For some reason apps can't access gps. I suspect this and the previous issue with no audio in call might be caused by gapps. Can anyone point me to a tested package of gapps? I used the one by cm12.1
Keyboard Force close ,But imidiately gone ,every time going in settings and pressing back button
Ydraulikos said:
Just noticed a problem with location. While location is on and GPS seems to work it says "No apps have requested location". For some reason apps can't access gps. I suspect this and the previous issue with no audio in call might be caused by gapps. Can anyone point me to a tested package of gapps? I used the one by cm12.1
Click to expand...
Click to collapse
I have also noticed it. Here maps can't locate me on any location setting.
Farsiris said:
Keyboard Force close ,But imidiately gone ,every time going in settings and pressing back button
Click to expand...
Click to collapse
Have you wiped cache/dalvik-cache ?
No force close here.
Ydraulikos said:
Just noticed a problem with location. While location is on and GPS seems to work it says "No apps have requested location". For some reason apps can't access gps. I suspect this and the previous issue with no audio in call might be caused by gapps. Can anyone point me to a tested package of gapps? I used the one by cm12.1
Click to expand...
Click to collapse
maybe you can try lp gapps base from @KHM90
here http://forum.xda-developers.com/showthread.php?p=58047099 this is lollipop gapps base file with add on
and if you want full gapps package you can try my gapps
http://forum.xda-developers.com/showpost.php?p=58373397&postcount=1
it's full gapps package
looks like gps hal not compiled. here is patch for gps hal https://www.mediafire.com/?xglqcu7b29dne10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on 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.
You will need to provide your own Google Applications package (gapps).
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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for unofficial LineageOS 13.0 builds for LG G4 model H815 only.
Its a continuation of the official one as it was abandoned back in July and I still prefer MM (N has still bugs and does not support encryption).
Known issues:
the kernel has security bugs which need to be addressed
its in testing state as I cant test it atm.. please report back! PLEASE MAKE A FULL BACKUP BEFORE TESTING!!
Installation:
First time flashing LineageOS 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install latest TWRP from the official twrp.me website
Perform a nandroid backup of your current ROM (optional but recommended)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
Google Apps:
OpenGApps (choose arm64, 6.0, nano)
TWRP Recovery:
https://twrp.me/devices/lgg4.html
Full Stock ROMs:
H815 V20D
Bootloader:
Remember ---> Flashing bootloader is risky so you flash at your own risk!
H815 V20D
Modem:
H815 V20D
ROM:
Last known fully working is 20170813! Sorry have to fix the blobs first!
Nightlies: http://droid.binbash.it
Sources:
Android: https://github.com/LineageOS
Device: https://github.com/steadfasterX/los_android_device_lge_h815
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8992
G4 common device tree: https://github.com/LineageOS/android_device_lge_g4-common
Proprietary files: https://github.com/TheMuppets/proprietary_vendor_lge
.
XDA:DevDB Information
lineage-13.0-unofficial, ROM for the LG G4
Contributors
steadfasterX, codeworkx, genesixxbf3
Source Code: https://github.com/steadfasterX/los_android_device_lge_h815
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader unlocked, v20A (or greater) bootloader stack
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-08-21
Created 2017-08-21
Last Updated 2017-11-03
FAQ
1. Q: Encryption is not possible?
A: if the GUI for encrypting the device is not working:
Its highly recommended to backup all your data including the internal storage (I recommend FlashFire or / and Titanium)
Flash my screenlock fix (search here at XDA) in TWRP.
Reboot to android.
ensure that you met all usual requirements (battery, screen lock set) and then open a terminal or adb shell. Type:
vdc cryptfs enablecrypto inplace pin 1234
Replace 1234 with your desired pin ofc.
sfX
Reserved
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
steadfasterX said:
the kernel has security bugs which need to be addressed
Click to expand...
Click to collapse
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
thewild said:
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
Click to expand...
Click to collapse
its the same source then the official build (and so genessix) used so it should work the same way but as my device is broken atm and I await repair I cannot test it..
Last time I checked the security patches in my build got increased to July 2017 where the latest official ones had June..
so afaik there should be no critical issues in Android but the kernel is last time updated in May 2016 (should be the same for genessix builds).
My plan is maybe to integrate the Llama kernel and backport fixes from the 14.x tree.
don't expect that this happen in the near future (we can hope though) because atm I'm quite busy with my unofficial unlock stuff.
.
OK I'll keep an eye on this thread then.
Good luck !
Any tester reports?
Netsab said:
Any tester reports?
Click to expand...
Click to collapse
Yes.. I use that ROM with my unofficial unlock testers. Atm I cannot test cell service but it boots up fine, WiFi, cam etc works fine.
sfX
Sent from my LG-H815 using XDA Labs
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
zeduck said:
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
Click to expand...
Click to collapse
thx for testing..
yea I rem that there was a "trick" .. Could you try this build pls: http://droid.binbash.it:58885/h815/lineage-13.0-20170912-UNOFFICIAL-h815.zip
It includes an insecure kernel which will allow to debug.
Factory Reset in TWRP
Flash in TWRP
Boot Android
Enable encryption
when it reboots open a terminal and type (linux or FWUL): while true; do adb logcat ;done
on windows ensure that once the logcat aborts that you restart it immediately again!! and use just adb logcat
if using windows or linux: ensure the terminal buffer is big enough bc thats a a lot to handle.. (go into the settings of the cmd or terminal and set it to a very high value. e.g. 5000000)
let it bootloop and boot into Android again (logcat should run all the time)
CTRL+C when its completed with the above
copy & paste the whole stuff in a text file and attach it here
sfX
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
zeduck said:
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
Click to expand...
Click to collapse
without logs I cannot say anything for sure...
It may can be solved by just typing the encrypt command over adb or it requires to modify the ROM..
If you like you can try the following but keep in mind that having a complete Backup is a good idea always and when I say complete I mean including internal storage which is not be backuped by TWRP!! Use e.g FlashFire app to accomplish this. I would take a TWRP backup for all (use my latest beta!!!) and then FlashFire to backup internal storage.
Encryption often fails to a wrong formatted data partition so this can be a reason as well.
Try this:
Backup as described above
In TWRP select wipe - advanced - press "Format data" button to format the data partition
Boot android
set a pin or password for the lock screen!
Encrypt
If succeeded restore backup with FlashFire
As always there is a risk and it requires some time so I would not recommend to do this on a busy day.. as you say at the weekend fe.
Then we can try to use the adb commands and if that doesn't work as well the logcat..
sfX
Sent from my LG-H815 using XDA Labs
Hi !
I gave a try with lineage-13.0-20170918-UNOFFICIAL-h815.zip that I dirty-flashed over my previous lineage-13.0-20170204-UNOFFICIAL-h815 version.
Everything went fine (I had to replace the su zip/app though), except that satellite location would not work (network location was fine) : I kept getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
I'll give another try with the latest lineage-13.0-20170927-UNOFFICIAL-h815.zip.
If that fails too, I guess I'll have to clean-flash it then.
EDIT :
Bad news : after a clean flash, I keep getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Netsab said:
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Click to expand...
Click to collapse
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
Thanks you, I'll try.
breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
thanks for your report. btw a dmesg is very helpful in these cases but the above should be fixed on next build.
next build will also have all proprietary stuff upgraded to v20p.
sfX
EDIT
new build is up
.
Hey sfX,
When trying to dirty-flash 20170930 over 20170813, the phone gets stuck on the boot animation (for over 30 minutes).
I did not try to clean-flash it though ; I thought I'd let you know first.
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICIAL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
datorprofessor said:
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICAIL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
Click to expand...
Click to collapse
Better wait until I fixed the current nightlies..
nice app btw. when all is fixed i may take a look into it
Sent from my LG-H815 using XDA Labs
Code:
#include <std_disclaimer.h>
/*
* 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 atyou.
*/
Hi everyone, here is my port of Oreo on OnePlus 5. Source is based on AOSP android-8.0.0_r3 (r9 since 20170916, r15 for 20171008), as it's for Pixel. Device repo, kernel and vendor etc are available at the end of the post.
And the same note as before: this ROM is highly experimental, and only meant for the brave ones. I may not update this work regularly.
Hardware features:
Things went more smoothly than before.Majority of hardware features are working, including mobile network, WiFi, Bluetooth (file transfer, network, audio etc), GPS, camera / camcorder, fingerprint, sensors, HW-based encryption etc.
There are some minor issues regarding HW:
1. Virtual keys and hardware keys are enabled altogether. You can disable hardware keys at /proc/touchpanel/key_disable and /sys/module/fpc1020_tee/parameters/ignor_home_for_ESD . If you do want the virtual keys to hide, read first several pages of replies and there are some solutions.
2. Slider is not working, but it produces key event. There are lots of tools that can be used to customize actions for key events, and examples can be found in the first several pages of replies as well.
3. No offscreen gestures.
4. No option for color profile switching (default, sRGB, DCI-P3). You can switch that manually at /sys/class/graphics/fb0/color_profile
Known bugs:
1. Permissive SELinux, and init allows services without a SELinux domain to start
2. Behavior of camera is not consistent - it works on my phone, but it may crash yours. If your phone reboots into EDL/9008 mode after flashing this ROM, use recovery or fastboot to flash back to other ROMs IMMEDIATELY!
3. Sometimes the system does not show charging status (no flash sign in battery icon, but LED lights up as usual), while the battery is being charged just fine.
4. No UI shown when alarm clock goes off. This is an AOSP bug (missing NotificationChannel parameters). Use Google Clock from Play Store instead.
5. VoLTE is broken. Maybe we need to wait for an official release for updated blobs.
And as you may have already known, AOSP does not include a fully functional browser nor a file manager. An `adb install` may be needed after flashing.
Screenshots:
{
"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"
}
Download:
Make backups! Make backups! Make backups!
20171008: https://drive.google.com/open?id=0BwkmhbR5VHpARHYwUE1BSGkxbTQ
20170924: https://drive.google.com/open?id=0BwkmhbR5VHpAU2lUVEVQcDRuaDQ
20170916: https://drive.google.com/open?id=0BwkmhbR5VHpAbkpMWFU1R1VLNDA
20170910: https://drive.google.com/open?id=0BwkmhbR5VHpAcGsyZ3hYWkZZcFU
20170907: https://drive.google.com/open?id=0BwkmhbR5VHpAMEVQX3h0UG1pUHM
You will lose Magisk and GAPPS after upgrading since boot and system partitions are overwritte. Better flash GAPPS right after the firmware, otherwise apps depend on GAPPS will FC even if GAPPS are re-installed.
This is NOT a flashable zip. Use fastboot to flash:
Code:
fastboot erase boot
fastboot flash boot boot.img
fastboot flash system system.img
And wipe data before usage.
NOTE: This ROM requires encrypted data partition. If your data partition is not encrypted, format it. Moreover, OxygenOS 4.5.10 4.5.12 firmwares are required.
Changelog:
20171008
Since proper development on Oreo has started, this ROM has served its purpose as an experimental (or first-taste-only) ROM, and thus will not receive any updates anymore.
Updated blobs to OxygenOS 4.5.12 (baseband version was not changed, but better use the new firmware bundled with 4.5.12)
Updated to android-8.0.0_r15
Switched to new kernel source used by MoKee (may solve some WiFi issue, and possibly some others)
Some minor cosmetic changes
No new patches applied, the 0924 archive would be fine.
20170924
Fixed voice translation in Google Translate (maybe other apps as well)
Add a power HAL and double tap to wake is available in settings now (wondering if it actually works)
Use RenderScript driver from OnePlus 3 Oreo beta. Stock one is too old for Oreo, thus it was not loading at all.
Included navigation bar fix from this post
(Also tried new kernel used in MoKee and Lineage OS, but it still causes stalls when remounting so I switched back to the old kernel)
20170916
Bluetooth address should be correct
Fixed broken compress_offload feature (some music player (or ringtones) rely on this)
Make DASH chargers recognized as standard AC charger with fast charging support
Update to android-8.0.0_r9
20170910
Fixed Bluetooth audio. Now LDAC, AAC and SBC all work. If you want aptX / HD, find libaptX{,HD}_encoder.so elsewhere and push them to the phone.
Fixed AOSP keyboard crash when switching to symbol / numbers panel: https://android-review.googlesource.com/#/c/platform/packages/inputmethods/LatinIME/+/469478/
20170910
Initial build
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8998 (aosp-o-new branch)
Device: https://github.com/updateing/android_device_oneplus_cheeseburger (aosp-o branch)
Vendor: https://github.com/updateing/android_vendor_oneplus_cheeseburger (aosp-o branch)
In order to build kernel with AOSP, you need build/core/tasks/{kernel,dt}.mk from other ROMs build system. And external/{libnfnetlink,libnetfilter_conntrack} needs to be forwarded to AOSP master.
Source patches are attached to this post.
Credits:
MoKee/@XiNGRZ for this awesome kernel
Qualcomm for the great SoC
And Google for the OS
Thank you all!
Nice, will give it a go later, I presume there shouldn't be a problem with TWRP and going back to our present rom?
You also didn't post any gapps link, would these work ok?
http://www.cyanogenmods.org/forums/topic/gapps-lineageos-15-android-oreo-roms/
You're a brave man @djsubterrain
Does this work as a secondary ROM on multirom?
ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
No..As it says its not a flashable zip
ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
Judging by the way you need to flash this it's categorically NO
ZachChampion2020 said:
Does this work as a secondary ROM on multirom?
Click to expand...
Click to collapse
It's labelled "EXPERIMENTAL" so it's highly unlikely, you really think that would be a priority to get it working with multiboot when the rom isn't even fully working?
niceeeeee
Nice to see some OREO love for our device. Thanks Developer for your hard work.
djsubterrain said:
Nice, will give it a go later, I presume there shouldn't be a problem with TWRP and going back to our present rom?
You also didn't post any gapps link, would these work ok?
http://www.cyanogenmods.org/forums/topic/gapps-lineageos-15-android-oreo-roms/
Click to expand...
Click to collapse
TWRP should work fine. Personally I'm using TWRP 3.1.1, official build, and haven't noticed any issue.
There should not be any issue when going back to 7.x ROMs (though I have not tried myself), but as wiping data is always involved when changing ROMs, do make a backup of everything including internal storage!
I have not tried any unoffical build of Gapps, and the only official build available now is DeltaGapps. It doesn't work OOB however, I need to extract some libs from APKs to get it to work.
1st to release N for bacon, O for cheeseburger.
Good job bro.
Good!!
Guo Lai Yang Wang Dalao!
Good job bro~
Sent from China fanboy~
missing on u in bacon family.. like u provided Nougat rom for oneplus 1..
*crais for posting OT* @updateing ,by any chance,are you working on oreo for bacon as well? Your work for Nougat on bacon is highly appreciated.
Mr.Ak said:
*crais for posting OT* @updateing ,by any chance,are you working on oreo for bacon as well? Your work for Nougat on bacon is highly appreciated.
Click to expand...
Click to collapse
Bacon already has an Oreo port.
djsubterrain said:
Bacon already has an Oreo port.
Click to expand...
Click to collapse
Ikr,but hopefully he'll be able to get camera working on oreo for bacon.
First O rom. Wow ?
Snapdragon815 said:
1st to release N for bacon, O for cheeseburger.
Good job bro.
Click to expand...
Click to collapse
Mmmm.... I love some bacon on my cheeseburger... Typed on the 1+1 while my 1+5 is charging... Keep up the good work!
Thanks Dev. Oreo love
{
"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 8.1 is coming on your Huawei MediaPad M3 8.4, Kirin 950 SoC with the LineageOS 15.1 !
In October 2021 this ROM reached the end of life ( EOL )
Devices Supported :
Huawei MediaPad M3 8.4 :
BTV-DL09; BTV-L0J; BTV-W09
About LineageOS :
LineageOS 15.1 is a free, community built, aftermarket firmware distribution of Android 10 (Q), 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.
* 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.
*
Warning !
Installing a custom ROM on your device can sometimes be difficult and also with unwanted consequences! Therefore, make sure that you understand exactly what risks this operation entails - you are the only one responsible for all actions taken on your device.
Downloads ( EOL ):
LineageOS-15.1-BTV_2022-01-05.zip md5: 4b424433f7b746d9abad7c5adfec07a1
Only for BTV-W09 :
boot_w09_oreo_2022-01-05.img md5: f33b2ba35cbfb67b62b28b771bdff240
This ROM do not include GApps
please use always the last available pack :
OpenGApps for Android 8.1 ARM64
recommended to use nano or pico version
Instructions :
1. install the New TWRP 3.3.1-0 ( please check the second post )
2. format data in TWRP & reboot device into twrp to be able to use data !
3. go to Wipe -> Swipe to Factory Reset
4. wipe Vendor & System partitions
5. copy LOS-15.1 ROM & GApps to Internal/External Storage
6. go to Install -> check the LOS zip file
7. Add more Zips
8. check GApps zip file
9. Swipe to confirm Flash
10. Wait a bit until you'll see : "
- Installation complete!
- Unmounting partitions
Updating partitions details ...
... done
11. Wipe Cache/Dalvik -> Swipe to Wipe
12. If your device it's BTV-W09 please install now boot_w09_oreo_xxx.img
( Install -> Install Image -> choose "boot_w09_oreo_xxx.img" -> Select Partition to Flash Image: Boot )
13. Reboot System
14. Enjoy!
What's working :
* Touchscreen
* Audio & Video
* Wi-Fi
* Bluetooth
* GPS
* Lights
* Notification light
* Sensors
* Internal/External Storage
* ADB/MTP & USB/OTG
* Off-mode Charging
* RIL & LTE data connection
* HWComposer
* Camera
* DRM enabled ( the same Level L3 like on Stock EMUI Firmware )
* Fingerprint scanner
* Hardware Video Decoder
Not working :
* SELinux Disabled; ( won't be enabled anytime soon )
* Encryption; ( won't be fixed anytime soon )
* Cast - not working
* there may be others minor issues like camera not fully working and so on
Credits :
LineageOS Team
Source :
kernel: android_kernel_huawei_btv Branch: oreo !
Screenshots :
Contributors
surdu_petru
Paypal Donation : paypal.me/petrusurdu1
Source Code: https://github.com/Huawei-Dev?tab=repositories
ROM OS Version: Android 8.1/Oreo
ROM Kernel: Linux 4.4.x
ROM Firmware Required: Stock Android N - EMUI 5.x
Based On: LineageOS
Version Information
Status: Stable
Project Status
EOL
Created 2020-04-19
Last Updated 2022-01-05
TWRP 3.3.1-0
TWRP 3.3.1-0
You need this new TWRP in order to flash Lineage OS 15.1 !
Must be installed only on Android N EMUI 5.x
Working on all Huawei MediaPad M3 8.4 with Android N EMUI 5.x !
Download :
twrp-3.3.1-0.img md5: 984779bc7af812eb1b3e67e197732dbc
Installation :
adb reboot bootloader
fastboot flash recovery twrp-3.3.1-0.img
fastboot reboot
Click to expand...
Click to collapse
You need to FORMAT Data in order to decrypt /data, you need this step because LineageOS 15.1 do not have implemented right now encryption/decryption support !
Back To Stock EMUI !
You can switch at any moment from LineageOS to Stock Huawei Firmware EMUI 5.x Android N !
Before take any action by installing the new TWRP-3.3.1-0/LOS 15.1, please make sure you can return back to stock by following the steps below !
From stock EMUI 5.1 you need to keep safe your ROM reference in order to be able to download the proper update.zip for your device !
adb shell getprop | grep 'ro.build.display.id'
Click to expand...
Click to collapse
[ro.build.display.id]: [BTV-DL09C100B311]
Click to expand...
Click to collapse
You should download from here the exact version of your update.zip ( FullOTA-MF ) which match "BTV-DL09C100B311" !
Extract UPDATE.APP from update.zip and put to dload folder created on the root of internal storage !
Please use "dload" method to flash via erecovery /dload/UPDATE.APP !
Warning !!!
What I described above works only if in the download link above you find the version EMUI 5.x Android N to match your "ro.build.display.id" ... but I guess from there you can only download the EMUI 4.x Android MM which are not suitable for our purpose !
So if you really want to successfully return to stock EMUI, make sure you have an update.app EMUI 5.x Android N that can be successfully installed via "dload" method before to switch to LOS 15.1 Android Oreo!
Another possibility would be to perform a full backup in your current configurations( TWRP & Stock EMUI 5.x ), assuming that you are already on EMUI 5.x Android N - before to switch to the new TWRP & LOS 15.1 ! And for restore your full backup, you must reinstall your previously TWRP - wich has capability to restore your encrypted full backup !
Sim not working !
Why your SIM will not working on Lineage OS ?
Please provide this INFO, and I'll fix your issue on the next Update Of LineageOS.
Thanks !
Warning !
Please do not install this new custom ROM, if the first three posts are not clear enough to you .
You can start by following this GUIDE with detailed explanations !
Thanks !
Warning !
Please post all unrelated questions to this topic here !
Someone will definitely help you there.
Please post here your feedback, issues or whatever it's related to development with this new custom ROM !
Thank you for the understanding !
EDIT:
Thanks to @ericzollman & @sergio_sant for their tests, the new TWRP 3.3.1-0 & LineageOS 15.1 can be installed on All Huawei MediaPad M3 8.4 !
Camera Working !!!
Hi !
I just managed to fix Camera ( photo & video recording ) on Lineage OS 15.1 (Android Oreo 8.1) !
For some unknown reason default Snap camera can't save pictures nor video, but we can use Open Camera which working without issues
EDIT :
DRM was already enabled along with LiveDisplay/Reading mode, Prevent accidental wake-up or World/Global Phone Network Type !
Hi.
First of all, thank you for this great work.
Your ROM is amazingly stable even it is the very first version.
Today I think I found a somewhat performance issue.
I installed Geekbench 5. Just to check how this machine fast compared to the other APs being used these days.
But the results seem too low. Please check this Geekbench 5 benchmark result page: https://browser.geekbench.com/v5/cpu/1877147
Expected results are: https://browser.geekbench.com/android_devices/371
I'm not an expert for Android development. Just curious
Thanks again!
Awesometic said:
Hi.
First of all, thank you for this great work.
Your ROM is amazingly stable even it is the very first version.
Today I think I found a somewhat performance issue.
I installed Geekbench 5. Just to check how this machine fast compared to the other APs being used these days.
But the results seem too low. Please check this Geekbench 5 benchmark result page: https://browser.geekbench.com/v5/cpu/1877147
Expected results are: https://browser.geekbench.com/android_devices/371
I'm not an expert for Android development. Just curious
Thanks again!
Click to expand...
Click to collapse
Thanks !
There is no power management implementation and maybe that's why you got those poor results ! In fact I guess that the whole system run on a lower power configuration right now.
I have not time yet to try to work on increase performance , there is a lot of other important issues that' must be fixed prior.
For the moment I'm glad that it runs smoothly and without any random reboots
headset doesnt work
dhdhehdv76 said:
headset doesnt work
Click to expand...
Click to collapse
Thanks, I'll add to Not working list into OP !
Also we have an in house Huawei Bluetooth chip which can't be enabled on Android Oreo, even if it's working well on LOS 14.1 Android Nougat !
It was much easier if it was a BCM like on other Huawei / Honor devices ... I know that a ROM without BT is useless, but I have no clue how can be fix it ... it's been three days since I've only been working on BT fixing, and unfortunately no positive signs so far
OK, I'll try to fix headset issue right in the next update !
maybe and i dont know very well but if the mate 8 which is almost the same device has the same bluetooth chip is it possible to use its code for the bluetooth part because its already updated to oreo if i remember correctly ? personally i dont use the bluetooth at all. waiting for headset fingerprint and maybe the power manager because im playing pubg on it but dont stress yourself health is more important and thank you for your hard work have a good month.
qlue4e said:
maybe and i dont know very well but if the mate 8 which is almost the same device has the same bluetooth chip is it possible to use its code for the bluetooth part because its already updated to oreo if i remember correctly ? personally i dont use the bluetooth at all. waiting for headset fingerprint and maybe the power manager because im playing pubg on it but dont stress yourself health is more important and thank you for your hard work have a good month.
Click to expand...
Click to collapse
Yes, that's the bad news ... I already used all Oreo stuff from Mate 8, but unfortunately Mate 8 uses a BT chip based on Broadcom (BCM) !
Hi.
I'm going to report another unimplemented thing just found; Speakers work but only the top. The bottom speaker doesn't work.
Maybe you already know that.
One question, is there any chance to get stereo sound with the 2 speakers?
Awesometic said:
Hi.
I'm going to report another unimplemented thing just found; Speakers work but only the top. The bottom speaker doesn't work.
Maybe you already know that.
One question, is there any chance to get stereo sound with the 2 speakers?
Click to expand...
Click to collapse
Sound it's not working at all right now after I tried to fix headset issue, and it's been 10 hours since I've been trying to get it back the way it was
Starting next week the development here will be very slowly as I restart my work , and I'll not have too much free time for development.
From what remains to be fixed, nothing can be fixed in a few hours .... so I don't know when I'll have time to try to fix the rest of the issues, also I don't know when I'll release a new update .
Thanks for understanding !
surdu_petru said:
Sound it's not working at all right now after I tried to fix headset issue, and it's been 10 hours since I've been trying to get it back the way it was
Starting next week the development here will be very slowly as I restart my work , and I'll not have too much free time for development.
From what remains to be fixed, nothing can be fixed in a few hours .... so I don't know when I'll have time to try to fix the rest of the issues, also I don't know when I'll release a new update .
Thanks for understanding !
Click to expand...
Click to collapse
Take a break.
I, probably we all don't want you to be pressed by the updates. Publishing LineageOS itself is the present for us!
Actually still waiting for the updates, but this because only you could do develop this. But don't want you to go hurry.
Awesometic said:
Take a break.
I, probably we all don't want you to be pressed by the updates. Publishing LineageOS itself is the present for us!
Actually still waiting for the updates, but this because only you could do develop this. But don't want you to go hurry.
Click to expand...
Click to collapse
I think you're right, I wanted to do too much at the same time, and ended up with a broken LOS build !
There are far too many stuff to be implemented and fixed on this ROM and it sound likely will never be finished ... only the correct kernel update can take 6 months, so updating to Android Pie will not be as soon as I thought initially .
EDIT:
It looks like I finally managed to fix the sound issues : stereo speakers enabled & also headset issue
New Update !!!
New Update Of LOS 15.1 For MediaPad M3 8.4
Changelog:
- DRM enabled - now you can watch video streaming that needs drm support !
- fixed stereo speakers & headset
- enabled LiveDisplay & Reading mode
- added Prevent accidental wake-up
- Camera fixed ( but not fully working )
* video recording only on default format
* video recording on front camera not working
* HDR & also most all settings not working apart default !
- enabled World/Global Network preference type
- GPS improved
- Updated Android security patch level : April 5, 2020 !
Please check OP to download the new update, thanks !
Good news !
Hi !
I just managed to fix fingerprint scanner on my device
And another good news, there is a way to update this device to Android 10 : I just found out it was possible even if we don't have fstab implementation into kernel/dts - and this stuff can't be implemented in our device as dts images can't be builded or updated ! So, there is a way to by-pass this kernel requirement and boot the latest Android Q on the legacy devices
surdu_petru said:
Hi !
I just managed to fix fingerprint scanner on my device
And another good news, there is a way to update this device to Android 10 : I just found out it was possible even if we don't have fstab implementation into kernel/dts - and this stuff can't be implemented in our device as dts images can't be builded or updated ! So, there is a way to by-pass this kernel requirement and boot the latest Android Q on the legacy devices
Click to expand...
Click to collapse
Great news, thanks again for all your hard work!