Develop Bugs

[ROM][P900/T900][Unofficial] Resurrection Remix 5.8.5 [7.1.2][2017/09/26]

Code:
/*
* Your warranty is now void.
*
* Neither me nor Resurrection Remix nor anyone else mentioned in this post is
* responsible for bricked devices, dead SD cards, thermonuclear war, or you
* getting fired because the alarm app failed. Please do some research if you
* have any concerns about features included in this ROM before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at
* us for messing up your device, we will laugh at you.
*
*/
This is my first ROM built with help from jdelano who used to build this ROM for these devices.
Even if this is quite new to me, issue reports are welcome and I'm trying to help as good as I can.
About Resurrection Remix
Resurrection Remix has been based on CM, slim, omni and original Remix ROM builds creating an awesome combination of performance, customization, power and the newest features while being completely open source.
Features
Statusbar customization (Centered clock, custom battery icon, battery bar,...)
Navigationbar (activate navigation bar, rearrange buttons, custom actions,...)
Hardware buttons customization
Lockscreen customization (shortcut custumization, hide emergency button,...)
Gestures
Quicksettings customization
Interface customization (custom dpi, ambient display,...)
Themes (OMS support)
and many more
Changelog
Known issues
MHL out to TV doesn't work
Mentioning issues
Before mentioning issues, please make sure you followed the instructions mentioned below and you're not using custom kernels or mods modifying system files.
Installation instructions
First install/Clean Flash
Download latest ROM zip file
Download GApps
(Download latest TWRP and install it) - T900 users need to use a special TWRP linked in Downloads section
Reboot into recovery
Make Nandroid backup (recommended)
Wipe Data, System and (Dalvik) Cache
Flash ROM and GApps
Reboot
Enjoy Resurrection Remix!
Update/Dirty Flash
Download latest ROM zip file
Reboot into recovery
Make Nandroid backup (not needed in most cases, but better to be save if something went wrong)
Flash ROM
Reboot
Enjoy the update!
Downloads
ROM
P900 (v1awifi)
T900 (v2awifi)
TWRP
P900
T900: Your TWRP is linked in this thread under Installation - step 3
Open GApps
Download latest GApps from Open GApps official website using
Platform: arm
Android: 7.1
Variant: the one you prefer (I use stock without issues but on another device I had issues with GBoard settings force closing)
Credits
RR Team
CyanogenMod/LineageOS Team
OMNI Team
SLIMROMS Team
Substratum Team
Open GApps Team
Exynos5420 Team
and of course all the contributers, supporters and donators
Sources
P900 device sources
T900 device sources
RR sources
​

Screenshots
{
"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"
}
​

I just updated my phone to 5.8.2 last night. It'll be interesting to run the same ROM on both of my devices. Thanks for your contribution...I look forward to trying it out this evening.

So happy that you took this on @Schrolli97 I love RR and our device deserves the best in software, it's really that good. Best of luck

New builds are up and linked in OP.
Next update should show up in OTA updates

Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).

shonkin said:
Has anyone run into issues with their external sd card -- "corrupted sd card" -- after updating to the last couple versions of RR? This happened as well in the Lineage 14 version (and is discussed there at length). I'd hoped it was avoided in RR, but alas, no. At least, not for me. The card is *not* corrupted; rather the OS isn't reading it correctly. I had to back off with RR to an earlier version capable of still reading exfat (the default microsd card format).
Click to expand...
Click to collapse
I had this some time ago. I moved all data to my PC. Formatted the card in my tablet and moved it all back. Now it works fine

Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).

Anybody wants great sound on your tablet? Tested by me. Works great. I installed the whole choobang. Damn! I have bass on my speakers now!
https://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709

Schrolli97 said:
New builds are up and linked in OP.
Next update should show up in OTA updates
Click to expand...
Click to collapse
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).

Gary_O said:
@Schrolli97 thanks for carrying on with this great RR Rom! I clean installed the 2017/02/24 version, and it has been working great. Donation sent!
There is a fix to the lock screen non-rotation issue (which you may know about). Posting here for others, FYI...
Add the following code to the root/system/build.prop file, then save it and reboot.
Code:
log.tag.launcher_force_rotate=VERBOSE
lockscreen.rot_override=true
You can use the included Deathly Adiutor app to edit the build.prop file (under Tools / Build prop Editor).
Click to expand...
Click to collapse
Very happy that you guys enjoy this. Hope that I can contribute to making this device even more awesome
Thanks for mentioning this fix. Just added it to the OP :highfive:
Let's see if I can get it to work that you don't need to edit build.prop anymore.
shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" uu. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.

