** UPDATE 2016-09-28 ** Android 6.01 enables support for HW_Crypto in Snapdragon 800+ phones, which requires recompiled TWRP.
-----------------------------------------------------------
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?
Digian said:
Hi, can anybody clarify whether TWRP is meant to be able to decrypt CM13 (Android 6.0.1) EXT4 partitions ?
According to TWRP 3.0.2.0 it should support encryption but this version was released a while ago. I never tried it with an old Android 5 rom.
When I enter my encryption pin in TWRP it gives a "password failed" error.
I finally got CM13 encryption all setup and now I find I cant do an upgrade because CM updater reboots to recovery which then cant decrypt to write the updates.
So if it DOESN'T support encryption, how the heck do people upgrade their encrypted CM installs ? Is there a better recovery than TWRP ?
Click to expand...
Click to collapse
What phone are you using?
Sent from my GT-S7580 using Tapatalk
DodoGTA said:
What phone are you using?
Click to expand...
Click to collapse
Galaxy s4 LTE-A (i9506) aka "ks01lte".
Ok so it turns out Snapdragon 800 phones have hardware encryption module which is not compiled in TWRP.
You can see my thread here for more info, if anyone can help re-compile TWRP for i9506 to add the required dependency for HW_CRYPTO, i will tip some $$
# HW CRYPTO - TWRP needs to be compiled with these flags (there may be other tweaks required, im not sure)
TARGET_HW_DISK_ENCRYPTION := true
TARGET_KEYMASTER_WAIT_FOR_QSEE := true
http://forum.xda-developers.com/gal...wrp-mount-encrypted-partition-recent-t3468989
Note this problem affects many phones, snapdragon 800, 801, 808 and probably other CPUs with HW crypto.
Nexus 5 | MSM8974 Snapdragon 800 | hardware keystore
LG G4 & LG G4 H815 | MSM8992 Snapdragon 808 | can't find quickly
Sony Xperia Z3 Compact | MSM8974AC Snapdragon 801 | hardware keystore
Sony Z1 Compact | MSM8974 Snapdragon 800 | hardware keystore
Sony Xperia Z3 | MSM8974AC Snapdragon 801 | hardware keystore
1+1 | MSM8974AC Snapdragon 801 | hardware keystore
Galaxy s4 i9506 (msm8974) | Snapdragon 800 | hardware keystore
{
"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"
}
First, let's get the disclaimer out of the way.
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.
*/
This is LineageOS 15.1 built from the official sources with no modification on my part. @Krizthian has done this, but it hasn't been updated since September 2018, plus my build here has the Lineage Recovery.
What works:
Almost everything
Lineage Recovery
What doesn't:
Bluetooth audio on calls
How to install:
1. Install Lineage Recovery (optional, you can use whatever)
2. Get the ROM and GApps and copy the files to a convenient location on your phone.
3. Boot to recovery mode.
4. Do a factory reset. If you are coming from some previous version of LineageOS then this step is optional.
5. Flash the ROM and GApps.
6. Reboot. The first boot will take time for optimization.
Downloads:
Android File Host
Lineage Recovery (Drive)
LineageOS (Drive)
Open GApps
Lineage extras
how about battery life ?
For what it's worth, I've added hammerhead to my build roster. Weekly hammerhead builds for 15.1, using a pristine LineageOS source tree (no modifications whatsoever), are at https://lineageos.disavowed.jp/hammerhead/.
wileyc said:
For what it's worth, I've added hammerhead to my build roster. Weekly hammerhead builds for 15.1, using a pristine LineageOS source tree (no modifications whatsoever), are at https://lineageos.disavowed.jp/hammerhead/.
Click to expand...
Click to collapse
Thanks very much. Just updated my hammerhead 15.1 with a dirty flash of your 0909 build and my flo 14.1 with a dirty flash of your 0907 build. Everything went smoothly, both running fine. There have been no other updates to these roms since May so you've kept both my daily drivers going. Thanks again for the good work.
anivegmin said:
Thanks very much. Just updated my hammerhead 15.1 with a dirty flash of your 0909 build and my flo 14.1 with a dirty flash of your 0907 build. Everything went smoothly, both running fine. There have been no other updates to these roms since May so you've kept both my daily drivers going. Thanks again for the good work.
Click to expand...
Click to collapse
No worries, glad I could help. New builds will appear weekly, early Sunday morning Tokyo time. If there are other legacy/sustaining platforms you'd like to see, please let me know and I'll add them to the build roster.
wileyc said:
For what it's worth, I've added hammerhead to my build roster. Weekly hammerhead builds for 15.1, using a pristine LineageOS source tree (no modifications whatsoever), are at https://lineageos.disavowed.jp/hammerhead/.
Click to expand...
Click to collapse
What about 16? Can you add it too?
Kotaless said:
What about 16? Can you add it too?
Click to expand...
Click to collapse
Sure. I just verified that the 16 branch successfully builds; I've added to the weekly build roster and copied my test build to the server.
Please understand that I have not tested 16 on hammerhead at all, and probably won't for the time being. I added it to the roster because I have the storage space and spare compute cycles; if it doesn't work, please ask the folks with commit access to the LineageOS source tree to pull in the appropriate fixes and my build infra will automatically pull it in the next cycle.
Cheers
wileyc said:
For what it's worth, I've added hammerhead to my build roster. Weekly hammerhead builds for 15.1, using a pristine LineageOS source tree (no modifications whatsoever), are at (omitted).
Click to expand...
Click to collapse
Great work! :good: I'm now running your 15.1 image and works almost perfectly (bluetooth audio calls not working).
Would be great if there was someone brave enough to test the 16 image
__iro__ said:
Great work! :good: I'm now running your 15.1 image and works fine! (Bluetooth calls not yet tested though)
Would be great if there was someone brave enough to test the 16 image
Click to expand...
Click to collapse
I've been testing this LOS 16 on a second Nexus 5 that I have.
https://forum.xda-developers.com/google-nexus-5/orig-development/rom-lineageos-16-0-nexus-5-t3921162
https://sourceforge.net/projects/nexus5oof/files/LineageOS/
Everything seems to work, I'm just getting a general lag (especially with google apps) as compared to 14.1 and 15.1. I'll keep testing and if latency/lag improves I'll definitely be replacing 15.1 as my daily driver.
I'm assuming the LOS 16 in wileyc's repository is the same build? Maybe not, I'm not sure how these things work.
wileyc said:
Sure. I just verified that the 16 branch successfully builds; I've added to the weekly build roster and copied my test build to the server.
Please understand that I have not tested 16 on hammerhead at all, and probably won't for the time being. I added it to the roster because I have the storage space and spare compute cycles; if it doesn't work, please ask the folks with commit access to the LineageOS source tree to pull in the appropriate fixes and my build infra will automatically pull it in the next cycle.
Cheers
Click to expand...
Click to collapse
I dirty flashed it over EnesSastim's LOS 16 but sadly it doesn't boot. Thanks anyway.
Dirty flashed wileyc's flo 0914 build onto my Nexus 7. Everything running fine with September security patch.
Kotaless said:
I dirty flashed it over EnesSastim's LOS 16 but sadly it doesn't boot. Thanks anyway.
Click to expand...
Click to collapse
Argh, that's too bad. Thanks for letting me know -- I've removed 16 from the build roster for hammerhead.
Have now flashed 0914 builds of LOS 14.1 and LOS 15.1 onto my Nexus 7 and Nexus 5 respectively. Everything running perfectly with latest September security patches. Thanks again to @wileyc for providing these builds and keeping my 6 year old devices up to date and running smoothly.
So, for what it's worth ... 15.1 broke on multiple devices, including hammerhead, sometime last week. I put a brief writeup here.
Hi, i downloadet the last ROM file: lineage-15.1-20200303-UNOFFICIAL-hammerhead.zip from: https://lineageos.disavowed.jp/hammerhead/
I Flash it, but when i flash OpenGAPPS: open_gapps-arm-8.1-nano-20200311.zip
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 8.1.0
ROM Build ID | lineage_hammerhead-userdebug 8.1.0 OPM7.181205.001 39eb443102 test-keys
ROM Version increment | 39eb443102
ROM SDK version | 27
ROM/Recovery modversion | 15.1-20200303-UNOFFICIAL-hammerhead
Device Recovery | TWRP 3.2.2-0-fac1b383
Device Name | hammerhead
Device Model | Nexus 5
Device Type | phone
Device CPU | armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm
Display Density Used | 480
Install Type | Dirty[Data NOT Wiped]
Smart ART Pre-ODEX | false
Google Camera already installed | false
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | true[whitelist]
Google Pixel Features | false
Current GApps Version | No GApps Installed
Runtime Permissions | Reset
Installing GApps Zipfile | /sdcard/00 Mods/open_gapps-arm-8.1-nano-20200311.zip
Installing GApps Version | 20200311
Installing GApps Type | nano
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | false
Ignore Google WebView | false
Total System Size (KB) | 1033516
Used System Space (KB) | 765524
Current Free Space (KB) | 267992
Additional Space Required (KB) | 17660 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 267992 | 267992
Remove | Existing GApps | + 0 | 267992
Remove | Obsolete Files | + 0 | 267992
Remove | cmsetupwizard | + 0 | 267992
Remove | extservicesstock | + 16 | 268008
Remove | extsharedstock | + 12 | 268020
Remove | packageinstallerstock | + 5928 | 273948
Remove | provision | + 0 | 273948
Install | Core | - 103724 | 170224
Install | batteryusage | - 1324 | 168900
Install | calsync | - 2856 | 166044
Install | dialerframework | - 12 | 166032
Install | googletts | - 24764 | 141268
Install | packageinstallergoogle | - 5692 | 135576
Install | search | - 104892 | 30684
Install | speech | - 39128 | -8444
| Buffer Space | - 9216 | -17660
------------------------------------------------------------------
Additional Space Required | 17660
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Click to expand...
Click to collapse
How i can fix it?
Only: open_gapps-arm-8.1-pico-20200311.zip works fine
EDIT:
https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
An all works fine!!
Nice to see all these builds from wileyc. Unfortunately my hammerhead is broken (damaged connector on the motherboard), so I can't contribute much anymore.
Just put a new battery in the Hammerhead! Let's go!
ChongoDroid said:
Just put a new battery in the Hammerhead! Let's go!
Click to expand...
Click to collapse
My battery health is 50%, where did you get the battery from, do you have a link? thanks
Hi all, sorry in advance as I suspect is a silly question but here it goes: what Android version is Lineage 15.1 based on?
Thanks!
Android 8.1, Oreo
{
"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
ABOUT
ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
Blog: blog.arrowos.net
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
Flashing GApps in recovery for vanilla build doesn't work, either use WeebGapps Magisk module or Lite Gapps
Hotspot
Be sure to include a log : check how to
FLASHING STEPS
•Make sure you are on 12.0.1.0 and above firmware to flash ROM.
•Reboot Recovery (Use the recovery on download section to flash ROM)
•Flash Rom
•Format data
•Reboot System
•Once you see Bootanimation, Hold the power button to force reboot (To avoid bootloop on first boot)
DOWNLOADS
Download Vanilla Build
Download GApps Build
Download RECOVERY
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/Redmi-MT6768
Telegram: Channel | Group
CONTRIBUTORS
Communos
Firas
Reserved
wow pro god sir
rsyforreal said:
wow pro god sir
Click to expand...
Click to collapse
wow pro god sir
im doing all the recomendation but after install rom ,format data and reboot the phone boot into fastboot mode.
Ragod45 said:
im doing all the recomendation but after install rom ,format data and reboot the phone boot into fastboot mode.
Click to expand...
Click to collapse
I did! it booted fine, is there a gapps to install for this version?
Hmm... all I see is a neverending blue and white arrow symbol.
Ragod45 said:
is there a gapps to install for this version?
Click to expand...
Click to collapse
With the OpenGapps test builds for Android 11, or the NikGapps, the installer always complained about not enough space on the system partition, even though it was already the smallest package (pico/core).
Only the FlameGapps basic package installed without errors on my device, but since it doesn't boot, I can't tell you if it actually works.
Here's the log from the OpenGapps pico package:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | RQ1A.210205.004
ROM Version increment | eng.ebincr.20210225.160609
ROM SDK version | 30
ROM/Recovery modversion | v11.0
Device Recovery | TWRP 3.4.2b-1213-c4a6db32
Device Name | merlin
Device Model | M2003J15SC
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 440
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /external_sd/Download/open_gapps-arm64-11.0-pico-20210130-TEST.zip
Installing GApps Version | 20210130
Installing GApps Type | pico
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | false
Total System Size (KB) | 1186384
Used System Space (KB) | 971236
Current Free Space (KB) | 198764
Additional Space Required (KB) | 25676 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 198764 | 198764
Remove | Existing GApps | + 0 | 198764
Remove | Obsolete Files | + 56 | 198820
Remove | extservicesstock | + 0 | 198820
Remove | extsharedstock | + 52 | 198872
Remove | packageinstallerstock | + 3284 | 202156
Remove | provision | + 0 | 202156
Install | Core | - 174976 | 27180
Install | calsync | - 2556 | 24624
Install | dialerframework | - 32 | 24592
Install | googletts | - 37896 | -13304
Install | packageinstallergoogle | - 3156 | -16460
| Buffer Space | - 9216 | -25676
------------------------------------------------------------------
Additional Space Required | 25676
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
MyBrainIsAStrainer said:
Hmm... all I see is a neverending blue and white arrow symbol.
With the OpenGapps test builds for Android 11, or the NikGapps, the installer always complained about not enough space on the system partition, even though it was already the smallest package (pico/core).
Only the FlameGapps basic package installed without errors on my device, but since it doesn't boot, I can't tell you if it actually works.
Here's the log from the OpenGapps pico package:
Code:
# Begin Open GApps Install Log
------------------------------------------------------------------
ROM Android version | 11
ROM Build ID | RQ1A.210205.004
ROM Version increment | eng.ebincr.20210225.160609
ROM SDK version | 30
ROM/Recovery modversion | v11.0
Device Recovery | TWRP 3.4.2b-1213-c4a6db32
Device Name | merlin
Device Model | M2003J15SC
Device Type | phone
Device CPU | arm64-v8a,armeabi-v7a,armeabi
Device A/B-partitions | false
Installer Platform | arm
ROM Platform | arm64
Display Density Used | 440
Install Type | Clean[Data Wiped]
Google Camera already installed | Clean
VRMode Compatible | false
Google Camera Compatible | true
New Camera API Compatible | false
Google Pixel Features | false
Current GApps Version | No GApps Installed
Google Camera version | Legacy
Installing GApps Zipfile | /external_sd/Download/open_gapps-arm64-11.0-pico-20210130-TEST.zip
Installing GApps Version | 20210130
Installing GApps Type | pico
Config Type |
Using gapps-config | Not Used
Remove Stock/AOSP Browser | false[NO_Chrome]
Remove Stock/AOSP Camera | false[NO_CameraGoogle]
Remove Stock/AOSP Dialer | false[NO_DialerGoogle]
Remove Stock/AOSP Email | false[NO_Gmail]
Remove Stock/AOSP Gallery | false[NO_Photos]
Remove Stock/AOSP Launcher | false[NO_GoogleNow/PixelLauncher]
Remove Stock/AOSP MMS App | false[NO_Messenger]
Remove Stock/AOSP Pico TTS | false[default]
Ignore Google Contacts | false
Ignore Google Dialer | true[NoRemove]
Ignore Google Keyboard | false
Ignore Google Package Installer | false
Ignore Google NFC Tag | true[NoRemove]
Ignore Google WebView | false
Total System Size (KB) | 1186384
Used System Space (KB) | 971236
Current Free Space (KB) | 198764
Additional Space Required (KB) | 25676 << See Calculations Below
------------------------------------------------------------------
# End Open GApps Install Log
INSTALLATION FAILURE: Your device does not have sufficient space available in
the system partition to install this GApps package as currently configured.
You will need to switch to a smaller GApps package or use gapps-config to
reduce the installed size.
NOTE: The Stock/AOSP NFC Tag is not available on your
ROM (anymore), the Google equivalent will not be removed.
NOTE: The Stock/AOSP Dialer is not available on your
ROM (anymore), the Google equivalent will not be removed.
# Begin GApps Size Calculations
------------------------------------------------------------------
TYPE | DESCRIPTION | SIZE | TOTAL
| Current Free Space | 198764 | 198764
Remove | Existing GApps | + 0 | 198764
Remove | Obsolete Files | + 56 | 198820
Remove | extservicesstock | + 0 | 198820
Remove | extsharedstock | + 52 | 198872
Remove | packageinstallerstock | + 3284 | 202156
Remove | provision | + 0 | 202156
Install | Core | - 174976 | 27180
Install | calsync | - 2556 | 24624
Install | dialerframework | - 32 | 24592
Install | googletts | - 37896 | -13304
Install | packageinstallergoogle | - 3156 | -16460
| Buffer Space | - 9216 | -25676
------------------------------------------------------------------
Additional Space Required | 25676
------------------------------------------------------------------
# End GApps Size Calculations
# Begin User's gapps-config
# End User's gapps-config
Click to expand...
Click to collapse
Due to dynamic partition, the system gets resized after you flash system and reboot, leaving no space for gapps, so flash gapps before first boot, or you could use Magisk module gapps, here's the link:
https://drive.google.com/uc?id=1JBeuXQsHXy-T5hFcxmRQFBwh5yRRnKf1&export=download
Also note that first boot is a bootloop, you need to force reboot after waiting a minute or so
Please let me know if you still have issues, I'll fix them in next build.
Hi, i just tried again, installed rom, installed magisk and booted sucessfully without bootloops.
FLAME,OPEN and NIK GAPPS wont work at all!
after the system booted, i updated magisk and installed magisk module gapps. after reboot, i tried to open the google store but got stuck on logo from the app and thats it. so ill be waiting for next build to see if we got some bug fixes. thanks for the hard work !
Ragod45 said:
Hi, i just tried again, installed rom, installed magisk and booted sucessfully without bootloops.
FLAME,OPEN and NIK GAPPS wont work at all!
after the system booted, i updated magisk and installed magisk module gapps. after reboot, i tried to open the google store but got stuck on logo from the app and thats it. so ill be waiting for next build to see if we got some bug fixes. thanks for the hard work !
Click to expand...
Click to collapse
I see, thanks for reporting, I'll fix this in next build, stay updated
Communos said:
so flash gapps before first boot
Click to expand...
Click to collapse
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
or you could use Magisk module gapps, here's the link:
https://drive.google.com/uc?id=1JBeuXQsHXy-T5hFcxmRQFBwh5yRRnKf1&export=download
Click to expand...
Click to collapse
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
Please let me know if you still have issues, I'll fix them in next build.
Click to expand...
Click to collapse
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd. EDIT: Ok, I have reinstall ArrowOS, but this time, I formatted the partitions first in TWRP. Now I have the full storage available. Man, there are so many little thing to keep track of.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
MyBrainIsAStrainer said:
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
Click to expand...
Click to collapse
The 8gb storage issue is peculiar, No one complained about any issue like this in the telegram group.
For the WeGo navigation app, can you please record logs while it starts and freezes? Would make it easier to briefly look over the issue.
I'll look over everything you reported, and try to fix them.
Logs would be highly appreciated.
Communos said:
The 8gb storage issue is peculiar, No one complained about any issue like this in the telegram group.
Click to expand...
Click to collapse
Looks like your reply overlapped with my edit. I think I fixed it by reinstalling ArrowOS. But this time, I used the "Format Data" option in TWRP's wipe menu beforehand. That gave me the full storage.
For the WeGo navigation app, can you please record logs while it starts and freezes? Would make it easier to briefly look over the issue.
Click to expand...
Click to collapse
Attached is the 'adb logcat' output from changing the storage to the third restart attempt (this time, it didn't freeze but crashed). I hope it's what you wanted. I'm new at this. If you need something else, let me know.
I just noticed that encrypting the phone does not work. If you select it, the device enters into a reboot loop (blank screen -> Redmi logo -> blank screen -> Redmi logo -> ...).
I don't think I can give you a log, because at that stage, adbd isn't running yet. If there's a way to get any helpful info on that, let me know.
On miatoll (Redmi Note 9 Pro, exactly) the mic does not turn on during phone calls.
Before clean-flashing this rom I installed the most recent firmware
( fw_joyeuse_miui_JOYEUSEEEAGlobal_V12.0.2.0.QJZEUXM_53af718a4c_10.0.zip )
Another ROM (Fluid 1.2) does not have the problem, nor the stock ROM, so I know the hardware is good . . .
Any advice would be appreciated!
This rom build is NOT for Miatoll, Redmi Note 9 with HelioG85 does not come under Miatoll category.
fbachofner said:
On miatoll (Redmi Note 9 Pro, exactly) the mic does not turn on during phone calls.
Before clean-flashing this rom I installed the most recent firmware
( fw_joyeuse_miui_JOYEUSEEEAGlobal_V12.0.2.0.QJZEUXM_53af718a4c_10.0.zip )
Another ROM (Fluid 1.2) does not have the problem, nor the stock ROM, so I know the hardware is good . . .
Any advice would be appreciated!
Click to expand...
Click to collapse
Please reach out to your device maintainer and report the bugs to him/her.
geht dieses rom auf das merlinnfc gerät oder nicht.
Raymen03 said:
geht dieses rom auf das merlinnfc gerät oder nicht.
Click to expand...
Click to collapse
it works on nfc
New FINAL ArrowOS Update is up!
Download: arrow_merlin-gapps.zip
Changelogs:
- This build is a followup build of previous ArrowOS build.
- GApps Included
- Fixed few minor bugs
MyBrainIsAStrainer said:
That is what I did. I installed ArrowOS with OpenGapps as an additional ZIP. ArrowOS installs fine, then the installer for OpenGapps says there isn't enough room on the system partition and exits with error code 70.
Only the FlameGapps install without error, but then the system won't start (endless ArrowOS logo).
That one sort of works, but there seem to be a few stability issues. I often get the message that the Google Play services had repeatedly crashed. Play Store works fine for me, although I had to restart the app once.
All in all, it seems usable, but I'm not sure it's reliable.
So far, I encountered only minor issues. Like some developer settings that are present in other ROMs but seem to be missing here:
I can't find an option to enable adb root access. Running 'adb root' anyway prints the error: "adbd cannot run as root in production builds".
There's also no option to enable the extended restart (where you can select if you want to boot into recovery, bootloader, or normal system). I also can't take a screenshot from the restart menu. Stuff like that isn't critical, but helpful for people like me who can't remember all the different key combos.
One weird problem I encountered is with Here WeGo (a navigation app from the Play Store that I like because you can use it offline). At first, it works fine. But when you then tell it to use the SD card for those offline maps (and not the precious internal memory), the apps freezes every time it tries to start. You have to uninstall and reinstall it to make it lose its settings and work again. I guess I can use it with the internal storage for now, but it does cost me ~1.5 GB that I could find other uses for. Again, I'm not sure if this is your build's fault, but it worked on every other ROM and phone I've tried so far. In case it's important: I get no permission request for the SD card when I switch the storage in the app.
And while I'm at it: Any idea why the internal storage is only 8 GB total? I bought the device with 64 GB. I understand that there's bound to be some overhead for A/B stuff, recovery, and whatnot, but I've lost almost an order of magnitude here. It seems odd. EDIT: Ok, I have reinstall ArrowOS, but this time, I formatted the partitions first in TWRP. Now I have the full storage available. Man, there are so many little thing to keep track of.
Obviously, I haven't had the time yet to put the ROM through all its paces, but so far, I'm pretty impressed with it. I have not run into any game-breakers so far. You did a good job.
Click to expand...
Click to collapse
I tried the WeGo app on new build, seems like a source issue, I guess I can't fix it
riceDroid for OnePlus 8T|9R [kebab][lemonades]
View attachment 5815623
What is riceDroid?
* Ricedroid is a FREE OPENSOURCE Android Operating System based on LineageOS and crDroid, that aims to provide necessary "ricing" aka customizations for ANDROID while being fast and stable. This operating system is highly inspired by Oxygen OS (10-11) and nothingOS, we strive to make things different but not too far from AOSP.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The term \'rice\' is used to describe a person's unix desktop where \'ricing\' is an act where someone customizes their desktop such as the changing icons, panels or system interface.
source: https://jie-fang.github.io/blog/basics-of-ricing
Based on Android 13 | Tiramisu QPR1
What's working?
Most basic stuffs
Bugs and Issues
Please tell me with a logcat attached
Variants available
CORE build only - comes with basic gapps, no setupwizard
Device specific changes
Based on OOS 12 Firmware, Flashing OOS 12 firmware is a must before installing, boots on OOS13 firmware but touchscreen doesn't work
Shipped with OOS Camera - most features exposed working.
Shipped with Chaeyo.0 kernel - based from OOS 12 kernel source - CFS scheduler focused kernel.
Credits
LineageOS kebab team - for most of device/kernel tree changes
chandu078 - base device/vendor tree
cjh1249131356 - oneplus camera source
Notes
I will only maintain Official GMS core variant based on OOS 12 due to limited free time. Other variants will be officially maintained by sir manidreddy a.k.a Lord Itachi
If you have any type of concerns, please address it here, I'll try to accommodate as soon as I see the message.
Changelog
Source Changelog
Download link
riceDroid-13.0-202301210506-kebab-v10.1-CORE-OFFICIAL.zip
Installation Guide
Fastboot - recommended method
Download SDK platform tools here and follow this tutorial
Reboot to fastboot
Enter fastboot mode
Perform flashing commands listed on attached file: fastboot-commands
Enter recovery mode
Wipe data/cache/dalvik-cache
Sideload preferred zip files (magisk, gapps etc.)
Reboot to system
Sideload - recommended for those who were able to flash oos 12 on A/B slots
Fastboot flash recovery.img from firmware payload.bin
Reboot device into recovery mode
Enter ADB sideload mode
adb sideload ROM.zip
Wipe data/cache/dalvik-cache
Sideload preferred zip files (magisk, gapps etc.)
6. Reboot to system
Android OS version: 13.0.0_r24
Security patch level: January 2023
Build author/Device Maintainer: dlwlrma123
Device tree source code: https://github.com/ricedroidOSS-devices/device_oneplus_kebab
Device vendor source code: https://github.com/ricedroidOSS-devices/vendor_oneplus_kebab
Kernel source code: https://github.com/ricedroidOSS-devices/android_kernel_oneplus_sm8250
Firmware source code: https://github.com/ricedroidOSS
Firmware created by: The ricedroidOSS Team
Reserved for changelog purposes.
Bro! I love this rom. Working amazing without any problem. But remember, IU a.k.a Lee Ji-eun is mine (my). Rest is everything fine.
Currently I am on Elixir OS android 13 based so can I directly flash ricedroid over it ? Or do I have to roll back to oxygen os 12?
Can anyone help please ?
therajatshahare said:
Bro! I love this rom. Working amazing without any problem. But remember, IU a.k.a Lee Ji-eun is mine (my). Rest is everything fine.
Click to expand...
Click to collapse
Can you share the download link please?