Discusion about Android Lollipop (initially for Mi3W)

Discusion about Android Lollipop (initially for Mi3W) - Xiaomi Mi 4

Hello,
This is a thread about Android Lollipop for Mi3W. I make it because this build by Ivan is also compatible with the Mi4W. I can't share links because it's not my work and Ivan didn't release his sources. I make it for discussing around this build and your feedback because I think we should not spam Mi3 section with feedbacks about Mi4.
Here are some of my screenshots :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With some test I can say that on Mi4 :
-Video recording is broken (but can be fixed using one+one camera app)
-HDR picture doesn't work with stock google camera
-Good picture quality
-Good sound quality (better than MUI with headset in my opinion, in fact I use a jack-tape adapter in my care and sound is less saturated for higher volume)
-No random reboot on this device (contrary as Mi3 wich reboot in deep sleep mode)
-No unlock with menue keys (contrary as Mi3)
-USB OTG working
-Wifi and bluetooth working perfectly (and MiBand is compatible)
-MMS not send while using wifi (normal but MIUI is capable of auto switch between Wifi and mobile data for sending or receiving an MMS)
The last but not the least :
On Mi4 it seems that maximum CPU frequency is lower than normal (Mi3 users have 2.3GHz and they run 2.3GHz on lollipop), I'm not sure if it's 1.1GHz or 1.7GHz max on Mi4 but I tried several overclock apps wich allows me to get 2.5 but only when they are open, after frequency automatically switch to a lower frequency (tested with stress test, and observed with cpu spy). So it seems impossible te get higher frequency on this device.
Anyway wit such low frequency Lollipop still smooth to use.
If someone managed to make it run higher that would be nice to know how.
And you what's your opinion about this port?

I flashed Lollipop 2 day ago. No problems at all, except the camera bug but I'm using one+one camera and I don't have any problems. Regarding the frequency, I hope Ivan will fix it even if the device runs very smooth (more than Miui 6) also with the lower frequency (it could be an advantage for battery saving). Maybe picture and video quality could be better but except this I'm very satisfied with this rom.

I hope the same, that would be perfect to have a fully working Android L on our devices. MIUI is not smooth at all in balanced mod. And with android L everything is smooth with lower frequency. It seem that MIUI is only good with high frequency CPU...

lollipop issues
I found some issues like wifi stop working and its hard to reconect this also applies for celular network like when using a elevator (normal), the signal is gone but after you leave the elevator it keeps without signal for a while.
Improvements reboot to recovery and screenshot would be nice
The volume widget is usefull but if you could add a volume icon in the notification bar would be awesome. (Also be able to modify this icons wold be nice)
Sometimes the gps keeps turned up even with no apps using it
I dont like voice commands or voice talk to write so i disable but when i disable after reboot if keeps active strange.
But beside that a ****ing awesome rom to my opinion the best one

https://mega.co.nz/#!kwFCXD5A!c7ama3gHUVLYlF754BtkihOpe8EURnOyBwVZA0LEKpc
Sorry for spamming.. Can test this and report back if it work on Mi4..this CM12 for Mi3.. Just give feedback here. List all bug if you can. Thanks.

