[OFFICIAL] LineageOS 18.1 for the Moto Z2 Play - Moto Z2 Play ROMs, Kernels, Recoveries, & Other D

[OFFICIAL] LineageOS 18.1 for the Moto Z2 Play - Moto Z2 Play ROMs, Kernels, Recoveries, & Other D

i had built this myself at home but never thought to publish it or make it official since i thought it was too much work.
so glad someone actually did publish an 18.1 rom for this phone so not everyone has to build it at home (especially since many cant).
great work as usual

What the hell, that's unexpected to say the least. I'm quite happy with AICP and don't feel like hopping but good to have choice.

I owned this phone for 4 years hoping it would get official Los. 2 months ago it got destroyed and now i see this.

Arcline said:
I owned this phone for 4 years hoping it would get official Los. 2 months ago it got destroyed and now i see this.
Click to expand...
Click to collapse
that sounds painful and i feel really bad.
how destroyed is it? is there any chance of repairing it? and how did it get destroyed...

Hello! Which MindTheGApps package should I install: the arm or arm64 one?
And which version: 11 or 12.1?
Thank you in advance for your help and work.

dezraj said:
Hello! Which MindTheGApps package should I install: the arm or arm64 one?
And which version: 11 or 12.1?
Thank you in advance for your help and work.
Click to expand...
Click to collapse
arm64, 11

Flash, bang, mind the gapps - and here comes Lineage! Really nice version, very light (but not poor), battery friendly. Moto actions, JBL mod and powerpack mod work fine, no unexpected behaviour so far (three days).
Thanks @marcost22 !

System encryption doesn't work. Phone won't boot after using the option.
Also how this ROM has built in google services? Without installing any GAPPS package there is already google play services, play store and google app installed out of the box.
Nevermind, I didn't format system between installations that's why gapps remained.

Notification LED working for anyone? It's enabled in options and I tried setting different values but doesn't seem to ever blink.

Newbie question here. I'm stuck at the step of flashing the lineage recovery img. Do I need TWRP installed first? Or does lineage-recovery replace that? It doesn't seem to be writing the recovery - or it is writing it super-quick - and I dont understand what the errors/info messages mean:
Code:
>fastboot flash recovery lineage-18.1-20220807-recovery-albus.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16462 KB) OKAY [ 0.618s]
Writing 'recovery' (bootloader) Image not signed or corrupt
OKAY [ 0.154s]
Finished. Total time: 0.818s
I've tried booting into recovery after this, and nothing happens. When I hold volume up + power, I get into a bootloop of the yellow text warnings that I have an unlocked bootloader until I let go of either the volume or power, from which it will then boot into the regular OS.

Oh, never mind, it seems I can get to the Lineage recovery without turning off the device and instead using the volume keys from the fastboot menu to select "Recovery mode". And that appears to take me to LineageOS recovery. Not sure why I can't get there using the volume up + power.

