Database Develop

[ROM][LINK] Sailfish OS Droid 4 maserati

I DID NOT MAKE THIS ROM!!!!!! - A developer by the name of TheKit made this rom, so do not give me any credit for this rom, give it all to them.
I am simply linking it because I love this phone, I love Sailfish OS on it, and I think a lot of people would enjoy Sailfish OS on it as well and just don't know it is available.
Q: "What is Sailfish OS and why should I use it?"
A: Sailfish OS is a great OS for many reasons. Having used multiple android roms I can attest to the fact that:
1. It has MUCH better battery life (however it has a weird battery read bug, see issues below)
2. It is MUCH faster and generally more stable when it comes to the things that work (your calls won't drop, your system won't lock up due to lack of ram, etc.)
3. It has a great gesture driven UI that is a joy to use and very gorgeous to look at. No more of this all white bull**** Google has been forcing down our throats since 2014
Q: "How good is the battery life?
A: After a day of playing cave story at work and reading discord and listening to music, I am at about 30-40% end of day (I start at 8:30AM, stop at 4:00PM)
Okay now that the Q/A segment is over, lets get to the real meat
ISSUES
1. Battery Read is wonky, it only goes in 10% increments until it reaches 20%, then it starts going in 5% increments
2. If you use the 2.1.3.7 build keyboard backlight is broken, but it works fine on the 2.1.0.11 build
3. Bluetooth is wonky, I was able to play audio through speakers in the 2.1.3.7 build...
4. FM Radio is broken too
5. As the maemo-talk thread says, CDMA is untested, and like on Photon Q, most likely does not work. GSM works great though! :good:
6. The old 2.1.0.11 build has a slew of issues compared to the new 2.1.3.7 build. These include data not working out of box, wifi requiring a reboot to work, and auto rotation not working in a majority of apps by default. Consult this thread and the maemo talk thread for more help, and if you want rotation anywhere, install patchmanager 2.0 and auto rotate anywhere from warehouse for sailfish os.
Alien Dalvik install tutorial
I did not make this and do not know who did. the developer claims someone threw a brick at them with an sd card attached. The sdcard contained links to these files in the form of a text file names "monkeyAIDS.txt"
https://drive.google.com/file/d/1mS6di1jYfVeDoFBjcANS6SmfkhGyEKoa/view - AD Jolla C (different from the Turing phone rpm, this is built for 3.1.x kernels)
http://sfos.scanf.su/maserati/alien-patched.tar.gz
So extract both files to your ~/ (home) directory and type in the following:
devel-su
[insert root password you set in settings]
zypper in [alien dalvik rpm]
rsync -a /home/nemo/alien/ /opt/alien/
ln -s /vendor /opt/alien/system/vendor
reboot
OPTIONAL: fix for the default 320PPI value
devel-su
[insert root password]
vim /opt/alien/system/build.prop
change ro.sf.lcd.density to the value of your choosing (Droid 4 is 256)
Keyboard Backlight Fix, works on 2.1.0.11, don't know about 2.1.3.7 -- Thank you @moodroid for this legendary patch!
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then do 'pkcon install mce' and 'systemctl restart mce'.
Download Links
Here is the thread with the Download Link to the 2.1.0.11 build
https://talk.maemo.org/showthread.php?t=99031&page=9
If you don't mind a lack of keyboard backlight and want a more up to date build, grab the new and fabulous leaked 2.1.3.7 Build:
https://drive.google.com/file/d/1k3MOCrMvbFb114Omf0MzSvnQ7wBkTiWH/view?usp=sharing
Basically if you are fed up with how ****ty the latest Lineage OS builds are and just want to try something new, give this a try. Why not? What have you got to lose. All in all great work by TheKit and I am very happy with the port as it is and I think you will be too.

Hi,
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks

moodroid said:
Hi,
On 2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks
Click to expand...
Click to collapse
dude you are a legend!
I would add that to the OP but you are first comment so anyone viewing the op will see this. I will definitely tell TheKit about this (then again, he gave you the 2.1.3.7 build so you can just tell them yourself)

