[EOL][ROM][11.0][OFFICIAL] crDroid Android v7.19 [hammerhead]

[tmihai20]

Did someone tried dirty flash ? What about network issue ? Thx

I applied the OTA (technically it should be considered a dirty flash) and WiFi is working well. Sim is also working well. I must be lucky then.

 

[Sercan Ali]

Great ROM. Thanks

Sent from my Nexus 5 using Tapatalk

 

[rus43]

You're not the only one with a problem with bootanimation. The AICP firmware has the same problem.

 

[Bouquins]

Hi all ! I installed this ROM, which seems to run without issue. I have a question: is it possible that the date on the screen, when tapped, opens my calendar app ?

Thank you !

 

[wtel]

I dit it.
Same issue, I enter the password, the Wifi network remains "registered" but I can't connect.
Initial setup is blocked there.

Got the same problem with crDroidAndroid-10.0-20200516-hammerhead-v6.6

 

[srepole]

I' ve tested a little trick to bypass bootanimation bug.
Twrp is basically what we need.
Mount system.
Then go to advanced/manager.
We need to find bootanimation.zip and bootanimation file.
They are respectively stored in system/system/media and in system/system/bin
Once find them just rename both adding .bak
Unmount system.
Reboot.
Just give to device about 1 min to completely boot otherwise we will experience some lags.
That' s all.

 

[seraphim5]

Only 2 real issue

So I have only two issues that if fixed would make this ROM solid for me. The first is while scrolling on webpage they randomly freeze this is fixed my hitting home then going back and it's chrome, Firefox and opera on any long scrollable sites IE 9gag or Facebook. The second is talked about already that the boot animation is super slower so to workaround this I just deleted it from media and it defaults to the old Android boot animation that once boots and screen goes dark I can wake it without further issues.

 

[DonCatoli]

The auto download link for android 10 in the main page redirects to the clover 6.7 build, please click below that on the hammerhead 6.6 zip instead.

 

[DonCatoli]

I' ve tested a little trick to bypass bootanimation bug.
Twrp is basically what we need.
Mount system.
Then go to advanced/manager.
We need to find bootanimation.zip and bootanimation file.
They are respectively stored in system/system/media and in system/system/bin
Once find them just rename both adding .bak
Unmount system.
Reboot.
Just give to device about 1 min to completely boot otherwise we will experience some lags.
That' s all.

This prevents the rom from booting up for me, just stays on the Google screen.
Only renaming bootanimation.zip gets me to boot with the generic Android animation and it's a slideshow, one hour in still no boot into the rom.

 

[srepole]

This prevents the rom from booting up for me, just stays on the Google screen.
Only renaming bootanimation.zip gets me to boot with the generic Android animation and it's a slideshow, one hour in still no boot into the rom.

Just follow steps i provided.
You' ll have to rename the file named bootanimation.zip but also bootanimation one.
I specified both paths to easlily find them.

 

[dahawthorne]

For goodness' sake, why are you people obsessing about the boot animation? Yes, I find it slow, but no more intrusive than other ROMS that I've tried - and I've tried a few. I have a six-year-old device running new software and I'm grateful for it. Stop corrupting the devs' work by trying to "make it better" by "improving on" the boot animation, which is of absolutely zero, zero, ZERO relevance to the functionality of the ROM.

 

[DonCatoli]

Just follow steps i provided.
You' ll have to rename the file named bootanimation.zip but also bootanimation one.
I specified both paths to easlily find them.

I'll reiterate, when I rename both system/system/media/bootanimation.zip to system/system/media/bootanimation.zip.bak and system/system/bootanimation to system/system/bootanimation.bak the device won't boot the rom, it just stays on the Google logo. I can only get away with renaming the media file (system/system/media/bootanimation.zip), regardless it is pointless as the rom never loads, it just stays on the slide show animation until the fully charged battery is depleted, I will never to another alternative rom unless this issue is resolved...if it can be.

---------- Post added at 02:31 AM ---------- Previous post was at 02:27 AM ----------

For goodness' sake, why are you people obsessing about the boot animation? Yes, I find it slow, but no more intrusive than other ROMS that I've tried - and I've tried a few. I have a six-year-old device running new software and I'm grateful for it. Stop corrupting the devs' work by trying to "make it better" by "improving on" the boot animation, which is of absolutely zero, zero, ZERO relevance to the functionality of the ROM. Get a life, FFS!

You are commenting without knowing what the situation is as the rom never loads, it just stays on the slide show animation until the fully charged battery is depleted hours later. regardless this is not be something to get passionate about so I will just switch to another rom to avoid upsetting people because a technical issue that should be understood occurred.

 

[vadimkaz]

I decided to try CrDroid as it was recommended as stable (as LOS17 is) and with great customisation opportunities. Previously was happy with LOS 17.1, but why not to try another A10 firmware. The result was just the same as you described here. I am not sure if slow animation leads to slow boot. If this is the issue, there is probably reason to remove it to default one, if not - then the developer is expected to fix something else, and no reason to fight the animation. In my case when I renamed animation files back, the system simply failed to boot (just transformed to endless animation). In fact I am not sure if the project is still in development or it was put aside.

 