audahadi said:
https://mega.co.nz/#!kwFCXD5A!c7ama3gHUVLYlF754BtkihOpe8EURnOyBwVZA0LEKpc
Sorry for spamming.. Can test this and report back if it work on Mi4..this CM12 for Mi3.. Just give feedback here. List all bug if you can. Thanks.
Click to expand...
Click to collapse
Hi, It's not spamming, no problem guy, I was spamming Mi3 sections about flashing these roms on Mi4.
Basically yes it'll boot on this device but only if you first get a perfectly clean phone (No miui installed and full wipe performed), let me explain, I hope to be clear :
- I managed to flash the previous build without TDB and makes it boot, but I had got a bunch of FC (not efficient wipe) and Gapps where not present even after flashing micro Gapps.
-With TDB enabled, installing CM12 result on non booting CM12 (bootloop or trying to boot on MIUI but with bootloop) and totally messing my MIUI rom on system 1. Plus messing my sdcard (all files placed in a folder called (0)
The biggest issue with flashing CM12 build comes from CWM recovery, I guess all the CancroCM team should start by working on a perfect CWM recovery. Because the ones we actually have (furniel and donbot's one) :
-Are not able to dual boot MIUI and CM12 (as it's an alpha an I only have one phone I use it as daily basis so I can't afford to always restore it, I need a perfecly working rom too)
-Are not able to perform any wipe (cache, dalvik, data) this results on not working rom (doesn't flash rom or rom get into bootloop at first start)
So if your team have some time to check it that would be perfect. I really hope you'll do something for a perfect CWM. Because I love CM (more than MIUI) and I really appreciate your work that's why I want to test it but I need to keep another rom.

Riichard63 said:
Hi, It's not spamming, no problem guy, I was spamming Mi3 sections about flashing these roms on Mi4.
Basically yes it'll boot on this device but only if you first get a perfectly clean phone (No miui installed and full wipe performed), let me explain, I hope to be clear :
- I managed to flash the previous build without TDB and makes it boot, but I had got a bunch of FC (not efficient wipe) and Gapps where not present even after flashing micro Gapps.
-With TDB enabled, installing CM12 result on non booting CM12 (bootloop or trying to boot on MIUI but with bootloop) and totally messing my MIUI rom on system 1. Plus messing my sdcard (all files placed in a folder called (0)
The biggest issue with flashing CM12 build comes from CWM recovery, I guess all the CancroCM team should start by working on a perfect CWM recovery. Because the ones we actually have (furniel and donbot's one) :
-Are not able to dual boot MIUI and CM12 (as it's an alpha an I only have one phone I use it as daily basis so I can't afford to always restore it, I need a perfecly working rom too)
-Are not able to perform any wipe (cache, dalvik, data) this results on not working rom (doesn't flash rom or rom get into bootloop at first start)
So if your team have some time to check it that would be perfect. I really hope you'll do something for a perfect CWM. Because I love CM (more than MIUI) and I really appreciate your work that's why I want to test it but I need to keep another rom.
Click to expand...
Click to collapse
Which cwm u used?..

Hadi al-Haiqal said:
Which cwm u used?..
Click to expand...
Click to collapse
I was using the furniel and donbot 11th release (r11) 6.0.5.1
Envoyé de mon MI 4W en utilisant Tapatalk

audahadi said:
For now we only support installation on system 1.. No dualboot. But we'll look at this.
Click to expand...
Click to collapse
Oh okay, nice to hear some news, I hope that'll be possible

audahadi said:
For now we only support installation on system 1.. No dualboot. But we'll look at this.
Click to expand...
Click to collapse
Oh but if only system 1 is supported that means that there is a script on the zip file that force flash to system 1 right? So that may be why I was thinking that wipe with this recovery wasen't efficient.

Related

[Q&A] [ROM][5.1.1] CyanogenMod 12.1 for Acer A700[UNOFFICIAL]

Q&A for [ROM][5.1.1] CyanogenMod 12.1 for Acer A700[UNOFFICIAL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] CyanogenMod 12.1 for Acer A700[UNOFFICIAL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

My A700 don't want anything but CM10 ... what happens ?
Hi
I try to install it on my A700 rooted and with CM11 and encounter a problem that i can't solve.
I use Clockworkmod 6.05
I have wipe data/factory reset and format dalvik cache as well
During installation i have seen a message telling something about "detected EXT4 [...] and a folder name beginning with /dev and including TEGRA-3 in it (sorry, i didn't made a screen copy)"
Then after a long time "Script succeded : Result was [/system]".
And a message telling the installation was completed.
But when i reboot the phone, i do have the Acer logo, then after a long wait, it reboot and do the same again and again
So after some despair, i try to reinstall CM11 and also try Pac-man but to no avail... seems impossible to reinstall any kitkat android .
As a consequence, i try to install CM 10.2 and it works
Another strange thing is that the "wipe data/factory reset" now hang on "format /cache"... i have to reboot the a700, then go to advanced and choose format /cache from there to be able to finish it.
As i can guess i missed something and want to try your version of CM12 , can you help me understand how to solve this problem ?

Hi,
You should try to make a cleaner install by
- make a factory reset
- format /system
- flash the CM 12.1 ROM
- flash the CM 12.1 Gapps
- reboot

Shreps said:
Hi,
You should try to make a cleaner install by
- make a factory reset
- format /system
- flash the CM 12.1 ROM
- flash the CM 12.1 Gapps
- reboot
Click to expand...
Click to collapse
Hello
thanks but i can't use the factory reset as it hang on the "format /cache" operation
So what i have done each time i try was :
format /system
format /cache
format /data
wipe dalvik cache
I don't get it ... could this be a problem with the CWM i install on it ?

this is insane
OK i install CTR yesterday to give a try but still have issues
Now i am 100% sure there is no link with CM 12.1, so i don't know how to remove my message from [Q&A] about it.
Here is the message i got when installing it
{
"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"
}
Is it the normal behavior ?
When i want to install Full GAPPS, i have this message
Is it normal as i just format the /system ?
As said yesterday, i do each time :
-Format /system
-Format /cache
-Format /data
-wipe dalvik cache
I even remove all backups as they don't works
even with CTR, i am still unable to use wipe/factory reset ... when doing the format /cache, nothing happens, the menu never came back ...
If i do one after another Format /system, Format /cache ,Format /data, the menu disappear... and i have the same issue on CWM so perhaps this is an issue that everyone has ?
OK so CM11, CM12 and Pacman don't works (loop on the Acer logo).
This is strange as before trying to install CM12, i was using CM11.
The only one that works is CM10.2.
But now the insane part : at the beginning, to install CTR, as my CM10.2 was "fresh" i install firefox and flashify.
So i have the 2 icons on the desk
After formatting many times, wiping all i could, and installing many OS, i reinstall CM10.2
And the icons and wifi parameters were still there !
It is as not everything was wipe
is there any way to check what happens using Adb or fastboot at each step ?

VICTORY!
Thanks to Shreps, i have been able to resolve my issue
Here are what i have done using his advices in fastboot mode
> fastboot erase cache
> fastboot erase system
> fastboot erase userdata (takes 28s to finish it !!!)
> fastboot reboot-bootloader
> fastboot erase boot
> fastboot erase recovery
> fastboot flash recovery C:\.........\recovery-ctr.img
> fastboot boot C:\.........\recovery-ctr.img
I have change the boot and recovery erase to do it at the last moment - just in case something goes wrong
Then i have install CM12.1 and i have the following message
After rebooting, i was glad to see this expected screen :victory::victory:
Oh i forget to add i use CM12.1 Gapps
I have test many features (camera, wifi, checking each parameters screen to see each options) and you have done a wonderful work Shreps !
Ok one last tought for people who want to try
The "desktop" seem to be quite small for icone at first, as on this screen capture
I mean, i have put the google icon on the right and you still have a big place unavailable on the right
In fact, this is because of the google search bar - after removing it, the screen was resized to take space available.
Ok again THANKS Shreps for both your help on my problem , the CTR and CM12.1

Ok i have less than 10 posts, so my comments won't be on the discussion about CM12.1 - sorry for that.
RichieXX said:
My parents have a Acer A700 . I have changed ROM from CM11 to Pacman, because the performance was very poor. They are actually very happy with it. What is the performance of your CM12 against CM11 or Pacman KK? Is it worth changing to Lollipop.
Click to expand...
Click to collapse
Mankann said:
Thank you, Shreps, for this ROM! Have been testing it for a couple of days, and it's nice, the performance is the same as on CM 11 - actually it feels even smoother
Click to expand...
Click to collapse
Ok i never try Pac-man but i have use CM11 for some months, CM10 for some days and now CM12 for some hours
I have the same feeling as Mankann - for me, CM12.1 is somewhere between CM10 and CM11 regarding the smoothness
The navigation between menu is far quicker than CM11, the applications on another side are slower to launch than CM10 but still a little quicker than CM11. It was quite slow when reinstalling all apps from Playstore.
But the result is fine, i believe only a few is missing to have something very smooth. I don't know if this is more RAM or CPU.
I have to use it for a couple of hours to see if i encounter issues

Strikerfoxx said:
Ok i have less than 10 posts, so my comments won't be on the discussion about CM12.1 - sorry for that.
Click to expand...
Click to collapse
No problem. I found your answer yet.
Ok i never try Pac-man but i have use CM11 for some months, CM10 for some days and now CM12 for some hours
I have the same feeling as Mankann - for me, CM12.1 is somewhere between CM10 and CM11 regarding the smoothness
The navigation between menu is far quicker than CM11, the applications on another side are slower to launch than CM10 but still a little quicker than CM11. It was quite slow when reinstalling all apps from Playstore.
But the result is fine, i believe only a few is missing to have something very smooth. I don't know if this is more RAM or CPU.
I have to use it for a couple of hours to see if i encounter issues
Click to expand...
Click to collapse
Thank you for your first impressions of CM12. At the end I probably remains only the self-test.

I have found an issue
When i use the camera, if i switch from frontal to back on or vice-versa, the application hangs, then stopped with an error message
You have to restart the camera application and from time to time you have the message "impossible to connect to the camera" (probably bad Translation as i use CM12 in French "Impossible de se connecter à la camera") so you have to restart the tablet
---------- Post added at 09:47 AM ---------- Previous post was at 09:39 AM ----------
Second issue is noise in headphones (there was no noise on CM 11). Disabling stock AudioFX (and its complete removal) as well as installing ViperFX, which I used on CM 11, change some audio effects but not the constant ssssshhhhhhh.
Everything else is very nice
Click to expand...
Click to collapse
I also have the audio blank noise "shhhh" when using VLC and headphone. For me it is just a small noise
I didn't check audiofx but the sound is there even after the video have ended, and it stop if i close VLC.
Sorry for all theses post , the goal is to help improve this version of CM:fingers-crossed:

No Apps can be installed
I've installed the latest rom 16.06 250MB space of 32 Gib could be used , can you fix it? Its the first lollipop rom and it run verry well !

I had CM11 KK on my a700. I tried to flash cm-12.1-20150616-UNOFFICIAL-a700 in CWMR 6.0.4.4.(couldnt find newer version) like usual, but it didnt work. Now my a700 is stuck in a bootloop. I tried to flash CM11 KK again, but only a cyanogen logo appears and then it reboots. Can someone help?

Stammleser said:
I had CM11 KK on my a700. I tried to flash cm-12.1-20150616-UNOFFICIAL-a700 in CWMR 6.0.4.4.(couldnt find newer version) like usual, but it didnt work. Now my a700 is stuck in a bootloop. I tried to flash CM11 KK again, but only a cyanogen logo appears and then it reboots. Can someone help?
Click to expand...
Click to collapse
Do You have a JB bootloader? Did you try to factory reset?
Envoyé de mon One+

>>bootloader version jb-653b3d3 (unlock mode)<< appears always above in the left corner. when i do wipe data/factory reset, it reboots, but only to the acer logo.

Just dusted off my Acer 700 from the closet. I had totally forgotten I had it (received free gift sometime ago!). Went from stock 4.1.1 straight to this and I am still testing things out. One recommendation I have is to go with CTR (not TW or CW) and wipe+format partitions. You don't see any errors and just installs in a cleaner filesystem.

Stammleser said:
>>bootloader version jb-653b3d3 (unlock mode)<< appears always above in the left corner. when i do wipe data/factory reset, it reboots, but only to the acer logo.
Click to expand...
Click to collapse
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
---------- Post added at 09:20 AM ---------- Previous post was at 09:09 AM ----------
Hi Sterist
Did you try to remove the flex partition and expand the system one ?

Strikerfoxx said:
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
---------- Post added at 09:20 AM ---------- Previous post was at 09:09 AM ----------
Hi Sterist
Did you try to remove the flex partition and expand the system one ?
Click to expand...
Click to collapse
not on the a700
I tried it on my s4 and note 4 since they can recover (most) partition errors, and upon trying to resize any partition, it failed and have a error. that was several days ago and I can't remember what the error was
maybe I forgot to unmount it...

A new build is online based on the r6 tag
Click to expand...
Click to collapse
I download it this morning and plan to install it in a few days
Is there any way to install it using the update screen in Cyanogen instead of using CTR each time (and format everything) ?

Great !
5.1 on my A700, I'm gonna test it right now...

Strikerfoxx said:
Try to install CTR for A700 made by shreps and if it didn't work, follow what i have done in that post using fastboot to be sure that no data are still on your device.
Click to expand...
Click to collapse
i downloaded the CTR file, but i dont know how to install it.

My experience with the rom : installed it without any issue, with nano gapps, after full wipe (TWRP 2.6). Install and set up was not that long. Restored my apps with TB.
Great to have CM12 (thanks to the dev !) All seemed to work fine at first. But I got many huge lags, ~30 sec to load an app, then again ~30 sec to change page or scroll down... (not all the time - and Antutu scired a good 19500). Got the same kind of lags when I tested CM11 I think.
More importantly, I can't play most of my videos (with MX player or some streaming app). It freezees on the first images while the sound continues to play normally. Someone have any idea where that come from ? I tested some ambient display parameters, some 2d/3d acceleration parameters under development parameters but nothing changed...
I think I might have to go back to pac man rom, which didn't had these issues for me...

[DISCONTINUED][AOSP][6.0.1] Fire Nexus ROM - [SUBSTRATUM] [M4B30X] [22 Oct 2016]

{
"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"
}
Fire Nexus ROM
Introduction
This ROM is based off AOSP marshmallow. I have merged changes from CAF and Cyanogenmod to enable this boot on our HDX devices.
Features
- AOSP with optimisations from CAF
- Open GAPPS nano is built-in
- Clear all recents
- Advanced Power Menu
- Substratum Theming Support
- Init.d Support
- SuperSU is built-in
Prerequisites for Installation
- Unlocked bootloader is a must
- TWRP 3.0.2-0 installed
- This does NOT work with Safestrap
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Issue List
- Sideloading of some apps may be necessary
- Bluetooth
- LTE
- WiFi may need to be manually toggled after wakeup
Kernel Source Code
- https://github.com/CyanogenMod/android_kernel_amazon_hdx-common
Credits
- AOSP
- CodeAurora Forum
- Cyanogenmod
- Substratum Team
XDA:DevDB Information
mm-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-22
Last Updated 2019-10-02

Release Notes / Change log
22 October 2016
- Initial Release
- Xposed needs testingConfirmed as working

Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).

schr01 said:
Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).
Click to expand...
Click to collapse
Yes, rotation is a problem. If I remember rightly it is the same issue as with other custom ROMS. Try locking the screen rotation in the correct aspect then running open camera again. The app should then appear correctly.

Thank you for your tip. It works.

Woohoo!
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.

Davey126 said:
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Good to hear Xposed is working and your problematic messaging app
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
I would expect CM 12.1 data restore to not work. The framework in this ROM is very different from CM 12.1.
You might also run into problems dirty flashing from the KitKat build of the ROM.
Clean flash would be recommended in both cases when coming from an older or different ROM.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Kids sometimes use my tablet so having the reboot to recovery options etc can be a problem.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.
Click to expand...
Click to collapse
Thanks for the detailed feedback :good:

Thank you for nexus rom.
Thank you for nexus rom.
It works almost good for me, but google contacts cannot synchronize gmail account.
In nexus5 (6.0.1), it can be synchronized by contacts->settings->accounts->google.
In thor, contacts->settings->accounts->(not shown google).

Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?

rootnooby said:
Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?
Click to expand...
Click to collapse
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)

ADB Backup/Restore
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?

I had no installations problemes with TWRP 3.02.

Davey126 said:
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?
Click to expand...
Click to collapse
Will take a look, before the next release.

ggow said:
Will take a look, before the next release.
Click to expand...
Click to collapse
Thanks. Two reasons for wanting this:
- transfer apps and all associated data between devices
- create targeted backups or nandroid clone on devices with limited internal storage
Titanium used to be the go-to choice but it hasn't been updated in nearly two years (struggles on Android 6+) and also utilises adb functions for transport.

FYI - I was able to get this rom to dirty boot a CM 13 build but that's as far as it went. Processor pegged on lock screen judging from heat and sluggish response (5+ sec per key press). Obviously a clean flash is highly recommended by dev but was looking for a path to bring my existing CM 12.1 build (apps and data) forward. Probably hang out on Lollipop for awhile as it meets my needs with no meaningful loss of functionality vs Marshmallow with Greenify, Nova and a few Xposed modules thrown in.
Might give Nexus 6 another whirl once adb backup/restore is working (see previous posts for background). I do miss AOSP ...
Also sad CyanogenMod can't get their act together and fix the ridiculous bug that throws up a fur ball when SIM access is requested on CM 13 if there ain't no SIM card installed (hello...tablets!!). Regression was introduced in a nightly build last March and never resolved.

Camera isn't working on apollo

@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.

chipsugar said:
@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.
Click to expand...
Click to collapse
I have been looking into Bluetooth as I need this working too. But with these new versions of android running with old binaries, it becomes really difficult to get everything working as it should.

Davey126 said:
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)
Click to expand...
Click to collapse
Installed with 2.8.7, Apollo, with no issue!

My Apollo was on 4.5.5.1, then installed with Safestrap v4, and then Fire Nexus KK ROM. After waiting weeks for the 1-Click bootloader unlock tool, I finally decided to go for the step-by-step unlock procedure and managed to have my Apollo unlocked yesterday afternoon.
I clean flashed your TWRP 3.0.2.0 and this Fire Nexus MM ROM immediately after unlock and am really pleased with the new ROM and the newly found freedom. The ROM works quite well so far except for 1) camera (tried Snap Camera and Camera MX), 2) Google Contacts cannot sync with Gmail account.
As I came over from SafeStrap v4, is there any old files and folders need to be tidy up?

[ROM] LineageOS 14.1 (official)

Can this be flashed with current twrp?

Absolutely, that's what I did. Use sideload.
MrWhite0429 said:
Can this be flashed with current twrp?
Click to expand...
Click to collapse

Can't wait for those issues to be fixed so I can use it. Surprises me how fast you're working tdm

EEEEE I LOVE YOU
thank you so damn much tdm, i was scared this phone would be developmentally dead

Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
A 'Clean' install consists of the following:
Factory Reset (or manually wipe (format) Data partition - Internal Storage wipe is NOT necessary)
Manually wipe (format) your System partition <-Unnecessary
Flash your ROM
Flash GApps package <-Use opengapps arm64 7.1 micro
Flash SuperSU v2.79 <-Use the arm64 version of SU found on the LineageOS website
Wipe the Dalvik & cache <-Unnecessary
Reboot (Because of the SuperSu install, there may be a bootloop or two. It also warned me before I rebooted that I didn't have an OS installed, even though I did.)
NOTE: YOU WILL LOSE ALL OF YOUR DATA AND APPLICATION SETTINGS using this method. Be sure to do a NANDroid backup prior in case you want to restore later.
Click to expand...
Click to collapse

Glad someone else got it to work, and thanks for the instructions. Note formatting /system is not necessary, neither is wiping cache or dalvik.
If you want su, lineage has a flashable root package. Check on their site. SuperSU may work but it's not supported in any way.
I'll check the WiFi stuff, I probably missed a config or calibration file or something.
The in-call audio is probably an issue in the amplifier code. I just got that working yesterday, so no surprise there. Fix should be relatively easy.
mattx1002 said:
Just installed and it works...pretty alright!
Bugs:
-Wi-Fi range seems to have shrunk ten-fold (LTE works perfectly fine, so it seems to be a problem with whatever Wi-Fi module(?) is being used with the ROM)
-Can't hear anyone on calls (What you already addressed)
That's all I've found so far. I was able to install SuperSU v2.79, which is super dope, and I've tested it with my good friend Titanium Backup to great results. Thanks a whole bunch for all the hard work, TDM!
P.S.: If you're dumb like me, and you're pretty new to all of this stuff, follow this guide that I sourced from the Open GApps FAQ to install the ROM:
Click to expand...
Click to collapse

I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!

tdm said:
I need a log from stock and I don't really want to flash back and forth. Can someone do me a favor and get a log of a phone call using stock 7.1.1? Just run eg. "adb logcat >call.log" and then make a call, establish voice communication, hang up, and hit ^C.
Thanks!
Click to expand...
Click to collapse
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)

mattx1002 said:
LTE works perfectly fine
Click to expand...
Click to collapse
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.

Thanks I got it. I used the amp parameters from your log but still can't get in-call audio. Need to keep looking....
maestromony said:
Sent private message to you. That logfile was made right? (stock 1.2.0B09 7.1.1 tulip locked)
Click to expand...
Click to collapse

Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse
I'm on T-Mobile.

I'm on AT&T. LTE works for me.
Vixenko said:
I know this is off topic, what carrier do you have? I think my carrier didn't activate LTE for me at all.
Click to expand...
Click to collapse

Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?

Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
tdm said:
Okay been working away on this. Got the WiFi MAC and the notification light working. Still haven't figured out call audio, which is the biggest show stopper right now.
Got a question though....
As far as I can tell, the notification light hardware only seems to support a single color at a time (red, green, blue). They can't be mixed to provide eg. yellow or orange. So, it can't do the typical yellow for the "medium battery" color. What do you people prefer for that? What does stock show?
Click to expand...
Click to collapse

mekzmaz323 said:
Thanks for your work again.
Stock:
Constant green when its fully charged (and blue blinking when notification arrived).
Constant blue when its charging.
Red Blinking when level is below 15%
In my opinion you can leave it like that.
Click to expand...
Click to collapse
I agree. I'm fine with it being the same.

WiFi and lte
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
tdm said:
Here at long last, Lineage 14.1 for the Axon 7 Mini!
... I'll fill this post out more later ...
Current status: Alpha
Currently supported devices:
US variant (tulip) running 7.1.1 b14 firmware.
Known major issues:
Phone audio doesn't seem to work.
Bluetooth audio stutters incessantly, unusable.
Notification LED doesn't work.
Cannot seem to get NFC to work.
Known minor issues:
WiFi mac addr isn't set properly.
WiFi connection seems a bit flaky. (?)
Download:
lineage-14.1-20171019-UNOFFICIAL-tulip.zip
MD5=5b4ca59d5b9f69e59dc44ba28637b71a
Tested with opengapps arm64 7.1 micro.
Sources:
device_zte_tulip
kernel_zte_msm8952
Click to expand...
Click to collapse

These are known issues except for LTE. My LTE works fine and I have reports that others do also.
CRAFTER0302002 said:
My WiFi is very bad and unstable. Also I never have more than 1 bar of LTE signal. And when I make a call others can't here me and I can't here them.. Those are my only problems.
Version: B14
Thanks @tdm for all your work!
Click to expand...
Click to collapse

Today's build is up, with handset audio working!
I think the volume adjustments may need work, but I do hear audio.

I'm off work tomorrow so I may stay up tonight and give this a try! In anyone's opinion is this stable or suitable for daily use?

[ROM][9][Pie][Flo][UNOFFICIAL] Pixel Experience Plus (2/13/2020)

{
"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"
}
PixelExperience Plus for ASUS Nexus 7 2013 [Flo/Deb]
What is this?
Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device
Based on Android 9.0 PIE
DON'T FLASH GAPPS, ALREADY INCLUDED IN ROM!
Installation:
1. Download the ROM and Magisk from the links below.
2. Wipe everything except internal storage.
3. Reboot recovery you will have no OS installed but that's ok i promise your device will boot back into recovery.
4. Flash the ROM and DO NOT flash GApps as it is already included!
5. Flash Latest Magisk to get root access.
6. Reboot and Enjoy!
Known issues:
- You will be required to repartition your device to at least 1.3gb. If you have anything higher or exact than 1.3gb than your fine.
- Navigation bar glitches sometimes.
- Deep Sleep does not work when NFC is enabled so i recommend you disable it when your not using it to get your tablet to go in deep sleep.
- When you boot up the ROM for the first time you may notice that the boot animation will freeze and then your device reboots back to the google logo. This is not a device side issue but a ROM side issue but let the tablet reboot a couple times if necessary & your tablet will eventually boot to the setup wizard and into the ROM. This is normal.
- Use Latest Official TWRP recovery below for Flo which is version 3.3.1.0 and you won't have the install supersu thing when you reboot recovery.
- You tell us!
Downloads:
Latest 2/13 build for Flo is here: https://www.androidfilehost.com/?fid=4349826312261722127
Download folder for Flo is here: https://www.androidfilehost.com/?w=files&flid=293644
Magisk: https://github.com/topjohnwu/Magisk/releases
TWRP: https://dl.twrp.me/flo/twrp-3.3.1-0-flo.img.html
Sources:
Flo Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/pixel-pie
Deb Device Tree: https://github.com/followmsi/android_device_asus_deb/tree/pixel-pie
Kernel: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-pie
Vendor: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-16.0

Thanks dude, I have a LTE version, will you help to release Q for DEB as well? Thanks.

Reserved for future use

one more just in case

Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.

sir_bazz said:
Thanks very much for making time to maintain this.
May I ask which blobs are used for this build? If Im reading it correctly, it's the same ones that @followmsi has switched to rather than the previous QC ones?
I'll definitely install this and give feedback but am of the current belief that the previous blobs provided much better performance,(on deb at least), than the ones used in the other most recent build.
Hadn't mentioned it yet as was still trying to pinpoint why it feels less responsive. Not sure if it's GPU or disk IO or even CPU because the numbers all look fine but the device feels noticeably less responsive when playing something taxing like PoGo.
Edit: just saw the blobs link.
Click to expand...
Click to collapse
I am using followmsi's latest pixel and pie aosp sources which includes fixes for hardware decoding and compass. I don't have any slow downs when i tested the build however i wouldn't know how to even fix it if there were slow downs because i am just building using his sources. There is nothing changed or added besides those sources. You can expect a new build from me every month with new security patches because i am currently the one mantaining pixel experience
Cheers and have a good day

Is Netflix working on this rom?

guillaumeserton said:
Is Netflix working on this rom?
Click to expand...
Click to collapse
yes but you have to install the older version of netflix look at other peoples posts on different rom threads because i don't care about netflix and you will find the fix there in those threads and posts

Issues
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.

prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
The only thing that shouldn't be working is compass and I will hopefully fix it in the next build but gyroscope and accelerometer is working for me on my flo with no problems however I can't say this for deb as I don't have that device to test. But I would do a clean flash wipe everything except internal storage and try flashing the ROM again. Also remember to not flash gapps as its already included

prodOne said:
Latest build (05/02) borked all the sensors (gyroscope, compass, accelerometer). After dirty flashing it over an earlier build they all stopped working.
Had to go back to stock 6.0.1 and it's all ok now. 6.0.1 feels like a rocket by the way. I don't know about your experience with these pie roms, but for me it's been high battery drain (especially when watching youtube) and overall intermittent choppiness.
Click to expand...
Click to collapse
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.

sir_bazz said:
Actually I saw the same thing when dirty flashing to the changed blobs build from the other thread.
An additional restart was required to get them working.
Haven't had a chance to try this build, (deb), yet but it's likely the same.
Click to expand...
Click to collapse
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956

Tested deb for a few days, ( with the patch linked above), and it's pretty good.
Dirty flashed, wiped cache and dalvik, installed ElementalX kernel and then the deep sleep patch.
My early concerns regarding the changed blobs and performance were unfounded. Everything appears to work and the rom runs smoothly.
Did experience an issue with sensors no longer responding after a couple of days and although easily resolved with a reboot, I rolled back to an earlier PE build to avoid a repeat.
Looking forward to trying any further builds though. Hopefully will have time to troubleshoot, or at least a grab a useful log next time.

JT1510365 said:
You can fix deep sleep by flashing this zip I provided and I tested it and now my tablet goes into deep sleep. This zip add-on works for all pie ROMs except unlegacy because its already included. Huge thanks to @followmsi for providing the fix
Download here and flash in recovery:
https://www.androidfilehost.com/?fid=1395089523397959956
Click to expand...
Click to collapse
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas

pcmender2005 said:
Hi mate I cant seem to install this I keep getting error code 7 I have updated the twrp in recovery any ideas
Click to expand...
Click to collapse
i have no idea it flashes and works fine for me

JT1510365 said:
i have no idea it flashes and works fine for me
Click to expand...
Click to collapse
Ok no probs will have a look at the update script.

I've given this rom a try, and I am also receiving an error 7 from twrp-3.3.0-0-flo
Code:
BLKDISCARD ioctl failed: Invalid argument
failed to execute command [erase 4,756,4689,298235,326400]
new data receiver is still available after executing all commands.
script aborted: E1001: Failed to update system image.
E1001: Failed to update system image.error: 1001
Updater process ended with ERROR: 7
This device must be re-partitioned before installing this rom
Otherwise works just like it was stated on the original post.

sir_bazz said:
Tested deb for a few days, ( with the patch linked above), and it's pretty good.
installed ElementalX kernel and then the deep sleep patch.
e.
Click to expand...
Click to collapse
which Kernel did you use ? tried both 6 and 7 EX - soft brick

Custom setting
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?

jhford said:
@JT Your Havoc ROM has custom status bar settings, etc., but it seems that this ROM doesn't. Why?
Click to expand...
Click to collapse
Because havoc is more customizable and feature filled compared to pixel experience. Pixel experience is meant to give you the same experience as if you were to use and buy the google pixel phones its the same ROM basically as what the pixel has. There's nothing I can do about this pixel experience is meant to be more of a stock bare minimal experience rom compared to havoc which is more feature filled and customizable.
Cheers

karmacoma7 said:
which Kernel did you use ? tried both 6 and 7 EX - soft brick
Click to expand...
Click to collapse
Apologies man.
Sometimes I completely forget that not everyone here is up to date with development for our devices.
I should've made clear that kernel build is by @followmsi and found in his online file repository.
https://drive.google.com/drive/mobi...k92ZUdnTTg?usp=drive_open&sort=13&direction=a

[ROM][10][Q][Flo][UNOFFICIAL] crDroid 6.0 (12/30/2019)

crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Always Have a full functional Backup. Just in case if you want to!
First time installing crDroid to your Nexus 7 2013 or coming from another ROM:
** Make sure you're running a proper working Recovery (TWRP)
1) Copy crDroid zip, gapps zip, to your device
2) Boot into Recovery
3) Wipe everything except internal storage.
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk v20.1 (whatever is most recent).
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
- NFC has been removed and disabled so it's unusable at the moment.
- Navigation bar glitches sometimes.
- Since it's Android Q you may have problems with certain apps not working properly. You will have to tell the developer of the certain app to update their app to be compatible with Android Q. This is not a problem with the ROM.
- Compass seems to not be working.
- Encryption does not work.
- Several crDroid features may or may not be available yet.
- You will be required to repartition your system to at least 1.3gb.
- You tell us!
Downloads:
Latest 12/30 build for Flo is here: https://www.androidfilehost.com/?fid=4349826312261688703
Download folder for Flo is here: https://www.androidfilehost.com/?w=files&flid=302533
GAPPS: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
Sources:
Device Tree: https://github.com/followmsi/android_device_asus_flo/tree/los-17.0
Vendor Tree: https://github.com/followmsi/android_vendor/tree/flo-deb-lineage-17.0
Kernel Tree: https://github.com/followmsi/android_kernel_google_msm/tree/followmsi-10
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Followmsi (For device, vendor, and kernel sources)
- Many others... (if you're feeling upset being out of the thanks list just send a PM )

Reserved for future use
Happy flashing and enjoy android 10 Q!

I have a problem installing the GApps with ROM build 20191126 . Coming from LineageOS 16.0 (flo) I wiped everything except of the internal storage.
But I always get "Incopatible Android ROM detected. This GApps pkg is for Android 10.0.x ONLY. Please download the correct version for your ROM: 6.0.1 (SDK 23)"
Is this a problem of the ROM or the GApps package?
Frapl

Frapl said:
I have a problem installing the GApps with ROM build 20191126 . Coming from LineageOS 16.0 (flo) I wiped everything except of the internal storage.
But I always get "Incopatible Android ROM detected. This GApps pkg is for Android 10.0.x ONLY. Please download the correct version for your ROM: 6.0.1 (SDK 23)"
Is this a problem of the ROM or the GApps package?
Frapl
Click to expand...
Click to collapse
Have you messed with the build.prop file or any other system files located in system/system in twrp? I did that accidentally and the only way to get it fixed was to reflash the rom and wipe everything except internal storage then reboot recovery then flash the rom and then reboot recovery again and then flash gapps. Try that and make sure you have the latest version of twrp recovery

Hi all.
Just downloaded crDroid to give a test spin to see how it is.
I'm primarily a gzr, aex guy.
LineageOS and crDroid are my next rom choices.
A note about OpenGapps 10.
It has issues mounting system on some devices.
Installing ROM, rebooting into system and then rebooting back into recovery, works.
Honestly takes too long for me.
A quicker way that normally works is.
- Install ROM.
- Mount (or unmount and remount) system in TWRP.
- Install OpenGapps 10.
- Reboot to system.
- - or install Magisk, kernel, what ever else and then reboot to system.
At first glance, crDroid seems to be working well. :highfive:
Cheers.

Thanks for the suggestion to Mount the system in TWRP. That fixed my issue.

JT1510365 said:
Have you messed with the build.prop file or any other system files located in system/system in twrp? I did that accidentally and the only way to get it fixed was to reflash the rom and wipe everything except internal storage then reboot recovery then flash the rom and then reboot recovery again and then flash gapps. Try that and make sure you have the latest version of twrp recovery
Click to expand...
Click to collapse
I did not modify anything, just coming from LineageOS 16.0 (by ripee) wiped everything, except the internal storage, and installed your rom using TWRP-3.3.1-1_UA. My current solution is to modify the GApps package install script so the version check is not failing. At the moment everything is running fine.
Frapl

Thank you @JT1510365 for giving Flo another Android 10 ROM.
Coming from @followmsi aex 7 Aplha.
I see you mentioned 1.5Gb required for system, but I have partitioned with @followmsi 1280_120 script. After reading a post by Clamor about partitions to 1.5Gb required complete format look complex. I skipped the process.
I'm able to clean flash your ROM, with OpenGapps beta Pico (unmount-remount system in TRWP, with @ipdev suggestion).
Run really smoothly so far, but I did encounter 2 problem.
1) video glitch, a fix was given by @ipdev to mod media_codecs.xml (see attached screenshot)
2) when tap battery in settings, it crashed. Return to home screen.
Thanks again!
Update to 2.
After pressed battery in settings, crashed back to home screen. A small window appeared, I select app info and settings info appear. Did the clear cache, no go. Clear cache and storage (Bad idea) and reboot. After the cdroid bootanimation, screen just faded to Black. No lock screen, not able get back into ROM.
Did a complete clean install of ROM only, reboot into ROM. No other things are added, tapping battery in settings still crashed. Is no biggy, does not take away the smoothness of the ROM.
Anyone know how to get weather next to the home screen at a glance?

