yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] evronetwork:
Probably kernel issue as I'm having hot reboots as well :-}

EDIT: I revert to the previous performance kernel and the issues of hot reboot stopped, so something is wrong with the latest performance kernel ;)

EDIT2: Well I found the worsed glitch ever, so don't flash 27/10 rom(clean flash) then dirty flash 29/10 then flash 29/10 performance kernel and again flash the previous performance kernel or you might end up like me EVERYTHING work but the screen when they call you or you're calling. I wanted to call someone and then change my mind hehe "screen-touch" is dead&soft keys do nothing other than vibrate yeahhhhh then functioning just fine after the other is ending the call(because you can't). If they call you you can't answer then or cancel them ..just nnnnnnnnnnnnice | I reflash(dirty flash) the 29/10 rom and this bug is eliminated, hopefully it won't introduce some other bug :P
[Desire HD Android Development] deaddead:
Love it, thank you :)
[Desire HD Android Development] sashank:
Strange. After reading the multiple reports of freezing and random reboots with Oct 29 nightly + Oct 29 perf kernel, I was fully expecting to see the same. But my phone has been running much smoother and faster than it has recently. No black screen + freezes on wake-up yet, no keyboard freeze (AOSP keyboard, haven't tried with SwiftKey yet), no application crashes (except one persistent 'process system has stopped working' on the lockscreen on wake-up, which required a reboot). I'm actually experiencing less lag compared to before with similar numbers of apps running and absolutely none of the above mentioned issues. Opening settings menu also seems more snappy. I've used it for half a day with this combo, so I'll use it for a day or two more and report on the performance. Point to note, I'm running perf kernel - smartassv2 - 245/1516 MHz - fiops scheduler. Also under memory management, I have zRAM disabled and asset purging and KSM checked.
[Desire HD Android Development] demanzke:
I am actually experiencing the same except for a couple keyboard hangs here and there, 27 and 29 are running solid and very smooth in comparison. I had a reboot every couple days before with different CPU settings and nothing changed in that regard. one thing I noticed though was higher idle consumption in 29, it was decent in 27.

edit: started getting browser hangs now, on big/ memory hungry pages
[Desire HD Android Development] R0yke:
Works great Thank you...

Thank you,

works like a charm...

:good::good::highfive::highfive:
[Desire HD Android Development] vliegnerd:
Anyone in the Netherlands that has recieved the Cellbroadcast "NL-Alert" last monday using this ROM? It's supposed to be supported in CM10.1, but I haven't recieved the test message (nov 4, 12:00). Cell broadcast is enabled. (Using a nightly)
[Desire HD Android Development] Chevyguy85:
Well looks like battery life is back to normal for me. Flashed 10/29 again the other day. Also running greenify and killjoy script. Also have had only 1 random reboot that I know of.

Left my phone on while at work last night and came back to find I had no data access. Changed from 2g mode to 2g/3g mode, airplane on/off, and cycled data connection. Only thing that worked was a restart.

Not using the performance kernel currently.

Sent from my too hard to implement ICS Inspire 4G on 4.2.2
[Desire HD Android Development] ultimate-tester:
Nope, I didn't receive any message. No clue if there actually was a message broadcasted that day haha.

Aren't you supposed to enable additional features to receive those test messages?

I just enabled every option there is in the option menu of broadcast messages and let's hope the next test message will be received.
[Desire HD Android Development] GeigerS:
gapps-jb-20130812 missing?

I am not finding gapps-jb-20130812-signed.zip on goo.im. Am I just missing something or is it gone?
[Desire HD Android Development] pauleversham:
Use this mirror http://d-h.st/PBY . :D
[Desire HD Android Development] Z_0r10n1S:
I'm running 1029 nigthly with 0916 perf kernel and works very well. Only one black screen issue (had to reboot) in about 3/4 days. Battery drain becomes normal now for me too. 1day and half or 2 with moderate use with 2g even on. :thumbup:
[Desire HD Android Development] addy75:
The version from 20131007 was the last "good" working one.

20131014 had a lot of freezes, reboots, "bad" battery durance and a lot of keyboard laggs, freezes and "restarts"

20131027 had less problems than 20131014. Keyboard was still buggy

The last version 20131029 was even better with less problems. Battery usage was ok, power indication still buggy (jumps about 10% in 2minutes), 20131014 was better. Keyboard is still laggy. Sometimes swipe is very slow.

I'm looking forward to get the next, better version :)

4.4 i'm waiting :D
[Desire HD Android Development] KalZakath:
Hey Musta, any progress in working on qcom/display? Maybe backporting is not very bad idea if there is nobody who could help in getting new codbase working on dhd/inspire 4g. I really like your work and i'm thinking that your cm 10.1 is best driver for my dhd, so i am looking forward to see your clean cm 11 nightlies:)
[Desire HD Android Development] Z_0r10n1S:
Cm11 alpha released for HTC Incredible S that runs the same hardware. Relevant issues are still camera and gps.

Mustavaalkosta, do you think are able to upgrade? ;)
[Desire HD Android Development] Mustaavalkosta:
Thanks. There are plenty of these errors:

