crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
Known issues:
- Same bugs as Lineage OS 15.1.
- HW Issue is still present.
- You tell us!
Downloads:
Latest 6/13 build for Flounder is here: https://www.androidfilehost.com/?fid=6006931924117895279
ROM Download folder is here: https://www.androidfilehost.com/?w=files&flid=295526
Sources:
Device Tree: https://github.com/LineageOS/android_device_htc_flounder/tree/lineage-15.1
Vendor Tree #1: https://github.com/TheMuppets/proprietary_vendor_htc/tree/lineage-15.1
Kernel Tree#1: https://github.com/LineageOS/android_kernel_google_msm/tree/lineage-15.1
Kernel Tree#1: https://github.com/LineageOS/android_kernel_htc_flounder/tree/lineage-15.1
Thanks to:
- @ripee (for him helping me build these awesome ROMS for y'all!)
- @followmsi (for his wonderful help that he always gives me!)
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
crDroid G+ community
reserved just in case
So, my impressions with the ROM so far
The bootanimation is not fitted to the screen
It force encrypt my data in spite of installing magisk, tried to format and reinstall the ROM again just for it to encrypt the second time.
Live display doesn't work, but I think it is the hardware's fault because live display also doesn't work with every other Oreo roms.
One random shutdown out of the blue.
The performance is heavily hindered by the encryption but other than that I see no major bugs
ChristopherXI said:
So, my impressions with the ROM so far
The bootanimation is not fitted to the screen
It force encrypt my data in spite of installing magisk, tried to format and reinstall the ROM again just for it to encrypt the second time.
Live display doesn't work, but I think it is the hardware's fault because live display also doesn't work with every other Oreo roms.
One random shutdown out of the blue.
The performance is heavily hindered by the encryption but other than that I see no major bugs
Click to expand...
Click to collapse
Flashing just magisk won't remove encryption do these steps properly:
Wipe everything except internal storage
Flash the ROM
Flash this zip right after the ROM to disable force encryption
https://www.androidfilehost.com/?fid=6006931924117895653
you have to do this with every ROM you flash if you don't then your device becomes force encrypted again
Flash latest opengapps arm64 8.1 nano and after that flash latest magisk 19.3
Now were not done yet you now have to click on wipe in twrp and click format data type yes to confirm (Note this remove all your files in internal storage but if you don't do this then your device stays force encrypted you have to do this you have no choice so copy your files to your computer if you can you can copy them back to the device later.
And if you think there's another way to do it there's not I owned this device and its a pain but google loves to screw up there nexus 9 with force encryption and this is how I fixed the performance issues.
Yes live display won't work and its best to disable it its a los15.1 bug
That's it boot into the ROM and encryption should be removed
Sometime soon I will provide another boot animation in next build that works better but I will upload another one for you tomorrow just in case
Cheers
JT1510365 said:
Flashing just magisk won't remove encryption do these steps properly:
Wipe everything except internal storage
Flash the ROM
Flash this zip right after the ROM to disable force encryption
https://www.androidfilehost.com/?fid=6006931924117895653
you have to do this with every ROM you flash if you don't then your device becomes force encrypted again
Flash latest opengapps arm64 8.1 nano and after that flash latest magisk 19.3
Now were not done yet you now have to click on wipe in twrp and click format data type yes to confirm (Note this remove all your files in internal storage but if you don't do this then your device stays force encrypted you have to do this you have no choice so copy your files to your computer if you can you can copy them back to the device later.
And if you think there's another way to do it there's not I owned this device and its a pain but google loves to screw up there nexus 9 with force encryption and this is how I fixed the performance issues.
Yes live display won't work and its best to disable it its a los15.1 bug
That's it boot into the ROM and encryption should be removed
Why did you remove your thanks on my thread?
For the meantime I will provide another boot animation in next build that works better but I will upload another for you just in case
Cheers
Click to expand...
Click to collapse
Uhhh didn't you know that flashing Magisk disables force encryption?
Every other rom even oreo ones only needed a magisk flash and boom, encryption gone. Ofc i flash magisk right after installing the rom and not booting into the system, giving it no chance to encrypt
ChristopherXI said:
Uhhh didn't you know that flashing Magisk disables force encryption?
Every other rom even oreo ones only needed a magisk flash and boom, encryption gone. Ofc i flash magisk right after installing the rom and not booting into the system, giving it no chance to encrypt
Click to expand...
Click to collapse
just use the zip i provided i flash magisk on any rom on my nexus 9 and my device is still force encrypted you have to use that zip i provided you shouldnt have problems with encrpytion crdroid uses the same sources as lineage
ChristopherXI said:
Uhhh didn't you know that flashing Magisk disables force encryption?
Every other rom even oreo ones only needed a magisk flash and boom, encryption gone. Ofc i flash magisk right after installing the rom and not booting into the system, giving it no chance to encrypt
Click to expand...
Click to collapse
Uhhh didn't you know the the flags to remove forced encryption need to be set. Flash the zip in previous instructions before magisk and it will remove forced encryption. Why is it so hard to follow instructions?
RTFM
madbat99 said:
Uhhh didn't you know the the flags to remove forced encryption need to be set. Flash the zip in previous instructions before magisk and it will remove forced encryption. Why is it so hard to follow instructions?
RTFM
Click to expand...
Click to collapse
Uhhh Every other rom i've installed on my tab, even other oreo ones only needed a magisk flash and force encryption is removed, this one needs a separate one to remove the encryption flags is new to me, which is weird.
Hi JT, do you think the hw decoding acceleration is a no way on Oreo?
mom4751 said:
Hi JT, do you think the hw decoding acceleration is a no way on Oreo?
Click to expand...
Click to collapse
It seems the developers have stopped working on this tablet because of the hw decoding acceleration issues. I believe its just too hard to fix which is a shame because I wish we would have pie for this tablet but pie has even more issues so I don't think it will ever get fixed.
Just flashed on my nexus 9 all good followed you instructions. Shame development is near dead shame no android 9 [emoji22][emoji106] thanks
Sent from my ELE-L09 using Tapatalk
Is this his feature such a super slow charge? I updated it to 8.1.1, crDroid 4.7.2. Everything works fine, but with any use of the charging unit, it does not show charging speed
more than 500 mA / 4.3V, it will be so charged for days ..
How is this ROM running?
I am on 7.1.2 and all I am looking for is better performance in Clash of Clans.
Happy Cthulhugiving! This is probably a dumb question, but I have been lurking in these forums for years now on stock rom which shipped on the tablet. What is downside of having no HW acceleration with these roms? Does that mean that I can't play any games or watch full screen video? I'm sure this has been explained in other places, but if I flash this rom, what would be the negative effects over keeping stock rom?
granduke said:
How is this ROM running?
I am on 7.1.2 and all I am looking for is better performance in Clash of Clans.
Click to expand...
Click to collapse
7.1.2 is prob best stable you will get all of the 8 roms have issues with playing Netflix etc I went back to stock as all I purely use mine for is watching movies
Sent from my VOG-L09 using Tapatalk
is development not being maintained.what has happened. Has developer moved on or what. if so will go back to lineage 14.1.
mrk2815 said:
is development not being maintained.what has happened. Has developer moved on or what. if so will go back to lineage 14.1.
Click to expand...
Click to collapse
I have stopped making oreo roms for the nexus 9 because of the hw acceleration issues and the fact that development with oreo based roms and devs have stopped working and trying to find a fix to make these oreo roms stable. The oreo roms for the N9 aren't stable enough to be daily drivers but they are cool to play around with for a little bit. Who knows maybe someone will come around at some point and want to work on trying to find a fix. But really there is only a few people making roms right now. I am working on a couple nougat roms for this tablet so stay tuned for them but right now i am having building issues but i will keep you posted.
If you want to have your tablet most up to date these lineage 14.1 builds for flounder built by milaq are a good choice:
https://milaq.net/downloads/android/flounder/cm-14.1/
granduke said:
How is this ROM running?
I am on 7.1.2 and all I am looking for is better performance in Clash of Clans.
Click to expand...
Click to collapse
not very good it was just a test build to play around with you are better off flashing nougat or marshmallow roms
its working rally well for me.i just played a bunch of video ccontent and for me it s much smoothe then android 7 was and had more crashes with android 7 with any rom compared to heis one .so i gues i will just use this rom.i am running netflix, pluto tv, amazon prime videos, and youtube.all works with out no hickups.i am using youtube vanced an older version of the youtube.using net flix 6.2, and pluto tv, as well as redflix anda few other video content apps an all works really well on teh device.so i dont know what the issue is all about.i even have magisk manger installe with these hidden from root as well.
if you have plans to update your oreo rom.now hw video is working.look at this thread.
https://forum.xda-developers.com/ne...xus-9-wifi-t4051433/post81772595#post81772595
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"
}
LineageOS is a free and open-source operating system for smartphones and tablet computers, based on the Android mobile platform.
This is an unofficial build of LineageOS for the Pixel 2 (walleye). I always liked Lineage (and its predecessor CyanogenMOD) as well as the Google line of phones. Unfortunately having a Google Pixel phone isn't certainty for a lot of custom ROMS anymore, so that's why I decided to compile my own version. It's been quite challeging, but I think I finally have a build that is good enough to share.
About
This ROM is is always built straight from the LineageOS sources found on https://github.com/lineageos. There are only 3 changes in order to get this build:
The binaries for this ROM come from AICP
GApps are compiled with the ROM from MindTheGapps including the Pixel specific bits for unlimited photo upload for instance
Disabled Android Verity Boot (AVB), so we don't get the security warning when booting
I am not a developer, I only build this ROM and it reflects the the current status. If there are any things missing or not working I suggest to contact the LineageOS team, they are the real geniuses here and deserve all the credits. I will try to keep this ROM updated on a regular basis.
First Installation
Installing the ROM can be a little hard, especially the first install. Upgrades will be relatively easy though. This first setup is only needed when coming from a different ROM then this. I can't support you if you did't follow this first installation. Be warned it will wipe your user data in the process
In order to get the initial setup and also to use the same vendor partition as the ROM you have to install the latest stock Pixel 2 image from Google found here. More info on unlocking your phone and installing the latest Pixel image can be found in the excellent post by @nathanchance found here. The bestway to flash a stock ROM in my opinion is @Deuces' script found here. The benefit of this is that it'll flash the image to both slots, so they are both on the latest build, including the bootloader and radio. All instructions for using the script are inside the forum. After flashing the image make sure you reboot at least once (no need to set it up now though).
Place the ROM and optionally the TWRP zip and root from (Magisk or from LineageOS (not tested) on the phone and reboot to recovery by using the command line (fastboot boot twrp.img)
Wipe 'data' and 'Dalvik / Art Cache' from TWRP - Wipe - Advanced Wipe. Optionally you should also delete the Android folder on your internal storage through the TWRP File Manager
Flash the ROM and optionally the TWRP zip and reboot the phone
Upgrades to new version
After the hard initial work to get the ROM installed it's going to be easy for upgrades to new versions.
Download the new ROM and reboot of flash to TWRP
Flash the new ROM and optionally TWRP. If you want to flash another kernel or a root solution you will have to reboot you phone, so it switches slots and let it boot normally. Then go back to recovery and flash in this order: TWRP - kernel - Magisk and reboot
After a monthly update from Google and only when LineageOS also adapted to the latest monthly sources (I will tell you this) you will have to do an extra step:
Download the latest Lineage OS ROM and place it on the internal storage
Download the latest image from the Google Factory Images site and run Deuces' script. No need to wipe your data!
After the script finishes it automatically boots into the bootloader. From here fastboot into TWRP and flash the previously downloaded new ROM, optionally followed by TWRP.
Optionally, after a reboot you can flash Magisk and/or another kernel.
Not working
Substratum
Use Powerbutton for flashlight when Ambient Display is set
Active Edge
Now playing
Downloads
I'm not maintaining this project anymore, download link has been removed.
Happy flashing
Miraculous... Will flash soon. Thank you for keeping Pixel 2 relevant.
Is link not posted yet?
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
Why would it be closed?
JCBiznatch said:
I want to thank you for posting. But, I get the feeling this will just be closed as well really soon. Hope this sticks around, because XDA is not what it use to be, at all!
Click to expand...
Click to collapse
I completely agree...
Any chance for an MD5
jascolli said:
Any chance for an MD5
Click to expand...
Click to collapse
Added in the same folder:
MD5: a28cd4f3cabe627fbe99cbe1485cba3f
TCUofficial said:
Why would it be closed?
Click to expand...
Click to collapse
I don't have a clue. It just seems that anyone who posts a ROM gets the thread closed. It's almost as if they don't want walleye to have any development.
Just check this forum out compared to the pixel XL 2 forum.
Thanks very much for sharing this. I've got it installed and it's running fantastic.
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
razrlover said:
Everyone who has had a rom thread has closed the thread for different reasons, time, family, frustration or lack of support etc...
I see don't see why we should be negative and assumee the same is the case with this build. Every rom thread has produced better and more stable builds as time progressed.
@Joregen2009, I have seen your name around before, appreciate you building!!
Click to expand...
Click to collapse
It's my pleasure. I only wanted to share my build, because I know that many of you much be as frustrated as me for the lack of ROMs for our device.
We'll see how long this thread will hold. If it's up to me I'll try to provide at least a weekly build from the actual sources, or whenever there are some major changes in the sources that are important for our device until the Lineage Team declares our device official. Let's hope that happens soon and that this thread can contribute to that.
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
@jorgen2009
Hey thanks so much for the ROM. Its working great!
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
I'm trying to figure out how to rebuild it with the drivers for my TP-LINK WN722N V1.
I really don't know what I'm doing but I'm trying to learn.
I'm trying to follow this guide to accomplish this.
https://forum.xda-developers.com/showthread.php?t=2338179
I do have Kali for Magisk up and running just fine.
Lsusb command shows my WiFi Adaptor but the kernel won't let me use it.
Thanks so much for reading, if what I'm trying to do is stupid feel free to let me know why haha. If I get it to work I'll share it with everyone.
redsmith said:
Awesome! Thanks for this ROM. Any known issues one should be aware of before flashing?
Click to expand...
Click to collapse
The only thing that I am aware of is the fact that the battery LED isn't working, but that will be solved in the next build
tkacer said:
Does Lineage have Substratum support ?? Having trouble connecting......
Update. Found answer - : no substratum support
Click to expand...
Click to collapse
Sorry, than I fear it's not supported by LineageOS in general yet, I don't use it myself
gahndii said:
@jorgen2009
Is there any chance you could link me the kernel source for this specific build? (Pixel2)
Click to expand...
Click to collapse
Sure, see LineageOS sources on github, I didn't touch the kernel in this build:
https://github.com/LineageOS/android_kernel_google_wahoo
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
banciii said:
I am still getting the security warning when booting. Am I the only one so I missed something?
Other question: is the Trusted Faces not working because the used GApps package has not been modified for the Pixel, or the ROM has got some incompatibility issue?
Click to expand...
Click to collapse
Are you sure you are on the April vendor? Your vendor version must be the same as the ROM needs (currently the April one).
Trusted Faces is GApps related yes, it's not in MindTheGApps. I'll try to make a build with OpenGApps in to see if that works. Both Face Detection for Media and Face Unlock are in the Nano package (https://github.com/opengapps/opengapps/wiki/Nano-Package)
redsmith said:
Great job. Just a little bug: Long press power button to turn on torch is not working when Ambient Display is set to always on.
Click to expand...
Click to collapse
I'll put it in the known issues list in the OP later this week for an overview
Another build is up. This time I used OpenGapps so you might need to clear the Store cache. I had no problems upgrading myself. The Text-to-speech improved a lot with these Gapps for me.
New in this build is the LED light when charging and some basic stuff for more compatibility with our device and some networks. Also all the normal changes since the last build for LineageOS are in of course. For the download link see the OP. I also adjusted the OP a bit to show the things that are known not to work. Let me know if I missed something so I can adjust the list
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Hotspot
Flash
GPS
What's not working :
Boot doesnt work all the time (just dont reboot the phone, i guess)
GSIs (Generic System Images) work fine though for some reason
DAC(?)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions :
Download the build
If you dont have a vendor partition yet, create one GUIDE
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Here
H932 Build
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-15.1-treble branch
XDA:DevDB Information
LineageOS 15.1 - Treble, ROM for the LG V30
Contributors
SGCMarkus, rashed97
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-10-03
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that, same for vendor
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/Linea..._base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 22.07.2018
- Updated blobs to H930 V20R
- fixed vibration becoming dull after a while
- all other past changes from normal LOS since last update here
- updated source
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a
- Vibration motor ready for P GSIs
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Does this work on the US998?
A. Hasn't been tested yet. Try it out and report (but make a backup first as always).
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
okaiuz said:
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
Click to expand...
Click to collapse
The reboot problems only occur with the 2 LineageOS builds, not with GSIs (or i was just really extremly lucky, but i doubt that).
On LOS i have a ~20% boot chance (did once 35 boot tries after another...), and on GSIs it boot always like 6 or 7 times after another. Suppose it works there, really unlikely i was that lucky lol
The GSI of LOS by phhuson also works btw (just no double tap 2 wake).
I would actually love to make way more ROMs.... I even had a CrDroid test build once (to check if its only LOS with that problem), but sadly im out of space now.... dont have more space than for LOS :/
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
okaiuz said:
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
Click to expand...
Click to collapse
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
SGCMarkus said:
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
Click to expand...
Click to collapse
i have to thank you again for you work!
Thursday i'll try to partition my v30+ and try your treblelized los!
i give a chance even to phh los, aosp and rr!
i 'll yo know my experience, hoping that you can fix the boot problem!
Regards!
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
donky kong 017 said:
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
Click to expand...
Click to collapse
Use Viper4Android and the predicament is solved.
Nikola Jovanovic said:
Use Viper4Android and the predicament is solved.
Click to expand...
Click to collapse
does viper use the quad DAC. AFAIK no. ATM i use the V30 Quad DAC and Ainur Sauron
As it also counts for this, i will simply refer to my post in the other LOS thread
https://forum.xda-developers.com/showpost.php?p=76536335&postcount=20
you're the best!
tnx to phh also!
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
elba96 said:
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
Click to expand...
Click to collapse
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
SGCMarkus said:
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
Click to expand...
Click to collapse
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
okaiuz said:
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Click to expand...
Click to collapse
Yes, you can still use the non treblelized version
Still working on adding features though, fixing major bugs first ^^
Doblix said:
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
Click to expand...
Click to collapse
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
elba96 said:
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
Click to expand...
Click to collapse
My testers say its ready for daily usage
Couldnt test for battery life yet myself. Didnt have the time to setup everything a new... University life is tough
SGCMarkus said:
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
Click to expand...
Click to collapse
Yes vendor is listed there and I could also format it. I am at university right now and reverted to stock to be able to use it (which can be flashed fine btw.), I will see when I find the time to flash again and post the log here then.
{
"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"
}
What This Is
This is a personal project to get Lineage OS running on my Pixel 3a. As such it is provided as is, though I will endeavor to provide regular builds and offer limited support as I am able.
What's Been Tested
This is my daily driver, so I've flashed ElementalX kernel and openGapps Pico over stock.
T-Mobile (at least), camera, wifi, bluetooth, gps are used regularly without issue.
What Was Not Tested
Root
Squeeze sensor
Gapps beyond Pico
Known Issues
eSIM doesn't work and has been removed
If flashing Gapps, an app downloaded at first-time setup Data Transfer Tools will crash constantly and needs to be uninstalled. This may mean you can't transfer data from an old phone to this one via setup.
Downloads
Lineage OS 16.0 Unofficial
Installation
I have not had success with an installable zip for TWRP yet, so the rom images must be flashed via fastboot. You should be familiar with fastboot before attempting to install this rom. It is recommended that you back up your current OS before installing a new one.
Installing this or any rom will void your warranty.
After unlocking OEM and your bootloader, boot into bootloader either with fastboot reboot bootloader or by holding VOLUME DOWN + POWER from power off, plug your phone into the computer.
If running on a linux machine with fastboot installed you can execute the flash-all.sh script included in the download. Alternatively or otherwise:
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w (to wipe cache and data)
After installing, Gapps (ARM64, 9.0, see note in Known Issues), kernels, Magisk (UNTESTED) and other zips can be installed as normal via TWRP.
I Wanna Go Back
Up-to-date stock images are provided by Google and can be reflashed from bootloader.
Just follow the instructions at the top of the page.
Sources
LineageOS
Vendor proprietary packages (thanks to Dirty Unicorns and ZVNexus)
Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!
gee one said:
Nice work! I'll have to wait until tonight to test it.
I've been working on my own builds. The June firmware worked well, but after updating to July firmware and vendor, WiFi calling isn't working. The camera had always been a little fickle. I can't wait to test...
Click to expand...
Click to collapse
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how) wifi calling works fine on T-Mobile, and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
koichirose said:
Does it support Google Camera fully (with motion and everything)?
Any hope of making it official?
Great work!
Click to expand...
Click to collapse
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working works with Google Photos installed. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.
pipyui said:
Let me know what you discover! I haven't tested wifi calling (wouldn't even know how), and while I looked through my logcat, I can't say I was entirely confident in my ability to read it...
Mostly 'access denied' errors on some gpu libraries and an error reading the squeeze sensor config (but only when I'm connected to adb).
Thanks! I hadn't tested google camera motion till now, but it doesn't look to be working. Haven't had trouble with pictures and video otherwise through it though.
In regards to making it official, maybe with some polish. I'm new to the android dev scene so not too confident in my ability to maintain a project like this yet.
But I'll look into the process.
Click to expand...
Click to collapse
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
Nevermind @koichirose, camera Motion works fine once I installed Google Photos. :good:
gee one said:
Yes, I get a lot of selinux errors in the logcat too. I haven't had time to research them.
The squeeze issue is odd, perhaps some uid is conflicting. I think these are set up in the init files.
Click to expand...
Click to collapse
It's odd that it only shows up when I connect to logcat via adb. Local terminal logcat doesn't show me these squeeze errors.
Also, wifi calling working on T-Mobile :good:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
Chronzy said:
Thanks for building. I had issues installing apps from the play store, lots of download pending despite force stopping play store and several reboots. Also magisk doesn't appear to work when flashed through twrp. I didn't try patching the kernel through magisk manager though. Good first look though!
Click to expand...
Click to collapse
I ran into this same issue - had to remove Data Transfer Tools (don't need root for this, since it was downloaded by gapps) and do a cache wipe to be able to download apps again. I think it blocks you from using the play store until you complete google's first-time setup, and this app blocks that (not to mention it crashes frequently).
I'll test out Magisk when I'm able. You may need to enable root access to apps in dev settings, but I'm unsure.
OMG thank u so much! Was waiting for this forever, hope you can make twrp zip
Getting "Sim not Found" on both rooted and unrooted
Tiebe said:
Getting "Sim not Found" on both rooted and unrooted
Click to expand...
Click to collapse
Have you checked OP? eSIM doesn't work. Need physical SIM
Uzephi said:
Have you checked OP? eSIM doesn't work. Need physical SIM
Click to expand...
Click to collapse
I have a physical sim. I solved the problem tho. I just had to reflash the stock radio image
Thanks for putting a build together! Provides even more incentive for me to make the switch over to a 3a Keep up the good work.
Is the device showing as certified without root?
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
Unstroofy said:
Is the device showing as certified without root?
Click to expand...
Click to collapse
It is not certified.
Dreamsocks66 said:
Could anybody who has been testing out this rom give me any idea of what their battery life is like? I feel like mine has been much worse since flashing this. Dropped 10% overnight with nothing running and in airplane mode.
Click to expand...
Click to collapse
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
Geo411m said:
any chance for a 3aXL port? I've been wanting to do one myself but I'm in the middle of a kitchen remodel so not much time to setup a build environment.
Click to expand...
Click to collapse
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
pipyui said:
It is not certified.
I get about 2 days out of a charge on ElementalX kernel, but I'm sorry to say I've hardly tested vanilla LoS kernel.
In my experience I usually have to go through a full charge cycle on a new rom then restart my phone for battery life to stabilize.
While I should be able to build an XL port, I won't be able to test it myself. Let me know if you'd like to run a build in beta.
Click to expand...
Click to collapse
I'll test for you
Neat, I'll get a build together for ya tonight then.
Any chance of a flashable zip for the official twrp?
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.
{
"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"
}
ArrowOS
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | Chat
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
Blog: blog.arrowos.net
Pre-installation:
TWRP(Z00T) (Download from here)
TWRP(Z00L) (Download from here)
NikGapps core (Download from here)
Installation:
Backup your data to PC, OTG flash drive
Flash recovery and boot to recovery
Wipe system, data, cache and dalvik, then reboot to recovery
Copy ArrowOS and Gapps to internal memory then flash them in TWRP in same order
Reboot and enjoy
Download:
Google Drive Folder
What's not working?
USB Debugging (Wireless Debugging works fine, you can use it instead...)
What's working?
Everything else?
Known minor issues:
Rarely, opening the settings from quick settings can crash the system-ui. This issue is not persistent and if it happens, only happens after a reboot or restarting system-ui(like changing ui elements from customization options).
Opening a notification will solve this issue until the next reboot, also this problem didn't happen when i had a password/pin protection.
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.108
Based On: AOSP
Android Security Update: September 5 2022
SELinux: Enforcing
Status: Stable
I made this rom for personal use and can't regularly update or maintain it. Don't have enough time or storage space on my drives for it. So, if you find some other bugs feel free to report it for other users but i probably won't be able to fix them. Apart from the hotspot problem i didn't encounter any major issues...
I made 2 roms for these devices, crDroid and ArrowOS, wanted to see if ArrowOS was more lightweight and faster compared to crDroid... didn't see much difference in terms of performance. and ArrowOS dropped android 11 support so the security updates are a bit behind. anyways, since i already built it why not share it? so you guys have a vanilla rom option as well... personally i'll stick with the crDroid for now. but it's a personal preference.
link to the crDroid thread: https://forum.xda-developers.com/t/...d-v7-29-unofficial-20-04-2023-stable.4578239/
Thanks so much for your effort and great work.
@OP It just so happens my Z00T JUST got her cracked screen as SERIOUSLY bloated battery (seriously, it pushed the screen up 1mm bottom right corner... Till I popped the back cover that is, lol!) Replaced!
I actually beta tested for a dev way back when these where new, lol
Gimmie a day, I'll report back, if your still wanting Laser feedback?
Cheers either way!
lenigma1too said:
@OP It just so happens my Z00T JUST got her cracked screen as SERIOUSLY bloated battery (seriously, it pushed the screen up 1mm bottom right corner... Till I popped the back cover that is, lol!) Replaced!
I actually beta tested for a dev way back when these where new, lol
Gimmie a day, I'll report back, if your still wanting Laser feedback?
Cheers either way!
Click to expand...
Click to collapse
yeah would be nice. i'd like to see if it works on Z00L and if the same bugs are present or if there are more bugs... i don't have any way of testing that variant but since every other developer built roms for these 2 devices together and both had similar experience i'd assume Z00L would be fine as well...
zenfone selfie said:
yeah would be nice. i'd like to see if it works on Z00L and if the same bugs are present or if there are more bugs... i don't have any way of testing that variant but since every other developer built roms for these 2 devices together and both had similar experience i'd assume Z00L would be fine as well...
Click to expand...
Click to collapse
*Open mouth, insert foot*
Its actually the ze551kl, the 1080p variant of the Z00L 720p.
But, rereading your op, it IS this variant you couldn't test, correct?
Anyways, now that I'm no longer lying to you (), I'll be testing on a ze551kl, not ze550kl or selfie
lenigma1too said:
*Open mouth, insert foot*
Its actually the ze551kl, the 1080p variant of the Z00L 720p.
But, rereading your op, it IS this variant you couldn't test, correct?
Anyways, now that I'm no longer lying to you (), I'll be testing on a ze551kl, not ze550kl or selfie
Click to expand...
Click to collapse
i think that's a Z00T as well? still... even if it's the same code, it's still a different device. any testing is better than none i just wanna know if the Z00L rooms are working tho i compiled em but still no feedback for em.
zenfone selfie said:
i think that's a Z00T as well? still... even if it's the same code, it's still a different device. any testing is better than none i just wanna know if the Z00L rooms are working tho i compiled em but still no feedback for em.
Click to expand...
Click to collapse
Thanks for the great work and effort to keep these devices alive.
Today I only tried the installation on ze550kl z00l and everything went fine. Twrp 3.3.1-0 is nikgapps core arm64. I haven't been able to test it thoroughly, but the basic functions work very well. The audio is also great, unlike previous versions of Android 10 where the audio sometimes worked and sometimes it didn't.
Immediately after, as recommended by you, I installed CrDroid, so I can't say about this rom.
A thousand thanks
jimjack12 said:
Thanks for the great work and effort to keep these devices alive.
Today I only tried the installation on ze550kl z00l and everything went fine. Twrp 3.3.1-0 is nikgapps core arm64. I haven't been able to test it thoroughly, but the basic functions work very well. The audio is also great, unlike previous versions of Android 10 where the audio sometimes worked and sometimes it didn't.
Immediately after, as recommended by you, I installed CrDroid, so I can't say about this rom.
A thousand thanks
Click to expand...
Click to collapse
by audio do you mean the loudspeaker issue during calls? or was there another audio bug in the 10 roms? i didn't actually use 10 on this phone. just tested briefly and loudspeaker issue was big enough for me to just walk away. don't know all the details about previous roms except for groovy nougat.
Con l'audio intendo che non si sentiva nulla completamente, suoneria, musica, ecc...
Questa versione tuttavia non sembra avere questo problema.
Hi @selfie zenfon.
With the little time I have available, I tried to do some tests on ze550kl z00ld.
As mentioned in the previous post, I installed crDroid, with twrp 3.3.1-0, but after doing a factory data reset as the operating system and after the first recharge, the smartphone went into bootloop.
Then I installed Twrp 3.7.0_9 and Arrowos. I also tried doing a factory data reset with this rom and it has been working fine for about 3 days without any bootloop.
I can also say that it is about 10% smoother than CrDroid.
I would also try CrDroid with Twrp 3.7.0_9 as soon as possible to see if it will bootloop again.
Also I want to compliment you: I don't know if you are a developer and I don't know how you compiled these roms, but I can tell you that they work very well and I can say that they are among the best custom roms for these devices.
Thanks so much for the great job
last and probably the final build is up!
hotspot fix applied to the arrowos as well...
enable blurs option is removed.
face unlock wasn't working on this rom so removed the relevant packages and it won't show up in the settings anymore.
duckduckgo browser won't be pre-installed as a system app as it's available on playstore.
this build doesn't have a pre-installed browser right now, but as i said i made these roms for my personal use first... i won't be using ddg and not having a pre-installed browser isn't a problem for me.
jimjack12 said:
Hi @selfie zenfon.
With the little time I have available, I tried to do some tests on ze550kl z00ld.
As mentioned in the previous post, I installed crDroid, with twrp 3.3.1-0, but after doing a factory data reset as the operating system and after the first recharge, the smartphone went into bootloop.
Then I installed Twrp 3.7.0_9 and Arrowos. I also tried doing a factory data reset with this rom and it has been working fine for about 3 days without any bootloop.
I can also say that it is about 10% smoother than CrDroid.
I would also try CrDroid with Twrp 3.7.0_9 as soon as possible to see if it will bootloop again.
Also I want to compliment you: I don't know if you are a developer and I don't know how you compiled these roms, but I can tell you that they work very well and I can say that they are among the best custom roms for these devices.
Thanks so much for the great job
Click to expand...
Click to collapse
tried 3.7.0_9 again, no matter what... i can't install any roms with it. either it says factory reset on the first boot and reboots to the recovery. or system boots up but can't do anything... can't install apps, take photos etc. my storage becomes unusable. if i wipe the partitions using older version and install the rom with the latest, then it works. but if i wipe my phone with the new twrp is causes that problem... @str4610 also used a newer twrp without any issues but i don't know. i can't make it work
don't know anything about the crdroid bootloops, i didn't have that problem yet. but if this rom works better for you that's fine. applied the hotspot fix now this one is a fully functional option as well...
also it would be nice if you can test the latest builds for both if you have some spare time. i can test the z00t but i don't know if the z00l builds even booting up should work but can't be certain without actual testing.
edit: ah twrp was fine. my phone was messed up lol had to resize my data partition and everything is ok with the latest twrp now.
Thanks so much for the great job.
I confirm the installation of the new version of CrDroid and ArrowOs (It's a pity that this rom has been abandoned..).
TWRP used: 3.7.0_9-0.
Installation:
1) Format the data
2) Wipe system, data, cache and dalvik
3) Reboot into Twrp and install CrDroid+NikGapps Core
To speed up the system a bit, enable developer options and scale animations from 1 -> 0.5
I confirm the following features:
-Bluetooth
- Double tap to turn off/wake the screen
- Wifi
- Torch
- Camera
- Basic functions.
Not using the smartphone as a daily driver, I can't say more.
Thank you so much for your time and effort to maintain this device.
@jimjack12
thanks for testing it most of the custom rom groups stopped developing 11 long before arrow did. it's still not that far behind and security updates are not "that" important on such an old phone. and i can't promise to update crdroid or lineage either. i don't have enough storage on my drives so i was using an old sata 2 hdd from 2007/2008 lol
can't regularly set this development environment for just the updates.
120gb off brand ssd hanging for system/swap/cache and 640gb old af hdd with some badsectors is for android source code not ideal... all my actual drives are almost full...
final update is released... applied the last patches i made for crdroid, all cores should be online for all the devices now. didn't get any bug reports for arrowos but since my device sources were the same, i assumed it would have the same issue.
Last time I checked the previous update prior to the latest one didn't had the Smart Orientation. Rest was all good.
Is it implemented now???
CapTain335 said:
Last time I checked the previous update prior to the latest one didn't had the Smart Orientation. Rest was all good.
Is it implemented now???
Click to expand...
Click to collapse
no feature updates. just applied the fixes i made for crdroid.
zenfone selfie said:
View attachment 5913753
I made this rom for personal use and can't regularly update or maintain it. Don't have enough time or storage space on my drives for it. So, if you find some other bugs feel free to report it for other users but i probably won't be able to fix them. Apart from the hotspot problem i didn't encounter any major issues...
I made 2 roms for these devices, crDroid and ArrowOS, wanted to see if ArrowOS was more lightweight and faster compared to crDroid... didn't see much difference in terms of performance. and ArrowOS dropped android 11 support so the security updates are a bit behind. anyways, since i already built it why not share it? so you guys have a vanilla rom option as well... personally i'll stick with the crDroid for now. but it's a personal preference.
link to the crDroid thread: https://forum.xda-developers.com/t/...d-v7-29-unofficial-20-04-2023-stable.4578239/
Click to expand...
Click to collapse
sorry, on my cellphone, Asus Zenfone Selfie can't be flashed
i am using Z00T version
fdxnameword said:
sorry, on my cellphone, Asus Zenfone Selfie can't be flashed
i am using Z00T version
Click to expand...
Click to collapse
zenfone selfie works fine with this rom. its my own test device. maybe your download failed? or file corrupted while copying to the phone? what's the error you're getting?
if the phone was encrypted it might require a data format(not wipe)