[ROM] [27 DEC 2015] CyanogenMod 11.0 [4.4.4] [Stable] - HTC Desire 610

CyanogenMod 11.0 is a free, community built distribution of Android 4.4 (KitKat) which greatly extends the capabilities of your phone.
These are unofficial builds of CM11.0 for the HTC Desire 610.
To hear about the latest updates and changes to CyanogenMod as a whole, you can follow +CyanogenMod on Google+!
My change log is in post #2.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What doesn't work yet
- NFC
Installation Instructions
1. You must unlock your bootloader or be S-OFF.
2. You must have a custom recovery installed that allows SELinux. Get TWRP build for HTC Desire 610 from here.
3. Download the current HTC Desire 610 build from here. The MD5 file for it is here if you want to check you downloads integrity.
4. Get Gapps from here.
5. Fully wipe your device from TWRP Recovery. eg Format "System" and Factory Reset.
6. Install Rom and Gapps from TWRP Recovery then Wipe dalvic and cache then Reboot.
Note: If you want to use Xposed Framework you will need to flash the a3ul_xposed_fix.zip in post#3. But be warned, it reverts a few framework files to an older version and MAY give some unwanted side effects.
Credits
- CyanogenMod Team.
- u-ra for his work on the MEMUL which I used as a template to bring up the A3UL.
XDA:DevDB Information
CM11 for HTC Desire 610, ROM for the HTC Desire 610
Contributors
MiniBlu
Source Code: https://github.com/MiniBlu
Kernel Source Here
Device Tree Here
Vendor Files Here
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2015-12-27
Beta Release Date: 2015-12-08
Created 2015-12-08
Last Updated 2015-12-27

---

Change Log
27 Dec 2015
- Re-synced to upstream sources.
- Fixed camera.
- Fixed speaker phone.
- Improved external SD card access.
- Improved GPS lock times in some regions.
- Removed some unused drivers and libraries.
8 Dec 2015
- Synced to latest upstream sources (security patches for all stagefright bugs)
- fixed battery drain when screen off (Wake lock issue with play services)
- Set LCD density back to 240 DPI
- Partially fixed camera
2 Dec 2015
- 1st test version released

---

Optional Extras
- Fix for xposed framework not installing is here. (only flash this if you really want to use xposed as it is a hack that MAY cause some unintended strange behaviour) .Just flash it from TWRP and reboot.
- Sense 7 addon zip for a3ul_CM11. This is an addon zip that adds the sense 7 launcher and some sense 7 apps to the system partition. Just Install it from TWRP then wipe dalvic & cache and reboot. Once rebooted, select "Sense Home" as your default launcher. All credit for porting these apps goes to @xpert I have just packaged a few of his apps that seem to work OK on our device into a flashable zip that installs them to the system partition so you won't get left with no available space on your data partition. If you use this don't forget to go and thank him here

---

Reserved
Delete

---

I'm on the first build, do I just dirty flash the new build, or clean wipe and install the new build?

---

Can't wait for everything to be fixed and for lollipop. Thank you MiniBlu.

---

Wow, great work I'm waiting for camera fix

---

On the previous build I could use xposed but now when I try to install I get this
Any reason why?

---

Bug: Spotify app no working

---

Att
Would this rom work on the att version

---

Ok my upgrade path was
Twrp install zip
Clear dalvic
Reboot
(dirty upgrade)
Seems fine so far but I will keep testing
MGfusion said:
On the previous build I could use xposed but now when I try to install I get this
Any reason why?
Click to expand...
Click to collapse
Confirmed bug, won't work for me either
Pocho121 said:
Bug: Spotify app no working
Click to expand...
Click to collapse
Works perfect here

---

MGfusion said:
On the previous build I could use xposed but now when I try to install I get this
Any reason why?
Click to expand...
Click to collapse
Apparently the latest CM11 upstream changes with security patches cause this, you can find info on it here http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
I have attached an update zip called A3UL_xposed_fix.zip to this post and linked to it in the optional extras post (post#3). Just flash it from TWRP and reboot to fix this.

---

DaGWaR said:
Would this rom work on the att version
Click to expand...
Click to collapse
Yes. It will work on at&t version. You may see some minor screen resolution issues. If you do let me know and I'll add a separate build variant to the rom for at&t devices.

---

MGfusion said:
I'm on the first build, do I just dirty flash the new build, or clean wipe and install the new build?
Click to expand...
Click to collapse
Dirty flash should be OK if coming from previous cm version. But because off changes to google services I would recommend formatting "system" partition to make sure gapps is cleaned up properly. And always wipe dalvic and cache after installing rom and gapps.

---

DaGWaR said:
Would this rom work on the att version
Click to expand...
Click to collapse
Yes, I'm on att and it works fine (except for the bugs)
---------- Post added at 02:19 AM ---------- Previous post was at 02:19 AM ----------
MiniBlu said:
Dirty flash should be OK if coming from previous cm version. But because off changes to google services I would recommend formatting "system" partition to make sure gapps is cleaned up properly. And always wipe dalvic and cache after installing rom and gapps.
Click to expand...
Click to collapse
OK thanks

---

Going and flash now hope the random reboots from slimrom not on it a bit tired of that
Sent from my desire 610 using XDA Free mobile app
---------- Post added at 04:27 AM ---------- Previous post was at 03:52 AM ----------
miniBlu u r a god amoung ppl with htc desire 610. if i change the screen density back to 200 would the icns show as small as slimrom did.

---

DaGWaR said:
Going and flash now hope the random reboots from slimrom not on it a bit tired of that
Sent from my desire 610 using XDA Free mobile app
---------- Post added at 04:27 AM ---------- Previous post was at 03:52 AM ----------
miniBlu u r a god amoung ppl with htc desire 610. if i change the screen density back to 200 would the icns show as small as slimrom did.
Click to expand...
Click to collapse
yes they will, but you may see some other problems with app compatibility. Slim rom uses screen driver from original at&t rom which I think is meant for 200 dpi. You can reduce icon size of default launcher by long pressing empty space on screen then pressing the 3 little dots above the widget icon. Then select "Grid size" COZY and "Larger icons" OFF. Or install a 3rd party launcher from play store, such as "Nova Launcher" which allows full control of icon sizes and grid layouts.

---

DaGWaR said:
Going and flash now hope the random reboots from slimrom not on it a bit tired of that
Sent from my desire 610 using XDA Free mobile app
---------- Post added at 04:27 AM ---------- Previous post was at 03:52 AM ----------
miniBlu u r a god amoung ppl with htc desire 610. if i change the screen density back to 200 would the icns show as small as slimrom did.
Click to expand...
Click to collapse
MiniBlu said:
yes they will, but you may see some other problems with app compatibility. Slim rom uses screen driver from original at&t rom which I think is meant for 200 dpi. You can reduce icon size of default launcher by long pressing empty space on screen then pressing the 3 little dots above the widget icon. Then select "Grid size" COZY and "Larger icons" OFF. Or install a 3rd party launcher from play store, such as "Nova Launcher" which allows full control of icon sizes and grid layouts.
Click to expand...
Click to collapse
I don't think it actually set at 200 even though it does show that in build prop. In aptoide there is a hardware stats option when I clicked with previous build I got the following, second image is most recent build from 8/12/15 which show first build at 213 and new build at 240
Also, battery seems to be better for me
Drain over night for 8hrs from 80% was only 11% drop is that OK or should I try full format and flash ??
Also, how do you check playstore wakelock thing?

---

Oh wow, no deep sleep at all here, I'm gonna try full flash later today unless anyone can shed some light on this thanks
Alot of apps seem to be checking for alarm Alot I don't have no alarms set though
If the device isn't going into a deep sleep then I'm guessing I can get battery use down a lot more

---

wo88les said:
I don't think it actually set at 200 even though it does show that in build prop. In aptoide there is a hardware stats option when I clicked with previous build I got the following, second image is most recent build from 8/12/15 which show first build at 213 and new build at 240
Also, battery seems to be better for me
Drain over night for 8hrs from 80% was only 11% drop is that OK or should I try full format and flash ??
Also, how do you check playstore wakelock thing?
Click to expand...
Click to collapse
about the screen you could be right. 213 is probably the lowest value the screen driver in the internatinal kernel version will accept and 240 was the default value in both international and US AT&T(I had to double check this 1 as I thought it ws 200) roms. But I did download kernel sources for both variants from htcdev and the main difference between them was the display drivers which agreed with there naming convention for the kernels. Build_number_a3ul_3.4.0.zip for US AT&T which has an FWVGA screen acording to both its specs and its build.prop. And Build_number_a3qhdul_3.4.0.zip for international which has a qhd screen in its specs as well as it build.prop. So it seems like all variants are probably best left at 240 DPI and we're just lucky that both work ok with kernel built for either variant.
About the battery drain. This was a well known fault with cm11, after a PlayServices update that came after cm11 stopped being activly developed and the method they had used to disable the SystemUpdateService started causing a wake lock that was preventing the phone from ever going into "deep sleep". I use "better battery stats to tes for these type off problems. In the old build it was showing a google services wake lock 100% of the time. and awake screen off % plus awake sceen on % always = 100%. Attached screen shots sho much improved results in the new version.