Greetings,
I've been playing around with SailfishOS on my Droid 4 in the past few days, and I have a few questions about the whole thing. TheKit publicly shared a 2.1.3.7 build for the Droid 4 on his thread at Maemo, is that the one you are talking about or is it a different build? As someone mentioned this specific build seems to have issues with wifi, and I have the same problem. I can't post links, but the download link to the build I mentioned is on page 12.
The 2.1.0.11 build seems to work fairly well, however I wasn't able to install Alien Dalvik. After the installation the "Android Support" button does show up in the settings app, however nothing happens when I click the start button. I also attempted installing an apk both via the GUI (by clicking on it in the downloads) and via the command line by using "apkd-install", but it doesn't seem to work. Full log of the installation process attached.

I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).

NIKKOS said:
I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).
Click to expand...
Click to collapse
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again

moodroid said:
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again
Click to expand...
Click to collapse
No worries.
If anyone is wondering how to change the SailfishOS UI scale (I find the default one to be way too big) here's how I did it via the terminal:
Code:
devel-su
rm /etc/dconf/db/vendor.d/locks/silica-configs.txt
dconf write /desktop/sailfish/silica/theme_pixel_ratio value
I believe the default value should be around 1.1; you can also reset the value to stock with:
Code:
dconf reset /desktop/sailfish/silica/theme_pixel_ratio
or read the value with:
Code:
dconf read /desktop/sailfish/silica/theme_pixel_ratio
Not exactly droid 4 related, but thought I'd share.

Okay, I got the backlight to turn on!
Type the following in the terminal:
Code:
devel-su
echo 255 >/sys/class/leds/keyboard-backlight/brightness
It seems to properly react to some triggers like standby after being turned on but not to others like sliding the keyboard in and out (which means it will always stay on if the screen is on, regardless if it's been slided in or out). My assumption is that the keyboard sliding trigger got broken in some way, as I believe that's the way the backlight is being turned on. The events which trigger the backlight seem to be stored in the file /sys/class/leds/keyboard-backlight/trigger, so I assume that would be a good starting point to attempt fixing this.
The keyboard backlight intensity can also be changed, just change the 255 to a different value (it goes from 0 to 255).
Note: this change is not permanent, it will need to be applied again at reboot. Writing a script which executes the above commands at boot should be trivial though, and I will include instructions when I get it done myself.
EDIT:
Here's how to make the change permanent. Following these instructions you will create a Systemd service which will turn the backlight on when active and off when inactive; it will automatically run at boot and it can also be controlled like any other Systemd service (i.e. using systemctl via the terminal)
Type the following commands through the terminal:
Code:
devel-su
cd /etc/systemd/system
touch keyboard-backlight.service
chmod 744 keyboard-backlight.service
You will now need to edit the keyboard-backlight.service file with a text editor (either vim or nano will do, vim comes preinstalled, nano does not). Depending on your preferred text editor, type the following:
Code:
vim keyboard-backlight.service
or
Code:
nano keyboard-backlight.service
Now write the following to the file and save it:
Code:
[Unit]
Description=XT894 keyboard backlight service
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo 255 >/sys/class/leds/keyboard-backlight/brightness"
ExecStop=/bin/sh -c "echo 0 >/sys/class/leds/keyboard-backlight/brightness"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Now type the following to enable the service:
Code:
systemctl enable keyboard-backlight.service
That's it. You can now control the service by using the following:
Code:
systemctl start keyboard-backlight //This will turn the backlight on
systemctl stop keyboard-backlight //This will turn the backlight off
systemctl status keyboard-backlight //This will display the service status

Can anyone share the google drive file from the first post? Is there an alternative link available? Or could you PM me a google drive link? Thanks!

Can anyone suggest the best/correct ROM-slot size for TWRP?
Is it still like for CM/LOS:
800MB for system
10MB for cache
and rest for data as one likes?

[ROM][UNOFFICIAL][10][Q]LineageOS 17.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 17.1 ROM for Z5 compact (suzuran).
Download 2022-09-11
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: 10.0 (Q)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 September 2022
Using sony blob's from stock version 32.4.A.1.54
Memory issues finally fixed!
Battery consumption significantly reduced! For further reduction, please follow these instructions.
Google Pay does not give an error when starting the app. This does not mean, that payment is working. I can't test it, because I don't use this feature at all. Please report if it's working or not.
Updated aptX encoder blobs.
P2P-Crashes fixed.
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!!!) There is a version 3.2.3 out there, but with that version I had problems to restore my backups. 3.2.1 is just working perfect for me!
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.
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:
Bluetooth
Camera; both built-in camera (Snap) and 3-rd party camera apps.
Snap 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 (see attached screenshot)
Fingerprint
FM-Radio
GApps (pick this version: ARM64, 10.0, pico [tested])
German app AusweisApp2 working (see this post)
GPS
Headset
LiveDisplay (see attached screenshots)
Location services
Notification LED
Offline charging
Phone calls (see attached screenshot)
SafetyNet test passed successfully
Signed build
SMS
Torch
WiFi
These things are NOT (or badly) working:
Camera focus at low distances.
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.
If you have problems with GApps:
Sometimes the SetupWizard of GApps crashes on and on. Then you have to boot into TWRP, mount system, and go into terminal, where you have to delete SetupWizard (see screenshots):
Code:
cd /system/system/priv-app
rm -rf SetupWizard
Reboot.
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.

Hi Bernie,
First things first : Thank you so much for your amazing work on this device.:highfive:
So hard to find a good, compact and up to date smartphone.
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
On your Los14.1 (i tried with the last one you created, a few days ago) : it would be something like 0.8go ram (so everything run smoother) still without gapps and other apps / settings.
Maybe, now our days, 3go ram is mandatory for android + gapps + 3rd party ...

Ryu--X said:
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
Click to expand...
Click to collapse
I know about that. I've tried with gapps and I can confirm that ram is running out of free space. Sometimes the system is not responding any more (screen is flickering and it seems that nothing happens) and I have to restart it (press power button quite a long time until power menu appears).
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?

Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs

Berni-0815 said:
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Click to expand...
Click to collapse
I can confirm that unfortunately GPS isn't working.
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
casouzaj said:
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
i didn't have this behavior on my tests, but i usually let the system start and wait for few minutes before using it (especially on 1st boot).
Also, i always reboot once after the 1st boot.
Hope it will help

casouzaj said:
after the language selection, my phone reboots on the 'Just a sec', endlessly.
Click to expand...
Click to collapse
Clean install?
That should not happen...

Ryu--X said:
I can confirm that unfortunately GPS isn't working.
Click to expand...
Click to collapse
You have to enable google's location service in location settings. With that, maps is working with correct location; but I don't know if the location comes from gps, wlan or network. It's raining since many days and I don't want to stand outside in the rain and wait for gps connection... :angel:
I've tried to install f-droid and their location services; no better results...
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
Click to expand...
Click to collapse
Yes, I know. The problems are always the closed-source binaries from qualcom and sony that are not properly working on LineageOS versions > 14.1
We're working on it but I'm not able to say if we can fix these issues.

BTW: Is anyone able to make an outgoing call successfully?

Berni-0815 said:
Clean install?
That should not happen...
Click to expand...
Click to collapse
Yup,, every single time!
Sent from my Xperia Z5 Compact using XDA Labs

As I said, that should not happen...

Berni-0815 said:
BTW: Is anyone able to make an outgoing call successfully?
Click to expand...
Click to collapse
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)

Ryu--X said:
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Click to expand...
Click to collapse
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?

I'm not on any aspect a Dev but I give you all my energy on continuing the developpment of this ROM.
Any other support available ?

Berni-0815 said:
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
Click to expand...
Click to collapse
Here it is !

And you can make an outgoing call sucessfully? The other end rings and you can make a call?

Berni-0815 said:
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Click to expand...
Click to collapse
Yes exactly , both ways are ok (incoming and outgoing).

