yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] jonny-boy:
I have problems with GPS. I don't know if it is rom related but for some apps gps works, but for some dont. I use 2 different GPS status apps, one gets a successful gps connection, the other one not.

The SportsTracker app for example doesn't get a gps connection, either. I doesn't know since which nightly, but GPS worked correctly some nightlies before. At the moment I am on 17.01 with clean flash.
[Desire HD Android Development] Mustaavalkosta:
Both GPS Status & Toolbox and Sports Tracker work fine here. I'm getting almost instant fix even inside the building. Are these same apps you have been trying or some other sports tracker seeing there are a few in the Play Store?
[Desire HD Android Development] jonny-boy:
Hmm, I don't know why, but now GPS works for me with Sportstracker. I tested to get an gps connection with my old bluetooth gps receiver which works good. After disconnection the receiver sportstracker works now with my phones GPS too so maybe it was something with Sportstracker. The GPS Status App was always working for me.
[Desire HD Android Development] jazzfrequency:
Hi mustaa and thanks once again for the good work !! A little bug..is that when try to play mp4 video from gallery i have always "can not play video"..but those videos downloaded from internet and not from camera. Keep in mind that the same videos were play without any problem from cm file manager and others like rootexplorer. The problem also applies with all previous nightlies. Thanks!
[Desire HD Android Development] paulb_nl:
Yea that should save a lot of battery with that long boot time. :) Did you have some success with the custom RIL class?
[Desire HD Android Development] Mustaavalkosta:
Well, not really. I was mainly playing around and checking what's that about but didn't get to actually fixing anything yet. I'll probably try if hotswapping SIM card is something that could be fixed with that. I also tried to figure out why PIN request takes so long to appear but didn't find much yet from the radio side. At least it seems like BOOT_COMPLETED broadcast is taking very long to get broadcasted which could partly be blamed on gapps since PIN request appears much faster without gapps. But I don't know if this is the full story yet.
[Desire HD Android Development] ryox70:
still no fix on the unresponsive touch after a boot
[Desire HD Android Development] nicram:
Fix boot time? https://github.com/Quarx2k/android_frameworks_base/commit/448e72d7b7c40955e2458a41e512d3709d2d9ae5
[Desire HD Android Development] Mustaavalkosta:
Still waiting for logs on that: https://bugs.opendesireproject.org/show_bug.cgi?id=6

It's atmel touchscreen specific issue and I have synaptics touchscreen so logs are absolutely required. Also could use someone who's able to be active preferably on IRC when changes for it are tested.

That was included on 20150118 nightly. I don't know more.
[Desire HD Android Development] ryox70:
how can i know if i have an atmel screen or synaptics and logs how can i take em for ya?
[Desire HD Android Development] danvo01:
i have clean flash 0118 nightly and I have problem with very long app restoring process (restore apps from stored google config) through wifi - 19 apps wasn't installed from evening to morning. It's about any setting somewhere? Thanks for help..
[Desire HD Android Development] rjand:
You can check /sys/android_touch/vender for touchscreen type.
[Desire HD Android Development] Mustaavalkosta:
You almost certainly have atmel because I haven't noticed any issues with synaptics.

A few ways to extract kernel log can be found here: http://xdaforums.com/showpost.php?p=58064252&postcount=288
[Desire HD Android Development] ryox70:
thanks [MENTION=3382363]Mustaavalkosta[/MENTION] will upload the logs later
[Desire HD Android Development] internauta2000:
Hi Musta...

I have an Inspire 4G with ATMEL touch without any problems.
[Desire HD Android Development] xdagee:
Under [MENTION=3382363]Mustaavalkosta[/MENTION]'s permission, I will do that.
[Desire HD Android Development] Mustaavalkosta:
Yeah, I figured as much due to low amount of complaints but now it's confirmed that not everyone suffers from it even with atmel. Thanks!

This leads me to a question: are you atmel guys, with or without issues, using S2W or DT2W by any chance?

