yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] rjand:
If you previously used CM11 then the same radio will do. If coming from stock you may need to update your radio to get GPS to work.

I don't think turning off animations is a good idea, from memory it caused some problems on CM11, possibly with the dialer, so most likely will do the same here, if not now then further down the line when more features are added / bugs fixed.
[Desire HD Android Development] KkdGab:
I know about that. But the thing is, I don't have permission [MENTION=3382363]Mustaavalkosta[/MENTION]
[Desire HD Android Development] Mustaavalkosta:
Pull requests work just fine for occasional commits. If it becomes more regular thing, we can talk about direct access then to ease the workflow. I like to retain some degree of control instead of making it completely free access to everyone even though any help is welcome. Without a code review system, which would be a bit overkill at this point, this is probably the best way.
[Desire HD Android Development] KkdGab:
OK, I see.
[Desire HD Android Development] jonny-boy:
For me the little arrows inside the wlan icon which show the activity status are not exact in the middle, but that's no big deal
[Desire HD Android Development] entony80:
Happy New Year
[Desire HD Android Development] Mustaavalkosta:
Nightlies started

Nightlies

I test ran my build script last night and now the first nightly build is out. First post and our website download mirror info are updated accordingly. These will be built 6 hours later than 11.0 nightlies for now. I'll probably drop 11.0 builds to weekly schedule soon and then 12.0 nightlies will take the regular 00:30 PDT schedule spot.

I'm not sure what's exactly going on with the previously announced codefi.re maintenance as there were some complications so nightlies may be suddenly disrupted if they take the server I'm using down for OS change and upgrades.

OTA updates

Our OTA server should be working now and build includes slightly modified version of CMUpdater which should allow you to get notification for new nightlies (and snapshots in the future) and download them directly. I'll be testing it as soon as the second nightly is out so this is still somewhat untested.

When I tested the whole process a while ago in test environment flashing from updater worked fine with TWRP 2.8.1.0. I don't know about other recoveries so results may vary. It should work with any recovery that works otherwise and has support for regular /cache/recovery/command commands.

Keep in mind though that, AFAIK, it doesn't do backup before flashing.

Bugs

I opened our bugzilla for bug entries but you will need to register to be able to make new bug entries. It'll be THE place for handling bugs for 12.0 builds so search there to see if your issue has been listed already and then fill in a bug report with steps-to-reproduce, logs, screenshots and so on if it's not already there. Bug tracking tool won't do miracles by itself, it just enables us to track them more efficiently and maybe also kill bugs more efficiently. For any of this to happen there needs to be good bug reports. "This doesn't work, fix it" still doesn't cut it.
[Desire HD Android Development] xdagee:
Wow first nightly is out. Thank you [MENTION=3382363]Mustaavalkosta[/MENTION] for keeping our device for the 3rd time running. You are a true legend & a role model every developer should look out to.

Feature Request

As you have made things clear about OTA updates and bugzilla. What if someone will like to see a feature? Do you permit for that?
[Desire HD Android Development] Mustaavalkosta:
If it complies with what upstream is offering or isn't depended on CM (probably meaning just kernel features), then sure. I still won't be implementing things that are not offered in official CM builds.
[Desire HD Android Development] xdagee:
I practically a kernel feature request
[Desire HD Android Development] marek287:
Superuser

For me superuser seems to be missing (cm-12-20150101-UNOFFICIAL-ace.zip)
[Desire HD Android Development] Mustaavalkosta:
It's just disabled by default. You can enable it from development settings.

https://github.com/CyanogenMod/android_vendor_cm/commit/4bcfc3137a7740284465f7af7fc3d819f2d0392d
[Desire HD Android Development] Mustaavalkosta:
So, OTA updater is not working yet. I'm not sure why as unit test for the server works flawlessly. Debugging in progress.
[Desire HD Android Development] Mustaavalkosta:
Can someone with 20150101 or 20150102 build installed check if your device gets 20150101 and/or 20150102 builds listed in About Phone > CyanogenMod updates? I fear Android's internal cache mechanism is making my testing very confusing. Issue seems to be somewhere in the apache's config files but I can't verify with 100% certainty if it's now working ok or not due to not being very familiar how this Volley API works.
[Desire HD Android Development] Torgadden:
Hi Mustaavalkosta,

First off thanks for bringing 5.0 to our devices.