shonkin said:
Nope, sorry y'all...
Two different microsd cards, formatted on the tablet with android as portable (exfat). Both work fine with last version of RR previous to 2/28/17 version. As soon as I install newest version, either clean or dirty install, I get the "Corrupted Samsung SD Card" message. Both cards are *brand* new -- one a Samsung Evo plus 64g, the other a Samsung Evo 128g.
For folks with the card formatted internally, it will work of course (different format). I'm about to restore my old version, but thought I'd give ya a heads-up. And again, this same issue has shown up over in the LIneage 14 folks' page.
I know this is complaining. But hey, maintainers of these Roms get total respect from me... and THANKS. Just passing along info to help....
---------- Post added at 11:36 PM ---------- Previous post was at 11:24 PM ----------
VERIFIED that removing 2/28 version and reinstalling the 2/18 version restores functionality to sdcard (portable exfat).
Click to expand...
Click to collapse
Same issue to me, it report SD card (exfat) corrupted after upgrading to 2/28 version.

Schrolli97 said:
For me it's working fine so I can't say much about it. I guess the only fix at this time is disabling sdcardfs via build.prop...
For anyone else having this problem:
Changing "ro.sys.sdcardfs=true" to "ro.sys.sdcardfs=false" in build.prop and rebooting should fix this.
Click to expand...
Click to collapse
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.

shonkin said:
Super-appreciate this rom.... but no, this is not a fix. Identical message "corrupted sdcard" before and after changing the above in Deathly Adiutor. I had to revert to an earlier version of the rom before the sdcardfs setting came into play. Is there any way to remove that code from my end? As in, remove it altogether, or somehow having it revert to what worked just fine before it came along?
An interesting corollary is my Samsung Note 4 phone, which I also run Resurrection Rom on (the 3/7/17 version). No issues with the micro sd card in it... and interestingly, that RR build has no Deathly Adiutor in it. I'm in over my head at this point, but pass on that info for what it is worth.
Click to expand...
Click to collapse
If changing build.prop values doesn't work, I don't think there's a way to revert this from your end. I don't even know if (i.e. how easy) I can revert it. So I guess I will read about it. It may take a while, though, as I'm quite busy for the next week.
Deathly Adiutor is an altered version of kernel Adiutor that only works with devices using the processor of our tablet. I don't think the note 4 is one of those devices. Also it probably has another maintainer who's​ maybe just not including it in the ROM.
I guess sdcardfs is also just included by lineage maintainers whose device drivers I'm using. Though, I didn't have enough time to check, yet.
I'll keep my eyes open. Will tell you when I know more.

New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
For the next update I'll target the SD card if the problem is still present.

Schrolli97 said:
New builds are up and should show up in Settings > Configurations > Miscellaneous > Updates.
Non-rotating lockscreen is fixed.
Click to expand...
Click to collapse
Thanks, and thanks for incorporating the non-rotating lockscreen. :good:
I have noticed a problem with Substratum with this 20170317 version of the RR ROM. Substratum is running in Legacy mode, and not OMS mode. On the previous version 20170228 RR ROM, Substratum was running fine in OMS mode. I did a full wipe / clean install of the 0317 ROM. I have installed the same version of Substratum (604) on both 0228 and 0317 ROMs.
Per some other forum suggestons, I tried force closing Substratum, then clearing the data and cache for substratum and reopening it. Still in Legacy mode. Anyone else experiencing this?

Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices

JodyBreeze901 said:
Quick question, is anyone else having Bluetooth issues? I'm not able to connect to any Bluetooth devices
Click to expand...
Click to collapse
I have not experienced any Bluetooth issues. Although so far only connected to my Mpow bluetooth headphones, worked first time.

Alrighty then.......looks like it's time for a clean install
Sent from my SM-N920C using Tapatalk

I dirty - flashed the 0317 update, and I wasn't going to say anything... But since someone else clean-flashed and has the same problem with substratum, I decided to post.
It is running in legacy mode, and isn't applying anything. I've cleared data on substratum, disabled/rebuilt the themes, and uninstalled all/reinstalled all. Of course, the tab has been rebooted in between many times.

[rom] lineage os 13 for htc 526g plus dual sim (mt6592) (port)

MODERATOR NOTICE:
This thread does not meet the requirements laid out in the sticky titled "Device Forum Rules (Please Read before posting)." All ROMs posted in the Development section must contain a link to the developers sources.
THREAD CLOSED
{
"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"
}
LINEAGE OS 13
REQUIRES UNLOCKED BOOTLOADER AND RECOMMENDED TWRP 3.0.2
YouTube - Unlock Bootloader
Check Another Port By Salman On Unlocking Bootloader
Pre-Installed Apps :
AudioFX - Audio optimizer with presets to alter the music listening experience.
Browser - A light-weight browser that relies on the System Webview, for low end devices, also known as Jelly.
FlipFlap - An app for smart flip covers, only included on select devices.
Calculator - which resembles a four-function calculator and offers some more advanced functions.
Calendar - Calendar functionality with Day, Week Month, Year or Agenda views.
Camera - Dependent on device specification will take video or photos, including panoramic.
Clock - World clock, Countdown timer, Stopwatch and Alarms.
Contacts - Phonebook for numbers and e-mail addresses.
Email - Email client that handles POP3, IMAP and Exchange.
Files - Simple File Manager to move copy and rename files on internal storage or SD-Card.
Gallery - Organise photos and videos into a timeline or albums for easy viewing.
Messaging - SMS messaging.
Music - A music player, formerly known as Eleven.
Phone - for making Calls. Includes Speed dial, Phone number lookups and call blocking.
Recorder - A screen and/or sound recorder.
Trebuchet - A customizable launcher that supports protected apps.
Sim Toolkit
Features :
Audio in calls
Loudspeaker
Bluetooth
Microphone
SMS (Receive and Send both working)
WiFi (2.4ghz ofcourse for MT6592)
USSD
Data
Dual SIM
Hotspot
Screen Recording (In-Built)
Both storages (SD and Internal)
Gapps
2G/3G Switch
Camera - Features Include ; Flash Mode, Picture Size, Quality, Countdown, Pro Photography Mode and many more.
VPN (Bug fixed and works now)
Latest Security Patch (January 1, 2017)
Lineage OS API Level : Fig (6)
Multi-Window (Enable in Developer Options)
Bugs :
Found one which is common in all custom ROMS - GPS ( Still Working ON FIX )
For optimum speed and RAM Management please enable swap using ROHAESOFT RAM EXPANDER
Using customer path /zram0 at 512MiB
Additional Features:
1. Good RAM management
2. Improved audio and video recording quality
3. Efficient power saving.
4. Screen recognizes two fingers.
5. Support for ipv4 and ipv6.
6. Faster boot.
X. All other features are there which you expect in Lineage OS 13
INSTALLATION - Using TWRP 3 FOR HTC 526G+
1) Wipe cache, dalvik cache, system
2) Flash LINE526.zip
3) FlASH ARM for android 6.0 GAPPS
4) Wipe cache and dalvik cache again
5) Reboot System
Version Information
Status: Stable
ROM OS Version: 6.x
ROM Kernel: Linux 3.4.x
Credits :-
Lineage OS For providing the source ROM
Roushan Kumar Sharma - For porting to MTK6592
Download Links :
MOD EDIT: DOWNLOAD LINK REMOVED
GApps
Screenshots Attached Below
Beauty Catches Attention :silly:, But Character Catches The Heart
Be Sure to Hit the Thanks Button

vpn is still not working.
vpn is still not working in my device that is recently flashed. plz help!!

which VPN app are you using ?

Which gapps to use.. X86 or ARM

ARM for android 6.0

I am getting an error while flashing LINE526.zip.
Unable to execute some file in zip written in red..

Error 7 while flashing
I get error 7 while flasing this rom and error 25 while flashing gapps

installed the lineage os 13 ..... great rom working real smooth......
only problem was that only sim 2 was working although both sim showed signal
major signal drop every 5 minutes
sim network issues only

Ram Singla said:
I get error 7 while flasing this rom and error 25 while flashing gapps
Click to expand...
Click to collapse
are you on custom recovery that is recommended in the this thread ?
make sure you are flashing the correct gapps

priyansh21 said:
installed the lineage os 13 ..... great rom working real smooth......
only problem was that only sim 2 was working although both sim showed signal
major signal drop every 5 minutes
sim network issues only
Click to expand...
Click to collapse
tested both sim cards it shows no signal drops for me

truzz_patel said:
are you on custom recovery that is recommended in the this thread ?
make sure you are flashing the correct gapps
Click to expand...
Click to collapse
I solved this problem by reflashing both of them but I wrongly formatted my phone due to which when I flash stock ROM it shows BROM error 4008 and its probably due to drivers plz help give me all drivers link needed to flash stock on HTC I am using win 10 64 bit plz help

Ram Singla said:
I solved this problem by reflashing both of them but I wrongly formatted my phone due to which when I flash stock ROM it shows BROM error 4008 and its probably due to drivers plz help give me all drivers link needed to flash stock on HTC I am using win 10 64 bit plz help
Click to expand...
Click to collapse
Hey there, i will surely help you solve the problem, since it will he a long process i will be private messaging you [emoji1]
Sent from my HTC One X9 dual sim using Tapatalk

truzz_patel said:
tested both sim cards it shows no signal drops for me
Click to expand...
Click to collapse
Major drops for me but, specially sim 1 its shows no mobile network most of the time

GPS Fix
In order to fix GPS, replace the GPS.conf file in /system/etc folder, and set the permissions to -RW--R--R, and restart the phone. File is attached, remove .txt from the filename before replacing. I've tested on my phone, running this R and YGPS shows the correct GPS lock.
Happy testing..

Network Drop Fix
priyansh21 said:
installed the lineage os 13 ..... great rom working real smooth......
only problem was that only sim 2 was working although both sim showed signal
major signal drop every 5 minutes
sim network issues only
Click to expand...
Click to collapse
It happens if you clean install the ROM, meaning wiping the data as well. In order to fix this, format everything except External SD Card using TWRP, and install Resurrection Remix ROM build date 20161119, boot the phone and then go to recovery after successful boot. Now, only wipe Cache, Dalvik Cache and System, do not wipe data. Install the ROM and gapps and clear cache and Dalvik. That's it. You'll no longer notice the signal drops.
Note : I chose 20161119 RR build because I have noticed that the signal quality is way better than any other custom ROM build.
Happy testing.

Owais Siddiqui said:
It happens if you clean install the ROM, meaning wiping the data as well. In order to fix this, format everything except External SD Card using TWRP, and install Resurrection Remix ROM build date 20161119, boot the phone and then go to recovery after successful boot. Now, only wipe Cache, Dalvik Cache and System, do not wipe data. Install the ROM and gapps and clear cache and Dalvik. That's it. You'll no longer notice the signal drops.
Note : I chose 20161119 RR build because I have noticed that the signal quality is way better than any other custom ROM build.
Happy testing.
Click to expand...
Click to collapse
Thanks for the fix... Will try and tell

In Sim 1 mobile network is not showing plzzz fix this

[OFFICIAL] LineageOS 17.1 for Xperia Z3 [CLOSED]

Thread depreciated. There won't be anymore official LOS 17 builds for this device. ​
Please jump to:
The official LineageOS 18.1 thread for z3 or dedicated thread for z3dual​
if you are looking for new builds.
-------------------------------------------------------------------------------------------------------------------------
{
"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 10 (Q), which is designed to increase performance and reliability over stock Android for your device. LineageOS is based on the Android Open Source Project (AOSP) and can be used without the need to have any Google application installed.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below. There are also inofficial TWRP recovery builds available - if you want to use TWRP you need to ensure that it is compatible with Android 10.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Detailed instructions:
Install LineageOS on z3
Downloads:
Final official build of 17.1 ROM for Z3:
Google Apps (optional): Open GApps (choose ARM as Platform and Android 10)
Changelog:
Changes for z3
Source Code
The source code of LineageOS is available here. If you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The z3 device tree is available here.
The kernel source code for this device is available here. The used configuration is lineageos_shinano_leo_defconfig available at arch/arm/configs/lineageos_shinano_leo_defconfig in the kernel source.
Bug reports:
How to submit a bug report - Please do not submit anymore bug reports for 17.1 - try 18.1 first please.
LineageOS GitLab
Donate to support development:
Donate via PayPal to NeoArian *** Our main contributor for LineageOS 16 & 17 for Z3 and Z3 Compact ***
Donate via PayPal to LineageOS
Thanksgiving
Thanks to everyone who ever contributed to the custom development for this device, especially:
@nailyk
@rcstar6696
@tomascus
@Diewi
@xkeita
@drakonizer
XDA:DevDB Information
LineageOS 17.1 for Xperia Z3, ROM for the Sony Xperia Z3
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12

Remarks, Questions & Answers
Known Major Issues
Official Lineage Recovery is currently broken. There are two options:
TWRP recovery (inofficial build, optional): TWRP
Unofficial Lineage Recovery build.
WiFi issues in some countries (e.g. Iran): low speed @ 5GHz, hotspot and connection issues. This topic is related to a dirty workaround. A solution is here but will not be integrated into our official Lineage kernel.
Disk Encryption: Disk Encryption is working, however not with the default password (no password). Workaround: Set password first, then start disk encryption, not the other way round! Solved
Bluetooth Low Power may create wakelocks in certain scenarios.* Solved
Thermal throttling of CPU cores: Due to a design issue of the thermal manager ("Thermanager") when used with older kernels like ours you have to expect that the frequency throttling of the CPU cores may fail, especially after(!) the device was getting hot and is recovering. This may lead to performance issues until reboot and other issues. Workaround: reboot device after heavy use.*
Reported size of adoptable storage seems to be wrong. However, remaining free space seems to be reported accurately.
Formating a SD card as internal storage may cause the card to be reported as "corrupted".
Screen rotation may not work after a while. Solved, to be integrated into builds from mid April 2021 onwards.
You tell us (with logs please)...
* To our knowledge, these are general issues on all AOSP/LineageOS based custom ROMs for this device family (Shinano). However I would be happy to be mistaken here and if sombody has a solution.
Further hints
This ROM currently does not work with the Z3 Dual SIM variant. Here's a build for the Z3dual.
If you need Google Apps we recommend the OpenGApps "nano" package, however, I personally use the "stock" package which works as well. The ROM also seems to work with MicroG and BiTGApps.
Magisk - see this post for issues with latest Magisk versions
If you need to install a lot of apps you may run out of internal DATA storage capacity, especially if you install one of the larger GAPPS packages. These apps are initially placed on the system partition and do not cost you DATA capacity. However, every update which comes over the Play Store then fills up your data partition. Using an SD card formated as "external" storage does not help you much (unless you use a tool like app2sd which is no more recommended) and isn't encrypted. Formating the SD card as "adoptable storage" comes with the drawback that some apps do not allow to be migrated to this storage, and unfortunately this is true for some streaming music/video apps which need to store a lot of data obviously (for offline use). The solution I am using is to partition a SD card as "mixed", which gives you the possibility to offload at least some apps to adoptable storage while you still have a classical external FAT32 partition where e.g. your streaming app can save its offline files:
Find a large (I tested a 400GB microSDXC card) and fast ("A1" or higher) Micro SD card.
Follow this guide to partition your SD card. Note: all data on the card will be lost.
Restart your phone.
When you are notified that a new storage card has been detected, use it as "external". (Your internal partition has been recognized at that point already and does not need interaction.)
Go to settings / Storage. Verify that you see three entries: 1. Your internal phone storage of 16GB. This includes your SYSTEM partition. 2. Your SD card with an SD card symbol. The size shown should be the full capacity of the card. If you click on it, your "external" partition is shown (misleading) as "System" and blocked. Click on migrate data to migrate all possible apps to your adoptable storage. 3. Your sd card partition formated as mobile storage (unencrypted!).
How to create logs:
Follow How To Logcat
When creating a log, can you make sure you run the command with the -b option to include kernel messages:
Code:
adb logcat -b all
If your device randomly reboots:
Go to Settings -> System -> Advanced -> Developer options -> Store logger data persistently on device. After the reboot occured: Pull the logs from /data/misc/logd/ (root required).
If your device crashes during boot and reboots to recovery:
Code:
adb pull /proc/last_kmsg
Please submit logs from clean systems without "Exposed" or similar modifications in place
Your feedback is wanted regarding the following topics
Please have a look at lineage-18.1!
A big THANK YOU also to @ronnay ryukay for having maintained the inofficial 17.1 thread!

Thank You.
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?

mer5ad said:
lineage-17.1-20200910-recovery-z3.img version is 3.3.1.0, right?
Click to expand...
Click to collapse
TWRP and Lineage Recovery are different things. See Post #2 for details. Current TWRP version is 3.3.1.0 iirc.

Mr.Tom_Tom said:
Contributors
Mr.Tom_Tom, NeoArian, Myself5
Source Code:https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 23.5.A.1.291
Based On: LineageOS
Version Information
Status: Nightly
Created 2020-09-11
Last Updated 2020-09-12
Click to expand...
Click to collapse
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_

dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing and b. i had to regrant permissions for most apps . but that was because i m using BitGapps instead of opengapps. i confirmed it after reading the BiTGapps post!!
[edit] the permission regranting problem of bitgapps has been fixed

nikapos said:
dirty flashing over previous lineage unofficial build worked for me just fine. didn t even have to reflash magisk, just the rom and gapps did the trick. my apps and settings were all there after reboot. minor inconveniences a. i had to erase data contacts storage - it kept force closing but thats maybe because i m using mindthegapps instead of opengapps and b. i had to regrant permissions for most apps.
Click to expand...
Click to collapse
Hmm, ok, sounds good. Will try it. :good:

0LDST4R said:
Crazy guys, thank you very much...
As a long time user i know a clean flash is recommended, but how to switch from the unofficial to the official version? Even possible?
Greetz,
0LDST4R,
_-_-_-_-_-_-_
Click to expand...
Click to collapse
download D6603_23.5.A.1.29.ftf rom and use FLASHTOOl software.

Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...

kwasior500 said:
Any ideas how to run 4k/120fps on android 10? Last thing holding me with stock based MM...
Click to expand...
Click to collapse
not supported by device hardware. be reasonable!

NOT 4k 120FPS, 4k OR 120FPS

Upgraded from 16 to 17 (dirty flash). Most things seem to work well. A few minor issues:
- Data connection occasionally stops working. Can't figure out why, but I think when I disable/enable wifi is connected. Need to dig deeper
- Smart lock with BT device stops working after a while. Have to remove the device and re-enable
Happy otherwise. Good job!

@Mr.Tom_Tom
how can mount System to boot with RW ?

dsp3 said:
Upgraded from 16 to 17 (dirty flash).
Click to expand...
Click to collapse
Thanks for this feedback, but please do NOT dirty flash. When installing official LOS17.1 the first time, do this with a clean setup.

WiFi 5GHz (Russia) does not work. Can you make changes to the kernel?

new update with working calendar widget. i also had to boot into recovery to reflash bitgapps fo the phone to boot normally.
---------- Post added at 06:08 PM ---------- Previous post was at 06:00 PM ----------
where is the update stored if downloaded from settings->system->update? i want to make sure it is promptly deleted after install.
[edit] ok, you have the option to delete the files after install. the option is found within the update settings.

Just tested Google Duo.
No audio issues. Finally. Thanks, thanks, thanks.
So i guess there are no probs in free hand mode too.

Amazing rom. All very smooth. Thanks a lot!
Unfortunately the back camera does not work for me.
First I was able to start it and a black picture came up. Yesterday I did the new OTA update, that didn't change the problem.
This morning I wanted to save logs about the problem and now the Camera App doesn't start anymore.
Logcat:
2020-09-20 10:59:54.035 8972-8972/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: org.lineageos.snap, PID: 8972
java.lang.RuntimeException: Unable to resume activity {org.lineageos.snap/com.android.camera.CameraLauncher}: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4205)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
at android.os.Handler.dispatchMessage(Handler.java:107)
at android.os.Looper.loop(Looper.java:214)
at android.app.ActivityThread.main(ActivityThread.java:7356)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
Caused by: java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
at com.android.camera.PhotoModule.initializeFocusManager(PhotoModule.java:2830)
at com.android.camera.PhotoModule.onResumeBeforeSuper(PhotoModule.java:2598)
at com.android.camera.CameraActivity.onResume(CameraActivity.java:1889)
at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1453)
at android.app.Activity.performResume(Activity.java:7958)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:4195)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:4237)*
at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:52)*
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)*
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)*
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)*
at android.os.Handler.dispatchMessage(Handler.java:107)*
at android.os.Looper.loop(Looper.java:214)*
at android.app.ActivityThread.main(ActivityThread.java:7356)*
at java.lang.reflect.Method.invoke(Native Method)*
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)*
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)*
By forcing stop and restart I was able to reproduce the original error. The log is too big to put it in the post, therefore in the attachment.

SageDroid said:
Unfortunately the back camera does not work for me.
Click to expand...
Click to collapse
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.

Mr.Tom_Tom said:
Thanks for providing a log. When you first installed LOS 17.1 official, did you do a clean install (wipe data & cache)? If not, please do so.
Click to expand...
Click to collapse
Thanks for looking into it. Yes, I wiped them all. Even the internal storage.

[ROM][9.0][ LineageOS 16.0 - MediaPad M3 8.4 ][ Final Update 07/03/2021 ]

{
"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 9 (Pie), 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.
Warning !
Installing a custom ROM on your device can sometimes be difficult and also with unwanted consequences! Therefore, make sure that you understand exactly what risks this operation entails - you are the only one responsible for all actions taken on your device.
What's Working :
Touchscreen
Audio & Video
Hardware video decoder
Wi-Fi
Bluetooth
Lights
Camera
Internal/External Storage
USB/ADB/MTP/OTG
Off-mode Charging
DRM enabled ( the same Level L3 like on Stock EMUI Firmware )
Sensors
Notification light
Fingerprint scanner
RIL & LTE data connection
What's Not Working :
WiFi tethering
SELinux Disabled
Encryption
GPS
Instructions :
Install the new TWRP 3.3.1-1 ( needed for Android Pie/Q )
Reboot to TWRP 3.3.1-1
Perform a clean wipe for the first install
Flash the latest build available and gapps
Reboot
Downloads :
Final Build : 07/03/2021 : LineageOS-16.0-BTV
Root addon : https://download.lineageos.org/extras
Google Apps : https://wiki.lineageos.org/gapps.html
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 /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Any bug not reported in the bug report format below may be ignored.
DEV: Information
Contributors
surdu_petru
Kernel Source Code: android_kernel_huawei_btv
ROM OS Version: LineageOS 16.0 - Android Pie
Version Information
Status: CLOSED
Created 2020-11-22
Last Updated 2020-12-06

TWRP 3.3.1-1
TWRP 3.3.1-1
Downloads :
twrp-3.3.1-1.img md5: 5267939dc15954d4538855743e100ed7

*** reserved ***

Oooo

Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)

Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?

Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
---------- Post added at 11:13 AM ---------- Previous post was at 11:08 AM ----------
ravedave2005 said:
Very exciting news!
question: Why are you working on Android 9 instead of jumping to Android 10? (i think i saw in the other thread that you already managed to boot it up on your tablet)
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=83888223&postcount=686

orangpelupa said:
Awesome! Btw encryption is listed as not working, does this mean android adoptable storage won't work?
Click to expand...
Click to collapse
Yes, unfortunately it doesn't work ... I guess it's working in the same way like in LOS 15.1.
I'll spend a few days in the near future to see why it doesn't work and maybe I'll find a solution.
Half Alive said:
Been using it for half a day now. I'm amazed that it's not laggy/buggy for a testing build.The build is fluid and smooth. I thought it'll random reboot every 5 minutes. No force closes or reboots until now. I might be spesking too soon though.
For rotation I used *rotation control* app from the play store and the controls are pinned in the notifications.
And Because it felt that stable I went and installed magisk and safetynet passed with the same steps explained in the Oreo thread.
Pie gestures are there for who cares about it. And you can enable A10 gestures with magisk and an app.. You can google (Android 10 gestures for android pie) and it's worth it tbh.
ofc If I encounter any bug first thing I'd do is removing magisk.
Appreciate your work man. Hope working on the Oreo builds helped a little in bringing Pie. We saw a glimpse of the huge efforts you made to bring Oreo and you keep pushing through.. Hope you're getting enough sleep n rest.
Click to expand...
Click to collapse
Thank you very much for your feedback

Update !
All sensors are working now on LOS 16.0

Hi !
Fingerprint sensor it's also fixed right now
Unfortunately the camera does not seem to be able to activate very easily ...
Starting now to build Android 11 , Lineage OS 18 ... if I manage to boot successfully, I guess I'll abandon this project ( and also I'll skip Android 10 ) and I'll start working on the last Android !
Why Android 9 without Camera working, instead Android 11 without Camera working, right ?
Anyway, I'll keep you updated ...

Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk

Userusing said:
Hello,
First of all, I want to thank you for your amazing work. I really appreciate it.
Bugs in my btvdl09:
1) My bluetooth keyboard (logitech k380) connects but the tablet suddenly shuts down and boots into eRecovery. I'm having the same issue in LOS 15.1 and mentioned this issue in the thread. For LOS 15.1 I managed to resolve the issue by flashing your boot_lte_4.3.img kernel but I got the well-known wifi + bluetooth speed problem back!
The Google drive links of console-ramoops-0 and dmesg-ramoops-0 files (I don't know how to attach files to posts in threads.):
https://drive.google.com/file/d/1ObE1tOuG-5y50rDNMh5ZCJE6MrQP2cs8/view?usp=drivesdk
https://drive.google.com/file/d/1Oi5Od8U3If28GszdlRuZ6r8FNbJ58DPK/view?usp=drivesdk
2) When I insert a flash drive, everything works fine but as soon as i unplug the flash drive, it suddenly shuts down.
The links of console-ramoops-0 and dmesg-ramoops-0 files:
https://drive.google.com/file/d/1OskZOuvi0cc6nxI2fKNga9lamJEF5l6S/view?usp=drivesdk
https://drive.google.com/file/d/1OuHnnerAwUema7ufClNibt9XnByIIhLw/view?usp=drivesdk
3) I noticed that the display becomes snowy from time to time. It happens often under rather heavy tasks like surfing the web with 15 tabs open or installing something etc.
Below is the log file and a screenshot of the incident.
https://drive.google.com/file/d/1pp1CjEYiV-nvrfetfauQ1okFwsSBIEuk/view?usp=drivesdk
Click to expand...
Click to collapse
Ok, I know your issues, unfortunately I can't do anything to fix your bluetooth keyboard.

New Update !
The links from OP are removed and will be updated asap !
You can download from here a second test of LOS 16.0 Android Pie .
Changelog:
All sensors fixed
Fingerprint sensor fixed
Downloads :
lineage-16.0.0-btv.zip
boot_w09.img
Thank you very much for your attention !

Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!

friedsonjm said:
Did a total wipe, 9.0 nano gaaps, booted fine, restoring programs now, thanks!
Click to expand...
Click to collapse
OK, adoptable storage does not seem to work; formats card to 20% then reboots. Have to create partition on SD card using my PC, then format SD card to portable storage on M3 I am not able to download books using Amazon Kindle, I've uninstalled and reinstalled, won't download to main or SD Card. Other apps seem able to download OK Kindle error is 'Device Storage is Full' 19GB free on main, and 32GB free on SD Card
EDIT: And, I missed the part about the new TWRP version... time to start over.
OK, starting over, have confirmed that adopted storage still does not work.

SIM fixed right now on LOS 16.0 Android Pie !
Info not concerned to the WiFi devices.
The fix will be added to the next update !

Wooow.. U did it Los 16 for the M3...
Thank u so much for your hard work...

OK, new TWRP, fresh app installations, SD Card as portable storage, same problem with Kindle (on internal storage) being able to download.
EDIT: Apparently, when Kindle was restored, it did not automatically get storage permissions. Fixed that, and now working fine!
Will now try to download a Google Maps 'offline map' to internal.

This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!

friedsonjm said:
This is strange... gboard installs, but voice typing does not work. Have checked permissions, that's not the issue. When I try to use it, says 'initializing' then that stops and does not allow voice input.
The problem may be that I don't have 'Voice Typing' showing under setting, even though gboard is installed... maybe because I used pico gaaps? Thinking about installing a larger package...
EDIT: Downloading the Micro GAAPS package added voice typing back into the system... I've turned on all permissions for board, set Google Voice typing to 'on,' and still not working.
I'm open to suggestions!
Click to expand...
Click to collapse
Well, on Android 9 our hal Audio ( we still using stock hal Audio from EMUI 5.x, Android 7 ) it's not fully working ... in fact wasn't working at all at beginning but I managed to find a hack to enable audio working but only partially as you can see !
Headset and also voice call on LTE devices it's not working due to this issue ... and ofcourse your related audio issues !
I'm sorry I wasn't clear from the beginning .

[ROM][Android 11][Z00T][Z00L] ArrowOS v11.0 [18.05.2023][STABLE]

{
"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)