yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] Chevyguy85:
Been running the Nov 18 nightly with the newest performance kernel and killjoy no problems so far

16+ hours of uptime according to phone so no random reboots. Left my phone on at work to test battery drain with airplane mode screen shot is the drain for that almost 6 hours at work. I don't use anything that requires more than 2 touches so no clue if I have the 4+ touch problem. Charging light went off as soon as I unplugged the phone last night. Cell signal/data seemed slow to come back after turning off airplane mode but it could just be my own impatience and not having used airplane mode much. Still needed to flash the torch fix to enable high brightness setting.

Good to see another collaboration on 4.4 hopefully in the coming weeks we'll have a couple different stable builds to choose from.
[Desire HD Android Development] s0ulreaver:
It says ATMEL_x0080_x0020
[Desire HD Android Development] demanzke:
+1, also no keyboard hangs so far, this one is a keeper.
[Desire HD Android Development] deckoff:
Any known bugs, I've seen none in the opening post. I use DHD official stripped ROM, but I need some of the 4+ functions badly.
[Desire HD Android Development] rjand:
The 4+ multi-touch if you need it, and a small delay when answering a call before you can talk seem to be the main bugs, the second one is easy to work around, the first doesn't affect most people. Apart from these the last two nightlies (11/16 and 11/18) are both very stable.

Does anyone know what the Media Service is? I charged my phone to 100% last night, quit all apps (long pressed home button and then pressed the close all button), used Greenify to hibernate any other apps, and then used Advanced Task Killer to kill most of what was left, but Media Service used almost all the battery overnight. I don't normally bother trying to kill all apps like this, but I needed the phone this morning with a good charge. Usually it only discharges about 1% overnight (when airplane mode is on).
[Desire HD Android Development] Mustaavalkosta:
It could be some unexpected side effect from MediaProvider changes but I can't say anything for sure because I couldn't find anything with "Media Service" from the source, or something going mad after task killer. I suppose a regular reboot is more recommended to "clean up" the running apps and services than using task killers and of course try not to have apps that don't behave well on your device. :)

Did it say Media Service in android's native battery UI or some 3rd party app? I'm just looking for some more clues to track down the app/service behind that label.
[Desire HD Android Development] Chevyguy85:
I had that problem as well. It was in the native battery usage app/screen thingie. Mine showed something like 70% to MediaProvider and screen being only 10%. Unfortunately I don't remember which nightly I was running that the time. Haven't seen it pop up since then though.
[Desire HD Android Development] Mustaavalkosta:
Yeah, MediaProvider / android.process.media has a long post on some Google bug tracker how it has been eating away people's batteries. I'm not saying that this behavior is "normal" but it has a history of doing that.

That being said, when it comes to my priority tweaks, in theory, I suppose it's possible that due to the lower process priority the scanning process keeps the device awake longer than with stock priority but I'm a bit doubtful that it would alone really extend, let's say, scan time of 1-3 minutes to several hours which in turn would cause the battery to empty. But then again I don't have anything that would state that it can't do that.

Sometimes I just hate the quote in my signature... :p

If it seems that this has been starting to occur only after MediaProvider priority changes (on or after 20131027 nightly), I guess I must revert those changes but the data doesn't really point to any certain direction at the moment. :(
[Desire HD Android Development] Chevyguy85:
So far so good on the Nov 18th nightly

Sent from my too hard to implement ICS Inspire 4G on 4.2.2
[Desire HD Android Development] rjand:
I'm on the 11/16 nightly, and its only happened the one time so far on this nightly. It has happened on other nightlies, even other ROM's going back months. Although it is very random, it is very annoying when it does happen.
[Desire HD Android Development] Z_0r10n1S:
That wakelock happens from me from cfX jb4.1 or before. Now I run 1116 nightly with last perf kernel and I think that is low, but at the time I did full procedure to eliminate MediaService WL, I found a post with fix and instructions to make it work but I forgot where :(

After that the problem was solved and now the percentage of that WL is come back to normality. I'll provide a screenshot of better battery stats after recharging my phone.

Anyway the fix consists in freeze all process which about media (such gallery, media provider, and so on), clean data and caches of those applications, clean the db database files from both memories and things like that.
[Desire HD Android Development] Mustaavalkosta:
Ok, thanks for the additional info. Good to know this issue isn't linked with priority changes so they can stay. :)
[Desire HD Android Development] demanzke:
never happened to me, I'm using 4.4.0.34403 on a daily basis.
[Desire HD Android Development] damac:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series

Yep, with previous versions, I ended up doing a restart about every 12 hours. Not needed now :)

