Special for the a5_chl Virgin Mobile US Desire 816, may work ok on other (single-sim) a5's too.
for dwg, dug:
Grarak's official cm13 for dual sim
dual-sim initialization tip:
OK..let me clarify few doubts for new users 21st Build
1) SIM 1 Calling / Data working. In-call volume working
2) Sim 2 Calling / Data works but In-call volume NOT working. Basically you won't hear anything.
3) Wifi works, GPS works.
Persisting issue: SIM 1 network mode shows WCDMA Preffered in engineering mode (*#*#4636#*#*) however network type always sticks to 3G mode. It does not switch to 2G when 3G is unavailable hence there will no network coverage at all.
Probable fix: While installing the ROM, insert 2 SIM cards in SIM1 and SIM2 slot both. Make sure the after first boot, both Sim cards must be initialized. After initialized you can set preferred data SIM as SIot 1. The network mode will be set to GSM/CDMA (Auto Prl). Thats when SIM 1 will be able to auto switch 3G and 2G and network coverage will be stable.
***Initializing only SIM2 card slot after first boot might make wifi intermittent. Hence advised to initiate both slots after first boot time.***Initializing only SIM1 card slot after first boot will set network mode to WCDMA Preferred and network coverage will be unstable as stated above***.
Hence advised to initiate both slots after first boot time.
Flashes fine with official TWRP.
Official HTC firmware here:
Instructions to install the stock firmware (use the posted recovery.img and the new RUU from the previous link)
Here, I uploaded official Lollipop 0P9CIMG.zip for you guys.
copy 0P9CIMG.zip to external sd card. Remove card.
After flashing stock recovery,
fastboot oem lock, insert sdcard, and then reboot into hboot.
remove the file after it finally finishes multiple reboots into htc stock.
I strongly suggest updating your firmware to htc lollipop with an official ruu or you may have hardware issues like touchscreen, wifi, and/or bluetooth problems. It might work with kitkat firmware though, and you are free to try if you want. Post results if you do.
It appears kitkat firmware can cause not only touch issues but wifi issues.
Rom and firmware are two different things... inside OTA's it contains a firmware.zip at which updates bootloader, radio, etc.... so without taking firmware upgrades and just installing what's released on XDA will lead you to bugs other users don't have ..
For Example :
4.4.4 firmware will work with 5.0.2 fine for some users and some have to update too 5.0.2 for Wi-Fi to work...
But any Android version past 5.0.2 you need to have either lollipop firmware or marshmallow firmware in order for Wi-Fi to work...
Sent from my 831C using Tapatalk
Disclaimer: Void warranty, not responsible for anything, you know flashing is your choice and any damage is your own problem.
ESPECIALLY with a beta like this.
Wipe cache, data, and system for clean flash.
Dirty flash not recommended but may work.
if you dirty flash don't complain about bugs.
verify they happen on a clean flash too, without installing any other zips. then post your issue, and send me a logcat.
If you install gapps, use the ARM/6.0 versions, and either install them on a clean flash or wipe the dalek-cache before rebooting.
It's still beta, so expect weird bugs.
mass storage file transfer
Phone incoming and outgoing calls
WiFi (including hotspot)
sd card as internal storage
you tell me. preferably with attached logcat/dmesg.
Current A5 ROM folder:
You'll want to grab the a5ul version in the front folder. Newest date.
Advise placing the md5sum file with it on the sdcard before flashing, TWRP will check that the file was downloaded without corruption that way.
as of 7/8/2016, built with Vynikal's fork of JustArchi's optimized build flags, with UBER 5.3 toolchains.
also with sepolicy support for SuperSU, and Viper4Android.
needs but not built in yet: https://github.com/bigsupersquid/fra...es_xml_eri.xml
get UBER arm-eabi 5.3 from here
decompress it, copy the UBERTC-arm-eabi-5.3-* folder to prebuilts/gcc/linux-x86/arm/arm-eabi-5.3 (instead of prebuilts/gcc/linux-x86/arm/UBERTC-arm-eabi-5.3-*)
official CM repo with these changes:
init cm repo to 13.0 instead of 12.1 as in the instructions.
roomservice.xml, goes in your build directory/.repo/local_manifests
<?xml version="1.0" encoding="UTF-8"?> <manifest> <project name="bigsupersquid/android_kernel_htc_msm8974" path="kernel/htc/msm8974" remote="github" revision="cm-13.0" /> <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" /> <project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" /> <!-- <project name="CyanogenMod/android_hardware_sony_thermanager" path="hardware/sony/thermanager" remote="github" /> <project name="CyanogenMod/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="cm-13.0" /> --> <project name="bigsuperprojects/android_device_htc_a5ul" path="device/htc/a5ul" remote="github" revision="cm-13.0" /> <!-- <project name="Grarak/android_device_htc_a5dwg" path="device/htc/a5dwg" remote="github" revision="cm-13.0" /> --> <project name="Grarak/android_device_htc_a5-common" path="device/htc/a5-common" remote="github" revision="cm-13.0" /> <project name="bigsupersquid/Android-Blob-Utility" path="external/android-blob-utility" remote="github" revision="master" /> <!--<project name="Grarak/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-13.0" /> --> <project name="bigsuperprojects/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-13.0" /> <remove-project name="CyanogenMod/android_packages_apps_CMUpdater" /> <project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" /> </manifest>
The gcc-5.3 fix commits are spread all over the android tree, and JustArchi's flags are in android_build... I'm not going to fork and maintain all that stuff. I'll post individual commits for patching later, and a squid branch of device_htc_a5ul for the optimisations. Use the cm-13 branch and it'll build with all the regular CM stuff. Use the optimised one, and you may be hunting down fixes with Google for errors that pop up through the build.
Thanks to @Grarak for all the hard work on upstream source code and fixes for the a5. And CM of course. And all the device maintainers, developers, forum posters, and whoever else I ruthlessly kanged bits and parts of this from.
A big THANK YOU to donators: @sorensenbill, @clydeml, @aftertzf, @Ed128, @ajones23