yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] a user:
if you are doing anything over encrypted connections (https, ssh, banking etc.) do not use the frandom module. keep the havege default version in crossbreeder.

i just did a quick research on this crossbreeder mod. there are some interesting things in it and some that are very device specific and most probably won't yield the desired result on oour device. though it is quite customizable.

EDIT: checking HAVEGE and digging more into its nature i would even recomend against using this too. it seems to be a very weak random device, most probably by factors weaker than the standard dev/random /devurandom and in contrary to frandom not really faster than the standard linux devices.
[Desire HD Android Development] a user:
err guys, i'm sorry but i discovered that due to a few typos in my last version of my tweaks something were never periodically executed hence rendered some features not working.

i fixed it and uploaded a new version 1.3.3. i didn't observed it before because it was fixed long before but i included the wrong file in the zip.
[Desire HD Android Development] spikey001:
Well if using the frandom module won't improve anything then I guess there is no point looking at it further.

I just thought it would be a nice option to experiment with, if it was relatively simple to implement :D
[Desire HD Android Development] hacktrix2006:
The commands that i post are not mine.

They are for fixing GPS mainally but it seems to also help with the touchscreen for me when it dies from time to time.

dd if=/dev/zero of=/dev/block/mmcblk0p13

dd if=/dev/zero of=/dev/block/mmcblk0p14

reboot

There is no need to merge it to CM10.1 as one user has already requested which is what i think bestfil was on about.

I myself am not sure why this is but what i am sure is the issue of dying touch screen is on the latest nighties i have gone back to 622 and the dead touch is not there.

Going to reflash latest soon and see if issue comes back.
[Desire HD Android Development] a user:
that's not what i wrote!

it may improve performance for some apps (though somehow i doubt anybody is using apps that rely so much on the random device that you would feel the deifference). but it gives much weaker random numbers used for encryption. i personally would not want this as i am using various things like online banking and cloud services over ssl on my dhd.
[Desire HD Android Development] spikey001:
Sorry, I misread.

Well I do not use my phone for anything with encryption as far as I can think, so I would like to give it a try if I can find a way, or if Musta adds support. However a lot of users, yourself included, use encryption so would it be best to leave support out of the kernel on a general basis?

If so I will just give it a go myself using Punchmod as that seems something I could possible manage. However I don't know of a compatible kernel that has frandom support.

Do you know of any that I could try with?
[Desire HD Android Development] FuKaKa:
after 2 days with RC5 , I can say that this rom is really good exept bugs in camera. take a pic with flash and phone restart, turn off flash it take a picture, but it shows in green after I take :silly: and the phone become laggy after using camera

anyway, this rom is awsome :highfive:
[Desire HD Android Development] Mustaavalkosta:
There has been only one atmel TS change since 0620. None for synaptics. You got atmel or having some weirdness going on? :-o I haven't had any problems with synaptics lately. Even the after-boot deaths have mystically disappeared for the time being. This doesn't mean it's fixed (things usually don't fix themselves) but seems like it's pretty random.
[Desire HD Android Development] hacktrix2006:
I have a synaptics just like you Mustaavalkosta, I will be flashing back up to see if it happens it could be weirdness all together. It was ok till i hit 626 then the issues started up. Only change now is after the 622 was installed and it didn't happen i wiped the whole phone completely thats recovery all the way to boot even the SD-Card and stated again so hopefully once i have the Titanium Backup made (great software) i will try to flash 627.

It just seems weird to me that it was happening on 626. If it happens again though i will last_ksmg, P.S your rom is great next phone is going to be a Google phone, i know it won't be the same but at least its better then Sense LOL. Thanks Man!
[Desire HD Android Development] a user:
as i wrote a few pages back, i had that dying tochscreen issue on turning screen on also on the 0626. and it was the very first time ever i experienced such an issue.

i also have a synaptics one.
[Desire HD Android Development] hacktrix2006:
well i will flash 627 and see how it goes.
[Desire HD Android Development] xpurtwitness:
I've been getting a lot of device freezes and reboots in the last month or so of builds. When I initially went to this ROM, I had almost no issues for weeks at a time, but somewhere in the last couple of months, that changed. It also seems more sluggish, but I can't figure out why. I've done clean installs, and avoided restoring apps from TiBa, choosing very little app data to restore (same as when this ROM was stable for me), also reformatted and partitioned my SD card just to cover all the bases. I'm having trouble pinpointing, but after it locked up today, I pulled the last_kmsg and am attaching it here. I hope that it's useful. Currently I'm on the 20130624 nightly + button fix + non-branding inspiremod. The issue happened without the button fix, as well. No other mods, with default settings regarding performance.

Argh, it just froze again after I uploaded the last_kmsg!
[Desire HD Android Development] Mustaavalkosta:
Sadly, that last_kmsg is from recovery's kernel. :(

Linux version 2.6.35.10 (mx@ubuntu) (gcc version 4.4.3 (GCC) ) #2 PREEMPT Mon Apr 30 19:52:46 CEST 2012

Thanks though for trying!
[Desire HD Android Development] linkit87:
With RC 5 and 06/05 performance kernel I don't have any touchscreen issue at all. With last nightly the touch screen hangs 3/4 time for day.

Don't know if can help.
[Desire HD Android Development] Mustaavalkosta:
Not really. I'm very puzzled by these issue reports as I haven't had problems and I also haven't made any display/touchscreen changes very recently and didn't spot anything on CM's end either. If people's logs are also still empty like they have been this far with the same symptoms, there's very little to do except be very lucky with guessing. :(
[Desire HD Android Development] rjand:
I also had lots of problems with touch screen issues requiring battery pulls, hot reboots, apps fc'ing, etc during the May nightlies, but since the start of June these issues have all cleared up. For me this Rom is as stable now as it has ever been.

I've never enabled any of the s2w, etc features - I don't know if that makes a difference.
[Desire HD Android Development] evronetwork:
Camera bugs? thats probably only you.

The MOST annoying I've seen is that when in camera mode you can't focus but this happens to lots of roms so I'm waiting for a solution in the future.

I can take a picture with flash on, flash auto or flash off, no green what so ever. Try wipe everything, flash the rom(don't restore any of your backups and try again, probably some app you've got is giving you hard time)
[Desire HD Android Development] ILA:
It's not only him... I had a similar problem. After I take a picture with a flash the phone would just reboot... So I decided to dirty flash the RC5 again in hope that it would fix it, but no luck. I ended up stuck on the boot animation so I had to do a full wipe and a clean install. Everything was working afterwards. I don't know what caused it, but there's definitely something going on there.

I've read a few days back that this could be battery related so [MENTION=4803298]FuKaKa[/MENTION] how old is your battery? Mine is over 2 years old so I didn't bother to report this bug, but seems that it isn't just me...

[MENTION=4447997]evronetwork[/MENTION] I agree on the MOST annoying thing in the camera and hope that someone figures out how to add the touch to focus on the video mode soon. [MENTION=3382363]Mustaavalkosta[/MENTION] :)
[Desire HD Android Development] XL3N7:
The reboot when flash is used issue is battery related. Mine would last all day but under 30% it would reboot when I took a pic with flash. Got a new battery and it's never happened again. Maybe this rom needs more current when flash fires but it definitely is battery related.
[Desire HD Android Development] FuKaKa:
I did that and the bug still there

my battery drain a lot. my phone is 1ys old, so I think it's my battery problem :confused:

I found 1 more bug: cant download app from gg play. i use the gapps on 1st page
[Desire HD Android Development] Mustaavalkosta:
It's not really about the age per se. It's about how many charging cycles you have done with the battery. I had relative's HTC Sensation on my test/fix bench a while ago that was little over a year old and it would do all kinds of weird stuff: abruptly shutdown by itself for no reason, flash was no go unless it was plugged in to a charger, etc. I got a new battery for it and all the problems went away. I'm not saying this will be some sort of miracle cure but apparently you can kill battery within a year to the point it can't support the phone's power needs anymore.

I also replaced my ace's battery early this year and my own cam flash issues went away. Lag issues can be partly because android.process.media starts scanning the files. I had this after shooting video but I haven't tested it much otherwise so I don't know if the process also chugs all the CPU time with pictures. At least it's possible. If it's just this scanner process that makes ace laggy, I'm not sure if there's anything to do about it except maybe somehow kill/freeze the whole process permanently but that will have side effects. Single core is becoming a bit too little in situations like this. :(

You can check running processes at least in terminal app by running "htop". CPU% column should be hilighted/chosen by default. Landscape mode is pretty much required to see anything useful.

Edit: If those experiencing lags after using camera could check with htop for whether that android.process.media is consuming much CPU time that would be great to either confirm that it's that process that causes lag or maybe something else. Thank you.
[Desire HD Android Development] diyabolic:
i had that lag after taking pics. just replace camera app with leaked one for google edition of htc one and samsung s4. no more lag

you can find it somewhere on xda
[Desire HD Android Development] FuKaKa:
Search for 5m and I cant find it :D