Thanks!
[Desire HD Android Development] jsethi3:
I had the same issue. I immediately took did the restart, force restart infact (took out the battery), and then the restore picked up and went fine. But I also enabled the flag in the security - allow apps from unkown sources. All was fine after that. I had to, though, restore the apps which failed - manually.
[Desire HD Android Development] vincentt84:
i have a huge battery drain on my voice calls, even much more than my screen backlight, and sometime a call will terminated with no reason, i love this rom and i wish to fix this problem, can any1 give me a help? thanks

by the way, i did a full wipe and repartition my sd card in 1024ext4, so i m sure this is a clean install.

and i attached a screenshot for you guys, thanks again
[Desire HD Android Development] damac:
That screenshot shows that calls have used more battery than screen but nothing about times, but then if you've made many calls, the screen would've been off during those times and battery consumption by calls would be higher.

Anyway, what's signal strength like where you're calling from/receiving calls mostly? If the signal for HSDPA/3G/Edge is lower than 2G, try switching to 2G for a day or two to see if this gets better. Also, (like iphone), you might be holding the phone wrong :) Try to keep the sim/microsd card cover somewhat free of obstructions when you talk. The antenna contacts could be weak as well. Or, a different radio might help. Sorry if I'm not being very helpful, too many variables!
[Desire HD Android Development] rjand:
Is there an option like in CodefireX 4.2 to allow any widget on the lockscreen? I'm trying to a Poweramp widget to the lockscreen.
[Desire HD Android Development] damac:
I think you can just drag left/right the lockscreen and an empty screen appears with '+' on it. Click on that and it allows you to add a widget. Is that what you were after?

edit... just checked, only some types of widgets can be put on the lockscreen. Perhaps they need to be specifically lockscreen widgets?
[Desire HD Android Development] rjand:
Yes, but there is only 10 widgets to choose from, Google+, Chronus, Calendar, Digital Clock, gReader, Torch, etc. but not the wants I would like. In CodefireX you can enable Allow any widget, then any of your widgets on the phone can be added to your lockscreen.
[Desire HD Android Development] qazsxdcfv:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series

Naaa , its a custom settings mods .. , smali editing i think ..

------

And wow , M1 great .. But i dont like slow update & i dont like to download it all days too .. Haahaha:cool::D

Sent from my hTC Desire HD powered CyanogenMod 10.1 by Mustaavalkosta™
[Desire HD Android Development] vincentt84:
i have only 4 call on today, and in my previous rom my battery can last at least 12 hours, so i think this is a weird issue for me, anyway i try to flash M1 version to see how the result, and thanks for your reply, :)
[Desire HD Android Development] Uli321:
Regarding transfer of phonebook to car I was a bit inacurate, indeed the phonebook in the car is empty, however there is no error message or something like this.

Uli
[Desire HD Android Development] adam5150:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series

Has the chronus update set for next update.
[Desire HD Android Development] Mustaavalkosta:
It should be already in the most recent build.
[Desire HD Android Development] st0nedpenguin:
Hopefully the Chronus changes mean I won't have to enable wifi location every boot just to kickstart the weather updates.
[Desire HD Android Development] qazsxdcfv:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series

25/01 builded ? .. I'm at school , so I'm late about the news , gonna check it soon ..

Sent from my hTC Desire HD powered CyanogenMod 10.1 by Mustaavalkosta™
[Desire HD Android Development] a user:
is it just me or doesn't the led blink anymore upon receiving mails?
[Desire HD Android Development] ai6908:
It blinks for me in 0120 version...which version are you in?
[Desire HD Android Development] a user:
the newest 25th
[Desire HD Android Development] mcduffie2010:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies / M-Series