This is such a fantastic ROM. Thank you so much JT1510365!
No hassle clean install, extremely solid & dependable, and now the daily driver on the FLO.
I do very much wish that it was available for the DEBs.

blambo said:
This is such a fantastic ROM. Thank you so much JT1510365!
No hassle clean install, extremely solid & dependable, and now the daily driver on the FLO.
I do very much wish that it was available for the DEBs.
Click to expand...
Click to collapse
wish granted will try making a deb build tonight
Thank you for your kind words

Happy New year @JT1510365! ?
All the best to you in 2020!
Thanks for creating ROM for all of us, really appreciates your time! ?

JT1510365 said:
wish granted will try making a deb build tonight
Thank you for your kind words
Click to expand...
Click to collapse
Your work, help, and support are very much appreciated JT1510365. Please just take it slow and have fun with it.
Let me know if I can be of help in any way.
And, have a happy, healthy & prosperous New Year!

blambo said:
Your work, help, and support are very much appreciated JT1510365. Please just take it slow and have fun with it.
Let me know if I can be of help in any way.
And, have a happy, healthy & prosperous New Year!
Click to expand...
Click to collapse
Thank you and I will let you know when the deb build is available

Anyone having issues with camera on this build?

JT1510365 said:
Anyone having issues with camera on this build?
Click to expand...
Click to collapse
Camera (still picture and video recording) are working fine for me.