Yes, I am seeing both builds on CyanogenMod updates screen.
[Desire HD Android Development] Mustaavalkosta:
Ok, great! I guess I somehow fixed it then after almost losing my mind when this didn't make any sense and opened a bottle of beer. I suppose one must conclude now that beer = solution as I'm not exactly sure what I did in the apache configs to make it work. :p Thanks for a quick response!
[Desire HD Android Development] marek287:
Updating

[MENTION=3382363]Mustaavalkosta[/MENTION] Is it good to update using this update feature? I have always made full wipe until now.
[Desire HD Android Development] Mustaavalkosta:
You can still do that even if you get notified when new build is available and use the updater to download the zip. I can't say that it's better or worse to dirty flash as the end result depends on various things. Just do whatever works for you. I've kept my changes that require root access to a minimum which in turn has made dirty flashing relatively safe previously. It's too early to say how ART changes things though.
[Desire HD Android Development] becks90:
Flashed first nightly after full whipe, and later dirty flashed second one using the OTA feature, everything worked fine, really enjoying this Rom.

Thanks Master :good:

PS: Had to look it up again, so: Developement options (for SU, etc) are enabled by repeatedly pressing the "Build-Number" button in Settings -> About Phone
[Desire HD Android Development] Torgadden:
Just a minor observation. Touching the screen when CyanogenMod updates is checking for new versions appears to kill the search. Could just be me though.
[Desire HD Android Development] Mustaavalkosta:
Yeah, touch event will cancel the dialog. One could argue whether it's a feature or not but that's how it has been working on official builds too as long as I can remember. :p
[Desire HD Android Development] rjand:
I've a problem with Bluetooth and media audio not being routed correctly when I try to use PowerAmp to output to some Bluetooth speakers I have. The audio continues to come from the phone speakers even though PowerAmp thinks it is routing correctly.
[Desire HD Android Development] Mustaavalkosta:
It'll be fixed tomorrow. audio_policy.conf was missing 48kHz output and a2dp was trying to output 48kHz audio stream thus failing at it. You can add that manually too and reboot if you want to fix it right away. Playing music works fine here now with my Jabra BT speaker.

https://github.com/OpenDesireProjec...mmit/af86110e90dd422fd42d9c5a18542c6ba845adc5
[Desire HD Android Development] rjand:
Mustaavalkosta you're more helpful than some off my friends, and a lot more helpful than some of my relatives.
[Desire HD Android Development] pat99:
At 3-4 different interval i had rebooted my device.

First boot: 45min

Second boot: 12min

Third n forth boot: 2min

Are those results are normal?

I've slightly tweaked the ROM by doing two things. First flashed [TWEAKS]NITRO_X™_SPARK EDITION V-2B5 and Secondly removed 21MB of unnecessary apps from System/apps n priv-app folder.

Also i'm getting around 359MB of free RAM. Which means ROM is in Beast Mode!
[Desire HD Android Development] Mustaavalkosta:
I haven't timed subsequent boots but seems about right. Today's build is taking ages to boot though due to kernel memory allocator change (SLAB->SLOB). Used to be around 35mins ROM only and now this is 1h 10mins already and counting... I guess claims that it's simpler thus better for system resources didn't exactly hold true.
[Desire HD Android Development] rjand:
Did it boot up okay? I want to hold of installing today's nightly in case it won't boot.
[Desire HD Android Development] xdagee:
WoW!!! over an hour and still counting ... I hope it doesn't look like it's ending in bootloop. Also what if we do an OTA update??? Is it gonna have an effect on it?

Maybe you should wait for Mustaavalkosta responses first before proceeding.
[Desire HD Android Development] Mustaavalkosta:
Yeah, it boots but just takes ~142% (35mins -> 1h 25mins) longer based on this single test with just ROM without gapps. :p

Yep, SLOB slows boot down in general when it comes to creating ART cache files. It's ok tomorrow though. I switched allocator to SLUB as it seems to work again. IIRC, there were some issues with it and GCC 4.8 in the past which made us to move to SLAB. SLUB has more recent changes from faux123's tuna kernel and first boot time is similar compared to SLAB.
[Desire HD Android Development] xdagee:
Oh okay, So does mean we will see SLUB in the next builds or you will stay with SLAB? I sure most of us here are more interested in quick bootup time and highly optimized ROM. Which I also believe is your main focus.
[Desire HD Android Development] rjand:
It took somewhere between 1hr 8 minutes and 1hr 16 minutes for first boot here on today's "nightly", with Gapps and 27 other apps installed. I had previously enabled the performance profile.

Thanks Mustaavalkosta for enabling options for setting max.. cpu frequency.
[Desire HD Android Development] jonny-boy:
For me the AudioFx APP has no effect while playing audio over the intern speakers. Is that a Rom issue or is it on the cyanogemod side? I am on the 0101 build
[Desire HD Android Development] RaVe-N:
Man I wish I had have read this before I flashed today's nightly... It's been going at least an hour already. The last thing flashed on this phone was a JB version of slim rom so I had to update the recovery as well... is there a way of telling if it's actually doing anything?? :-/

EDIT: At least 1:20 so far... still going... It does look like it's doing something coz the arrow slows down every now and then, and I haven't noticed the animation restarting...
[Desire HD Android Development] jonny-boy:
Delete
[Desire HD Android Development] Mustaavalkosta:
SLUB will be in use tomorrow and in the future unless something goes boom with it. I haven't noticed anything this far.

No idea, I haven't tried that yet. Probably something with our audio pieces though. I'll know more once I have official nightlies running on my other devices.

I'm quite sure it will boot but as mentioned it takes insanely long to (re)create ART cache. My 1h 25mins first boot test result was without any gapps so with gapps it will take even longer as the amount of APKs going through dex2oat increases.
[Desire HD Android Development] RaVe-N:
It did work - I think it was about 1:45... it's not exactly the most responsive, but it is an ooold phone so I guess that's expected. (I've lost my OneX so this is a fill in loaner phone until I buy something else...) Good to see it's still very much alive and kicking here though. :)
[Desire HD Android Development] Mustaavalkosta:
If I'm not experiencing placebo effect SLUB may make it a bit snappier tomorrow in addition to decreasing boot time back to "normal". :)
[Desire HD Android Development] pat99:
You're right, It doesn't work with Internal Speaker. I think it's of those features which gets enabled when you've headphone connected to your device, just like sense based roms.

Luckily i've got your back covered, only if you're interested. Flash Pon-3 v5-Lollipop, it's modified version of Viper4Android and sounds way better then any other sound engine on Lollipop exclusively. Just don't forget to remove AudioFX from System before flashing!

link: http://xdaforums.com/showthread.php?t=2530976
[Desire HD Android Development] Mustaavalkosta:
Now that nightlies are running DOGE preview builds will be removed in the coming days. If you have grown some sort of special bond with any of them and have started to call it "my precious" make sure you have it somewhere secret and safe.
[Desire HD Android Development] rjand:
Calculator still broke on 0105 nightly, working on 0102, broke on 0104, didn't test 0103.
[Desire HD Android Development] Mustaavalkosta:
Without knowing exactly why or what, it might be fixed tomorrow: https://github.com/CyanogenMod/andr...mmit/5bcfdcbfe4789f147cf6ebebe2786e1f077bd210
[Desire HD Android Development] rjand:
Calculator still not working on 0106 nightly. Logcat attached if it helps, please ignore if it is an upstream issue.
[Desire HD Android Development] Mustaavalkosta:
Ok. Yeah, it helps. I had logcat of the crash but I somehow lost it and haven't had time to get a new one yet but now I have one. :) It's also upstream issue as calculator is 100% CM but if I find time I'll take a look.