GPS is also giving problems. Can't get a satellite lock in 25
[Desire HD Android Development] ai6908:
I was going to flash the 0125 version....i guess i will wait...;)
[Desire HD Android Development] Mustaavalkosta:
I haven't touched anything for a few days as I've been busy with other stuff. I can't remember reading anything LED related in CM changelogs either.

Same goes for this.
[Desire HD Android Development] maxexcloo:
Are there any plans to put out builds based on the recently announced release candidates? It would be awesome if this version of your excellent port could have a finalized stable release :)
[Desire HD Android Development] Mustaavalkosta:
I'll do SR3 at some point which will be based on 10.1.3 and have the small ace specific changes that I've done since SR2.

ps. This is not a port per se, source built stuff. ;)
[Desire HD Android Development] humano:
Hey, thanks man. :)

I am waiting for that SR3 until you release the new roms with kitkat.... Thanks :)
[Desire HD Android Development] alpha007org:
Mustaavalkosta: I am using your ROM (older version) for a couple of months now (about 4 -5 ). In the meantime I was occasionally checking this thread about new releases and what king of bugs has it and how to get around them.

I remember reading about Torch Fix for latest release.

I assume there are more flashable fixes available and I am wondering why don't you post them on the first page?

---

If anyone would point me to the most common fixes I would very appreciate it...
[Desire HD Android Development] Mustaavalkosta:
There are already CM11 builds out there but maybe you meant you are waiting for something more polished to come out. :)

I only have torch fix which is flashable. You can get it from here: http://downloads.codefi.re/mustaavalkosta/cm-10-1-unofficial-ace/tests/torch_fix-signed.zip

In addition one can change hw backlight behavior with another zip but those who want to change it are probably aware of the directory, or can find it with ease, which holds the patch zips so I don't have to separately advertise them.

I'll probably include that Torch fix in the SR3 too because the 10.1 branches are practically in frozen state so tracking Torch locally to fix the issue doesn't require additional maintenance in the future.
[Desire HD Android Development] alpha007org:
What about performance kernel?

Is Perf. kernel written for CM? Or is it applicable on most ROMs?

Why is it called Performance kernel? Are Clocks higher? Other tweaks present?

Where can I get latest release?
[Desire HD Android Development] Mustaavalkosta:
Only PLL2 bus clocks are higher and it won't run on every device including mine so I don't give any support for it since testing is not possible. Some people asked for it after I forked synergye's KangBang kernel so I provided it. Everything is versioned with simple date format (YYYYMMDD) so it should be easy to figure out the latest release on either ROM or kernel. Everything related to this ROM can be found in the general cm-10-1-unofficial-ace directory on both hosting sites.

Perf kernel should run like every other standalone kernel but like I said earlier I don’t support it so I don't know whether it runs on some other ROM or not.
[Desire HD Android Development] evronetwork:
Although O/C PLL2 bus clocks should provide more performance, to be honest in daily life I can't tell the difference. So if you give me an ACE phone to make a call with standar kernel and an ACE phone with perf kernel I won't find which is which :P
[Desire HD Android Development] Mustaavalkosta:
SR3

Download: [codefi.re][goo.im]

Buttonlight patch: [codefi.re][goo.im]

Manifest: [github]

Changelog:

- Updated liblight from Evervolv msm7x30-common repo to fix charging LED issues.

- Torch high brightness patch is now integrated

- MediaProvider has lower priority for media scanning process so it won't choke the CPU.

Still based on 10.1.3 so no changes from upstream.

Goo.im links coming as soon as the files show up on the website.
[Desire HD Android Development] Steam.:
Thanks for the new release.Codefire is unusually slow though.Varies from 18 mins left upto 1 hour, speed isn't constant at all..
[Desire HD Android Development] evronetwork:
So new rom in CM11 and in CM10.1 ..nice! so I can play with CM11 but still have a stable CM10.1 SR3, what more can I ask? thanks man