Feel free, no need to ask me for a permission. I can't prohibit anyone from taking screenshots even if I wanted to. I'll probably take some shots from M1 when it's ready sometime next month and add them to first post. That's when the basic features CM wants to include for the first real release are in.
[Desire HD Android Development] xdagee:
I think I was the first person who reported this unresponsive touch issue. I first discovered it when I had started flashing nightlies alongside gapps. since then the issue has been there even on today's 20150119 nightly (which i even submitted a log on that). Not everyone has been posting but i receive some pMs confirming the dead touch on their devices as well. I don't know whether it has something to do with the gapps or the nightly builds. On every instance, if you reboot without unlocking the phone before network loads, you will experience the touch not responding. Until you reboot and unlock the phone before the network loads. BTW how do I confirm whether am on ATMEL or Synaptics?
[Desire HD Android Development] Mustaavalkosta:
http://xdaforums.com/htc-desire-hd/...-12-doge-preview-t2951781/page44#post58276278

It's a kernel issue. That much I know. It would just help if people suffering from it are doing something specific that triggers it -> easier to pinpoint the issue. Based on the stack trace it could be S2W / DT2W because that changes suspend/resume behavior and it's toggleable feature.
[Desire HD Android Development] xdagee:
did you check the logs I submitted today?
[Desire HD Android Development] Mustaavalkosta:
Yes, but it wasn't kernel log. I also answered to bugzilla which is where the action will be happening so follow that for the status updates. You should be also receiving emails about status updates on the bugzilla.
[Desire HD Android Development] danvo01:
I found a bug in settings/ keyboard and language/ add new keyboard FC. Except problem with wifi is all ok..
[Desire HD Android Development] internauta2000:
I personally do not use S2W / DT2W, but I tried activate these, the device rebooted several times and even re-flash the ROM... Everything worked fine on my phone.
[Desire HD Android Development] rjand:
Which nightly did you test this on? I've been using Swype keyboard on all nightlies I've tested, currently on 0116.
[Desire HD Android Development] danvo01:
I'm using 0118 and now dirty flashed to 0119. Same problem. :( I don't want clean flash again :crying: Is any way to set swype keyboard other way than in settings?
[Desire HD Android Development] rjand:
Did you clean flash 0118, if not which nightly where you on before / last clean flashed?

I take out you clicked on the Swype app in the app drawer and followed the on screen prompts to enable it for first time use?
[Desire HD Android Development] Mustaavalkosta:
Apparently we were newsworthy on December: http://www.ibtimes.co.uk/htc-desire...llipop-via-cyanogenmod-12-alpha-build-1480234
[Desire HD Android Development] Mustaavalkosta:
I disabled the whole S2W feature from kernel for today's nightly after inspecting the code and it's more or less related to the error messages seen from kernel log. If this doesn't solve it then I might be interested to hear what atmel users have in /sys/android_touch/vendor. If there are different revisions or versions of atmel panel, it might explain why some of you are having issues while some don't.
[Desire HD Android Development] danvo01:
Yes, 0118 was clean flash. Adding Swype keyboard I tried both ways - through settings and through swype app too. Same result. I will try

todays nightly, clean flash. We will see :)
[Desire HD Android Development] ryox70:
hey [MENTION=3382363]Mustaavalkosta[/MENTION] here's the logs hope its the right one and it helps
[Desire HD Android Development] Mustaavalkosta:
No errors in those logs.

For atmel users in general

In case this wasn't clear from the previous posts I'm still waiting for answers from you to following questions:

Is touchscreen causing issues for you?

Are you using S2W or DT2W?

What do you have in /sys/android_touch/vendor?

In addition if you have had issues with touchscreen is 20150120 nightly working for you?

Please, submit the answers to bugzilla so they are in one place instead of scattered around this thread.

This is difficult enough already without a device to test on. Making it even more difficult by not providing answers to my questions is unnecessary at best. If you want this fixed you need to help me to help you.
[Desire HD Android Development] xdagee:
Though there might be a few of us here experiencing this issue; I do my possible best to submit logs and response to you the best that I can; I already posted kernel logs for yesterday's build and am currently flashing today's build. I always do a full wipe because I want to be sure of whatever is happening. I responded to you on comments 7 & 8 about the atmel on our device on bugzilla.
[Desire HD Android Development] Mustaavalkosta:
Yeah, it's ok. You have already provided most of the information I already have. I just need more information from different people to form some kind of pattern so I can try to compare that to the code and see if something strikes out. The usual tactic "let's try this and see what happens" isn't helping now as I don't have the hardware to try that on. This is why I'm very demanding, and maybe even a bit obnoxious, about user feedback with this particular issue.
[Desire HD Android Development] pat99:
Submitted required answers to bugzilla, hope that could solve the matter to rest.
[Desire HD Android Development] danvo01:
so.. problem with selecting keyboards is gone. But now i have problem with mybackup root - my apps i can't restore. But all restoring process ends with Done (always this means OK) but after restart these apps aren't there (and until restart of course too) What security is it? I have enabled installations from unknown sources and disabled Google play app checking. So what next? Thanks for any help. Btw my apps are standard apps from play store. I have backed apps because this is too high data traffic.
[Desire HD Android Development] pat99:
The version of app you've backed up is the same you're restoring with? I've faced such issue while restoring some of my apps while i was on KitKat. So kindly check the App version, whatever app you've used while backing up those apps.