W/Adreno200-ES20(12103): <qgl2DrvAPI_glBufferSubData:778>: GL_INVALID_VALUE
D/OpenGLRenderer(12103): GL error from OpenGLRenderer: 0x501
E/OpenGLRenderer(12103): GL_INVALID_VALUE

I can't remember seeing those before. Maybe something worth investigating at some point.

Yeah, I was browsing Evervolv repos late last night before passing out. A few weeks back I managed to make 10.2 to boot with their display stuff but due the difference/incompatibility with kernel side things, video was very laggy. When I have the next big enough hole in my calendar to tackle this rather messy and time-consuming process to make everything play nice together again, I'll see if I can make something good enough for public release from Evervolv's pre-existing work instead of trying to make our 10.1 repos work which seems to take too much time that I don't have. I'm very keen on seeing how ace performs with Kitkat.
[Desire HD Android Development] En Kee:
Transparent Status Bar

Hi guys!

I've made the status bar 100% transparent for the last build (cm-10.1-20131029-UNOFFICIAL-ace.zip)

Be aware that it's NOT a flashable zip, you have to put the files yourself

android.policy.jar in framework

SystemUi.apk in system/app

Don't forget to set permissions.

Link : https://drive.google.com/file/d/0B3gq5MEdUYxiVGtyWmxwYUNrYlE/edit?usp=sharing

Preview :
[Desire HD Android Development] alaci:
Woohoo! Fantastic! Thanks! :)
[Desire HD Android Development] Z_0r10n1S:
When screen is unlocked works well but with lockscreen it doesn't.

Screenshot:
[Desire HD Android Development] evronetwork:
Can anyone test the latest nightly version if the answer-a-call-bug-one-second-delay exist?

Thanks
[Desire HD Android Development] En Kee:
It's because the lockscreen isn't fully transparent. You can change that in

System settings

Lock screen

Background

Color fill

Put alpha to transparent.

Done ;)

Envoyé depuis mon Nexus 7 avec Tapatalk 4
[Desire HD Android Development] Z_0r10n1S:
Yes it exists as usual for me.
[Desire HD Android Development] Ribeard:
Would this work for, say, another CM based Rom or am I likely to **** up the Rom I have now if I try and push this?
[Desire HD Android Development] En Kee:
I don't know for other based CM roms. Make a backup then try. ;)
[Desire HD Android Development] Seentol:
Love it ROM, but sometimes my DHD is freezing, i've black screen (10% light) and just keep off the battery help me. Some ideas?

2.00.0029

Unlocked

S-ON
[Desire HD Android Development] evronetwork:
Try to make a clean flash and see if the problem persist

Damn, the charging led is fixed quite some time but this bug really annoys me, I need to either wait 1-2 seconds or answer twice
[Desire HD Android Development] evronetwork:
Any news about CyanogenMOD 10.2 or even better CM 11?

It suppose to be able to run out of 512mb ram so out phones should benifit from the low fooprint of this, so it's not just a name versioning

P.S. Hopefully the answer-bug would be gone too :p
[Desire HD Android Development] serzenus:
is call log limited to 500 entries ?
[Desire HD Android Development] Mustaavalkosta:
I just started putting pieces together for CM11 but as randomblame said sometime ago: don't expect it to be stable anytime soon. And I'll even one-up that: I'll be happy if I can achieve anything worth making public so

keep your expectations at bay

. I'm just giving these updates to keep everyone up-to-date about the state of any

possible

new release. :)

I'm also still not able to use new codefi.re servers due some after-migration issues so unless I get that situation resolved soon too I may lose my access to good build machine next month when the old server is scheduled for decommission. The time difference between me and server admin together with my normal sleep rhythm these days make things a bit difficult to sort out.

Edit: Nevermind, I just caught the admin online and it's ok. There was some misunderstanding on my part.

Unrelated question for everyone using nightly builds: What's the majority opinion about the MediaProvider change? Has it mitigated the lag issues after taking pictures or not? Have all the

new

stability issues with the latest nightly build been resolved with older kernel?

I'm interested to know if MediaProvider change gives me a reason to do SR3.
[Desire HD Android Development] rjand:
I reckon if you get anything to a near public state it will be pretty good.

Haven't noticed a big difference personally about the lag with the camera, I think it is a bit better, but nothing done to actually test the difference, could be just placebo effect.

Latest nightly definitely stable for me with the previous performance kernel, only occasional glitch is with the latest Twitter, but I think it is Twitter itself - could be because I haven't disabled the pictures showing in the feed.
[Desire HD Android Development] Z_0r10n1S:
[MENTION=5129269]mustav[/MENTION]aalkosta: I'm on last nightly with 0916 perf. Indeed it is better for me than last nightly kernel, black screen issue has gone, but I have some spontaneous reboot, 2/3 in the last week. But they are not so bad then pulling out the battery so... By the way the ROM is very stable for my daily use, so thank you again! About media provider I can't help you because I use very rarely camera.
[Desire HD Android Development] Mustaavalkosta:
I made a new nightly build (20131116) with reverted LK patches so people can test the default kernel too if they have been having new issues with the 20131029 build. I also made a matching perf kernel but it should be essentially the same as 20130916. Everything should be available at both hosting sites.

CM11 is now approximately at the same stage I got with 10.2 before. It's a good start but there's still a lot to do.
[Desire HD Android Development] Z_0r10n1S:
You are great Dev! Thank you! I'll try soon.