In other news for everyone, if you have found that OTA update check just keeps going and going without finishing, I think I found the root cause for it (it wasn't apache) and it should be fixed tomorrow.

https://github.com/OpenDesireProjec...mmit/4887384cd326257fbda363082a1a1ab93442be22
[Desire HD Android Development] rjand:
Fast charge isn't working when the phone is connected to a PC.

Wi-Fi doesn't seem to reconnect to configured networks when you enter their coverage zone - I need to manually reconnect. Will test this one further.

Can't believe how well this ROM is working for being this early in development. Great work as always Mustaavalkosta.
[Desire HD Android Development] comesefosseantani:
I''ve just flashed it! it's great thank you!

it took about 50 minutes for the first boot (with gapps pico).

I noticed that during the setup wizard when asked to enter my google account the email field was not visibile. If i blind-clicked in the white space the keyborad came up, but even entering the text nothing was visibile. Switching between portrait and landscape allowed me to see what I was typing, but just for a while, then blank again.
[Desire HD Android Development] pat99:
Have some lollipop

CM12 Nightlies are still in Alpha! But there's always a way around...

Press and Hold at the middle of white screen, which practically let's you select written text. By then you'll get to see what you've typed.
[Desire HD Android Development] xda-dhd:
Updated TWRP to 2.8.1.1

TWRP 2.8.1.1
[Desire HD Android Development] nhanvn1111:
Link error

Please check your link, it empty
[Desire HD Android Development] jazzfrequency:
hi Mustaavalkosta and thank you for keeping DHD alive with LP !!! you are awesome !!

I replaced calculator with apk from first release DOG4 and its working now.

In latest nightly i have an annoying sound from the speaker every time i have notification for call, sms etc, something like tik before the notification sound starts.

Is it something in audio_conf ?
[Desire HD Android Development] rjand:
Wi-Fi connecting okay today after a reboot. Yesterday Wi-Fi kept saying Authentication problem and clicking on the network name and then Connect without changing the password allowed it to connect. Using 0106 nightly since yesterday.
[Desire HD Android Development] xda-dhd:
Ready file TWRP

Is a link not to download, this news post.

Here link to thread

And

Ready file TWRP
[Desire HD Android Development] evronetwork:
Hi there remember me? (it's been a while since I got my OnePlus One).. trying to sell the DHD but still no good offer around :P

I'll try to update the phone to CM12 once it becames pretty much stable and try again, android 5.0 is suppose to be ligher and might help Desire to work more smoothly

..we will see, also it's fun to flash and I'm only flashing official roms in my 1+1(no microsd presend and that's not very good when full wipe ...everything)

P.S. I liked Mustaavalkosta work in the past, not gonna chance now :P
[Desire HD Android Development] paulb_nl:
From your logcat I found its crashing because drawable btn_zoomin.png is missing for hdpi. I put a comment on CM gerrit so they know about it. http://review.cyanogenmod.org/#/c/82504/
[Desire HD Android Development] Mustaavalkosta:
I threw in temporary workaround for it using xhdpi drawable: https://github.com/OpenDesireProjec...mmit/42cdc441b46ec571a712f72662c2b60d82ad5101

Thanks for locating the issue! :)
[Desire HD Android Development] xdagee:
My Takes On The Fourth Day Of My Testing of CM12 Nightlies

Credits Very Important ;)

First of all I will like to give credits to Mustaavalkosta and his entire team of bring Lollipop on our "never dying" device.

You guys rock :) [wait a minute why aren't we featured [CM12 for DHD/Inspire 4G] on the xda-news portal?]

Now on my main issue;

I know these are alpha builds, and we all can see that every effort has been made to get the best out of our device.

After testing every nightly till now, I have realised an issue which it seems no one is talking about it or even haven't noticed.

It's about dead touch capabilities or unresponsive touch.

This is the situation;

After flashing on first boot phone responses fine. After Gapps has been flashed and rebooted if you dont unlock before the network loads, you will notice this issue (touch becomes unresponsive) unless you remove the battery and restart it but it doesnt end there if you dont unlock before network loads, you will face the same issue again and again.

I thought the issue was only with gapps so i flashed without gapps, waited for some minutes, connect the wifi, did some little stuffs and restarted and baam same issue (touch wasn't responding).

I dont know how you are going responses to this; but i will get a logcat for this.

P.S I tested both with EXT4 and F2FS file systems.

for those who dont know about F2FS visit here
[Desire HD Android Development] Mustaavalkosta:
See if you can extract logcat and dmesg when it dies. I haven't noticed such issue but in case you have atmel panel it may have something to do with that.
[Desire HD Android Development] Mustaavalkosta:
A little over 200 backported kernel patches for memory management (+ misc) from kernel.org master branch coming to the next nightly among other things.

https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/commits/cm-12.0
[Desire HD Android Development] jazzfrequency:
Hi mustaa...

I have radio 12.65.60.29_26.14.04.28_M but i saw that you have some newest radio versions in codefi.re (radio-ace).

Should i flash a new radio version ? or it is ok with the current that i have?

Τhere are differences only with s-on,s-off that has to do with newest radios ?

Thanks !
[Desire HD Android Development] paulb_nl:
Nice work! You must have had little to no sleep pushing all those commits. :)
[Desire HD Android Development] Mustaavalkosta:
If it ain't broken, don't fix says the old proverb. If you don't have any issues with your current radio, no need to upgrade it unless you just want to try something new. :)

Haha, yeah. Let's just say the past few days have been a bit hectic and had they been paid workdays someone would have been put in jail. :p
[Desire HD Android Development] rjand:
Calculator working again on 0109 nightly.

Phone appears to be a lot snappier then previous builds. Dialler is a lot more responsive than KitKat dialler was - great work. Is this due to these kernel patches or the change in I/O scheduler from SIO to ROW?

ES Task Manager reporting an extra 13MB of available RAM, although in use I don't seem to have any extra free.

Improved dialler means no way am I going back to KitKat, plus Lollipop looks far better. Android just keeps getting nicer and nicer to use with each new release.

--- Edit ---

Problem with ringtones and alarms on this build. PS I dirty flashed from 0106 nightly where ringtones and alarms were working properly for me.
[Desire HD Android Development] rjand:
I have 2 logcats of audio issues with 0109 nightly.

The first logcat is me trying to play the Lyon.ogg ringtone using ES Media Player (part of ES File Explorer).

The second logcat is when I call my phone from another device, again I have set Lyon.ogg as my ringtone.

You will also notice lots of Exchange errors in these logs which I haven't removed the lines. I have an ActiveSync server set up with a Corporate account for my contacts and calendar - email doesn't work properly on it and I use K9-Mail for IMAP mail as it is a lot faster than the Android email client.

The other audio errors I found where that many of the alarm audio files either didn't play when choosing them from the alarm clock app, or they would be a group of 3 or 4 that sounded the same as each other instead of being unique.

--- Edit ---

Forgot to attach logcats
[Desire HD Android Development] Mustaavalkosta:
Thanks! I have probably derped while cleaning up HALs half asleep. :silly:
[Desire HD Android Development] rjand:
No worries. I went to the 0108 nightly and copied the Calculator.apk file over from the 0109 nightly to get the calculator working. I notice that ROW is also the default I/O scheduler on the 0108 nightly (previously SIO on 0106 and earlier). ROW scheduler makes the phone feel snappier than SIO - I would definitely anyone to either upgrade (but avoid 0109 nightly unless you don't care about ringtones and alarms), or change your scheduler in the earlier builds, 0106 to 0108, from SIO to ROW. It isn't possible to change the scheduler in earlier versions.
[Desire HD Android Development] Mustaavalkosta:
Yeah, I spent some time benchmarking readahead values and schedulers for nand and sdcard in pure throughput terms and got like +10MB/s higher reading from my Sandisk Class 10 sdcard in the end with larger readahead buffer and CFQ scheduler. For nand it wasn't that dramatic change but there were some noticeable differences. I didn't find a way to measure latencies though so no idea how the new settings affect those.

https://github.com/OpenDesireProjec...mmit/9c6851511f109e67c97539c970d28d888d85327b
[Desire HD Android Development] Mustaavalkosta:
[MENTION=4891658]rjand[/MENTION], can you check if your earlier build goes mad too when you change af.resampler.quality value from 255 to 4 in your /system/build.prop?

Edit: I switched it for myself and result was same kind of errors in logcat after that. So current workaround for today's nightly: remove that property from build.prop as paulb_nl suggests below. I'm testing other possible values now in case some of them work in addition to the default value which has been used before due to mismatching property value (255 doesn't exist in audio resampler code anymore).
[Desire HD Android Development] paulb_nl:
Can you try to remove af.resampler.quality=4 from build.prop? In your log it crashes right after setting the audio quality.
[Desire HD Android Development] xdagee:
logcat dead touch after reboot

Hi [MENTION=3382363]Mustaavalkosta[/MENTION], here is a logcat I was able to pull based on the issue reported earlier.

few things i noticed was:

touch is responsive when connect to PC through USB (though I didn't do for normal power but am sure it will be the same) and rebooted.
[Desire HD Android Development] Mustaavalkosta:
Did you manage to get dmesg also? That might be more useful in this case as the issue is likely with the kernel and it doesn't spew its errors into logcat. If you didn't, that's ok. Try to get it next time that happens.

adb pull /proc/kmsg

And wait 5-10 seconds to be sure it's all there and abort the process with ctrl + c.

adb shell su -c "dmesg" > dmesg.txt

or

adb shell su -c "dmesg > /sdcard/dmesg.txt"
[Desire HD Android Development] rjand:
Still errors in logcat, not sure if they are exactly the same as reading them on the phone, but audio still works on 0108 nightly with this set to 4.