Hi all:
Here is a LineageOS 18.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-12
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these command line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 11 (R)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
Camera (with the restriction to 8 MP); both built-in camera (Snap) and 3-rd party camera apps.
Camera2 may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support
Fingerprint
FM-Radio (maybe it needs a few restarts before it's working)
GApps (MindTheGApps 11 arm64)
German app AusweisApp2
GPS
Headset
Hotspot
LiveDisplay
Location services
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
SafetyNet test passed successfully
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Camera focus at low distances.
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
If you want to remove apps, that are available in much better variants (or that you don't need ), enter these lines one by one in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm -rf /system/product/app/Email
rm -rf /system/product/app/Exchange2
rm -rf /system/product/app/Jelly
rm -rf /system/product/app/Recorder
rm /system/product/priv-app/Eleven/Eleven.apk
rm /system/system_ext/priv-app/Gallery2/Gallery2.apk
"Email" is the built-in E-Mail app, I've replaced it with K-9 Mail
"Jelly" is the built-in browser, I've replaced it with Firefox
"Eleven" is the built-in music-app, I've replaced it with poweramp
"Gallery2" is the built-in picture gallery, I've replaced it with simple gallery pro
Don't forget to reboot!
Hello,
Thanks for updating the ROM!
The performance is about the same (maybe a bit faster), and everything works OK.
However hotspot is still not working for me.
litelinux said:
However hotspot is still not working for me.
Click to expand...
Click to collapse
Oh, I'm sorry, I haven't answered your post in the los18 thread.
I'll take a look at it asap.
I'm using this ROM since some hours now and I have to say, that it's working very good. Better that expected. The device is not getting warm (or hot) and the battery comsumption is very low.
I'll take a closer look at this for some days now.
If the overall performance is convincing, I will delete the "BETA" status...
Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.
esrevinu said:
Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.
Click to expand...
Click to collapse
Working for me.
{
"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"
}
(Posted on accident, please delete)
@litelinux Thank you for the answer.
I had installed NikGapps full version. It seems that some gapps made that trouble. With NikGapps core, I can use "Recent Apps" button.
But, even NikGapps core version seems to cause unexpected reboots if micro SD card is set as phone storage(adopted storage), not potable storage.
And, is it normal that the fingerprint reader works when the screen is off?
Hello,
Animations are not as smooth as in Android 10, such as:
Opening/closing recents
Notification panel
Background grayout of popup boxes
Horizontal scrolling
Not sure what the problem is...
Sorry for repeating this but I really hope it would be solved.
esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
I can't confirm that at my device.
litelinux said:
Animations are not as smooth as in Android 10
Click to expand...
Click to collapse
Maybe because it's still in development state? At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...
esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
Berni-0815 said:
At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...
Click to expand...
Click to collapse
Both are present on my device.
litelinux said:
Both are present on my device.
Click to expand...
Click to collapse
That's right. Something must have been messed up! I have to investigate it more.
Berni-0815 said:
That's right. Something must have been messed up! I have to investigate it more.
Click to expand...
Click to collapse
You need to cherrypick this commit
Keyguard: Allow disabling fingerprint wake-and-unlock · LineageOS/[email protected]
* When the fingerprint sensor is embedded in the power key, wake-and-unlock is total chaos. Add an option to disable it. * The default behavior is unchanged. Change-Id: I50c0a857daba92c17470d...
github.com
Hello,
Thanks for the ROM,
I installed this version, it works fine at the moment.
Indeed, the photo lag application but by installing open camera it's OK.
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP
esrevinu said:
You need to cherrypick this commit
Click to expand...
Click to collapse
Thanks. I've already seen that there have been made changes in that files. But unfortunately there have been made so much changes that a simple cherry-pick is not possible! I've tried to manually change these files and I'm hoping, it works.
I will report....
FRFaucigny said:
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP
Click to expand...
Click to collapse
I've blocked nothing! AFAIK the maximum resolution of the built-in sensor is 8,3MP and the resolution of 23MP is realized by software upscaling. Try to take a photo of the same object with 8,3MP and 23MP and compare them. I for myself have never seen any difference.
So, for me 8,3MP is fine..
Bummer. I was hoping root install for F-Droid would be fix by now.
You're right! I haven't tested if the so called "FDroidPrivilegedExtension" can be used in this version. I'll try it next.
Is that what you're meaning?
Related
Anyone's Google Play Services update recently? If you're suddenly experiencing dreadful battery life due to Google Play Services (see pic below) then this fix might be right for you.
Background: Recently, an update to Google Play Services (ver. 7.0.97) was released and reports flooded the internet with complaints of battery life issues. People had battery graphs similar to this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also experienced this issue. After checking my frequency tables in my kernel tweaker, I noticed that my phone was NEVER going into Deep Sleep, and, instead, was sitting at 300mhz even when the screen was off. After some Googling and reading some comments on GitHub, it seemed apparent that the problem was one Service in particular "SystemUpdateService".
The Problem: Without going into much detail SystemUpdateService is basically Google's OTA update service, and when it detects that your phone need and update while running a Custom ROM, it fails and re-runs this check over and over again. It's this wakelock that drains your battery.
The Solution: Enabling the service. You read that correctly. For whatever reason, enabling the service actually prevents the wakelock from occurring. I, along with a few testers, have been using our phones for hours now after having run the script and the wakelock and battery drain is completely gone.
Method #1: init.d Script
For those of you with custom ROMs that support init.d scripts, simply unzip and place this script in the /etc/init.d folder (as root) and set permissions to 755. The service becomes disabled again as soon as the phone reboots. We place this script in the init.d folder so the script runs automatically every time the phone boots. If your Custom ROM does NOT support init.d scripts skip over to Method #2 or 3.
DOWNLOAD SCRIPT HERE: View attachment fixUpdateService.zip
Permissions Screenshot:
The source code to this script (Edited slightly, Credit to Oreganoian on Reddit):
Code:
echo "Disabling SystemUpdateService Battery Drain"
su -c pm enable com.google.android.gms/.update.SystemUpdateActivity
su -c pm enable com.google.android.gms/.update.SystemUpdateService
su -c pm enable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdatePanoActivity
su -c pm enable com.google.android.gsf/.update.SystemUpdateService
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$Receiver
su -c pm enable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
echo "Script Execution Successful"
Method #2: Manually Running the Script
This method works best if you like working in the terminal or file explorer. Or if you would rather just do things yourself. Place the script above in the /etc/init.d directory and set permissions to 755. This time, however, you must run the script yourself EVERY TIME THE PHONE BOOTS. You can do this by using your file explorer, if it supports executing scripts (see output below) or running the script via Terminal.
Terminal: Run this command as root (type "su" and hit enter):
Code:
./etc/init.d/fixUpdateService.sh
File Explorer: I personally use FX (File Explorer), which is a wonderful app by the way, so the output in the screenshot below may be styled different but generally should appear the same:
Method #3: Enabling SystemUpdateService via App
Now, if you're a no frills kinda person, or just don't feel comfortable rummaging around in your filesystem or terminal, there is an app you can download called Disable Service which lets you do the same thing, just with a nice GUI. YOU MUST DO THIS EVERY TIME YOU REBOOT YOUR PHONE.
Steps:
Once installed, launch the app.
Then click the "System" tab on the top right.
Scroll down and select "Google Play services"
Scroll down to "SystemUpdateService" and CHECK the box.
Done!
There you have it! Hope this helps!
Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
blackzigong said:
Great!
Method 1 doesn't work on hammerheadcaf 20150318 but Method 3 is working like a charm and the battery drain issue seems to be gone!
And CyanogenMod is going to deal with this issue before long:
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
Click to expand...
Click to collapse
Interesting, I'll try to see if I can edit the script to get it to work right. Make sure you enable the service with that app every time you reboot your phone.
Also, I've been reading those CyanogenMod discussions. Very interesting. Hopefully they tackle the issue soon and the solution makes its way into other ROMs
Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
As far as I know, this bug only affects custom ROMs.
Method 1 didn't work but method 2 and 3 worked. I believe the permissions for the script
should be 755 instead of 744.
Update : changing permissions didn't help either.
755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.
soundneedle said:
755 or 744? Screenshot shows 744 but instructions say 755. Assuming 744 is correct.
Click to expand...
Click to collapse
Permissions for init.d scripts should;d be 755. I'll update the picture to reflect that. Thank you for pointing that out.
Kc_Nirvana said:
Hello...
This only occurs in custom roms or it happens also in Stock Rom?
Thank you...
Click to expand...
Click to collapse
I'm experiencing the battery drain with stock HTC sense on my M8 and GP services 7.0.97. The battery usage is very high for GP services (e.g. 38% for screen off!) and the "awake" bar shows the phone awake even during periods of low usage--too many awake intervals.
Will init.d scripts work on CM11s?
CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
http://review.cyanogenmod.org/#/c/91579/
http://review.cyanogenmod.org/#/c/91021/
AndrasLOHF said:
CM fixed this a couple days ago with 2 commits. Hopefully all the ROM teams will incorporate it into their builds.
Click to expand...
Click to collapse
CM11s may not get another update though. I can confirm that the shell script doesn't work at startup on CM11S.
Edit: sorry didnt realise this was posted in the Nexus 5 section
Does this also effect cm11s?
Pretty important to add that for that 3rd Method to work you also have to enable that same SystemUpdateService in Google Services Framework. (In addition to enabling it in Google Play Services).
At least, that's what I've read on other posts/Google+ pages. I'm trying it now so do this at your own risk =)
Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?
humba80 said:
Thanks for the script. Works for me, but only manually. I can't get it to work in the init.d at startup. It's in the folder, permissions 755. I'm not that into scripts - anyone who got it working mind for some tips?
Click to expand...
Click to collapse
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.
Sandman-007 said:
Your ROM may not support init.d. Mine doesn't and so I'm using tasker to run the script at boot.
Click to expand...
Click to collapse
Tasker! Didn't think of it. Thank you!
Script works for me, but it doesn't solve battery drain: I have to use privacy guard to remove both keep awake and wake up...
Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots
vaisakh7 said:
Why you try these hard to stop the Systemupdate Wakelock??
See my guide here.Its simple as you like.No scripts included:http://forum.xda-developers.com/showthread.php?t=3060548
This is a permanent fix.No need to redo after reboots
Click to expand...
Click to collapse
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks
gpvecchi said:
Yup, but checking after the script mod, only keep awake permission was denied and I still got more than 8000 wake locks
Click to expand...
Click to collapse
Did you try my fix?
I've attached screenshots there.
Tapped from my furious ZR
Lineage 18.1 for Xperia XZ
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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.x (Pie),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. DON'T Flash OEM from SODP.
3. You need to flash Stock Oreo and boot into it before flashing this ROM.
4. This ROM is suitable for dual and single model
5. You will meet a delay when recognize sim at the first boot.
6. VoLTE is supported, but you need to enable it on stock firmware at first.
Downloads Links
LineageOS 18.1:
Unofficial: https://sourceforge.net/projects/release-sjll/files/kagura/18.1/
Google Applications (optional):
NikGapps: https://nikgapps.com/ (ARM64->Android R->core,)
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
About the builds:
Source: https://github.com/linelessos
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
The LineageOS Team
The CyanogenMod Team
The SODP Team.
Olivier
Chippa_a
Everyone involved in working and testing
Contributors
@erikcas @Sjll
ROM OS Version: 11.0
ROM Kernel: Linux 4.4.x
Version Information
Status: Beta
FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: 2.4 Ghz Only
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Ok
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: No test
- Offline Charging: No
- USB: Ok
- USB Tethering: No test
- USB OTG: No test
- Encryption: No
- SEPolicies: Permissive
First of all , thanks @erikcas @Sjll for your time and effort.
What I did.
1. Celean install. ( f8331 .192 stock rom )
2.Before first boot.
3.Flash ...Download twrp-3.5.2_9-0-kagura.img
4. Get in TWRP and copy lineage-18.1-20210418-UNOFFICIAL-kagura.zip , NikGapps-core-arm64-11-20210130-signed.zip to phone.
5. install lineage18.1 rom zip and Nikgapps-core zip.
6.Reboot. it should take 2 min or less.
------------------------------------------------
what is not working!
1.There is no incoming and outgoing screen so you cant answer phone or end the call.
2. Screen doesnt turn on or wake up with incoming calls.
still testing..
star__dust said:
First of all , thanks @Sjll for your time and effort.
.....
what is not working!
1.There is no incoming and outgoing screen so you cant answer phone or end the call.
2. Screen doesnt turn on or wake up with incoming calls.
still testing..
Click to expand...
Click to collapse
URGENT notification! For 20210418 buildHere providea temp fix, for bluetooth, doze issue. I will fix it in next build.
1. Enable USB debug and allow debug as root in developer settings.
2. Run
Code:
adb root
adb shell mount -o remount,rw /vendor
adb pull /vendor/etc/vintf/manifest.xml
3. Open mainfest.xml with text editor, then Remove these codes in it:
Code:
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
4. Save and run
Code:
adb push manifest.xml /vendor/etc/vintf/manifest.xml
adb reboot
Sjll said:
URGENT notification! For 20210418 buildHere providea temp fix, for bluetooth, doze issue. I will fix it in next build.
1. Enable USB debug and allow debug as root in developer settings.
2. Run
Code:
adb root
adb shell mount -o remount,rw /vendor
adb pull /vendor/etc/vintf/manifest.xml
3. Open mainfest.xml with text editor, then Remove these codes in it:
Code:
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
4. Save and run
Code:
adb push manifest.xml /vendor/etc/vintf/manifest.xml
adb reboot
Click to expand...
Click to collapse
it says bluetooth version 2.0 not bluetooth version 1.0!
-------------------------------------------
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
------------------------------------------------
Anyway, I remove the this part of line but it didn't change anything.
star__dust said:
it says bluetooth version 2.0 not bluetooth version 1.0!
-------------------------------------------
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
------------------------------------------------
Anyway, I remove the this part of line but it didn't change anything.
Click to expand...
Click to collapse
Make sure you really deleted this part in manifest.xml in vendor partition. For my test result, it solved the doze issue.
Or wait for next build.
Sjll said:
Make sure you really deleted this part in manifest.xml in vendor partition. For my test result, it solved the doze issue.
Or wait for next build.
Click to expand...
Click to collapse
unfortunately, it is still same!
star__dust said:
unfortunately, it is still same!
Click to expand...
Click to collapse
Sorry, I posted wrong codes. You need to remove 2.0 and only keep 1.0.
Sjll said:
Sorry, I posted wrong codes. You need to remove 2.0 and only keep 1.0.
Click to expand...
Click to collapse
I did remove bluetooth version 2.0 codes. as I said before it didn't change anything.
I got to say that rom was really smooth and stable for a beta build.
I will wait next build. Thanks anyway.
hehe, LOS 18.1 for this device, good news
@Sjll: Is it possible the include the signature spoofing patch (to be able to use microG) in your new build ?
That would be great since there is no opportunity to patch this from 'outside' afaik ...
Thanks in advance
2faraway2 said:
hehe, LOS 18.1 for this device, good news
@Sjll: Is it possible the include the signature spoofing patch (to be able to use microG) in your new build ?
That would be great since there is no opportunity to patch this from 'outside' afaik ...
Thanks in advance
Click to expand...
Click to collapse
I will consider it.
star__dust said:
First of all , thanks @erikcas @Sjll for your time and effort.
What I did.
1. Celean install. ( f8331 .192 stock rom )
2.Before first boot.
3.Flash ...Download twrp-3.5.2_9-0-kagura.img
4. Get in TWRP and copy lineage-18.1-20210418-UNOFFICIAL-kagura.zip , NikGapps-core-arm64-11-20210130-signed.zip to phone.
5. install lineage18.1 rom zip and Nikgapps-core zip.
6.Reboot. it should take 2 min or less.
------------------------------------------------
what is not working!
1.There is no incoming and outgoing screen so you cant answer phone or end the call.
2. Screen doesnt turn on or wake up with incoming calls.
still testing..
Click to expand...
Click to collapse
star__dust said:
I did remove bluetooth version 2.0 codes. as I said before it didn't change anything.
I got to say that rom was really smooth and stable for a beta build.
I will wait next build. Thanks anyway.
Click to expand...
Click to collapse
You need to check your proximity sensor with Dev Check App.
Sjll said:
I will consider it.
You need to check your proximity sensor with Dev Check App.
Click to expand...
Click to collapse
I have checked proximity sensor with Dev Check App. My proximity sensor works fine and rest of sensors too.
The problem is when I tap on person name in contacts list , calling screen doesnt pop up but you can hear dial sound.
Except the above problem it seems everything works fine for now.
star__dust said:
I have checked proximity sensor with Dev Check App. My proximity sensor works fine and rest of sensors too.
The problem is when I tap on person name in contacts list , calling screen doesnt pop up but you can hear dial sound.
Except the above problem it seems everything works fine for now.
Click to expand...
Click to collapse
I have installed lineage-18.1-20210419-UNOFFICIAL-kagura.zip without NikGapps-core-arm64-11-20210130-signed.zip.
Now, everything seems just fine.
Thanks.
star__dust said:
Second Try..
What I did.
1. Celean install. ( f8331 .192 stock rom ) ..if you have already done it skip this part.
2.Before first boot.
3.Flash ...Download twrp-3.5.2_9-0-kagura.img
4. Get in TWRP and copy llineage-18.1-20210419-UNOFFICIAL-kagura.zip , MindTheGapps-11.0.0-arm64-20210412_124247.zip
5. install lineage18.1 rom zip (reboot).
Click to expand...
Click to collapse
6. if you want to Gapps then get in twrp and flash MindTheGapps.
7.Reboot..
Anything to care of if using the single model (F331) ?
2faraway2 said:
Anything to care of if using the single model (F331) ?
Click to expand...
Click to collapse
rom says "Sony Xperia XZ Dual!"....be caution.
This mean, rom will change your phone model number from F8331 to F8332!
just in case , during first clean installation get your twrp backup for your f8331 rom.
if you want to get back old stock rom f8331, you will need your backup to turn your phone model back from f8332 to f8331.
alright, thanks mate, that should be no prob at all
lineage-18.1-20210419-UNOFFICIAL-kagura.zip Test ReviewEdit: Some are minor
** Experiencing reboot when taking photos using Camera for a while. (especially front camera, 15 seconds or sometimes while taking 2-4 photo) EDIT: I finally get the error after using 3rd party camera it shows me this error. (Camera ID 0 at the back and ID 1 at the front) you can recreate the error using the attached 3rd party apk
{
"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"
}
** Frequently reboot when auto rotation is on while the phone is on landscape mode.** Random reboot when using fingerprint unlock. (encountered 4th time now)* After receiving notification screen won't turn on. (experience once)
* Double tap to sleep/wake don't work
** When turning on the phone from a long sleep, the touchscreen won't work or frozen, you need to press the power button for the phone to sleep then press again to turn it on for the screen to work. (I thought at first it's on the gestures that are not working but after several times of occurrence I notice that it's not responding to any touch, you have to turn off the screen and turn it on again for the touch to function)
* Sometimes you cant pick USB Preferences when connecting to a computer, but restarting the phone can fix the problem.
** Heating issue.---------------------------
USB OTG: Ok - works fine.
USB Tethering: Ok - works fine.
The data signal is better than stock. (in my experience)
---------------------------
rooting using Magisk makes me boot-loop.
still testing...
Hi @Sjll will this rom work for the Xperia XZs?
in the following conditions, the device will reboot
sometimes in camera, but the built-in gcam go is working fine for me.
the flashlight is turned on
sometimes while unlocking the device through the fingerprint sensor
IDK why but while launching the "mi home" app
and there are some issues in the following
sometimes especially after a long time of not using the device, the screen will freeze after it was turned on. it's the same whether it has the fingerprint unlock activated or not. after it was unlocked through the fingerprint and go into the home screen, it's not responding to any gestures. it happens more frequently than lineage os 16.
for some reason, it can't pair with my wireless headphone, and it says "system UI not responding". and I press "stop" and the screen goes black and it reboots.
the speaker and microphone are not functioning well during the "phone call" on the "local" hardware. I also encountered this issue when at lineage os 16. when I was in lineage os 16, my solution is connected to a wireless headphone, and it solved the problem. but since I can't connect to a wireless headphone currently, I can't figure out any solution and I can't make any phone calls. to be specific, when I am calling others, I can hear their sound, but they can't hear my sound. if I turn on the speaker mode, I will hear my own sound from my speaker with lots of noise.
and I am only a junior high student if any info I've given is wrong, I apologize.
Hi all:
Here is a LineageOS 19.0 ALPHA ROM for Z5 compact (suzuran).
Download 2022-03-12
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking.
Kernel sources
Tree sources
Features:
OS Version: 12 (S)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 February 2022
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.6.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
Working:
Audio
Bluetooth
Fingerprint
FM-Radio (maybe it needs a few restarts before it's working)
German App AusweisApp2 (needs extended length NFC data; default in LineageOS 19.0)
LiveDisplay
Location services (see screenshot)
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
SMS
Sounds
WiFi
Please tell me...
Please keep in mind: This is an early ALPHA version and in permanent development status.
These things are NOT working (or badly working):
Camera
Encryption
Payment
Streaming (mirroring)
Maybe some more things are not working.
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
The SIM card recognition works now; please stay tuned.
Currently I'm fighting with a crash loop while trying to enter SIM PIN.
Seems this is going to be a longer fight...
Berni-0815 said:
Currently I'm fighting with a crash loop while trying to enter SIM PIN.
Seems this is going to be a longer fight...
Click to expand...
Click to collapse
Hello Berni
For a short time, I tried rom with a spare device.
I also installed NikGapps.
First, it doesn't recognize the sim.
I tried rebooting several times, but it doesn't recognize it.
Also, I can't move the app icon.
The safety net was fine with Magisk.
Please do its best.
I haven't uploaded my latest changes because they are too unstable!
norabitox said:
I can't move the app icon
Click to expand...
Click to collapse
That's not a bug, that's a feature!
Long-press on an empty part of the screen and tab on "Home settings" and switch the first switch ("Lock layout") to the "on" position.
The logic behind this feature is reverse, so don't wonder.
Berni-0815 said:
That's not a bug, that's a feature!
Click to expand...
Click to collapse
Is that so
Thank you
New version out; see 1st post.
Now working:
Phone calls
SMS
WiFi
FM-Radio (maybe it needs a few restarts before it's working)
LiveDisplay
Offline charging
Notification LED
I could flash your android 12 version. recovery is changed to stock recovery, I reflashed twrp.
Welcome Screen was flickered, after 2 reboots I could create my profile on my z5 compact.
I had a lot of crashed on homescreen.
Call and sms are working.
Weird! I don't have any crashes! Could you please grab and send LOGs?
good work, does gapps work?
Thanks will try out this rom after awhile
Please don't forget: This is a very early ALPHA version! Don't expect any miracle!
And if possible, grab LOGs and search them for fatal errors (" F " <- a blank, a capital letter F and a blank) and for messages like "dlopen failed: cannot locate symbol".
I'm using "grep" for that:
Git:
grep " F " logcat > logcat.fatal
grep "dlopen failed: cannot locate symbol" logcat > logcat.symbol
...or like that...
Hi! Could you port this rom on sony Z5 premium?
I'm only building for suzuran (Z5 compact E5803, E5823)!
Please ask @Joel16 for further assistance.
He's the maintainer for Z5 premium.
Berni-0815 said:
I'm only building for suzuran (Z5 compact E5803, E5823)!
Please ask @Joel16 for further assistance.
He's the maintainer for Z5 premium.
Click to expand...
Click to collapse
Ok THX!
arpias said:
Ok THX!
Click to expand...
Click to collapse
Just an FYI until it gets into more of a 'beta' phase I won't be building android 19 for Z5P.
Joel16 said:
Just an FYI until it gets into more of a 'beta' phase I won't be building android 19 for Z5P.
Click to expand...
Click to collapse
Ok Joel, i'll wait for it, THX in advance!
New version out; see 1st post.
Android security patch level: 5 January 2022
Stability improvements: Removed IMS and VoLTE stuff due to too much weird errors.
New version out; see 1st post.
Sensors now working
{
"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"
}
Moto Z2 Play
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Moto Z2 Play.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
albus
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
The EQ Apps for Audio Mods (eg. JBL2 App) won't work, and will crash.
Audio Mods have no alarm or notification audio through them.
Camera Mods don't (and won't ever) work.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Official Lineage OS builds for albus ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Code:
Technical details on our Treble implementation:
Treble is enabled with VNDK30, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Kernel Source: https://github.com/LineageOS/android_kernel_motorola_msm8953
Information:
ROM OS Version: 11.x
Kernel: Linux 3.18.140
ROM Firmware required: ALBUS_PPS29.133
Status: STABLE
i had built this myself at home but never thought to publish it or make it official since i thought it was too much work.
so glad someone actually did publish an 18.1 rom for this phone so not everyone has to build it at home (especially since many cant).
great work as usual
What the hell, that's unexpected to say the least. I'm quite happy with AICP and don't feel like hopping but good to have choice.
I owned this phone for 4 years hoping it would get official Los. 2 months ago it got destroyed and now i see this.
Arcline said:
I owned this phone for 4 years hoping it would get official Los. 2 months ago it got destroyed and now i see this.
Click to expand...
Click to collapse
that sounds painful and i feel really bad.
how destroyed is it? is there any chance of repairing it? and how did it get destroyed...
Hello! Which MindTheGApps package should I install: the arm or arm64 one?
And which version: 11 or 12.1?
Thank you in advance for your help and work.
dezraj said:
Hello! Which MindTheGApps package should I install: the arm or arm64 one?
And which version: 11 or 12.1?
Thank you in advance for your help and work.
Click to expand...
Click to collapse
arm64, 11
Flash, bang, mind the gapps - and here comes Lineage! Really nice version, very light (but not poor), battery friendly. Moto actions, JBL mod and powerpack mod work fine, no unexpected behaviour so far (three days).
Thanks @marcost22 !
System encryption doesn't work. Phone won't boot after using the option.
Also how this ROM has built in google services? Without installing any GAPPS package there is already google play services, play store and google app installed out of the box.
Nevermind, I didn't format system between installations that's why gapps remained.
Notification LED working for anyone? It's enabled in options and I tried setting different values but doesn't seem to ever blink.
Newbie question here. I'm stuck at the step of flashing the lineage recovery img. Do I need TWRP installed first? Or does lineage-recovery replace that? It doesn't seem to be writing the recovery - or it is writing it super-quick - and I dont understand what the errors/info messages mean:
Code:
>fastboot flash recovery lineage-18.1-20220807-recovery-albus.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16462 KB) OKAY [ 0.618s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.154s]
Finished. Total time: 0.818s
I've tried booting into recovery after this, and nothing happens. When I hold volume up + power, I get into a bootloop of the yellow text warnings that I have an unlocked bootloader until I let go of either the volume or power, from which it will then boot into the regular OS.
Oh, never mind, it seems I can get to the Lineage recovery without turning off the device and instead using the volume keys from the fastboot menu to select "Recovery mode". And that appears to take me to LineageOS recovery. Not sure why I can't get there using the volume up + power.
Known issue? Capacitive buttons (back, home, recent) not working.
[Edit: This issue is resolved below - turns out the Z2 Play doesn't have those buttons!]
The built-in capacitive buttons on my Z2 Play don't respond and don't seem to be recognized. Is this a known issue? I've fiddled with button settings and gesture settings in both Trebuchet launcher and now in Nova launcher without success. I also tried installing Button Mapper (https://play.google.com/store/apps/details?id=flar2.homebutton), but it does not recognize these button presses either. I'm using visible nav menu now instead, which is fine. But thought I'd check to make sure that this is a known issue?
Everything else seems to work great!
Currently running:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228
meelten said:
Notification LED working for anyone? It's enabled in options and I tried setting different values but doesn't seem to ever blink.
Click to expand...
Click to collapse
I'm not sure where the settings are for this? I don't seem to have much in my default LOS settings controlling the LED.
There is a white LED that turned on by default for me with LOS 18.1 out of the box when the phone was plugged in, but I found it too bright and annoying, and didn't see where to change the colours or brightness. And I don't see any settings to configure the LED for specific notifications either. So I just set it to stay off when plugged in. And that's it: that's the only setting I could find for LEDs?
zyngfang said:
I'm not sure where the settings are for this? I don't seem to have much in my default LOS settings controlling the LED.
There is a white LED that turned on by default for me with LOS 18.1 out of the box when the phone was plugged in, but I found it too bright and annoying, and didn't see where to change the colours or brightness. And I don't see any settings to configure the LED for specific notifications either. So I just set it to stay off when plugged in. And that's it: that's the only setting I could find for LEDs?
Click to expand...
Click to collapse
Open settings and type notification light in search.
it's possible install lineage os 18.1 official on moto z2 play XT1710-08? With other rom there is a problem and need to skip the command but I'm never succeeded..
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Now I would try to install lineage os 18.1 (same version on my xiaomi mi5). Can i have problem during installation? Thanks!
zyngfang said:
Known issue? Capacitive buttons (back, home, recent) not working.
The built-in capacitive buttons on my Z2 Play don't respond and don't seem to be recognized. Is this a known issue? I've fiddled with button settings and gesture settings in both Trebuchet launcher and now in Nova launcher without success. I also tried installing Button Mapper (https://play.google.com/store/apps/details?id=flar2.homebutton), but it does not recognize these button presses either. I'm using visible nav menu now instead, which is fine. But thought I'd check to make sure that this is a known issue?
Everything else seems to work great!
Currently running:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228
Click to expand...
Click to collapse
I'm guessing that by capacitive buttons you are refering to the on-screen navigation? If so, when disabled can you navigate by using the fingerprint sensor?
specialdo said:
it's possible install lineage os 18.1 official on moto z2 play XT1710-08? With other rom there is a problem and need to skip the command but I'm never succeeded..
Now I would try to install lineage os 18.1 (same version on my xiaomi mi5). Can i have problem during installation? Thanks!
Click to expand...
Click to collapse
I'm guessing it's the chinese variant? If so, then as long as you have the Pie firmware and latest twrp you should be fine
marcost22 said:
I'm guessing that by capacitive buttons you are refering to the on-screen navigation? If so, when disabled can you navigate by using the fingerprint sensor?
Click to expand...
Click to collapse
I mean the touch-sensitive, haptic "buttons" that are built into the Z2 phone. They sit below the bottom edge of the actual screen, to the left and right of the "home" fingerprint button. In the original default Android system, those buttons light up with white icons when they are available and they function as back and recent apps buttons, and they vibrate when touched. In this version of LOS 18.1, there are no buttons there. There is no haptic feedback or vibration when I touch those areas using LOS 18.1, and the system doesn't seem to be aware that they exist.
The fingerprint sensor works as a regular home button when I disable the onscreen buttons. But there is no back or recent app button, which makes it impossible to navigate the UI. So I have the onscreen buttons enabled. I note again that this functions OK for me, so it is not a deal breaker. But it would be better for me if those haptic (capacitive) buttons worked, because then I could disable the onscreen buttons and increase the usable space on screen. Does that make sense?
Moto Mod Compatibility - Quick Review - August 2022
I've been testing various Moto Mods under LOS 18.1 as I have time.
Functioning:
Moto Turbo Power Pack
Initial test: Seems to work fine!
Notes: There is no special battery icon or indicator that it is working, but you can go into the Battery or Moto Mod area to verify or configure.
JBL Soundboost 2 speaker
Initial test: seems to work great!
Notes: Don't try to use the equalizer settings in the JBL audio app - instead simply use the built-in AudioFX equalizer. You may need to open up the generic Moto Mods app for the speaker to be recognized. Drains battery from mod first as intended (before draining phone battery).
Insta-Share Projector
Initial test: Seems to work fine!
Not Working:
Per "Known Bugs" camera mods won't work:
360° Camera
Initial test: Mod recognized, but app won't run.
Unable to use with other apps.
Haselbad Camera
Initial test: Mod not recognized.
Camera will not power via power button when attached.
Tested with:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228
zyngfang said:
I mean the touch-sensitive, haptic "buttons" that are built into the Z2 phone. They sit below the bottom edge of the actual screen, to the left and right of the "home" fingerprint button. In the original default Android system, those buttons light up with white icons when they are available and they function as back and recent apps buttons, and they vibrate when touched. In this version of LOS 18.1, there are no buttons there. There is no haptic feedback or vibration when I touch those areas using LOS 18.1, and the system doesn't seem to be aware that they exist.
The fingerprint sensor works as a regular home button when I disable the onscreen buttons. But there is no back or recent app button, which makes it impossible to navigate the UI. So I have the onscreen buttons enabled. I note again that this functions OK for me, so it is not a deal breaker. But it would be better for me if those haptic (capacitive) buttons worked, because then I could disable the onscreen buttons and increase the usable space on screen. Does that make sense?
Click to expand...
Click to collapse
My nor any Z2 play i know have such buttons; only the fingerprint sensor which in stock can double as the "one button" navigation system (via gestures); could you please send me a picture of how it looks like in your device?
Hi all:
Here is a LineageOS 20.0 BETA ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-26
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these commands line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 13 (T)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.7.0!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Enforced SELinux support
Fingerprint (sometimes crashes)
GApps (tested: MindTheGApps)
German App AusweisApp2
GPS
LiveDisplay
Location services
NFC
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
Sensors
Signed build
SMS
Sounds
WiFi
...please tell me...
These things are NOT (or badly) working:
Bluetooth
Camera
Encryption
FM-Radio (removed; causes crashes of bluetooth!)
Headset
Network Traffic Monitoring
Payment
Streaming (mirroring)
Torch
VoLTE
Maybe some more things are not working. Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Please keep in mind, that this is a BETA version and there are some things not or not fully working. The ROM feels a little bit sluggish too! Please don't expect miracles...
...but it WORKS!
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.
Hello! Can you made this rom for z5 premium?
No! There is a maintainer for z5p, please ask him.
Berni-0815 said:
No! There is a maintainer for z5p, please ask him.
Click to expand...
Click to collapse
Okay, thx!
Awesome, thanks for the constant support to z5c!
New version (Halloween edition!) out; see 1st post.
No crashes any more; therefore I've bumped this version to BETA state
Bluetooth crashes no longer. A connection can be established, but it disconnects again immediately after connection; dunno why!
FM-Radio removed; it caused crashes of bluetooth
GApps are working! I've tested MindTheGApps
Oh! I've forgotten: Signature spoofing is now working!
Haven`t tested your new release on my old Xperia Z5C yet, but I installed unofficial LOS 20.0 in my Xperia XZ2, by @dtrunk90, and with his ROM, bluetooth A2DP/AVRCP profiles work pretty fine. Don`t know if the kernel plays a critical part on this matter. For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it. Thanks for giving our old little beast a new life, anyway!
casouzaj said:
Haven`t tested your new release on my old Xperia Z5C yet, but I installed unofficial LOS 20.0 in my Xperia XZ2, by @dtrunk90, and with his ROM, bluetooth A2DP/AVRCP profiles work pretty fine. Don`t know if the kernel plays a critical part on this matter. For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it. Thanks for giving our old little beast a new life, anyway!
Click to expand...
Click to collapse
Not sure if this helps but check the comments in https://review.lineageos.org/c/LineageOS/android_device_sony_tama-common/+/339303
For some reason switching BtAudio to AIDL breaks a2dp offload for some devices.
I've tried to reactivate a2dp. Unsuccessfully. It's now realized as a module and that's not the same as before.
casouzaj said:
For Z5C it`s still in version 3.10, whereas for the Tama platform, it`s 4.9. Maybe you guys could chat a little about it.
Click to expand...
Click to collapse
Feel free to port the kernel to 4.9 or anything else. We won't, because this really is a pain in the ass and could end in total frustration...
New version out; see 1st post.
Android security patch level: 5 November 2022
Los20 with MindTheGApps shows unreproducible random crashes. Until now I dunno why and I'm working on it.
But I think, it's not at my side and has to do with the (so my idea) early beta build of MindTheGApps...
I've tested on my Z5c with "NikGapps-go" yedterday and it work very well (store, mail, galery, map) without any crash.
MMS working after manual configuration of the APN (SFR).
The ROM is very smooth, more faster than lineage 19. Nice job!
Berni-0815 said:
it's not at my side and has to do with the (so my idea) early beta build of MindTheGApps
Click to expand...
Click to collapse
I've seen a lot of java illegal exception error messages; so, yes, its a problem at MindTheGApps' side.
Gadoin said:
I've tested on my Z5c with "NikGapps-go"
Click to expand...
Click to collapse
What are the differences between "core" and "go"? What does "go" exactly mean?
Berni-0815 said:
What are the differences between "core" and "go"? What does "go" exactly mean?
Click to expand...
Click to collapse
"go" apps are for low-end devices.
Apps run into navigator.
Navigator? Is that a kind of browser?
Oops i'm sorry for my english, i mean browser.
"go" apps runs into default browser.
Hm, our Z5C is now rather low-end, compared to today's flagships
So the Go version might be just the right thing. Sadly, I didn't get it to work on 19, and I'm still a bit afraid to switch to 20
NikGApps (I've installed the "core" flavour!) are working flawlessly indeed. Much better than MindTheGApps!