[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project
CyanogenMod is a free, community built distribution of Android 5.1 which greatly extends the capabilities of your phone.
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 at you.
*/
XDA:DevDB Information
[DEVELOPMENT] - CM12.1 - Android 5.1 - FreeXperia Project, ROM for the Sony Xperia Z3
Contributors
jerpelea
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2014-12-02
Last Updated 2015-04-13
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
Homepage
www.freexperiaproject.net
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
jerpelea said:
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
Click to expand...
Click to collapse
Repo link? download link? Whats working?
Thread cleaned.
Lets try and keep this one on the right tracks.
Bug reports with LOGCATS are OK, off topic chatting is not!
???Where is the rom
Where is the rom ?? is everything working?
adidouh113 said:
Where is the rom ?? is everything working?
Click to expand...
Click to collapse
http://fxpblog.co/cyanogenmod/cyanogenmod-12/
The build for Z3 isn't listed yet though, I hope OP will add it soon
we have enabled daily builds
if your device is not yet in the list will appear soon (1 day,1 week, 1 month) no ETA please
but you have to remember that is an early alpha build
Please do not ask for what is working or not
It is an early Alpha build. If you do not know what that is then DO NOT FLASH IT.
The point of this is for you to flash it, test what is working or not and provide feedback WITH LOGCATS so others can try and fix it.
Thread cleaned (Again)
Thread closed until there is a build available
Thread cleaned
@jerpelea, please PM a mod or report this post to get the thread re-opened immediately.
Thread opened, build is now available
WiFi is working. But systemui crashes as soon as you lock the phone. After a restart it crashes instantly. Looking forward to the next build.
---------- Post added at 01:42 AM ---------- Previous post was at 01:39 AM ----------
nimrodity said:
sorry but care to give any more info on what works and what doesn´t. Also where is the link, I am to dumb to find it
Click to expand...
Click to collapse
Link is http://fxpblog.co/cyanogenmod/cyanogenmod-12/
SystemUI - crashes can be fixed by adb pushing SystemUI from AOSP lollipop. All crashes now gone (including screen off). I'd suggest only those who know their way around adb try this (you need to r/w mount through adb shell) - here's the replacement SystemUI apk (it's from my latest 5.0.1 r2 build hehe) https://drive.google.com/open?id=0B0uD0ZLDjONjRW0xWS12MGF4OWc&authuser=0
Wifi - all good, nice to be able to access google drive, mail, play store etc
Camera - installed google camera - fc's as expected
SU permissions all good
Modem - cellular connected after pushing modem files and ril libs
Pleasantly surprised by first build - will test more stuff and report back..
{
"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"
}
iBuzman said:
SystemUI - crashes can be fixed by adb pushing SystemUI from AOSP lollipop. All crashes now gone (including screen off). I'd suggest only those who know their way around adb try this (you need to r/w mount through adb shell) - here's the replacement SystemUI apk (it's from my latest 5.0.1 r2 build hehe) https://drive.google.com/open?id=0B0uD0ZLDjONjRW0xWS12MGF4OWc&authuser=0
Wifi - all good, nice to be able to access google drive, mail, play store etc
Camera - installed google camera - fc's as expected
SU permissions all good
Modem - cellular connected after pushing modem files and ril libs
Click to expand...
Click to collapse
Did you need to manually push modem files and ril libs? Or are they in the build from the fxpblog.co site ?
^^ manually, I had them on hand (my 4.4.4 kitkat files) after grabbing them when trying to get lollipop aosp working.
iBuzman said:
^^ manually, I had them on hand (my 4.4.4 kitkat files) after grabbing them when trying to get lollipop aosp working.
Click to expand...
Click to collapse
Is that possible for you to share those files? I'd really like to use the build if modem is working Thanks!
^^ I'm away from pc for rest of night.
modem:
mba.b00 & mba.mbt plus all modem.b00 thru modem.b25 & modem.mbt ~ all from stock kitkat. abd push into /etc/firmware/
ril libs:
libril.so and librilutils.so from stock kitkit. adb push into /system/lib/
cant remember if I remembered (if that makes sense..) to abd push rild into system/bin hehe ~ I think I forgot to do it but worked anyway
you should be able to get away with doing in root explorer instead of stuffing around with adb pushing. you have r/w mount system via root adb root shell first (took me ages to get permissions to push system files.. plus what I do is very hit and miss.. n00b hacking away blindly lol).
---------- Post added at 07:46 PM ---------- Previous post was at 06:53 PM ----------
of course a flashable zip with systemui, modem and ril patches would be best - I'll see if I can learn how to make one (seeing we'll probably need it for a while yet).
probably try to put all the patches into the gapps flashable I think (why reinvent the wheel and I have to flash it already anyway)
thread cleaned again.
The build is in the download section for cm12 on the link given by the op.
Do not ask what us working, flash it and provide the feedback via a logcat. This is an alpha rom.
Do not flash it if you do not want to test it.
mobile seems to be somewhat working... goes in and out on me. was the file modem/mba dot MBT or MDT ?
mms - seemed to receive a few , but couldn't reply
calls - received one but it dropped. when i tried to call out i received an error with phone.ui (or similar)
iBuzman said:
^^ I'm away from pc for rest of night.
modem:
mba.b00 & mba.mbt plus all modem.b00 thru modem.b25 & modem.mbt ~ all from stock kitkat. abd push into /etc/firmware/
ril libs:
libril.so and librilutils.so from stock kitkit. adb push into /system/lib/
cant remember if I remembered (if that makes sense..) to abd push rild into system/bin hehe ~ I think I forgot to do it but worked anyway
you should be able to get away with doing in root explorer instead of stuffing around with adb pushing. you have r/w mount system via root adb root shell first (took me ages to get permissions to push system files.. plus what I do is very hit and miss.. n00b hacking away blindly lol).
---------- Post added at 07:46 PM ---------- Previous post was at 06:53 PM ----------
of course a flashable zip with systemui, modem and ril patches would be best - I'll see if I can learn how to make one (seeing we'll probably need it for a while yet).
probably try to put all the patches into the gapps flashable I think (why reinvent the wheel and I have to flash it already anyway)
Click to expand...
Click to collapse
if you have the zip ill be happy to test the rom and the zip. Needing my Phone "on the road" so without calls and mobile-data i cant test the rom
Related
Temasek's UNOFFICIAL CM13.0 BUILDS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will attempt to get builds out as soon as Temasek releases a new version, however due to commitments i may miss a release. I will not upload a ROM until i have flashed it myself. Please report any bugs or issues that you see; when applicable, Thank you.
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
...not ready yet
A WORKING version TWRP is required i use Official TWRP 2.8.7.2
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Ensure you’re on the latest vendor image from google - https://developers.google.com/android/nexus/images
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
probably something i havn't found as yet
@temasek
@apascual89 - Developer of nexus 9 temasek dark
@Chainfire
CM Team, CyanogenMod
@DrawnToLife
@zawata
@joshuabg
@craigacgomez
Source
Orignally forked from CyanogenMod
Kernel Source
Device Tree
Temasek Source
Rom Source
Changelogs
https://github.com/temasek/Changelogs/blob/cm-13.0/cm_hlte-Changelog.txt
Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65562191&postcount=652
Basketbuild Download - Backup Download Location (OR for those not in Google Shares)
https://basketbuild.com/devs/Joshndroid/Temasek Roms/flounder
GApps - Lollipop 5.1 64 Bit GApps Package
http://opengapps.org/
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to Chainfire
http://download.chainfire.eu/supersu
and one more.
okay rom is now uploaded onto basketbuild. Please follow link in post 2.
i recommend clean flash from another rom as usual. If dirty flashing in the future there is no necessity to flash gapps again, however sometime i do notice supersu goes a bit funny so i would recommend reflashing supersu just to be safe. failing that you can just install it again from market and cause it to update via openrecovery script.
awesome !!! love this rom on my N6 . and now also on my N9 thanks !!!
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
nericollin said:
Currently going through 2nd attempt at flashing. Used 64-bit GApps and linked SuperSU. Followed instructions for coming from another ROM. 20 minutes passed without a boot so I'll attempt again without flashing SuperSU until it (hopefully) boots up and I complete the setup screen.
Click to expand...
Click to collapse
Let me know otherwise I will full wipe again and try again myself
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
I know the change log is on the device once you flash the ROM. But I would like to know the changes that have been made besides what is in CM12 already.
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Does LTE work on this ROM?
Alright. Thanks man. I'll just flash it and play around
Edit:: Flashed it. Everything running great. One thing I have been looking for in several ROMs is the ability to put the nav bar on one side while in landscape. I kinda sucks having the bar at the bottom of my screen when it would be much more convenient right by one of my hands whole holding in it landscape. Is that possible here or in any rom yet.
joshndroid said:
Err... Far to many to list. Notification tweaks, button tweaks, stylus options, status bar options as well as others in temasek spare parts. That is a cm12 theme the standard colors would be regular cm in the attached screenahot
Click to expand...
Click to collapse
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
joshndroid said:
Guessing it went well this time round might make a change to the op to not recommend SuperSU flash on clean flash
Click to expand...
Click to collapse
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
Click to expand...
Click to collapse
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
zawata said:
FINALLY!!! hahaha kidding great job
Fianlly pass your updater error? What fixed it?
Click to expand...
Click to collapse
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
nericollin said:
My apologies for the late response, I fell asleep earlier than normal.
It never ended up getting to the setup screen. I wonder if this has something to do with the format of the system partition.
---------- Post added at 08:02 PM ---------- Previous post was at 07:45 PM ----------
UPDATE: the file system was in fact the problem. Changed it to F2FS and it works now even flashed the SuperSU zip too.
Click to expand...
Click to collapse
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
joshndroid said:
Reverted the bootable cm commit that was pointing to a register.inc for a 32 bit executable
. the one I highlighted to you about a week ago. Just tracking my own bootable for now.
Excellent that is good to hear. Were you originally partitioned to ext4 ?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I was! I figured it must have been that because I remember changing it from F2FS to ext4 when development for the N9 was still in early stages.
The ROM runs amazingly now though! Awesome job! Will report feedback if any issues arise!
andreglud said:
Does LTE work on this ROM?
Click to expand...
Click to collapse
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
joshndroid said:
I see some apn data in there that is required for LTE service to work yet I don't see a specific commit for it as Zawata did for his device tree.
Click to expand...
Click to collapse
So in short, I shouldn't expect it yet?
Not necessarily. I don't have a LTE device to try it on, so I can't just flash it and let u know.
disregaurd, didnt realize there were more replys
{
"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"
}
Brought to you by @nailyk!
Notice: Thread missing information/ credits/ mentions/ stuff etc etc. Work in progress.
All credit for this ROM must go to Nailyk as the main developer of Omni for Leo devices. I am just a tester / thread maintainer for Leo (Z3).
Disclaimer:
Code:
/*
* 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 me for messing up your device, I will laugh at you.
*
*/
Who can use it?:
This ROM is only for Xperia Z3 users with UNLOCKED and (preferably) UPGRADED bootloaders!
How to install:
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x)
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen / wait for purple LED on boot and press volume up key
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
(After first boot if you have initial issues try a second reboot and see if it stops. If not, clean install)
Rolling back to stock:
- Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
TWRP:
See Nailyk's TWRP build here for best compatibility (based on Omni sources):
TWRP 3.1.x-x
GAPPS:
Flash any 7.1.2 compatible Gapps package. I suggest OpenGapps.
Alternatively Microg and fdroid will serve you well as an alternative to Google Play Services.
Releases:
Latest:
2017-12-13: Android File Host Download
Mirror: releases.nailyk.fr/omnirom
Change Log: CVE Patches
TWRP 2017-11-21: Android File Host Download
Previous:
2017-12-02: Android File Host Download
Change Log: Fixed scripts for modem files at first boot. No issues with SIM detection, manual script running etc now.
2017-11-21: Android File Host Download
Change Log: Updated Security Patches to latest. No change to ROM.
2017-10-17: Android File Host Download
Change Log:
Code:
Lot of important changes here,
- Device was renamed z3 instead of leo,
- This release ""should"" support all leo variants. However, the script is on early stages: expect troubles.
In case of problem with RIL process the following:
Reboot into recovery,
connect to shell then:
Code:
mount /system
ln -s /system/vendor/etc /vendor/etc
sh /system/etc/init.blobs.sh
This build is patched against wpasupplicant attack (krackattack)
Some improvements about external sdcard & charging.
2017-09-28: Android File Host Download
MD5 Sum: b431c2c720be4a4dfd365a8343ca8115462a3393
Root etc:
For root it is suggested that you see phhSuperUser here: phhSuperUser Thread
Flash options such as Magisk or SuperSU if you wish, but there is not guarantee of support. Magisk 14.0 was tested by myself and working at first release.
Contributors:
@nailyk,
@xkeita, @tomascus, @derf elot, @TheavenginTitan
@tomgus1, @gr8st, @mcgi5sr2, @doriandiaconu, @Robot76, @panzerox123
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information:
Status: Beta
Logs:
This post will describe how to take logs.
If you are using the ROM and want to make development faster/ easier please simply take a log and post it here in the thread for us to check out.
Take logs when you notice bugs etc and try to reproduce them when taking the log and give us some description of the problem.
First you will need ADB:
Set up any adb environment on you PC (showing windows here for eg.- Linux/ Mac differs):
- For windows a minimal installation will be enough to take logs and takes 15 seconds.
15 second ADB Installer
Then open the folder it is installed to so you see "adb.exe" (obviously different on Linux/Mac).
Open and CMD window in the folder with adb and you can connect your phone.
Enable USB Debugging on the phone!:
Go to Settings - About Phone - Build Number (tap this until Developer options unlocks)
Go to Developer Options and enable "USB Debugging".
Now take the actual logs running adb logcat:
- Back to the PC CMD window.
- When you run the command a window will pop up on the phone asking for access. Say yes.
- Run the command - " adb logcat > logcat.txt "
- This will give you a text file with the log to post to us.
If possible take a dmseg /kmsg:
This is most useful for bootloops etc
You may need root on the device to access these:
- " adb shell su -c dmesg > dmesg.log "
- " adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log "
Screenshots
Screenshots thanks to @Tux111. Find some of his comments and hit thanks for him!
Full showcase of screenshots here: MEGA
What working?
@Dobsgw When you will update missing informations, could you please share informations about changelogs, what works, whats not, special features and some screenshots?
All the users (me too) will appreciate a lot.
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Dobsgw said:
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Click to expand...
Click to collapse
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Tux111 said:
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
Click to expand...
Click to collapse
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
tiliarou said:
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Click to expand...
Click to collapse
Xkeita TWRP is fine.
Nailyk also has a brilliant TWRP version found here in the forum.
It is updated to latest just ignore the title. 3.1.1-3
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
D6603 single SIM.
Can't provide right now, sorry.
EDIT: I'll provide it soon as possible!
How i have to make radio log?
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't upload here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Tux111 said:
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't uploader here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Click to expand...
Click to collapse
Thank you for taking the time to look into this.
Hopefully not a big issue
Mobile data D6603 german working LTE
Sent from my unknown using XDA-Developers Legacy app
edit
New twrp works fine and omnirom build too! Thx for hard work! ? Greets from German
Sent from my unknown using XDA-Developers Legacy app
App not using SD card photo ecc
Inviato dal mio unknown utilizzando Tapatalk
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
leo31 said:
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
Click to expand...
Click to collapse
You will have a brick.
Nothing you can do when unlock allowed:no.
The only thing is to contact sony, it is illegal (in some countries) to have an unlockable bootloader.
The images and most of the files do not use the sd card and when you want to pass applications to the system it does not allow attachment screenshot.
You could also add the option to expand the desktop and resize the navigation bar.
{
"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 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
Working
Boot
Mobile data
Cam (pics only)
flashlight
fingerprint
sdcard is recognized/mounted
Unknown/Untested
GPS
NFC
calls/sms (should work i guess, because data works)
audio (cant test that in class )
Issues
USB
Wifi
Bluetooth
Recording
Brightness change
Everything i forgot probably
As you can see on the "Working" list, this is a highly experimental build, flash at your own risk, and don't come crying to me if it should brick anything (it didn't for me, but seeing from the TWRP Thread the V30 can be picky).
Dont forget to make a backup!!!
If you want to report any bugs, NEVER do it without providing logs. I can't try to fix things without logs.
Helpful log commands:
logcat (usage: e.g. logcat > /sdcard/logcat.txt )
dumpsys (usage: e.g. dumpsys SurfaceFlinger > /sdcard/dump_sf.txt)
dmesg (usage: e.g. dmesg > /sdcard/dmesg.txt , might need root)
for more examples on how to use the commands, either google (do that first) or ask (only do this if you already googled how to use those commands).
FAQ
USB isn't working. How do I get logs?
In the ramdisk theres a nice little script which will print the logcat to /data/ramoops/cm14.1_<number>_logcat_<date/time>.txt
The logcat is many many hundreds of MB in size, why?
Its currently spammed with something like this:
Code:
E/QMI_FW ( 674): xport_reg Failed for service_id=0x35 version=0x1001 on 15
Replace
Code:
[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].[0-9][0-9][0-9] E/QMI_FW ( [0-9][0-9][0-9]): xport_reg Failed for service_id=0x35 version=0x1001 on [0-9]*[0-9]
in the log with your favorite editor which can use regex with nothing (or delete all those lines if you have that option)
Is there another way to get some logs?
In Developer Options, turn on "Local Terminal", and get a logcat or other logs with that.
The screen glitches, is there a way to fix this?
I hope so, working on this too.
After restoring my backup with TWRP, my phone won't recognize my PIN (not SIM PIN). What todo now?
Just follow the guide on here. Afterwards you have to setup your PIN again (also Fingerprints, and enable Trusted Agents in Settings -> Fingerprints & Security)
Download
Version 0.0.2: https://www.androidfilehost.com/?fid=962187416754470110
Version 0.0.1: https://www.androidfilehost.com/?fid=818070582850487924
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the LG V30
Contributors
SGCMarkus
Source Code: https://github.com/SGCMarkus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-01-25
Last Updated 2018-01-25
Changelog
v 0.0.1 Initial build
it boots
v 0.0.2
Mobile data works
Cam works (pictures only)
fixed graphics glitches
Fingerprint works
flashlight works
SDCard is recognized
If you are interested to contribute/help out/test, hit me up in PM, or join my Discord Server: https://discord.gg/DJRnTRC
I set it up to be a general server for all kinds of LG V30 things, but also for Developers to meet and talk to each other, and help each other out.
Downloading...
I'll try to flash it. I'm new on LG devices (come from Samsung...)
It BOOTS
Mike.YT said:
It BOOTS
Click to expand...
Click to collapse
I agree... FC everywhere
But I hope it's a first step...
Exam time here though, so i couldnt really work on this more :/
But i have hope now for actual Treble support (we have a partition called OP, idk how important the stuff in there is though, 344MB if im not wrong, gathered all the Oreo blobs from the V300S kdz (i hope i have all needed ones), and those take up 324MB xD)
But atleast already a working recovery (TWRP 3.2.1) which would recognize the /OP as /vendor
Will work on each project a bit more when exams are over
i don't know if can help someone to build lineage or aosp based rom, btw here are the link to source and kernel for v30:
h930: http://opensource.lge.com/osSch/list?types=ALL&search=h930
us998: http://opensource.lge.com/osSch/list?types=ALL&search=us998
v300: http://opensource.lge.com/osSch/list?types=ALL&search=v300
Here the content of readme:
1. Android build
- Download original android source code ( android-7.1.2_r4 ) from http://source.android.com
( $repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r4
$repo sync -cdq -j12 --no-tags
$repo start android-7.1.2_r4 --all
)
- Untar opensource packages of LGH930_Nougat_Android.tar.gz into downloaded android source directory
a) tar -xvzf LGH930_Nougat_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf LGH930_Nougat_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.4
b) mkdir -p out
c) make ARCH=arm64 O=./out joan_global_com_defconfig
d) make ARCH=arm64 O=./out CROSS_COMPILE=$(pwd)/../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- KERNEL_COMPRESSION_SUFFIX=gz -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image.gz) at out/arch/arm64/boot
Click to expand...
Click to collapse
I always loved to know how to build Kernel or ROM.
I'm not a dev so i cannot solve any FC or any other problem, so I need to know where to get the sources.
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all ?
SGCMarkus said:
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all
Click to expand...
Click to collapse
heheh don't give up my little dev... We believe in your skill :good:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
SGCMarkus said:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
Click to expand...
Click to collapse
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
foamerman said:
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
Click to expand...
Click to collapse
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
SGCMarkus said:
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
Click to expand...
Click to collapse
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
foamerman said:
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
Click to expand...
Click to collapse
Try it without gapps, its not worth to setup all that, it isnt daily driver ready... and gapps would just add more (unneccessary) stuff to the log ^^
--snip--
Well I tryred it but I got error 7 thats all I got
foamerman said:
Well I tryred it but I got error 7 thats all I got
Click to expand...
Click to collapse
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
SGCMarkus said:
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
OK I unzipped the file and deleted the (.zip/META-INF/com/google/android/updater-script) OK now I need a little help I'm a little slow I'm not sure how to zip it back up
{
"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.
*
* 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.
*/
Keep in mind, this ROM, and all Pie ROMs in general, are still under construction, it will take a while till all features you might know and love from Oreo are ported over to Pie.
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Flash
GPS
What's not working :
DAC(Works in USB AUdio Player Pro and Onkyo)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
As every other Pie ROM its still in early development, features will appear with time.
Instructions :
Download the build
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Downloads removed temporarily (see last post in here)
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
XDA:DevDB Information
Dirty Unicorns Pie for LG V30, ROM for the LG V30
Contributors
SGCMarkus, me2151
Source Code: https://github.com/DirtyUnicorns
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Version Information
Status: Alpha
Created 2018-09-30
Last Updated 2018-09-30
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 29.09.2018
- Initial release
Release 30.09.2018
- Updated Sources (fixes camera issues)
Release 06.10.2018
- Updated Sources
- Added QuadDAC Control Panel (Settings -> Sound -> Quad DAC at the very bottom) + Quick Settings Tile
- Widewine should be L1 now
- Brightness settings are now aligned with stock -> should fick AoD Blackscreen bug
- Support for the H930D (not to confuse with the H930DS, both are dual sim)
- Seperate download link for the H932 (thanks to @me2151 )
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Which Models are supported?
A. So far it works well on the H930(G/DS), US998, VS996 and LS998 (use H930 zip). Other models may have broken RIL or bootloop. People with a H932, please use that zip.
Nice one. Markus strikes back Thanks for another great rom Do you thing about porting Pixel Experience or Paranoid Android ?
Can someone please provide an alternate download. On AndroidFileHost it takes ~10 hours to download that file.
Dizzyrul3z said:
Nice one. Markus strikes back Thanks for another great rom Do you thing about porting Pixel Experience or Paranoid Android ?
Click to expand...
Click to collapse
PE is currently working.
Dizzyrul3z said:
Nice one. Markus strikes back Thanks for another great rom Do you thing about porting Pixel Experience or Paranoid Android ?
Click to expand...
Click to collapse
Check git, and see that Im not alone on this one ^^
Theres a damn lot what @me2151 did. Idk if we would even boot yet without him.
Also... I plan to keep it down on Pie ROMs, not doing the same anymore as with Oreo, thats too much hassle to maintain. Maybe 2 or 3 ROMs max from me, but we have other developers too (and its all open source, everyone can build their own ROM)
Congratulations and Many Thanks, @SGCMarkus and @me2151.
Dual Speaker Mod?
Thanks for the amazing work! I saw on the forums something about a dual speaker mod https://forum.xda-developers.com/lg-v30/development/rom-boombox-v30-t3765275
is that something that might show up in pie roms? thanks again!
Also what kernel is everyone using?
Diego1751 said:
Thanks for the amazing work! I saw on the forums something about a dual speaker mod https://forum.xda-developers.com/lg-v30/development/rom-boombox-v30-t3765275
is that something that might show up in pie roms? thanks again!
Also what kernel is everyone using?
Click to expand...
Click to collapse
There is a dual speaker mod in the appropriate section on the forums, I can't give you the link currently but I'm sure it's easy to find.
Flash gapps too or included??
chalmizzle said:
Flash gapps too or included??
Click to expand...
Click to collapse
Gapps NOT included - you have to flash them by yourself! Remember to select Android 9.0
FcBayernMinga said:
Gapps NOT included - you have to flash them by yourself! Remember to select Android 9.0
Click to expand...
Click to collapse
Thought as much ? thank you
Gonna push a new version today (after it compiled)
Updated sources, which also includes a fix for crashing of the GCam by @cstark27 (https://gerrit.dirtyunicorns.com/#/c/4501/ this is the fix btw)
Will edit this post as soon as its up (just so someone who plans to download might wait a bit ^^)
Release 30.09.2018
- Updated Sources (fixes camera issues)
will we ever see the miui on v30?
Many Thanks, @SGCMarkus and @me2151.
This ROM work on H930DS too?
stradfred said:
Many Thanks, @SGCMarkus and @me2151.
This ROM work on H930DS too?
Click to expand...
Click to collapse
Yes, just installed on H930DS and restoring apps from cloud.
Both sims are identified.
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Installed on H930DS without any glitches.
Great job @ SGCMarcus
---------- Post added at 06:15 PM ---------- Previous post was at 06:10 PM ----------
SGCMarkus said:
Gonna push a new version today (after it compiled)
Updated sources, which also includes a fix for crashing of the GCam by @cstark27 (https://gerrit.dirtyunicorns.com/#/c/4501/ this is the fix btw)
Will edit this post as soon as its up (just so someone who plans to download might wait a bit ^^)
Release 30.09.2018
- Updated Sources (fixes camera issues)
Click to expand...
Click to collapse
Hi,
Thanks for your work.
I do not see any camera app installed. Do I need to install camera separately ? If yes, would you be able to point out the app that has been tested to work on your rom?
Thanks again.
Very nice. Everything seems alright on US998 with TMobile. WiFi calling is enabled too ?. One thing I noticed is that if you enable show touches on developer options, the screen goes crazy every time you scroll or change windows. Thanks again for this rom!
Edit: Is there anyway to port the LG stock Oreo camera to this? It records nicely in 60fps. Can anyone extract it from oreo and upload it? Will it work? I just noticed that the rom has no camera lol
:good::good: Enjoying some tastt pie right now!! Thank you SGCMarkus!! PowerAmp and GStomper Studio had no problem using hi-res portion of dac!! Using cstark's gcam, with google motion!! I didn't see any root management, when Adaway asks for privileges, you better hit "Grant"!! :laugh::laugh::laugh:
KanBorges said:
Very nice. Everything seems alright on US998 with TMobile. WiFi calling is enabled too . One thing I noticed is that if you enable show touches on developer options, the screen goes crazy every time you scroll or change windows. Thanks again for this rom!
Edit: Is there anyway to port the LG stock Oreo camera to this? It records nicely in 60fps. Can anyone extract it from oreo and upload it? Will it work? I just noticed that the rom has no camera lol
Click to expand...
Click to collapse
Would also be interested in knowing whether LG cam works or not (doubtful).
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 !