Unofficial CrDroid-OSv6 Android 10

khalvat · Oct 1, 2020

Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn

Always Have a full functional Backup. Just in case!

Rom Download Link :
https://androidfilehost.com/?fid=8889791610682935022

Lineage Recovery link :
https://androidfilehost.com/?fid=8889791610682935019

Recomended Bootloader/Modem : https://androidfilehost.com/?fid=3700668719832239236 (I9506XXUDRB1_I9506XXUDRA1)

GAPPS: DOWNLOAD GAPPS - Not updated yet for 10.0 -- use Beta from link below
Platform: ARM
Android: 10.0
OpenGapps : https://opengapps.org/
BITAGaaps : https://androidfilehost.com/?fid=4349826312261650978

Device Source:
Device : https://github.com/Khalvat-M/android_device_samsung_ks01ltexx
Kernel : https://github.com/Khalvat-M/kernel_samsung_msm8974
Vendor : https://github.com/Khalvat-M/vendor_samsung

** Make sure you're running a proper working Recovery (TWRP is recommended)
TWRP Link : https://dl.twrp.me/ks01lte/
1) Copy crDroid zip, GAPPS zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
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, Android 10 is now supported)

ROM Asking for Decryption key on boot:
This isn't a ROM issue, but an issue with your device. Kindly boot into TWRP and go to wipe - choose FORMAT - TYPE - YES
***This WILL wipe your INTERNAL storage. Backup before performing the format.

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
1. You tell me

Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed
- have modified system files

