LineageOS 20.0 for Sony Xperia XZ1 Compact
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
DOWNLOAD
ROM: https://sourceforge.net/projects/yoshino/files/lilac/lineage-20.0/
TWRP: https://sourceforge.net/projects/yoshino/files/lilac/twrp/
Suggested Gapps (MTG): http://downloads.codefi.re/jdcteam/javelinanddart/gapps (choose 13.0.0/arm64)
Check the ChangeLog below for firmware requirements!
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Or if you are coming from Lineage 19.x, dirty flash to 20.0 is possible too: flash the new TWRP, ROM, and GApps, su addons (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985
Source Code
https://github.com/whatawurst/android_device_sony_lilac
https://github.com/whatawurst/android_kernel_sony_msm8998
https://github.com/whatawurst/android_device_sony_yoshino-common
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-10
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE:
CHANGELOG
Suggested Gapps (MindTheGapps) - choose 13.0.0/arm64:
https://androidfilehost.com/?w=files&flid=322935 or http://downloads.codefi.re/jdcteam/javelinanddart/gapps
v1.2 (2023-05-10):
Updated to T QPR2 release (LineageOS upstream)
Updated to May 2023 Security updates (both ROM and kernel)
Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
Fully enabled IMS on Congstar Germany via overlay on lilac
Possibly some battery/performance optimizations here and there
Fixed Android Auto support
Added new LineageOS "Charging control hal" for battery charging care (3)
Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
2023-01-08 | 1.1 | 47.2.A.11.228
- Updated to T QPR1 release (LineageOS upstream)- New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)- Any other updates by LineageOS upstream- Kernel security updates (also thanks to Flamefire)- Dropped keyprovd service - it is useless on unlocked BL anyway- Show 4G instead of LTE icon - saves some space too- Enable IMS by default - this still only works if carrier is supported- Fix some selinux denials (also thanks to Flamefire)- Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
2022-10-03 | 1.0 | 47.2.A.11.228
Initial release
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Sneexy said:
Hello, I've flashed this ROM onto my device and it works, however Wi-Fi seems to randomly disconnect for a few seconds then reconnect, sometimes doesn't reconnect at all. Tried searching for a solution but found none. It seems to disconnect when any type of location activity happens? Currently rooted but also happens without root.
Click to expand...
Click to collapse
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
victor126 said:
did you format data
reboot to recovery
wipe all internal portions
reboot to recovery
then flash rom
just curious because i was gona try it
Click to expand...
Click to collapse
Yes, multiple times.
Dirty flash from 19.1 and all work! Thanks
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
susetoyix said:
I have done clean flash and I don't get any notifications or call screen on phone calls causing missed calls. No problems on wifi and mobile
Click to expand...
Click to collapse
Weird, first time hearing this. Everything works just fine for me.
sohrab1985 said:
Weird, first time hearing this. Everything works just fine for me.
Click to expand...
Click to collapse
Kinda not recurring anymore after a few more reboots. I'll keep a lookout on this.
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
t mobile and its nvmo's are the only place this phone is not white listed
rez78 said:
Dirty flash from 19.1 and all work! Thanks
Click to expand...
Click to collapse
does split screen work on 20. it didnt work for me on 19.1
victor126 said:
t mobile and its nvmo's are the only place this phone is not white listed
Click to expand...
Click to collapse
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
How does it work compared to 19.1? Any bugs?
azndan2 said:
Anyone know if lte for t-mobile works on this? I couldn't get lte on lineage 19.
Click to expand...
Click to collapse
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
norabitox said:
4G calling didn't work for me.
I used carrierconfig, the LOS version with 4G calls working.
This requires root.
The carrierconfig is located at data/user_de/0/com.android.phone/file.
carrierconfig-com.android.crrierconfig-~.xml
Replace the contents without changing the numbers in the name.
Why don't you try it?
sorry for my weird english.
Click to expand...
Click to collapse
What do I replace the contents with?
tonsofquestions said:
Could you be more specific? I believe it's blacklisted on AT&T. It doesn't work at all on Verizon, because it has the wrong bands.
I've seen plenty of reports of it working on T-Mobile.
Click to expand...
Click to collapse
correct. t mobile and mint, and others that use t mobile work.
azndan2 said:
What do I replace the contents with?
Click to expand...
Click to collapse
carrierconfig.xml for the LOS version that LTE was working on your phone
victor126 said:
correct. t mobile and mint, and others that use t mobile work.
Click to expand...
Click to collapse
Sorry, what? Can you please be more specific?
First you said it was _not_ whitelisted on T-Mobile (so presumably doesn't work) and now you say it _does_ work on T-Mobile.
Related
{
"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"
}
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. You can also view the Changelog for a full list of changes & features.
Stop Update. My phone is bricked.
禁止任何内置推广APP以及收费ROM使用或参考本项目
Thanks
HamsterReserved
@modpunk @derf elot
Read FAQ at first please, Don't ask again.
What's working
Boots
RIL (Calls, SMS, Data)
Wifi
Bluetooth
Video Playback
Audio ( Record and Playback )
Camera
Flash
IMS (Partly)
VoLTE(Voice over LTE) Tested on G8142.
Dual sim cards
Know issue
1. Selinux is permissive.
2. Forceencrypt is disabled.
FAQ: Read me please.
1. I'm G8141, Can I use los?
For G8141, You can try to delete :
Code:
persist.vendor.radio.multisim.config=dsds
persist.radio.multisim.config=dsds
ro.telephony.default_network=9,0
in build .prop.
2. Google play service
Flash Opengapps or MindTheGApps by yourself. Or install MicroG.
3. Bootloop at Sony Logo
Try force-reboot.
If phone still bootloop, format cahce, system partition and flash zip again. DON'T flash gapps or Magisk. If you still bootloop, you may need to format userdata and make a clean installation.
4. I want Gcam
Los16 is based on stock blob, we are lack of support of RAW, so we can't support gcam.
4. I want longer battery time
We get full performance of CPU and GPU by default, you can try to limit the frequency of CPU.
4. I meet random reboot
Try to format userdata partition and make a clean installation. For G8142, you can try to disable Enhanced 4G LTE Mode in Mobile network. This will disable IMS, but more stable.
Version:
V1 based on stock 47.2.A10.62.
V2-Series based on stock 47.2.A10.80.
Download:
AndroidFileHost
Update Log:
V2.88:
1. Overclock [email protected] [email protected]
2. Support double tap to wake.
3. Full F2FS support of userdata and cache partitions.
3. Improve stability of sim card.
4. Optimization for swap.
5. CustomizationSelector added, it may reboot several times.
Notice: For dual users, Google FRP may cause crash if you make a clean installation. You need to unplug your sim card, after finishing the setup wizard, then plug in sim card again.
V2.86:
1. Support Android Go features.
This is an experiment version.
V2.85:
1. Color profile (Vivid mode) come back.
V2.8:
1. Fix the issue that volume of speaker low.
2. Fix Wifi disconnect (I played MOBA game on wifi for 2hours, No disconnect)
3. Fix no sound in call on V2.7.
4. Improve stability.
5. Color profile has been deleted by mistake, I will add it back in next version.
If you meet any problem, try to wipe cache and dalvik cache. I format my Data partition for this update.
V2.7:
1. Sony stock apps framework. added.
2. Sony Music, Album, Launcher added.
3. Lineage Music Album deleted.
V2.6:
1. Vivid mode in Setting-Display-LiveDisplay-Color Profile-Vivid
2. Fingerprint overlay fix.
V2.51:
1. 90Hz Screen frame rate.
2. Fix some overlay.
V2.5:
1.IMS works partly, we could call over LTE. This may need to flash FTF in your area.
2. Exfat supported.
3. Full languages supported.
Instructions :
Download the latest build
Flash Stock ROM
DON'T boot into stock.
Flash and boot to twrp.
Flash the latest build and gapps
Reboot
Contributers
@Sjll
Source
Github
ROM OS Version: 9.0
ROM Kernel: Linux 4.4
Version Information
Status: RC
Created 2019-06-19
Last Updated 2019-08-06
Thank you, I will try test.
It's a shame the US version is the only version I would use that is on 62. Ce1 is not there yet.
Edit. No fingerprint on the US I mean
HoiFung said:
Thank you, I will try test.
Click to expand...
Click to collapse
Edit:I encountered a strange problem, I can't change the system language to Chinese, but other apps show me Chinese. If you want to log, I will upload it.Other work is very good.
lonewolfbtown said:
It's a shame the US version is the only version I would use that is on 62. Ce1 is not there yet.
Edit. No fingerprint on the US I mean
Click to expand...
Click to collapse
Firmware in different regions should only be different on the operator's customization, I am not sure, but you can try,Flash other area firmware.I have been doing this in the stock firmware.
HoiFung said:
Firmware in different regions should only be different on the operator's customization, I am not sure, but you can try,Flash other area firmware.I have been doing this in the stock firmware.
Click to expand...
Click to collapse
My theory is lineage os will activate it when I flash it regardless of stock
EDIT: well fingerprint does work the the US version. But i get random freezes and reboots with for no reason when my sim card is in.
lonewolfbtown said:
My theory is lineage os will activate it when I flash it regardless of stock
EDIT: well fingerprint does work the the US version. But i get random freezes and reboots with for no reason when my sim card is in.
Click to expand...
Click to collapse
Temporarily no random freeze or reboot, did you start the stock firmware before flashing?
HoiFung said:
Edit:I encountered a strange problem, I can't change the system language to Chinese, but other apps show me Chinese. If you want to log, I will upload it.Other work is very good.
Click to expand...
Click to collapse
Because some people sell my ROM in China, I removed Chinese from system language.
HoiFung said:
Temporarily no random freeze or reboot, did you start the stock firmware before flashing?
Click to expand...
Click to collapse
No, you should not start with stock, maybe you need try ftf of other areas.
I only met freeze once. All work fine now.
I will try to improve the stability in the next version. Because the kernel is not based on Los15.1.
HoiFung said:
Temporarily no random freeze or reboot, did you start the stock firmware before flashing?
Click to expand...
Click to collapse
No I did not. Here's what I did.
1: flash the USA ftf .62
2: flashed twrp
3:flashed latest los and gapps
4: flashed magisk
5: booted device to no signal bars.
6: removed SD card. Rebooted after awhile
7: took sim out and device worked fine.
8: so its got problem with a T-Mobile sim card
lonewolfbtown said:
No I did not. Here's what I did.
1: flash the USA ftf .62
2: flashed twrp
3:flashed latest los and gapps
4: flashed magisk
5: booted device to no signal bars.
6: removed SD card. Rebooted after awhile
7: took sim out and device worked fine.
8: so its got problem with a T-Mobile sim card
Click to expand...
Click to collapse
Upload log please.
lonewolfbtown said:
No I did not. Here's what I did.
1: flash the USA ftf .62
2: flashed twrp
3:flashed latest los and gapps
4: flashed magisk
5: booted device to no signal bars.
6: removed SD card. Rebooted after awhile
7: took sim out and device worked fine.
8: so its got problem with a T-Mobile sim card
Click to expand...
Click to collapse
Maybe you need to set APN manually.
Sjll said:
Maybe you need to set APN manually.
Click to expand...
Click to collapse
Tried to set apn. Even deleted the apn. Still froze and rebooted
Sjll said:
Because some people sell my ROM in China, I removed Chinese from system language.
Click to expand...
Click to collapse
Please tell me where can I add it?
SoundEnhancement with cleraphase (Wireless Noise Cancelling) is possible to port in the future ?
And i see Sony Camera in this rom Slowmotion working normally ? All functions camera is ported ?
It is two important function for me on XZP
And what with Google Camera and ARcore on Lineage ?
hello
it is possible add 90hz kernel on this rom ?
CRNO said:
hello
it is possible add 90hz kernel on this rom ?
Click to expand...
Click to collapse
After the ROM is more stable, I will add it.
Indashio said:
SoundEnhancement with cleraphase (Wireless Noise Cancelling) is possible to port in the future ?
And i see Sony Camera in this rom Slowmotion working normally ? All functions camera is ported ?
It is two important function for me on XZP
And what with Google Camera and ARcore on Lineage ?
Click to expand...
Click to collapse
I had no plan to port SoundEnhancement to Los, because there still are much issues need to solve.
ARCore should works fine. You can download it from Google play, apkpure or apkmiror.
HoiFung said:
Please tell me where can I add it?
Click to expand...
Click to collapse
You need to rebuild the whole Los from source code.
After the system is stable, I will release the device tree. But I wouldn't add Chinese to the ROM on XDA before they stop selling my ROM.
lonewolfbtown said:
Tried to set apn. Even deleted the apn. Still froze and rebooted
Click to expand...
Click to collapse
Update adb log please.
I will check the source code. All works fine on my xzp. I think you could try to flash other areas' ftf files.
This thread hosts personal builds of LineageOS 17.x and PixelExperience 10 for Mix 2. Full credits to Arian, Wight and others doing the actual bringup, allowing us to build upon the awesome work.
Small changes in my builds:
Default stretch-to-fullscreen (force apps to render in 18:9) - LOS official solution defaults to OFF, which complicates setup
Grey-blue DeskClock color scheme (when possible)
Navbar stays on the right side of the screen under 270° rotation (optional - set the behaviour with "setprop persist.ui.seascape.disable <true|false>" in a rooted shell)
Signature spoofing support from MicroG
Revived navbar layout tuning via sysui_nav_bar tunable
...
What's working:
Everything?
Instructions:
Use firmware Stable V11.0.3.0
Use official TWRP
Download the latest build and optionally GAPPS (PE comes with GAPPS though, don't use any from external sources)
Reboot to TWRP
Flash the latest build, GAPPS and whatever other additions you need
Reboot
Extras:
Read here if you want to use unencrypted data - post is from Oreo thread, but still applies
Downloads:
SourceForge folder: https://sourceforge.net/projects/andyyan/files/ - new releases in the "10" folder
Root: use Magisk
Google Apps: http://opengapps.org/
Source Code:
https://github.com/LineageOS/
Donation:
Donate to @NeoArian
Donate to @wight554
Donate to me
XDA:DevDB Information
LineageOS 17.x, ROM for the Xiaomi Mi Mix 2
Contributors
AndyYan, NeoArian, wight554
Source Code: https://github.com/LineageOS/
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: MIUI V11.0.3.0
Based On: LineageOS
Version Information
Status: No Longer Updated
Created 2020-01-11
Last Updated 2020-02-27
Reserved
I don't know for how much longer I'll be able to keep building these, but even if I do stop, these should still serve as a good basis for installing GSIs, so you can leverage many of them out there, including my own. As far as I've tested the only major bug on that front is the proximity sensor.
Compared to the test builds of last year...
- Now using official LOS device trees - you might have to clean flash even if you come from a previous test build by me
- IMPORTANT regarding PE - if you're clean flashing, flash the package twice so that /system can be populated properly. I have no idea why this is happening...
is there any ETA on android 10 Resurrection Remix?
also thanks for your work as usual!
Mollic said:
is there any ETA on android 10 Resurrection Remix?
Click to expand...
Click to collapse
Its customization-centric role has largely been replaced by Havoc nowadays, so with my limited SSD space I'm dropping that as well.
Screen time have a bug, is look like this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great job for years
Grick713 said:
Screen time have a bug, is look like this.
Click to expand...
Click to collapse
Have you changed your system font? Seems incompatible.
Have a problem while installing new PE.
Wiped everything (system, vendor, data). Installed zip (twice, as advised), no error messages.
TWRP warns on reboot that no OS is installed. Phone reboots to fastboot.
Tried twice with the same result. Tried re-downloading zip without success.
Ok, managed to solve the problem. As the device tree is from LOS, the solution is in the LOS thread. Need a recovery with support for SAR. Seems like official TWRP does not. So flashed recovery from the first post of LOS thread and the OS have installed just fine.
dairinin said:
Have a problem while installing new PE.
Click to expand...
Click to collapse
Thing is, I tried Wight's SAR TWRP and it's the same thing on my side - I really had to flash it twice (but not in the same queue/go).
This shouldn't have happened in the first place either, as LOS flashed just fine without this hassle.
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
AndyYan said:
Aw, I don't use GAPPS so I didn't verify that...
Does manually changing prop.default make it pass? Supposedly there's nothing in the device source dictating that.
Click to expand...
Click to collapse
There are several lines that need to be changed (for instance, arch is set to 'arm' instead of 'arm64'). I decided to go with PE for now and don't want to reconfigure all stuff once more.
What a treat to start 2020 to! Thanks for the new build Andy. I'll be reporting back if I find something buggy or similar =)
candiduslynx said:
You can find them on Sourceforge: https://sourceforge.net/projects/opengapps/files/arm64/beta/
However, not flashable on LOS: Gapps detect SDK 27 (Android 8.1). @AndyYan, can you look into it?
Update: found that PE prop.default file is fine, but for LOS it's old (says SDK=27 and some stuff more). I think you forgot to include proper props to LOS build.
Click to expand...
Click to collapse
Weird, I didn't had this problem yesterday. I used "open_gapps-arm64-10.0-nano-20191209-BETA.zip" on LOS.
@AndyYan Thanks for your build of LOS, it's working like a charm here.
Just gotta need a patch for my provider APN. (I'm on it)
Great news!!! Thank you Andy. Can i dirty flash from LOS16 to LOS17?
The problem is solved，thanks！
SanHelios said:
@AndyYan
Nice to see you again being active, and thx (of course to all users who made it possible) providing LOS 17.
I know, this is probadly the wrong thread for this, but openGapps doesn't provide GAPPS for 10. The option is always greyed-out. Where do i get GAPPS then?
Click to expand...
Click to collapse
I recommend flamegapps
Thanks @AndyYan for the build. I have flashed the PixelExperience version and it is working fine. Using Parrot043's GCam version and the photo quality is also fine.
The major issue I have is regarding VoLTE incoming call support on my carrier (Airtel/India). Outgoing calls are fine, but for incoming (VoLTE) calls my phone doesn't ring at all, but on the caller side it looks as if it is ringing and I am not answering calls. For the time being I have switched to WCDMA mode.
Any input to solve the VoLTE issue is highly appreciated. I have tried creating an APN named IMS with type as ims, but that didn't work.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Moto g7
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 17.1 thread for the Motorola Moto g7, codename river.
How to Install:
Please follow the instructions on our Official LineageOS Wiki page here.
If you don't follow these instructions, please don't expect support here. We also don't support 3rd party addons (Magisk/XPosed/Dolby/Viper/etc.), so please don't seek support if you use these.
Known Bugs:
None.
Notes:
Official Lineage OS builds for river ship with full Project Treble compatibility! Flash GSI's to your heart's content after flashing Lineage. Please don't report GSI bugs here, report them instead to the GSI's maker.
Technical details on our Treble implementation:
Treble is enabled with VNDK29, and VNDK runtime enforcement. VNDK runtime enforcement means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run GSIs. without need for hacks or additional flashable zips. We relabeled /oem to /vendor (as /oem isn't wasn't used in custom ROMs anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image.
Download:
LineageOS Updater
npjohnson's Personal Updater -- These are experimental, likely to break/eat your cat/destroy your data, and include GApps -- you'll find no support for these.
XDA:DevDB Information
[OFFICIAL] [NIGHTLIES] LineageOS 17.1, ROM for the Moto G7
Contributors
npjohnson, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Firmware Required: Newest firmware available for your variant
Version Information
Status: Stable
Created 2020-04-01
Last Updated 2020-04-15
Awesome!
VoLTE working?
Edit 4/3: Like the unofficial releases, still no Wifi calling on Fi. Would be great if we could get that working.
Just an imporant FYI - ICYDK Community
https://www.androidpolice.com/2020/...-android-10-builds-will-probably-launch-soon/
At the time of this writing - there are some signing issues related to LineageOS 10 Roms (including river), so the link provided will take you to only version 16. Rest assured though, the team is working on it. The above link to android police, explained it all for me, hopefully for you as well. A screenshot is included in case the above link with the reference points disappear. Thank you for npjohnson for taking the time to support this. At last the river gets Android 10
LineageOS 17.1 works wonderfully however the Trebuchet Launcher does not seem to work as it crashes even upon first boot but any other launcher works perfectly.
The FM Radio does not work at all unfortunately, neither on LineageOS 16 nor 17.1, I hope that gets resolved soon.
Other than that, great work!
Very great to see this release. I have 2 questions:
- 1. Does this pass safetynet by just installing? I mean I don't want to install Magisk and Magisk hide
- 2. Does it work without any risks with the Februrary 2020 security update? I heard that if you are in that security update and then make a wrong move with formatting a partition there is no way to recover a brick / no blankflash available?
Thank you in advance!
Almost full Pixel Experience
No issues so far, running smooth and fast. I feel that this device is running faster than my Stock Pixel 3a XL. Magisk is working, so I'm using it as a daily driver from now on. Thanks a lot :good:
@npjohnson
This sounds nuts but this actually boots on the Moto G7 Play too. This tells me that 64bit builds can be ported to our device. The only thing that would need to be changed (I think) are touchscreen drivers, and gpio keys. I was able to boot into LOS recovery by changing river to channel in the default prop and flashing it. The screen is split and mostly unreadable but it is recognized by adb. Flashing the dtbo allows the boot logo to display properly with some flickering. Everything after that is still split however.
Given this info; Would you have any interest in trying to build for us too?
Also, would you have any idea how to resize a vendor partition? I think if I flash the vendor.img, it might fix the touchscreen. Right now twrp says it's bigger than my target device. (Which is a load of crap, I have 22gb free.)
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Is the upgrade procedure from 16.0 to 17.1 supposed to erase my data ?
Is there any specific procedure to install magisk?
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
farscaper11 said:
So I and like other people that have been reporting on Reddit, my device powers down a few seconds it boots into Los 17.1 i can't be certain but I think it started powering off and rebooting into TWRP 3.3.1.2. This has been from a clear flash/install.
Formated/erased everything
Followed Los 17.1 instructions to install Os and Gapps, Magisk
Device Boots into L.o.s 17.1 Gapps updates then devices powers down and reboots back in twrp
The device now just reboots after booting into L.o.s 17.1
Click to expand...
Click to collapse
fastboot -w (formats data, internal SD so back them up before doing this)
AgentICS said:
So from what I've experienced so far, calling doesn't work when using Google Fi on T-Mobile and location also doesn't work either on any app. OTAs also fail via the LineageOS Updater and the FM Radio is broken too
Click to expand...
Click to collapse
I can also confirm the issues with the FM Radio and the OTA updates failing. Originally I thought it may be due flashing over 16.1, but both issues persist after a complete wipe.
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
cybersecuritystudy said:
Anyone have an idea what to do if LineageOS is preventing any sort of mobile data connection? I'm using a Fi phone that I've flashed the standard retail update on before to get the Android Update to Feb 1. I'm using A Sprint MNO called Tello that works fine on Stock, any ideas?
Click to expand...
Click to collapse
Did you check for the correct apn settings?
jman315 said:
Did you check for the correct apn settings?
Click to expand...
Click to collapse
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
cybersecuritystudy said:
Thanks for the reply. I've researched that, and can't seem to quite find how to make a change in that. The standard procedures for doing anything with Access Point Names did not seem to show up in either Lineage 16.0 or 17.1. I found info on my carrier site (Tello), but have no idea how to change it since it doesn't show up as an option to change in the mobile network settings.
Click to expand...
Click to collapse
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
AgentICS said:
Phone calls on Google Fi do not work when connected to T-Mobile, only Sprint
Click to expand...
Click to collapse
Likely the way you setup Gapps
Google Fi Requires some extra packages to function correctly
you can find my personal Gapps Fi Pico package here:
https://www.androidfilehost.com/?w=files&flid=306318
jman315 said:
For me the APN settings can be found under...
Settings -> Network & Internet -> Mobile network -> Advanced -> Access Point Names
or
I can also find it by just searching for "access point names"
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
The 4-12 nightly OTA was the first to apply successfully. One other thing I have noticed that does not work since coming from LOS 16 is night light.
Click to expand...
Click to collapse
Thanks for the info. It's not in that location, all I have is Settings Version, Wi-Fi Calling, Carrier Video Calling, System Select, CDMA Subscription, and Carrier Settings.
The good news is, it looks like its working as of the 4-17 version I retried last night without needing to change anything. Thanks!
Also on a side note, I noticed there is no superuser download option for this version of LineageOS yet. Is this something that is coming down the line, or is there just a problem with doing this on the OS level?
LineageOS 19.1 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious
Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.
Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage
short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx
geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...
OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...
ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.
LineageOS 19.1 for Sony Xperia XZ1 Compact
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1 Compact, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
DOWNLOAD
You can download the latest ROM releases here: https://androidfilehost.com/?w=files&flid=333224
Latest TWRP: https://dl.twrp.me/lilac/
Check the ChangeLog below for firmware requirements!
INSTALLATION
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, sohrab1985
Source Code
https://github.com/whatawurst/android_device_sony_lilac
https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.6
Stable Release Date: 2022-09-18
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE:
CHANGELOG
2022-09-18 | 1.6| 47.2.A.11.228
* Final release, fixed DRM, WebView/Chrome issues in 1.5
* GPS config update
2022-04-20 | 1.3| 47.2.A.11.228
Initial release
tried ver.1.3 but still have issues with split screen not working after loading all my apps. gets trebuchet errors. didn't have time to get logs or troubleshoot what app causes it. but im not getting it with flamefires 17.1
Nice to have a separate LineageOS 19.1 for XZ1C thread, but it might be nice to credit this ROM to @derf elot more explicitely in the OP, since it seems to be mostly his work.
Rrreutel said:
Nice to have a separate LineageOS 19.1 for XZ1C thread, but it might be nice to credit this ROM to @derf elot more explicitely in the OP, since it seems to be mostly his work.
Click to expand...
Click to collapse
No worries, I asked @No1Alien if he could open the thread since I don't have much time to maintain it
Hi guys, an first of all thanks for the work you've done.
Now i'm bit confuse, i'v achieved the flashing of the os correctly (or maybe not) but i didn't update the firmware (an i think it's why my sim card is not detected). Question is : where can i find the firmware update "2022-04-20 | 1.3| 47.2.A.11.228" ? On sony website i only see 2021-12-06 for xz1c.
Am i missing something ?
Denam said:
Hi guys, an first of all thanks for the work you've done.
Now i'm bit confuse, i'v achieved the flashing of the os correctly (or maybe not) but i didn't update the firmware (an i think it's why my sim card is not detected). Question is : where can i find the firmware update "2022-04-20 | 1.3| 47.2.A.11.228" ? On sony website i only see 2021-12-06 for xz1c.
Am i missing something ?
Click to expand...
Click to collapse
2022-04-20 lineage 19.1 rom ver 1.3
47.2.A.11.228 Sony firmware
Updated in dirty way over LOS 18.1 from this forum, everything works including Zygisk and contactless payments
Hello, nice job. What TWRP version is needed ?
Very nice work! Haven't been able to test much yet, but when I picked it up just now after some days, I could see that battery drain does not seem to be an issue:
(This is not real-world usage though: wifi is on, but no SIM card, and just sleeping)
Rom lineage-19.1-20220408-UNOFFICIAL-1.2-lilac
Magisk 24.3
MindTheGapps 12.1.0
twrp 3.6.1_9-0-lilac
Running this on a spare XZ1 for testing. If the camera does eventually work one day, I think ill go to ebay aand buy a new XZ1c.
Thank you for all your hard work.
I'm currently on Havoc-OS 4.16 but can i flash Lineage 19 over Havoc? How to create backup of current Havoc in TWRP if i want to get back from Lineage OS 19? What should i select when creating backup?
Corias said:
Updated in dirty way over LOS 18.1 from this forum, everything works including Zygisk and contactless payments
Click to expand...
Click to collapse
Hi! Do you lose the homescreen arrangement (widgets, folders..) when you do this? (Trying to see if there's an advantage to dirty flashing)
Regards!
Dean F said:
Running this on a spare XZ1 for testing. If the camera does eventually work one day, I think ill go to ebay aand buy a new XZ1c.
Thank you for all your hard work.
Click to expand...
Click to collapse
Hi, check the last pages of the 18.1 thread, there's a link there. Someone got it working, seemingly. Still an early version, slow motion mode at least doesn't work and I'm uncertain on whether there's actually an improvement in quality vs open camera (took 2 pics to compare but didn't see any difference) but, still.. It works!
Hi and thank you (also to Derfy )! Great to see LOS 19 for this thing .
Question: I dirty flashed from latest available LOS 18.1, wiped Dalvik & cache, installed the MindTheGapps package as recommended, but swiping is gone on the AOSP keyboard. I can kill the AOSP keyboard forcibly, and then swiping came back just once but immediately disappeared again. Anyone else seeing this?
.:B:. said:
Hi and thank you (also to Derfy )! Great to see LOS 19 for this thing .
Question: I dirty flashed from latest available LOS 18.1, wiped Dalvik & cache, installed the MindTheGapps package as recommended, but swiping is gone on the AOSP keyboard. I can kill the AOSP keyboard forcibly, and then swiping came back just once but immediately disappeared again. Anyone else seeing this?
Click to expand...
Click to collapse
Have you tried turning it off and on again?
(tends to happen on first boot, no idea why)
Yes, multiple times .
claudiobar said:
Do you lose the homescreen arrangement (widgets, folders..) when you do this?
Click to expand...
Click to collapse
Maybe. I didn't use Trebuchet with LOS 18, so I can't say if the icons were in same places.
BTW guys how can I set an accent color in LOS 19?
Corias said:
Maybe. I didn't use Trebuchet with LOS 18, so I can't say if the icons were in same places.
BTW guys how can I set an accent color in LOS 19?
Click to expand...
Click to collapse
By changing the wallpaper, it automatically chooses accent colors based on it. It's how "Material You" works.