downloading at 750-850kb/s currently so I can't say it's blazing fast but it's not slow in any way
[Desire HD Android Development] Steam.:
Yeah I usually download from codefire at my full speed(2.0mb) but this time it was slow.I DL'd it about 10 mins ago, gonna flash it now.
[Desire HD Android Development] humano:
Great Musta.

Thanks!

PS: What gapps pack should we install with this new release?
[Desire HD Android Development] Steam.:
It's the same OS version, so same gapps.I keep using banks's gapps, the core ones that are less than 20mb.They work with no problems.
[Desire HD Android Development] ThunderDesire:
Great Job Musta....

I am unable to download ROM on my phone using any of the links (i.e. goo.im & codefi.re)...

If anybody know the reason please let me know...

Thanks Musta for keeping our old phone on steroid...
[Desire HD Android Development] evronetwork:
something below 500kb/s is slow, anything higher is acceptable for sizes up to 200mb, ok I'd prefer if it could reach my dl limit but we don't live in an ideal world. If we live in an ideal world HTC would see how many people signed the petition for our DHD and continue the support of our phone and just give us KitKat with sense(for people who want that) and devs here could just strip sense and we will be happy ..but that's not the case.

Use banks, whatever suits you more. Standard version is for everybody and core version(just google play) is for people who don't want all the google's crap. I personally prefer core and using it with the SR3

I can confirm that, I'm using SR3(clean flash) with banks gapps core, no issue what so ever. I might be wrong but I think core was about ~8mb(I'm lazy to check it out and confirm hahhahah I helped a dude so it's 8.75MB confirmed, so I was remembering well about it's size vs 26.56MB for standard) so it's way less than 20 :P
[Desire HD Android Development] bestfil:
Maybe U don't remember, but I tried to find out why I can't O/C CPU in my DHD. I almost believed that my chip is from the worst part of wafer or sth like that. Thus I thought I couldn't tweak over 1,2 GHz... Any attempt failed with CPU freeze (halt).

I tried CM10.1, CM10, CM9, AOSP, AOKP, Revolution HD and nothing.