That's my opinion, but i could be wrong. :fingers-crossed:
[Desire HD Android Development] danvo01:
yes, it was backup from today morning, clean flash after problems with keyboard. Don't know what's wrong..
[Desire HD Android Development] rjand:
Are you using the built in Superuser or SuperSU?
[Desire HD Android Development] danvo01:
phone is rooted, nothing more was needed before. Luckily,a week ago I did a backup with Titanium, so I used that one. But it is interesting. All other working fine.. Musta, you are great!
[Desire HD Android Development] Mustaavalkosta:
zram

I enabled zram after spending tonight poking kernel with various sticks from various directions. It seems when we tested it on CM11 zcache was the root cause for making zram behave weirdly. Apparently with both enabled it tries to compress memory twice and that's very stupid thing to do, especially on a single core device. I'm getting around 30% compression ratio at the moment meaning that 15MB of stuff that would normally use 15MB of memory now only uses 5MB. Your own mileage may vary. Zram size is set to 128MB. My initial feel is that zram is also better option for our device than zcache but because I don't really have any real facts about this take it with a grain of salt.

In another news I did a rollback on the kernel to remove recent backports because they caused issues like I feared. Kernel's internal APIs go haywire quite easily with this stuff and it's not good.
[Desire HD Android Development] internauta2000:
I know that the focus of attention is another... but when upgrading to 20150120 nightlie, my battery drain full and the phone presents lags.
[Desire HD Android Development] jazzfrequency:
20150120 includes zram kernel in order to be test ?

I stick with 116 nightlie and from the moment i flash it my mphone is online for 5 days without any manual or random reboot and it is super stable !

Also i delete (audio.offload.disable=1) from build.prop for maximum and super audio quality because i had auto volume cut off in higher volume.
[Desire HD Android Development] rost2006:
Had no possibility to flash last several nightlies.

Error is occurred

"

Error flashing zip '/sdcard/ROM/CM12/cm-12-20150120-UNOFFICIAL-ace (1).zip'

Updating partition details...

I:Unable to mount '/sd-ext'

......

"

TWRP log file is attached.

any help?
[Desire HD Android Development] Mustaavalkosta:
Zram support has been there since CM11 but it hasn't been in use. AFAIK you can't switch off zcache on-the-fly though and if you enable zram with zcache enabled you won't benefit much from zram because you end up compressing memory twice which is rather useless. Compressed data doesn't compress again that well.
[Desire HD Android Development] Mustaavalkosta:
Update to 2.8.1.2 TWRP. You are using older version because it doesn't have by-name support available.

mount: failed to mount /dev/block/platform/msm_sdcc.2/by-name/system at /system: No such file or directory
[Desire HD Android Development] rost2006:
Thanks, maestro!
[Desire HD Android Development] ffroms:
I'm using nightly 20150118 and works great even though I had some problem starting ROM but now is OK.

Only problem (so far) is with data connection (2G and 3G) so I don't know is it global problem or only me.

Any suggestions?
[Desire HD Android Development] Mustaavalkosta:
No problem. When you provide logs sometimes you get instant solutions. :)

Have you tried inserting your operator's APN info manually?
[Desire HD Android Development] bilal.fanatic:
Boot

How long is the first boot supposed to take?

Ive been waiting for more than 10 minutes now. :confused:

nevermind, it booted.