Downloading :thumbup:
[Desire HD Android Development] evronetwork:
I don't expect to get 4.4 stable anytime soon but it will be good for performance and efficiency ..the kitkat should help phones like ours who don't have 2GB or ram or more :p (it's suppose to work with 512mb or ram, but probably to help those Chinese phones/tablets that stuck with 2.3.x android and have 512mb of ram ..there are so many out there)

As long as I can call/text and receive calls/texts but also have ringtones in calls and text I don't mind using experimental roms but that's just me heh

Oh I see a new nightly ..let's test it! :D
[Desire HD Android Development] AtomosVE:
Multitouch more than 3 causes problem

It's Kernel Issue. checked with today's nightly:1116.

Multi-touch more than 3 messes touch at all. one of touchpoints points last touch for x and 0(top) for y.

Mine using synaptics touchscreen.

I think Sweep2wake or doubletap2wake, etc. patch caused the problem.

I've noticed same in Sense Kernels (on Sense ROM;) ) supports those.
[Desire HD Android Development] Z_0r10n1S:
I update now. Format system/dirty flash/wipe caches for me. Didn't install gapps which were yet present and updated.

That kernel issue is very annoying. Should I turn off s2w that I use, as workaround? Or have I go back to previous kernel?

I run synaptics.
[Desire HD Android Development] AtomosVE:
Nope: I'm already turned that off. Still same.
[Desire HD Android Development] Z_0r10n1S:
So previous perf kernel 0916 or maybe with new perf kernel which from words of mustavaalkosta is similar with that?

Edit: how can I reproduce issue? Tried it but seems safe.

BTW downloaded new perf kernel and ready to try.
[Desire HD Android Development] evronetwork:
guys I'm fine, I dirty flash it and I'm using Sweep2wake ..no problems at all until now :fingers-crossed:

(I had issues with the perf kernel but I didn't flash perf kernel this time)

EDIT: I really really hate the answer-delay-bug :(
[Desire HD Android Development] Z_0r10n1S:
It seems me too. Using s2w. For now all runs fast and smooth. :thumbup:

Edit: Transparent status bar patch works well with last nightly. :thumbup:
[Desire HD Android Development] rjand:
Latest performance kernel and nightly ROM working great Mustaavalkosta. Great work again.

If you haven't much dev time I'm happy for you leave this ROM as it is as it is near perfect already and use whatever time you can spare us on KitKat - please don't read that as me telling you how to spend your time by the way.
[Desire HD Android Development] humano:
Hey guys,

Could somebody answer a newbie question?

How do you restore your smartphone after changing the rom?

Do you use Titanium Backup or use other tool?

I just need to keep my contact list (agenda), all the whatsup stuff and the advances in Real Racing 3.

Thanks in advance
[Desire HD Android Development] chrisb906:
Go to recovery.
[Desire HD Android Development] gogsy1975:
+1... working perfectly... :good:
[Desire HD Android Development] Mustaavalkosta:
No worries, this ROM will only receive minor tweaks at this point that don't take much time. Upstream development is pretty much over and I don't know what to do about the remaining major bugs like audio delay on calls and I don't have enough time to figure them out by trial & error.
[Desire HD Android Development] Simonekl:
And will or dont will SR3 kitkat?

Thanks
[Desire HD Android Development] AtomosVE:
to reproduce this: touch 4 pooints and move your fingers (maintain 4 points).

you can see wrong buttons got pressed, Icons are moving erratically. etc.

WARNING: even your phone can hot reboot.

Can I download non-default(bundled with in) kernel?
[Desire HD Android Development] evronetwork:
Just re-flash the rom and you'll have the original rom that came with the rom(nothing else will change)

I'll try to reproduce what you are saying (if I got right what you mean that is :P)

EDIT: I did install multitouch test app and tried three points ..works perfectly, when I touch a forth.. program crashed ..after flickering. Did it three times, now I'm just having a black screen(no response whatsoever, it came alive after a few minutes.. and the app is closed :p)

So indeed there a bug well done finding it :good:

EDIT2: In the latest nighly the led-charging-bug came back :( so when you remove the microusb cable after fully charged the led stays lit for a few minutes

If you eliminate again the led-charging-bug, the audio answer delay and this new multiple touch bug we'll have the most stable 4.2.2 rom ever, I dare to say that it would be more stable than the original rom from htc :D (you should apply as a software developer at htc or something haahahha)
[Desire HD Android Development] Mustaavalkosta:
I'm not exactly sure what you are asking but SR3 won't be kitkat. There may be SR3 with MediaProvider changes but I haven't decided anything yet. If there will be kitkat rom, it'll have separate thread.

Yeah, LED is still staying on, even after my and paulb-nl's changes, on some cases when battery reaches 100%. I don't know what's going on with that. It's a minor bug though as quick replug turns it off. I prioritize getting kitkat going more currently. :)

Audio delay is a big black box of mystery for me. I don't even know where to look so it's a waste of time to work on at the moment even though it's very annoying issue.
[Desire HD Android Development] evronetwork:
So you're moving on kitkat, that's nice.. so maybe as you work with kitkat you might find and solve the led/audio bugs(and touch more than 3 points-recently :P) by accident (although I haven't really work on programming for a long time, I did my fair share on java one time ..and the most weird accidents was the most wonderful things :p)
[Desire HD Android Development] sashank:
Multi-touch bug for >3 fingers has been present for a long, long time. Not just in this ROM but other AOSP JB ROMs for DHD too. I noticed this more than a year back with the Jellybean bean flinger animation. Try to use 3 touches, it works fine. 4 touches, screen freezes and the bean flinger restarts i.e. the smiling jellybean appears. Sometimes, I think rarely, the device hot reboots.

Either it's a bug or the DHD screen just doesn't support more than 3 touches, I'm not sure.
[Desire HD Android Development] Z_0r10n1S:
After dirty flashing I had to flash gapps or market gmail and others didn't work. Flashing gapps and everything is working fine.

Bad torch apk is still present.

Installed new perf kernel and works like a charm!
[Desire HD Android Development] Chevyguy85:
Well the LED bug was fixed for me, now with the newest nightly and the matching perf kernel it's back. Not a big deal oo a light comes on, more of an annoyance. Thanks for all the hard work! Battery life seems higher on the newest ones but it could just be me paying more attention. 15h+ on battery and 51m screen on and it's down to 58 so still not as horrible as what came with the phone.
[Desire HD Android Development] AtomosVE:
Thanks for believing me and reproducing it :) you're lucky not experiencing hot reboot!

Hope bug will be fixed in kernels, before then, Don't touch more than 3 We will be safe anyway..

Oh I didn't know this..

I noticed this after sweep2wake patch arrived to kernels while I was using Sense ROMs before. touching 4 points was safe before.
[Desire HD Android Development] evronetwork:
DHD supports more than 3 touches, I did the same multitouch test when I had 2.3.7 android so I'm sure

Something is wrong with your rom, try to make a fresh flash and flash gapps, then every dirty flash you're doing, you won't have to reflash gapps CM has a tool build in that take care of that

About the led bug, I've mention some posts ago (you can read it, it's not too far)

Not a problem mate, to be honest without some multitouch program it doesn't create me any issues, any at all! No hot reboot, no flashing things ..I could only replicate that in a multitouch app ..that's it

I use sweep2wake everyday but I'm not having any issues :D
[Desire HD Android Development] ku9911:
hi , flash to latest nigtly ,

my pc can defect the sd card , but it showed 0 byte when it plug with usb

no problem in the phone storage , and it certainly not the sd card problem , because i was check the sd card with usb card reader

anyway to fix it?
[Desire HD Android Development] GeigerS:
I use Titanium Backup. Before I flash a new ROM I back up everything and then make an update.zip of the user apps which I flash after ROM and gapps.
[Desire HD Android Development] AtomosVE:
just we can't beat this if this not fixed.. not more problem. Maybe :D

(Cytus, the rhythm action game. press the circle(s) when horizontal line comes on it)
[Desire HD Android Development] Mustaavalkosta:
I got an idea to check liblights to maybe fix the remaining LED issue while I was browsing through some github repo yesterday for kitkat stuff. I already forgot what was the repo but I pulled in new liblights from Evervolv's msm7x30 repo and made a new nightly. I didn't notice anything breaking up more and because the 100% issue seems to be quite random, any help with testing is welcome. It's available at both hosting sites.

Edit: If this change doesn't fix it, I guess I need a timemachine to go back to yesterday to see what was the repo that had the commit that inspired this test. :silly:
[Desire HD Android Development] Chevyguy85:
I'll test it out and let you know. Might even get ambitious and do a clean install too.
[Desire HD Android Development] evronetwork:
I'll test that later today or tommorow morning, I'm just playing with 4.4 taktik for a bit :D

EDIT: I've test it and the led bug is fixed ...sort of

It doesn't take a minute or more for the let to turn off but it still takes 5-10 seconds to do it. Other than that multitouch bug is there(it should be kernel-bug), I didn't test the audio-delay-bug but it should be there too :D

P.S. This might be an isolated case as my phone is quite slow with so much apps in it(although I did use a task manager to close any up, the single core seems unable to work very smooth ..from time to time. KitKat seems to be smoother than JB). I'll check it again soon to confirm the result.
[Desire HD Android Development] Mustaavalkosta:
Ok, well, if it's really not staying on until battery percentage drops to 99% anymore, I guess we found the culprit. Let me know if the earlier behavior re-occurs later. I'm waiting a while to make sure this is either ok or not, then maybe do SR3 with MediaProvider and liblights changes.
[Desire HD Android Development] s0ulreaver:
I am using the 2910 nightly and the multi touch is working fine with 4 points.

It registers maximum 4:
[Desire HD Android Development] AtomosVE:
Does yours use atmel? you can check sys/android_touch/vender for touchscreen type.

Mine using synaptics
[Desire HD Android Development] MusikMonk:
Browser history might be a more feasible solution, even if it's less cool. ;)
[Desire HD Android Development] evronetwork:
I was right to have my suspicions, the reason for my suspicions were that after the phone was charged 100% and I remove the plug there was a small delay on the response(probably due to many apps that I've got) ..and the fact that I'm having a single core processor phone while I'm doing quite a few things(running multiple services etc).

So I manage to use quite much of my battery and charge it again without anything running(as possible as this might be) and success! the green led turns off when you unplug the cable in less than 1 sec(more or less), so I can call it fixed!

Thanks man, hopefully you won't drop support on this version due to CM11 ..as much as I love 4.4 it still isn't ready for daily job(now on the other hand if you make it stable I'm happy to join CM11 and you can drop support on 4.2.2 :p)

I DIDN'T check thoroughly if the problem occurs with less than 100%, I've check it just a bit and seems fine :-}

Dmn you must be the only one having 4 point working without any problem (mine at this very same program after three points it flashes a few times and the app crashes instantly)

---------------------

Now let's get the CM11 and test it! :P
[Desire HD Android Development] Mustaavalkosta:
That's like... cheating. Time machine or nothing! :p

Anywho, although looking at my github browser history after jumping from repo to repo for 3 days can be a bit like looking for a needle in a haystack, looks like I re-found what I was looking at on Saturday: https://github.com/LegacyCarbon/and...mmit/5b27e9a57e5ef85d2fbe8414c7459ef5538d676f

Not sure what's b/6970382 or will that change disable LED altogether while charging but it's something to test out if Evervolv's liblights still won't work properly.
[Desire HD Android Development] Mustaavalkosta:
CM11

In case people following this thread didn't notice already, there's first CM11 build out since late last night. You can participate in the discussion & bug hunt here: http://xdaforums.com/showthread.php?t=2533007