Related
This is the ONLY thread you guys will talk about the CrDroid ROM.
DONT post questions or whatever at the other leaked AOSP ROM thread else it'll create much confusion
So far annoyances thats been reported are:
• Random reboots (at least for some people)
• Auto-brightness
• Underclocked CPU
• Not working HDR & Panaroma (solved with workaround)
DOWNLOAD LINK FOR CRDROID ROM
http://pan.baidu.com/s/1bnzqPBL
Reserved
Via the Internet
Regarding Random Reboots !
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
M3gAtR0N said:
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
Click to expand...
Click to collapse
LKspro said:
after u have the first reboot, cover the upper sensors and touch the screen while it is off. Then the screen should freeze and rebbot after a while
Click to expand...
Click to collapse
This is from @LKspro
Via the Internet
TiTAN-O-One said:
This is from @LKspro
Via the Internet
Click to expand...
Click to collapse
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Good rom lots of settings but useless... always reboot..
M3gAtR0N said:
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Click to expand...
Click to collapse
Yeah, first time it happens random, but if it once happens to you, then you will be able to reproduce it.
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
wai10691 said:
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
Click to expand...
Click to collapse
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
krispuniq said:
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
Click to expand...
Click to collapse
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
wai10691 said:
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
Click to expand...
Click to collapse
Done... Flashing went ok but after booting all my apps are gone (I didnt do a clean wipe while flashing.. only wiped dalvik)
The apps are gone anyway.. so i went back to recovery and did another clean flash.. Reboot the phone, but no mobile network. Unable to latch on to network even manually.. so may be there is something missing in the boot.img ?
Back key
Anyone can confirm back key in this rom didnt behave as it should after deleting pre-install files such as baidu services apps
edit 1 - looks like it has been warned by the dev as do not delete keyboard input method or else back button wont work..
Where is the link to the ROM. I'd update OP. Also, is there any bugs with the ROM? Or is it working like AOSP?
Via the Internet
Download link
http://pan.baidu.com/s/1bnzqPBL
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
fzurita said:
I just got the 5.1 OTA. It feels a little faster so far. Although, my 5ghz WiFi router doesn't work right anymore. It will only connect at 2.4 GHz.
Click to expand...
Click to collapse
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
the-cortana-project said:
I think it is a bug From Google, the same was with 4.4.3, WLAN bugs and more, i think in next update it will be fixed
Click to expand...
Click to collapse
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
fzurita said:
This has to be a new bug. It used to work fine in 4.4.4 and 5.0.
Click to expand...
Click to collapse
Is there any other issues?
theinspector said:
Is there any other issues?
Click to expand...
Click to collapse
Not that I have seen so far. The camera seems about the same as before. The Wi-Fi bug is kind of annoying though since it limits how fast I can transfer files around.
if only we could have a port for non GPe Z Ultra :victory:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
@scrubber @blueether @egzthunder1
Just received the 5.1 update as well...
Looks like several bugs have been addressed... Seems quicker/less laggy.
Nice that they fixed the charging info on the lock screen that always said the wrong thing when NOT charging...that always bugged the hell out of me for some reason.
Will check back tonight after a day of use.
---------- Post added at 09:27 AM ---------- Previous post was at 09:24 AM ----------
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
SÜPERUSER said:
you tried to flash OTA with unlocked bootloader? ...if so ...lol :silly:
Click to expand...
Click to collapse
Oops! ?
I know, shame on me. I should never attempt to install an update that shouldn't have anything whatsoever to do with my boot loader being locked or unlocked.
Actually, I should probably start paying Google to collect my personal data and ask them each time I install apps as well.
Care to explain exactly in detail why a OTA would failed on a unlocked boot loader? And why it would affect a factory boot loader at that? And why the 5.0 update didn't give a damn (as it should) about if the boot loader was locked or not?
MrSewerPickle said:
My update failed. It rebooted and the started applying then the Android Error icon showed up. I have a unlocked, non-rooted 5.0 install. Anyone else have that problem?
Click to expand...
Click to collapse
Experienced the same issue here.
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
fosselman said:
Didn't work on my GPE either. Had to reboot twice before getting the phone to work. Went into settings to manually look for an update and now it says my phone is up to date even though it is still 5.0.
Click to expand...
Click to collapse
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Mugenmundo said:
Experienced the same issue here.
Click to expand...
Click to collapse
draiko913 said:
Same here. Went to install the update and it failed. Rebooted and now system update is showing that my phone is up to date. Guess I'll have to sideload the ota once someone publishes the link.
Click to expand...
Click to collapse
I just got another notification saying it downloaded it again and is ready to install. Gonna wait til I get off work to install it.
Is anyone able to grab the OTA link and post it?
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
I received my update today too. So far so good.
You can do the :
- App Settings -> Clear Data (on Google Framework services)
- Dial *#*#2432546#*#*
- Settings - > About -> System Update
It may even prompt you to download again before you get to the System Update screen.
Saatvik Shukla said:
If someone is running the 5.1 GPE on their ZU-gpe, can you share the build.prop from it please?
Click to expand...
Click to collapse
Here you go
installing..,
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Any idea what fixes are in this one?
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/...019-04-01.html
https://source.android.com/security/...language=zh_cn
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2019-04-01.html
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
I am dling the factory image now, but boot.img should be in there. Are you sure it was not a bad dl?
-Boot.img is in there. Extract the zip then open the "image-blueline....zip" it is in there. If it is not then something is wrong with your dl.
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
FilthyFord said:
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
Click to expand...
Click to collapse
Native tethering. This method works on my 3 XL as well as my wife's "little" 3 on T-Mobile.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
atu567 said:
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue, cant find stock kernel either.
extracted the zip, fastboot flash boot boot.img, fixed.
jk didnt work oddly enough.
got to login then wouldnt let me use my screen. no touch input.
edit again: update platform tools fixed problem. https://dl.google.com/android/repository/platform-tools_r28.0.2-windows.zip
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
wssxzzzz said:
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
Click to expand...
Click to collapse
No problem with safetynet here.
sliding_billy said:
No problem with safetynet here.
Click to expand...
Click to collapse
Ok, thank you, I think that is my problem.
wssxzzzz said:
Ok, thank you, I think that is my problem.
Click to expand...
Click to collapse
What is the problem?
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
benj! said:
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
Click to expand...
Click to collapse
Def the cam app I noticed too and I'm on Jan update, it's nice tho!
I installed the April update to fix the flashing bug of the ambient display, bit it is still there. Any body else having this issue? Also, is there any fix for this?
After updating my Pocophone to the latest version, both my mobile data and wifi took a significant hit in speeds, it was able to hit 2.4mbps easily while now it can barely hit 200kbps. Has anyone else experienced this and does anyone have any idea on how to fix this and if not, how do I let Xiaomi know of this so they can fix this?
Rettro said:
After updating my Pocophone to the latest version, both my mobile data and wifi took a significant hit in speeds, it was able to hit 2.4mbps easily while now it can barely hit 200kbps. Has anyone else experienced this and does anyone have any idea on how to fix this and if not, how do I let Xiaomi know of this so they can fix this?
Click to expand...
Click to collapse
Most probably the OTA update messed it up. Try factory re-setting or a clean flash of the ROM.
In my case, March update had made my mobile data very unreliable. But rebooting the poco fixed it. So try rebooting once if you haven't done that.
Yeah it's been buggy sometimes when I long press wifi icon in the menu it wont do anything
tnsmani said:
Most probably the OTA update messed it up. Try factory re-setting or a clean flash of the ROM.
Click to expand...
Click to collapse
Was hoping it wouldn't have to come to this but might try it. Do you reckon waiting for next months patch would fix it? Is factory resetting my only hope?
lockhrt999 said:
In my case, March update had made my mobile data very unreliable. But rebooting the poco fixed it. So try rebooting once if you haven't done that.
Click to expand...
Click to collapse
I've rebooted it plenty and it doesn't do much. Unless you mean factory resetting like the other lad said.
Rettro said:
Was hoping it wouldn't have to come to this but might try it. Do you reckon waiting for next months patch would fix it? Is factory resetting my only hope?
Click to expand...
Click to collapse
Try a clean flash of the same version of the ROM without wiping internal storage.
tnsmani said:
Try a clean flash of the same version of the ROM without wiping internal storage.
Click to expand...
Click to collapse
I'm quite new to rooting and flashing so could you lend me a hand as to how to approach that? Also, if i choose to wait, is it likely the next months OTA will fix these issues?
Rettro said:
I'm quite new to rooting and flashing so could you lend me a hand as to how to approach that? Also, if i choose to wait, is it likely the next months OTA will fix these issues?
Click to expand...
Click to collapse
If you don't fully understand the process of flashing and the difficulties involved, then it might be better to wait for the update. However, you can learn about the processes in the meanwhile and if the update doesn't solve your issue, then you can try a clean flash of the ROM.
tnsmani said:
If you don't fully understand the process of flashing and the difficulties involved, then it might be better to wait for the update. However, you can learn about the processes in the meanwhile and if the update doesn't solve your issue, then you can try a clean flash of the ROM.
Click to expand...
Click to collapse
Alright, thanks for your help man. I appreciate it
Just checked updates and there it was.
gaww said:
Just checked updates and there it was.
Click to expand...
Click to collapse
Installing now, I wonder what the exact changelog, wish they have more info with these updates
champ784 said:
Installing now, I wonder what the exact changelog, wish they have more info with these updates
Click to expand...
Click to collapse
Please post how things went - especially if you are rooted (?), as its easy to end up unrooted at times.
OTA is failing for me after unrooting. I also restored the latest restore.img from the relevant thread before I attempted to update.
Anyone with root able to get OTA installed?
NotATreoFan said:
OTA is failing for me after unrooting. I also restored the latest restore.img from the relevant thread before I attempted to update.
Anyone with root able to get OTA installed?
Click to expand...
Click to collapse
I have not updated, but it will continue after rebooting - is there any way to stop it ?
gaww said:
I have not updated, but it will continue after rebooting - is there any way to stop it ?
Click to expand...
Click to collapse
The update was already downloaded to my phone, but did not attempt to install until I started it manually.
NotATreoFan said:
The update was already downloaded to my phone, but did not attempt to install until I started it manually.
Click to expand...
Click to collapse
I am not so worried about rerooting if it is necessary, but am very worried about getting wiped. How did yours come out ?
gaww said:
I am not so worried about rerooting if it is necessary, but am very worried about getting wiped. How did yours come out ?
Click to expand...
Click to collapse
I'm all set. No wipe, and rooted again on 10.0.31.
NotATreoFan said:
I'm all set. No wipe, and rooted again on 10.0.31.
Click to expand...
Click to collapse
Did you have to unroot before updating ?
Never-mind had to unroot it would not work otherwise. But still wont finish - maybe because i may still have a different then stock kernel even though I unrooted.
gaww said:
Did you have to unroot before updating ?
Never-mind had to unroot it would not work otherwise. But still wont finish - maybe because i may still have a different then stock kernel even though I unrooted.
Click to expand...
Click to collapse
You need to unroot, and also make sure you have the reserve.img partition restored. If you unlocked the bootloader after the .27 OTA, reserve.img is deleted during unlock.
NotATreoFan said:
You need to unroot, and also make sure you have the reserve.img partition restored. If you unlocked the bootloader after the .27 OTA, reserve.img is deleted during unlock.
Click to expand...
Click to collapse
I had read something about that file earlier, but forgot about. I spent hours trying to get it updated to no avail. i will search, but wondered if you could show me the way to do that,
gaww said:
I had read something about that file earlier, but forgot about. I spent hours trying to get it updated to no avail. i will search, but wondered if you could show me the way to do that,
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/7t...d1925-10-0-19-fastboot-rom-ota-fixer-t4040629
Download the newest package in the first post, and then download the updated userdata.img from this post: https://forum.xda-developers.com/showpost.php?p=82141557&postcount=117
NotATreoFan said:
Go here: https://forum.xda-developers.com/7t...d1925-10-0-19-fastboot-rom-ota-fixer-t4040629
Download the newest package in the first post, and then download the updated userdata.img from this post: https://forum.xda-developers.com/showpost.php?p=82141557&postcount=117
Click to expand...
Click to collapse
Will this cause a wipe ? If so, will wait for a bigger update.
I'm not currently rooted, so my results won't matter too much atm
gaww said:
Will this cause a wipe ? If so, will wait for a bigger update.
Click to expand...
Click to collapse
No. All data will be intact. You are not formatting or overwriting userdata.
NotATreoFan said:
No. All data will be intact. You are not formatting or overwriting userdata.
Click to expand...
Click to collapse
All I have to do is to not screw up, and after having been on Samsungs since S3, where most things were straight forward and relatively easy, there is a good chance I will.
Will be doing more reading - wish there was a guide like the unlocking and rooting of the US TMo guide thread.
gaww said:
All I have to do is to not screw up, and after having been on Samsungs since S3, where most things were straight forward and relatively easy, there is a good chance I will.
Will be doing more reading - wish there was a guide like the unlocking and rooting of the US TMo guide thread.
Click to expand...
Click to collapse
It's very simple, and the script does most of the work. All you have to do is hit Enter a few times, and let it run.
Back up your data to be safe, and worse case scenario, there is an MSM tool available that will restore the phone to stock.
NotATreoFan said:
It's very simple, and the script does most of the work. All you have to do is hit Enter a few times, and let it run.
Back up your data to be safe, and worse case scenario, there is an MSM tool available that will restore the phone to stock.
Click to expand...
Click to collapse
Is there a better backup than Google Drive for data - was so easy with TWRP ?
gaww said:
Is there a better backup than Google Drive for data - was so easy with TWRP ?
Click to expand...
Click to collapse
Use Google Drive backup, but you should first temporarily turn off your password/fingerprint authentication. That's the only way to ensure a complete backup is run. That's been an issue with Google device backup as a whole since 9.0 began enforcing encryption on backups.
You can turn it back on as soon as the backup completes.
One thing I've noticed already on this update is idle battery drain with 5G enabled (connected or not) has improved dramatically.
I would suggest that anyone who re-roots after makes sure to use a freshly patched kernel pulled after the update.