Then I finally flashed stable CM 7.2 and... WOW I can tweak over 1,2 GHz, up to 1,5 (max available value in CM7.2, I haven't tried if there is possibility to change any settings to make CPU faster).

Is it possible by the great developer, as You Mustaavalkosta are, to find out what settings where changed wrongly while making newer versions of CM.

I think that someone made on simple mistake and the rest of developers copy-pasted this settings without knowing that it will affect a small amount of DHDs...

Any way - thanks for the great ROM as YOUR CM.10.1 build is, but I can't work on it because I can't use your "power" kernels, and I can't tweak to the desired 1,4~1,5 frequency which could give the smoothest and the most stable edition for all, not only for 95% of the community.

---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------

Maybe U don't remember, but I tried to find out why I can't O/C CPU in my DHD. I almost believed that my chip is from the worst part of wafer or sth like that. Thus I thought I couldn't tweak over 1,2 GHz... Any attempt failed with CPU freeze (halt).

I tried CM10.1, CM10, CM9, AOSP, AOKP, Revolution HD and nothing.

Then I finally flashed stable CM 7.2 and... WOW I can tweak over 1,2 GHz, up to 1,5 (max available value in CM7.2, I haven't tried if there is possibility to change any settings to make CPU faster).

Is it possible by the great developer, as You Mustaavalkosta are, to find out what settings where changed wrongly while making newer versions of CM.

I think that someone made on simple mistake and the rest of developers copy-pasted this settings without knowing that it will affect a small amount of DHDs...

Any way - thanks for the great ROM as YOUR CM.10.1 build is, but I can't work on it because I can't use your "power" kernels, and I can't tweak to the desired 1,4~1,5 frequency which could give the smoothest and the most stable edition for all, not only for 95% of the community.
[Desire HD Android Development] cyb3r.pr3dat0r:
is your voltage low when you do OC ? use aokp's performance control and make sure volate is around 1200-1500
[Desire HD Android Development] elguneid:
is it stable ?? and what about battary any battary tweak here ??
[Desire HD Android Development] evronetwork:
My phone goes to 1.86GHz easily(default voltage), I didn't try it further but in that frequency the battery don't last very much. Maybe my phone is better as I bought it on Jan 2012 so probably it's not one of the first DHD's.

P.S. This rom is one of the most stable/good performance roms I ever know for my phone, maybe the best. Virtually as best as a good company can do it(apart from the 4 point multitouch bug - it's not important anyway), so I'll recommend to stay on topic rather than O/Cing ..that area is far from here ;)

P.S.2 Something irrelevant to the topic but important for the O/C in our phones, if you dig around you'll find that the max frequency that this chip can go is 1.2GHz <-- thats what a company would use if they want to get a bit more performance, so if you search about our cpu(I've done that in the past) the max frequency that is "safe" is 1.2GHz ..for those who didn't do their homework :p
[Desire HD Android Development] mehrshadkh:
It most be a joke?! This rom always was and always would be the best rom for my phone! I never needed overclock for smoothness cause it is realy smooth. I remember I have overclocked cm 7.2 Oxygen rom to 1.9 GHZ And after that I never feel that I need my phone to be overclocked. With this rom I have everything that I need from my old phone! I feel that you dont know how to overclock! But as I remeber this rom can be overclocked to 1.7 or more! But it is not necessery realy! And you need apps to overclock roms. It is not included in roms.
[Desire HD Android Development] AtomosVE:
Stable ROM but media provider hogs cpu a lot

Media provider hogs cpu a lot so cpu clock stayed highest. = drain.

Except this, very stable as daily driver Thank you for great effort to port CM10.1 to desire hd.
[Desire HD Android Development] evronetwork:
Actually CM has overclocking features, you just need where to enable them

Go to the device info and tap 5-7 times(I don't remember how much it's needed), you'll unlock some tools, there you can change the frequency and much more (change to SIO, BFQ, CFQ, SmartAssv2 etc).

From what I understand the guy was trying to O/C he's phone and when he did, the phone couldn't work stable enough, so probably he has a low quality cpu(which barely pass the QC point). I might be wrong but that what I got from his writting.

So if he has a low quality cpu, he'll never reach 1.9GHz even if he double the voltage(..that would be overkill btw and probably will cause the cpu to burn). If he manages to raise the voltage to the maximum permitted level and keep the chip cool he might have a change to reach way more frequency that 1GHz(stock) but IMHO it's not worth the risk ..if you wanna O/C, just make it work at 1.2 or 1.3GHz and you'll be fine, after all 20-30% extra frequency is more than enough but DON'T expect 20-30% extra performance, it doesn't work that way.

Source: A humble overclocker(PC)
[Desire HD Android Development] mehrshadkh:
thnx. 7 times On device info! I just feel that he didnt find the setting as he mentiond! And as I said I never felt that I need my phone to be overclocked with this rom It is smooth enough and I prefer to save more battery!
[Desire HD Android Development] Mustaavalkosta:
Any chance you could try to find out which triggers MediaProvider staying on long enough that it actually increases battery consumption? Also more exact times of how long it stays active could help. I haven't been able to make MediaProvider to stay active so long that it would have made any difference. I've kept the phone idling on the desk for days without a recharge so there must be some sort of trigger for this behavior.
[Desire HD Android Development] evronetwork:
If I had a dual cpu running at 2.3GHz or a quad core at 2.3GHz you can be sure I'd U/C(underclock) it to 1.6-2GHz or less if the battery was less than 3.000mAh, it won't impact performance much but the battery savings would be huge(also if you undervolt it due to less frequency you'll gain even more battery savings)

You'll get more performance from a better architecture rather than higher frequency, what if you O/C your phone to 2GHz? you'll have a bit better performance but the battery would be so much worse and with 2GHz you won't able to compete against dual core at 1.6GHz or more

..you might in some apps that use a single core but still this depends on how well the app is optimized for your cpu.

I'd be happy with a quad at 1.6GHz and 2GB of ram(yes ram is low in our phones, so any optimizations in ram would help us out. So 4.4 when it'll be stable it will be a huge improvement, then we just need a 3.4 kernel which has even more ram optimizations)

Anyway, we're getting off topic.. I'm already a bit much off, so I'll stop here :good: