[ROM][11.0][UNOFFICIAL] LineageOS 18.1 [togari] [STABLE] - Sony Xperia Z Ultra

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Bugs
What's working:
Boot
Bluetooth
Camera / Camcorder
RIL (DATA/Call/SMS)
FM Radio
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
NFC
LED lights
Sensors
GPS
Audio Playback
Video Playback
Touch screen
ExFAT SDCard
What's not working:
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
C6802,C6806,C6833,C6843
Downloads
Recovery : My Unofficial TWRP
Gapps : Open Gapps 11.0 ARM
Magisk (Flash under TWRP): Unofficial Flashable APK
Rom : Download
Sources
Device/Kernel/Vendor Tree: Sources
Donate
DONATE To Me
Big Thanks
LineageOS Team.
AICP Team.
all sony-msm8974 / sony-rhine contributors.

Changelogs
2021/10/13
Fixed modem firmware and RIL support for C6806 GPE variants.
2021/10/07
Updated to Android 11.0.0_r46 with October security patches.
Upstream updates and fixes.
Fixed modem firmware and RIL support for C68x3 variants.
2021/10/04
Fixed Camera Focus/Capture issues.
2021/10/03
Added missing SONY boot logo.
Updated libril sources.
Allow 3rd-party apps to access libOpenCL.
Adjusted configs for sdFAT. (SDCard kernel driver)
Misc updates.
2021/09/30
Fixed WiFi Hotspot authentication issues.
Disabled C2 codecs, which is not for legacy devices.
2021/09/28
Fixed an issue that sometimes camera service not starting correctly after booting.
Tweaked WiFi settings for better speed.
Fixed WiFi coexist with Bluetooth enabled.
Support 5Ghz wifi hotspot feature.
2021/09/26
Fixed Offline charging.
Optimized vibrator strength.
Optimized brightness level.
2021/09/25
Fixed Touchscreen.
Fixed NFC.
Fixed Audio.
Fixed C6802 RIL Firmware support.
Fixed Camera/Camcorder.
Fixed Vibrator.
Added LiveDisplay support.
Fixed Sensors.
Updated sdFAT drivers.
2021/09/15
Initial release of LineageOS 18.1 for Z Ultra.

Screenshots

Because your twrp not working, I extracted system.img from your package by brotli and sdat2img, checked if it is actually mountable, then flashed boot.img and system.img by TWRP 3.0.0 terminal.
Not sure if this method is right & necessary, but anyway…
1. At the moment of powered on, SONY logo is not apperead. Just black screen, and purple led flashes.
2. Successfully get into lineageOS boot animation. but device did not get into system for 30 minutes. I tried it again with userdata cache erase but It stucks at boot animation forever. In other word, bootloop. Yeah.
3. Offline-charging seems not working. Red led flashes once and Just black screen. Device stuck at this state even if usb cable detached. So I need to turn off forcefully.

Bikkoism said:
Because your twrp not working, I extracted system.img from your package by brotli and sdat2img, checked if it is actually mountable, then flashed boot.img and system.img by TWRP 3.0.0 terminal.
Not sure if this method is right & necessary, but anyway…
1. At the moment of powered on, SONY logo is not apperead. Just black screen, and purple led flashes.
2. Successfully get into lineageOS boot animation. but device did not get into system for 30 minutes. I tried it again with userdata cache erase but It stucks at boot animation forever. In other word, bootloop. Yeah.
3. Offline-charging seems not working. Red led flashes once and Just black screen. Device stuck at this state even if usb cable detached. So I need to turn off forcefully.
Click to expand...
Click to collapse
Okay, I will add a loggy service in the next build, then you can grab logcats for me.
EDIT: BTW, did you flash my boot_permissive.img? because i forgot to set SELinux to permissive in the first build.

tarkzim said:
Okay, I will add a loggy service in the next build, then you can grab logcats for me.
EDIT: BTW, did you flash my boot_permissive.img? because i forgot to set SELinux to permissive in the first build.
Click to expand...
Click to collapse
No, I flashed boot.img in zip file. I just flashed boot_permissive.img and behaviors are…
1 and 3 are exactly same with normal boot.img. but I could managed boot into system. System UI crashed and touchscreen not working. When usb connected, It charges, Xperia Z ultra Device appears in my PC, adb not working.
Seems It is very unstable also. It does not boot often and shows Boot animation -> Black Screen -> automatically reboot. It does not show full lineageOS logo even if when successfully booted. Boot animation -> Black Screen -> system.

Bikkoism said:
No, I flashed boot.img in zip file. I just flashed boot_permissive.img and behaviors are…
1 and 3 are exactly same with normal boot.img. but I could managed boot into system. System UI crashed and touchscreen not working. When usb connected, It charges, Xperia Z ultra Device appears in my PC, adb not working.
Seems It is very unstable also. It does not boot often and shows Boot animation -> Black Screen -> automatically reboot. It does not show full lineageOS logo even if when successfully booted. Boot animation -> Black Screen -> system.
Click to expand...
Click to collapse
Thanks for trying, looks like the init-phase of the ROM booting is working, once i have loggy service done, it could just output the logs that i need, hopefully we can figure this out soon.

Bikkoism said:
No, I flashed boot.img in zip file. I just flashed boot_permissive.img and behaviors are…
1 and 3 are exactly same with normal boot.img. but I could managed boot into system. System UI crashed and touchscreen not working. When usb connected, It charges, Xperia Z ultra Device appears in my PC, adb not working.
Seems It is very unstable also. It does not boot often and shows Boot animation -> Black Screen -> automatically reboot. It does not show full lineageOS logo even if when successfully booted. Boot animation -> Black Screen -> system.
Click to expand...
Click to collapse
Hey, I've uploaded a build which containing loggy service, it will start to record logcat to your /cache partition like this:
/cache/logcat_2021-XX-XX...txt
Click to expand...
Click to collapse
Let it boot into system and let it crash a few times, then go to recovery and grab the log files.
I also include a FIX for touchscreen, but not sure if it's working, let me know if you have tried it! thanks.
TEST BUILD: HERE

tarkzim said:
Hey, I've uploaded a build which containing loggy service, it will start to record logcat to your /cache partition like this:
Let it boot into system and let it crash a few times, then go to recovery and grab the log files.
I also include a FIX for touchscreen, but not sure if it's working, let me know if you have tried it! thanks.
TEST BUILD: HERE
Click to expand...
Click to collapse
After flash your rom, every twrp I have(include your one) not boot. I tried to use volume up button to get into recovery but It also not works. So I have no idea what recovery you are talking about.
Anyway, Your touch fix not working. I connected OTG mouse, keyboard to navigate your rom a bit.
LineageOS full logo apeared normally.
SystemUI: Does not response message once. But seems rom working normally.
WIFI: Seems working
Bluetooth: A2DP seems working. but no sound.
Sound: Seems sound itself not works. AudioFX app also not works.
Can't test ADB because There is no way to get authentication. Device get into bootloop(Full logo -> blackscreen -> soft reboot) soon so I coudn't test more.
I tried to get log by flash stock rom without cache partition. but there isn't log.

Bikkoism said:
After flash your rom, every twrp I have(include your one) not boot. I tried to use volume up button to get into recovery but It also not works. So I have no idea what recovery you are talking about.
Anyway, Your touch fix not working. I connected OTG mouse, keyboard to navigate your rom a bit.
LineageOS full logo apeared normally.
SystemUI: Does not response message once. But seems rom working normally.
WIFI: Seems working
Bluetooth: A2DP seems working. but no sound.
Sound: Seems sound itself not works. AudioFX app also not works.
Can't test ADB because There is no way to get authentication. Device get into bootloop(Full logo -> blackscreen -> soft reboot) soon so I coudn't test more.
I tried to get log by flash stock rom without cache partition. but there isn't log.
Click to expand...
Click to collapse
Okay... sad to hear that, actually when you wipe the "data" partition it also wipe the cache partition i guess.
I've ordered an old Z Ultra from used market, but not arrived yet.