[DonCatoli]

I decided to try CrDroid as it was recommended as stable (as LOS17 is) and with great customisation opportunities. Previously was happy with LOS 17.1, but why not to try another A10 firmware. The result was just the same as you described here. I am not sure if slow animation leads to slow boot. If this is the issue, there is probably reason to remove it to default one, if not - then the developer is expected to fix something else, and no reason to fight the animation. In my case when I renamed animation files back, the system simply failed to boot (just transformed to endless animation). In fact I am not sure if the project is still in development or it was put aside.

The older LOS 16 builds of crDroid run fine for me (other than not being able to connect to hidden SSIDs which seems common with LOS spin offs yet work perfectly with LOS builds) so you can revert to that.

 

[hhrokarvi]

crDroid Update:

crDroidAndroid-10.0-20200628-hammerhead-v6.7.zip

Changelog

Short Changelog:
- June Security Patches
- Initial crDroid 6.7 code
- Added per-app sensor block option
- Added Ambient Edge Pulse layout
- Added OxygenOS styled dismiss all button
- Reworked quick QS brightness slider
- Fixed new clocks preview layout in settings
- Fixed an issue with data not connecting on reboot
- Optimized system performance
- Fixed overlap bug in crDroid Settings layout (Finally!!!)
- Added Divided Lines, SFUNY, Oroño, Sammy highlight and MNML clocks
- Added new default Calendar app
- Improved dark theming support
- Added Accuratist font
- Fixed bug with wallpaper that could crash system
- Made some changes to network monitor
- Redesigned BatteryMeterView
- Cleanup some duplicate settings
- Added battery temp on Battery screen in Settings
- Added thermal profiles on Battery screen in Settings
- Fixed Launcher weird UI issue with bottom bar
- Removed Google assistant hint on lockscreen (cleaner UI - shortcut works still)
- Improved Updater UI by adding support links and some more information
- Improved battery consumption
- Improved dark theme support
- Added support for per app network isolation
- Tweaked QS Header image
- Test fix Dialer not updating recent call log after call
- Fixed out of memory issues with Recorder
- Fixed QS Detail Header
- Further refined NetworkTraffic indicator
- Further refined GamingMode
- Removed ringtone audio focus for Wired/BT headset (for now)
- Updated translations


Notes
- Due to bigger System size in this update, you need to repartition your Nexus 5 even if you don't use GApps.
- Tried my fixes for the boot animation, no dice, causing building issues and more, so that issues will remain until I find some better solution.
- Don't flash the Official TWRP 3.4 if you're using repartitioned TWRP, it'll be a bad time.
- Join the Telegram Group for support, queries and banter. Link Here

Stay Safe Everyone!

 

[vadimkaz]

crDroid Update:
- Tried my fixes for the boot animation, no dice, causing building issues and more, so that issues will remain until I find some better solution.

Hi! You are definately wrong. In 6.7 slow animation IS fixed. It is slow only at 1-st boot (and booting takes some 5-7 minutes. All further reboots take aprox 3 minutes with very fast and nice animation.
Upd: the animation starts with
red circle in the middle of display then it becomes blue, splits to several circles (and this is still slow)
then the display goes off (sleeping?) and if you wake it up with power button it suddenly starts "dancing"

 

[DonCatoli]

Hi! You are definately wrong. In 6.7 slow animation IS fixed. It is slow only at 1-st boot (and booting takes some 5-7 minutes. All further reboots take aprox 3 minutes with very fast and nice animation.
Upd: the animation starts with
red circle in the middle of display then it becomes blue, splits to several circles (and this is still slow)
then the display goes off (sleeping?) and if you wake it up with power button it suddenly starts "dancing"

Not for everyone, for me on the first boot is just stays on the bootup animation from 100% charge to 0%, never passes it. crDroid 6.6 works perfectly and is what folks that can't get past the boot animation on 6.7 should stick with until it is resolved.

 

[vadimkaz]

Not for everyone, for me on the first boot is just stays on the bootup animation from 100% charge to 0%, never passes it. crDroid 6.6 works perfectly and is what folks that can't get past the boot animation on 6.7 should stick with until it is resolved.

Yes, sure, the problem should be resolved for all cases: the ways we install and the platform have too many variations. We have a phone motherboard (820 or 821), a display (original or a compatible from aliexpress), memory amount (16\32). Besides we may have boot (locked\unlocked), partitions (original or resized(using one of the 2 resizing methods)). And of course we have different "clearnesses" (what we have wiped before installing). And finally what zips we install with the firmware (partition resizing zip, magisk zip, version of gapps) and exact versions of those. Of course the developer keeps in mind only some of them that he considers might influence upon the problem.

 

[krazyko]

crDroid Update:

Notes
- Due to bigger System size in this update, you need to repartition your Nexus 5 even if you don't use GApps.

Stay Safe Everyone!

Repartition? Does that mean the 1.5G is no longer good enough and we need to bump it up to 2? And with that being the case we can't dirty flash?

 

[ish.org]

Thank you for updating to crDroid 6.7.
I feel this is very stable.
I'm using open_gapps stock with 3gb system partition resized by hand with parted and gdisk.