Ryu--X said:
Yes exactly , both ways are ok (incoming and outgoing).
Click to expand...
Click to collapse
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...

New version out; see 1st post

Berni-0815 said:
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
Click to expand...
Click to collapse
Pretty strange, indeed.
The phone i tested with is on another provider than my z5c.
I got to say that i checked the apn before making my tests, and they were good.
I will retry with the new version tonight .
Thanks

The APN shouldn't matter for regular calls unless you're using Wifi calling or VoLTE, maybe disable both and see if it works.

[Unofficial] Lineage 18.1 for Xperia XZ [Treble]

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 build​Here 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 build​Here 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 Review​Edit: 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.

[Rom] Ubuntu touch [halium 9] with waydroid [11] support

This is an update to the Ubuntu Touch build that I shared a while back.which was based on halium 7. Now we are moving to halium 9. Even with quite a few unsolved issues ,these builds are marginal improvement over the previous ones.
This port had been no means easy, in reality, the initial builds was even more buggy compared to previous gen ,but most of them were much easier to fix, as I got lots of help from the porting community.I was able to get it to a booting state in about 3 months time as compared to more than a year with halium 7 , to be fair the delay was also due to the fact that I was not exactly an android developer or a developer for that matter, and had to read a lot at first .
anyways I share it here as I have reached a point where further bug fixing is beyond my capability . or in other words, Googling error codes and testing all possible methods /solutions don't seem to yield any meaningful full result, I do really wish someone better than me would look into it and make it even better ;- )
In the meantime let me add more Verbose ;-P
What is ubuntu touch
ubuntu touch is different from other oses as it is fork of Linux as compared to all our favorite mobile oses being forks of android. in other words, it is a fully functional Linux os optimized to run on arm64 device in a touch environment.The original idea was conceived by canonical and later they stoped their work and open-sourced the project and transferred the assets to the ubports community, the community is actively improving it, and trying to bring it to feature parity with Android .
whats working on this port
calls,data ,wifi
sound, vibration
auto rotation
auto, manual brightness
Offline charging
GPS
and other misc things
whats partially working
camera (preview and take video works clicking picture not working)
fingerprint (fingerprint wakes the device but cant enroll fingerprints)
Bluetooth (everything works except file transfer)
what does not work
adb,mtp
one of the feature improvements amongst other things is the support for waydroid
Waydroid
waydroid is a containerised approach to get an android environment running in a Linux system with the added advantage of full hardware access.so we can android apps and games natively. more details can be found here. to install way droid open terminal and paste the following
sudo -s
mount -o rw,remount / && apt update && apt install waydroid && waydroid init
It also need a fix as waydroid is intended for treble devices which can be found in this post. Thank you @erfanoabdi for enabling support for non treble devices.
Installation
- flash the halium-boot and the following zip file
- clean flash recommended
- reboot after the initial setup is done
Halium-boot .img
ubuntu_touch_installer_Kenzo_halium9_v7.zip
Please Donate
Every rupee ,euro ,doller counts. It would feel wounderful to be gifted something no matter how small.
If you like to do more, please consider buying me a coffee or may be even another Kenzo.
if you are in India please use this upi id -- > [email protected]
else do pm me.
default user password is " a "
For the History book
ubuntu_touch_installer_Kenzo_halium9_v6.zip
ubuntu_touch_installer_Kenzo_halium9_v5.zip
ubuntu_touch_installer_Kenzo_halium9_v4.zip
ubuntu_touch_installer_Kenzo_halium9_v2.zip
The sources
[https://github.com/mathew-dennis
[https://github.com/LineageOS
[https://github.com/Halium
[https://github.com/ubports
Thankyou
ubports community --> TheKit ,FlowHack, kn8rider divin, ari and everyone else
Redmi note 3 community --> thanks to all Dev's for keeping the device alive for the community .
This port would have never reached anywhere without their efforts..
And the truth is my efforts are very little as compared theirs...thank you ...
changelog
"Why not make something new from old code!" (Also because my pc can't handle A10+ builds)
v7
- updated to latest rootfs (ota-24)
V6
- updated to latest rootfs (ota-22)
- rebuild android image
- auto-brightness
V5. 1 (this is a patch for v5)
- bluetooth (everything else except file transfer )
- offline charging
- gps ( for real this time ) ( as ut dont have A-GPS support 1st fix might take 5+ min ,then it should work as normal)
v5
- gps is working now ( it's broken again)
-changed audio hal to a late start service
-enabled wireless display option (should work on miracast devices ) (not tested )
-fixes from ubports --> magnetometer and notification led is working and other fixes from ota 18 to ota 20
v4
- fixed issue with initial setup --thankyou Kn8Ryder
-audio should come up more often during boot than before
Telegram
If you are interested in bug fixing and contributing to this project , report a bug , click here to reach Telegram group

#Screenshots

what is default user password...

KrutosVIP said:
what is default user password...
Click to expand...
Click to collapse
"123" if u flashed old rom first, else "a"

mathew..denniss said:
"123" if u flashed old rom first, else "a"
Click to expand...
Click to collapse
ok, will try

Touch not working! after initial setup

mathew..denniss said:
"123" if u flashed old rom first, else "a"
Click to expand...
Click to collapse
Working for me, thanks for porting this amazing system.

BraveAmbush said:
Touch not working! after initial setup
Click to expand...
Click to collapse
For me the fix was to firstly install old ubuntu touch, load it and configure. After that,flash bootimage of new Ubuntu Touch with Halium9, then flash .zip with new Ubuntu Touch. It will give error, it is normal - go to /data/ and delete dir "ubports", then try again.
After that - just reboot, system will start with configured profile "Ubuntu"
The password is just "a"

Also, for me sound not working.

KrutosVIP said:
For me the fix was to firstly install old ubuntu touch, load it and configure. After that,flash bootimage of new Ubuntu Touch with Halium9, then flash .zip with new Ubuntu Touch. It will give error, it is normal - go to /data/ and delete dir "ubports", then try again.
After that - just reboot, system will start with configured profile "Ubuntu"
The password is just "a"
Click to expand...
Click to collapse
both flash may end with flash error that not a problem its a busybox compatibility thing.(not relevant )

KrutosVIP said:
Also, for me sound not working.
Click to expand...
Click to collapse
try a hard reboot(long press power button) .it should work afterwards

BraveAmbush said:
Touch not working! after initial setup
Click to expand...
Click to collapse

mathew..denniss said:
both flash may end with flash error that not a problem its a busybox compatibility thing.(not relevant )
Click to expand...
Click to collapse
For me deleting ubports helps to end without error-
When i don`t delete and get error, the system just don`t want to boot.
No animation, just black screen and when reboot

um that for me sound dont work too..
if not delete ubports in recovery and install, it 'll show a short black screen with a small mouse and reboot.
Also there are strange permission issues in the system dirty flashed from halium 7

Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.

jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.
Click to expand...
Click to collapse
An update on this, after two more tries of reinstalling old ubuntu touch > flashing halium-boot through fastboot > Flashing zip through TWRP. It flash without issue and booted. Initially the sound isn't working, but after several weird restarts (select poweroff but it restarted, select poweroff but it froze on boot logo, etc etc), sound is working. This is a fun project

updated the flashable zip .. thankyou for the fix @Kn8Ryder

t
jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" errotry v4
Click to expand...
Click to collapse
jeangjenq said:
Can I ask for some clarification? I managed to install the alpha version from your previous post, but how do you flash these update zips? I tried flashing them via TWRP on the device but I keep getting "recovery busybox setup failed" error.
Click to expand...
Click to collapse
try v4 ,it has some more fixess.busybox things are gone now

how many minutes does waydroid open to you ?

I did clean install
boot halium + v4 update
then install waydroid thru terminal
loading screen boot logo waydroid? is this alright?
im waiting to it

[ROM][UNOFFICIAL][BETA][13][T]LineageOS 20.0 for z5c (suzuran)

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!