DEVELOPMENT UPDATE:
I've got my Z Ultra device, and solved touch issues by running firmware update after every boot, now the major problem is Audio, Camera, and RIL, will try to fix them.

New build released
Fixed Touchscreen.
Fixed NFC.
Fixed Audio.
Fixed C6802 RIL Firmware support.
Fixed Camera/Camcorder.
Fixed Vibrator.
Added LiveDisplay support.
Fixed Sensors.
Updated sdFAT drivers.

Offline charging still not working. Device won't be turned off automatically and just stuck at blackscreen afterward. Need to do force reset. This will be really problematic when battery completely ran out.
And Magisk not works. Have no idea If It is fault of rom or bridge or magisk.
I still didn't drive the rom in deep, only a few minutes. but I coudn't found critical errors till now. Some setting sections crashed but after reboot it back to normal.

Bikkoism said:
Offline charging still not working. Device won't be turned off automatically and just stuck at blackscreen afterward. Need to do force reset. This will be really problematic when battery completely ran out.
And Magisk not works. Have no idea If It is fault of rom or bridge or magisk.
I still didn't drive the rom in deep, only a few minutes. but I coudn't found critical errors till now. Some setting sections crashed but after reboot it back to normal.
Click to expand...
Click to collapse
Oh thanks for the heads up, I forgot to include a fix for offline charging.
Will be included in the next build.
For Magisk, I also don't know what's the cause of it yet.

If possible I hope the rom could have root access for apps in near future. Using bridge or not, systemless or not, magisk, supersu, phhsu all not working and There is no way to get root access for apps currently.

Bikkoism said:
If possible I hope the rom could have root access for apps in near future. Using bridge or not, systemless or not, magisk, supersu, phhsu all not working and There is no way to get root access for apps currently.
Click to expand...
Click to collapse
Try this Magisk MOD , Found it on THIS thread and it worked on our device.
Flash it under TWRP.

New build released
Fixed Offline charging.
Optimized vibrator strength.
Optimized brightness level.

tarkzim said:
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Bugs
What's working:
Boot
Bluetooth
Camera / Camcorder
RIL (DATA/Call/SMS)
FM Radio
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
NFC
LED lights
Sensors
GPS
Audio Playback
Video Playback
Touch screen
ExFAT SDCard
What's not working:
Camera capture photos (Might be freezing, Use 3rd-party apps)
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
C6802,C6806,C6833,C6843
Downloads
Recovery : My Unofficial TWRP
Gapps : Open Gapps 11.0 ARM
Magisk (Flash under TWRP): Unofficial Flashable APK
Rom : Download
Sources
Device/Kernel/Vendor Tree: Sources
Donate
DONATE To Me
Big Thanks
LineageOS Team.
AICP Team.
all sony-msm8974 / sony-rhine contributors.
Click to expand...
Click to collapse
You're awesome man. Revived this device after a long time

msi.1362 said:
You're awesome man. Revived this device after a long time
Click to expand...
Click to collapse
Make Xperia Z Ultra great again.
After 2 days of using : Magisk root works. All sensors seems fine. Experienced weird battery drop while sleep once but can not determine if it is old device failure or rom fault, overall battery management seems fair.
Some serious problems I have experienced :
1: 5ghz wifi is ridiculously slower than 2.4ghz and not really usable.
2: Some major apps I using simply not start. I attached logcat for those. logcat.txt for com.newin.nplayer.pro, logcat2.txt for com.jetappfactory.jetaudio
Edit:
1: Problem 2 is kinda random error seems related with camera app somehow. When this problem occurs, There is no camera app in launcher and I need to reboot the device to solve problem. And after camera app disabled, Problem seems gone.
2: 2.4ghz wifi also being unreasonably slow when bluetooth in use. Not really sure if it is hardware limit. but as far as I remember, Other roms are not like this.
Edit2:
1: Forget bout first section of first Edit. Problem back. Some major apps do not start regardless camera app disabled or not and need to reboot.
logcat
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com

New build released
Fixed an issue that sometimes camera service not starting correctly after booting.
Tweaked WiFi settings for better speed.
Fixed WiFi coexist with Bluetooth enabled.
Support 5Ghz wifi hotspot feature.

Related

[ROM][SM-G313HN] Cyanogenmod 11 for Galaxy Trend 2 (Updated 14th December 2015)

Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
General:
CyanogenMod 11 for Samsung Galaxy Trend 2. (SM-G313HN) This is not 100% completed, so bugs can be expected. There are some bugs listed on this post and if you find more, report them to me. (Either to this thread or via private messages) It will help alot to fix them.
Note: Google apps are not included. Get them here. I recommend using Mini or smaller, because when installing a OTA update, the bigger packages don't fit on RAM if the internal storage is full. You can install the rest from Play store. It is also kinda pointless to have for example, Youtube and Google Maps on /system, because when they are updated, the updated versions go to /data anyway.
Screenshots:
Downloads:
* Latest build
* All builds
Installation:
* Install a custom recovery. (Get CWM here)
* Download the latest version to your SD-card.
* Boot into the recovery mode by pressing <Vol. Up> + <Home> + <Power>
* You can navigate on the recovery mode with the volume keys. <Power> opens the selection and <Back> goes to the previous menu.
* Backup your stock ROM by going to the SD card by going to "backup and restore" -> "backup to /storage/extSdCard". You need about 3-4 gigabytes of free space on the card, depending how full your internal storage is. You can go back to stock if you don't like this ROM, by going to "backup and restore" -> "restore from /storage/extSdCard".
* You need to do a factory reset before installing this. You can do this by selecting "wipe data/factory reset". The installation won't let you install the ROM without doing this.
* Select "install zip" -> "install from /storage/extSdCard" and then select the zip you downloaded.
* Optionally install the OpenGApps-package while you are in the recovery the same way. (Doesn't need a data wipe)
* When it is done installing, go back to the main menu and select "reboot system now" and that should be pretty much it. The first startup takes a while.
Updating:
CyanogenMod checks for updates weekly by default. You can update the phone manually by going to Settings -> About phone -> CyanogenMod-updates, tapping the refresh button and selecting the latest one. After it is downloaded, you can install it.
What works?
* Audio
* Bluetooth (At least file transfer between 2 devices is confirmed, no other devices tested. (For example. headsets, keyboards, etc.)
* Calls
* Camera
* Data connection
* DSP Manager
* GPS
* NFC
* Offline-charging
* OTA updates
* Text messages
* USB (Adb, MTP, PTP, UMS, Tethering, etc)
* Video playback/recording (Mostly.. Front camera video recording doesn't work and some codecs don't work.)
* WiFi
* Wired headsets (Audio, microphone, button)
Bugs:
* First startup might is laggy. The best way is to just skip everything, change the language and set up the accounts, etc. from the Settings app.
* Some videos don't play, because there are some codec issues. (For example on Facebook. YouTube seems to work fine.)
* Some have reported about higher battery drain when using WiFi compared to stock ROM.
* Reported that when calling or sending messages, the phone causes more interference to TV/radio signals than stock. (Excessive transmitting power?) Not too noticeable unless you are very close to the antenna, so it shouldn't cause too much problems. Possibly uses more battery.
* When USB debugging enabled and the phone is restarted, turning USB tethering on too quickly doesn't turn it on completely and removing the USB cable the phone causes the phone to freeze. (This happens when using Linux, the computer shows that it is trying to connect to the internet but the phone shows that USB tethering is not enabled) When this happens, it can be fixed (When the cable is not removed) by going to the settings -> developer settings and disabling ADB, then re-enabling it and finally then turning on USB tethering. Yes, Linux + ADB + turning on USB tethering within 10-20 seconds after rebooting. I know this doesn't affect many people, but happens to me frequently.
* Front camera video recording doesn't work.
Changelog:
Code:
===================================
Build 20151214
===================================
* Fix libskia. (Updated sources)
* Remove unused or otherwise useless binary blobs. List of blobs:
/system/bin/at_distributor
/system/bin/atx
/system/bin/atxd
/system/bin/usb_portd
/system/bin/usbdev_mode
/system/etc/apanic_rename.sh
/system/etc/copy_cp_imgs.sh
/system/etc/show_navi.sh
/system/etc/usb_portd.conf
/system/lib/lib_SA_GoogleFX_ver124b.so
/system/lib/libatlog.so
/system/lib/libatparser.so
/system/lib/libaudiosa.so
* Rework /system/etc/media_profiles.xml. (Doesn't seem to fix or break anything..)
* Change kernel compression from XZ to GZip. (Speeds up booting by few seconds)
* Disable CONFIG_KSWAPD_NOSWAP from kernel. (Enable better swapping)
* Remove unused services from /init.hawaii_ss_vivaltonfc3g_base.rc.
===================================
Build 20151209
===================================
* Android security patch December 1, 2015.
* Removed the a2dp_audio_hw patch, because it did not do anything.
===================================
Build 20151207
===================================
* Fixed libstagefrighthw. (Caused some app crashes, for example YouTube and Facebook)
* Enabled zRam. (This should speed up the phone nicely, when there are alot of apps running in the background.)
* Patched a2dp_audio_hw. I don't know if it changed anything.
* Cleaned the init scripts a bit.
===================================
Build 20151128
===================================
* Fixed bluetooth
* Fixed NFC
* This build now uses CyanogenMod /init instead of the stock one
* Now uses OTA updates (yay!)
===================================
Build 20151119
===================================
* Fixed the "WiFi amnesia" bug
* Fixed offline charger
===================================
Build 20151118
===================================
* Fixed the codec issues
* Built with newer sources, now shows "Android security patch level"
===================================
Build 20150829
===================================
* First release.
Source code:
* Device tree
* Kernel
Thanks to itigr for helping me alot in this project!
Thanks a lot!
Best wishes with very first custom rom for Trend 2! Keep going!
I prefer pico or nano GApp build. This one should works on CM-11.
update:
I've found that this is very stable and fast ROM, not bugged as I had experience with CM11 on Huawei.
It even works with microG (GApp replacement) very nice! I only use Play Store and YouTube app.
New Pipe (Youtube replacement) have problem only for WebM format video is blue/pink filtered, but smooth playing. For MPEG-4 format, play normal.
Samsung S6 CM11 theme and S Launcher 6 made Trend 2 looks similar to stock touchwiz environment
I found more bugs. Bluetooth isn't working and device forgets wifi password with every reboot.
New build coming soon! Changes:
- Most of the hardware codecs work now. (Tested: video recording/playback, Youtube, DSP Manager)
- When I updated the CM sources, there was "Android security patch level" in "About phone". Not sure if these will update automatically or what.
EDIT: New build is available!
EDIT2: Fixed the "WiFi amnesia". Quick patch: https://www.androidfilehost.com/?fid=24269982086999294.
EDIT3: New build uploaded. Fixed the WiFi bug and the offline charger now works.
EDIT4: Accidentally uploaded the eng-build. (Red flashes around the screen and insecure ADB) >.< Rebuilding..
EDIT5: Re-uploaded the build.
Small teaser:
{
"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"
}
Nikiz said:
Small teaser:
Click to expand...
Click to collapse
G313HN got CM12.1 now )
G313HU got CM11 )
and now G313HZ is the worst of all (
Most of all: G313HZ use Spreadtrum chip instead of Broadcom
doesntexits said:
G313HN got CM12.1 now )
G313HU got CM11 )
and now G313HZ is the worst of all (
Click to expand...
Click to collapse
Well, er, it is CM12.0 for G313HN
And Galaxy V (G313HZ) got whole thread with CM11.0 also.
adeii said:
Well, er, it is CM12.0 for G313HN
And Galaxy V (G313HZ) got whole thread with CM11.0 also.
Click to expand...
Click to collapse
But it has lots of bugs
Well, the CM12.0 is not usable yet. The base system works pretty well, but RIL/WiFi/Bluetooth are not working yet. Well, it is the first build that actually boots. Also logcat shows alot errors. It is strange, the RIL and WiFi works for about 30 seconds after the first boot, then suddently stops working.. Also, I found out why the stock /init works and CM one doesn't. ueventd tries to load < 32 characters long ueventd.{hardware}.rc and "ueventd.hawaii_ss_vivaltonfc3g.rc" is too long. It needs to be renamed (or patch the init) "ueventd.hawaii_ss_vivaltonfc3g.r" or sometimes "ueventd.hawaii_ss_vivaltonfc3g". (I have absolutely no idea why it varies..)
Nikiz said:
Well, the CM12.0 is not usable yet. The base system works pretty well, but RIL/WiFi/Bluetooth are not working yet. Well, it is the first build that actually boots. Also logcat shows alot errors. It is strange, the RIL and WiFi works for about 30 seconds after the first boot, then suddently stops working.. Also, I found out why the stock /init works and CM one doesn't. ueventd tries to load < 32 characters long ueventd.{hardware}.rc and "ueventd.hawaii_ss_vivaltonfc3g.rc" is too long. It needs to be renamed (or patch the init) "ueventd.hawaii_ss_vivaltonfc3g.r" or sometimes "ueventd.hawaii_ss_vivaltonfc3g". (I have absolutely no idea why it varies..)
Click to expand...
Click to collapse
Great job anyway.
Btw bluetooth should work if you'll use the stock libs (on cm11).
and thanks for pushing patches .
itigr said:
Great job anyway.
Btw bluetooth should work if you'll use the stock libs (on cm11).
and thanks for pushing patches .
Click to expand...
Click to collapse
Thanks. Btw, here are the DS-versions of the patches: https://github.com/ZIM555/android_device_logands/tree/master/patch Just add the external/tinyalsa to it. Btw, could you try to boot HU with HN kernel and show what "cat /proc/cpuinfo" and "cat /proc/simslot_count" shows with it? It might be possible to make one ROM for both devices. Just need to change "ro.telephony.ril" on init. I just need a way to detect which device it is regardless of what kernel/ROM it is running.
EDIT: Well, I need to figure out a way to disable NFC, preferably without deleting files.
Nikiz said:
Thanks. Btw, here are the DS-versions of the patches: https://github.com/ZIM555/android_device_logands/tree/master/patch Just add the external/tinyalsa to it.
Click to expand...
Click to collapse
Ok, i'll check it out.
Well, the Cyanogenmod Updater is not working.. The OTA server seems to be working though.
EDIT: Oh, it works. Had to add "/api" to the url.
Nikiz said:
Well, the Cyanogenmod Updater is not working.. The OTA server seems to be working though.
EDIT: Oh, it works. Had to add "/api" to the url.
Click to expand...
Click to collapse
What server do you use btw? xdarklight's one?
itigr said:
What server do you use btw? xdarklight's one?
Click to expand...
Click to collapse
I use this: https://github.com/julianxhokaxhiu/CyanogenModOTA It is simple and easy to set up. Doesn't require mysql-databases, etc. Just download it and boom, it works. Or at least should work. I had to do some small modifications to it.
itigr said:
Btw bluetooth should work if you'll use the stock libs (on cm11).
Click to expand...
Click to collapse
Got Bluetooth working on CM libs! Well, atleast file transfer works between two devices. I have no headsets to test though. Just add bt_vendor.conf to /system/etc/bluetooth-
Code:
# UART device port where Bluetooth controller is attached
UartPort = /dev/ttyS0
# Firmware patch file location
FwPatchFilePath=/system/vendor/firmware/
#Firmware Patchfile name
FwPatchFileName=BCM4343A0_001.001.034.0044.0127_ORC_Vivalto-3G_5MC.hcd
(SM-G313HU seems to use a newer patch file, just rename it)
Also made some changes regarding NFC, but I have no way to test it.
The OTA server seems to just dump all builds, regardless of what version is in use so the phone will show older builds as updates as well..
New build! Changes:
* Bluetooth is now working. (At least file stransfer)
* Small changes to NFC, might not work though. I have no way to test this.
* Uses now the Cyanogenmod /init, no longer using the stock one.
* OTA updates enabled!
Great. One more question, does your kernel compile while building CM? I can only compile it by going to kernel dir and running make here, then defining TARGET_KERNEL_PREBUILT, eitherway it ****s about "zconf.hash.c" .
UPD0: Just started compiling and sata connection died -_-, dammit.
UPD1: one guy reported couple months ago that headset (bluetooth or wired, no idea) button doesn't work
itigr said:
Great. One more question, does your kernel compile while building CM? I can only compile it by going to kernel dir and running make here, then defining TARGET_KERNEL_PREBUILT, eitherway it ****s about "zconf.hash.c" .
UPD0: Just started compiling and sata connection died -_-, dammit.
UPD1: one guy reported couple months ago that headset (bluetooth or wired, no idea) button doesn't work
Click to expand...
Click to collapse
I am compiling the kernel while building CM. It just works for me. I use ArchLinux. Try to use my kernel sources. One thing though, the build might fail, because the new glib. Use "export LANG=C" before building, or add it to "~/.bashrc". For some reason linking libwebviewchromium.so takes for me about 12-48 hours when I reinstalled Arch, normally it took about 6 hours for the whole build..
I just tested the wired headset with the "Okay Google"-thingamajig and it is working perfectly.

[ROM][9.0][i9100][FINAL] Pixel Experience (Pie & Plus Edition) [AOSP][r46][20200330]

[ROM][9.0][i9100][FINAL] Pixel Experience (Pie & Plus Edition) [AOSP][r46][20200330]
{
"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"
}
PixelExperience for i9100​
What is this?
An AOSP based ROM, with gapps included, and all Pixel stuffs (launcher, wallpapers, icons, fonts, bootanimation).
Based on Android 9.0
Code:
/*
** Your warranty is now void.
**
** We are not responsible for bricked devices, dead SD cards,
** thermonuclear war, or you getting fired because the alarm app failed. Please
** do some research if you have any concerns about features included in this ROM
** before flashing it! YOU are choosing to make these modifications, and if
** you point the finger at us for messing up your device, we will laugh at you.
**
**/
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Lights
Screenshots
Sound / vibration
Known issues
* Call recording only records microphone
* Slow start due to GAPPS. Wait 5 minutes before setting up the appliance.
* Initial wallpaper with different colors on the first start. Apply again and return to normal.
* Disable the animations in developer settings for a smoother experience.​
DON'T FLASH GAPPS, ALREADY INCLUDED​NO ETA REQUESTS!!!​
Download: AFH​
Android OS version: 9.0
Security patch level: November 2019 (Plus) ; December 2019 (Pie Edition)
Source code: https://github.com/PixelExperience
KERNEL: https://github.com/CarbonROM/android_kernel_samsung_smdk4412
ROM Developer: @linusdan
Credits - @rINanDO
You need 1.5GB of system partition for ROM to install.
Not sure how? See in this post
If you like my work, do not forget to click the button thanks. It's free!!!
XDA:DevDB Information
Pixel Experience, ROM for the Samsung Galaxy S II
Contributors
linusdan
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.0.x
Based On: AOSP
Version Information
Status: Stable. No Longer Maintained
Created 2018-11-18
Last Updated 2020-03-30
ALL OLD COMPILATIONS HAVE BEEN DELETED
READ THE SECTION D DESCRIBED FOR SUCCESSFUL INSTALLATION.
A. Bugs
Did you find a bug or problem?
Make a logcat and put it in pastebin/hastebin. I'll look when I can
You will need a computer, adb installed, usb debugging enabled on the smartphone and a usb cable.
Here's how to do it here.
1. Open Command Prompt (Windows) or Terminal (Linux/macOS).
2. Type:
Code:
adb logcat -d > logcat-dd-mm-yyyy.txt
This will save the log to logcat-dd-mm-yyyy.txt.
B. Magisk
Please do not ask me about compatibility with Magisk.
The i9100 Kernel (3.0.101) does not support namespace to work.
C. Root
PixelExperience does not contain software engines to support root access support for legacy devices such as LineageOS. No patience to adapt / develop a solution.
For now, the builds are rootless (forgot to warn).
I'll check a way to bring compatibility when you have time
D. Error 7
ROMs android 8+ require TWRP with version 3.2.3 or higher because of the security script to ensure that it will not be installed on different phones, avoiding major problems.
The Pixel Experience is no different. In order for you to have OTA updates or success in clean installation, you need to update TWRP.
Upgrade from Samsung stock ROM to latest build using ODIN 3.13.1
Also recommended for devices with Android 4.4 - 5+
Read this post.
Changelog
(Plus Edition)
OBS:
If you decide to use this edition, you must do a clean install.
01042020 - Final build
November security patch
Updated gapps
Updated sources
Added support for exFAT + NTFS (Thanks to @TALUAtXDA)
20102019
October security patch
Disabled Multicast DNS
Init: Remove fake battery state
Fix unlocking SIM PIN (by rINanDO)
Doze: Fix menu visibility settings
Performance: Disabled Kernel Samepage Merging
Resize userdata partition to leave room for the crypto footer region
13092019
Replacement build due to bootloop after use for a few minutes. Sorry for the inconvenience.
11092019
September security patch
26082019
Initial build
(Pie Edition)
30032020 - Final build
Updated gapps
Updated sources
Fixed SIM Pincode
December security patch
Added support for exFAT + NTFS (Thanks to @TALUAtXDA)
25072019
Updated gapps
Updated sources
Updates by rINanDO:
Fixed wakelock issue after using flashlight once. Resolves excessive battery drain after use.
14072019
July security patch
Updated gapps
Fixed turn on the screen via home button
Updates by rINanDO:
Set swappiness to 100
Using Preload-partition for misc
Added Bluetooth SIM Access Profile support (Not tested)
Fixed stereo microphone recording (also in videorecording)
Fix autofocus in preview
Set ro.config.small_battery to true. This will trigger device-idle in 15
minutes instead of 30 minutes
05062019
June security patch
Updated gapps
Theming and fonts improved
Network traffic indicator improved
Translations updated
Others fixes
11052019 - Replacement build
Add Lineage basic USB HAL
Performance tests and stability. Thanks @chhapil for collaborating!
10052019
Updated gapps
Updated sources
Performance enhancements
Video recording fixed by @rINanDO
Add SamsungDoze to prevent battery drain
New Pixel Experience features (https://www.xda-developers.com/pixel-experience-custom-rom-latest-updates/)
19042019
Updated gapps
Updated sources
Add live display
Add support to F2FS
Improvements in the SELinux
Fixed allow home button to wake
Add dummy keydisabler to allow navbar disabling
Bugs
Superuser causes bootloop
Video recording in camera app not working.
07042019 - First official build
Updated gapps
Updated sources
April security patch
Fixed WiFi HotSpot
SELinux enforcing mode
Fixed sound picker crash
Ported FunctionFS to our kernel (Thanks to rINanDO, ChronoMonochrome)
Bugs
Sometimes the camera stops and gives connection error. Use OpenCamera app for now.
14032019
Updated gapps
Updated sources
Increase heapsize to 360mb
Fixed crashes of Pixel Launcher
SELinux: come back to permissive mode
Snap camera replaced by Camera2 app for now.
Removed libyamaha-mc1n2-audio, was causing conflicts and excessive battery consumption
Fixes by @rINanDO:
Fixed graphical glitch at wake up
Screen tearing fixed, thanks to @ChronoMonochrome
Wakelock on flashlight (Flashlight turned off after 10 secs)
Fixed GAPPS crash at first startup. (I think it was Ashmem-tracking hack)
Moved Exynos4 framework hacks to device tree's, thanks to @ChronoMonochrome
Removed AshMem-tracking hack, thanks to @ChronoMonochrome for hacking our libsecril.so!
Move Target SDK to shims to allow textrelocation for gps, sensors and ril (removed bionic/libc-hacks)
Known issues:
Slow start due to GAPPS. Wait 10 minutes before setting up the appliance.
Initial wallpaper with different colors on the first start. Apply again and return to normal.
Crashes when trying to change the ringtone in the settings of the device. Thanks to @Exhigh for reporting!
05032019 - deleted
Updated gapps
Updated sources
Enabled libyamaha-mc1n2-audio
Enabled SELinux enforcing mode
Known issues:
Slow start due to GAPPS. Wait 10 minutes before setting up the appliance.
Sometimes there are some lags. Turn off animations, turn on power saving mode and dark mode for a better experience. Slowdown is still making me pass anger to get a good optimization
07022019
Updated gapps
Updated sources
PowerHAL added
Fixed dark mode issue
Performance and speed improvements
dalvik.vm.heapsize adjusted to 256m again
Fixed error at try download files via navegador or third-party apps
13012019
Updated gapps
Updated sources
Fixed turn on the screen via home button
Fixes by @rINanDO:
ZRAM set to 200MB
Fixed memory leak and crash in hwc
Fixed high-res display statusbar issue
Applied GO config for 512mb devices
17122018
Updated gapps
Fixes by @rINanDO:
Fixed screenshot and Colorfade animation
Updated pinnerService, which caused excessive lags and battery drain
Tryout: Change size of dalvik.vm.heapsize to 360m, as an attempt to soften the system slowdowns with gapps included
16112018
Initial build
Apps tip
Gallery: Gallery Go by Google
Music player: Vanilla Music
Internet Radio: TuneIn Radio
I had to give couple of clean flashes and a lot of reboots to make it working.
Pixel setup app kept on crashing on first boot and couldn't bypass it.
Finally managed to boot.
All working fine so far but with some stutter and slowness
I have upgraded from Pixel Experience 8.1 with a dirty flash (only cache and dalvik wiped). It was running with the first boot. All the functionality I need is working well. But it is a little bit slower than 8.1.
hedgehog99de said:
I have upgraded from Pixel Experience 8.1 with a dirty flash (only cache and dalvik wiped). It was running with the first boot. All the functionality I need is working well. But it is a little bit slower than 8.1.
Click to expand...
Click to collapse
I am aware of this and looking for solutions to optimize
Flashed this ROM the other day. The UI seems very slow and stutter-ish with this ROM.
I wanted to flash another ROM today, but i just noticed, that connecting via USB is not working anymore. When I go into the setting menu, everything is grayed out.
I tried different ports on my computer as well as different cables.
Does anyone have a solution for this?
exza137 said:
Flashed this ROM the other day. The UI seems very slow and stutter-ish with this ROM.
I wanted to flash another ROM today, but i just noticed, that connecting via USB is not working anymore. When I go into the setting menu, everything is grayed out.
I tried different ports on my computer as well as different cables.
Does anyone have a solution for this?
Click to expand...
Click to collapse
Hi
No idea why usb is not working but i would just download the rom and gapps on a micro sd card and install it from there then using twrp.
Sent from my [device_name] using XDA-Developers Legacy app
exza137 said:
Flashed this ROM the other day. The UI seems very slow and stutter-ish with this ROM.
I wanted to flash another ROM today, but i just noticed, that connecting via USB is not working anymore. When I go into the setting menu, everything is grayed out.
I tried different ports on my computer as well as different cables.
Does anyone have a solution for this?
Click to expand...
Click to collapse
Erase the system via TWRP and test without the system.
TriboDoP said:
Hi
No idea why usb is not working but i would just download the rom and gapps on a micro sd card and install it from there then using twrp.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No need to flash the gapps. It is described in the OP.
linusdan said:
No need to flash the gapps. It is described in the OP.
Click to expand...
Click to collapse
Okay! Thanks!
Sent from my [device_name] using XDA-Developers Legacy app
linusdan said:
Erase the system via TWRP and test without the system.
Click to expand...
Click to collapse
While I was trying to find a way to flash another ROM I discovered, that probably my Micro-USB-Port went bad / defective, because I would get weird behaviour when connecting it to my PC (connected - not connected - connected every 2 seconds).
So I am pretty sure this issue is hardware related. Thanks anyway for your quick response!
exza137 said:
Flashed this ROM the other day. The UI seems very slow and stutter-ish with this ROM.
I wanted to flash another ROM today, but i just noticed, that connecting via USB is not working anymore. When I go into the setting menu, everything is grayed out.
I tried different ports on my computer as well as different cables.
Does anyone have a solution for this?
Click to expand...
Click to collapse
Go to developer options and select MTP from there
Hi, can you dirty upgrade from Oreo or do you have to wipe everything and flash?
Thanks in advance.
Fajormein said:
Hi, can you dirty upgrade from Oreo or do you have to wipe everything and flash?
Thanks in advance.
Click to expand...
Click to collapse
Full wipe & flash
Can I install this ROM in GT-I9100P 16GB?
Leonardo Ledda said:
Can I install this ROM in GT-I9100P 16GB?
Click to expand...
Click to collapse
I did not adapt the tree to the model.
chhapil said:
I had to give couple of clean flashes and a lot of reboots to make it working.
Pixel setup app kept on crashing on first boot and couldn't bypass it.
Finally managed to boot.
All working fine so far but with some stutter and slowness
Click to expand...
Click to collapse
hi man please could you give more information about how to bypass that pixel setup crash? i cant make it boot, it just crashes after every reboot.
notayax said:
hi man please could you give more information about how to bypass that pixel setup crash? i cant make it boot, it just crashes after every reboot.
Click to expand...
Click to collapse
When you finish installing the ROM by TWRP, do the cache cleaning before you reboot, ignore all the initial configuration and make the menu settings.
NEW BUILD IS UP!
Download & changelogs in OP.

[ROM][9.0][OFFICIAL] dotOS 3.1 for the Galaxy A3 2016 | a3xelte | SM-A310xx

{
"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"
}
Galaxy A3 2016 | a3xelte | SM-A310xx
OFFICIAL | Android 9.0
Download​
Changelog:
Code:
[COLOR="Teal"]2019-07-07[/COLOR]
- More SELinux fixes (Stricted)
- Remove old implementation of Keydisabler and use Lineage Touch HAL instead (Stricted)
- dotOS 3.1 with many UI improvements and new features
- June 5 Security Patch
- Camera deadlocks are gone now (at least when using default Snap Camera) by fixes in the camera wrapper (danwood76)
- Updated stock vendor blobs (danwood76)
- Improve WiFi battery consumption by enabling the capability of the WiFi firmware to scan efficiently in the background in the framework-res overlays (danwood76)
- Add missing magnetometer config file in vendor/etc/yas_set.cfg (danwood76)
[COLOR="Teal"]2019-05-16[/COLOR]
- Update vendor security from 2018-07-30 to 2019-02-01
- Switching to NFC force download mode in libnfc-sec-hal.conf to improve reliability although turning on can take longer (danwood76)
- More SELinux fixes (danwood76)
- Fixed kernel issue from stock that the device was not charging sometimes (danwood76)
- May 05 2019 security patch (danwood76)
[COLOR="Teal"]2019-04-10[/COLOR]
- Fixed Tethering and Hotspot by enabling CONFIG_NETFILTER_XT_TARGET_CT in the kernel defconfig (danwood76)
- Much more kernel improvements (danwood76)
- Cleaned up ramdisk
- April 05 2019 security patch
[COLOR="Teal"]2019-03-29[/COLOR]
- More SELinux fixes (danwood76)
- Touchkeys are now also disabled when the display is turned off (danwood76)
[COLOR="Teal"]2019-03-26[/COLOR]
- Initial Release
/*
* 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.
*
*/
Click to expand...
Click to collapse
Installation instructions:
1. Make sure you have TWRP installed on your device to be able to flash the rom.
2. Download the latest build from the link above and copy it to a place where you can find it later.
3. Optionally download GApps for using the Play Store and other Google related services from here: https://opengapps.org. Choose ARM as architecture and 9.0 as the OS version. The size of the GApps package is upon to you how much apps you want to have preinstalled. Copy this zip aswell to a place where you can find it easy later. If you download it with Chrome or with the Google Drive App it should be by default in the Download folder.
4. Turn your phone off and press Volume UP + Home Button + Power button at the same time until the splash screen appears. Then your device should boot into the recovery. There you wipe following partitions: Data, System, Cache, Dalvik if this is your first install. All of your installed applications get lost by this. Your photos, videos etc. won't get deleted if you haven't ticked the box for internal storage. As the kernel also supports F2FS i would change the filesystem for the cache partition from ext4 to f2fs for a better system performance. Now go to the main TWRP menu, click on install and go to the place where you have placed your zips and first select the rom and then click on the left button if you have downloaded the optional GApps package to add another zip to the queue. Now swipe the slider at the bottom to install and reboot the phone to the system. The first boot can take a while and after booting you could experience some lags because of the GApps initialization but they should disappear after some time.
4. Now you have successfully installed the rom and you're ready to use dotOS on your device. Congratulations!
Bugs:
- VoLTE (isn't working on samsung devices and won't work anytime in the future too)
- HWC isn't enabled yet (could lead to a bit performance decrease in apps with alot of layers)
XDA:DevDB Information
dotOS 3.1 for the Galaxy A3 2016, ROM for the Samsung Galaxy A Series
Contributors
dariotr
Credits
@danwood76
@Stricted
@alexax66
Source Code:
https://gitlab.com/dariotrombello
https://gitlab.com/Exynos7580
https://github.com/DotOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
Based On: dotOS
Version Information
Status: Stable
Stable Release Date: 2019-03-22
Created 2019-03-22
Last Updated 2019-07-11
Discord
I've created a new Exynos 7580 Discord because the old one from the Lineage 15.1 project got deleted. I regularly share testing builds here. Join if you want . If you have any questions or problems with the ROM, write them also there.
https://discord.gg/TEfC5hA
Building
You can find a guide for building dotOS for the Galaxy A3 2016 here: https://github.com/dariotrombello/local_manifests
Wow! Very great!
fix hwc
to enable hwc use this commit
https://github.com/SamsungGalaxyJ5-...mmit/8017ccdab7aa8d31c5de755a98717877551046e1
Jullian_Ms said:
to enable hwc use this commit
https://github.com/SamsungGalaxyJ5-...mmit/8017ccdab7aa8d31c5de755a98717877551046e1
Click to expand...
Click to collapse
Are you sure that this is working? I think it has to do with something else
The ROM is now out official with working OTA Updater. Changelog from the last unofficial build:
- Widevine L1 is working now for a better quality when streaming movies etc. via Amazon Prime or Netflix (thanks to danwood76)
- A few more SELinux fixes
Borduni said:
The ROM is now out official with working OTA Updater. Changelog from the last unofficial build:
- Widevine L1 is working now for a better quality when streaming movies etc. via Amazon Prime or Netflix (thanks to danwood76)
- A few more SELinux fixes
Click to expand...
Click to collapse
Although we now have Windevine L1 our phone is not supported on Netflix or Amazon Prime (it is not on stock either).
There are some hacked versions of Netflix floating about but I don't think you really need HD on our tiny screen .
danwood76 said:
Although we now have Windevine L1 our phone is not supported on Netflix or Amazon Prime (it is not on stock either).
There are some hacked versions of Netflix floating about but I don't think you really need HD on our tiny screen .
Click to expand...
Click to collapse
Widevine L1 is even supporting 4K, isn't it?
Borduni said:
Widevine L1 is even supporting 4K, isn't it?
Click to expand...
Click to collapse
L1 just enables a more protected version of DRM, it is carried out in a secure area of the CPU (mobicore). So yes it supports higher resolutions but neither Netflix nor Amazon support non certified phones, you may be able to get round it by changing the build fingerprint. I've not tested it because I have no need for HD video on a 4.7" screen .
Bug, or Problem?
Man, help me. I installed the Dot OS 3.0 (Pie) version, until I was able to use it for about 5 - 8 hours, but suddenly he started to stop the interface making me unable to use the phone, first I formatted it thinking it was just a bug , but it remained, I went back to version 2.5 of DotOS (Oreo) but still still giving the same problem ...: /
Kyukazai said:
Man, help me. I installed the Dot OS 3.0 (Pie) version, until I was able to use it for about 5 - 8 hours, but suddenly he started to stop the interface making me unable to use the phone, first I formatted it thinking it was just a bug , but it remained, I went back to version 2.5 of DotOS (Oreo) but still still giving the same problem ...: /
Click to expand...
Click to collapse
What exactly is the issue?
Did you wipe /data /system and erase the cache before installing?
Can you provide a logcat of the error?
danwood76 said:
What exactly is the issue?
Did you wipe /data /system and erase the cache before installing?
Can you provide a logcat of the error?
Click to expand...
Click to collapse
The issue is the same, the UI interface always stops running and the phone stuck for 45 seconds, after I stop the UI and restart it, the phone stay normal, after aproximately 1 - 2 minutes the problem return and permance in a loop
Yes, I did have a full wipe, data, system, cache, internal storage, etc...
Where I can get the logcat?
Kyukazai said:
The issue is the same, the UI interface always stops running and the phone stuck for 45 seconds, after I stop the UI and restart it, the phone stay normal, after aproximately 1 - 2 minutes the problem return and permance in a loop
Yes, I did have a full wipe, data, system, cache, internal storage, etc...
Where I can get the logcat?
Click to expand...
Click to collapse
You can produce a logcat using this guide: https://forum.xda-developers.com/showthread.php?t=1726238
Did you install gapps?
If so try a full clean flash but without installing gapps.
danwood76 said:
You can produce a logcat using this guide: https://forum.xda-developers.com/showthread.php?t=1726238
Did you install gapps?
If so try a full clean flash but without installing gapps.
Click to expand...
Click to collapse
Ok man, I'll try a full clean flash without Gapps and I will relate for you the situation, thanks for the response
Kyukazai said:
Ok man, I'll try a full clean flash without Gapps and I will relate for you the situation, thanks for the response
Click to expand...
Click to collapse
Yeah, I tried this and works! The phone back to work perfectly. So much thanks :victory:
But, it's possible to install the xposed with this ROM?
Kyukazai said:
Yeah, I tried this and works! The phone back to work perfectly. So much thanks :victory:
But, it's possible to install the xposed with this ROM?
Click to expand...
Click to collapse
You should be able to install the latest opengapps with DotOS without issue.
I don't think there is official Xposed for Pie, and I have heard that the unofficial is very unstable.
Why do you need xposed?
danwood76 said:
You should be able to install the latest opengapps with DotOS without issue.
I don't think there is official Xposed for Pie, and I have heard that the unofficial is very unstable.
Why do you need xposed?
Click to expand...
Click to collapse
Yeah, I see the unofficial, I will stay in Oreo, but thanks for the answer
I need the xposed for the modules: LTweaks, Gravity Box, Xposed Edge.
XD
Found a little bug
When you drop down the notification panel whilst in landscape and try to close it by tapping in the blank space below the "no notifications" text or around it, the menu bugs out, showing the tiles for a split second and then closing all together.
keep going..
Hello. I have been following dot OS for a long time. I've noticed that during both the trial of both stable and android pie .. The location is wifi hidden. I enter the user name and password manually, but does not recognize it. Although it appears to be a registered wifi network, the connection happens. everything is ok when wifi is removed from the modem interface. We wish to have a small share ..
Router bug
I noticed a bug when I try to connect the router along with the mobile data, it just does not turn on.
Good Job man, and thanks so much for this great ROM . You're the best.

[Android 11/R] LineageOS 18.1 for LG G3 (Unofficial)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
LineageOS 18.1 is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Features:
RIL: LTE, Calling + recording, SMS and MMS
Wi-Fi: Connection to 2.4 and 5 GHz, Wi-Fi Display with audio
Bluetooth pairing, sharing and audio
Audio & video playback, streaming and recording
NFC
GPS and sensors
Camera
Powered on/off and wireless charging
USB file transfer/MTP and charging
USB, Bluetooth and Wi-Fi tethering (hotspot)
Google services and SafetyNet compliant (banking apps and Google Wallet work out of the box)
Storage encryption and SDCard
LineageOS Recovery with encryption support (not required, but endorsed )
Slimport HDMI
LG Quick Circle case support with FlipFlap
Known issues:
DRM/Widevine L3: Amazon Prime and Play Now (Polish TV stream) are working and streaming, but the quality is 540p.
YouTube doesn't show 1440p in video quality options.
Slimport HDMI connection creates screen flickering, but it's not visible on an external display.
Won't work:
VoLTE
Check out the changelog in the post below.
Make sure you're on the correct firmware for your variant.
1. If you're coming from another ROM or performing a clean flash:
Reboot to Recovery
Backup any important data
Format Data partition
Wipe Dalvik, Cache and System
Flash the ROM
Flash GApps (optional, can't be flashed after the first boot)
Reboot to System
2. If you're updating the ROM or performing a dirty flash:
Reboot to Recovery
Flash the ROM
Wipe Cache
Reboot to System
Download LineageOS 18.1 ROM and Recovery
Alternative download for LineageOS 18.1
TWRP for LG G3
Google apps (MindTheGapps recommended)
Rooting your phone by Linus Tech Tips
Stock ROM by @MESA
3__HacerPermisivo.zip - this switches your selinux to permissive
bootimage_adb_unsecure by @AdrianDC - debugging, disables adb auth
Mr_Bump.zip by @dadi11 - fix for Secure booting error (boot certification verify)
Join G3 development channel on Telegram to get more info about my projects.
LineageOS GitHub repo
github.com/itsHardStyl3r
device and kernel sources
​
18.1, 23.04.2023
Code:
* Kernel: Updated prima driver (Wi-Fi)
* Kernel: Updated sdFAT driver from 2.3.0 to 2.4.5
* Kernel: Fixed race condition for TCP listens (https://gitlab.com/LineageOS/issues/android/-/issues/3916#note_669493796)
* Enabled DRM Clearkey 1.3 plugin
* Reimplemented ZRAM
* Fixed geotagging in photos
* Disabled wallpaper zooming effect to increase performance of app drawer
* Fixed Wi-Fi settings not being applied, including LG G3 default hotspot name
* Fixed Wi-Fi WPA3 networks
* Fixed turning off DiscoveryService and NearbyMessagesService
* Adjusted sepolicy settings
* G3 should now appear as a phone in File Managers via USB
* d85x, f400, vs985: Declared support for Mifare NFC tags
- ls990 does not have pn547 NFC chip, so I can't confirm it works.
* Reverted "Disable wifi AP MAC randomization" to fix 5 Ghz hotspot
- It works now: https://imgur.com/a/6JgSynU.
* Enabled XZ compression
* Fixed HIDL power stats, TetherController and TelephonyManager errors
* Updated screenshots
18.1, 14.04.2021
Code:
* April 2021 Android Security Bulletin: r34
* Promotion to Official 18.1 #306996 #306997
* Sanitized sources so I could push to LineageOS (mostly vendor stuff) - not really worth mentioning
* Fixed TimeKeep implementation
* Fixed "Switched to AOSP RenderScript" from 31.03.2021 update
18.1, 31.03.2021
Code:
* March 2021 Android Security Bulletin: r32
* Fixed encryption
* DRM protected now works (e.g. Netflix)
* Switched to AOSP RenderScript
* Builds now come with smaller font footprint
18.1, 14.02.2021
Code:
* Updated source (LineageOS/lineage-18.1)
* sepolicy additions
* device tree updates (Trust VINTF)
* CameraServiceProxy error fix
* more bringup
18.1, 20.12.2020
Code:
* Initial release
https://imgur.com/a/j98w3ko
Reserved #3
Reserved #4
You are great, thank you..
The second beta release is awesome. Everything seems as it should be. Animations are very smooth. I wonder what is next.
Horrah! just downloading...
thank you for your hard work!
turquoise.ht said:
You are great, thank you..
i wanna submit my very first impression after a few hours of use. i had no problem during installation and in general everything is ok. animations were laggy at the beginning but they are smoother now after a while. i am sure things will get better soon. thank you very much again for your efforts.
-google drive crashing, google chrome cannot see the google account so cannot start sync.
-magisk 20.4 does not work but 21.1 beta works.
Click to expand...
Click to collapse
These bugs are related to the GApps, these are very shady but the basics work. I am waiting for @walter79 to respond and I'll build our own GApps.
Thanks for the feedback.
D855 32gig: came from 17.1, flaweless install, all works perfect, no lags or hassles. Nice work, will be my LOS from now on! Thank you HardStyl3r for this ROM.
and what Gapps can I install for LG g3 D855?
fefe128 said:
and what Gapps can I install for LG g3 D855?
Click to expand...
Click to collapse
you will find it in the download folder ==> first post here....
fefe128 said:
you will find it in the download folder ==> first post here....
Click to expand...
Click to collapse
yes. I have it. I apologise
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
fefe128 said:
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
Click to expand...
Click to collapse
same here: it seems root + TWRP is gone...
fefe128 said:
I installed and want to switch instead of Lineage recovery sleep on TWRP recovery. How ?
Click to expand...
Click to collapse
LZ_ said:
same here: it seems root + TWRP is gone...
Click to expand...
Click to collapse
The setup wizard is tricky this time. It automatically replaces TWRP with LineageOS Recovery unless you uncheck the option. To bring back TWRP, use flashable ZIP in my TWRP thread, flash it (either adb sideload or sdcard is fine) and skip the signature check failure.
HardStyl3r said:
The setup wizard is tricky this time. It automatically replaces TWRP with LineageOS Recovery unless you uncheck the option. To bring back TWRP, use flashable ZIP in my TWRP thread, flash it (either adb sideload or sdcard is fine) and skip the signature check failure.
Click to expand...
Click to collapse
Good news on the LS990. installed and booted up fine. Data and telephony both working. Rom seems just fine. Still have my twrp . No fc and no reboots. Can't get magisk 20.4 to flash so no root yet but as smoothly as it's running so far we're looking good. Thank's for the LS990 build.
Update !! Found Magisk 21 and installed root. Works fine now. One question about setup manager related to installing lineage recovery. Is it a onetime setup question or will it ask this on future updates and or resets ? Just wondering if it's something we need to be on guard against . Possible to disable the feature ? Fortunantly I happen to catch it and uncheck it so I'm good. Thanks
LS990 users you can install this . The old reboot problem we had with lineage 17 is gone. This runs good enough I'm going to continue with it as daily driver for now.
Max Frost said:
Good news on the LS990. installed and booted up fine. Data and telephony both working. Rom seems just fine. Still have my twrp . No fc and no reboots. Can't get magisk 20.4 to flash so no root yet but as smoothly as it's running so far we're looking good. Thank's for the LS990 build.
Update !! Found Magisk 21 and installed root. Works fine now. One question about setup manager related to installing lineage recovery. Is it a onetime setup question or will it ask this on future updates and or resets ? Just wondering if it's something we need to be on guard against . Possible to disable the feature ? Fortunantly I happen to catch it and uncheck it so I'm good. Thanks
LS990 users you can install this . The old reboot problem we had with lineage 17 is gone. This runs good enough I'm going to continue with it as daily driver for now.
Click to expand...
Click to collapse
This should only pop up when you clean /data. As far as I know, Setup Wizard only appears on first boots, which includes clean /data. If you've unchecked this, I think you are safe. Enjoy. And yeah, the latest Magisk beta works.
Fixed: took the latest Magisk-v21.1.zip, then run the TWRP-App and installed .bin file. Enable Advanced restart and all works fine again!
Why can't I find Advanced Reboot option? Someone enliten me!

[ROM][UNOFFICIAL][13] LineageOS 20 for Xperia X

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.​​LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.​​All the source code for LineageOS is available in the LineageOS GitHub organization.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​You can also view the changelog for a full list of changes & features.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try to play with some mods.​
About FDE and FBE​Full-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).​​FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.​​To make it a bit clear:​- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.​- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the same​​Moreover, to work with new encryption you need a recovery with appropriate support.​​Downloads Links
LineageOS 20:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/suzu​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3786431​
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.​​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
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
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
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
You are an amazing person..
- There was a problem
Random Reboot in previous versions
- In addition to the problem of phone data not working, knowing that my network is
Orange Jordan
After months, the reason appeared to be an error in the DNS of the device. I do not know whether the problem was resolved or not.
I will try the version today and give you the result.
Thank you again
I didn't expect to have a13 on my phone! Thank you for your works. Will try this now.
amazing, thank you very much.
already flashed on my suzu, works really fine
Hi Chippa_a, Thanks for a great ROM and supposting our old device.
Chippa_a said:
2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
Click to expand...
Click to collapse
This version of Google Cam work great with this ROM and if you don't use Gapps, you can install Google Cam Services and use it without Gapps.
Chippa_a said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.​​LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.​​All the source code for LineageOS is available in the LineageOS GitHub organization.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​You can also view the changelog for a full list of changes & features.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try to play with some mods.​
About FDE and FBE​Full-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).​​FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.​​To make it a bit clear:​- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.​- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the same​​Moreover, to work with new encryption you need a recovery with appropriate support.​​Downloads Links
LineageOS 20:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/suzu​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3786431​
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.​​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
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
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
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
Click to expand...
Click to collapse
Good evening.
After a few days of use.
There are some points of the system:
- No light when charging
- There is a repetition of the process of unlocking the phone, "that is, after entering the password, the phone will be locked again, and you will enter the password again."
- The problem of phone data does not work, and this problem is from version 16 until now, without a solution.
Battery consumption is higher than the previous version
- There is a problem with the sound, "it suddenly disappears" and the sound cannot be returned until after restarting the phone.!
...
These are the most important points.
tareqabamawi said:
Good evening.
After a few days of use.
There are some points of the system:
- No light when charging
- There is a repetition of the process of unlocking the phone, "that is, after entering the password, the phone will be locked again, and you will enter the password again."
- The problem of phone data does not work, and this problem is from version 16 until now, without a solution.
Battery consumption is higher than the previous version
- There is a problem with the sound, "it suddenly disappears" and the sound cannot be returned until after restarting the phone.!
...
These are the most important points.
Click to expand...
Click to collapse
Been testing this for few days now. (With Gapps)
- I have no problem with light when charging.
- I can confirm there's a repetition when unlocking, but this only happen to me once.
- mobile data works for me.
- I can confirm sound suddenly disappear and restart fix it, this happened just once.
I also wanted to add.
- GPS works.
- USB OTG works.
So far I'm very satisfied with this. Feels smoother than a12 , also camera quality seems improved. Thank you for bringing this great works.
I had a problem with this rom
the phone does not charge , it makes the charging light turn on and the charging icon for 2 seconds then the light flashes once then it wont charge anymore
i install the rom without twrp, i used lineage 20 recovery
Nice Rom for the Sony X so far.
The recorded Voice in Whatsapp is to low/quiet.
In Ventor/ect is the mixer_paths_tasha.xml
Which parameter do you have to change for a louder recording?
Thank you in advance for the help.
After 7 days as a daily companion, here is a summary of this ROM (lineage-20.0-20230308-UNOFFICIAL-suzu)
(Clean Install with TWRP 3.7.0_12-0-20230309-suzu and MindTheGapps-13.0.0-arm64-20221025_100653)
Pro:
-Google Cam (DMGC_7.3.020_ver.4.5) works perfect with HDR
-ROM runs smooth without lags or random reboots
-Better overview thanks to the higher resolution on the Display (everything is a little smaller as Android 11)
-WiFi stability (WPA2 5ghz) is better than Android 11 (last Official Build)
-GPS, Bluetooth, Simcard recognition/Phone Data (O2 Germany 4G), OTG, Fingerprint, Audio Speaker, Lights....everything works perfectly
Cons:
-Microphone in Apps like Whatsapp or Recorder is much too quiet (unusable) but when making normal calls everything is ok
-Power consumption too high, cell phone gets very warm and charges longer
-Screen retention effect (Fake burn in from the last Screen)
I like this ROM and I hope that these few bugs can still be fixed.
That's how long I'll be back on Android 11 for now.
XxAttackerxX said:
After 7 days as a daily companion, here is a summary of this ROM (lineage-20.0-20230308-UNOFFICIAL-suzu)
(Clean Install with TWRP 3.7.0_12-0-20230309-suzu and MindTheGapps-13.0.0-arm64-20221025_100653)
Pro:
-Google Cam (DMGC_7.3.020_ver.4.5) works perfect with HDR
-ROM runs smooth without lags or random reboots
-Better overview thanks to the higher resolution on the Display (everything is a little smaller as Android 11)
-WiFi stability (WPA2 5ghz) is better than Android 11 (last Official Build)
-GPS, Bluetooth, Simcard recognition/Phone Data (O2 Germany 4G), OTG, Fingerprint, Audio Speaker, Lights....everything works perfectly
Cons:
-Microphone in Apps like Whatsapp or Recorder is much too quiet (unusable) but when making normal calls everything is ok
-Power consumption too high, cell phone gets very warm and charges longer
-Screen retention effect (Fake burn in from the last Screen)
I like this ROM and I hope that these few bugs can still be fixed.
That's how long I'll be back on Android 11 for now.
Click to expand...
Click to collapse
How many time can phone in idle ?
FYA_EXel said:
How many time can phone in idle ?
Click to expand...
Click to collapse
Over Night with Android 11 you have 4-5 Percent and with Android 13 from here you have 8-10 Percent Drop in Standby. (Wlan, Bluethooth, GPS is deactivated)
Is kernel 4.9 more stable than 4.14? Which is the latest I see on sony sw binaries https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-loire/
What is fixed or new in Version lineage-20.0-20230416-UNOFFICIAL-suzu ?
Changelog please. Thanks
Hi ! Thanks for this work.
I wonder if Lineage Os 20 ( Android 13 ) will run well on a 3GB RAM device.
It's actually my wifi device only for banking ap. On Lineage Os 18 and Gapps.
( I've seen a difference between android 11 nd 12 on my XA2 with iOdé Os - and also 3GB of RAM only )
Best regards.
@Chippa_a changelog for latest build please...
Thanks a lot for this ROM and the latest Update (22nd of May)!
I didn´t managed to install the ROM on my single-sim suzu using TWRP (tried 3.7.0._9-0 and _12-1). With LOS 18 recovery I succeded in the first try. Didn´t understood by now what is the problem.
Didnt found a bug in 3 days of use without Gapps. Fingerprint-sensor is working better than ever. Accu-drain is less than with LOS 18. LOS-Stock camera is fully sufficient for my needs.
Best regars.
Does the built-in updater (Settings -> System -> etc) list also the installed version offering to reinstall it?
alfacrux said:
Does the built-in updater (Settings -> System -> etc) list also the installed version offering to reinstall it?
Click to expand...
Click to collapse
yes

Categories

Resources