Related
This is for CyanogenMod 13.0, Android version 6.0.1, unofficial builds whose primary purpose is meant as preview.
Credits: All credits go to kabaldan, stargo and CyanogenMod contributors.
Disclaimer
Code:
Use at your own risk, responsibility is all yours, provided as-is, no warranties...
You know the drill.
What has changed/is new can be viewed at cyanogenmod gerrit: http://review.cyanogenmod.org/#/q/status:merged
Latest change for the January 30, 2016. build is at http://review.cyanogenmod.org/#/c/130563/
Latest change for the February 13, 2016. build is at http://review.cyanogenmod.org/132753
Latest change for the March 21, 2016. build is at http://review.cyanogenmod.org/127971
SELinux is disabled (if you care about security you'd might wan't to wait for an official build)
SELinux enabled in March 21. build
ART preopotimization is enabled: speeds up first boot after wiping dalvik cache: only some of framework, GApps (if present) and user installed apps need to be compiled. It also saves some space in /data as system apps odex/art/oat files are stored in /system partition instead of /data/dalvik-cache. This is the reason for the large size of the update package.
disabled GPU page faults logging in kernel as it only (unnecessarily) spams the logs
Included the new Snap camera app (the old AOSP Camera2 is still kept as a fallback): Both are called "Camera" but you'll be able to easily differentiate between them by the icon.
Keyboard backlight behaviour has been updated to resemble stock-like behaviour. Details can be read in the commit message of the change (Patchset 1, not PS2, or here). Feel free to test and share what you think.
Reverted to old keboard backlight behaviour in March 21 build
All relevant changes (i.e. differences from default/stock CM13) can be viewed at my github repo
Installation (first time install):
1) Download the build
2) Boot into recovery (power button + voulme up)
3) Make a full nandroid backup
4) Flash update package (install zip ...)
5) Wipe data/cache (factory reset)
6) Reboot to system
Update (if you're updating existing cm-13.0 or upgrading from cm-12.1)
1) Download newer update zip file and install it from recovery.
2) Wipe dalvik-cache
3) Reboot to system
It might be useful to enable aplogd logging, especially if you come across some issues.
You can enable aplogd in terminal or adb shell
Code:
su
setprop persist.log.aplogd.enable 1
Logs are saved in /data/aplogd/
In case of a full system reboot include /proc/last_kmsg as well.
NOTE !!! :
Please do make a full nandroid backup! In case anything goes wrong or you simply wan't to go back, you should be able to recover/restore in a jiffy. If, by chance, you have issues restoring system when twrp claims it failed to mount system, a relatively simple workaround is to flash whichever CM update, flash GApps you used previously and then restore only data, wipe dalvik, reboot... hope for the best...
Downloads
March 21, 2016.
Some of changes:
Code:
Enabled SELinux enforcing
Reverted to old-style keyboard backlight behaviour: it won't be brighter than screen but it also won't completely turn off kbd backlight on very bright conditions (I shoud really put some effort into it...)
Using Flo's PowerHAL
Updated interactive governor in kernel
Enabled Motorola memutils in kernel (should improve memory operations)
Quite a bit of other updates/changes/fixes
All details can seen at CM gerrit and my github repo (not very practical but...)
MD5: 96ce2fc03b43c0123fcdc559fb531761
File size: 348,852,931 bytes
Download
February 13, 2016.
MD5: 19d3cb88cdc9a1cf1857b3e263298b19
File size: 348,081,995 bytes
Download
January 30, 2016.
MD5: 454c62323c5e8f93f96ec6a9de580a2f (or use the attached to post md5sum file)
File size: 343,989,482 bytes
Download
So from what I've experienced with using this all day, it runs perfectly. I've had no bugs or anything like that so far. I think service was working too (can't tell now because I just canceled my ting account) but earlier today when it was still active, I had bars. Didn't try data though.
Other than that, everything is running very very smoothly.
u guys probabaly already know this but my service with i-wireless aka a sprint based variant isnt detected at all. Shame cuz it runs likes a dream otherwise. I guess not installing gapps has contributed to this performance boost tho
How are you guys going about installing 13.0? Does it install nicely on top of 12.1 or is a device wipe required? How about your version of TWRP?
timekiller_9 said:
How are you guys going about installing 13.0? Does it install nicely on top of 12.1 or is a device wipe required? How about your version of TWRP?
Click to expand...
Click to collapse
Data wipe is not mandatory.
You can use kabaldan's twrp from cm-12.1 thread
I installed it over CM12.1, and besides some minor glitches (ie. bad version of leftover google services - which can be easily repaired by flashing the latest gapps), the ROM's running well. To be honest, I don't see many differences.
Thanks for great work
Hello.
Can anyone help me with installation CM13 at new phone? Should I root phone, install Safestrap, create new partition and install this rom on it? Or maybe in this phone should I do something else?
I have problem wit bootloader unlock. I try to pass on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
but when I enter a code webpage refuse to generate code :/.
KusioST said:
I have problem wit bootloader unlock. I try to pass on
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
but when I enter a code webpage refuse to generate code :/.
Click to expand...
Click to collapse
Please post in one of the many threads related to bootloader unlock issues in Q&A or General... this issue has nothing to do with CM13.
Also, just as an aside - if you can't get the code to work use one of the other methods like motochopper et al.
Sorry for that. I just don't see something like how to install this rom so I ask. I will search information in other parts of forum. You can delete my posts to maintain this thread clear.
mrvek said:
This is for CyanogenMod 13.0, Android version 6.0.1, unofficial builds whose primary purpose is meant as preview...
Click to expand...
Click to collapse
I installed this ROM, but GSM network don't work. There is no option in network setting to change network type like in 12.1 for XT897. In 13.0 for XT894 GSM patch was automatically added. I need to search some fix for this ROM and install it after I install ROM?
My phone have attached additional SIM slot for SIM card and I use it in EU.
KusioST said:
I installed this ROM, but GSM network don't work. There is no option in network setting to change network type like in 12.1 for XT897. In 13.0 for XT894 GSM patch was automatically added. I need to search some fix for this ROM and install it after I install ROM?
My phone have attached additional SIM slot for SIM card and I use it in EU.
Click to expand...
Click to collapse
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Proximity sensor and luminance sensor not working, and bright adjust not modify brightness. more someone with this problem?
mrvek said:
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Click to expand...
Click to collapse
So You said that I need to do second try and have hope that this time it will work?
Installed it on my wife's xt897... Data is currently unknown as due to the bloat of 12.1 she swapped to an iPhone (and boy she hates it). The front camera isn't showing up either. Google Calendar keeps quitting and showing as a pop-up error.
Otherwise it's a nice ROM indeed. Once the kinks are worked out (and I replace the battery) she'll probably use it again.
I have no problems with Google Calendar (but as I mentioned before, I flashed CM13 gapps just after system). Unfortunately you're right: front camera is broken. Hope somebody fixes that.
For me Cell data, calendar, wi-fi and also front camera are working. I have dirty flashed over CM12.1 and also flashed new gapps.
Funny, I dirty flashed over 12.1 and flashed Gapps as well. IIRC the Google calendar glitch, on this phone at least, was also in 12.1. If it were my phone is wipe and retry but beng my wife I'm not sure I can right now.
mrvek said:
No such issues here, everything works out of the box.
I remember something like that in the beginning of cm-12.1 when installing clean, there was no signal, no options under mobile network settings in Settings (without factory reset network was fully functional) but it was most likely some local/obscure glitch/derp. The only way around it was to not wipe data. Weird...
Click to expand...
Click to collapse
I made advanced wipe choosing system, data, cache, and dalvik-cache. Now after installation GSM start to work .
I have question about sms application. Why when i tapped 2 time this same letter i get some special letter (for example n --> ń)? Where can i change it?
KusioST said:
I made advanced wipe choosing system, data, cache, and dalvik-cache. Now after installation GSM start to work .
I have question about sms application. Why when i tapped 2 time this same letter i get some special letter (for example n --> ń)? Where can i change it?
Click to expand...
Click to collapse
Most likely kabaldan's multipress feature from the old cm10 days I keep using. Your system language is Polish?
Anyways, you can configure multipress language and timeout using system properties (terminal emulator or adb shell):
Language property: "persist.sys.keypad_multipress_l"
Timeout property: "persist.sys.keypad_multipress_t"
To setup language (default is "auto", i.e. system language):
Code:
su
setprop persist.sys.keypad_multipress_l {language code (cs, da, de, de2, es, fi, fr, hr, hu, it, lt, nl, no, pl, pt, ro, sk, sl, sv)}
To disable multipress feature use english language (en):
Code:
su
setprop persist.sys.keypad_multipress_l en
To setup timeout between keypresses while subsequent key presses are considered for replacement (default is 200ms):
Code:
su
setprop persist.sys.keypad_multipress_t {timeout value in miliseconds}
You can either experiment or lookup Unicode characters here or here. E.g., for Czech (cs) letter "A" is replaced with unicode "00C1" which translates to "Á", etc.
List of supported languages and the mapping can be seen in the commit: e.g. here for Czech language, etc.
As for everything else: I really have no issues whatsoever with CM13. I no longer use google calendar but had no issues with it, both rear and front cameras are working, led lights, proximity, ambient light sensor are all fully functional. Perhaps enable aplogd...
This is the Official Jaguar rom for Aries, which is based on AOSP with some flavors from Slim and Dirtyunicorn. The rom was originally made for Xperia Z1 Honami in August 2015, then extended to Z1c Amami and now it is time for Z3c Aries. There have been thousands of downloads and great success with both Z1s. You can check respective original development threads. I hope the trend will continue with Jaguar for Aries.
Why LP, as opposed to MM and Nougat? Several reasons. The main one is Sony's unfriendliness to development community. Camera sucks, because Sony wouldn't provide proper blobs. Also, MM brings very few features, as opposed to LP. MM is still in alpha, but is already being abandoned by developers in favor of Nougat. Nougat will never work for Z1/Z2/Z3, because Sony wants you to buy a newer device. And finally, all LP roms, except Jaguar, have been abandoned by their developers since November 2015. CM still publishes nightly LP, but they have abandoned CM 12.1 kernel, meaning, they haven't incorporated about 800 security patches from Google and Code Aurora in LP kernel. Enough reasons for you?
The main difference from other roms is the emphasis on security and multiple features. With that in mind , let's see what Jaguar has to offer:
1. Hardened Kernel, modified M5; hardened rom built with HYPERTOOL 5.4
2. All ciphers enabled in kernel instead of just a few
3. Hardened/Fortified Bionic and Libs
4. Fstack protection strong to resist buffer overflows
5. Many System apps and processes are made read-only, to reduce elevation of privilege
6. Selinux replaced with Tomoyo Security, Yam security
7. Disc encryption, keymaster to 256 bit AES instead of 128
8. Latest TWRP with working brightness and ability to decrypt Data (Coming Soon)
9. Random number generation mixed hardware/software, as recommended by Linus Torwalds
10. Options to randomize host on every boot
11. Option to have a separate password for lock screen and boot
12. Qualcomm's Time Services disabled due to leaking on early boot (set time to automatic to get it from your carrier)
13. WIFI Background Scanning disabled to prevent leaking
14. Internet disabled for both WIFI and Data until Afwall is set and activiated (Afwall included in download, install as regular app)
15. The phone is VOLTE ready and you have all network options available in Cell menu (not just LTE/WCDMA/GSM)
16. GRsecurity features, such as Sidechannel implemented
17. Some Pax Security Features
18. Option to deny USB connection: denied always; denied when locked; and allowed always
19. Hardened webview with Google and other "interesting" IPs removed
20. Prevention of bruteforcing screen pin: the phone will reboot upon 3 unsuccessful attempts
21. Perfect_Event_Paranoid ported from Grsecurity: now third party apps can't use other apps including system to elevate privileges
22. Camera hardware button works to focus, take pictures and start video recording
23. Option to disable writing to Tombstones (a lot of private info is dumped there if there is a crash)
24. Option to disable continuing writing of logcat
25. Option to disable device cameras: back; front, both or none
26. Option to disable third party apps to access clipboard
27. Always latest Google Security Patches
28. Always latest Code Aurora Security Patches
29. Changes ported directly from Google Android Gerrit, so most of those in MM and even N are in this rom
30. About 80% of kernel changes are ported into Jaguar kernel from 3.10 and 3.18 (not Sony AOSP 3.10 that has Down Syndrome, but Linux/Google/Code Aurora one)
31. Rom is odexed to significantly increase boot speed (under 30 seconds) and application start
32. Many more security features ported from Linux and Copperhead OS
33. Dns Crypt: a feature allowing to choose among many Dns providers (all encrypted)
34. Seccomp: secure computing enabled in kernel
Other features include: Layers Theme Engine; Native Call Recording with interface integrated in Dialer with no restrictions; Privacy Guard; Native Wakelock Blocker; Native Black List; Global Menu; Slim Recents; Traffic Indicators; Advanced Reboot; Slim Pie; CPU Info on Screen; Ram Bar in Recents; Open source Superuser (not Supersu) included and integrated in Settings; True Offline Charging with Screen Off; Kernel Adiutor included (unzip and install as a normal app) and integrated in Settings plus more
Things users need to know to have smooth experience:. These are not bugs, but rather an explanation of some features
1. If you want to do data encryption, keep in mind that unlike Android, Jaguar uses 256 bit encryption. If you were encrypted on other roms, you won't be able to decrypt. So, wipe encryption and then re-encrypt on Jaguar. Also, keep in mind that if you ever did factory reset on official TWRP 3+ for honami, your data partition is screwed and have to be resized to enable encryption. This has nothing to do with the rom, but rather with the official TWRP itself. Fastboot my unofficial TWRP 3.0.2, (it is coming for Xperia Z3c, which, by the way has working brightness, as well as ability to decrypt and mount data
2. Jaguar contains a script running on early boot, which cuts the internet access to both WIFI and Data until Afwall is running. This is done to prevent leaking, as well as having all your internet traffic routed through some interesting number of servers, including this IP: 26.147.196.22. So, install Afwall and activate it, otherwise, no Internet for you
3. If your system language is different from English and you want to make changes in Phone/Cell Network settings, switch to English first, make the changes and then return to your language. The changes you made will hold. If you try to make the changes in your language, you will have com.android.phone crash. Localization takes time and is virtually impossible to implement in Jaguar, which is a one-person-rom
4. Sony TimeKeep, which is ported from MM/N, now sets the correct time on reboot without the Internet or GSM signal. All you need to do is set it once and TimeKeep will save/recalculate/restore the same on each reboot
5. GAPPS: if you use them, you need to flash them right after the rom (or each update) and before reboot. Flashing after reboot will result in multiple f/c
6. Due to Volte implementation, you might be required to flash LP or MM stock baseband (only if you have no 2g/3g signal)
Download: All updates and change logs are in Post #3
Instructions:
1. Be on LP at least, have TWRP, unlocked bootloader and root
2. In TWRP, wipe data/factory reset, then wipe System/Data/Cache/Dalvik
3. Flash the rom
4. If you use xposed, flash the latest installer
5. Reboot, install Afwall and Kernel Adiutor as normal apps; activate Afwall to have Internet
6. Enjoy the rom, say thank you, donate or do both
Warning: If your device and/or anyone in the immediate vicinity dies, don't blame me: it is all China and Russia's fault.
Credit: CM, AOSP, Slimroms, DU, Copperhead OS, Myself5 (kernel)
UPDATED KERNEL SOURCE: https://forum.xda-developers.com/devdb/project/dl/?id=23107 . Don't flash. This is not kernel, but rather sources to compile kernel
Kernel Source: https://github.com/AOSP-Jaguar/kernel_sony_msm8974
XDA:DevDB Information
JAGUAR ARISE LP 5.1.1 OFFICIA, ROM for the Sony Xperia Z3 Compact
Contributors
optimumpro
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP, CM, Slim,DU
Version Information
Status: Stable
Stable Release Date: 2016-10-16
Created 2016-10-17
Last Updated 2017-02-09
Development update and some screenshots
I broke my Z1 screen again and I am not in the mood for after market screens. And I am sick and tired of Sony crappy treatment of development community.
I am now looking at Lenovo Zuk Z2 or Z2 pro. Both excellent phones with the latest CPU and made out of metal and glass by Motorola which they bought from Google a couple of years ago. Zuk is friendly to developers and their blobs don't dumb down camera and they don't seek to "unify" bugs for all their devices. I no longer wish to support a fat bastard corporation that can't make a good phone, but thinks that just by putting their logo on the phone would make it worth $700.
RE Jaguar. I will continue to maintain Jaguar mainly with security patches... for a while, but my main work will be concentrated on Zuk. There is a lot of work to be done cleaning Android N and implementing security and other features from Jaguar...
Screenshots are here http://forum.xda-developers.com/showpost.php?p=62560391&postcount=2
This is where you have downloads
February 9: New release including
1. February Security patches
2. DNS_Crypt (in settings/security)
3. Seccomp (secure computing implemented in kernel)
4. Open Source Superuser integrated
5. Silent SMS notification enabled
6. 1440p profile in camcorder added
7. Sony TimeKeep: now time is set locally without the Internet or GSM signal (you need to set it right the first time only)
If you enable Dnscrypt and you use Afwall, allow internet for apps running as root...
If you prefer closed source Supersu, just flash the zip...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=23074
____________________________________________________
January 21. TWRP 3.x with the ability to decrypt and mount data on Jaguar
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22772
Flash in fastboot: fastboot flash recovery recoveryz3c.img
or use an app able to flash from SD card...
__________________________________________________________________________________
January 6: New release with January Google and Code Aurora patches. Also, Qcom time service is back...
Download: https://forum.xda-developers.com/devdb/project/dl/?id=22459
You can flash on top of another Jaguar release. Otherwise, fresh install (read the OP)
___________________________________________________________________
December 10. Rom updated to include
1. December security patches
2. Signature Spoofing (as in Omnirom), switch in Developer settings
3. USSD fixed (maybe)
Download: http://forum.xda-developers.com/devdb/project/dl/?id=22023
________________________________________________________________________________
November 10. Rom updated to include November Security Patches. I have also removed Supersu, since the rom has a built-in root manager and quite a few people no longer like Chinese owned Supersu.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=21434
_________________________________________________________________________________
October 17. Latest version:
1. October security patches from Google and Code Aurora
2. Over 80 commits from Google Master Gerrit which included changes to bionic, art, frameworks and system
3. Updated Afwall
Rom Download: http://forum.xda-developers.com/devdb/project/dl/?id=20947
Afwall/KernelAdiutor Download: http://forum.xda-developers.com/devdb/project/dl/?id=20946
Afwall and Kernel Adiutor: unzip the file and install as normal apps
Thank you for making this really solid rom.
I only have one concern, is the reversed fisheye bug present?
stefx98 said:
Thank you for making this really solid rom.
I only have one concern, is the reversed fisheye bug present?
Click to expand...
Click to collapse
I really don't know what it is, as I don't have Z3. Someone else tested it and verified everything worked...
optimumpro said:
I really don't know what it is, as I don't have Z3. Someone else tested it and verified everything worked...
Click to expand...
Click to collapse
I was referring to the camera bug where the photos that you take look bent a little in a circular fashion, but what i could see from the screenshots, it looks like it's not present.
I will give this rom a try as soon as i get home and the effort that was put into it is really extraordinary
stefx98 said:
I was referring to the camera bug where the photos that you take look bent a little in a circular fashion, but what i could see from the screenshots, it looks like it's not present.
I will give this rom a try as soon as i get home and the effort that was put into it is really extraordinary
Click to expand...
Click to collapse
Screenshots are from Z1/z1c, which were not affected with that bug, so they are probably present. But please, try it out and post your feedback, I'm interested, but not able to do it on my device at the moment
Salutes for the OP for supporting Z3c
OMG! This is awesome.I'll flash it as soon as someone confirms no bug in camera.Thanks for your hard work!
ysfernblc said:
OMG! This is awesome.I'll flash it as soon as someone confirms no bug in camera.Thanks for your hard work!
Click to expand...
Click to collapse
Just be "someone"!
fluffi444 said:
Just be "someone"!
Click to expand...
Click to collapse
Of course I want,but I Can't.I'm a student and I use camera so often and I'm so experienced in aosp camera quality.If someone confirms camera quality,I am ready to be a tester user
ysfernblc said:
Of course I want,but I Can't.I'm a student and I use camera so often and I'm so experienced in aosp camera quality.If someone confirms camera quality,I am ready to be a tester user
Click to expand...
Click to collapse
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...
optimumpro said:
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...
Click to expand...
Click to collapse
Here is a photo on a dark and gloomy day...
optimumpro said:
Here is a photo on a dark and gloomy day...
Click to expand...
Click to collapse
Reverse fish eye bug is present if u have unlocked the bootloader....take a pic of something straight...
optimumpro said:
My family member has a Z3c. There is Open Camera there and no fish eye problem whatsoever. I am going to post a few pictures taken by both cameras later...
Click to expand...
Click to collapse
Is your family member using this rom, or anything based on this rom? If so, please take a picture of computer monitor/tv screen/door, something with clear straight lines.
Cirra92 said:
Is your family member using this rom, or anything based on this rom? If so, please take a picture of computer monitor/tv screen/door, something with clear straight lines.
Click to expand...
Click to collapse
Why would I post something taken on another rom? Here is a picture of a computer monitor. Yes, you can see some distortion. Too bad for Z3 and you are not getting a better camera.
optimumpro said:
Why would I post something taken on another rom? Here is a picture of a computer monitor. Yes, you can see some distortion. Too bad for Z3 and you are not getting a better camera.
Click to expand...
Click to collapse
Just asking Yeah just as I expected, that is an issue present for 2 years already, with no clear effort from Sony to release a proper calibration for Z3/Z3C.
I'm really interested in your unofficial TWRP, my phone is encrypted and the official TWRP can't decrypt it.
jacobs0n said:
I'm really interested in your unofficial TWRP, my phone is encrypted and the official TWRP can't decrypt it.
Click to expand...
Click to collapse
It is coming...
@optimumpro
Your work seems very appealing and thank you very much for supporting our beloved z3c!
I have a few questions,
1-Did you specifically choose the word "arise" ?
If Yes, then forget question one
If No, then it would be nice to change name to "Aries" because z3c codename is Aries.
2-Is this rom battery and resource friendly?
If the answers are somehow satisfying i'm thinking of unlocking my bootloader and use your rom.
Thanks in advance and best regards.
Tosgaba said:
@optimumpro
1-Did you specifically choose the word "arise" ?
If Yes, then forget question one
If No, then it would be nice to change name to "Aries" because z3c codename is Aries.
Click to expand...
Click to collapse
It's probably a typo, since the Z1 version is called Jaguar Honami.
From the Z1 thread:
This rom is now about 40% Nougat. One of the side effects: Xposed framework no longer works, but getting rid of it and instead using Privacy Guard is almost as good. Don't forget, Xposed is an exploit, which provides hooks for good and bad things.
Click to expand...
Click to collapse
These security features sound nice.
Does Xposed work on this one? Also, could I flash this and not enable encryption?
Normally, I'd flash it and get the answers myself, but I don't want to unlock my BL if I don't have to.
Sent from my Z3C using Tapatalk
I DONT TAKE ANY WARRANTY WHATSOEVER IN ANY DAMAGE THAT MAY RESULT IN FOLLOWING THIS GUIDE OR USING THE SOFTWARE, ROM IN QUESTION, IN ANY WAY, MAY IT BE AS INTENDED OR NOT. IF YOU HAVE ANY FEELING YOU COULD END UP SUING ME FOR RISKS *YOU ALONE* ACCEPTED TO TAKE, YOU SHOULD IMMEDIATELY STEP BACK AND LEAVE THIS POST, ALL THE OTHERS: BE CAREFUL. YOU WILL LOSE ALL OF THE DATA ON YOUR PHONE'S USERDATA, CACHE AND SYSTEM PARTITION AND THE PHONE WILL BE FACTORY RESET!
STOCK FIRMWARE INSTALLER: https://support.wikomobile.com/maj/Lenny5_OPE_V34.zip <-- if you brick your device.
Hey folks
This is just a brief explanation on how i built this ROM, a complete guide to building the rom may be published at a later point in time. For the Downloads, go to the Links section. The flashing guide will be focused on Lenny 5, but the image may work on other treble-enabled devices, too, so feel free to try and report if your device works with this build.
Build variant: arm-aonly-floss-su-userdebug
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Build description:
I have an old Wiko Lenny 5 around here and wanted to use it as a Kodi Remote etc. at home, but didn't want to use their stock ROM. Also i wanted some freedom in using my device, specifically a rooted device and microg implementation. After trying to build TWRP with no success and the Wiko Build information being massively outdated i then focused on Generic System Images, as Lenny 5 is Treble-enabled. Big thanks to @phhusson for the whole lot of effort he put into building AOSP GSI's (and also clues towards building LineageOS GSI's). After having AOSP9 installed on it for some time, i got bored and tried to compile LineageOS using the patch-and-build system provided on phhusson's github. That worked just great on AOSP9, but failed to build a bootable LOS16 in the first place. So after some recherche, i stumbled across @AndyYan's thread, containing some LineageOS GSI's prebuilt and ready to use. These worked great on my phone, but as stated above, i wanted to customize my LineageOS even further, so i manually patched my build-tree with AndyYan's Lineage-Treble-Patches by doing what this build script does, tested and it booted (i guess it's mainly related to the SELinux Policies not being correctly built for LOS with only phh's treble-patches). So far so good.
Additionally, i implemented the MicroG services by cloning these prebuilts on github to the respective folder in the build tree and before the build executed
Code:
export WITH_SU=true
to include LineageOS's root system in the build. I adapted the treble_arm_afS.mk device config to not use phh's su and the device/lineage/floss.mk file to include
FDroid
FDroidPrivilegedExtension (which is being built from treble sources)
MicroG services (use Play Store Apps)
FakeStore (use Play Store Apps)
MozillaNlpBackend (MicroG Network Location backend)
NominatimNlpBackend (MicroG Network Location backend)
OpenWeatherMapWeatherProvider (for LineageOS Weather Provider)
You are then free to use no Playstore at all or i.e. Yalp Store to download Play Store Apps.
After downloading the Image you may need to Unpack it via 7-zip or another tool.
Flash the device:
To install this custom ROM on the Wiko Lenny 5, in your stock ROM go to Settings->Developer Options->OEM unlock->Enable. Also, in the Developer Options, make sure, ADB Debugging is active and, on prompt, accept debugging connections from your computer.
On your computer, enter Command Prompt and issue the following commands:
Code:
adb reboot bootloader
*wait for device reboot*
fastboot oem unlock [COLOR="Red"]<-- this will factory reset the device!!![/COLOR]
*press vol up on the phone to allow unlocking the bootloader, and wait for the phone to return to fastboot mode*
fastboot erase userdata
fastboot format cache
fastboot format system
fastboot flash system <path-to-the-downloaded-gsi>
*wait for each process to finish*
fastboot reboot
now, wait for the phone to reboot, it should, after some time, show you the usual LineageOS startup screen. Take your time to set up your phone. To make MicroG and FakeStore work properly, you will have to Go to Settings->Apps&Notifications->App-Permissions->Spoof package signature->Menu->Show System Apps and allow FakeStore to spoof Signature. Go to Settings->System->Advanced->MicroG Settings and add your Google account. Activate Device Registration. Then activate Google Cloud Messaging and Google SafetyNet, if you want to take advantage of those services. Inside the UnifiedNlp Settings choose MozillaNlp in the first, and NominatimNlp in the second setting.
Go back and choose "Self check", if required, if required, grant MicroG GmsCore the permission to spoof signature, this should make most of the boxes go "checked". If Phonesky shows errors about signature spoofing, this should normally be gone after a reboot of the phone (given you allowed FakeStore sig spoofing). Disable battery optimization and then reboot the phone.
Check back in MicroG Settings->Self check, if all the boxes have been checked. If not, most mandatory points are self-explanatory.
This Lineage ROM will not allow you to update to a newer version. I cannot guarantee continuous updates, but encourage you to try building LineageOS treble with the way explained above, yourselves. If enough interest is around, i will consider doing updated builds from time to time.
Update:
Today i compiled a recent source tree containing the 5th of October patches. I will try to keep up with updating the Image whenever security fixes are released. The download links below have been updated to the newest version. To update your phone without deleting the data on it (make sure you have adb debugging enabled), you can simply do
Code:
adb reboot bootloader
fastboot flash system <system-image.img>
fastboot reboot
and then give your phone some time to "update". it should boot normally without erasing your data.
Links:
ROM .7z [~430MB]
ROM .img (~1.1GB)
(version was compiled at 19th of October '19, containing the October 5th security fixes.)
Let me know if this works for you, too!
Cheers
ivelischt
*reserved for additions/build guide*
Nice work
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Hanthonious said:
Nice work, I'll test the ROM later or tomorrow, also I like to see some development for this phone, also, It would be very nice to develop a custom recovery for it for better flashing experience and being able to flash gapps.
I have kinda workplace on my PC, I'm still wondering to build my first ROM but I think it will take lot of time.
Click to expand...
Click to collapse
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
ivelischt said:
Thanks. The custom recovery thing is a bit more difficult for treble devices, but i'd be happy to learn more from more experienced people.
I was not able to get TWRP running despite "successful" Custom recovery builds.
The build is quite straightforwards if you have some experience on compiling with linux. But you need around 200400Gigs of free space per build tree (lineage, aosp, ...). The most difficult thing for me was to alter the sources for inclusion of the packages i mentioned above, including microG. to build with opengapps, i expect, you'd use the same approach to include them in the build tree as with microG, just using the other packages and probably slightly customized CUSTOM_PACKAGES config. there is a k300 recovery out in the wild net. so there should be at least *some* possible way to port twrp for the k400, too.
about the time to build the rom: it took me about a day to sync sources and, using 2 cpus at 4gig's of java virtual memory, about 6 hours to compile the first round. after that, only compiling the changes made, it took me about another half an hour to recompile the changes. the editing process is marginal, if you know how to append to/remove from/patch the source files, the lineage4microg and treble rom-builder bash-scripts on github give you a pretty good insight in how to apply patches. also, from the dockerfiles you can get a list of all the dependencies your system needs to build the tree. i used these sorts of "tricks" to ensure my build runs well.
so far from me. i will try to find some free time in the future to put up some guide on how i built the rom as-is.
feel free to report if the rom works on your device!
best regards
edit: 400Gigs is better
Click to expand...
Click to collapse
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Hanthonious said:
The ROM works great but I'd like to see one like this with gapps to install on my device (freaking system image size), I've never used MicroG before and I don't know well how to use it.
Also, if you have the knowledge (I'm pretty sure you know more than me) we can investigate a way to create a TWRP version for K_400
Click to expand...
Click to collapse
Hi Hanthonious
ivelischt said:
If there's interest in other build variants (specifically with microg and floss - fdroid, moz-nlp, openweatherprovider - implemented), ask me, i will do my best.
Click to expand...
Click to collapse
as the microG variant requires some "special sauce", namely the ability to spoof signature as well as other small fixes in the source code, my source tree is a bit different from the "vanilla/gapps" source tree. thus, to build variants not containing microg, you can simply sync the lineage source tree and apply the additional phh treble sources&patches. *edit: next to phh's patches, you will also need AndyYan's patches; you can find information about it in the OP. given, i write a guide (which i still intend to, but this takes some time), the patching step will be explained more clearly* basically, it's one step less than compiling it with microg. at the moment i cannot afford enough disk space to create another work tree, which is why i "can't promise" other build variants, until this issue is gone. which may be tomorrow or in a year. maybe you can find a gapps-version of treble-lineage 16 here in the xda boards. otherwise you will have to wait, or try to build it yourself. also, you might be interested in @AndyYan's lineage version, which is vanilla (no gapps or microg).
i would guess that the system image will not grow excessive just by including opengapps, but i may be wrong. i think that you'd possibly would have to choose a "non-complete" opengapps-package, to make it fit.
to quickly summarize what microg does is, that it spoofs its signature to make your phone think that you have the real Google Services Framework, Google Cloud Messaging, etc. services installed. this makes apps, which depend on these services, work even though you don't really "have" them. additionally, microg establishes an "essential" communication between itself and the real google services to allow you to use google services despite having all their bloatware.
to round this up, you have fakestore which spoofs existence of Google Play Store for those apps and games, which specifically check for GPS's existence (Phonesky app).
i think this should quite generally point out, what microg is for (an api which connects you to google, whilst only handing out information, which is crucial to keep a specific connection alive)
you can then use i.e. Aurora Store to download and update your preferred playstore apps. i tell you this specifically, as i hope that, using it right, microg might be able to give you a "fully stocked" phone experience, whilst keeping most of your data secure and your phone unbloated by google's app-hoard.
if you follow the instructions in the OP on how to fully enable microG, this might be a very handy solution for you, too, so maybe, you want to give it a chance.
to point out my issues with twrp (as far as i can tell using my little experience): twrp is device specific. which means, you need a vendor tree and you need to include it whilst building, so twrp can compile against it. now, treble is a way of excluding your device specific vendor tree from the build altogether (your system image basically doesnt contain the vendor files in a "folder" (/vendor), but in a seperate partition. this partition is "simply" beeing symlinked to from your system partition. this way you will never need to build vendor-specific sources but android builds against standardised "api's" which are being "serviced" by treble-enabled phone's vendor-files (lying at the vendor-partition). this makes building aosp and/or lineage, etc. easier as you can build one variant per architecture, which fits all treble enabled phones of that architecture (arm/64/binder32/64,a/ab,...). this is, very basically said, what is called a HAL (hardware abstraction layer) on a desktop computer.
but at the same time it's much more difficult to find vendor sources for those phones, as there is no more need at all for manufacturers to make these sources publich (as far as i understand it). as a matter of fact, you may not need these vendor sources for modern aosp (8.1+), which really is a grace!! but twrp doesn't seem to work when compiled against treble trees.
i even managed to compile a kernel which is mentioned at the wikogeek site for the lenny 5. i tried to include that kernel when compiling the recovery image but even that did not work out. as i am no experienced programmer (especially not in the high languages), i will not be the person to ask when it comes to finding out what bugs and how to circumvent it.
there is a little light at the end of the tunnel, though. as far as i understand it, treble-phones come with mostly generic kernels, which *could* make it easier to find a way to build a kernel/boot/recovery image in a similar fashion we build the gsi (generic system image) with. additionally, if there is some effort on it, i imagine, that it would be possible to generally modify twrp in a way so it's able to build against treble source trees with missing vendor source. this would enable twrp to run on virtually any phone which is treble enabled and there would be few to no need to port it for each device, specifically. maybe there would then be versions as in the treble gsi's (arm/64,a/b,...) as well as build variants for alternative display sizes etc.
but i wouldn't even know where to start...
i hope i was able to answer your questions. if you decide to stick with the variant in the OP, you should consider downloading and installing the most recent updated build.
best regards
Problems I found in the rom and if there is a way to solve them
Yo,
I wanted to point out the problems I found in the rom and if there is a way to solve
These are the problems I encountered:
1: *THE MOST IMPORTANT*
I can't pass the safetynet test, I researched a lot and I still couldn't solve
When I try to pass the safetynet test on magisk it gives "safetynet API Error"
When I try to do the test with the "SafetyNet Helper Sample" app it gives "SafetyNet request: success
Response validation: fail
Error Msg:
ApException [17]: API: SafetyNet .API is not
available on this device. Connection failed with:
ConnectionResult {statusCode = SERVICE_INVALID,
resolution = null, message = null}
And the "SafetyNet Test" app gives me "fail (Google Play services not available)"
I am aware of the new problem with the safetynet:
(sometimes people are still able to pass the test probably because it is still in maintenance or something)
https :// www . androidpolice . com /2020/03/11/safetynet-improvements-kill-magisk-hide
https :// twitter . com /topjohnwu/status/1237656703929180160
https :// twitter . com /topjohnwu/status/1238514375150850048
https :// twitter . com /topjohnwu/status/1237830555523149824
But even so I should be able to run the test even if it give both negative should run instead of showing those errors
2: The contacts I had on the SIM card and Google account do not appear in the contacts.
So I went on WhatsApp to save the ones I wanted to save, but after a few days and a few restarts the contacts are still saved, but on WhatsApp it shows that they are not saved even appearing in the contacts, to appear again saved on WhatsApp, I have to save them all again
3: Cant login in Clash Royale with google play games account, can i flash the rom and gapps to work or the microg and google play services will create some conflict, is there a way to unninstall microg completly and reflash the rom without microg and flash gapps?
4: Error when login in pokemon go: unable to authenticate, I researched it and it seems to be because the safetynet is negative but I can't even run the test (only after I became aware of the new safetynet problem) even with this new problem I would like to try to run the test to see if it passed since some people still are successfully passing the test
5: in the microg settings in self-check an option is not checked in the box "UnifiedNlp do not have location to test geocoder" I already researched to see if it solved something but I couldn't
edit: I solved it using the "Apple WI-FI" backend instead of the "Déjà Vu Location Service"
BUT NOW ITS GIVE ME AN UNCHECKED BOX
"Network-based location enabled:
you either disabled network-based location
(in system settings) or the system is not
supported"
6: some times in the time widget just appear "loading widget..."
and these are all the problems that I encountered, pls help me
solving these problems, thx!:good:
sorry for some mistakes i translated from portuguese to english with google translator and my knowledge of english
CooperTUGA, thanks for writing. And I want to apologize for letting you wait for so long. In fact, at the moment i do not actively develop this ROM (due to data loss on my virtual machine).
Anyways, i will try to address your issues as good as i can, though i must admit, none of these issues happened on my device.
ad 1: The only thing that comes to my mind is, that something went wrong when registering your device with the Android-ID. (see OP activation instructions). The SafetyNet-API itself should be working, atleast I had no similar issues (after Registering the device it takes some time - around 5 minutes - for Android to reflect the registered state).
But if someone happened to have this issue and knows another solution, you are welcome to tell!
ad 2: Does it help when you try to import the Files from the SIM card? As for Google contacts, it is - from my POV - stringent, that, if the SafetyNet API doesn't work properly, you will be unable to access Google Services (as Google Contacts) which would explain the missing Google Contacts.
ad 3: GApps and microG are two different things. GApps install a version (open-source fork, contains proprietary binaries) of the Official Google Apps, that is, they provide full functionality towards google services, provided you registered your device correctly.
microG is a pure Open Source fork of that, providing but the Framework with which Google Apps can be run. It does not provide Google Apps (like PlayStore etc.) by itself but merely allows them to run, given the configuration is right. This microG-ROM is not built to work with GoogleApps like PlayStore, but instead relies on the microG Services to get Apps, providing same or similar services, running (like Aurora Store etc.). To address your question, it is possible, to change the source code which was used to build this ROM, so it builds with Gapps or completely free of any such services, in fact it would mean to exclude certain patches, but such projects (Treble-enabled) are covered by others and because of above stated reasons i will not be able to provide such in near future.
Short but clear: No, there is no way to "uninstall" microG as it is built together with the ROM and the source used was especially prepared to use microG. But if configured right, you should be able to use your Google-Account in combination with Google-Services-Apps or Games despite using microG.
ad 4: See above. If everything's configured right, you should be able to play Pokemon GO, although i don't use any of these Apps (Clash Royale, Pokemon GO, WhatsApp). I never encountered any Problems along using Google Apps with this ROM.
ad 5: Well, the error says it all. I have Mozilla Location Service installed, which works like a charm. Maybe try this one? You can get it from FDroid, search for "MozillaNlpBackend" and see if it helps to sort this out? This works for me, after all.
ad6: as this is very unspecific, i cannot really tell what's the problem, but i would guess it has to do with the SafetyNet API not doing what it should or even the Location Backend not reporting position in time...
Did you clean your cache and data partitions while installing this ROM? I really am not sure what could create the behaviour you describe. Maybe there was a change in the SafetyNet/Device Certification process since this ROM-Build, maybe theres someone in those boards who could answer this, but i unfortunately can't...
I'm sorry that i cant give you more positive news, but hopefully it helps you in orienting what some common problems could be caused by.
Let me know about your success in trying to get the ROM working.
Best regards and greetings to portugal!
ivelischt
additionally: if you are interested in porting the Lineage Source for GSI/Lenny 5, you might be interested in this Thread: https://forum.xda-developers.com/android/help/how-to-root-wiko-lenny-5-t3819469
specifically, i wrote a guide there on how to build Android/Lineage Source for Treble devices. Maybe this helps you in getting your own build environment, enabling you to build to your disguise.
Images are not available anymore. Anyone here?
I've created this thread to discuss LOS19. Hopefully, one of the maintainers will create a proper thread.
Downloads
Official: https://download.lineageos.org/sunfish
Installation
https://wiki.lineageos.org/devices/sunfish/install
Upgrading from 18.1
https://wiki.lineageos.org/devices/sunfish/upgrade
Updating
https://wiki.lineageos.org/devices/sunfish/update
If you find their work useful, don't forget to support all their work.
https://paypal.me/LineageOS
https://patreon.com/LineageOS
Visual Voicemail Error
I'd like to thank @razorloves for working on a fix to the VVM problem. Razorloves has already provided the work to the Android project. Let's hope all goes well. The work is greatly appreciated.
Razorloves created a new "Dialer.apk" for LOS19. The LOS18 version is already being shared in that thread.
I've attached "Dialer-19.1.zip", which contains the file razorloves created with the fix. There's also a sourceforge download link. I don't know if that would be better.
To try this fix....
Enable USB debugging in your phone.
Enable ADB root in your phone.
Use these adb commands....
'adb root'
'adb remount'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is from 2008
'adb push Dialer.apk product/priv-app/Dialer/Dialer.apk'
'adb shell ls -l product/priv-app/Dialer'
--you should see the Dialer.apk file is now from 2022
reboot your phone.
Hopefully, the fix will make it through AOSP & onto the official LOS19 ROM soon.
Got notice that the VVM issue has been closed. The Dialer app will be fixed in next build.
So, if you're on LOS19, you can just wait for the June 2 build.
Big thanks to @razorloves for the work that made it happen
EDIT: Sorry! Deleted this post because my lack of knowledge made it appear like I was insultingly impatient. Many thanks to all the people who make LOS available for us dunces.
Sincere apologies to anyone whom I might have offended.
Since I switched from LOS18 to LOS19, I'm having a couple of issues.
This is NOT a complaint. I'm simply sharing to see if others are also experiencing these.
I updated per the LOS webpage instructions (ie. not a clean install). Phone has no custom-kernel,
no GApps, and no Magisk. Build is June 9th (latest).
1) Calendar notifications.
I'm not getting calendar notifications. This was working fine in LOS18. I'd get a notification at the defined time before an event. Sometimes, while I'm working on the Calendar, I get old notifications (as in events from days ago). Today, while testing, I got a "Calendar keeps stopping" popup.
My calendar data is offline. I deleted my calendar and created a new one. Nothing changed.
2) Charging.
When I plug into my PC, I get the sound acknowledgment from my phone. The Battery screen tells
me "Charging". However, it is not charging.
EDIT: As always, I'm a day late and a dollar short.
This is a known LOS19 issue (with USB) that was being processed. They have a fix in place that we should see next build (June 16th). Thanks (again) to the LOS team for their time/effort!
Is anyone else having the Calendar issue? If you're not, did you update to LOS19? Or, did you perform a "first time" install (wipe data & such)?
Thanks for your time.
@mangokm40 How is the battery life on LOS 19?
AkumDX said:
@mangokm40 How is the battery life on LOS 19?
Click to expand...
Click to collapse
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
mangokm40 said:
I've not noticed any difference from LOS18. I'm very happy with the battery life.
I cannot compare to stock, as I've never used it.
Click to expand...
Click to collapse
Oh okay ... Haven't used LOS 18 for few months now... Currently on 13 beta, battery isn't that great so thought of switching
4a LineageOS 19.1 Update 2022-06-16 - Security Bump
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-09 + lineage-19.1-20220609-recovery-sunfish to build 2022-06-16. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 12 minutes.
There are a bunch of changes as you can see here:
I tested the USB fix. It's not working for me. Thanks to user razorloves. I toggled the "Always allow USB connections" setting in "Settings->Privacy->Trust". My phone is now charging, even when locked.
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "June 5, 2022".
The Vendor security patch level (just below) is also "June 5, 2022".
The Build number at the bottom is now "SQ3A.220605.009.A1".
The Baseband updated to "g7150-00090-220406-B-8411773".
See Android Security Bulletin - June 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220616" and active slot 'a'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
lefteyecat said:
Are the quick tiles the same as the vanilla rom? (Big and Missing a wifi)?
Click to expand...
Click to collapse
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
mangokm40 said:
This is what it looks like. The red arrow points to the 'edit' button.
If you don't see the 'WiFi' & 'Mobile Data' buttons, you can edit which tiles show up. I got rid of the new 'Internet' one.
Click to expand...
Click to collapse
Thanks,looks like i have to hold out on 18 for as long as i can.
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
Nope.
creeve4 said:
Does LOS recovery allow for full system backup/restoration?
I am running stock Android 12 (rooted with a lot of customization that I don't want to setup again if I don't like LOS).
Click to expand...
Click to collapse
i use swiftbackup and nova launcher, its not as good as twrp ( still need log in verifications) but does restore all apps and screen positions , best and easiest solution i have found so far. Root reguired.
Is anyone running the latest version of LOS19 (lineage-19.1-20220623-nightly-sunfish-signed.zip) ?
I'm asking because there's this VVM issue open for a OnePlus7, running LOS18.
VVM is working for my 0616 build of LOS19, and the issue mentions it broke when they installed their device's 0619 build. Thus, I looked at the list of changes for our device here.
There are 5 changes to "android_packages_apps_Contacts".
There are also many changes to "android_vendor_lineage" that mention APN changes for various carriers.
I'm wondering if anyone is running the 0623 build & has VVM working.
Thanks.
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
mangokm40 said:
Missed Calendar notifications & Trebuchet's 'Hidden apps'
1)
I found this way to fix my Calendar notifications in LOS19. I'm posting it here, in case someone else was having the same problem.
2)
If you've missed 'Hidden & protected apps' since your move to LOS19, there appear to be good news. The 'Changes to be included in next build' includes 'Trebuchet: implement hidden & protected apps'. WooHoo!
Click to expand...
Click to collapse
Thank you mangokm40 for all the infos, tips, tricks and hints you post! Really appreciate it!
4a LineageOS 19.1 Update 2022-07-14 - Security Bump, Calendar Update, Hidden Apps
Using the built-in Updater, I OTA-updated Pixel 4a (Google Ed) LineageOS 19.1 sunfish build 2022-06-16 + lineage-19.1-20220616-recovery-sunfish to build 2022-07-14. I have no GApps, no custom-kernel, and Magisk is not installed. Everything went smoothly. I used 'Caffeine' & the "install" part took 11 minutes.
There are a bunch of changes as you can see here.
The ones that I noticed are:
1) Security Bump - see details below.
2) Calendar Update - the update to version 1.0.30 didn't clear the search crash problem. The battery use is now forced to "Unrestricted", to allow all notifications to appear on time.
3) Hidden & Protected Apps - It remembered all my hidden apps from LOS18 & they were hidden without needing any new input from me. WooHoo!
After the reboot, I went to Settings->About phone->"Android version". The "Android security update" now shows "July 5, 2022".
The Vendor security patch level (just below) is also "July 5, 2022".
The Build number at the bottom is now "SQ3A.220705.003.A1".
The Baseband remains as "g7150-00090-220406-B-8411773".
See Android Security Bulletin - July 2022 for details about the security fixes.
I rebooted to recovery to verify that it was also updated. It now shows version "20220714" and active slot 'b'.
Thank you to the Lineage Team, PeterCxy, cdesai, & mikeioannina (listed as maintainers) for their work.
Hello, can someone help me with the following question?
* Does Google Pay / banking apps work good with this rom? I suppose that magisk is needed along with some safetynet fix?
Thanks!
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device, while adding a lot of eye-candy (ie features).
Features:
https://github.com/crdroidandroid
Screenshots
https://crdroid.net/#gallery
Flashing Instructions:
See the post: https://forum.xda-developers.com/t/...crdroid-v9-5-with-gapps.4593649/post-88663897
Pre-installation:
Download the ROM
download the May 2023 stock firmware (*NEW STEP*)
Backup any important data
Have an exit strategy if it goes wrong
GApps are included
Magisk 25.0 or newer for root (after first boot) - NOTE: v26.1 is the currently latest stable build.
NB: The FASTBOOT release method i use is not that well documented. But, iuts basuically what occurs from flashing google supplied firmware releases, so it must be at least half good. It's a few more build steps & time, but it also makes it far easier for me to flash ( and for you). Not having a working TWRP, I dont understand (apart from the extra steps. time & storage) why all ROMs for P4A are not released like this.
Update installation:
Leave out the -w from the command. Its hard to miss
Sources:
ROM: https://github.com/crdroidandroid
Device: https://github.com/LineageOS/android_device_google_sunfish
Kernel: https://github.com/crdroidandroid/android_kernel_google_msm-4.14
Vendor: https://github.com/TheMuppets/proprietary_vendor_google_sunfish
Gapps: https://github.com/BlissRoms/platform_vendor_bliss
Download:
ROM crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT.zip MD5: 575B8DEDB8371839AD38888BBB4F820E
BOOT IMAGE crDroidAndroid-13.0-20230619-sunfish-v9.5-UNOFFICIAL-DiamondJohn-FASTBOOT-boot.img MD5: A9BD232C4773E4B6C5A5BA19E2C1DC68
Changelog: see attached in the release post listed above as flashing instructions
Known issues:
You tell the rest of us!
Visit official website @ crDroid.net https://crdroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help the crDroid team pay server costs
OR
Donate to help others
The initial "out of the box" builds of crDroid 9.5 (A13) kept failing at the veeeeery last stage, where it would try to build a flashable image, and would fail the check that it would fit on the devices partitions.
I then built a non-googled version (by accident) and that succeeded. Obviously because the google apps installed by default, by crDroid, were taking too much space.
I spent HOURS trying to find where in crDroid the list of which google apps are installed, but failed. I am sure if someone pointed it out to me, I would slap my forehead, and say "obviously"!. And that is one of the difficulties in building crDroid. Other ROMs have telegram channels where one can speak directly with the ROM devs to ask questions. All I could find for crDroid was a user channel.
So, to get a build with google installed, I set it up to build crDroid without google, and added in the code from Bliss (a ROM I have already built, and they have addressed the size issue specifically for pixel devices. inc sunfish) to add google services & apps. That worked! I also noticed that there is an official release here for another device, on XDA, that also has no google...
The google apps installed by what I have done are actually pretty comprehensive. Below is a list:
GoogleExtShared
GooglePrintRecommendationService
DocumentsUIGoogle
GooglePackageInstaller
TagGoogle
CalculatorGooglePrebuilt
CalendarGooglePrebuilt
Chrome-Stub
DevicePolicyPrebuilt
GoogleContacts
GoogleTTS
LatinIMEGooglePrebuilt
LocationHistoryPrebuilt
Maps
MarkupGoogle
ModuleMetadataGoogle
Photos
PixelThemesStub
PixelThemesStub2022_and_newer
PrebuiltDeskClockGoogle
PrebuiltGmail
SoundPickerPrebuilt
TrichromeLibrary-Stub
WebViewGoogle-Stub
talkback
AdaptiveVPNPrebuilt
AndroidAutoStubPrebuilt
ConfigUpdater
DeviceIntelligenceNetworkPrebuilt
DevicePersonalizationPrebuiltPixel2022
FilesPrebuilt
GoogleDialer
GoogleOneTimeInitializer
GoogleRestorePrebuilt
PartnerSetupPrebuilt
Phonesky
PrebuiltBugle
PrebuiltGmsCore
PrebuiltGmsCoreSc_AdsDynamite
PrebuiltGmsCoreSc_CronetDynamite
PrebuiltGmsCoreSc_DynamiteLoader
PrebuiltGmsCoreSc_DynamiteModulesA
PrebuiltGmsCoreSc_DynamiteModulesC
PrebuiltGmsCoreSc_GoogleCertificates
PrebuiltGmsCoreSc_MapsDynamite
PrebuiltGmsCoreSc_MeasurementDynamite
AndroidPlatformServices
SafetyHubPrebuilt
ScribePrebuilt
SecurityHubPrebuilt
SettingsIntelligenceGooglePrebuilt
SetupWizardPrebuilt
TurboPrebuilt
Velvet
WellbeingPrebuilt
EmergencyInfoGoogleNoUi
Flipendo
GoogleServicesFramework
PixelSetupWizard
QuickAccessWallet
StorageManagerGoogle
TurboAdapter
WallpaperPickerGoogleRelease
com.google.android.dialer.support
Personally, im a little chuffed I got it working. I would also like to say, the instrctions for building crDroid on trheir guthuib page are really lacking. I had to use what I learnt from other ROMs (and their instructions) to even get started.
AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.
MY future plans for this ROM.
Firstly, this is UNOFFICIAL. I am not associated with crDroid in anyway. Any of you could do the same as what I have done.
If there is a bug, 1 of three things could happen.
1. Its something you have added to the ROM. Its now up to you to fix.
2. If the bug is sunfish specific, but I dont get bothered by the same bug, Meh. Chances are I wont fix it
3. Its a crDroid or LOS bug, I will direct you to post the bug with crDroid / LOS.
By all means, post the bug here to let others & me know and maybe help you, but do not get perturbed If I dont start spending time coding to fix it.
Changes to the ROM I foresee right now, since it is a personal share of the ROM I plan to run on my daily, primarily for ME, are:
The QS tile headers are a Japanese anime theme. I will probably replace those with some abstract textures
The default wallpaper which appears on the lockscreen before you unlock, although is better than others, I will change to another space theme to match my Live Wallpaper
The theming colours are missing Teal!?!? I will probably replace an existing colour.
Im thinking *maybe* the boot animation to the old nexus prime prime one (see below)
maybe others I haven't noticed thus far, but I dont think anything too crazy or offensive.
NO GUARANNTEE, but since crDroid add features very often (eg brightness slider styles since the official v9.5 release), I will probably go with close to monthly builds to keep up.
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.
DiamondJohn said:
Most of your questions are answered explicitly by my post above yours.
As for minimal GApps, I also generally previously flashed min GApps, so as to exclude anything I can get from the playstore. I actually read the list of included GApps after I had started the build (over 150,000 steps) and thought about cutting it back, and restarting. However, It is simple to Force_Close-Clear-Freeze-Hide any app that you dont want, which practically makes it as if it was never installed. If your rooted, yu can use my app TeMeFI to do it. Thats how I do it, including i5tens such as MatLab & Eleven ( as I use Vinyl from the playstore) and Viper instead of MusicFX. Everyone has their own preferences,
I am NOT going to build & release multiple version with different levels of GApps.
Click to expand...
Click to collapse
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.
chozendroid said:
Firstly, thanks so much for continuing to support this device. I really love the device itself and definitely welcome any custom ROM support.
Click to expand...
Click to collapse
And to state the obvious, I LOVE this device and build custom ROMs for it, for me to use.
A few weeks ago I watched a number of videos about how this device is still a good choice today. So we two are not the only ones.
https://www.youtube.com/results?search_query=pixel+4a+2023
chozendroid said:
Are you planning to make your vanilla builds available by chance? I kinda like the idea of starting with a vanilla ROM and installing only a minimal Gapps package if the option is available
Click to expand...
Click to collapse
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever? I tried adding Google services via a Magsk module and it wasnt great. The keyboard never popped up when I entered a text field, and I couldnt install the updated GBoard. I had to install the M$ keyboard. AND that GApps module obviously requires root/Magisk.
I personally would of assumed "VANILLA" android (ie ASOP / Pixel Device) includes Google Services, but meh, what do I know.
chozendroid said:
I appreciate the response. It is your build, so I fully respect your decisions. I personally don't root (Google Pay issues and intermittent errors with specific banking apps), so I'll just have to stick with the basic approach of hiding whatever apps I don't use. Definitely look forward to giving it a try over the weekend when I have some downtime.
Click to expand...
Click to collapse
As for Force_Close-Clear-Freeze-Hide, im pretty sure you don't have to root the device.
And maybe, dont forget the link I posted to the other android file host build. Maybe he has built with less google stuff. But, I think he built before the brightness slider themes were added and who knows when the next build will occur. He has no contact details. I would like to know how he got GApps to be included.
I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.
DiamondJohn said:
Actually, on the other OFFICAL release of crDroid for another device, he called his de-googled build "VANILLA". Were you asking about a ROM with any google whatsoever?
Click to expand...
Click to collapse
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb
prog19 said:
I dont know anything about development (but been using custom roms since the nexus 4 days), but in my mi 9 se. I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload). As i am new with this P4A i wish to know why a similar aproach doesn't work with our device.
Click to expand...
Click to collapse
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
prog19 said:
.... I flash the build using the provided recovery (by means of adb sideload) then flash gapps (also by adb sideload)....
Click to expand...
Click to collapse
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.
chozendroid said:
This is exactly what I was asking about actually. A de-googled/vanilla build which would allow me to just sideload minimal Gapps via adb
Click to expand...
Click to collapse
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.
DiamondJohn said:
Again, are you 100% certain you can sideload GApps onto an existing ROM on the Pixel 4A? read above. If you can, then that's what I will build from now on. Much easier for me.
Click to expand...
Click to collapse
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.
DiamondJohn said:
DOPO aver creato quanto sopra, ho scoperto che qualcun altro ha effettivamente creato crDroid con googl;e installato e l'ha pubblicato su Android File Host. Non ho testato la loro build, ma sono passati 10 giorni e ci sono stati commit extra da quella build. In particolare gli stili del dispositivo di scorrimento della luminosità.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
Penso che qualche anno fa mi sono imbattuto in questi caricamenti AFH di questo ragazzo quando avevo un Nexus 5, e non sono riuscito a trovarlo comunque per contattarlo allora.
Click to expand...
Click to collapse
DiamondJohn said:
AFTER I built the above, I founmd that someone else has actually built crDroid with googl;e installed, and posted it up on Android File Host. I havent tested their build, but it was 10 days ago now, and there have been extra commits since that build. Specifically the brightness slider styles.
crDroidAndroid-13.0-20230525-sunfish-v9.5.zip: https://androidfilehost.com/?fid=10620683726822056190
I think a few years ago I came across this guys AFH uploads when I had a Nexus 5, and I could not find anyway to contact him back then.
Click to expand...
Click to collapse
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it
DiamondJohn said:
Using ADB sideload, you HAVE to be on a specific version of a ROM; especially for the first flash or when switching between ROMs. This fastboot method first flashes any prerequisites, reboots, then completes the flash. All in a single step, no confusion in getting the correct starting point. To me its a LOT better, but more work for the DEV (ie ME). If you have flashed Bliss, then you would know you actually have to first flash an older fastboot file, and then install the latest version via sideload.
My method is a single step EVERY time I do a release. Including for those people who install for the first time, regardless of what ROM/firmware they are coming from. The only difference will be the -w parameter for the first time. They onlyt have to insure they are running a valid platform-tools (ie ADB/fastboot)
So, the ROM sideload way works for P4A, but this way is easier to install. In building, I first get the sideload file, but then have to run a few more steps and build time to get the sideload file out, and then a few more steps. ie its more work for me. But I think better for flashing; including for me. When I first flash the official Bliss, I made a mistake and the ROM was not working correctly
Im not 100% certain, but I do not think you can add/overlay GApps by sideloading a GApps file over a P4A ROM. Like on older devices using TWRP. Or am I wrong? If Im wrong, then I will build without GApps and people can choose their GApps level/coverage. Easier for me, and better for others.
Click to expand...
Click to collapse
Thank you for the very detailed answer
Marcia8246 said:
Hi! I have installed this github Rom, but have few little bugs, your rom is different? I want try it
Click to expand...
Click to collapse
Yes. I already explained the difference, in addition to not knowing any details that I have also doc'd in the OP.
To be clear, I know nothing more about this ROM than you. Actually, even less, as you have flashed it.
chozendroid said:
I'm not sure because I haven't seen any P4A ROMs based on Android 13 without built-in Gapps thus far. But like @prog19 mentioned, this is how it works for other devices. That's what I do with my OP6T, but I know each device has it's nuances, hence the reason I asked. It's not a necessity. I just find that it creates a lighter initial installation which is a matter of personal preference.
Click to expand...
Click to collapse
As for working for "other devices", thats one of the changes in Googles newer devices. But the same would go for the Pixel 4A 5G, the 5, 6 & 7 series pixel devices. Try and find a single sideloadable ZIP that makes an incremental change on one of these devices, to one of the system partitions. And its not just google. Thats one of the reasons to use Magisk modules, they allow a partial targeted change to a RO partitions.
I think there is an official A13 GrapheneOS ROM for the Pixel 4A, that has no GApps.
FYI: Im kicking off a kinda test build, with a smaller google footprint, and 11 modified header QS images.
Also ONLY on my installed ROM on personal device (NOT in the ROM). I have debloated Aperture (the Camera)l, Eleven & Audio FX and installed Google Camera (It has "Night Vision" which I dont know if its better, but I like the option), Vinyl as my music player, and ViperFX as my Eq. Viper eq's the sound for the player, but not from some other apps.
See below post for how:
[OFFICIAL] BlissRom 16 [Typhoon] [sunfish][Android 13]
BlissRoms comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience. Our focus...
forum.xda-developers.com
The RisingOS actually has a good Music player, that is updated on F-Droid, I would probably go with that, if I remembered the name, and wasn't committed with boot scripts to Vinyl. Since its part of a ROM, probably get more attention.
I also liked the calculator on RisingOS. I'll check if someone can get me the APK and it works, and the name of the Music player.
FYI: I did a test build over last night, but three of my changes didn't go as expected, so I will need to fix them and do another build before release. DOH!
The boot animation frame rate is WAAAaay to fast
One of my new QS Tile headers isnt displaying. Dont get it as it is literally the same as another one just a different shade/colour pallet
The default wallpaper remained unchanged.
I did note that there was a small flurry of changes (bug fixes, not new features)
One of the new headers is interesting, but I dont think I will personally use it (ironically I would use the one that failed...)
Its basically a view of the circuit board from the back. Kind-a simulates you are actually dragging the screen off to reveal the circuits underneath. If only I could find a photo of the correct side of the main board and not from the back. Anyone?
Another FYI, I installed ReVAnced as root and it went without a hitch, All I did was:
Downloaded & installed the revanced manager APK
Started it up to see which version of You Tube it expected
Source the correct version of youtube from APK Mirror OR APK pure etc etc etc
Installed the base correct & expected Youtube
Ran ReVanced Manager. Selected it to apply the "Default Patching" BUT turned off the MicroG support
Ran the patching
Installed it as root
rebooted
Detach youtube from playstore
Enjoy!
forgot step 8.5 for ReVanced install, Detached it from the playstore
also realised the reason / where I failed on the three points of the ROM build issues.