can you give me the link?
[Desire HD Android Development] diyabolic:
here

http://xdaforums.com/showthread.php?t=2340858
[Desire HD Android Development] HanZie82:
Whith a discription like that you have to put a link in. I cant find anything on XDA about "camera app with leaked one for google edition of htc one and samsung s4".
[Desire HD Android Development] diyabolic:
post just before yours

i downloaded the app on my mob so didn't now where i found it..it was somwhere on g+, i just did google search and found it
[Desire HD Android Development] iphonoid:
Thanks for keeping this phone cutting edge:D
[Desire HD Android Development] hacktrix2006:
auser can one have permission to integrate your systune .set files for CM10.1 into one 99misc file please putting all my tweaks into one basket LOL and thought it be nice to ask first.

627 is working great now no deaths on touchscreen at the moment knock wood. Will flash the next nightie that comes out next other then that Desire HD is working great now on 4.2.2. Nice work OP and team.
[Desire HD Android Development] HanZie82:
Thanks i thought your link was a response to FuKaKa.

Sorry for my ignorance. :D
[Desire HD Android Development] Mustaavalkosta:
I just tested my practically unused wired original HTC headset by recording something to my answering machine service and in voice recorder app and it seemed to work fine. Could it be that your headphone jack is damaged like a few others have reported? At least there shouldn't be anything generally wrong with the rom because the mic wouldn't work for anyone then.
[Desire HD Android Development] hacktrix2006:
Just had the Touchscreen die, Spoke too soon and jinx'd it but i have a present for you OP.

Last KMSG

Hope this helps with catching the issue. It happened after a reboot.

Not sure if this is part of the issue. Noticed in the log the following.

[ 7.390075] WARNING: at ../../../../../../../mnt/iscsi-r710-local_storage/homes/mustaavalkosta/cm/kernel/htc/htc7x30-3.0/arch/arm/mach-msm/clock.c:209 clk_disable+0x5c/0x16c()
[ 7.390106] ebi_grp_2d_clk is unbalanced
[ 7.390106] Modules linked in:
[ 7.390106] Backtrace:
[ 7.390136] [<c004600c>] (dump_backtrace+0x0/0x104) from [<c05cf138>] (dump_stack+0x18/0x1c)
[ 7.390167] r6:c0051868 r5:00000009 r4:cf831eb8 r3:00000000
[ 7.390197] [<c05cf120>] (dump_stack+0x0/0x1c) from [<c00a7e6c>] (warn_slowpath_common+0x54/0x6c)
[ 7.390228] [<c00a7e18>] (warn_slowpath_common+0x0/0x6c) from [<c00a7ebc>] (warn_slowpath_fmt+0x38/0x40)
[ 7.390228] r8:00000000 r7:c0807b0c r6:cf830018 r5:a0070013 r4:c07c0afc
[ 7.390258] r3:00000009
[ 7.390258] [<c00a7e84>] (warn_slowpath_fmt+0x0/0x40) from [<c0051868>] (clk_disable+0x5c/0x16c)
[ 7.390289] r3:c06e810d r2:c06d9428
[ 7.390319] [<c005180c>] (clk_disable+0x0/0x16c) from [<c031e468>] (kgsl_pwrctrl_axi+0xe4/0x1d0)
[ 7.390319] r7:c0807b0c r6:c07f3388 r5:00000008 r4:c07f31e0
[ 7.390350] [<c031e384>] (kgsl_pwrctrl_axi+0x0/0x1d0) from [<c031e69c>] (kgsl_pwrctrl_sleep+0x148/0x348)
[ 7.390350] r6:c07f3388 r5:00000008 r4:c07f31e0 r3:00000000
[ 7.390380] [<c031e554>] (kgsl_pwrctrl_sleep+0x0/0x348) from [<c031ef78>] (kgsl_idle_check+0x60/0xc8)
[ 7.390411] r5:c07f31e0 r4:c07f3298
[ 7.390441] [<c031ef18>] (kgsl_idle_check+0x0/0xc8) from [<c00c12a0>] (process_one_work+0x2a8/0x45c)
[ 7.390441] r6:cfb82c00 r5:cf830010 r4:cf81df80 r3:cf831f50
[ 7.390472] [<c00c0ff8>] (process_one_work+0x0/0x45c) from [<c00c1c94>] (worker_thread+0x1f0/0x334)
[ 7.390502] [<c00c1aa4>] (worker_thread+0x0/0x334) from [<c00c6c44>] (kthread+0x90/0x98)
[ 7.390502] [<c00c6bb4>] (kthread+0x0/0x98) from [<c00abb24>] (do_exit+0x0/0x71c)
[ 7.390533] r6:c00abb24 r5:c00c6bb4 r4:cf819ec4
[ 7.390533] ---[ end trace b8e9edbf38a570ec ]---
[Desire HD Android Development] Mustaavalkosta:
Nah, that's supposedly just some HTC debug crap that I've been meaning to remove but haven't got done yet. That "error" has been there as long as I remember and it's there whether TS works or not. According to the log synaptics initiates just fine:

[ 4.865081] [TP] synaptics_ts_probe: panel_version: 108
[ 4.865753] [TP] max_x: 494, max_y: 7F8
[ 4.865753] [TP] ts->raw_ref: 273, ts->raw_base: 1543
[ 4.866363] [TP] synaptics_ts_probe: max_x 1172, max_y 2040
[ 4.866394] [TP] input_set_abs_params: mix_x 0, max_x 1172, min_y 0, max_y 1900
[ 4.866760] input: synaptics-rmi-touchscreen as /devices/virtual/input/input1
[ 4.867370] [TP] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode

Regular log after boot up:

<6>[ 5.222869] [TP] synaptics_ts_probe: panel_version: 20b
<6>[ 5.223510] [TP] max_x: 494, max_y: 7F8
<6>[ 5.223541] [TP] ts->raw_ref: 273, ts->raw_base: 1543
<6>[ 5.224151] [TP] synaptics_ts_probe: max_x 1172, max_y 2040
<6>[ 5.224151] [TP] input_set_abs_params: mix_x 0, max_x 1172, min_y 0, max_y 1900
<6>[ 5.224517] input: synaptics-rmi-touchscreen as /devices/virtual/input/input1
<6>[ 5.225158] [TP] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode
[Desire HD Android Development] evronetwork:
I've never got any problem with RC5 or M3.. I've done a few flashes(because sometimes I'm playing with roms) so I'm pretty sure its not the rom. About the battery, mine is about 1.5year old and sometimes I'm positive its way worse than a new one(sometimes is just fine) ..of course a task manager is in place and auto-kills everything that tries to work when screen is off :P

P.S. I've done many bad chargings to the battery(when you charge the battery try to leave it until 100%, it'll keep your battery life longer) - I want a nano battery, hell when they are gonna release those cuties? (FYI nanotechnology batteries would last 20 times more(capacity) and would extent its life by 100 times ..it seems like a dream)

P.S. On the downside if you increase a battery by 20 times to charge it in the same time you'll need 20 times the amps, so with simple math if we have 5v 1A charger(fast) and takes ~30-50 minutes you'll need 5v 20A charger(which seems impossible, 20amber requires quite THICK wires).. different solution might come with increasing the voltage so 10v would need 10A(half), 20v need 5A ..etc). If you try to charge a phone with 5v 1A and its 20 times larger in capacity would need 20 times the time :P (..but it would last 20 times more, so..)
[Desire HD Android Development] ILA:
Thanks for the info. :) But I think that there is no such thing as "bad charging" a lithium battery like that. In fact I think that charging it like that (in full cycles (form min to 100%)) is more harmful, as I read. This was the practice with the old NiCd batteries (along with forming it) and people are still accustomed to doing that even though it is not needed or even harmful to some batteries. The main advantage (among many others) of the lithium battery is that it can be always filled up when needed and not needing it to be fully drained to do that.
[Desire HD Android Development] avemt1:
Ilans is correct. Lithium is a single element molecule which makes it easier to reform the double bond. The old NiCad batteries had to be charged to 100% due to the fact that if not, there would not be a uniform crystalline structure. We do not have to worry about that with Li+ batteries as much. It is good to let them die at least once per month so that the battery is not overrun by free electrons.
[Desire HD Android Development] bestfil:
/\

|

|

|
[Desire HD Android Development] Mustaavalkosta:
That's more like a hack or workaround and shouldn't be incorporated in any ROM to keep it as much "you yourself wanted to do this" as possible for the users. In addition, I don't see any practical way of including that into this ROM. I also fail to see why it would do anything for the touchscreen with the information I have about mmcblk0p13/14.

http://forum.cyanogenmod.com/topic/18880-gps-broken-since-611/page__st__20#entry171860

Black magic? :silly:
[Desire HD Android Development] hacktrix2006:
Thats why i mentioned about it, I know its a hack and its EFS partitions which is mainly GPS. But when i run the commands it does release the touchscreen i do not know why it just does.