Thanks to:
- fagyi - Can't stress enough how much you do. Thank you so much for everything!!!
- Google
- LineageOS
- SlimRoms
- AOSPA
- AOSIP
- AICP
- OmniRom
- NamelessROM
- Many others... (if you've been left out just send a PM )

XDA

evDB Information
[ROM] [10.0] crDroidAndroid v6.0 [UNOFFICIAL], ROM for the S4 i9506( ks01lte)

Contributors
khalvat
Source Code: https://github.com/crdroidandroid

ROM OS Version: Android 10
Based On: LineageOS

Version Information
Status: Stable

Created 2019-12-10
Last Updated 2020-09-11

jegogo99 · Dec 11, 2019

mod edit: translated

Long live the S4. Thanks for the input

Sent from my POCO F1 mediante Tapatalk

Larga vida al S4. Gracias por el aporte

Enviado desde mi POCO F1 mediante Tapatalk

DiamondJohn · Dec 11, 2019 at 1:05 AM

Which bootloader and Modem is it built for?

khalvat · Dec 11, 2019 at 1:18 AM

DiamondJohn said:
Which bootloader and Modem is it built for?

Added in post

Negan · Dec 11, 2019 at 2:40 AM

jegogo99 said:
mod edit: translated

Long live the S4. Thanks for the input

Sent from my POCO F1 mediante Tapatalk

Larga vida al S4. Gracias por el aporte

Enviado desde mi POCO F1 mediante Tapatalk

Hey there please remember to post in english! I translated it for you!

DiamondJohn · Dec 11, 2019 at 4:11 AM

khalvat said:
Guys I will not update Havoc until its problams are resolved. Our new android 10 CrDroid is available and its stable working android 10 features well:good:

FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.

crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.

I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.

khalvat · Dec 11, 2019 at 4:40 AM

DiamondJohn said:
FYI: I cannot get Magisk 20.1 installed on crDroid. however, the playstore does download and install apps.

crDroid home launcher crashes every time(see attached for logcat), pixel launcher works.

I also didn't get a GPS Fix. Admittedly indoors, but my current Havoc-OS Oreo did right next to it.

All good here. No any crash

1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds

khalvat · Dec 16, 2019 at 10:43 PM

New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze

DiamondJohn · Dec 17, 2019 at 9:54 AM

khalvat said:
All good here. No any crash
1 Flash Rom without gapps and boot to rom
2 After working for a while reboot and flash latest beta gapps
3 magisk for root will fix soon in next builds

khalvat said:
New build 2019-12-16 is Available
Device changelog:
Fixed some minor bugs
Added samsung Doze

I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.

Would a clean flash enable Magisk?

khalvat · Dec 17, 2019 at 1:56 PM

DiamondJohn said:
I just dirty flashed the latest build over the previous build. It tried to re-instate Magisk, but failed.

Would a clean flash enable Magisk?

Sorry Magisk issue still not fixed.

kiprio · Jul 21, 2007 11 2 0

When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.

khalvat · Dec 25, 2019 at 7:31 PM

kiprio said:
When I launch the music player, it seems, that the sound is skewed. The some is when I use the "Duolingo". In the previous version is all right.

Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build

DiamondJohn · Dec 26, 2019

khalvat said:
Yeah. I know.its was my mistake in latest build. Fixed audio bug now so wait for new build

I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:

The changes I had to make to get it to build (from memory)

Code:

echo "#  dummy" > hardware/samsung/AdvancedDisplay/Android.mk;
echo "#  dummy" > device/samsung/qcom-common/doze/Android.mk;

## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B])
##    [B]remove line 56[/B]
##	[B][email protected] \[/B]

Is that related to above issue?

I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?

So, the takeaway is the source can be built pretty easily :good:

Can anyone check bluetooth audio?

===================================
edit: the actual error

Code:

hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "[email protected]service (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"

khalvat · Dec 26, 2019 at 8:09 PM

DiamondJohn said:
I have successfully built the ROM from your source:good:, but I have not test-flashed it to see if it works.:fingers-crossed:

The changes I had to make to get it to build (from memory)

Code:

echo "# dummy" > hardware/samsung/AdvancedDisplay/Android.mk; echo "# dummy" > device/samsung/qcom-common/doze/Android.mk; ## (geany [B]hardware/interfaces/audio/common/all-versions/default/service/Android.mk[/B]) ## [B]remove line 56[/B] ## [B][email protected] \[/B]

Is that related to above issue?

I personally do not use bluetooth audio (so NO issue for me personally), but does the above mean there is an issue with bluetooth audio? or do you use another fix not in github?

So, the takeaway is the source can be built pretty easily :good:

Can anyone check bluetooth audio?

===================================
edit: the actual error

Code:

hardware/interfaces/audio/common/all-versions/default/service/Android.mk: error: "android.hardware[email protected] (EXECUTABLES android-arm) missing [email protected] (SHARED_LIBRARIES android-arm)"

Nice:good:. If u can start pixelexprience build and share in our XDA page.

DiamondJohn · Dec 26, 2019 at 11:00 PM

khalvat said:
Nice:good:. If u can start pixelexprience build and share in our XDA page.

Two problems there.
1. I build for my own devices/uses and share on XDA if there is no-one else building it, or has provided a recent build.
2. I like the most eye candy I can get

, and Pixel Experience is targeted for an AOSP experience :cyclops:. ie not for me.

misy · Dec 27, 2019

I can not get the GPS fix. The phone sees many satellites, but does not fix the position. How can I solve this?
PS. GOOD ROM. The battery lasts a long time!

replaced by I9506XXSDPL2_I9506XXUDOJ2_bootmodem GPS fix- OK!!!

DiamondJohn · Dec 29, 2019

A rooted crDroid!

khalvat said:
Sorry Magisk issue still not fixed.

FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:

Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:

oooo.... it really did not like the install of the latest viper, which uses Magisk.

khalvat · Dec 29, 2019 at 10:12 PM

DiamondJohn said:
FYI I just did a build using @kyasu kernel, and the small changes I noted above, and it built without a hitch, and Magisk flashed AND is working. So I now have a rooted crDroid :highfive:

Code:

<?xml version="1.0" encoding="UTF-8"?> <manifest> <project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-17.0" /> <project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-17.0" /> <project name="Khalvat-M/android_device_samsung_ks01ltexx" path="device/samsung/ks01ltexx" remote="github" revision="10.0" /> <project name="Khalvat-M/vendor_samsung" path="vendor/samsung" remote="github" revision="10.0" /> <project name="Khalvat-M/kernel_samsung_msm8974" path="kernel/khalavat_samsung/msm8974" remote="github" revision="10.0" /> <project name="kyasu/android_kernel_samsung_msm8974" path="kernel/samsung/msm8974" remote="github" revision="lineage-17.0-test" /> </manifest>

Not being rooted meant not being able to actually install/use my most commonly used apps. So this will be good until you get your kernel sorted:good:

oooo.... it really did not like the install of the latest viper, which uses Magisk.

Yeah it was from kernel but im working on other devices so have not time for change kernel source for now.

Also add devicesettings in roomservices from linneageos

khalvat · Jan 2, 2020

New build 2020-01-01 is Available
Fixed bugs

I had not time to fix root problam so i will fix in next build
Happy new year???️??Merry christmas

ameshiya · Jan 2, 2020 at 8:25 AM

khalvat said:
New build 2020-01-01 is Available
Fixed bugs

I had not time to fix root problam so i will fix in next build
Happy new year?️Merry christmas

Great News Sir

HNY & MC , Wishes You All The Success in Your Pro And Perso life

Regards .

Unofficial CrDroid-OSv6 Android 10

Senior Member

Senior Member

Recognized Contributor

Senior Member

Forum Moderator / Recognized Themer

Recognized Contributor

Attachments

Senior Member

Senior Member

Recognized Contributor

Senior Member

Member

Senior Member

Recognized Contributor

Senior Member

Recognized Contributor

New member

Recognized Contributor

Senior Member

Senior Member

Senior Member