Known issue? Capacitive buttons (back, home, recent) not working.
[Edit: This issue is resolved below - turns out the Z2 Play doesn't have those buttons!]
The built-in capacitive buttons on my Z2 Play don't respond and don't seem to be recognized. Is this a known issue? I've fiddled with button settings and gesture settings in both Trebuchet launcher and now in Nova launcher without success. I also tried installing Button Mapper (https://play.google.com/store/apps/details?id=flar2.homebutton), but it does not recognize these button presses either. I'm using visible nav menu now instead, which is fine. But thought I'd check to make sure that this is a known issue?
Everything else seems to work great!
Currently running:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228

meelten said:
Notification LED working for anyone? It's enabled in options and I tried setting different values but doesn't seem to ever blink.
Click to expand...
Click to collapse
I'm not sure where the settings are for this? I don't seem to have much in my default LOS settings controlling the LED.
There is a white LED that turned on by default for me with LOS 18.1 out of the box when the phone was plugged in, but I found it too bright and annoying, and didn't see where to change the colours or brightness. And I don't see any settings to configure the LED for specific notifications either. So I just set it to stay off when plugged in. And that's it: that's the only setting I could find for LEDs?

zyngfang said:
I'm not sure where the settings are for this? I don't seem to have much in my default LOS settings controlling the LED.
There is a white LED that turned on by default for me with LOS 18.1 out of the box when the phone was plugged in, but I found it too bright and annoying, and didn't see where to change the colours or brightness. And I don't see any settings to configure the LED for specific notifications either. So I just set it to stay off when plugged in. And that's it: that's the only setting I could find for LEDs?
Click to expand...
Click to collapse
Open settings and type notification light in search.

it's possible install lineage os 18.1 official on moto z2 play XT1710-08? With other rom there is a problem and need to skip the command but I'm never succeeded..
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Now I would try to install lineage os 18.1 (same version on my xiaomi mi5). Can i have problem during installation? Thanks!

zyngfang said:
Known issue? Capacitive buttons (back, home, recent) not working.
The built-in capacitive buttons on my Z2 Play don't respond and don't seem to be recognized. Is this a known issue? I've fiddled with button settings and gesture settings in both Trebuchet launcher and now in Nova launcher without success. I also tried installing Button Mapper (https://play.google.com/store/apps/details?id=flar2.homebutton), but it does not recognize these button presses either. I'm using visible nav menu now instead, which is fine. But thought I'd check to make sure that this is a known issue?
Everything else seems to work great!
Currently running:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228
Click to expand...
Click to collapse
I'm guessing that by capacitive buttons you are refering to the on-screen navigation? If so, when disabled can you navigate by using the fingerprint sensor?
specialdo said:
it's possible install lineage os 18.1 official on moto z2 play XT1710-08? With other rom there is a problem and need to skip the command but I'm never succeeded..
Now I would try to install lineage os 18.1 (same version on my xiaomi mi5). Can i have problem during installation? Thanks!
Click to expand...
Click to collapse
I'm guessing it's the chinese variant? If so, then as long as you have the Pie firmware and latest twrp you should be fine

marcost22 said:
I'm guessing that by capacitive buttons you are refering to the on-screen navigation? If so, when disabled can you navigate by using the fingerprint sensor?
Click to expand...
Click to collapse
I mean the touch-sensitive, haptic "buttons" that are built into the Z2 phone. They sit below the bottom edge of the actual screen, to the left and right of the "home" fingerprint button. In the original default Android system, those buttons light up with white icons when they are available and they function as back and recent apps buttons, and they vibrate when touched. In this version of LOS 18.1, there are no buttons there. There is no haptic feedback or vibration when I touch those areas using LOS 18.1, and the system doesn't seem to be aware that they exist.
The fingerprint sensor works as a regular home button when I disable the onscreen buttons. But there is no back or recent app button, which makes it impossible to navigate the UI. So I have the onscreen buttons enabled. I note again that this functions OK for me, so it is not a deal breaker. But it would be better for me if those haptic (capacitive) buttons worked, because then I could disable the onscreen buttons and increase the usable space on screen. Does that make sense?

Moto Mod Compatibility - Quick Review - August 2022
I've been testing various Moto Mods under LOS 18.1 as I have time.
Functioning:
Moto Turbo Power Pack
Initial test: Seems to work fine!
Notes: There is no special battery icon or indicator that it is working, but you can go into the Battery or Moto Mod area to verify or configure.
JBL Soundboost 2 speaker
Initial test: seems to work great!
Notes: Don't try to use the equalizer settings in the JBL audio app - instead simply use the built-in AudioFX equalizer. You may need to open up the generic Moto Mods app for the speaker to be recognized. Drains battery from mod first as intended (before draining phone battery).
Insta-Share Projector
Initial test: Seems to work fine!
Not Working:
Per "Known Bugs" camera mods won't work:
360° Camera
Initial test: Mod recognized, but app won't run.
Unable to use with other apps.
Haselbad Camera
Initial test: Mod not recognized.
Camera will not power via power button when attached.
Tested with:
lineage-18.1-20220807-nightly-albus-signed
lineage-18.1-20220807-recovery-albus
MindTheGapps-11.0.0-arm64-20220217_100228

zyngfang said:
I mean the touch-sensitive, haptic "buttons" that are built into the Z2 phone. They sit below the bottom edge of the actual screen, to the left and right of the "home" fingerprint button. In the original default Android system, those buttons light up with white icons when they are available and they function as back and recent apps buttons, and they vibrate when touched. In this version of LOS 18.1, there are no buttons there. There is no haptic feedback or vibration when I touch those areas using LOS 18.1, and the system doesn't seem to be aware that they exist.
The fingerprint sensor works as a regular home button when I disable the onscreen buttons. But there is no back or recent app button, which makes it impossible to navigate the UI. So I have the onscreen buttons enabled. I note again that this functions OK for me, so it is not a deal breaker. But it would be better for me if those haptic (capacitive) buttons worked, because then I could disable the onscreen buttons and increase the usable space on screen. Does that make sense?
Click to expand...
Click to collapse
My nor any Z2 play i know have such buttons; only the fingerprint sensor which in stock can double as the "one button" navigation system (via gestures); could you please send me a picture of how it looks like in your device?

Related

[ROM][0.0.7.3]ICS CM9 ThinkPad Tablet (Alpha)

This a a CM9 Port for the Thinkpad Tablet made by Jon2555 and me. Its still under development, so you might run into bugs.
You are flashing this ROM on your own risk. It could eat your kittens, steal your breakfast or brick your device!
{
"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"
}
(Higher Resolution)
Requirements:
- A US, UK or WE device (Might also work on others)
- root (obviously)
- CWM
Installation:
- Download xxx.zip and put it on a sd-card
- Boot into CWM (Reboot and press Vol+)
- Make a nandroid backup in CWM!
- Make sure the backup worked!
- Full Wipe (May not be needed if you come from an earlier CM9 version)
- Flash zip in CWM
Restore HC:
- Boot into CWM (Reboot and press Vol+)
- Restore old nandroid backup
Working:
- Wifi
- Touchscreen + Stylus
- Bluetooth
- HW Acceleration
- Sound
- External Mouse
- Folio (mostly)
- VPN
- Hardware Button
Not Working
- Camera
- 3G
- HW Video Decoding (i.e. for Youtube HQ)
- No mount as USB/MTP
Known Bugs
- Wifi doesn't always reconnect to networks
- Trebuchet has wrong size and misses a few pixels
- Sometimes apps on the market are incompatible (see Play Store/Market)
- Sound doesn't mute when headphones are plugged in
Play Store/Market
Sometimes the market marks apps as incompatible. This happens randomly. If it happens to you try one (or more) of the following:
http://forum.pocketables.net/showthread.php?p=80033
http://forum.xda-developers.com/showpost.php?p=23753023&postcount=5
Search here in xda for a hacked market and install it
Reflash the whole ROM
Folio
The Folio works but some of the special keys don't. One problem with the Folio is, that there are different Keylayouts (i.e. UK, US) but without a different device ID. In the standard setup this ROM uses the UK layout, if you want to use a US layout, you have to delete a file:
Code:
su
mount -o rw,remount /system
rm /system/usr/keychars/Vendor_1241_Product_0003_Version_0110.kcm
Thanks:
- The Cyanogenmod team
- digetx for the Green Flash fix
- Everyone releasing their source codes for other builds
- Everyone trying to find and report bugs
If you like our work press the thank button or buy us some lego.
Download
http://everyrandom.com/files/download.php?file=185alpha00731.zip
Sourcecodes
https://github.com/Koshu
Changelog:
Code:
[B]Version 0.0.7.3.1[/B]
- Fixed Pen driver to solve reboot problem
[B]Version 0.0.7.3[/B]
- Added new experimental play store hack v2
[B]Version 0.0.7.2[/B]
- Added new experimental play store hack
[B]Version 0.0.7.1[/B]
- removed assert check again
[B]Version 0.0.7[/B]
- fixed touchscreen scrolling issue
[B]Version 0.0.6.3.1[/B]
- added missing generic.kl again
[B]Version 0.0.6.3[/B]
- Added xt_qtaguid to kernel to solve reboot bug
- Changed some configs to fix minor bugs
[B]Version 0.0.6.1[/B]
- Fixed wrong Generic.kl for folio
[B]Version 0.0.6[/B]
- Fixed Hardware Button Rotate Key
- Fixed Hardware Button Home Key
- Added disable Touchscreen through pressing the Browser Button
- Fixed VPN (Needs testing)
- Fixed Folio (Expect some keys not available in normal CM9)
[B]Version 0.0.5[/B]
- Changed to newest CM9 Sourcecode
- Fixed naming in storage listing
- Quill recognizes pen as pen
- Gtalk works with new CM9 and new Gapps
[B]Version 0.0.4.2[/B]
- Sound works (no Headphones, but maybe we will get there today) Update: Headphones work
[B]Version 0.0.4.1[/B]
- Sound works in ALSA and partially in Android (Click sounds work, youtube and Music doesn't)
[B]Version 0.0.4[/B]
- Fixed Green overlay issue (thanks digetx for the hint)
- Fixed Problem with surface Buffer (No force close of GUI anymore)
[B]Version 0.0.3.2[/B]
- Modified N-Trig drivers directly in Kernel (Touch Wrapper isn't needed anymore)
- Still trying to figure out how to fix the green overlay issue
[B]Version 0.0.3.1[/B]
- Fixed GPS (?)
- Fixed internal media storage
[B]Version 0.0.3[/B]
- Wrapper for new ICS-Touchscreen API -> Touchscreen works
[B]Version 0.0.2[/B]
- Wifi works (But not Signal Strengh in UI)
- Reboot Problems hopefully fixed (needs further testing)
[B]Version 0.0.1 (First Try)[/B]
Working:
- successfully booted
- stylus
- bluetooth (loaded fine but not tested transfering)
Bugs/Not working:
- Reboot Problems (like in CWM)
- No touchscreen (only Stylus)
- No wifi
- No camera
- a bunch of other things

First!!!!.
On a more serious note, nice to see a more organised OP for the rom. I hope we can make more progress with the development.

I can confirm this version does fix any freezing that was happening due to the pen button bug. This version is also silky smooth thanks to Koshu's and Jon's hard work.
Also, a fix for trebuchet not displaying correctly is to use Apex Launcher highly recommend. It has additional features as well that in my opinion make it a better experience.

Yup, that problem was happening every 5-10 minutes, and just worked for two hours without any problem with .00731. Also, just on another note, there's that ever occurring problem of loss of pen strokes after like 5-10 minutes after which I have to replace the battery or lock/unlock the tablet before it continues to work. Is this now a hardware problem as I've had it since day 1, through all the updates and also this ROM now.

@yahoowizard
I had that issue since day once as well, and it happened just yesterday when I restored an early build (I think it was 005x but not sure). But I feel like since 006x I haven't had that issue.
I've used build 00731 (full wipe) with Quill and Lecture Notes for several hours today without that occurring. So yeah I'm not sure what causes that bug, but like I said above, I feel like it was fixed a few builds past.

Put this on last night. Not having any market issues (any problem apps you want me to check?)
Only problem I have now is Chrome Beta still crashes after a few seconds use?
Thanks for all the hard work!

soveryevil said:
Put this on last night. Not having any market issues (any problem apps you want me to check?)
Only problem I have now is Chrome Beta still crashes after a few seconds use?
Thanks for all the hard work!
Click to expand...
Click to collapse
Yeah it does... and it does this on my other devices, too. Its still a beta so lets fix things with chrome when its stable or when there is nothing else to do.

with full wipe the installation takes about 15 seconds, says its complete (really skeptical here). on boot, it shows the lenovo logo but wont boot up, tried for about 20 minutes now..
//got bootloop now. so i guess i cant really say how it works for me

pau-pau123 said:
with full wipe the installation takes about 15 seconds, says its complete (really skeptical here). on boot, it shows the lenovo logo but wont boot up, tried for about 20 minutes now..
//got bootloop now. so i guess i cant really say how it works for me
Click to expand...
Click to collapse
A lenovo boot logo? Then something went totally wrong. I replaced the boot animation, means that there are still parts of stock HC on your tpt. You might want to recheck if the zip is downloaded and moved to your sdcard without errors and try again.

well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really

pau-pau123 said:
well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really
Click to expand...
Click to collapse
Ah ok that logo^^, that's normal, sorry thought you were talking about the bootanimation. Do you have an US device?

Koshu said:
Ah ok that logo^^, that's normal, sorry thought you were talking about the bootanimation. Do you have an US device?
Click to expand...
Click to collapse
haha ye, should have put it a little clearer.
ye, US, 32GB

pau-pau123 said:
haha ye, should have put it a little clearer.
ye, US, 32GB
Click to expand...
Click to collapse
Just to make sure, did someone else try to install ICS on a tpt with OTA2.5?

Koshu said:
Just to make sure, did someone else try to install ICS on a tpt with OTA2.5?
Click to expand...
Click to collapse
I did. I got stuck on the boot animation as well, but a full wipe of things followed by a reinstall of this ROM fixed it.

Koshu,
Thanks for the excellent ROM -- after a few hurdles that were all my fault, I managed to get it up and running.
First, I'd like to say: if anyone is unable to get this running because ClockworkMod Recovery reboots itself after 30 seconds (even if you're doing nothing, e.g. sitting at the main CWM menu), chances are you installed the "ROW" (Rest of World) CWM on a non-ROW tablet. This was the case for me. HOWEVER, don't fret if you already wiped out your system -- there's a workaround.
Plug a USB device with logic (e.g. not a "dumb" battery; something like a phone or flash drive) into the full-size USB "Host" port on your thinkpad. This, magically, will prevent CWM from rebooting after 30 seconds, allowing you to properly use it for backup/restore and for flashing CM9.
In fact, this is the only difference I could find between the ROW CWM that I accidentally flashed, and the US one. So if you always will have a USB device handy of some type, you can continue to use the ROW CWM and don't have to mess with it. Plug 'er in and it magically works!
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.

yahoowizard said:
Yup, that problem was happening every 5-10 minutes, and just worked for two hours without any problem with .00731. Also, just on another note, there's that ever occurring problem of loss of pen strokes after like 5-10 minutes after which I have to replace the battery or lock/unlock the tablet before it continues to work. Is this now a hardware problem as I've had it since day 1, through all the updates and also this ROM now.
Click to expand...
Click to collapse
pen wonk - pen is periodically not recognized by the system
Unfortunately, I experienced the pen wonk periodically in class today. I wonder if it's a hardware issue too or an Android issue, because I have also experienced it on every ROM including stock. I'll try to get a logcat while note taking tomorrow to see if we can get any information about the 'pen wonk' issue.
allquixotic said:
Koshu,
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.
Click to expand...
Click to collapse
First of all, congrats on getting up and running and figuring out that CWR workaround. I also have US, Wi-Fi only US TPT. I can successfully connect my bluetooth keyboard and even enable it as a input device within the bluetooth settings. But the keyboard isn't listed anywhere in the Language & Input settings menu. I believe it should have a new subsection name Physical Keyboard Is the keyboard folio listed?
@Koshu
I was wondering if there was a way to disable the 3G/WAN in ICS if no such connection is possible? I have a Wi-Fi only model but still have empty cell bars in my status bar. Just curious

pau-pau123 said:
well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really
Click to expand...
Click to collapse
Ok, so it already worked on similar devices. Did the installation Finish? Like allquixotic stated there reboot problems in cwm. It shouldn't reboot on it's own in the installation process.

allquixotic said:
Koshu,
Thanks for the excellent ROM -- after a few hurdles that were all my fault, I managed to get it up and running.
First, I'd like to say: if anyone is unable to get this running because ClockworkMod Recovery reboots itself after 30 seconds (even if you're doing nothing, e.g. sitting at the main CWM menu), chances are you installed the "ROW" (Rest of World) CWM on a non-ROW tablet. This was the case for me. HOWEVER, don't fret if you already wiped out your system -- there's a workaround.
Plug a USB device with logic (e.g. not a "dumb" battery; something like a phone or flash drive) into the full-size USB "Host" port on your thinkpad. This, magically, will prevent CWM from rebooting after 30 seconds, allowing you to properly use it for backup/restore and for flashing CM9.
In fact, this is the only difference I could find between the ROW CWM that I accidentally flashed, and the US one. So if you always will have a USB device handy of some type, you can continue to use the ROW CWM and don't have to mess with it. Plug 'er in and it magically works!
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.
Click to expand...
Click to collapse
"Mostly" Means that the Folio is working except some special keys, because there is no function to map them to in ASOP/CM9. These still need to be implemented. The rest should work out of the box. The driver folio is in the kernel, thats correct, but android still needs some mapping files to get a keyboard working. This is not the case for the mouse, which always worked if i remember correctly. Could you post a dumpsys with connected Folio?

obscure.detour said:
pen wonk - pen is periodically not recognized by the system
Unfortunately, I experienced the pen wonk periodically in class today. I wonder if it's a hardware issue too or an Android issue, because I have also experienced it on every ROM including stock. I'll try to get a logcat while note taking tomorrow to see if we can get any information about the 'pen wonk' issue.
Click to expand...
Click to collapse
Hm, never happened to me and I took a lot of notes with the tpt, too. Please also try to get a dmesg, because if this is happening on all roms, it could also be a problem of the kernel driver.
First of all, congrats on getting up and running and figuring out that CWR workaround. I also have US, Wi-Fi only US TPT. I can successfully connect my bluetooth keyboard and even enable it as a input device within the bluetooth settings. But the keyboard isn't listed anywhere in the Language & Input settings menu. I believe it should have a new subsection name Physical Keyboard Is the keyboard folio listed?
@Koshu
I was wondering if there was a way to disable the 3G/WAN in ICS if no such connection is possible? I have a Wi-Fi only model but still have empty cell bars in my status bar. Just curious
Click to expand...
Click to collapse
Jepp there is a way. It's not really disabling the 3G, more like removing the icon. But let me check if there is a way to auto detect this, because i try to avoid multiple ROM versions and I'm still planing to get 3G working.

How do I get a logcat or a dmesg? While using some developer setting in Writepad Stylus (I think?) I noticed that the screen doesn't recognize the stylus at all at some points. It wasn't that the lines weren't registering, it was just that it was almost as though the pen was dead. But yeah, replacing battery or lock/unlocking tablet fixes it so >.> no idea what's going on there. If you fix that problem, I will love you forever, hahahaha

[Q&A][ROM][7.1] LineageOS 14.1 for Xperia SP

Thank you so much @AdrianDC for all the effort you make to keep SP in top notch condition <3
Oh and Happy New Year Bro

thnx adrian for ur efforts wish u a happy new year ^^

@Adrian DC
Thanks for your excellent work and support. Happy New Year.
Use packages for ARM, Android 7.x, Micro or Pico
Click to expand...
Click to collapse
Is there any reason why you recommend the micro/pico packages? I am thinking to flash the stock package and I see that replaces a lot of stock/AOSP apps. Will that cause any problems with the ROM? Thanks in advance.

JetArmstrong said:
Is there any reason why you recommend the micro/pico packages? I am thinking to flash the stock package and I see that replaces a lot of stock/AOSP apps. Will that cause any problems with the ROM?
Click to expand...
Click to collapse
System partition is not big enough on older devices to support ROM and full gapps packages.
Pointless anyways as most apps can be added from the Play Store.

Adrian DC said:
System partition is not big enough on older devices to support ROM and full gapps packages.
Pointless anyways as most apps can be added from the Play Store.
Click to expand...
Click to collapse
Thanks for the fast response

Hi Adrian,
happy new year! I see you can't wait until new year to release the LineageOS for our Xperia SP, that's crazy Thank you, again!
One thing I could find in your first post: In future the root access will be removed from LineageOS? Yes, I know you write
information will be given later, but I'm nosy.. Any reason for this change by you or LineageOS?
Regards -kerberos-

thank you. Happy new year

Still cannot access sd card location at the file manager app?

engr_exxi said:
Still cannot access sd card location at the file manager app?
Click to expand...
Click to collapse
Yes, same for me here regarding the CM/Lineage file manager. If I use for example the Totalcommander it's no problem to use the SD-card.
Regards -kerberos-

-kerberos- said:
Yes, same for me here regarding the CM/Lineage file manager. If I use for example the Totalcommander it's no problem to use the SD-card.
Regards -kerberos-
Click to expand...
Click to collapse
but since the app is already included in the rom, and I don't want another app taking some precious storage. Still can manage to access the sd card's file through the settings menu. But better if the sd card's access is fixed at the app itself.

I have exact the same intention, but I can't fix it by myself. So I have to wait if most likely Adrian have time to fix it. My expectation is, due to the shift from CM to LineageOS he is busy with more important tasks. So my idea is just a temporary solution, until the standard file manager app is fixed.
Regards -kerberos-

engr_exxi said:
but since the app is already included in the rom, and I don't want another app taking some precious storage. Still can manage to access the sd card's file through the settings menu. But better if the sd card's access is fixed at the app itself.
Click to expand...
Click to collapse
just a workaround not a solution, you can access SD card's files from settings then Storage and then press the SD card name/icon and try to avoid pressing the eject button ofc
Sent from my Xperia SP using Tapatalk

I use file manager MiXplorer https://forum.xda-developers.com/showthread.php?t=1523691

Noob question. How to disable zram?

DomZ0628 said:
Noob question. How to disable zram?
Click to expand...
Click to collapse
I don't know how, but I know you shouldn't do that

Thanks a Lot for this Rom @Adrian DC
I'm having issue with offline charging.
when i unplug the charger, it shows the battery percentage and hang in there.
pressing power on/off key do nothing.
have to press emergency power off button or,
press and hold volumeUP and Power on/off button until phone vibrates.
Is there permanent fix for this?

Dn.Thanujaya91 said:
Thanks a Lot for this Rom @Adrian DC
I'm having issue with offline charging.
when i unplug the charger, it shows the battery percentage and hang in there.
pressing power on/off key do nothing.
have to press emergency power off button or,
press and hold volumeUP and Power on/off button until phone vibrates.
Is there permanent fix for this?
Click to expand...
Click to collapse
Same with cm13. Quick fix:
Power up your phone while the charger is connected.

I have two users. When i change of user, and return in first, the background change to default...

Dn.Thanujaya91 said:
Thanks a Lot for this Rom @Adrian DC
I'm having issue with offline charging.
when i unplug the charger, it shows the battery percentage and hang in there.
pressing power on/off key do nothing.
have to press emergency power off button or,
press and hold volumeUP and Power on/off button until phone vibrates.
Is there permanent fix for this?
Click to expand...
Click to collapse
JetArmstrong said:
Same with cm13. Quick fix:
Power up your phone while the charger is connected.
Click to expand...
Click to collapse
I'm pretty sure that in the builds a months before the end of CM13, there was the old charging animation, the colored one. Back then, everything worked find.
When I flashed the last snapshot of CM13, I got the black and white charging animation and since then, the bug has occured.
I hope this makes it easier to find out which commit caused this regression.

[ROM][UNOFFICIAL][8.1.0][TB-X704F] LineageOS 15.1 for Lenovo Tab4 10 Plus

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Wifi
Bluetooth
Audio
LED
USB
RIL
Encryption
Fingerprint
Camera (partly)
Broken
Camera (autofocus & hdr)
Hall sensor
Selinux Enforcing
Source code:
device: https://github.com/yener90/android_device_lenovo_TBX704
kernel: https://github.com/yener90/android_kernel_lenovo_msm8953
vendor: https://github.com/yener90/android_vendor_lenovo_TBX704
Important
If you are using this ROM first time, wipe data. Wipe data completely. I mean the option where you need to enter "yes". Use this option and then flash the rom.
This ROM only works with the TWRP I added.
If you want to use GAPPS, flash it directly after flashing ROM. Don't let the ROM boot. Otherwise your device will not get certification, so you will not have Google Access.
Instructions (thx @matshias, just changed few lines to get ROM flashing working)
Put your ROM (and GApps) onto your sdcard (sdcard must be exfat or fat32, NTFS not supported)
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Don't setup, cause you will need to format your tablet later again. Shutdown tablet. Hold volume up and power button to start to bootloader
Then run
Code:
fastboot flash recovery twrp-3.2.3-0-<your-filename>.img
to flash TWRP
Select with volume buttons "Recovery Mode" and press power button
Select to write to system, otherwise you can't flash ROM
Backup at least system and boot partitions to your sdcard cause you will wipe data in next step. Choose "System Image" for the system partition backup.
Format data using this tutorial
Flash ROM
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Restart
Download
2019-04-08
• changes to fingerprint
• changes to sdcard (careful those who are using sd card as internal)
• security updates: 2019-04-05
• updated TB-X704L fix file for fingerprint support
ROM
TB-X704L fix
TWRP
Older downloads
2019-04-05
• partly fixed camera (autofocus & hdr dont work), use Open Camera
• some debugging features disabled, should improve performance
ROM
2019-03-30
• fixed fingerprint
• first attemps fixing camera (will take longer than expected...)
ROM
2019-03-27
• intital release
ROM
Optional downloads
Dolby Digital Plus (use the TWRP one)
GAPPS (use 8.1 arm64; I suggest using pico variant)
Thanks
@highwaystar_ru (he gave me the important hint, also used his sources and his thread )
@LumenReaper (for his work with CM14.1, where I took big part of his device tree :fingers-crossed
@Flowah123 for the TB-X704L files :fingers-crossed:
Donations
For donations you can click here
Thanks to @rorzer, @Preyer11, @Tschumi, @MrMagic, @max_work & 5 x anonymous
Please don't support Lenovo and buy their tablets
Code:
[I]Updates vary depending on the model where our tablets receive Android and security updates after the introduction.
We announced Tab 4 10 Plus in February 2017 and since then it has received seven OTA updates.
However, this model has reached the end of its update cycle and will not receive any more updates in the future.
- Lenovo (2018-05-11)[/I]
Just seven updates and not even one major upgrade, please don't support them.
Reporting bugs
Please tell what mods you are using and what tablet variant (TB-X704F or L or ABCDEFGH..)
If your tablet doesnt start:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files and upload it here.
if your tablet starts and bug appears later:
go to TWRP. use file manager, go to sys/fs/pstore, copy the files
start your tablet normal, let the bug appear, enter adb root
use adb logcat and adb shell dmesg, copy the content to a text file and upload here
XDA:DevDB Information
[ROM][UNOFFICIAL][8.1.0][TB-X704F] LineageOS 15.1 for Lenovo Tab4 10 Plus, ROM for the Lenovo Thinkpad Tablet
Contributors
yener90
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2019-03-27
Last Updated 2019-05-13

The system itself runs very well. Also TWRP is very nice in landscape.
Maybe some notes after a short test phase, because your post is not so detailed yet.
Works:
- Encryption (forceencrypt is enabled)
- Clearly better audio quality than in Lineage 14.1 (Yener has already made me aware of my mistake)
- Significantly newer kernel (3.18.115 instead of 3.18.31)
Broken:
- Hall sensor
- selinux (for completeness only)
All in all very good rom. Thank you Yener!

Great work guys! I am waiting for the fingerprint to get fixed and then installing asap.

ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away
---------- Post added at 04:38 PM ---------- Previous post was at 04:38 PM ----------
ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away

peterCR56 said:
ROM loaded and running with no problems so far so thanks to @yener90, also thanks to @LumenReaper for starting the whole ball rolling. one thing I noticed is after doing Format data and wiping system, data and the caches i'm re-encrypted, it's not a major problem though, when i do another update in the future i'll format data again and see if encryption goes away
Click to expand...
Click to collapse
This rom has force encrypt enabled, so it will not go away

LumenReaper said:
This rom has force encrypt enabled, so it will not go away
Click to expand...
Click to collapse
good to know, i thought i missed something

:victory: finally

Thank you for doing this!!!
Thank you for working on this device!!! I thought the Tab 4 10 Plus I imported for Korea was never going to see another update after I read the news awhile back. I took the plunge and installed TWRP and rooted my device tonight. I can't wait to get Oreo or even Pie installed on my tablet in the future!

First off, very well done @yener90 and @LumenReaper, thank you.
Am I correct in thinking that if I flash this to my TB-X704V it should work except for the SIM functions ?
Also are Gapps included?
TIA

Sparkrite said:
First off, very well done @yener90 and @LumenReaper, thank you.
Am I correct in thinking that if I flash this to my TB-X704V it should work except for the SIM functions ?
Also are Gapps included?
Click to expand...
Click to collapse
I'm not sure, if X704V works. Try to boot from the recovery, I uploaded, from your pc.
For this switch to bootloader mode and enter fastboot boot twrp.img
If you get on your screen an error like: no dtb found, than your device requires special fix.
Don't try it out then.

yener90 said:
I'm not sure, if X704V works. Try to boot from the recovery, I uploaded, from your pc.
For this switch to bootloader mode and enter fastboot boot twrp.img
If you get on your screen an error like: no dtb found, than your device requires special fix.
Don't try it out then.
Click to expand...
Click to collapse
Cheers, for fast reply.
I'll certainly try that out later today and let you know.
EDIT:
Just tried it and booted to your TWRP just fine, nice landscape view BTW.
All appears OK, but while it "saw" the ext SD I couldn't explore it but I could the explore the internal SD.
Just one thing, when I went to exit by rebooting to system, it crashed and just hung there.

Sparkrite said:
Cheers, for fast reply.
I'll certainly try that out later today and let you know.
EDIT:
Just tried it and booted to your TWRP just fine, nice landscape view BTW.
All appears OK, but while it "saw" the ext SD I couldn't explore it but I could the explore the internal SD.
Just one thing, when I went to exit by rebooting to system, it crashed and just hung there.
Click to expand...
Click to collapse
Thats normal. Install twrp and boot to recovery. There it will never freeze.
Try it out. Before you do copy your system files to your pc. Maybe for your device some files are required.

Just one more thing, as I said, does the ROM have Gapps already installed?
TIA

Sparkrite said:
Just one more thing, as I said, does the ROM have Gapps already installed?
TIA
Click to expand...
Click to collapse
Nope
UPDATE
Download
2019-03-30
• fixed fingerprint
• first attemps fixing camera (will take longer than expected...)
ROM Download

I'm thinking on buying this tablet, but I've heard that the 5ghz wifi has some dropouts. Have anyone test it out with this rom with iperf? (Wifi Speed Test app for example)
Also I'm interested to know what issues have been found with the fingerprint. (1 minute before the dev solved it)

MiSSigNNo said:
I'm thinking on buying this tablet, but I've heard that the 5ghz wifi has some dropouts. Have anyone test it out with this rom with iperf? (Wifi Speed Test app for example)
Also I'm interested to know what issues have been found with the fingerprint.
Click to expand...
Click to collapse
Don't buy it please.
Don't support Lenovo. That ******* dont care about their customers.
I just developed that rom, to show that ****** that its not hard to build an Oreo ROM for this nice tablet.

yener90 said:
Don't buy it please.
Don't support Lenovo. That ******* dont care about their customers.
I just developed that rom, to show that ****** that its not hard to build an Oreo ROM for this nice tablet.
Click to expand...
Click to collapse
What would you recommend instead?
I come from a CHUWI Hipad that was a complete disaster: really hard to even create a TWRP
I've been looking for other alternatives and essentially we have:
Huawei and Kirin: 0% development with closed Kirin processors
Samsung/LG/Asus/Xiaomi: The cheapest with 3Gb goes for over $250 (there aren't many brands with cheap tablets in fact)
Chuwi, Teclast, ... all are **** brands with Mediatek processors that are even worse than Kirin for dev purposes.
So essentially for under $200 with 3Gb+ RAM there is only one Snapdragon tablet called Lenovo Tab4 10 Plus
But the only issue I've found so far reading reviews are the dropouts with 5Ghz WIFI AC band.

MiSSigNNo said:
What would you recommend instead?
I come from a CHUWI Hipad that was a complete disaster: really hard to even create a TWRP
I've been looking for other alternatives and essentially we have:
Huawei and Kirin: 0% development with closed Kirin processors
Samsung: The cheapest with 3Gb goes for over $250
Chuwi, Teclast, ... all are **** brands with Mediatek processors that are even worse than Kirin for dev purposes.
So essentially for under $200 with 3Gb+ RAM there is only one Snapdragon tablet called Lenobo Tab4 10 Plus
But the only issue I've found so far reading reviews are the dropouts with 5Ghz WIFI AC band.
Click to expand...
Click to collapse
Hehehe I also had a Chuwi Tablet and was a disaster . 5GHz was solved with latest update.
Xiaomi Mi Pad 4 Plus sounds nice for me. Xiaomi also has a much better support. It came out after my Lenovo Tablet. If that would be available than, I would buy Xiaomi.

Thanks for this. Great job.
Can we have R/W system? AdAway freezes when trying to overwrite system hosts file. Basically I would be happy with your first release supporting hosts file linked to other path either even without fingerprint or camera support.

yener90 said:
Hehehe I also had a Chuwi Tablet and was a disaster . 5GHz was solved with latest update.
Xiaomi Mi Pad 4 Plus sounds nice for me. Xiaomi also has a much better support. It came out after my Lenovo Tablet. If that would be available than, I would buy Xiaomi.
Click to expand...
Click to collapse
Yeah, I like Xiaomi Mi Pad 4 Plus, the problem is that the cheapest in my country is for $400, if I buy in Aliexpress it goes for nearly $300... and I found this tablet for just $180 (half the price!) in Amazon
I understand that most brand OS support is **** (including Samsung), and I definitely have a Xiaomi Pocophone F1 because they have a really great support not only in ROM dev, but good prices for replacements (screens and all that).
But If they have solved the 5Ghz issue, then I believe that we should even try in the future to go for official Lineage 16 as they did on the oldie Yoga Tab 3 Plus

[ROM][UNOFFICIAL][11][R]LineageOS 18.1 for z5c (suzuran)

Hi all:
Here is a LineageOS 18.1 ROM for Z5 compact (suzuran).
New: ROM with microG apk's included in priv-app:
Download 2023-06-12
Please pay attention: microG can't coexist with GApps! So decide whether to install microG OR GApps!
If you want to remove microG, enter these command line by line in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm /system/priv-app/DroidGuard/DroidGuard.apk
rm /system/priv-app/FakeStore/FakeStore.apk
rm /system/priv-app/GmsCore/GmsCore.apk
rm /system/priv-app/GsfProxy/GsfProxy.apk
exit
Reboot!
Or flash this microG-remover.
This is a 7z archive with the zip'ed ROM and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 11 (R)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 June 2023
Using Sony blob's from stock version 32.4.A.1.54
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!)
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted. For rooting you can use Magisk.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Audio
Bluetooth
Camera (with the restriction to 8 MP); both built-in camera (Snap) and 3-rd party camera apps.
Camera2 may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support
Fingerprint
FM-Radio (maybe it needs a few restarts before it's working)
GApps (MindTheGApps 11 arm64)
German app AusweisApp2
GPS
Headset
Hotspot
LiveDisplay
Location services
Notifications
Notification LED
Offline charging
Phone calls
Reboot into recovery and bootloader
SafetyNet test passed successfully
Signed build
SMS
Sounds
Torch
WiFi
...please tell me...
These things are NOT (or badly) working:
Encryption
Camera focus at low distances.
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.Please tell me...
Use this ROM at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this ROM in any way.
Benefits:
Added Aurora-Store, F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
One last request:
Please, do not ask about problems for which my ROM is not responsible.
From now on I will only react to problems that I can reproduce and that are caused by my ROM.
I'm sorry for that, but I'm developing this ROM in my spare time and I still have a normal life.

If you want to remove apps, that are available in much better variants (or that you don't need ), enter these lines one by one in a terminal:
Code:
adb root
adb shell
mount -o remount,rw /
rm -rf /system/product/app/Email
rm -rf /system/product/app/Exchange2
rm -rf /system/product/app/Jelly
rm -rf /system/product/app/Recorder
rm /system/product/priv-app/Eleven/Eleven.apk
rm /system/system_ext/priv-app/Gallery2/Gallery2.apk
"Email" is the built-in E-Mail app, I've replaced it with K-9 Mail
"Jelly" is the built-in browser, I've replaced it with Firefox
"Eleven" is the built-in music-app, I've replaced it with poweramp
"Gallery2" is the built-in picture gallery, I've replaced it with simple gallery pro
Don't forget to reboot!

Hello,
Thanks for updating the ROM!
The performance is about the same (maybe a bit faster), and everything works OK.
However hotspot is still not working for me.

litelinux said:
However hotspot is still not working for me.
Click to expand...
Click to collapse
Oh, I'm sorry, I haven't answered your post in the los18 thread.
I'll take a look at it asap.

I'm using this ROM since some hours now and I have to say, that it's working very good. Better that expected. The device is not getting warm (or hot) and the battery comsumption is very low.
I'll take a closer look at this for some days now.
If the overall performance is convincing, I will delete the "BETA" status...

Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.

esrevinu said:
Is the "Recent Apps" button in the nav bar working?
I just installed this rom, but that button is not working.
Maybe app switcher is missing.
Click to expand...
Click to collapse
Working for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

(Posted on accident, please delete)

@litelinux Thank you for the answer.
I had installed NikGapps full version. It seems that some gapps made that trouble. With NikGapps core, I can use "Recent Apps" button.
But, even NikGapps core version seems to cause unexpected reboots if micro SD card is set as phone storage(adopted storage), not potable storage.
And, is it normal that the fingerprint reader works when the screen is off?

Hello,
Animations are not as smooth as in Android 10, such as:
Opening/closing recents
Notification panel
Background grayout of popup boxes
Horizontal scrolling
Not sure what the problem is...
Sorry for repeating this but I really hope it would be solved.

esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
I can't confirm that at my device.

litelinux said:
Animations are not as smooth as in Android 10
Click to expand...
Click to collapse
Maybe because it's still in development state? At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...

esrevinu said:
And, is it normal that the fingerprint reader works when the screen is off?
Click to expand...
Click to collapse
Berni-0815 said:
At my device, for example, the fingerprint reader is not working when the device had been in deep sleep mode for a longer time. Then I have to unlock it by using the "normal" swipe...
Click to expand...
Click to collapse
Both are present on my device.

litelinux said:
Both are present on my device.
Click to expand...
Click to collapse
That's right. Something must have been messed up! I have to investigate it more.

Berni-0815 said:
That's right. Something must have been messed up! I have to investigate it more.
Click to expand...
Click to collapse
You need to cherrypick this commit
Keyguard: Allow disabling fingerprint wake-and-unlock · LineageOS/[email protected]
* When the fingerprint sensor is embedded in the power key, wake-and-unlock is total chaos. Add an option to disable it. * The default behavior is unchanged. Change-Id: I50c0a857daba92c17470d...
github.com

Hello,
Thanks for the ROM,
I installed this version, it works fine at the moment.
Indeed, the photo lag application but by installing open camera it's OK.
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP

esrevinu said:
You need to cherrypick this commit
Click to expand...
Click to collapse
Thanks. I've already seen that there have been made changes in that files. But unfortunately there have been made so much changes that a simple cherry-pick is not possible! I've tried to manually change these files and I'm hoping, it works.
I will report....

FRFaucigny said:
On the other hand, the resolution of the camera is at the maximum at 8.3MP.
You also have this resolution blocked?
With lineage OS 14 I was at 23MP
Click to expand...
Click to collapse
I've blocked nothing! AFAIK the maximum resolution of the built-in sensor is 8,3MP and the resolution of 23MP is realized by software upscaling. Try to take a photo of the same object with 8,3MP and 23MP and compare them. I for myself have never seen any difference.
So, for me 8,3MP is fine..

Bummer. I was hoping root install for F-Droid would be fix by now.

You're right! I haven't tested if the so called "FDroidPrivilegedExtension" can be used in this version. I'll try it next.
Is that what you're meaning?

[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 buildHere providea temp fix, for bluetooth, doze issue. I will fix it in next build.
1. Enable USB debug and allow debug as root in developer settings.
2. Run
Code:
adb root
adb shell mount -o remount,rw /vendor
adb pull /vendor/etc/vintf/manifest.xml
3. Open mainfest.xml with text editor, then Remove these codes in it:
Code:
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
4. Save and run
Code:
adb push manifest.xml /vendor/etc/vintf/manifest.xml
adb reboot

Sjll said:
URGENT notification! For 20210418 buildHere providea temp fix, for bluetooth, doze issue. I will fix it in next build.
1. Enable USB debug and allow debug as root in developer settings.
2. Run
Code:
adb root
adb shell mount -o remount,rw /vendor
adb pull /vendor/etc/vintf/manifest.xml
3. Open mainfest.xml with text editor, then Remove these codes in it:
Code:
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>1.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@1.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
4. Save and run
Code:
adb push manifest.xml /vendor/etc/vintf/manifest.xml
adb reboot
Click to expand...
Click to collapse
it says bluetooth version 2.0 not bluetooth version 1.0!
-------------------------------------------
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
------------------------------------------------
Anyway, I remove the this part of line but it didn't change anything.

star__dust said:
it says bluetooth version 2.0 not bluetooth version 1.0!
-------------------------------------------
<hal format="hidl">
<name>android.hardware.bluetooth.audio</name>
<transport>hwbinder</transport>
<version>2.0</version>
<interface>
<name>IBluetoothAudioProvidersFactory</name>
<instance>default</instance>
</interface>
<fqname>@2.0::IBluetoothAudioProvidersFactory/default</fqname>
</hal>
------------------------------------------------
Anyway, I remove the this part of line but it didn't change anything.
Click to expand...
Click to collapse
Make sure you really deleted this part in manifest.xml in vendor partition. For my test result, it solved the doze issue.
Or wait for next build.

Sjll said:
Make sure you really deleted this part in manifest.xml in vendor partition. For my test result, it solved the doze issue.
Or wait for next build.
Click to expand...
Click to collapse
unfortunately, it is still same!

star__dust said:
unfortunately, it is still same!
Click to expand...
Click to collapse
Sorry, I posted wrong codes. You need to remove 2.0 and only keep 1.0.

Sjll said:
Sorry, I posted wrong codes. You need to remove 2.0 and only keep 1.0.
Click to expand...
Click to collapse
I did remove bluetooth version 2.0 codes. as I said before it didn't change anything.
I got to say that rom was really smooth and stable for a beta build.
I will wait next build. Thanks anyway.

hehe, LOS 18.1 for this device, good news
@Sjll: Is it possible the include the signature spoofing patch (to be able to use microG) in your new build ?
That would be great since there is no opportunity to patch this from 'outside' afaik ...
Thanks in advance

2faraway2 said:
hehe, LOS 18.1 for this device, good news
@Sjll: Is it possible the include the signature spoofing patch (to be able to use microG) in your new build ?
That would be great since there is no opportunity to patch this from 'outside' afaik ...
Thanks in advance
Click to expand...
Click to collapse
I will consider it.
star__dust said:
First of all , thanks @erikcas @Sjll for your time and effort.
What I did.
1. Celean install. ( f8331 .192 stock rom )
2.Before first boot.
3.Flash ...Download twrp-3.5.2_9-0-kagura.img
4. Get in TWRP and copy lineage-18.1-20210418-UNOFFICIAL-kagura.zip , NikGapps-core-arm64-11-20210130-signed.zip to phone.
5. install lineage18.1 rom zip and Nikgapps-core zip.
6.Reboot. it should take 2 min or less.
------------------------------------------------
what is not working!
1.There is no incoming and outgoing screen so you cant answer phone or end the call.
2. Screen doesnt turn on or wake up with incoming calls.
still testing..
Click to expand...
Click to collapse
star__dust said:
I did remove bluetooth version 2.0 codes. as I said before it didn't change anything.
I got to say that rom was really smooth and stable for a beta build.
I will wait next build. Thanks anyway.
Click to expand...
Click to collapse
You need to check your proximity sensor with Dev Check App.

Sjll said:
I will consider it.
You need to check your proximity sensor with Dev Check App.
Click to expand...
Click to collapse
I have checked proximity sensor with Dev Check App. My proximity sensor works fine and rest of sensors too.
The problem is when I tap on person name in contacts list , calling screen doesnt pop up but you can hear dial sound.
Except the above problem it seems everything works fine for now.

star__dust said:
I have checked proximity sensor with Dev Check App. My proximity sensor works fine and rest of sensors too.
The problem is when I tap on person name in contacts list , calling screen doesnt pop up but you can hear dial sound.
Except the above problem it seems everything works fine for now.
Click to expand...
Click to collapse
I have installed lineage-18.1-20210419-UNOFFICIAL-kagura.zip without NikGapps-core-arm64-11-20210130-signed.zip.
Now, everything seems just fine.
Thanks.

star__dust said:
Second Try..
What I did.
1. Celean install. ( f8331 .192 stock rom ) ..if you have already done it skip this part.
2.Before first boot.
3.Flash ...Download twrp-3.5.2_9-0-kagura.img
4. Get in TWRP and copy llineage-18.1-20210419-UNOFFICIAL-kagura.zip , MindTheGapps-11.0.0-arm64-20210412_124247.zip
5. install lineage18.1 rom zip (reboot).
Click to expand...
Click to collapse
6. if you want to Gapps then get in twrp and flash MindTheGapps.
7.Reboot..

Anything to care of if using the single model (F331) ?

2faraway2 said:
Anything to care of if using the single model (F331) ?
Click to expand...
Click to collapse
rom says "Sony Xperia XZ Dual!"....be caution.
This mean, rom will change your phone model number from F8331 to F8332!
just in case , during first clean installation get your twrp backup for your f8331 rom.
if you want to get back old stock rom f8331, you will need your backup to turn your phone model back from f8332 to f8331.

alright, thanks mate, that should be no prob at all

lineage-18.1-20210419-UNOFFICIAL-kagura.zip Test ReviewEdit: Some are minor
** Experiencing reboot when taking photos using Camera for a while. (especially front camera, 15 seconds or sometimes while taking 2-4 photo) EDIT: I finally get the error after using 3rd party camera it shows me this error. (Camera ID 0 at the back and ID 1 at the front) you can recreate the error using the attached 3rd party apk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
** Frequently reboot when auto rotation is on while the phone is on landscape mode.** Random reboot when using fingerprint unlock. (encountered 4th time now)* After receiving notification screen won't turn on. (experience once)
* Double tap to sleep/wake don't work
** When turning on the phone from a long sleep, the touchscreen won't work or frozen, you need to press the power button for the phone to sleep then press again to turn it on for the screen to work. (I thought at first it's on the gestures that are not working but after several times of occurrence I notice that it's not responding to any touch, you have to turn off the screen and turn it on again for the touch to function)
* Sometimes you cant pick USB Preferences when connecting to a computer, but restarting the phone can fix the problem.
** Heating issue.---------------------------
USB OTG: Ok - works fine.
USB Tethering: Ok - works fine.
The data signal is better than stock. (in my experience)
---------------------------
rooting using Magisk makes me boot-loop.
still testing...

Hi @Sjll will this rom work for the Xperia XZs?

in the following conditions, the device will reboot
sometimes in camera, but the built-in gcam go is working fine for me.
the flashlight is turned on
sometimes while unlocking the device through the fingerprint sensor
IDK why but while launching the "mi home" app
and there are some issues in the following
sometimes especially after a long time of not using the device, the screen will freeze after it was turned on. it's the same whether it has the fingerprint unlock activated or not. after it was unlocked through the fingerprint and go into the home screen, it's not responding to any gestures. it happens more frequently than lineage os 16.
for some reason, it can't pair with my wireless headphone, and it says "system UI not responding". and I press "stop" and the screen goes black and it reboots.
the speaker and microphone are not functioning well during the "phone call" on the "local" hardware. I also encountered this issue when at lineage os 16. when I was in lineage os 16, my solution is connected to a wireless headphone, and it solved the problem. but since I can't connect to a wireless headphone currently, I can't figure out any solution and I can't make any phone calls. to be specific, when I am calling others, I can hear their sound, but they can't hear my sound. if I turn on the speaker mode, I will hear my own sound from my speaker with lots of noise.
and I am only a junior high student if any info I've given is wrong, I apologize.

Database Develop

welcome