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"
}
DarkJoker360 AOSP 10 for Huawei P10 Lite
*** Stable Version ***
About
Code:
[CENTER]Android is an open source software stack for mobile devices and a corresponding open source project led by Google. This site and the Android Open Source Project (AOSP) repository offer the information and source code needed to create custom variants of the Android stack, port devices and accessories to the Android platform, and ensure devices meet the compatibility requirements that keep the Android ecosystem a healthy and stable environment for millions of users.
This rom has been edited by DarkJoker360 with some additions such as:
* Pixel UI
* Theme picker
* Fruity pebble v2.0
* AospExtended's material icons
* Google bootanimation
[/CENTER]
Working
Code:
[CENTER]* Touchscreen
* Adb / Mtp
* Audio
* Boot
* Bluethoot
* Internal/External storage
* Sensors
* Wifi
* RIL
* Camera
* Android 10 gestures
* NFC
* FP gestures
[/CENTER]
Not Working
Code:
[CENTER]* Offline charge (It works by switching to permissive selinux)
[/CENTER]
Installation
Code:
[CENTER]* you must also have this recovery version installed : [URL="https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890"]TWRP[/URL]
* go to TWRP and do a full wipe (system, data, cache, dalvik/art cache) !
* reboot to bootloader
* extract AOSP 10 zip
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* flash root(optional)
NOTE: If you are coming from Android 9 flashing root is a MUST DO !
NOTE2: Flash only the Magisk zip linked in this post !
* reboot to System
* reboot to TWRP
* flash gapps (optional)
* reboot to System
* reboot to TWRP
* flash patch_r2.zip
NOTE: this zip is needed for having working NFC and overlays. DO NOT IGNORE IT !
* reboot system
* Enjoy !!![/CENTER]
Update
Code:
[CENTER]* extract the new update of AOSP
* reboot device to : TWRP
* wipe cache & dalvik cache
* reboot to bootloader
* run: fastboot flash system <drag system.img here>
* reboot to TWRP
* install gapps(optional)
* reboot to System
* reboot to TWRP
* install patch_r2.zip
* NOTE: this zip is needed for having a working NFC and overlays. DO NOT IGNORE IT !
* reboot to System
* Enjoy !!![/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/darkjoker360-developements/files/Huawei/P10%20Lite/Android-10/"]DarkJoker360 AOSP 10 and patch_r2 fix[/URL]
[URL="https://opengapps.org/"]Gapps[/URL]
[URL="https://forum.xda-developers.com/attachment.php?attachmentid=4882825&d=1574332554"]Magisk Phh v19.3[/URL][/CENTER]
Credits:
@phhusson
@flex1911
@haky 86
@Dil3mm4
@Hami_Do
Please support my work, it's very important! Thanks
DONATIONS
Regards !
XDA:DevDB Information
Android Open Source Project, ROM for the Huawei P10 Lite
Contributors
DarkJoker360
Source Code: [url]http://github.com/DarkJoker360[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x,bootloader unlocked and TWRP
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 10
Stable Release Date: 2019-11-24
Created 2019-11-24
Last Updated 2020-01-02
FAQ.
Gapps
The recommend package at the moment is this:OpenGapps_arm64-BETA
* Flash this after first boot(with patch zip flashed) and ignore Setup Wizard errors
* Open Play Store and Log in
If you get some errors about Play Services make sure it has full permissions.
Aosp has "ugly" ui
I am sorry for giving you AOSP, hi6250 sources aren't good for other rom actually. As soon as I am able to fix these issues with other custom roms I will provide them, otherwise I will customize it starting from next build by bringing pixel styles and new apps with recent ui look.
NOTE: while inatalling gapps you can may face error 70 insufficient space error, just resize system and if the problem persist flash pico gapps !
Thanks for developer
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Added new gapps and steps for their installation in OP and 2nd post.
NeoPreacher said:
I'm testing it right now. Flashing runs flawless. Rom runs well so far. ... More later.
First of all, I'm glad that I can use a pure aosp on this phone now. It can be used as daily driver. A cool thing is that I only needed to set device fingerprint to p8lite in magiskhideprops to fully pass safetynet. now it only needs nfc working, but I guess we need to wait for phh and his updates for now.
Two things I recognized pretty fast are GPS needs little help to get a fix, first fix needed nearly 4 minutes but then it gets fast fix but always with support (used gpstest from f-droid store) and downloads via wifi are generally (quite) slow.
Also I can't copy stuff from intern to ext sdcard.
This is not a real "bug report" as it is possible that I did something wrong, you'll never know. Just talking and see if anyone has the same issues. Cheers
Click to expand...
Click to collapse
Thanks for reviewing, I forget to include GPS stuff, in next build it will be fixed !
Nfc is almost fixed, we got it enabling at the moment.
For sd card I will take a look.
Here's a working fix to get nfc option (but no tile): https://forum.xda-developers.com/showpost.php?p=81021365&postcount=26
Q looks promising for our chipsets.
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
DarkJoker360 said:
I am working on to include everything in the system.img without using another zip. Do you want gapps included too?
For this time i preferred to use .img instead of a .zip format because most of TWRPs have some flashing issues. Do you want back the zip or no? I prefer no tbh, dunno about you. Let me know
Click to expand...
Click to collapse
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
NeoPreacher said:
It is a good decision to leave it as system.img, you mentioned it already, no flashing issues. Included gapps would shorten the flashing procedure a little, so I would also prefer this too.
PS: i just shared the fix to simply spread the ongoing progresses a little more. A working Q build that's now passing safetynet easily and already has working nfc (temporary with fix). That's huge progress. I'm really excited of what comes up the next weeks (not to hurry )
Click to expand...
Click to collapse
Thanks so much for beliving in me, cool stuff is coming really soon. Including a newer decent ui
Great work. .. waiting for new release.
Finally oreo vendor is getting some love and a taste of android 10... Please keep up the good work man... And thank you
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
ghassan haddad said:
Does ''offline charge not working'' mean that we aren't able to charge the phone while it is turned off or when it is locked?
Click to expand...
Click to collapse
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Copkiller2010 said:
I installed this ROM on my Mate 10 Lite. Works awesome but i cant get GApps working from the 2nd Post. I didnt get the Option to enter the Email and Password. Settings already set. Any Ideas ?
Click to expand...
Click to collapse
Tried a factory reset from twrp?
NeoPreacher said:
When it's turned off it won't charge, your phone will instead completely boot up.
---------- Post added at 12:12 PM ---------- Previous post was at 12:11 PM ----------
Tried a factory reset from twrp?
Click to expand...
Click to collapse
I have a question, the charge of 9watts are working?
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
FranckTheMiner said:
Hey,
I own a Huawei P10 Lite (WAS-LX1A, non-rebranded), and I followed your steps, using Askuccio's TWRP v1.0. I got it up and running, and I installed Magisk and the Android Patch, however, when I was figuring what worked and what didn't work, I took a screenshot and it said it couldn't due to storage issues, or something like that, which raised a red flag, and made me go and check how the file manager reported space, and sure enough it was reporting the +-32GB the phone had, however it was encrypted, which justified the storage issues. I did forget the GApps, which I'll install shortly to see if that was the problem. I also suspect that it can be related to the fact that I set the PIN without having used it to log in, so I'll reboot and test that out.
EDIT: Rebooted the device, entered pin, data is still encrypted
Click to expand...
Click to collapse
Same, add to that inability to sign in to Google Services. Were you able to sign in?
ghassan haddad said:
Same, add to that inability to sign in to Google Services. Were you able to sign in?
Click to expand...
Click to collapse
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
FranckTheMiner said:
I did get to that point, however I noticed on the 9.0 ROM the internal/external storage is featured as a working feature, so @DarkJoker360 it would be pretty helpful to new users to state that the internal storage isn't working, while the external does
Click to expand...
Click to collapse
The internal storage is working good !
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"
}
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
{
"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
/*
* Your warranty is... still valid?
*
* 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.
*
*/
Click to expand...
Click to collapse
Project Treble
Important!
Recommended for installation only for advanced users***What is Project Treble? ***
Project Treble allows to install - Generic System Images on our device with a minimum number of bugs.
Vendor - this is partition where proprietary files and drivers are stored, which are separate from the system.
***Userful Information***
Project Treble XDA Thread
Generic System Image (GSI) list
***Development and bugs***
Development has been started about 3 months. backwards During this time, dozens of errors were corrected and millions of nerve cells were lost.
Vendor is based on the stock firmware UOS273C with a large number of edits.
The kernel is used from vm03 with driver edits for working on Project Treble.
Bugs in Generic System Images:
On Oreo and Pie GSIs don't working SafetyNET.
My Magisk Module: Wileyfox Swift 2 SafetyNet Pass
Bugs in Vendor:
SELinux Permissive
For the fingerprint scanner to work correctly before being added to Settings, it is necessary to “poke” 5-6 times into it, for the driver to load correctly.
***Preparing device for support Project Treble***
Download TWRP Treble
Repartition script 16GB or 32GB
Download Treble Vendor
Download Treble Boot
Mirror on Google Drive
Mirror on Cloud Mail.ru
If you want get back default partition table just flash:
Download Revert - 16GB
Download Revert - 32GB
You need to copy all the necessary information to an external memory card or PC, since the internal memory will be formatted and devided into special partitions for Project Treble can work.
Install TWRP Treble in a convenient way for you.
Install Repartition script in TWRP. Depending on your internal memory size.
After installing repartition script, device will automatically reboot into Recovery, where you must do:
Format Data (Wipe > Format Data)
Wipe Vendor (Wipe > Advanced Wipe > Vendor)
After that necessarily to reboot the Recovery (Reboot > Recovery)
Flashing Treble Vendor (Just install zip archive)
Flashing Treble Boot (Select the option in the lower right corner Install Image, select Boot_Treble_new.img and flash it as Boot Image)
Install your favorite firmware (about this below). (Select the option in the lower right cornerInstall Image, than flash it as System Image)
***Installing Android Oreo or Android Pie GSIs***
Flash any GSi from Generic System Image (GSI) list or XDA Thread
always choose arm64 A-ONLY!
* If camera don't working on Pie flash:
Camera Pie GSI patch
* If the NFC item in the settings hangs, or the NFC does not turn on (this is usually the case in the old October GSI), flash:
NFC all GSI Patch
* Patch for fix fingerprint scanner on some Pie GSIs
Folder with patches
For ArrowOS GSI, HavocOS 2.0, AEX 6.1 fix not needed.
***Google Apps***
Install GApps only before the first launch of the ROM!
Open GApps Project
***Thanks***
Testing and moral support:
Kirill_MegaFon (4PDA)
xyzmean (4PDA)
Zent16 (4PDA)
backspace696 (4PDA)
Help in bug fixes and kernel sources:
vm03 (XDA)
Mirrors for download files:
anatoliy-is (4PDA)
Fingerprint overlay:
creativchic (4PDA)
XDA:DevDB Information
[Project Treble][UNOFFICIAL] for Wileyfox Swift 2/Plus/X, ROM for the Wileyfox Swift 2
Kernel Sourses
DevelopedInside
Contributors
fx-mod
ROM OS Version: Android 8.1.x and Android 9.x
Version Information
Status: Beta
Created 2018-09-30
Last Updated 2018-09-30
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
To return the phone to stock, just install Factory Firmware.
fred0r said:
Never heard of 'Project Treble' before, but it sounds very interesting to be able to use 'Generic System Images'.
Before playing around with it - can you please also provide a 'Repartition Script' to get back to the default Partitioning ?
Click to expand...
Click to collapse
Done!
i installed treble according to your instruction and flashed a AOSP 8.1 image (system-arm64-aonly-gapps-su.img.xz) which should include gapps and su.
unfortunately the su-part wasnt available, so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
[edit]
installed another rom which had the option in developers to reboot directly into the recovery - that worked.
---------- Post added 5th October 2018 at 12:12 AM ---------- Previous post was 4th October 2018 at 11:43 PM ----------
Now i installed the latest Oreo Resurrection-Remix from https://downloads.resurrectionremix.com/arm64aonly/ and during startup:
{
"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"
}
Another thing is, that on all GSI-Images i installed so far the system-fonts are very tiny - like it's using a too high screen-resolution.
fred0r said:
......so i tried to boot into the recovery by selecting it during the start of the phone - but i instantly came back to the 'boot-screen' without starting twrp.
for now the only way to get back on the 'treble-twrp' i need to boot it via fastboot (fastboot boot TWRP_Treble_marmite.img)
i this a bug or am i doing something wrong ?
Click to expand...
Click to collapse
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
fred0r said:
Nevermind - it works also to boot from the start. i needed first to select 'boot recovery' and then press on 'start' to boot into it.
Just installed the GSI from PixelExperience from pixelexperience.org and also get that 'vendor mismatch' message.
Click to expand...
Click to collapse
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
xXxSAMIxXx said:
I had this issue too and I believe flashing the vendor zip again did the job for me, not completely sure though.
Click to expand...
Click to collapse
vendor miscmatch message is a warning. Not an error!
a great work ..soon i will get this device
I'd like to try out Android P. Has anyone tried this with a Swift 2 device and can recommend a GSI to use?
Edit: I couldn't get Pixel Experience (9.0) to boot succesfully but phhusson's AOSP 9.0 works. It's very barebones indeed. Someone made an overlay that makes adaptive brightness possible but I still can't adjust the LED for notifications. Not being able to turn off the charging/low-battery LED is a bummer. Otherwise it runs fine but I'll try a different GSI today.
Did you use the arm64 a-only image? I tried the arm a-only and that wouldn't boot but I'm (quite) happily buzzing along with the former.
fx-mod said:
* Patch for fix fingerprint scanner on some Pie GSIs
Phh AOSP 9 v106 [02/10/2018] only
ArrowOS 9 [23/09/2018] only
Pixel Experience P [20/09/2018] only
Click to expand...
Click to collapse
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
erasmuswill said:
Is it possible to update the Pixel Experience P fingerprint scanner patch? The latest version of the ROM fixes the hotspot issues but the fingerprint scanner patch does not work.
Click to expand...
Click to collapse
it is done!
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
waver1967 said:
wileyfox swift 2X with 32GB storage.
32 gb repartition file ? or should i use 16 gb ?
just to be sure i'm not destroying my phone
Click to expand...
Click to collapse
32 GB of course
failed to mount system
after doing all the steps twrp says no os installed
oeps my mistake..
forgot to unrar gsi file
Is it possible to patch at least one of Pie GSI's to work almost perfectly? Right now it is not possible to use any of GSI's for more than a week because every one have some annoying bugs
puszekkk said:
(
Click to expand...
Click to collapse
What does not suit you?
anatoliy-is said:
What does not suit you?
Click to expand...
Click to collapse
Broken hotspot, dumped fingerprints after reboot, broken wifi, broken audio routing :/
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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:
#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.
*
*/
Features
Lots of goodies. Working to add more.
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM: AndroidFileHost
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your Honor 5x, or coming from another ROM:
** Make sure you're running a proper working Recovery such as TWRP
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk XX.x (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
SELinux is PERMISSIVE
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- AOSP
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
Join us on Telegram!
crDroid Community: https://t.me/crDroidAndroid
crDroid G+ community
XDA:DevDB Information
crDroidAndroid, ROM for the Honor 5X
Contributors
coldhans
Source Code: https://github.com/crdroidandroid
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock MM Firmware (No VoLTE)
Based On: LineageOS
Version Information
Status: Nightly
Current Stable Version: 5.1
Stable Release Date: 2019-03-12
Created 2019-02-07
Last Updated 2019-03-12
Reserved
Website: https://crdroid.net/kiwi
Reserved
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/9.0/changelog_kiwi.txt
Installing this right now
You're great man
---------------------------------------------------------------------------------------------------
Clean Installed it just now:
- First boot-up tooook much longer than what I've usually seen.
- Setup wizard was unable to move on when I tried to continue using Mobile Data. ( It stock at turning mobile data ON, when I skipped the Setup Wizard I noticed that APN was missing.)
- Fingerprint Enrollment was not Complete.
---------------------------------------------------------------------------------------------------
After A reboot still cant enroll finger print
and default music player is not usable because it keeps flashing the screen and I cant see anything.
Logs r attached.
everything work fine except Fingerprint Enrollment
nourpon said:
everything work fine except Fingerprint Enrollment
Click to expand...
Click to collapse
all what you need to do mate is the following (requires ROOT)
1-find yourself a good ROOT file explorer (Mine is ES)
2-navigate to data/system/users and delete fpdata folder
3-(no need to restart the device) go to setting app then security then fingerprint and try enrollment it may fall to complete about 1-3 times but it should be done easily after that
try that and tell me if it didn't work for you
GEKv2 said:
all what you need to do mate is the following (requires ROOT)
1-find yourself a good ROOT file explorer (Mine is ES)
2-navigate to data/system/users and delete fpdata folder
3-(no need to restart the device) go to setting app then security then fingerprint and try enrollment it may fall to complete about 1-3 times but it should be done easily after that
try that and tell me if it didn't work for you
Click to expand...
Click to collapse
Thank you for the tweak, it work fine now
---------- Post added at 05:56 PM ---------- Previous post was at 05:53 PM ----------
@coldhans will you update regularly this ROM ?
thank you for answer
greatwork ，crdroid is alwyas my daily rom。
wish better
and my bugs as follows：（kiwi-tl00）
same imei & always 50% battery display
GEKv2 said:
all what you need to do mate is the following (requires ROOT)
1-find yourself a good ROOT file explorer (Mine is ES)
2-navigate to data/system/users and delete fpdata folder
3-(no need to restart the device) go to setting app then security then fingerprint and try enrollment it may fall to complete about 1-3 times but it should be done easily after that
try that and tell me if it didn't work for you
Click to expand...
Click to collapse
this solution did not work, neither did the solution provided in here:
https://forum.xda-developers.com/showpost.php?p=78655571&postcount=204
KingJK said:
this solution did not work, neither did the solution provided in here:
https://forum.xda-developers.com/showpost.php?p=78655571&postcount=204
Click to expand...
Click to collapse
Youi just need to insist many times and it's work
nourpon said:
Youi just need to insist many times and it's work
Click to expand...
Click to collapse
It's just not worth it, I tried both solutions more than 5 times and kept restarting the device the suggested amount. It's killing the time, I went back to Arrow
path
GEKv2 said:
all what you need to do mate is the following (requires ROOT)
1-find yourself a good ROOT file explorer (Mine is ES)
2-navigate to data/system/users and delete fpdata folder
3-(no need to restart the device) go to setting app then security then fingerprint and try enrollment it may fall to complete about 1-3 times but it should be done easily after that
try that and tell me if it didn't work for you
Click to expand...
Click to collapse
* 2-navigate to data/system/users/0 and delete fpdata folder
Dirty flashed from crDroid 8.1.
As for now - no single issue Great job!
Hello,
i did fix fingerprint enrolmetnt issue this way:
1 reboot to TWRP mode
2 invoke file editor
3 delete files/folders:
/data/fpc
/data/system/locksettings.db
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
4 reboot to system
5 tap the "Continue (filinalze) phone setup on top of system settings GUI
6 select PIN+Fingerprint unlcock mode and continue as normal
Regards,
Dmitri.
Dmitri_01 said:
Hello,
i did fix fingerprint enrolmetnt issue this way:
1 reboot to TWRP mode
2 invoke file editor
3 delete files/folders:
/data/fpc
/data/system/locksettings.db
/data/system/users/0/fpdata
/data/system/users/0/settings_fingerprint.xml
4 reboot to system
5 tap the "Continue (filinalze) phone setup on top of system settings GUI
6 select PIN+Fingerprint unlcock mode and continue as normal
Regards,
Dmitri.
Click to expand...
Click to collapse
the simple way to honor 5x is to erase as root "data/system/users/0/fpdata" only once and then register the used fingerprint pattern and fingerprint and that's it.
how about buttery drains and performance in this rom combring it with cr 7.1.2
MOHAMED BEK said:
how about buttery drains and performance in this rom combring it with cr 7.1.2
Click to expand...
Click to collapse
For me it works just fine. I use it now as daily driver. Works better than crDroid on Android 8.1.
There is still issue, that only first SIM can run on LTE/4G. Second can run only EDGE. Changing SIM for data transfer doesn't help - only disabling the Sim used for data transfer allows to operate second Sim on LTE profile. I think the second Sim becomes then first reported to networking subsystem, so it is being allowed to use LTE profile. Even if You re-enable the first one, it is being reported as second Sim so it gets only edge profile.
Would it be possible to force reinitialisation of Sim cards when changing the Sim for data transfer? I think this way is operating stock software...
Cheers ?
Marcin
thanks so much
2/16 OTA update is out
Download: AFH | MEGA
Changelog: https://raw.githubusercontent.com/c...9b945aec31b8a6513e8a9cd703/changelog_kiwi.txt
coldhans said:
Download: AFH | MEGA
Changelog: https://raw.githubusercontent.com/c...9b945aec31b8a6513e8a9cd703/changelog_kiwi.txt
Click to expand...
Click to collapse
just popup to twrp after flashing the 20190216 ver
it was normal during the former ver.s
and the bugs i come to：1.same imei when two sims；2.50%battery always ，（Chinese kiwi-tl00）3.the options in the expanded desktop cannot be displayed4.the castscreen seemed abnormal
================================
after i wipe the data ，it come home....（twrp cannnot be touchble when the issue）
Hello !
{
"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"
}
The new Android 10 is coming to your Huawei MediaPad M3 Lite 8/10, Qualcomm Snapdragon MSM8940 with the new LineageOS 17.1 !
Please note that this ROM is one of my side projects, for which I could provide zero warranty. By installing this ROM, you acknowledge that you take all the risks that come with installing custom firmwares on your devices, including but not limited to bricking your device, losing your data, etc.
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.
Devices Supported:
Huawei MediaPad M3 Lite 10 :
BAH-AL00/BAH-L01/BAH-L09/BAH-W09
Huawei MediaPad M3 Lite 8 :
CPN-AL00/CPN-L0J/CPN-L09/CPN-W09
About LineageOS :
LineageOS 17.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.
*
*/
Downloads :
LineageOS-17.1-HuaweiMediaPadM3Lite_2023-02-26.zip md5 : b86f752b8851bf8a8e1ce9e2168ee92d
This ROM do not include GApps
please use always the last available pack :
OpenGApps for Android 10 ARM64
Instructions :
0. LOS 17.1 must be installed via TWRP 3.3.1-0
1. After device boot on LOS 17.1 you must to install the New TWRP 3.3.1-3
( TWRP 3.3.1-3 needed for flash GApps on LOS 17.1 )
2. plug USB cable to your Desktop/Laptop for copy files ( or add them to a external storage/microSD card )
3. go to Wipe -> Swipe to Factory Reset
4. copy LOS-17.1 ROM & GApps to Internal/External Storage
5. go to Install -> check the LOS zip file
6. Add more Zips
7. check GApps zip file
8. Swipe to confirm Flash
9. Wipe cache/dalvik -> Swipe to Wipe
10. Reboot System
11. Enjoy!
What's working :
* Touchscreen
* Audio & Video
* WIFI
* BT
* GPS
* FPS
* Lights
* Sensors
* Internal/External Storage
* ADB/MTP & USB/OTG
* RIL & data connection
* Camera Video recording
* Flip Cover
* Encrypt device
* SELinux Enforced
Not working :
* Photo Camera
* there could be also others minor issues !
Credits :
LineageOS Team
dianlujitao
LuK1337
Greg Kroah-Hartman for keep alive 3.18.y kernel !
Source Code :
device tree : android_device_huawei_bach Branch: ten!
kernel: android_kernel_huawei_bach Branch: ten !
Screenshots :
Contributors
surdu_petru
Paypal Donation : paypal.me/petrusurdu1
Source Code: https://github.com/Huawei-Dev?tab=repositories
ROM OS Version: Android 10 / Q
ROM Kernel: Linux 3.18.140
ROM Firmware Required: LineageOS 16.0 Android Pie
Based On: LineageOS
Version Information
Status: Stable
Created 2019-10-20
Last Updated 2023-02-26
Donors :
@ossizwei
@Jobode747
@Micromind
@morgan7676
@Kagum
@mrdark5555
@realdomdom
@xbor
@#marcg#
Norbert Ossendorf
Once again thank you very much to all donors !!!
Now that I've managed to unlock my M3 Lite I've decided to jump in with both feet
I've put this LineageOS 17.0 on with CyanogenMod OpenGAPPS 10 full. I'll let you know how I get on.
Do I need to update TWRP from 3.2.0.0 to 3.3.1.0?
thanks
Paul
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
Got getting messages repeatedly between these two:
"com.qualcomm.qcrilmsg.... keeps stopping"
"android setup keeps stopping"
csjjpm said:
Now that I've managed to unlock my M3 Lite I've decided to jump in with both feet
I've put this LineageOS 17.0 on with CyanogenMod OpenGAPPS 10 full. I'll let you know how I get on.
Do I need to update TWRP from 3.2.0.0 to 3.3.1.0?
thanks
Paul
---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------
Got getting messages repeatedly between these two:
"com.qualcomm.qcrilmsg.... keeps stopping"
"android setup keeps stopping"
Click to expand...
Click to collapse
Yes you can update now Twrp to 3.3.1.
Btw I didn't tested GAppps. So if it's not working just remove it.
This is happening a lot when I go into Setting: "android setup keeps stopping"
csjjpm said:
This is happening a lot when I go into Setting: "android setup keeps stopping"
Click to expand...
Click to collapse
Ok, just remove GApps and see how it's working ... later you can install nano or pico, not full version of GApps !
EDIT :
Full version of GApps it's not recommended at all as there is just a Betta LOS 17.0 !
Awesome!, thanks for providing full source.
I'm getting the same error "com.qualcomm.qcrilmsgtunnel" keeps crashing until I manually close the app on clean install, I have a tablet with no sim. Other than that the tablet seems to be working fine.
After installing opengapps android setup crashes repeatedly, but after disabling android setup, play store works as normal.
oddhap said:
Awesome!, thanks for providing full source.
I'm getting the same error "com.qualcomm.qcrilmsgtunnel" keeps crashing until I manually close the app on clean install, I have a tablet with no sim. Other than that the tablet seems to be working fine.
After installing opengapps android setup crashes repeatedly, but after disabling android setup, play store works as normal.
Click to expand...
Click to collapse
Well done !
oddhap said:
Awesome!, thanks for providing full source.
I'm getting the same error "com.qualcomm.qcrilmsgtunnel" keeps crashing until I manually close the app on clean install, I have a tablet with no sim. Other than that the tablet seems to be working fine.
After installing opengapps android setup crashes repeatedly, but after disabling android setup, play store works as normal.
Click to expand...
Click to collapse
Thanks, I didn't know if the 'android setup' was important or not. Have disabled it and all quiet now.
I tried a few version of GAPPS10, Pico, Nano etc. and still got the errors. Once 'android setup' disabled now issues.
Thanks
Installed without GApps. Seems fine so far. Will test more once it completes charging. Thanks for all your hard work man. you have really enhanced the overall experience with this tablet.
fallensoldier said:
Installed without GApps. Seems fine so far. Will test more once it completes charging. Thanks for all your hard work man. you have really enhanced the overall experience with this tablet.
Click to expand...
Click to collapse
Thank you for feedback!
Hi I try to test this rom, very nice!! But it still has many bugs, but I'm sure it will improve over time! Report that it is present some bugs, when start cpuz app the device restarts suddenly, Chrome some times stop to work , the microphone does not work in any app (eg. google assistant "hey google") work with earphones. When you record a fingerprint and then reboot the device you lose the fingerprint setting.
Thank you so much for the chance to try an updated version of andorid on this tablet!!
I hope to be helpful, a great job has been done.
I will try this rom for a short time but will return to the stock version, it won't be easy to go in stock, because there is no custom rom based on the original firmware.
I will find a way to return to the stock.
Bye bye.
sergybizzi said:
Hi I try to test this rom, very nice!! But it still has many bugs, but I'm sure it will improve over time! Report that it is present some bugs, when start cpuz app the device restarts suddenly, Chrome some times stop to work , the microphone does not work in any app (eg. google assistant "hey google") work with earphones. When you record a fingerprint and then reboot the device you lose the fingerprint setting.
Thank you so much for the chance to try an updated version of andorid on this tablet!!
I hope to be helpful, a great job has been done.
I will try this rom for a short time but will return to the stock version, it won't be easy to go in stock, because there is no custom rom based on the original firmware.
I will find a way to return to the stock.
Bye bye.
Click to expand...
Click to collapse
Thanks for feedback ! Btw, I already noticed fingerprint issues .... but as you already said the ROM will be improved with each update !
At this time even Lineage OS didn't released the stable source yet .
@surdu petru Do you have the possibility to make a custom rom based on the latest stock rom to flash via twrp? It would be a great thing.
Thank you for your work!
sergybizzi said:
@surdu petru Do you have the possibility to make a custom rom based on the latest stock rom to flash via twrp? It would be a great thing.
Thank you for your work!
Click to expand...
Click to collapse
Sorry, no way ... I tried a few time to revert to stock but my device can't boot on stock recovery from some unknown reasons .
But there is a few users wich already reverted this device to stock after installed Lineage OS 16.0 ( Android Pie ), so you could search on Lineage16.0 thread for their posts, or you can get in touch with them through PM.
Good luck !
Ok no problem.. I'll find a way to get back to the stock .. But first I'll try the other roms with Android 9. Thank you
hello guys,
any chance to see an update for the LTE version?
thanks
mrbarnie
mrbarnie said:
hello guys,
any chance to see an update for the LTE version?
thanks
mrbarnie
Click to expand...
Click to collapse
My tablet is also LTE version . What it's not working now ? Anyway many stuff will be improved in the next updates .
great thanks a lot i thought that this update is only for the lite version, which means WIFI only.
i have BTV-DL09
Build BTV-DL09C100B311
EMUI 5.0.4
mrbarnie said:
great thanks a lot i thought that this update is only for the lite version, which means WIFI only.
Click to expand...
Click to collapse
NO, LITE version doesn't mean WIFI only !