{
"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.
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"
}
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
Sailfish OS (also styled as SailfishOS[4] or abbreviated to SFOS) is a general purpose Linux used commonly as mobile operating system combining the Linux kernel for a particular hardware platform use, the open-source Mer core stack of middleware, a proprietary UI contributed by Jolla or an open source UI, and other third-party components.
{
"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"
}
It's a beautiful OS developed by the Jolla and the mer team. The UI is totally gesture based. So say good bye to your boring Android navigation bar. The OS is fast and butter smooth with zero lags. This is a totally new experience and certainly a delightful one from the same old boring mundane Android which has had almost the same UI since 5.0.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* Thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* Before flashing it! YOU are choosing to make these modifications, and if
* You point the finger at me for messing up your device, I will laugh at you.
*/
Download Lineage OS 13.1 –
https://www.androidfilehost.com/?w=files&flid=191808
Download Sailfish OS –
sailfishos-athene-release-2.1.0.10-b1-lintuxido.zip
https://drive.google.com/open?id=0B82jllncceRqQUVTSFhjdk0xeWs
Copy above downloaded zip files on your Moto G4 Plus sdcard location.
What’s working?
1) Calling, SMS
2) Camera
3) Gallery
4) Browser
5) Bluetooth
6) Wifi
7) Wifi Hotspot
8) Dual SIM
9) Mobile Internet ( For Jio,go to Settings -> Cellular network -> Under Jio Sim open Data access point -> enter connection name jionet and choose Protocol Dual )
10) Jolla Store (Partially) (need to rename or delete following repo from device etc/zypp/repos.d/ssu_adaptation0_release.repo follow the process mentioned for 3rd number bug to remove the repo. Then access jolla store, it will work now with limited applications.
Bugs:
Please note, this is a BETA release. This ROM has some bugs and I will look forward to fix them in future.
1. Bluetooth some times misbehaving
2. Android apps are not supported
3. Screen turns off while making any calls or received any calls (Press Power + Vol UP or Down to access dial pad) Due to Proximity Sensor issue call progress screen gets off (Possible Workaround follow the steps below :-
Connect to internet,
set the ssh password in developer tools
open terminal application
type following commands carefully
[[email protected] ~]$ devel-su (it will ask password which you have saved in Developer Tools,
[[email protected] repos.d]# mv /etc/zypp/repos.d/ssu_adaptation0_release.repo /home/nemo/ ssu_adaptation0_release.repo.bkp
[[email protected] repos.d]# rm -rf /etc/zypp/repos.d/ssu_adaptation0_release.repo
[[email protected] repos.d]# zypper in mce-tools
[[email protected] repos.d]# mcetool --set-ps-mode=disabled
Now try to access dial screen
4. Proximity Sensor issue
5. On miscall it produce 3 loud beeps (Not found any fix yet to resolve this issue)
6. Reboot and Shutdown is not properly working (Need to keep pressing Power Button for 2-3 mins.)
Flashing process – (Flash Lineage OS first then Sailfish OS – Follow the below given steps)
1. Boot in TWRP recovery
2. Backup your existing OS with all partitions to /sdcard location and keep this backup safe on your pc or other location before proceed further
3. Wipe cache, dalvik cache, system, data.
4. Flash downloaded Lineage OS 13.1 zip file
5. Go back (TWRP Home screen), Click on Mount and uncheck Data only
6. Now go back, Click Install, select SailfishOS zip and flash it.
7. Once flash gets complete reboot
Reboot will take some time. (There is no boot animation so you will not able to see any logo or animation during boot)
UPDATE : - SFOS 2.1.4.14 Alpha Build download link
https://drive.google.com/open?id=1kORIVWKw4m7IdncTLRC39r4wfJ3r0_3E
Whats Working : Call, Messages, Camera, Bluetooth, Headphone, Browser, Gallery etc..
Whats Not Working : Some time boot loops (Unable to Fix Yet), Video Recording, Unable to detect SIMs on first boot.
UPDATE 1 :- to avoid boot loops, unlink wlan-module-load.service as mentioned below,
cd /lib/systemd/system/multi-user.target.wants/
unlink wlan-module-load.service
reboot
UPDATE 2 SFOS-2.1.4.14 Alpha build --> https://drive.google.com/open?id=10kIbaJdy9rgRF9Pc1jX8J1iI-_YwwKYj
Whats Working : Call, Messages, Camera, Wi-FI, Bluetooth, Headphone, Browser, Gallery etc..
Whats Not Working : Video Recording, some times unable to detect SIMs on first boot (reboot it so it will detect sim )
SFOS 2.2.0.29
Alpha1 download link --> http://drive.google.com/open?id=1lxn7LwD1cOa4eGfoVQ2pB7SlKYMbQckI
SFOS 2.2.1.18
download link --> https://drive.google.com/open?id=1shTSt9v93V65pvH6QvYhfFI3rM-w00y9
SFOS 3.0.0.8
download link --> https://drive.google.com/open?id=1stulEZ3txMWiHiNVvN9cQyPzny-QJZ5n
Download Lineage OS 13.1 –
https://www.androidfilehost.com/?w=files&flid=191808
Whats Working --> Call, Messages, Camera, Wi-Fi, Bluetooth, Headphone, Browser, Gallery etc..
Whats Not Working --> Camera auto-focus and Video recordings
If you liked my work, please support me by donating.
https://www.paypal.me/lintuxido
Watch the installation process at
https://youtu.be/vwIeavVKYjQ
XDA:DevDB Information
Sailfish OS 3.0.0.8, ROM for the Moto G4 Plus
Contributors
mukesht, Mister_Magister, mal, Shreps, murigny64, sledges, r0kk3rz, saidinesh5, krnlyng, PseudoDev and other great peoples of #sailfishos-porters channel, jolla team
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 6.0.x Marshmallow (can be working with 7.0 Nougat firmware also)
Version Information
Status: Beta
Current Beta Version: Beta1
Beta Release Date: 2017-09-05
Created 2017-09-05
Last Updated 2018-11-23
Does the jolla store have apps like: WhatsApp, alternative navigation/maps, email, etc?
Thanks for the great work. Really like it but wanna make sure i can use it as daily driver with my essential apps
@halifage
as mentioned above currently very few apps present in Jolla store for moto g4 plus, once I switched to OBS then we can see more apps for our device. email is present in current store.whatsapp is not there because whatsapp has restricted access using third party application. In future I will look for the android apps support for our device.
mukesht said:
@halifage
as mentioned above currently very few apps present in Jolla store for moto g4 plus, once I switched to OBS then we can see more apps for our device. email is present in current store.whatsapp is not there because whatsapp has restricted access using third party application. In future I will look for the android apps support for our device.
Click to expand...
Click to collapse
Thanks @mukesht. Keep up the great work. Really looking forward to trying this on my device
Nice work ... Keep it up...
Thank you very much Mukesh for this ROM,
I was waiting for this since a long time.
But can you help with some few things please :
1. I am currently on June security patch, so the bootloader can't be downgraded.
2. Should I try flashing sfos on this firmware?
3. Any precautions I should take?
Your help will be appreciated
Thankx.
Aakash12 said:
Thank you very much Mukesh for this ROM,
I was waiting for this since a long time.
But can you help with some few things please :
1. I am currently on June security patch, so the bootloader can't be downgraded.
2. Should I try flashing sfos on this firmware?
3. Any precautions I should take?
Your help will be appreciated
Thankx.
Click to expand...
Click to collapse
Not a wise idea to downgrade... But yeah u can flash on nougat.... Just take a nandroid backup
cool_sid said:
Not a wise idea
Click to expand...
Click to collapse
Any solution?
Aakash12 said:
Any solution?
Click to expand...
Click to collapse
I meant not a wise idea to downgrade... Just take a nandroid backup and also separately backup ur imei and then flash over nougat only....
cool_sid said:
I meant not a wise idea to downgrade... Just take a nandroid backup and also separately backup ur imei and then flash over nougat only....
Click to expand...
Click to collapse
But isn't lineage os 13.1 marshmallow, will not it downgrade?
Thankx by the way , have you tried this, (flashing over June security patch)?
Aakash12 said:
But isn't lineage os 13.1 marshmallow, will not it downgrade?
Thankx by the way , have you tried this, (flashing over June security patch)?
Click to expand...
Click to collapse
Nope but I will try tonight... I'm running RR..
cool_sid said:
Nope but I will try tonight... I'm running RR..
Click to expand...
Click to collapse
Having bootloader of June security?
Do post here if it works fine.
cool_sid said:
Nope but I will try tonight... I'm running RR..
Click to expand...
Click to collapse
Is it running, on June security?
Aakash12 said:
Is it running, on June security?
Click to expand...
Click to collapse
No I got bootloop on los14.1... I haven't flashed cm13 cz I just read it corrupted the bootloader...
So I'll just ask someone more knowledgeable if its because of cm13 or something else.... Then I'll flash cm 13..
cool_sid said:
No I got bootloop on los14.1... I haven't flashed cm13 cz I just read it corrupted the bootloader...
So I'll just ask someone more knowledgeable if its because of cm13 or something else.... Then I'll flash cm 13..
Click to expand...
Click to collapse
@cool_sid : you need to unlock the bootloader first, Just boot device using twrp.img, make nandroid backup. Install twrp recovery. Keep firmware as it is (dont need to downgrade), boot in twrp and flash lineage 13 zip then sfos zip.
:victory: lo voy a probar, gracias por compartir
Is there any update?
And i am in love with this rom and plz plz plz add more support.
mukesht said:
@cool_sid : you need to unlock the bootloader first, Just boot device using twrp.img, make nandroid backup. Install twrp recovery. Keep firmware as it is (dont need to downgrade), boot in twrp and flash lineage 13 zip then sfos zip.
Click to expand...
Click to collapse
Mukesh, Thankx you for this suggestion,
But can you tell me will this method work for June security patch on stock rom with ,of course, unlocked bootloader?
Aakash12 said:
Mukesh, Thankx you for this suggestion,
But can you tell me will this method work for June security patch on stock rom with ,of course, unlocked bootloader?
Click to expand...
Click to collapse
@Akash12, it will not work on stock rom and I suggest you to dont try it on stock rom coz you will face boot loop issues. You have to flash lineage os 13 from twrp recovery on your stock rom after that you can flash sfos 2.1, then it will boot successfully. (make stock roms proper nandroid backup first)
mukesht said:
@Akash12, it will not work on stock rom and I suggest you to dont try it on stock rom coz you will face boot loop issues. You have to flash lineage os 13 from twrp recovery on your stock rom after that you can flash sfos 2.1, then it will boot successfully. (make stock roms proper nandroid backup first)
Click to expand...
Click to collapse
Thank you mukesh
{
"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
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）
crDroid for Sony Xperia XZ1 Compact
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Code:
IMPORTANT: Make sure you have an unlock Bootloader
Please if you have Locked Bootloader you may check this http://developer.sonymobile.com/unlockbootloader/
Code:
WORKING
- RIL
- VoLTE
- Mic
- Sound (Speaker and Headset)
- LED
- Thermal Manager
- Audio and Video Decoders/Encoders
- Camera
Code:
BUGS
- Not finding
- In this ROM tooo many settings, some may not working and this is normal ;)
- Post in this thread
Code:
HOW-TO INSTALL
- You need have stock ROM 47.2.A.11.228
- Download ROM zip
- Copy to your phone
- Enter to custom recovery and make wipe system, wipe data
- Install ROM & Gapps & Magisk
- Turn off your phone & then on
- First time phone restart itself this is normal
Code:
ADD. INFO
- If you want right bootanimation then delete bootanimation.zip on path /oem/media/
- Sim detect ~30 sec, if you choose 3G network in settings, sim detected without any delay
- Stock camera (not Sony) after first lunch write that you need insert SD Card, just go to application settings and re-switch permission "storage"
Download
HERE
Download crDroid_10
HERE
And don't forget buy me a juice
XDA:DevDB Information
crDroid, ROM for the Sony Xperia XZ1 Compact
Contributors
russel5, @derf elot @modpunk
Source Code: https://github.com/whatawurst/android_device_sony_lilac
ROM OS Version: 11
ROM Kernel: Linux 4.x
ROM Firmware Required: 47.2.A.11.228
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2021-01
Created 2021-01-28
Last Updated 2021-01-28
v1
- initial release
Hello, thank you so much, I'm interested in that many features :good:.
I'm After flashing LOS. Can you help me - how can I get flashable official firmware before installing your custom roms?
Flash all firmware 11.228 via newflasher, start up your phone. When you see first setup window you can turnoff your phone. Then flash custom recovery and see how to install in this OP
russel5 said:
Flash all firmware 11.228 via newflasher, start up your phone. When you see first setup window you can turnoff your phone. Then flash custom recovery and see how to install in this OP
Click to expand...
Click to collapse
Thank You, I'll do it asap
Hello, unfortunately i experienced bug after flashing aex, crDroid and after all them LOS in twrp. Previously I had downloaded stock, deleted all ta files create partition folder and then flashed stock firmware by newflasher (dedicated to my country). That was fine, also fastboot reboot bootloader and fastboot boot twrp was ok. I wiped indicated in instruction partitions/format them, and after booting to system. I was uneable to use it. I'll attach pictures. I could only one think. Use power button to see power options and navbar (in crproblem.jpg file you can see superimposed navbars... strange). (after i firstly saw problem i wiped them all and tried to reinstall ROM with same result new thing is not working LOS) Maybe I should choose other firmware from newflasher (maybe uniwersal, working in all country?). Now I'm forced to use stock, because of custom ROMs doesn't work.
While I was flashing stock, newflasher asked me "if I want to flash persist partition" I chose n
I really need help, (stock rom sucks and I don't want to use GApps because of privacy issues.)
if you have same problems on all custom roms than you do something wrong.
try flash stock rom and start your phone, make a first settings and other thing.
russel5 said:
if you have same problems on all custom roms than you do something wrong.
try flash stock rom and start your phone, make a first settings and other thing.
Click to expand...
Click to collapse
Thank you, I succefully installed taht wonderful ROM . I think it'd be good to mention in a main post that before you install zip yoru device must be fully configured (first configuration is enough, not needed to look in Google account) and have set pattern (it worked for me) without it did not work, you can see only black screen like in a previous post.
Maybe it took part, maybe not but after first configuration I copied twrp.img to SD card and booted twrp from fastboot "fastboot reboot bootloader" then "fastboot boot path_to_img_file/twrp.img" after boot I installed twrp by install ==> install ==> install image ==> twrp.img as a recovery only then I started with next steps
Thank you for supporting me with device problems and answering noob questions I'll test that ROM and give feedback if I have time.
russel5 said:
crDroid for Sony Xperia XZ1 Compact
Click to expand...
Click to collapse
There is no selinux support
This is TREBLE project, selinux only in permissive mode
Love, love, loving this ROM! The level of customization is awesome and it is such a beautiful display. I haven't been able to test every setting but I will continue to tinker with it. Thank you so much for the hard work!
P.S. - Sent you some juice money
One thing I noticed, I can no longer send mms without having mobile data on. I was always able to send mms without it on stock fw, cricket/att network but now it has to be on to send and receive pictures and other mms. Is there a setting I'm missing?
Thanks
First, big thanks for juice.
Today I will update rom, seems VoLTE has been fixed.
About your problem, don't know, mms is so old feature never used it. Check your apn or try reset your internet option.
Thread updated, see post #2
Still testing things but I used my phone for work today and really liked the responsiveness of this ROM. I use Google Maps a lot and there was always some lag on the stock fw but none that I could notice on the crDroid. This ROM boots quick and loads resources quick.
I flashed update after work and it seems more stable. I had one minor freeze on v1 and home screen would crash when I was trying to set it up but I also have nova launcher and that might have conflicted. V2 has had no crashes and after setting up the home screen, I just might ditch nova for a bit. Again, I love this ROM.
As far as the MMS goes, I can't find an option to download new internet settings like stock had. I reset apn but still can't send mms without data. It's not a deal breaker but now I'm super curious. Could it be related to the RIL? I honestly don't know, I'm just learning as I go but if that's the case is there anyway to restore the stock RIL? Like replacing the telephony-common.jar?
Thanks again for all your hard work
I'm interested to get the best sound on our device (I created another thread about that).
Here I just want to confirm that rom works with dolby digital plus from here, after freeze audiofx: https://forum.xda-developers.com/android/software/mm-p-dolby-digital-plus-arise-20181115-t3868192
Next is xperia keyboard, I flashed it successfully (but remember to mount system in twrp before install process). Note: After updating rom it is always disappears (it's mentioned in its thread)
Here is it: https://forum.xda-developers.com/android/apps-games/sony-z3-keyboard-lollipop-update-t3056448
Hello,
I want to report that "long press home" doesn't work when swipe-up gestures are enabled
I tried to upload video where I tried to use it but xda app treats mp4 file as invalid.
VoLTE don't work for me.
ROM is very fast and very customized but sometimes WhatsApp and others apps don't show correctly the notifications.
How to install new fonts？？
JanoGT said:
VoLTE don't work for me.
ROM is very fast and very customized but sometimes WhatsApp and others apps don't show correctly the notifications.
Click to expand...
Click to collapse
Hi, on your stock rom volte works?
If yes, share here your oem.sin from stock rom, thanks.