Develop Bugs

[ROM][MTK][STOCK] fairphone FP1 kitkat 4.4.4

This is Android 4.4.4 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.4 - but most likely not all. Major security hole detectors are green now (VTS, Bluebox, Zimperium).
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/filedl/devs...mhoffmann/fp1-kk-stock/fp1-kk444-CH-0.9.7.zip MD5sum: 9140c93ff8f2b8327fdd330d2448c16f
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
- CTS is complaining about some issues. https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
- As this is a merge of 4.4.4 into the MTK stuff, watch out for more bugs than the previous release. Not merged: the new 4.4.4 dialer screen (we stick with 4.4.2 dialer as the modifications are too heavy), chromium does not support wml anymore (who cares?).
- You most likely need to wipe to install this when coming from the previous KK version to 4.4.4. Email app e.g. seems to crash without.
- Playstore version of Google Authenticator does not work (see https://github.com/google/google-authenticator-android/pull/4). Use the OSS version https://github.com/google/google-authenticator-android/releases - this is not specific to FP1 but seems an MTK issue.
- A dirty update (without wipe) from 0.8 on an encrypted device seems to reboot once during the "Android is upgrading" dialog
- Sometimes the lower part of the homescreen launcher seems to lose transparency.
Changelog fp1-kk444-CH-0.9.7 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAY-2016 (https://source.android.com/security/bulletin/2016-05-01.html)
- Kernel CVEs including the mediatek wifi ones from https://source.android.com/security/advisory/2016-03-18.html, CVE-2016-2549, CVE-2016-2847, CVE-2016-2547, CVE-2016-2546, CVE-2016-2545, CVE-2016-2384
Changelog fp1-kk444-CH-0.9.6 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 2-APR-2016 (https://source.android.com/security/bulletin/2016-04-02.html)
- Kernel CVEs including the one from https://source.android.com/security/advisory/2016-03-18.html, CVE-2015-7550, CVE-2016-0774, CVE-2016-0821, CVE-2016-0723.
Changelog fp1-kk444-CH-0.9.5 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-MAR-2016 (https://source.android.com/security/bulletin/2016-03-01.html)
(incl. the kernel fixes that Google only publishes for Google One / Sprout - ported to MT6589)
Changelog fp1-kk444-CH-0.9.4 (you might want to check if there are new gapps here as you need to flash them again at same time: http://opengapps.org/):
- Android Security Updates from Google bulletin 1-FEB-2016 (http://source.android.com/security/b...016-02-01.html)
- Kernel CVE CVE-2015-8785
Changelog fp1-kk444-CH-0.9.3:
- Android Security Updates from Google bulletin 1-JAN-2015 (http://source.android.com/security/bulletin/2016-01-01.html)
- Some kernel CVEs (CVE2015-8543, CVE2015-8575, CVE2015-7509)
- Attempt to fix German's E-PLUS on O2 roaming
Changelog fp1-kk444-CH-0.9.2:
- Fix that you can now call funny numbers like *143# without phone application crash
- Fix to be able to add contacts to SIM card
Changelog fp1-kk444-CH-0.9.1:
- several kernel CVEs (CVE-2015-5697, CVE-2015-8539, CVE-2015-8215, and a few more without CVE yet)
- the december 1st security advisory bulletin skia issue introduced in 0.9.0 - aka as the dilbert bug - is fixed now
Changelog fp1-kk444-CH-0.9:
- android security bulletin https://source.android.com/security/bulletin/2015-12-01.html
- also update gapps if you install them: http://opengapps.org/?api=4.4&variant=nano
Changelog fp1-kk444-CH-0.8:
- google location providers are used now, which should enable network location provider (in case you installed google apps).
Changelog fp1-kk444-CH-0.7:
- National roaming should be fixed (at least as good as CM). If you still have issue with national roaming, send me your mmc/mmn data.
- Use original FP1 lens parameters for fm50af lens - does this improve the auto/manual focus issues that some people reported compared to stock FP jellybean?
- Attempt to fix the problem where sometimes the scrollbar and recents screen stopped working and screen locked despite having higher screen timeouts.
- Full CTS result: https://christianhoffmann.info/2015.11.29_16.17.03/testResult.xml
Changelog fp1-kk444-CH-0.5:
- SELinux enforcing
- Camera app now shows all resolutions
- adb now requires acceptance of adb key
Changelog fp1-kk444-CH-0.4:
- ro.adb.secure set
- browser default pages revisited (removed wrong thumbnail).
- removed MTK root CAs that are not in AOSP
- fixed remaining security false-positives in VTS and Bluebox Trustable - all green now
- USB default setting should be MTP now
Changelog fp1-kk444-CH-0.3:
- More CVE fixes (e.g CVE-2015-3845). VTS and Bluebox Trustable are almost green. For some reasons they still think "Stagefright" is not fixed. Zimperium nevertheless shows all stagefright OK. Edit: found out why. It's false positive as MTK reports errors in MPEG4Extractor differently than stock.
Changelog fp1-kk444-CH-0.2:
- Netflix issue fixed with new blob from E3
- Some CTS issues fixed
- More security fixes CVE-2014-7911
Changelog fp1-kk444-CH-0.1:
- Upgraded to 4.4.4_r2.0.1: Yay! That was an insane amount of work. The following "shortcuts" were taken:
-- Chromium sources taken from AOSP - MTK added wml but it was too much work to merge this back in
-- Email app sources taken from aosp - MTK customized something there esp. exchange sync, is that really giving someone problems?
-- Dialer app taken from MTK without 4.4.4 updates - that stuff is too heavily customized also for dual sim, and 4.4.4 revamped the UI, so this was just too much work for now.
- Latest security fixes up to November 2015. Security fixes also for wpa_supplicant_8 (thanks to Michael Bestas for collecting them for CM)
- Kernel sec fixes
- FP1 power profile xml (does this actually change anything)
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.

Reserved - why do all people do this?

chrmhoffmann said:
This is Android 4.4.2 kitkat compiled from scratch from some other device sources that you find on the web. Adapted to fairphone FP1(U).
It includes various security fixes on top of 4.4.2 - but most likely not all.
NOTE: PHONES CAN BE LIFE SAVERS. DON'T RELY ON THIS PHONE AS YOUR SOLE COMMUNICATION MEANS. I HAVE NOT TESTED EMERGENCY CALLS, NOR CAN I GUARANTEE THAT THIS PHONE WILL WORK IF YOU ARE IN DANGER. CARRY ANOTHER PHONE WITH YOU. DON'T GO FOR A 3 DAY HIKE ONLY WITH THIS PHONE!
Without much ado...
To install...
- Flash the recovery from here: https://basketbuild.com/filedl/devs?dev=chrmhoffmann&dl=chrmhoffmann/fp1-kk-stock/recovery.img
- Boot into recovery and flash the rom, eg. with adb sideload. Download here: https://basketbuild.com/devs/chrmhoffmann/fp1-kk-stock
- I guess you also want to flash some KK gapps that can be found somewhere (e.g http://opengapps.org/?api=4.4&variant=nano)
- You might also lose your IMEI like me? Don't PANIC! The IMEI's are noted on your FP. Remove the battery and write down the numbers. Then once you have booted the phone, follow this simple tutorial to fix this: https://www.facebook.com/fXDAdev/posts/448292925303711
Bugs:
- IMEI loss when flashing from stock FP1. No clue why this happens. Are we somehow overriding some NVRAM?
As usual some credits:
- @Santhosh M : for some advice on the modem/baseband
- @keesj and fairphone for ___providing___ me a fairphone that replaced my own broken one (never figured out why it doesn't boot anymore)
- @CyanogenMod and koush for superuser stuff that I kanged into the MTK stock
- @CyanogenMod for the stagefright fixes
Let me know if
- it works also on older FP1 (without U).
- you have problems with your IMEI, too
- if you find other major issues
- if you think I am missing some security updates
- i had some issues getting the "phone" part of it work. Somehow it started working - not sure what it was. If you don't get the phone (call, etc.) to work, check your IMEIs first.
Click to expand...
Click to collapse
so far it works on my fp1 (without U), no Problems with my IMEI-Numbers. Thank you very very much, great!

Just flashed it and it works! Thank you so much! (although instructions how to create such a rom would be nice for me )
EDIT: some answers to your question:
I am using the FP1u.
No problems with my IMEI.
Other major issues: none noticed, and this actually fixed the transparency bug in the Play Store
Missing security patches: Stagefright CVE-2015-6602 is not fixed.
Thank you very much!

How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")

fredflegel said:
How do i flash the recovery? the typicall fastboot method does not work for me (says "flash not supported")
Click to expand...
Click to collapse
There's an old thread about it: http://forum.xda-developers.com/showthread.php?t=2615613
So in this case:
Code:
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/recovery
And because I can never remember if it's volume up or down when powering on: "Hold the Volume Up button, while at the same time press and hold the Power button. Hold these two buttons at the same time for about 10 seconds until the screen changes."
Then install from sideload, etc. and
Code:
adb sideload fp1-kk-stock-0.1.zip
Takes quite a while to update. I did NOT disable rom recovery, I don't think this one reverts the recovery, right?
aaaand
Sound and bluetooth seem to work fine, didn't test more so far.
Edit: By the way, are you going to do a Lollipop rom? That would be even more awesome than this. Meanwhile: Good job for raising the FP1 software to the minimum requirements for today.

Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?

fredflegel said:
Great Work! Thanks alot!
I will check this rom thoroughly. On little cosmetic issue that was fixed in Fairphones official rom is the issue with national roaming in german 02/E-Plus networks. I now allowed data roaming as a workaround, but this can get pretty expensive pretty soon. Any chance you can fix that in a future build?
Click to expand...
Click to collapse
You can enable "National data roaming" with GravityBox, which you can install via the Xposed installer. Helped in Austria with bob (and A1)

You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.

ccxxx said:
You forgot to mount the "external" storage:
Code:
tmpfs /storage/emulated tmpfs rw,seclabel,relatime,mode=755,uid=1023,gid=1023 0 0
Workaround for getting the correct one for now:
Code:
umount /storage/emulated
mount -t vfat /dev/block/mmcblk0p8 /storage/emulated
But there are still symlinks to /storage/emulated/legacy.
So that needs some kind of fix up.
Click to expand...
Click to collapse
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris

chrmhoffmann said:
I think that you are using the old non-repartitioned fp1?
There's no such thing as /dev/block/mmcblk0p8 anymore on the repartitioned devices.
Chris
Click to expand...
Click to collapse
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-

ccxxx said:
Uhm, yes, I guess.
TIL https://fairphone.zendesk.com/hc/en-us/articles/201327645-What-is-Fairphone-s-storage-layout-
Click to expand...
Click to collapse
You should then upgrade. It's much nicer with a single partition... And as you can see, I don't support the old storage layout any more
Chris

Upgrade to 4.4.4. available
See OP. Please test this. It's an update to android 4.4.4 and lots of additional security fixes.
Oh, and yeah, I recommend to wipe. Email (e.g. and maybe others) will crash without.
Chris

It wasn't obvious, how to do that, so I downloaded the "Storage Upgrader 1.8.7 * (~200MB)" from https://fairphone.zendesk.com/hc/en-us/articles/201189497-Fairphone-OS-multiple-versions-
It doesn't update the partitions when flashing, it does so on the first boot. It also overwrites the recovery.
After that I installed the 4.4.4 image and it boot loops: https://gist.github.com/ChristophHaag/64da8b31533d2c562c92
edit: And so does the 4.4.2 image that has worked before.
*sigh*
edit 2: Formatted a few partitions and tried again - now 4.4.4 works.

0.2 released.
It should fix Netflix (will confirm when all apps are installed after wipe) and should also squash a security problem that bluebox reported (CVE-2014-7911).
It should also make less CTS tests fails.
Still uploading... Edit: Uploaded.
Chris

Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work

btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.

jogri said:
Hallo, nach dem neuesten update funktioniert xposed-aktivierung nicht mehr. Sonst alles bestens
Sorry, in english:
After the newest update to 4.4.4 no chance to activate xposed-framework. Anyway, thanks a lot
for your hard work
Click to expand...
Click to collapse
Yes, the last security patches break xposed. https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
See e.g. here: https://plus.google.com/114407246718577124209/posts/BwiPxSu84bD
Chris

z3ntu said:
btw Google Authenticator doesn't seem to work correctly on the 4.4.2 version. Authy works though.
Click to expand...
Click to collapse
This is most likely related to this issue: https://github.com/google/google-authenticator-android/pull/4
It is most likely an MTK issue with problematic math library (or something like that).
Anyway, it works for me when I use the open source version of the google authenticator: https://github.com/google/google-authenticator-android/releases
Chris

Jeah, I used the Play Store version, but this is also mentionable in "known bugs" (and that they should use the open-source version)

Paranoid Android 6.0.3 - Geehrc (discontinued)

disclaimer :THIS IS UNOFFICIAL PORT
We are launching brand spanking fresh. All new features. New team members. New everything and we have made sure that everything that we are releasing has been polished to our best.
The main features and enhancements that you will probably end up noticing are our custom Quick Settings tile reordering functionality, floating window support, immersive mode, the new on-the-spot interface and CM Theme Engine. There's much more to come, so sit tight!
Feature highlights
Floating mode
Immersive mode
On-the-spot controls
Quick settings re-order
Paranoid OTA (Updates)
Battery styles
Advanced power dialog
Quick pull-down
Theme engine
BUGS:NFC (i hope fix it in few days)
First Boot Time may 10 minute
Download
AOSPA
Changelogs
As we're getting back into the thread game, keeping up with threads and updating them as per changelogs can be too hectic given our schedule. However, very detailed changelogs always go up on our Google+ page, follow us for constant updates!
Instructions & requirements
We highly recommend you to follow these instructions very carefully. Users usually tend to skip a few steps and eventually fall in trouble. Are you with me? Good. Let's get this train going.
Just a few things to keep in mind first -
If you're coming from another ROM / Stock, your system data (not internal storage) will have to be wiped. This includes apps, accounts, messages, call logs etc.
There's been some users complaining about different GAPPS variants messing up installs and causing a ton of issues. Upon investigating it seems OpenGapps Mini/Nano and Banks GAPPS work best.
Understand that Paranoid Android is a custom ROM and it might lead to addiction as it's relatively good. We shouldn't be accused of anything just incase your cat starts drinking wine. Things get a little woozy in the Paranoid World.
Some brain might be involved if things go wrong. Not a lot though, as much to solve what's 1+1.
Okay let's get to the main bit -
Once you have all the required files - boot into recovery and wipe the bananas out of your device. Get into the wipe menu and wipe data, system, cache and dalvik cache (basically everything except Internal Storage).
Once wiped, get into the "Install from zip" menu and select the ROM zip. (pa_bacon_6.x...). Once added to the install queue, TWRP will ask you if you want to add more zips into the queue - Click on "add more zips" and select the GAPPS package.
Swipe the bar on the bottom to flash/install zips. Once both zips are done installing - Reboot into system and set-up your device, do not do anything else.
Once you're done setting up your device - well that's when you're done. One thing though - Make sure you DO NOT INSTALL any other zip in the same queue as the ROM & GAPPS. Meaning, do not flash anything like a kernel or a root package while installing the ROM. We recommend you do that AFTER you're done setting up your device.
Important / Useful links
GAPS
SuperSu
As always, we listen to what you have to say. Help us make PA better by submitting good bug reports possibly with a log attached. Learn how to take logs HERE. Submit bug reports and we'll try to iron out issues as soon as possible - it really helps a lot.
Cheers and #StayParanoid!
Device Source :device-kernel-vendor
Special Thanks
@xboxfanj HE IS REALY PERFECT MAN. THX FOR EVERYTHING
@Kevinjoa
XDA:DevDB Information
Paranoid Android 6.0.3 - Geehrc (discontinued), ROM for the LG Optimus G
Contributors
metrixx02
Source Code: https://github.com/AOSPA
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSPA
Version Information
Status: Beta
Beta Release Date: 2016-07-31
Created 2016-07-30
Last Updated 2016-10-28

Screenshots
Screenshots

Reserved

cool, i will become an official tester of this ROM and will shall present bugs, errors and i will sending Logcats. Sorry for my bad english.✌

OK first, when you record a note voice, audio heard saturated. second: when you open often the camera and you spend to other applications can get a time when no longer opens and need to restart the phone. third: the ROM should bring a file manager by default

Ronaldj25 said:
OK first, when you record a note voice, audio heard saturated. second: when you open often the camera and you spend to other applications can get a time when no longer opens and need to restart the phone. third: the ROM should bring a file manager by default
Click to expand...
Click to collapse
i m looking some small fixes i hope looking next time ur issues could u send me log ?

Could you say is that rom have wakelock problem too ?

JacubSKY said:
Could you say is that rom have wakelock problem too ?
Click to expand...
Click to collapse
yea i know have small wakelock issues but amplify solve it

PA 6.0.1 Review
First: Thank you for your work :good:. First I tried the Kevinjoa CM 13, but it has a lot of soft reboots, so I moved here.
1) Installation: Before you beginn, you need TWRP (for e975), which you have to install via ADB (USB + PC) ask Dr. Google about that. Additional to PA you need GAPPs (I choose mini-Version) and it is useful to have chainfires SuperSU.zip (UPDATE-SuperSU-v2.76-20160630161323.zip). All 3 zips can be installed via twrp.
2) Limitations:
I use PA-Version pa_geehrc-6.0.1-20160730 since Aug 10th (2016). I don't have any reboots or something. Everything ist running smothly.
What is working:
- Wifi
- Mobile Data
- Camera
- Phone
- Bluetooth
- GPS
What is NOT working:
- NFC (there seems to be no option to activate it) I love NFC!
- IPv6 **
- Bluetooth sometimes has trouble to connect (Garmin forerunner + Pioneer headset)
- Mobile Data (HSDPA): Whatsapp + Mail is not working, while signal messenger and Chrome are working
** I had to disable IPv6 with "IPv6 Disable Tool", otherwise I encountered problems with mail, etc. I have native IPv6 for internet and the ipv6-stack seems to be the problem: "Socket timeout: failed to connect to server". Update: This is related to my mailprovider (hosteurope.de), which has a workaround.
The version seems to be battery draining, my phone was empty after less than 12 hrs. I will look to the reason.
OK guys, I will continue on this post.
Regards
Garmintroll
Update: I moved to resurrection remix, because oft Bluetooth and mobile data trouble.

garmintroll said:
First: Thank you for your work :good:. First I tried the Kevinjoa CM 13, but it has a lot of soft reboots, so I moved here.
1) Installation: Before you beginn, you need TWRP (for e975), which you have to install via ADB (USB + PC) ask Dr. Google about that. Additional to PA you need GAPPs (I choose mini-Version) and it is useful to have chainfires SuperSU.zip (UPDATE-SuperSU-v2.76-20160630161323.zip). All 3 zips can be installed via twrp.
2) Limitations:
I use PA-Version pa_geehrc-6.0.1-20160730 since Aug 10th (2016). I don't have any reboots or something. Everything ist running smothly.
What is working:
- Wifi
- Mobile Data
- Camera
- Phone
- Bluetooth
- GPS
What is NOT working:
- NFC (there seems to be no option to activate it) I love NFC!
- IPv6 **
** I had to disable IPv6 with "IPv6 Disable Tool", otherwise I encountered problems with mail, etc. I have native IPv6 for internet and the ipv6-stack seems to be the problem: "Socket timeout: failed to connect to server".
The version seems to be battery draining, my phone was empty after less than 12 hrs. I will look to the reason.
OK guys, I will continue on this post.
Regards
Garmintroll
Click to expand...
Click to collapse
Thx ur commends .i know that bugs first i will said that battery issue is wakelock problem if could u flash Xposed u will use Amplify and solve this problem but absolutely I look at this problem first chance .I know u are not alone .NFC is really problem.i did Smal compiles from NFC but can't solve .I don't know what is the problem exactly but I contact my friend I hope fix it soon .ipv6 issue is device source problem i could not anything now.when I solve NFC and wakelock issue I will interest it .but not have any idea this problem.i m interesting AICP usually.but when I have free time I look .
I don't understand what do you mean ur 1. Comment but it is help for u.
I m useng twrp geehrc version 3.0 if u want I can upload it .every time I did full wipe and flash ROM+open gaps aroma +SuperSU (any version)+xposed+viper4ndroid .and not have any problem
But if u want use adb it is not problem can u do my steps but I don't recommend windows adb I use everytime Linux terminal and adb .so u can't usr aroma installer in adb but I hope open gaps stock is solve ur problem.
I did not upload last build s .I m really sorry basketbuild is going maintances .i bought yesterday one host and domain I m planning use h5ai system and upload my works to domain adres .when I will do this share it .
this work my hobby.i m interesting free times .i did not fallow this forum everyday because i m working robotic hands Project but if u want contact me using hangouts i hope help for u quickly than forum

pa 6.0.3 is up

How to enable hardware key backlight? Is there any option in the settings to configure it?

Working great on an old Sprint LG LS970 - thanks!
Question: Sprint/Ting 4G works, Sprint/Tello data does not work. Have attempted various APN editing tricks, but no dice. Any suggestions?

NFC
metrixx02 said:
pa 6.0.3 is up
Click to expand...
Click to collapse
Any news about NFC?

tdurack said:
Working great on an old Sprint LG LS970 - thanks!
Question: Sprint/Ting 4G works, Sprint/Tello data does not work. Have attempted various APN editing tricks, but no dice. Any suggestions?
Click to expand...
Click to collapse
Tello activate your phone as a modem APN works for me:
user ID: [email protected]
APN: mi.pamsn

[NEW ROM][UB] February 9: Jaguar Leo LP 5.1.1 Official Hardened

This is the Official Jaguar rom for Leo, which is based on AOSP with some flavors from Slim and Dirtyunicorn plus a bunch of features only this rom has, such as a working camera button. . The rom was originally made for Xperia Z1 Honami in August 2015, then extended to Z1c and now to Z2/Z3/Z3c. The rom has been downloaded thousands times and enjoyed great success. I hope the trend will continue with Jaguar for Leo.
Why LP, as opposed to MM and Nougat? Several reasons. The main one is Sony's unfriendliness to development community. Camera sucks, because Sony wouldn't provide proper blobs. Also, MM brings very few features, as opposed to LP. MM is still in alpha, but is already being abandoned by developers in favor of Nougat. Nougat will never work for Z1/Z2/Z3, because Sony wants you to buy a newer device. And finally, all LP roms, except Jaguar, have been abandoned by their developers since November 2015. CM still publishes nightly LP, but they have abandoned CM 12.1 kernel, meaning, they haven't incorporated about 800 security patches from Google and Code Aurora in LP kernel. Another reason - I take changes from Android Gerrit Master Branch, Code Aurora, Google Security Bulletins and 3.10, 3.18 and 4.x kernels. Enough reasons for you?
The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5; hardened rom built with HYPERTOOL 5.4
2. All ciphers enabled in kernel instead of just a few
3. Hardened/Fortified Bionic and Libs
4. Fstack protection strong to resist buffer overflows
5. Many System apps and processes are made read-only, to reduce elevation of privilege
6. Selinux replaced with Tomoyo Security, Yam security
7. Disc encryption, keymaster to 256 bit AES instead of 128
8. Latest TWRP with working brightness and ability to decrypt Data (Coming Soon)
9. Random number generation mixed hardware/software, as recommended by Linus Torwalds
10. Options to randomize host on every boot
11. Option to have a separate password for lock screen and boot
12. Qualcomm's Time Services disabled due to leaking on early boot (set time to automatic to get it from your carrier)
13. WIFI Background Scanning disabled to prevent leaking
14. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
15. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
16. GRsecurity features, such as Sidechannel implemented
17. Some Pax Security Features
18. Option to deny USB connection: denied always; denied when locked; and allowed always
19. Hardened webview with Google and other "interesting" IPs removed
20. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
21. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
22. Camera hardware button works to focus, take pictures and start video recording
23. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
24. Option to disable continuing writing of logcat
25. Option to disable device cameras: back; front, both or none
26. Option to disable third party apps to access clipboard
27. Always latest Google Security Patches
28. Always latest Code Aurora Security Patches
29. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
30. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10 that has Down Syndrome, but Linux/Google/Code Aurora one)
31. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
32. Many more security features ported from Linux and Copperhead OS
33. Dns Crypt: a feature allowing to choose among many Dns providers (all encrypted)
34. Seccomp: secure computing enabled in kernel
Other features include: Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Open Source Supeuser included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, (it is coming for Xperia Z3c, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. Sony TimeKeep, which is ported from MM/N, now sets the correct time on reboot without the Internet or GSM signal. All you need to do is set it once and TimeKeep will save/recalculate/restore the same on each reboot
5. GAPPS: if you use them, you need to flash them right after the rom (or each update) and before reboot. Flashing after reboot will result in multiple f/c
6. Due to Volte implementation, you might be required to flash LP or MM stock baseband (only if you have no 2g/3g signal)
7. Helpful fastboot commands: for flashing TWRP: fastboot flash recovery recovery.img
for flashing kernel: fastboot flash boot boot.img
Download: All updates and change logs are in Post #3
Instructions:
1. Be on LP at least, have TWRP, unlocked bootloader and root
2. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
3. Flash the rom
4. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
5. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault.
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Source: https://github.com/AOSP-Jaguar/kernel_sony_msm8974
XDA:DevDB Information
JAGUAR LEO OFFICIAL HARDENED, ROM for the Sony Xperia Z3
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP,CM,SLIM,DU
Version Information
Status: Stable
Stable Release Date: 2016-10-18
Created 2016-10-18
Last Updated 2017-02-09

Development update and some Screenshots
I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
Screenshots are here: http://forum.xda-developers.com/showpost.php?p=62560391&postcount=2

Download Section
February 9: New release including
1. February security patches
2. Sony TimeKeep to set the correct time on boot
3. Dns_Crypt (numerous choices of encrypted Dns providers) in Settings/Security
4. Open Source Superuser integrated in Settings
5. Seccomp/secure computing implemented and enabled in kernel
6. Twrp that supports data decryption, as well as TimeKeep
To use Dns_Crypt, you must allow Internet for 'apps run as root' in Afwall
Download Rom: https://forum.xda-developers.com/devdb/project/dl/?id=23079
Download TWRP: https://forum.xda-developers.com/devdb/project/dl/?id=23078
__________________________________________________________________
January 29. XDA is having a problem with upload/download. So, here is updated TWRP 3.0.2 that is able to decrypt and mount encrypted data partition. This one is different from the originally posted, because it includes the correct time. Together with the February release (not now), it will set the correct time both in recovery and the rom:
Download: https://www.androidfilehost.com/?fid=745425885120704246 There is a new TWRP on top of this post and in the download section...
January 12: New release This should take care of a color line on Auo displays. Also included is the fully working NFC-HCE for Android Pay (to pass Safety Net, you'll have to delete Supersu and su binary). And January security patches, of course...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22563
You may flash dirty on top of another Jaguar release. Otherwise - clean install
__________________________________________________________________________________
December 31. TWRP 3.0.2 able to decrypt data. This works well for Xperia Z1 and Z1c, but, since I don't have the device, it may or may not work for Z3. So, test it and report
Unzip the file (attached to this post) and flash in fastboot like this: fastboot flash recovery recovery.img
____________________________________________________________________________________________
December 14. New build with increased brightness levels. Flash only if you have a type of display that has flickering on low brightness. If you have no flickering, no need to upgrade
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22108
______________________________________________________________________________
December 10: Rom updated to include
1. December security patches
2. Signature Spoofing (Omnirom type), switch in Developer settings
3. USSD fixed (maybe)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22020
__________________________________________________________________________________
November 10: Rom updated to include November Security Patches. I have also removed SuperSU, as there is a built-in root manager and quite a few people no longer like the Chinese owned SuperSU[/COLOR]
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21437
__________________________________________________________________________________
October 18. New release including Code Aurora and Google latest security patches. Also, there is a new feature - option to prevent apps from accessing clipboard in background.
Download Rom: http://forum.xda-developers.com/devdb/project/dl/?id=20976
Download Afwall/KernelAdiutor: http://forum.xda-developers.com/devdb/project/dl/?id=20974

Any support for d6633?

I flash the baseband but after reboot the baseband is unknown again. And the ussd code not working.

leesiangcheng said:
I flash the baseband but after reboot the baseband is unknown again. And the ussd code not working.
Click to expand...
Click to collapse
Flash the correct baseband AFTER flashing the rom. If it says unknown baseband, you won't have even a sim card recognized.
USSD is a known issue. It works, but slowly: I get a response in 2-3 minutes...

Flash baseband alreadyworking .but after reboot the base band is gone.btw the rom is super fast.hope u can fix the baseband and ussd. Thanks for the rom.

leesiangcheng said:
Flash baseband alreadyworking .but after reboot the base band is gone.btw the rom is super fast.hope u can fix the baseband and ussd. Thanks for the rom.
Click to expand...
Click to collapse
You have to flash baseband for your country variant. I am in the US and had euro baseband and it took 10 sec for the phone to find signal. Then I flashed US baseband and and now I get signal right away...

Yes I flash my country baseband. At first it shows the baseband.but after reboot the baseband turn to unknow again.

Thanks for a great aosp rom! I'll try whenever I have time.
What do you mean with "localisation takes time"? Do you mean that gps is slow?
Sent from my D6603 using Tapatalk

blackhawk_LA said:
Thanks for a great aosp rom! I'll try whenever I have time.
What do you mean with "localisation takes time"? Do you mean that gps is slow?
Sent from my D6603 using Tapatalk
Click to expand...
Click to collapse
No, everything is fast here. Localization means translation to foreign languages. If you want to change mobile network settings (2g/3g/Lte), you would have to switch to English, make changes and then return to your language. That's the only area where you need to do that...

Wow looks amazing, but the million $ question is, is fisheye still present? Since camera is pretty useless on aosp with this fisheye since day 1 on z3..
Sent from my D6603 using XDA-Developers mobile app

corpsegrinder62 said:
Wow looks amazing, but the million $ question is, is fisheye still present? Since camera is pretty useless on aosp with this fisheye since day 1 on z3..
Sent from my D6603 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't know. Z2 users say there is no fish eye, but there is one on Z3 compact...

Thanks ! Amazing work !
Any plans for a dual sim version ? (D6633/D6683)

The ROM is FAAAST. Incredible, it restored my apps with titanium twice as fast as with other ROMs .
I have a little request, and is to have the network speed indicators in the right side, at the left of the WiFi indicator.
Thanks!
Sent from my Xperia Z3 using Tapatalk

This is greatest Z3 endeavor so far focused on security and stability!
We cant blame Sony for lack of official N ROM, however, lack of working MM source, no up to date MM ROM, which on galaxy s5 is something obvious makes me wonder if Sony doesn't make z3 obsolete for purpose.
Thank you for your effort!
Are there any prolonged battery life features?
Could any of users share battery life and image quality info?
To check if there is any camera distortion its enough to shot something like computer screen and see if its rectangle or it is distorted.

Camera fisheye bug is present.
Also, I I'm experiencing some light flickering on the screen at minimum brightness. Is more noticeable on white screens.
Sent from my Xperia Z3 using Tapatalk

This is awesome! I didn't expect a proper ROM for the Z3 anymore; Paranoid Android development seems slow and I'm still on infected's last CM12.1 ROM – so this is exactly what I'm looking for: A ROM with focus on security. I'll try it out as soon as possible.

Do you guys experience overheating? I encrypted my phone and it burns now... Using the same ROM but for Z3C...
Edit:
Is it possible to decrypt my phone ? I can only see the information that my phone is encrypted, can't click on it.

king960 said:
Do you guys experience overheating? I encrypted my phone and it burns now... Using the same ROM but for Z3C...
Edit:
Is it possible to decrypt my phone ? I can only see the information that my phone is encrypted, can't click on it.
Click to expand...
Click to collapse
Your phone is 'burninig', not because of encryption, but because you changed some settings in Kernel Adiutor. If you don't know what you are doing, don't touch anything. Untick all 'apply on boot' and reboot the phone to load default values. Jaguar on Z3c doesn't get over 50 degrees at highest loads (playing graphic intensive games)...

[ROM][UNOFFICIAL][N/O][F500,LS991,H81x,US991,VS986] LineageOS 15.1/14.1

Introduction
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.
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #20 for how to upgrade your bootloader stack).
.... and for your convenience I have even created TWRP flashable files for that here
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation Instructions
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional: Flash GApps (8.1 - ARM64 for LOS 15.1, 7.1 - ARM64 for LOS 14.1) if you like
Optional (if you want root): Flash the official LOS root-addon (addonsu-15.1-arm64-signed.zip or addonsu-14.1-arm64-signed.zip) or Magisk (do not report issues if you have Magisk installed though!)
Boot (will take a bit on first boot!!!)
Enjoy
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling FIXED!
Flashlight icon on quick toggles FIXED!
SIM pin unlocking (Ril works, better to use an unlocked sim card for now) FIXED!
Magisk when encrypted - state UNKNOWN
Permissive SELinux FIXED!
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
Go through the results here: click
older ones click here:
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
PREVIOUS OP (for historical reasons)
Introduction
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.
Requirements
LG G4 H815/H811
Latest MM firmware for H811 and latest Nougat/MM firmware for H815
Latest official TWRP or the latest TWRP preview from steadfasterX's server - This prevents the error 7 from appearing
For UsU devices, follow @steadfasterX's instructions for TWRP
Installation Instructions
Download appropriate zip for your device along with any additional modules such as gapps (arm64 android 8.1 needed)
Recommended - Create a full nandroid backup to allow you to restore to your previous OS if needed
Wipe system, data, cache and dalvik cache - Be aware that this WILL remove your currently installed OS and wipe your apps and most data
Flash the lineage zip, followed immediately by gapps if applicable
Reboot into system and wait for boot
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling
Flashlight icon on quick toggles
SIM pin unlocking (Ril works, better to use an unlocked sim card for now)
Magisk when encrypted
Permissive SELinux
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
XDA:DevDB Information
LineageOS 14.1/15.1 for LG G4, ROM for the LG G4
Contributors
ThePiGuy, steadfasterX, kessaras, berkantkz and LineageOS
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: v20 (or higher for H815) bootloader and modem
Based On: Lineage OS
Version Information
Status: Stable
Current Beta Version: 20180428
Beta Release Date: 2018-04-28
Created 2018-04-26
Last Updated 2019-12-22

Reserved

Reserved

Great work!
Need more stability to have a try but following it closely!
Thanks a lot.

Good job!
I missed Lineage OS.
Is encryption working?

YOU, @ThePiGuy, built this (with help from others)? Well done man.
Good luck and Godspeed man

zeduck said:
Good job!
I missed Lineage OS.
Is encryption working?
Click to expand...
Click to collapse
Yes it is

ThePiGuy said:
Yes it is
Click to expand...
Click to collapse
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!

talk to @codeworkx.
if your commits you added are clean and crystal clear of what you did and you kept authorship, maybe you should update the official and get some logs to them to also help you.
Minor bugs of audio and maybe some props to make the camera function correctly are not hard bugs. Me i do not have the time sorry. I do not even have the time with AOSCP now that im working so much :/

Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.

hteles said:
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
Click to expand...
Click to collapse
I have no idea (give it a go if you want )
belrik said:
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
Click to expand...
Click to collapse
First things first, got to get the audio working in the first place . And also, nobody seems to have seen the error that it kicks out in the logcat, so it might take a while to get it working - I'll try porting the cm-14.1 trees to lineage-15.1 rather than porting oreo cypheros trees to see if that makes a difference

@ThePiGuy what are the known bugs for this rom?

NummerEinsNerd said:
@ThePiGuy what are the known bugs for this rom?
Click to expand...
Click to collapse
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.

ThePiGuy said:
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
Click to expand...
Click to collapse
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.

kessaras said:
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
Click to expand...
Click to collapse
I haven't tested any others yet. I'm mainly focusing on the audio at the moment

Great job bringing LOS back to life for the G4!

Thanks for your effort! I will monitor this Thread closely and hope you soon find the audio issues

Hi,
Even though I'm not quite experienced, I'd like to join the development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Edit: Full message from GitHub
These missing files which had to be under "/system/vendor/etc" folder lead to crashes on the apps which use sound. By placing them to where they have to be, crashes on music player when trying to play any music and video recording are fixed. Although there has been no sound yet, these changes are required in order to prevent crashes.
Also, there may be another way in order to fix crashes instead of doing these changes. It is to edit the paths to "/system/etc/" as the files are already placed there.
I guess the lines for "/system/etc" can be removed as well but I am not sure if there are any system part that uses this directory. It's better to let them stay under "/system/etc" as well.
Additional message:
These changes also fixed handset and earphones. The handset is working on calls and earphones work on video/music now. However, the speaker still doesn't work. Video recording works as well as the built-in microphone does.
Additional message 2:
From now on, neither audio nor screen recorder crash. Both work well.
Click to expand...
Click to collapse

berkantkz said:
Hi,
Even though I'm not quite experienced, I'd like to join development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Click to expand...
Click to collapse
Brilliant!!! Thanks Don't worry about not being experienced - this is my first proper project at getting a rom going, so I'm learning as well

New H815 build out (20180428) with fixed audio, camera and screen/audio recorder. This has given rise to the fact that BT calling is indeed broken like it is on AOSCP
H811 build coming out soon.
Massive thanks to @berkantkz, without whom I wouldn't have been able to do it
Edit: H811 build is up as well now

Lineage OS 19 (ANDROID 12) for Moto G7 Play [UNOFFICIAL]

After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )

Thank you all for this ROM, also there are LineageOS 20 builds (Android 13) on official LineageOS site, i want to ask if there is an way to fix ambient display on LineageOS 19, LineageOS 20 sadly gives me way too low RAM to use it, and SWAP memory is not working on Lineage 20
Edit: many apps do restart extremely often, but it's understandable since it's only an 2 GB RAM device running an ARM64 ROMs

@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?

kreksoverzum said:
@feder86co @chuy19312 Tell me please, does 4K video recording works on this particular ROM? Or is it possible at least?
Click to expand...
Click to collapse
Well, i didn't test that but sadly, Moto Camera doesn't even have enough permissions to save pictures to SD Card

please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"

newbierooter said:
please help..
I don't got a OS bc i was installing a ROM but it didn't work..
I was trying to install this but it says "No devices found"
Click to expand...
Click to collapse
Try to install Fastboot/ADB Driver

feder86co said:
After a month or so of testing it as a daily driver, I'll post my self built rom. It's been built just following my building guide, I didn't touch the code in any other way (and it's quite noticeable regarding the loudspeaker). It's still got a few bugs (and a few newer ones), but this is the first stable-ish rom I've managed to build since April. Tested on the US version only.
-- DISCLAIMER --
It is highly advised to backup all your phone data, as it will be PERMANENTLY LOST during the upgrade process. Keep in mind that will be needed for future updates as well, as all self built Lineage 19 roms from source needed a hard reset to work properly. This is a highly experimental build, so EVERYTHING IS AT YOUR RISK. I take to responsibility whatsoever.
Also, FOLLOW THE INSTRUCTIONS BELOW as repartitioning the device is NECESSARY for the success of the operation.
---> DOWNLOAD LINK HERE: https://androidfilehost.com/?w=files&flid=335748 <---
-- REQUIREMENTS --
- a computer with adb and fastboot installed. For further information and downloads go to https://developer.android.com/studio/releases/platform-tools
- a minimal comfort using a command line interface. For reference, a complete guide for the moto g7 play can be found here: https://wiki.lineageos.org/devices/channel/install
-- INSTRUCTIONS --
- download the regular Moto g7 partitioning file: https://androidfilehost.com/?fid=14655340768118450531 (thanks SyberHexen ). Remember this is STRICLY NECESSARY.
- connect your Moto g7 play in fastboot mode to a computer with adb and fastboot installed
- from the folder where the file has been downloaded, flash the Moto g7 partitioning file using this command:
fastboot flash boot ocean_gpt.bin
- from the moto g7 play, wipe the memory and the dalvik cache, go into recovery mode, allow sideloading and then sideload the lineage-19.1-20220721-UNOFFICIAL-channel file using the following command:
adb sideload lineage-19.1-20220721-UNOFFICIAL-channel.zip
- OPTIONAL: if you desire to install the Google apps, reboot your phone into Recovery Mode and sideload the respective package (MindTheGapps-12.1.0-arm64-20220416_174313 worked great for me)
- reboot.
-- SOURCE --
- base Lineage OS 19.1: https://github.com/LineageOS/android/tree/lineage-19.1 . This includes the standard sm6150 kernel found here: https://github.com/sm6150-motorola/android_kernel_motorola_sm6150
- SyberHexen's Motorola Channel specific settings: https://github.com/SyberHexen/android_device_motorola_channel/tree/lineage-19.1
- Proprietary blobs extracted through this guide from SyberHexen's April build (Android File Host)
-- KNOWN BUGS --
- the Lineage and the Whatsapp camera don't work well, in particular they don't always shoot photos when the button is pressed. Google Camera does work great tho.
- the backlight doesn't always turn up when calls are received (putting a finger on the fingerprint sensor with the phone ringing will turn it on)
- screen on on notifications does not work
- loudspeaker can be tinny at high volume (may be due to the loudspeaker's poor quality and to the common settings of the mixer_paths.xml file, for more info on the topic: https://forum.xda-developers.com/t/anyone-have-fix-for-low-volume-from-speaker.4054283/ )
Click to expand...
Click to collapse
when will we have new updates?

Androi100 said:
when will we have new updates?
Click to expand...
Click to collapse
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org

chuy19312 said:
Here, in the official site, there is an 2023-05-07 update
LineageOS Downloads
download.lineageos.org
Click to expand...
Click to collapse
more on the site there is only one lineage 20

Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
Well, sadly, LineageOS 19 zips were deleted, even LineageOS 18 zips some time ago, and i never understood why, there are only LineageOS 20 builds today

Androi100 said:
more on the site there is only one lineage 20
Click to expand...
Click to collapse
I just remembered, i have the last official LineageOS 19 for Moto G7 Play, i uploaded it to my Google Drive, here you have an link
lineage-19.1-20221225-nightly-channel-signed.zip
drive.google.com
The only bug it have is that ambient display doesn't work, at least, is the only one i found
Note to official developer of this ROM. if there is an problem to share this old version ROM, please tell me , but please, don't report my link in case there is an problem, i can remove the link but not the ROM since i have it because LineageOS 20 restarts almost all of the apps, multitasking on that rom doesn't exist because when switching on apps, they get restarted, even system ones
Edit: if someone have an build of LineageOS 18 or 18.1, please, give me an link for it