[ROM][UNOFFICIAL][CM13.0][6.0.1][VirginMobileUS][A5][single-sim][7/5/2016 security] - Desire 816 Android Development

Marshmallow!
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:
shantanu223 said:
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.
Click to expand...
Click to collapse
post 3 has various user-supplied fixes, thanks y'all!
Flashes fine with official TWRP.
Official HTC firmware here:
http://www.htc.com/us/support/htc-desire-816-virgin-mobile/news/
Instructions to install the stock firmware (use the posted recovery.img and the new RUU from the previous link)
http://forum.xda-developers.com/desire-816/general/ruu-t2952058
Instructions to extract zip from RUU to flash from sdcard with hboot
http://forum.xda-developers.com/showpost.php?p=62680799&postcount=4
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.
xXminiWHOOPERxX said:
Okay ,
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
Click to expand...
Click to collapse
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.
Working:
graphics
touchscreen
rotation/tilt
compass
sound
sdcard
internal storage
mass storage file transfer
root
LTE
MMS
SMS
Phone incoming and outgoing calls
Network location
GPS
Bluetooth
WiFi (including hotspot)
USB tether
camera
sd card as internal storage
FM radio
NFC
not working
you tell me. preferably with attached logcat/dmesg.
Current A5 ROM folder:
https://androidfilehost.com/?w=files&flid=45601
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.
Source:
old, hidden
commits to 1/09/16 work. later are lost.
(cm-13.0 branch)
https://github.com/bigsupersquid/android_device_htc_a5
https://github.com/bigsupersquid/proprietary_vendor_htc
(cm-13.0-caf)
https://github.com/bigsupersquid/android_packages_apps_SnapdragonCamera
(master)
https://github.com/bigsupersquid/vendor_cm_prebuilt_common_etc_apns-conf.xml
https://github.com/bigsupersquid/kernel_htc_msm8974_arch_arm_configs_cm_a5_defconfig
needs but not built in yet: https://github.com/bigsupersquid/frameworks_base_core_res_res_xml_eri.xml
current sources:
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
Code:
<?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>
repo sync, then lunch cm_a5ul-userdebug, then mka bacon and profit
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

---

screenshots
And here's some screenshots.

---