Not sure why it works. But for now on the 629 and no touchscreen issues at all with touchscreen. Its clean installed as well with my Titanium Backup restore. So unsure whats causing the touchscreen death.
[Desire HD Android Development] Mustaavalkosta:
Yeah, nothing personal. It's an easy thing to try, better than I've been able to come up this far. :) Did you run those commands via adb while the touchscreen was unresponsive and it just started to work on-the-fly or did you reboot in between? I'm just asking because my TS issue goes away just by rebooting so it may not have anything to do with dd'ing partitions.
[Desire HD Android Development] hacktrix2006:
I tried the battery pull first the touchscreen was still dead after booting back up so i ADB'd in via laptop issued them commands once it rebooted it was working. Thats the bit i think is weird, a Battery pull or adb reboot used to work but its started to not work that way its strange. I take nothing personal about it two or more heads are better then one on this.

Yet touch wood (Brain) on 629 no touchscreen issues. All nighties are clean installs so unless the EFS Partitions go screwy and gets picked up on boot and somehow stops the touchscreen i not sure why formatting the EFS's work for fixing the issue.

I have even tried the 0.85 Hboot as well as the 2.0.0.29 hboot same issues i have swapped radio just incase and all this was before i reported it to you.

It could be down to my EMMC chip where the EFS partitions are that is failing i am just not sure. Will be sending a Desire HD off for repairs at some stage to test on that.

Edit2: Touchscreen back now after adb reboot from shell in SU mode

Edit: [MENTION=3382363]Mustaavalkosta[/MENTION] Touchscreen has died again, there was some cracking noise before it frooze.

I have managed to Logcat the device as well via ADB.

The screen or hardware keys are totally none responsive atm going to reboot the phone now to see if i can get it working again.
[Desire HD Android Development] Mustaavalkosta:
Are you using Trebuchet? There are some entries about input events and trebuchet in that log. Could you try if the problem goes away with Apex or Nova launcher? I'm using Action Launcher Pro so I'm just wondering if launcher could somehow have something to do with this. It sounds unlikely though but not much else to work with at the moment.

Also next time try to get dmesg too if possible. Thank you!
[Desire HD Android Development] hacktrix2006:
Yes i am using the stock Trebuche will try Apex (hate Nova).

Going to be a bit dumb on this next question how does one do a Dmesg ??????

Apex just caused a reboot after lock up. So unsure whats causing all this yet the cracking buzy noise was there before it happen again. So i think that my DHD is on way out.
[Desire HD Android Development] humzaahmed155:
Hmm, have you tinkered with CPU controls at all? Try underclocking
[Desire HD Android Development] hacktrix2006:
Its running stock clocks since the Touchscreen started to do the dying trick after that benching i did.
[Desire HD Android Development] rjand:
For what it's worth I've only had 1 battery pull since the start of June, using default Trebuchet launcher, synaptics touch screen, no full wipe in months.

I hardly ever reboot / turn off my phone as I usually let a nightly run for a week between upgrades, could touch screen issues be more common for people who reboot often?
[Desire HD Android Development] Mustaavalkosta:
This outputs it to your PC:

adb shell su -c dmesg > dmesg.txt

or if you want to save it on the device:

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

And yeah, that behavior doesn't sound like it's ROM related anymore, lol. Remember to duck down if it starts peeping more and more frequently.

Definitely. I've only had after-boot deaths without s2w / with the new s2w and even those haven't occurred in a while. I suppose it has something to do with turning on the TS at boot time but I just can't figure out what that "something" could be. I also tend to reboot several times a day while tinkering with things so I should be a likely candidate to experience after-boot death.

Run-time deaths are completely separate issue on my book and I'm pretty sure earlier run-time deaths were caused by s2w now that I rebuilt it from ground up myself and saw how it actually works under the hood.
[Desire HD Android Development] a user:
i only had the dying touchscreen with the new s2w and dt supporting kernel of the recent nightlies. at least it was a one time only till now.

i can say it has nothuing to do with rebooting often or not and neither with the stock launcerh (am using nova). i hope it remains a one time thing.
[Desire HD Android Development] rjand:
I had quite a few run time touch screen problems during the May nightlies when I was upgrading more often and they required battery pulls, and the majority of those happened after updating apps from the play store without restarting for some reason.

Currently running 0627 nightly with a few restarts and power offs as it's now the weekend and no issues as yet.

I think Mustaavalkosta you made some change to the graphics drivers / repos around the start of June which may have helped.
[Desire HD Android Development] hacktrix2006:
So far no issues no cracklings nothing since going to APEX so unsure what the issue is htop is showing nothing out the blue for CPU usage either.