Hey everyone
So... because i rather made a "big" of breakthrough today, im gonna share my progress on various projects.
My progress on LineageOS 15.1 (and GZOSP and CrDroid, didnt try more yet) all work pretty fine, basically everything works. Theres just 1 annoying thing (which im hunting down since easter). It can crash rather often during boot. Means: it freezes and then reboots.
See for yourself:
https://www.youtube.com/watch?v=rUUopOYDYjs:
https://youtu.be/l7HEMIreVwE:
A video of CrDroid (recorded with my OnePlus 2 lol)
https://youtu.be/d5XGM9xCrqE:
I also managed to create a seperate vendor partition (yes, i actually repartitioned) by making /system smaller (had 1.5GB left even though on full stock rom, not debloated a single bit). Made it 512MB in size.
This allowed me to actually use it (mount in kernel), and i managed to (nearly) bring Treble support to the V30
With nearly i mean that the GSI boots, but the process "system" crashes (2 libs missing, need to see how i get them to /vendor, currently they are in /system of my lineage build)
The libs are called [email protected] and [email protected]
Here a video of LOS15.1 with Treble Check (yes, that prop can be faked, i know, and its only half true so far i guess)
https://youtu.be/MUNij0sspKM:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
2) share my progress, making people hope that the V30 development isnt completly dead
3) Hopefully get a the attention of a few more devs, so we can figure those boot issues out (the reason i didnt release it yet, as it sometimes also freezes when you have gapps flashed)
best regards
SGCMarkus
PS: Ask all the devs you know, maybe someone knows the issue too, and knows a way to fix it
PPS: idk why the embedded youtube links dont work, but i put the links there on their own
Expect it to be used everyday! Beautifully
Wow good work. Hopefully tmobile varient will get recovery someday [emoji849] miss experimenting with roms. Stock on v30 is good with a theme but sometimes i miss custom roms
Sent from my LG-H932 using Tapatalk
So.. tested a build from last night fast before i rushed to the train ?
The GSI now boots successful and seems to be stable. Everything except haptic feedback/vibrator seems to work (i know the reason for that, as it loads the aosp implementation first, but the v30 needs the lge implementation in vendor)
Only saw wifi, bt, nfc was on, had signal (and asked for sim pin), and checked if camera had a preview, it did
{
"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"
}
Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess
Doblix said:
Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess
Click to expand...
Click to collapse
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)
SGCMarkus said:
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)
Click to expand...
Click to collapse
I would be interested in testing the treble ones if possible, if you can guide me how to do the repartitioning or what tools to use that would be no problem for me.
I solely use Linux on my PCs (Arch if that matters) so that is no obstacle for me.
A nice and user solution would probably be a flashable .zip file for TWRP which does the repartitioning directly on the device.
Excited
I'm really excited to get Lineage OS onto my V30. But I just don't think I can make the transition until the Camera is ported. The the only app which can utilize both sensors, 4k video recording and laser focus. I use the ported G camera for pictures right now because of HDR+, and it can record 240fps slow mo. But it can't record 4K video. There is just nothing which can fully replace the stock LG app and use all the camera's hardware properly. Even things like open camera can't use Laser focus. So I just can't make the switch until the LG camera is ported. Also I hope that the QuadDAC will be supported.
GSIs also dont seem to have the boot issues for some reason....
So its neither the ramdisk, nor kernel, nor vendor files.... something in my device tree is wrong then xD
PS: added a poll
Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!
Just wanted to add my 2 cents. Definitely extremely excited about a fully stable and working LineageOS. Even if it doesn't have Trebble. Stability is definitely a must (at least for me) since this phone is a daily driver, but I would love more than words could convey if we had a working AOSP type ROM for this phone. Please keep up the solid work, and thank you in advance! As a dev myself (not android, sorry) who has done volunteer work, I know how important the props are to keep you motivated. So again, awesome job so far, and thank you!
okaiuz said:
Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!
Click to expand...
Click to collapse
All GSIs should work, currently booted a LineageOS GSI, also tried the AOSP one
PS: found the fix for the vibrator... LGs implementation is just stupid lol
Needs ro.product.manufacturer set to LG or LGE, but GSIs dont have that.... only ro.vendor.product.manufacturer is set to LGE, but that isnt enough...
SGCMarkus said:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
Click to expand...
Click to collapse
Hey SGCMarkus,
First Off.... Amazing Work!!!!! Rly nice to see, that there is some developing going on. Cant explain, why this phone is like beeing dead to devs.
To get to the Point... I would imediately Stop setting Up my Linux Dev system and would Test 4 you. It is more important to Help the community getting some kickass Roms rather cooking for myself
If you are interested, Just leave me a PN with dl-link and additional Infos.
So Long,
Please keep Up that great Work.
Tipnuck
Related
Who can build it ??
I could try to Boot it up. Not More. So it have enough bugs for daily use. *troll*
I've been wanting to take a jab at it for some time, but I've been so busy with school especially now with finals coming up. But once finals are over and I'm on break I'll see what I can do.
We got the official cm 12.1 that went to trash more than a year ago. I doubt you sew CM 13.
Sent from my LG-H811 using XDA-Developers mobile app
duongthinh441 said:
Who can build it ??
Click to expand...
Click to collapse
I just started. I am noob with ROM development. Even if I do this would be my first ROM. So dont get your hopes hight. Please let me know if you can help me out with pointers to guides. Just syncing the CM13 repo.
DroidSK said:
I just started. I am noob with ROM development. Even if I do this would be my first ROM. So dont get your hopes hight. Please let me know if you can help me out with pointers to guides. Just syncing the CM13 repo.
Click to expand...
Click to collapse
You can build cm 13???
Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk
DroidSK said:
Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk
Click to expand...
Click to collapse
Yes thanks bro . yeah i think it run on gpro device
DroidSK said:
Like i said ... Just started. Not sure what i will run into. Will definitely post if i am successful.
Sent from my FIND7 using Tapatalk
Click to expand...
Click to collapse
You have to work ?
Yes i have to work. Will work on this during the weekend.
Sent from my FIND7 using Tapatalk
this is one of the problems with 6.0 on GPRO provided by dev
"I'll be honest: I needed just few more weeks with working USB to get Marshmallow fully functional. I got it running on E988, but some important stuff was broken, thus, device was unusable.
I got it to boot without SELinux - device tree needs new set of rules/fixes on current ones, because some old QCOM rules are dropped from vendor repos since mako isn't officially supported for M. That was ~90% fixed.
There were other problems which made device useless: modem and sensors - main reasons I haven't finished what I started. I had issues with reboots by DSP subsystem on every damn build, and just before my USB died, while experimenting with kernel and init files, I got an idea to disable modem and sensors services (they were causing DSP subsystem reboots) and boom, Marshmallow booted. Managed even to login to my Google account, install apps, use it for a while but had to revert back to LP - main phone without working modem is a tablet, not a phone Unfortunately, some time after that my USB decided to become just a simple charging port, so job was left unfinished.
So whoever is willing to tackle this issue:
- GPU drivers need update, both ion and gpu/msm update (kernel) and libs (need newer libs from mako/flo)
- Modem and sensors HAL need some updating - possibly only libs should be updated, since there were no changes in msm8960/apq8064 3.4 kernels connected to drivers
- Some SELinux stuff needs to be fixed
- Our device is stuck with OpenSSL, Marshmallow uses BoringSSL which has crippled some OpenSSL symbols, so there are some compatibility modules with missing symbols which need to be written... at least, that had to be done back then. Not sure now, it's nearly 5 months later now. Missing symbols can be the reason why both current and Lollipop (kanged from F240) modem/sensors didn't work, I really haven't managed to get usable logs before device's total freeze and reboot with these two services on, so whoever fixes this, well, gets functional Marshmallow
- Camera HAL, our issue since last KitKat days "
But haven't cm13 source code from cyanogenmod
I got some news for you all:
{
"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"
}
Just booted it. No modem, no network, no GPS, no camera, no sensors. It just boots.
Wow!!!
This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
EDIT: Crash is caused by sensors; disabling sensors service in init removes that crash, gets firmwares loaded but... that doesn't help our RIL, not at all. And of course there are no error messages from RIL, absolutely none to be found - dmesg simply states "rild-service crashed", logcat is flooded with NFC crashes so I simply don't have nerves to go through all of that... Gah. I really love this device.
Also, I've spotted an interesting problem - I've fixed fstab, both storages are visible, but it seems like I don't have access to external SD - probably something missing somewhere. Also, I think that kernel needs some more commits (I've patched it enough to get SELinux and GPU going, picking anything other than that causes too much conflicts and build issues... and I'm not even using ShadyKernel as a base, started from clean CM12.1 kernel), so I'll try patching google's kernel_msm for E980 support (from KK source drop). possibly something else is broken... who knows? Better question is what isn't broken, lol.
I'll fix that once I get RIL and sensors working. Other than that, Marshmallow is really nicely working on E980, it just needs a lot of work, and a bit more knowledge than I have... well, time to learn.
Whoever is willing to join, kernel is available on my github (lge-kernel-gproj, branch cm-13.0). Device tree and vendor files aren't still uploaded (there are bunch of changes I haven't committed yet), so you may want to wait for them...
Try bro !!
ShadySquirrel said:
This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
Click to expand...
Click to collapse
Thx for still be trying!
Thanks---I'd love for this to work so I have a viable spare brought back from the dead!
ShadySquirrel said:
This device is unbelievable... I've fixed most of selinux rules, fixed missing symbols for RIL - had it crashing only because it couldn't load dsps firmware, and same second I've fixed that, BOOM - kernel panic, reboot. Reason? DSPS subsystem crash... grrrrrrrrrrrr...
EDIT: Crash is caused by sensors; disabling sensors service in init removes that crash, gets firmwares loaded but... that doesn't help our RIL, not at all. And of course there are no error messages from RIL, absolutely none to be found - dmesg simply states "rild-service crashed", logcat is flooded with NFC crashes so I simply don't have nerves to go through all of that... Gah. I really love this device.
Also, I've spotted an interesting problem - I've fixed fstab, both storages are visible, but it seems like I don't have access to external SD - probably something missing somewhere. Also, I think that kernel needs some more commits (I've patched it enough to get SELinux and GPU going, picking anything other than that causes too much conflicts and build issues... and I'm not even using ShadyKernel as a base, started from clean CM12.1 kernel), so I'll try patching google's kernel_msm for E980 support (from KK source drop). possibly something else is broken... who knows? Better question is what isn't broken, lol.
I'll fix that once I get RIL and sensors working. Other than that, Marshmallow is really nicely working on E980, it just needs a lot of work, and a bit more knowledge than I have... well, time to learn.
Whoever is willing to join, kernel is available on my github (lge-kernel-gproj, branch cm-13.0). Device tree and vendor files aren't still uploaded (there are bunch of changes I haven't committed yet), so you may want to wait for them...
Click to expand...
Click to collapse
LG got a lot of G/Gpro hacks in our current ~LP kernel. You'd probably have an easier time porting what ever changes you needed from the other kernel you're referencing, to our current kernel. Rather than starting fresh. However if sometimes starting fresh is a lil easier if another similar device has done it already, and you have something to hold onto. I wish I could actively help your efforts but apart from not having a booting computer rn lol, school ain't no joke. I'm a senior now and I'm still tryna master my ACT score and start applying for colleges soon
Emmanuel U said:
LG got a lot of G/Gpro hacks in our current ~LP kernel. You'd probably have an easier time porting what ever changes you needed from the other kernel you're referencing, to our current kernel. Rather than starting fresh. However if sometimes starting fresh is a lil easier if another similar device has done it already, and you have something to hold onto. I wish I could actively help your efforts but apart from not having a booting computer rn lol, school ain't no joke. I'm a senior now and I'm still tryna master my ACT score and start applying for colleges soon
Click to expand...
Click to collapse
I do have CAF based kernel (LA.AF.1.1_rb8 + LG patches from Lollipop sources - believe it or not, LG pushed sources for E98x together with F240x ones), ready and booting. It was easier working on that than patching existing one - I don't want to spend few weeks just patchibg things up, like I had for lollipop and gpu driver backport... That kernel is 5.0.2 ready, just have to figure out from where does CM patch those - stuff isn't only from kernel_common... so I'm thinking about similar thing now - google_msm (everything is already there) + kitkat drop patchup, just to get camera and board going.
Our device tree is also a mess, part mako, part Optimus G. Missing lots of things (have you ever unpacked stock boot.img? Damn those inits...) Started working on pure G Pro tree, but that will have to wait for a bit - there is bit too much work, and I have studies to finish, lol. Just lets hope that my USB won't die again, since "fix" I've applied is kind of temporary.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.0 (Oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Hotspot
Flash
GPS
What's not working :
Boot doesnt work all the time (just dont reboot the phone, i guess)
GSIs (Generic System Images) work fine though for some reason
DAC(?)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions :
Download the build
If you dont have a vendor partition yet, create one GUIDE
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Here
H932 Build
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-15.1-treble branch
XDA:DevDB Information
LineageOS 15.1 - Treble, ROM for the LG V30
Contributors
SGCMarkus, rashed97
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-10-03
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that, same for vendor
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/Linea..._base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 22.07.2018
- Updated blobs to H930 V20R
- fixed vibration becoming dull after a while
- all other past changes from normal LOS since last update here
- updated source
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a
- Vibration motor ready for P GSIs
Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Does this work on the US998?
A. Hasn't been tested yet. Try it out and report (but make a backup first as always).
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
okaiuz said:
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
Click to expand...
Click to collapse
The reboot problems only occur with the 2 LineageOS builds, not with GSIs (or i was just really extremly lucky, but i doubt that).
On LOS i have a ~20% boot chance (did once 35 boot tries after another...), and on GSIs it boot always like 6 or 7 times after another. Suppose it works there, really unlikely i was that lucky lol
The GSI of LOS by phhuson also works btw (just no double tap 2 wake).
I would actually love to make way more ROMs.... I even had a CrDroid test build once (to check if its only LOS with that problem), but sadly im out of space now.... dont have more space than for LOS :/
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
okaiuz said:
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
Click to expand...
Click to collapse
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
SGCMarkus said:
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
Click to expand...
Click to collapse
i have to thank you again for you work!
Thursday i'll try to partition my v30+ and try your treblelized los!
i give a chance even to phh los, aosp and rr!
i 'll yo know my experience, hoping that you can fix the boot problem!
Regards!
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
donky kong 017 said:
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
Click to expand...
Click to collapse
Use Viper4Android and the predicament is solved.
Nikola Jovanovic said:
Use Viper4Android and the predicament is solved.
Click to expand...
Click to collapse
does viper use the quad DAC. AFAIK no. ATM i use the V30 Quad DAC and Ainur Sauron
As it also counts for this, i will simply refer to my post in the other LOS thread
https://forum.xda-developers.com/showpost.php?p=76536335&postcount=20
you're the best!
tnx to phh also!
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
elba96 said:
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
Click to expand...
Click to collapse
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
SGCMarkus said:
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
Click to expand...
Click to collapse
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
okaiuz said:
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Click to expand...
Click to collapse
Yes, you can still use the non treblelized version
Still working on adding features though, fixing major bugs first ^^
Doblix said:
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
Click to expand...
Click to collapse
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
elba96 said:
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
Click to expand...
Click to collapse
My testers say its ready for daily usage
Couldnt test for battery life yet myself. Didnt have the time to setup everything a new... University life is tough
SGCMarkus said:
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
Click to expand...
Click to collapse
Yes vendor is listed there and I could also format it. I am at university right now and reverted to stock to be able to use it (which can be flashed fine btw.), I will see when I find the time to flash again and post the log here then.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SailfishOS for ASUS Zenfone 5Z by VerdandiTeam
Warning: Flashing this may void your device’s warranty, lead
to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore
must be done entirely at your own risk. No one affiliated with this project is responsible for your
actions but yourself.
Click to expand...
Click to collapse
THIS IS NOT ANDROID NOR THERE IS ANY ANDROID APP SUPPORT. GO USE GNU OR SOMETHING
Not working:
Camera recording (in progress but i wanted to share the sfos with yall already)
Use advanced camera from openrepos if you want wide angle (jolla didn't get to add it to stock camera yet)
calls are untested altho should work
GPS is untested (probably works too)
INSTALL:
Strap in for a ride, if at any step you don't know what you are doing, you better give up and stay on android. If i'm doing something incorrectly then tell me but i've been fighting over 3 days just to get lineage and twrp working… but maybe i'm just stoopid
If you can install provided lineage 17.1 on slot a then you don't need these instructions and jump to flashing sfos:
I couldn't find any valid tutorial on getting stock android 10 but i've found stock fastbootable image somewhere (yes, don't trust it lol) so i will share it with you [link]
Also lineage removed 17.1 builds but the guy was making nightlies which are still available so i also uploaded the build i'm using for archive purposes [link]
Idea is that no matter where you are coming from or if you just bought device you should get to sfos this way. And if you are wondering still yes we will be removing ALL YOUR DATA so backup it.
Flash the provided stock via fastboot (there is script and even files for QDL but i haven't tested those). It's pretty straight forward you should figure it out, if not then there is some tutorial i think on this forum or on internet, if you can't handle it then give up really you can do more damage than good.
Verify that its booting, stock will be flashed to slot a. flash and boot twrp (android 10 version, link to image, link to installer) via "fastboot flash boot twrp-3.5.2_10-1-Z01RD.img" i'm not really using windows but you should be able to figure it out already. Flash lineage 17.1 from provided link, it will flash to slot b. afterwards flash twrp installer (the zip) so that you can boot twrp (just flashing twrp on boot on slot b doesn't work GO FIGURE). Reboot, verify that lineage is booting, reboot to bootloader, select recovery, hold power button (fastboot reboot recovery only works sometimes, again GO FIGURE). you should be back in twrp on slot b. Flash lineage again as well as twrp installer so that lineage will be installed on slot a as well as twrp will be bootable. reboot, verify that lineage boots and that you are in fact on slot a. Finally we have lineage on slot a.
Sailfish flashing instructions (come here if you have lineage 17.1 on slot a):
- download rootfs
- flash/boot twrp on slot a (or slot b, i'm not even sure at this point)
- wipe everything (you need to format data, not wipe, format. data NEEDS to be unencrypted, advanced -> format data -> yes, if you didn't realize yet we are wiping EVERYTHING so backup your data)
- Install rootfs (aka sailfish, it will flash kernel onto the same slot so you don't have to worry about switching slots, at least i hope so, if it doesn't boot, get the hybris-boot.img from the zip and fastboot flash boot it onto slot a)
- Boot
- Have fun
Changelog:
STABLE 1:
Initial public release
F.A.Q.
HOW TO REPORT BUG
After bug occurs type in the terminal following commands:
/usr/libexec/droid-hybris/system/bin/logcat
devel-su dmesg
devel-su journalctl
and give me logs from there (do not paste it in the post! Use pastebin.com)
devel-su will ask you for password, you can set it in developer tools.
Contributors
Mister_Magister
Source Code: https://github.com/VerdandiTeam
Thanks for the efforts you put in to bring Sailfish OS to our device. Good work! ??
please make stable SailFish OS
i would like to use this ROM as Primary ROM
rootfs is missing... where can i find it.
i had it before and i misplaced it.
can anyone share the file with me
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Mister_Magister said:
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Click to expand...
Click to collapse
Cool, ping me when ready to test
Mister_Magister said:
Hybris17 is almost ready. I'll re-port 5z on top of lineage17/hybris17 in hope of getting modem fixed. If the modem will turn out to be fixed i will push it forward as current hybris16 based port has only stereo and modem broken.
HEY ITS NOT DEAD OKAY
Click to expand...
Click to collapse
If this hybris17 is not a android rom like havoc or bliss.
Then I am in for using it
Vivek Garg 001 said:
If this hybris17 is not a android rom like havoc or bliss.
Then I am in for using it
Click to expand...
Click to collapse
Hybris is library that Sailfishos uses to communicate with android side of things so it's still sailfishos just using newer android base, lineage 17 in this case
Mister_Magister said:
Hybris is library that Sailfishos uses to communicate with android side of things so it's still sailfishos just using newer android base, lineage 17 in this case
Click to expand...
Click to collapse
How many basic things are not working currently????
I just need calls , camera and wifi to work properly and Android app support is there in this os ... So when it's ready just post it please
I'm requesting the developer to develop further more to best of sailfish for the device , I want to use sailfish as a daily driver
alwinbernat said:
I'm requesting the developer to develop further more to best of sailfish for the device , I want to use sailfish as a daily driver
Click to expand...
Click to collapse
You can't request **** you don't own me
Anyway, i finally started making port based on lineage17.1/hybris17.1 lets see if i get sim to work
Vivek Garg 001 said:
How many basic things are not working currently????
I just need calls , camera and wifi to work properly and Android app support is there in this os ... So when it's ready just post it please
Click to expand...
Click to collapse
There is no android support.
Currently what is blocking me is being unable to boot twrp at all so i cannot flash lineage 17.1 and therefore i cannot flash sfos. This device is such pita…
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Mister_Magister said:
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Click to expand...
Click to collapse
grt news sar
Mister_Magister said:
Good news, since i got 17.1 to work, i also got port working on 17 base and mobile data (and probably calls too) are working! So now hopefully i will have 100% working port as now i only have camera left to fix. After that i will release it again
Click to expand...
Click to collapse
I am waiting for the release
Camera even with wide angle is working fine, i'm just fixing recording. Fingerprint doesn't want to preserve fingerptints between reboots and actdead (charging off screen) is not working
Mister_Magister said:
Camera even with wide angle is working fine, i'm just fixing recording. Fingerprint doesn't want to preserve fingerptints between reboots and actdead (charging off screen) is not working
Click to expand...
Click to collapse
Will we be getting android app support???
Vivek Garg 001 said:
Will we be getting android app support???
Click to expand...
Click to collapse
Ofcourse not, ports don't have android support
So i released the build because i was impatient. Instructions may sound difficult but if you know what you are doing then its pretty straightforward
Step 1 get provided lineage 17.1 installed on slot A
Step 2 make sure /data is unencrypted, format it
Step 3 flash sfos on slot A
Step 4 voila
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/12.0/README.mkdn
Flashing Instructions:
Pre-installation:
gapps : MindTheGapps-Lite-12.1.0-arm64-20220611_132739
Magisk 24.3 for root - (Download from here)
First time installation:
backup your goodies
boot recovery
Wipe Caches, data, system
flash crDroid
(optional) flash Gapps
(optional) flash Magisk
boot system
Update installation:
Device trees:
Common (https://github.com/aoleary/device_lge_g4-common/commits/s)Device (https://github.com/aoleary/device_lge_g4/tree/crdroid)Kernel (https://github.com/aoleary/G4-Titan-Kernel/commits/titan)Vendor (https://github.com/aoleary/vendor_lge/commits/s)
Download:
ROM DOWNLOAD
Known issues:
LED blinking issue. Disabled for the moment
Offline charger broken
Display turns off during calls. Only way to turn screen on is to press power button.
GPS seems quite slow
No response from lockscreen lock button sometimes
Still not enforcing !
NFC is no better nor no worse than previous versions
ROM OS Version: 12.1
ROM Kernel: Linux 3.x (heavily modified by me with commits from Bullhead kernels)
ROM Firmware Required: Unlocked Bootloader
Status: stable
Sec. Patches : 2022.08.05
Created : 2022.08.19
Last Updated : 2022.08.19
Visit official website @ crDroid.net
LG G4 Users Telegram Channel => connect directly with other G4 users (and me, as I'm always there )
crDroid Community Telegram
crDroid Updates Channel
Battery life is crazy good in A12..
aoleary said:
Battery life is crazy good in A12..
Click to expand...
Click to collapse
You are the best, great rom, testing
Is there any way to avoid the flashing of the notification light?, by the way very good rom amazing work with the old lg g4
thedery01 said:
Is there any way to avoid the flashing of the notification light?, by the way very good rom amazing work with the old lg g4
Click to expand...
Click to collapse
Yes, I have disabled it for the moment, while we try to figure out why it's misbehaving..
The G4 handles A12 surprisingly well
I will try to release updated builds 2moro
ok thanks, so I'll look forward to tomorrow's update
Uploaded new builds yesterday..
* blinking LED light fixed (disabled it totally)
* some fixes for WiFi to improve stability
* BT stability improved and support for A2DP BT headsets added
* Wireguard VPN support added in the kernel (need to be root for it to work)
Thanks for the rom. Notification light bug is gone. The screen proximity sensor works directly in the phone call. To overcome this, disabling the sensor is the solution. But since the screen stays on all the time, there is a possibility that your face can be touched. I will be glad if you check it out.
thanks you did an incredible job but I have some questions, to know if it only happens to me, I have the lg g4 h811 variant, and when I install custom roms I have a lot of lag, I mean youtube is slow and it kind of gets stuck I would like to know if it's something I'm specific about the roms, or is it that my cell already has a problem, it's as if none of the roms works for me, someone told me that I suffer from ilapo but since my cell is not frozen in the logo and it works normally, but when installing rom This happens to me, can someone tell me what happens thanks.
thedery01 said:
thanks you did an incredible job but I have some questions, to know if it only happens to me, I have the lg g4 h811 variant, and when I install custom roms I have a lot of lag, I mean youtube is slow and it kind of gets stuck I would like to know if it's something I'm specific about the roms, or is it that my cell already has a problem, it's as if none of the roms works for me, someone told me that I suffer from ilapo but since my cell is not frozen in the logo and it works normally, but when installing rom This happens to me, can someone tell me what happens thanks.
Click to expand...
Click to collapse
Do you have this issue for all custom ROM versions, or just in A12?
I have a test build that might fix the black screen. Anyone here willing to test. I have already tested on my device and it seems positive so far..
Dirty flash is OK (that's what I did)
aoleary said:
Do you have this issue for all custom ROM versions, or just in A12?
Click to expand...
Click to collapse
a12 and the majority that I have tried, it is as if the performance in general was worse with rom, any ideas, do you think it is the ilapo, or is it something normal in roms, I thought that the performance would have to improve with rom
thedery01 said:
a12 and the majority that I have tried, it is as if the performance in general was worse with rom, any ideas, do you think it is the ilapo, or is it something normal in roms, I thought that the performance would have to improve with rom
Click to expand...
Click to collapse
As we advance through each android version, it's going to put more and stress on our old device, so it's going to be a bit slower than it was on Nougat, for example..
But i find it still usable on A12. Not as fast as it was on Nougat, but it doesn't grind to a halt either
If it was ilapo, you should have issues booting..
Maybe try formatting the data partition.
Be sure to backup your internal storage as this will wipe everything forever
aoleary said:
If it was ilapo, you should have issues booting..
Maybe try formatting the data partition.
Be sure to backup your internal storage as this will wipe everything forever
Click to expand...
Click to collapse
Well, thank you very much for answering, so far no problems with booting or automatic restart problems, my problem was just that of the lag in the roms, but well, I already understand the lag
I have installed on my lg g4 h815 usu. All features are working well on it, but only security lock like pattern, pin etc doest work. Everytime I try to make pin or pattern, it always reboot to system. Sorry for my bad english.
Btw, tq for your great job.
Kohbidin said:
I have installed on my lg g4 h815 usu. All features are working well on it, but only security lock like pattern, pin etc doest work. Everytime I try to make pin or pattern, it always reboot to system. Sorry for my bad english.
Btw, tq for your great job.
Click to expand...
Click to collapse
Hi,
You're welcome.
Strange, cos PIN works fine for me.
Can you grab a logcat?
This, sir
Kohbidin said:
This, sir
Click to expand...
Click to collapse
I don't see any attachment
Im sorry sir, I forgot
{
"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)