took about 15 minutes
[Desire HD Android Development] reformista45:
Hello, 40- 50 minutes, maximun, quiet.
[Desire HD Android Development] ffroms:
Yep. Tried that too but no luck.
[Desire HD Android Development] danvo01:
....yes, 0120 nightly has lags... longer time to accept calls and is slower. And people says that my voice in calls is more quiet. So don't know what is changed...
[Desire HD Android Development] Mustaavalkosta:
Ok, you can leave bug report here: https://bugs.opendesireproject.org/

Provide logcat, radio log and kernel log from boot up and I will take a look at some point. I can't really test it on my end because data connection has been working fine since the preview builds.

adb logcat -v time -d > logcat.xt
adb logcat -b radio -v time -d > radio_log.txt
adb shell dmesg > kernel.txt
[Desire HD Android Development] xdagee:
Taking Logs... {}

[MENTION=3382363]Mustaavalkosta[/MENTION]; There is one question that has been boggling my mind; it might sound nobbie but its very important :) the question is how do you want us to take logs? before the event or after the event? ANd if you could recommend some apps for taking logs. - thank you
[Desire HD Android Development] Mustaavalkosta:
Well, it depends what it is that you want to log. If it's a crash, of course, you want to take the log after the crash happens. With network issues like the one a few posts back it's usually more beneficial to log what happens on boot time when it's trying to bring up the network. There's no single rule to this.

When it comes to apps I don't recommend anything but good ol' ADB. Besides possible HW issues with USB jack, only reason not to use ADB would be that something happens while you are not next to a computer but I'm not sure if that's the best situation to be logging anything anyways. It's usually better to try to reproduce it later at home with access to ADB.

There's also the fact that running some logging app on your phone can, in some cases, interfere with the issue itself and produce faulty logs so for this reason it's preferable to keep the logging tool separate from the device you are trying to log. In a sense, logging apps are like throwing your recipe book into the soup you are trying to cook.

If you need help setting up ADB, "how to install adb" search results are full of guides but here are two direct links.

Windows: http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/

Cross platform: http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

If you insist on not using ADB then you are on your own. I don't use log apps so I don't have a slightest idea which one is the best.
[Desire HD Android Development] Mustaavalkosta:
intelliactive

I picked up faux123's intelliactive governor from his Galaxy Nexus (tuna) kernel. Tweaked it to match frequencies and touchscreens on ace/saga and played around with it a bit. It doesn't seem to cause planets to collide and on paper this sounds good so it's now default governor as of tomorrow (20150122).

It has builtin touch boost which means that it gets notified when you touch your screen and ramps up the clocks just like power HAL has been doing since CM10(?) for ondemand/interactive/smartass2. Not using external tool and writing to sysfs entries for this might be faster though which means less latency and more fluid UX. Well, this is what I gathered from the information available to me. Don't shoot me if I got some of this wrong. :p

You can still switch back to smartass2 under performance options if you so desire.

Related commits:

https://github.com/OpenDesireProjec...mmit/0ce8906d280330d2f19cf6adfbc7178911f80acd

https://github.com/OpenDesireProjec...mmit/854d43b90ebf0ebaa5871094cbaf40504ac9fd86

Note: Naturally we don't benefit from multi-core features.

ps. I'm using same governor on my Nexus 5 although I guess comparing it and ace is like apples and oranges.
[Desire HD Android Development] jazzfrequency:
Hi Mustaa, i just flash boot.img from 122, i have 116 nightlie and now testing the new governor.

Indeed INTELLIACTIVE is selected by default so i want to ask you your opinion if could be better change also scheduler to something else..

It seems that CFQ scheduler was a little bit more responsible than RAW.

Anyway after 30min with the new boot.img and INTELLIACTIVE & RAW selected phone seems to be faster but it is not enough time to make a conclusion.

Will keep testing and informed again..

Thanks !
[Desire HD Android Development] danvo01:
Musta, I tried 0119, then 0120 and found problems with wifi (0119 for example during download 0120 nightly, after display off, was rebooted, or stops that download when i tried it again -twice) Both versions was laggy, 0120 had problems with Mybackup root. Don't know how it is in new versions, but now i have 0116 and it is more fast and responsive. If it helps you to find differences which causes lags, it will be fine. Mybackup not works on 0116 too, but 2 - 3 day before was ok - in two steps: in 1st step need restore app only and after restart in 2nd step restore data.
[Desire HD Android Development] Mustaavalkosta:
I've set in init script ROW to be default I/O scheduler for internal memory while CFQ is used for sdcard. My amateurish testing indicated this is the best setup. You can try your own settings though and if you feel, or even better have hard evidence, that your settings are better I'm open for discussion. :p

There has been signicant changes in kernel and other things after 0120. I don't know about backup&restore apps that require root to work. I try to avoid those not to cause any unnecessary issues when they mess up your installation.
[Desire HD Android Development] ryox70:
Found Cause for Unresponsive touch

dt2w and s2w is the cause of unresponsive touch after network loads..... :( i did a a few reboots with both options toggled and waited for network to load and touch stayed responsive when both are off im not sure if the new kernel [MENTION=3382363]Mustaavalkosta[/MENTION] used or something but ive confirmed working on both DHD i have with 20150122 nightly latest recovery and F2fs v3 zip clean installed but thumbs if it worked for you...if it didnt post the needed logs over at Bugzilla :good:
[Desire HD Android Development] xdagee:
screenshot added! on post #3

I added some screenshot since people was demanding for it.

added on post #3 for build 20150122.​
[Desire HD Android Development] Mustaavalkosta:
I just upgraded bugzilla to a new version (4.4.7). Hopefully nothing broke but if you notice something broken that wasn't broken before feel free to PM. I have a copy of 4.4.6 saved so I can rollback if required.
[Desire HD Android Development] maxxjaxx:
Good day Musta, thanks for your hard work on providing us Android 5.0 on our ageing DHD....

I observed that on the 20150121 nightly and every other CM12 on this thread makes my opera mini app hardly loads image completely... it takes several minutes to show the images, please its not a network issues.

a screenshot is attached
[Desire HD Android Development] Mustaavalkosta:
What about stock browser? It has been working fine for me. If it's just opera, likely the issue is within opera and I can't do anything about that.
[Desire HD Android Development] maxxjaxx:
well just that I love using opera mini...I don't enjoy using the stock browser.
[Desire HD Android Development] Mustaavalkosta:
Yeah, I understand that but I can't do anything for proprietary software. You should contact Opera folks if it's just Opera browser that doesn't work.
[Desire HD Android Development] Mustaavalkosta:
Changelogs

I did some bash voodoo the other night and now there will be rough changelogs available. Since it's based on time instead of per repo git commit IDs it's not 100% accurate which means that if something changes within the minute when changelog was created it may be included or left out. But as long as my build automation is purely bash scripts this is pretty much "close enough" when it comes to time spent setting it up.

The method has also a few caveats that make it a bit unreliable. If something happens to the files I use for storing last sync time the whole thing gets quite messed up.

Anyways, now that you have been warned not to treat these changelogs as gospel, for nightlies the changelogs are available here: https://dl.opendesireproject.org/mustaavalkosta/cm-12-unofficial-ace/nightlies/changelogs/

Hopefully I can integrate those to OTA updater app too.

Edit: Now OTA updater should show the changelog for today's nightly. It's a bit mess because the log format didn't quite match with CM's official logs. I made tiny adjustments to the app and it should look a bit more readable tomorrow although it's not on-bar with CM's.
[Desire HD Android Development] rjand:
Mustaavalkosta you are a busy man!
[Desire HD Android Development] rost2006:
Is sync with google account available for built-in browser?
[Desire HD Android Development] Mustaavalkosta:
At least it logins 4-5 times on the first start so it needs Google account for something but I don't know anything more specific.
[Desire HD Android Development] Macedo_apk:
I don't know why but when I try to listen music using my headphones, the music app freaks out. Change the music 3 in 3 seconds and sometimes crash. I tried listen music without heaphones and everythings was ok. I don't have much time right now, so I can´t tell you more. Before changing to cm12, in cm11 the I had the same bug. So, am I the only one with this problem?

P.S.: sorry for the bad english
[Desire HD Android Development] pat99:
It's a bug on CM12, I did notice too but usually I ended up changing Default Music Player to somewhat lighter yet less RAM consuming music app. So i forgot mention about that. Good one keep it up.

BTW on CM11, Apollo v1.1 has got fixed so there won't be Unfortunately stopped working issue anymore.
[Desire HD Android Development] Macedo_apk:
What is the music app you use ?