JT1510365 said:
Thank you and I will let you know when the deb build is available
Click to expand...
Click to collapse
I peeked into your crDroid 10 DEB upload folder and found it.
You have done it!
Wipe everything but internal, install crDroid 10 DEB, install open_gapps-arm-10.0-nano-20190928-BETA, install Magisk 20.03. Wipe caches.
Very fast first boot time. No hiccups.
Quick page to page crD setup.
Set smallest width to 703.
Playstore/Google account login no issues.
Backup+ restore no issues.
Magisk SafetyNet Check: Success. No issues.
Good battery life & charge time, no issues.
Screen rotation no issues.
Camera fine no issues.
Networking & VPN Hotspot no issues.
LTE signal XLNT!
So far, this puppy is solid as a rock. Everything that I use it for works. (Wireguard, VPN Hotspot, Netflix, Plex, MXPlayer Pro HW+, email & web browsing, Juice SSH, AdminHands, etc.) No crashes/FCs/errors so far.
A great many thanks to you for your work, and for breathing new life into these DEB & FLO JT1510365! -Android 10 for DEB is a unique challenge, and very much appreciated.
Magnificent!

Is there any custom Kernels that work with 10 roms?

twist3d0n3 said:
Is there any custom Kernels that work with 10 roms?
Click to expand...
Click to collapse
No, sorry

Thanks!

hey how did you got netflix running? cant here. thx!!

Database Info

welcome