Facebook fix
flashing advice
vm apns (obsolete in latest builds)
long press 1 for voicemail (obsolete in latest builds)
visual voicemail
VM eri.xml (carrier name and 3g icon) (obsolete in latest builds)
ringplus apn (mvno slayer r4 reported to work, thanks @dforestb
Reset APNs for lte and MMS issues
GreyCelt said:
you may or may not recall the problem I was having with using Adoptable Storage and not being able to flash anything from the SD card once it was formated as Internal Storage,
GreyCelt said:
I found a work-around for not being able to flash zip files in TWRP if your SD card is formatted as Internal Storage. The app Flashify from the Google Play Store will do the job.
You do, however, have to pay $3.99 for the app if you want to flash more than 3 zip files per day....
Click to expand...
Click to collapse
I found an app in the Play Store called Root Essentials that has amongst its many features, an Adoptable Storage feature that will partition your SD card & lets you use part of it as Internal Storage and part of it as Portable Storage. You can save flashable items to the portable partition and they are accessible in recovery.
Click to expand...
Click to collapse
Personally, I like FlashFire by Chainfire too. It's like recovery in an app.

---

Great! Once WiFi works I'll try it out. Thanks.

---

Have tried the rom for 2hrs here is the review
*rom is smooth
*reliance India sim is working with data
*only 10% present battery drop after using the rom
Now the cons....
* WiFi not working
*as mentioned camera is not working.. Have tried all flashable camera zip snapdragon, oppo etc
* mobile restart while opening bluetooth
Thanks bro, atleast someone is working on cm 13
Hope soon we will see a big free cm 13 rom

---

vip1327 said:
Have tried the rom for 2hrs here is the review
*rom is smooth
*reliance India sim is working with data
*only 10% present battery drop after using the rom
Now the cons....
* WiFi not working
*as mentioned camera is not working.. Have tried all flashable camera zip snapdragon, oppo etc
* mobile restart while opening bluetooth
Thanks bro, atleast someone is working on cm 13
Hope soon we will see a big free cm 13 rom
Click to expand...
Click to collapse
WiFi and Bluetooth are having issues inserting firmware.
The camera driver can't identify the sensors yet.
And GPS is missing a stock lib that currently makes it bootloop.
Glad service and data are working for more than VM USA models.
Oh, and that high battery drop is probably from it trying to turn on WiFi. It won't give up and the phone actually gets pretty hot at the top unless you let it sleep.
Thanks for info.

---

so for whatever reason, when I was testing early on, /system/lib/hw/gps.default.so seemed to be causing bootloops.
Well, now it doesn't anymore. And my gps is working.
I'll upload another build in a while. Or you can try
Code:
adb root
adb remount
adb push gps.default.so /system/lib
and see if it fixes the first released build. Mine is different (experimentation, y'all) and it may possibly still bootloop the first release.
If it does, and you have adb enabled and authorized, you can just
Code:
adb root
adb remount
adb shell rm /system/lib/gps.default.so
and that should fix the botloop.
anyway... here, try it. It may be a while before I upload another build, takes a while.

---

it wont detect any sim on a5dug any solutions

---

joewyg said:
it wont detect any sim on a5dug any solutions
Click to expand...
Click to collapse
not right off but I'll add it to the OP.
did my cm12.1 12/25 build detect any sim? mostly same device folder but the RIL has been updated for 6.0.1. If the lollipop version didn't see a sim card there's not much I can do without one of those in hand to test on.

---

gonna test it and let you know, I've used other cm12.1 roms that worked though
your cm12.1 12/25 detected my sim

---

You should use my trees. I have almost everything working except camera and green lines when playing a video. But remove the camera fix before building. Will cause bootloop
Sent from my ONE A2001 using XDA Free mobile app

---

Grarak said:
You should use my trees. I have almost everything working except camera and green lines when playing a video. But remove the camera fix before building. Will cause bootloop
Sent from my ONE A2001 using XDA Free mobile app
Click to expand...
Click to collapse
awesome.
If I'd have realized you were working on this I might not have put the effort into it...
Thanks!

---

Grarak said:
You should use my trees. I have almost everything working except camera and green lines when playing a video. But remove the camera fix before building. Will cause bootloop
Sent from my ONE A2001 using XDA Free mobile app
Click to expand...
Click to collapse
Glad to know ur working on the CM13. Hope to see a stable release soon. [emoji2]

---

Grarak said:
You should use my trees. I have almost everything working except camera and green lines when playing a video. But remove the camera fix before building. Will cause bootloop
Sent from my ONE A2001 using XDA Free mobile app
Click to expand...
Click to collapse
I haven't seen any green line glitches using the latest caf adreno 3xx drivers from December, the nexus 5 version from the Qualcomm zip, using them with either device tree.
Something isn't working with the single sim, not recognized, so no cell functions yet.
WiFi and Bluetooth are spot-on though.

---

bigsupersquid said:
I haven't seen any green line glitches using the latest caf adreno 3xx drivers from December, the nexus 5 version from the Qualcomm zip, using them with either device tree.
Something isn't working with the single sim, not recognized, so no cell functions yet.
WiFi and Bluetooth are spot-on though.
Click to expand...
Click to collapse
I have been able to use single sim version for calls, sms and data.
WiFi, camera bug should be fixed ie. Only not working

---

vip1327 said:
I have been able to use single sim version for calls, sms and data.
WiFi, camera bug should be fixed ie. Only not working
Click to expand...
Click to collapse
I meant using Grarak's device tree. I haven't released a build from that yet.

---

For me incoming calls are not working with your build ( did not tested the 12-31 build) , and i have the "disconnecting" problem when ending a call like in cm 12.1.

---

drummer1839 said:
For me incoming calls are not working with your build ( did not tested the 12-31 build) , and i have the "disconnecting" problem when ending a call like in cm 12.1.
Click to expand...
Click to collapse
Do you have single or dual sim? A5 model variant (chl etc.)?
Carrier?
The 12/31 is the only marshmallow build yet. All my a5 ROMs are in a single shared folder as yet.
But if you're having service problems with the cm12.1 builds odds are the cm13 won't treat you any better.

---

bigsupersquid said:
Do you have single or dual sim? A5 model variant (chl etc.)?
Carrier?
The 12/31 is the only marshmallow build yet. All my a5 ROMs are in a single shared folder as yet.
But if you're having service problems with the cm12.1 builds odds are the cm13 won't treat you any better.
Click to expand...
Click to collapse
I have the single sim A5 and was having the service issues.

---

Clarkie_955i said:
I have the single sim A5 and was having the service issues.
Click to expand...
Click to collapse
What is your model variant (chl, ul), CDMA or gsm, and carrier? Gsm and dual sim phones are having issues with my builds.