yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] businello2000:
really strange ... if i activate the fast charge, the charging curve changes and actually is charging faster

Inviato dal mio Desire HD usando XDA Premium HD app
[Desire HD Android Development] walent:
Not sure what happened here
[Desire HD Android Development] thachtunganh:
Misplaced screen.

Now we have another bug!
[Desire HD Android Development] businello2000:
hi must...some screenshot of what i'm saying...the only strange thing are the mv .

unfortunally i' m fully on an audio project so i can't help u with the bug..but something must change on the code when activeted fast charge because of the different charging curve.

Inviato dal mio Desire HD
[Desire HD Android Development] Mustaavalkosta:
Yep, that has happened with other devices too. Not sure what's going on there. I saw some youtube video that happening on some tablet. Reboot should fix it.
[Desire HD Android Development] Mustaavalkosta:
Well, I don't know what to tell you but if you look here: https://github.com/Mustaavalkosta/htc7x30-3.0/commit/d5bc80ce14e63c5906b19c835f103bcb45f2f6fc

That's the only active fast charge implementation commit if we count out my permission fixes and debug code additions. See L556 and then L633 + L642-649 https://github.com/Mustaavalkosta/htc7x30-3.0/blob/cm-10.1/arch/arm/mach-msm/htc_battery.c. If-block on L556 is always true thus it never enters else-block on L633 and cable type controlling changes are only between lines L642-649 so they are never used. Even if they were used, they would only work according to defconfig changes and not sysfs as it's using #ifdef CONFIG_FORCE_FAST_CHARGE and not if (force_fast_charge == 1).

Battery driver blobs have received no changes regarding fast charge:

https://github.com/Mustaavalkosta/htc7x30-3.0/commits/cm-10.1/drivers/power/ds2746_battery.c

https://github.com/Mustaavalkosta/htc7x30-3.0/commits/cm-10.1/drivers/power/ds2746_param.c

dmesg shows also no traces of fast charge logging output from htc_battery.c:L643. I couldn't find anything else using force_fast_charge or CONFIG_FORCE_FAST_CHARGE than already mentioned files.
[Desire HD Android Development] bestfil:
touchscreen halt

I've noticed some strange behaviour of my touchscreen since a few updates.

After going back from the recovery mode every time the touchscreen stops working - means it looses "sensitivity".

It happens only after rebooting and using recovery mode. So it happened every time when I:

made an update of the ROM

used 4ext for any other reason

and I can't do anything except of unmount battery or use adb reboot command.

What logs shall I share with You, Mustaavalkosta?
[Desire HD Android Development] Mustaavalkosta:
Yeah, TS dies but display and device itself works fine. I've tried to replicate this and succeed and I've taken logs while it's dead but there's nothing in them as far as I could see. I'm not sure how to proceed finding a possible fix for this as there's no clues where to look.

If you want, you can take logcat and dmesg but I bet they come up empty too. :(

One thing I may be interested in knowing is that which panel you have, atmel or synaptics (see /sys/android_touch/vendor)?
[Desire HD Android Development] grayhawk11:
Had same problem sometimes n yes reboot fixes it...panel is Synaptics
[Desire HD Android Development] bestfil:
Synaptics_3K_0x108

If there was hardkeys (volume up & down) arrows feature, we could be able to restart phone without hell of PC - to avoid pulling out the battery.
[Desire HD Android Development] a user:
seems everbody is so satisfied that no one is posting here anymore ... :D
[Desire HD Android Development] jordy1955:
I was thinking the same. I am very happy with RC1 - currently 267hours uptime and counting. Everything works, only issue is momentary slowness every now and then - don't know why but it comes good very quickly. cheers
[Desire HD Android Development] coloured_chalk:
university exams :P
[Desire HD Android Development] Largamelion:
Same here, been running CM 10.1 for ten days and uptime is 233 hours... not a single random reboot. This rom is very stable and the fastest JB rom I 've tried. With CFX I had to constantly free RAM memory by clearing the recent apps to avoid freezes. With this rom I don't, it remains responsive no matter how many apps I open.

I have a Synaptics TS and it only failed once. I believe it happened right after the first boot after flashing gapps.
[Desire HD Android Development] jordy1955:
Yeah, same for me too. only one random reboot since install (dirty flash) over 0508. Many thanks to Mustaavalkosta great job.
[Desire HD Android Development] Mustaavalkosta:
Since I didn't know what else to try I reverted a display commit that may or may not have something to with these more frequent dead TS issues. Perf version is online, regular kernel will be updated in tomorrow's nightly as usual.
[Desire HD Android Development] aproape:
I don’t know if happened to anyone who used this ROM, but when I’m in a conversation my phone does not lock the screen (is black, but it access the settings from notifications). I notice that when I,ve changed ROM from M3 to RC1 and I suppose is because of the S2U. I've tried M3 standard is OK, M3 whit S2U kernel same problem.:confused:
[Desire HD Android Development] MusikMonk:
Do you have the Proximity Sensor Recalibrator installed and tuned?
[Desire HD Android Development] Mustaavalkosta:
S2U=S2W=Sweep2Wake? If yes, it's disabled by default. There's no certainty that s2w feature itself is causing any problems. At least all my personal writings has been purely speculative.
[Desire HD Android Development] Gio_ital:
Was happening to me too when I was in a conversation, then I disabled s2w and everything was fine. I didn't try the s2w in the latest releases.

My touchscreen is synaptics
[Desire HD Android Development] aproape:
Yes

---------- Post added at 02:36 PM ---------- Previous post was at 02:32 PM ----------

S2W yes, and is disabled.
[Desire HD Android Development] divhandyman:
Nightlies

Is anyone experiencing any issues on the nightlies? I am running 5/25 Nightly and no issues yet to speak of super smooth. I have not tryed the M series or RC so not sure if the issues are from these.
[Desire HD Android Development] SupremeBeaver:
Running RC1 here, no issues to speak of at all.
[Desire HD Android Development] pgptheoriginal:
I wonder why the battery life hasn't been an issue for several weeks, and now I'm experiencing this:

http://imageshack.us/photo/my-images/694/screenshot2013052718001.png/

Maps drained 40% during last night, and the phone was in airplane mode! Now I'll try uninstalling and re-installing it, but I'm sure I haven't touched any settings, I really don't know the reason of this behaviour...
[Desire HD Android Development] pnoire:
Running 0527 and perf-kernel and no issue for now.

Even a camera issue in previous nightlies is solved \o/

Thank you Mustaavalkosta for your great work!

EDIT [MENTION=3811525]pgptheoriginal[/MENTION]: Maps is well known to eat the battery if Location based services are enable. Look at this post in the thread of BetterBatteryStats: http://xdaforums.com/showpost.php?p=29420959&postcount=7059
[Desire HD Android Development] Papa Luigi:
the recent Google Maps updates have caused the same drain on my phone (RC1) and on my Nexus 7 (stock). I noticed on my phone the gps indicator is popping on once and awhile, then goes away.
[Desire HD Android Development] humzaahmed155:
[OT] Hey Mustaa, I'm building a CM10.1 ROM from source just for fun, I wondering if I needed any help I could ask you for some tips?
[Desire HD Android Development] Mustaavalkosta:
Try Greenify from the Play Store. It seems to be quite nice for preventing maps from waking the device up if you don't need the background features while still allowing the normal use the maps app when you really need it on the foreground.

Well, nothing special comes to my mind. Google's build environment guide + first post's Q&A guide should be all that is needed for replicating these builds.
[Desire HD Android Development] Roberto_Lim:
Was wondering, is there anyway to change the default camera app on the lock screen.

Aslo wanted to confirm that RC1 has been very stable for me.
[Desire HD Android Development] pnoire:
Yes. Usually, the first time you launch camera from the lockscreen, you get a pop-up to choose the app (if you have 2 or more camera apps installed, of course). You can set the app you want as default, just check "Always"

If you don't get the pop-up, it means that you've already set the native app as default. Go to Manage apps - Select Gallery and use Clear default actions

The next time you'll launch the camera, you will be asked for the app to use.
[Desire HD Android Development] Roberto_Lim:
Thanks, but that did not work for me.
[Desire HD Android Development] pnoire:
Weird, it works for me in nightly 0527.

Try to clean data and cache of Gallery + clear default actions. Do the same with the other camera app.

If it still does not work, try to uninstall/reinstall the camera app you want to use as default.
[Desire HD Android Development] Roberto_Lim:
Am on RC 1. The Camera app, called camera mod is even the default camera app in my Gallery. Still no go.
[Desire HD Android Development] pnoire:
Could it be that Camera mod replace the native app?
[Desire HD Android Development] Balu5:
thank you Mustaavalkosta for the great rom!

do you know any working fm radio app for this rom? I just realized that the radio app is missing.

thanks in advance ;)
[Desire HD Android Development] pnoire:
Try Spirit Free --> http://xdaforums.com/showthread.php?t=1059296
[Desire HD Android Development] bestfil:
Thanks!

New nighlty works well, means I hadn't got any problem after flashing. TS works fine for now.

I have noticed next issue, even worse than the dead TS.

Every time when I make a new phone call, after 10-20 seconds from the begining it ends. I mean "something" ends the call. Then I have to call once again the same person and then the problem doesn't occur.

If I call another person, problem occurs again. Then I call the same person again and the problem disppears.

It's all time like that since 5-10 nightlies...

What shall I send You?

Besides - ROM is almost perfect.

BTW: Could You add any handy tweaks to Your "advanced" menu, not only S2W and fast charge or You don't intend to make the rom more personal?
[Desire HD Android Development] a user:
Drain

A new (maybe old) problem:

Last night, before going to sleep i unpluged my phone from the charger.

NOTE: like it happens from time to time the device failed to detect that charging stopped, so the led still lid greed for around 1-2min after unplugging. This may be related to my issue.

now, after that i went to bed and next morning i observed i lost around 40% battery. checking it i saw a more or less constant 50mA drain. checking wakelogs etc. showed "android system" being the only one causing this. it cannot be any of the gapps as they are all frozen and no process was running.

looking into kernel and syslog seems to show something battery related. i just took a short look though.

used rom was 0524.
[Desire HD Android Development] Mustaavalkosta:
If you have ruled out the possibility that your cheek (screen turns on for a moment) or some badly behaving app ends the call, you can always reproduce it and take logcat+radio log and maybe dmesg. Use adb or some app or copy them from /devlog. I guess they are named something like system_log, radio_log and kernel_log there. If you can, it'd make it easier if you can pinpoint the timestamps for the logs when your call started and ended.

Edit: Advanced menu is only useful for stuff that has some sort of control interface for them already. This basicly limits it to operating with kernel sysfs interfaces etc. Any UI change requires changes in frameworks too.

Yep, I took a look too but didn't notice anything out of the ordinary. Battery spam on kernel log is probably just because of the drain. It spews out some status information.
[Desire HD Android Development] ILA:
Found a small bug...

Sometimes the DSP just stops working... I don't know why and it seems to be random.

Can someone look into this?

EDIT: I'm running the M3
[Desire HD Android Development] rjand:
When Android 4.1 ROM's first became available on the DHD I had similar call issues, updating to the latest radio fixed the drop outs.
[Desire HD Android Development] adam_purkis:
What do you mean by stops working? Crashes or just has no effect?

I am having problems with DSP on my Bluetooth audio. It seems to have no affect at all. I'm not sure if I'm doing something wrong but can anybody else confirm if DSP works for Bluetooth audio? Thanks !
[Desire HD Android Development] rjand:
After listening to music with Poweramp I sometimes get DSP manager has stopped working error message, but if I go back into Poweramp (or any app that uses audio) the audio is still working okay.
[Desire HD Android Development] ILA:
That's the thing. It doesn't crash... The effects just stop working (e.i. bass goes down along with overall loudness). Sometimes after a while it would start to work, but like I said, it's random and I don't know if it will start working or if I have to reboot to make it work...
[Desire HD Android Development] Mustaavalkosta:
I think I just noticed this too. My call ended and phone was in the settings menu. I turned s2w back on last night to test it with some new display commits. Seems like touchscreen doesn't shutdown properly when display turns off but stays active while in-call. I haven't noticed anything like this before today when I had s2w disabled. Workaround for the time being might be just turning s2w off. I don't call much so I can't really confirm this to a way or another for now. Maybe someone else can run more thorough testing for it.
[Desire HD Android Development] ILA:
I found another small bug: When in the "recent apps" by pressing the "menu" button they disappear, but when you go to the "recent apps" again, they're still there...
[Desire HD Android Development] pecora:
Sorry, also for me, 0528 build, clean install.

To clean the app there is obviously the button in the right up corner
[Desire HD Android Development] Mustaavalkosta:
Button light patches

So, for those who are annoyed by the short timeout on capacitive buttons backlight, I changed the behavior to work like physical keyboard backlight after recent CM change. Buttons will stay lit up until screen dims. But since I've continuously promised to keep this rom as pure CM as possible I'm not going to force this change on anyone and it'll stay optional flashable zip that will be recreated every night after nightly build finishes. This should ensure the compatibility even after upstream changes to services.jar but I don't and can't promise that it will work 100% of the time because the creation is fully automated and there's no one testing it before release, so use your own discretion with it.

You can download the first patch zip built for 20130528 nightly and future zips here: http://downloads.codefi.re/mustaavalkosta/cm-10-1-unofficial-ace/button-light-patches

Patch: button_light_with_dim.patch

And no, I don't have any plans to make such patches for other feature requests seen on this thread or any other features. This particular case was easy enough to automate as the change is only few lines and it was limited to single jar-file.
[Desire HD Android Development] a user:
i have this on this rom since i first used this rom. long before s2w even came into discussion.

though, it happens more or less only while on my right ear Oo

edit: btw. i have s2w disabled ;)
[Desire HD Android Development] Steam.:
That member mentioned slide2unlock.Is this implemented in the latest CM?If not, is it even possible?I really like this feature on my SGN.
[Desire HD Android Development] Mustaavalkosta:
Well, I sort of had it too but then it was due badly behaving proximity sensor, fixed that and haven't had any problems while in-call. Of course this can be random occurance thing too but it feels kind of funny that first time it happens within a day I re-enable s2w. I don't have another phone and I'm not going to bother anyone with million calls to document the problem better. Professional grade tester wanted. ;)
[Desire HD Android Development] Mustaavalkosta:
No, we have s2w. I suppose there was either typo or confusion about the term.
[Desire HD Android Development] a user:
hmm, how you fixed it exactly? i didn't thought of the proximity sensor because on all dozens of different roms i had i never ever had issues with the proximity sensor (while i saw many users sometimes haveing such issue).
[Desire HD Android Development] Mustaavalkosta:
Tomorrow's kernel won't have s2w at all. I reverted all the s2w related commits to rule it out completely. I'll upload a test kernel with s2w enabled. You can use it but bug reports with s2w kernel will be discarded for now. UI setting for s2w will stay in place as it'll be just grayed out if sysfs interface doesn't exist.

Since there's no log output and there are very conflicting information coming in there's not much else I can do. Check tests directory later for s2w version (although I'd encourage not to use it to have larger pool of testers for possible other causes for these weird bugs).

Fast charge was also slightly changed but I'm not sure if it actually charges faster now or did I just manage to change the log entries and some useless variables.
[Desire HD Android Development] Mustaavalkosta:
With recalibrator. Completely different issue than I was now having as back then it would switch display on and off. Now only capacitive keys were lit and speaker making touch noises. But now there'll be no s2w so maybe we can get something more definitive than mutual speculation and guesswork.
[Desire HD Android Development] Largamelion:
Many thanks! I 'm currently running RC1, will do a Nandroid backup first and give it a try (unless you tell me now it 's not compatible with RC1).
[Desire HD Android Development] pecora:
18-01 build is incredible fast!!
[Desire HD Android Development] a user:
@michelD: thank you for the feedback. maybe i only had bad luck and should have reflashed it a second time. i will for the 19th build and weill report back then.
[Desire HD Android Development] pecora:
R: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

Also for me no battery drain with 18/01 build.

Inviato dal mio Desire HD con Tapatalk 2
[Desire HD Android Development] a user:
a user's CM 10.1 script tweaks v 1.1

a user's CM 10.1 script tweaks v 1.1

i keep it short this time and only tell about the differences to v1.0

Changes/additions:

Usually if you flash a rom it overwrites the symbolic link for the hosts file to your installed one (in /data/local/hosts). If we have such a local

one and only if, then we restore that link on boot so that your desired hosts file is working again. For this we have a new script in userinit.d

You have now a settings file in /data/local where all the previously mentioned settings (and some new ones) can be changed. There is also a settings.defaul file which you shouldn't touch ;)

If you change anything in the settings file then it will not be overwritten when you reflash my tweaks. If when you flash my tweaks that file is missing than it will install the default settings file (settings.default).

The sound settings script can now be configured using two variables. See the settings file for details.

Added a new script tweaking the mount options for the ext4 partitons /data and /cache to greatly improve io performance.

You can now set within the settings file a different crontab source file to be used to configure cron. So your cron changes will not get overwritten when you flash the tweaks again (or a newer version). So i recommend to not change the original file initial_root_crontab but rather creat a copy/ new one and configure it in the settings file.

I hope i haven't forgot anything :P

p.s. now back to work :D
[Desire HD Android Development] nicopilami:
+1 :D
[Desire HD Android Development] a user:
btw. i also reflashed the 18th build and drain is nearly back to normal. it is at least again below 10mA. will watch it over the day.
[Desire HD Android Development] qazsxdcfv:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

maann just ask mustaavalkosta to include this to the ROM, seems the performance will be up and battery not getting down :thumbup::D , gonna test with 18/01 build ( because of my work , i can only flash xx/xx - 1 build :D )

Oh ya , if this have a link with kernel thing ?? If yes , i see synergye is testing now .. ( above post ) , and whoa ! What is the big cron definition ?

P.s sorry for lot of questions , I'm just a newbie that want to learn

P.p.s this can be opened by term , right ?

Sent from my hTC Desire HD powered CyanogenMod 10.1 by Mustaavalkosta™
[Desire HD Android Development] Libertunas:
I got some issues with wifi/usb/bt tather...

All of this show up and the other device connects on the hotspot but the data connection seems to not be shared.

Anyone can confirm this?

I'm on 18/01 with dirty flash
[Desire HD Android Development] qazsxdcfv:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

Nope , 17/01 works perfectly , ..

Sent from my hTC Desire HD powered CyanogenMod 10.1 by Mustaavalkosta™
[Desire HD Android Development] Mustaavalkosta:
I've been using wifi tethering for my tilapia from the beginning of these nightlies and no problems whatsoever. I'm pretty sure USB tethering is working too, although I haven't used that one in couple of days. I have never used BT tethering, so no clue about it.
[Desire HD Android Development] Mustaavalkosta:
I may include those new mount parameters for tomorrow's nightly. The rest is and should stay at user's own discretion. :)
[Desire HD Android Development] Libertunas:
Ok thx for the info,

it's strange coz other devices can connect on my hotspot but data connection seems to not be shared, i'll try something else before do a clean install.

Edit: nothing to do, i've done a clean install 18/01 and wifi tather doesn't share connection... it's strange coz i've no hardware issues with my dhd and tather works fine on other roms.
[Desire HD Android Development] mu3g:
monitor current statistics

What app can I use to monitor current statistics? Thanks.
[Desire HD Android Development] Uli321:
MyPhoneExplorer

Hi,

I installaed current release after full wipe.

Everything fine so far, however I'm not able any more to connect MyPhoneExplorer neither via Bluetooth nor USB to my HTC.

Prior to CM10.1, i.e. with RB31 or lower, I never had this problem.

Any idea??

Uli
[Desire HD Android Development] damac:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

Try battery monitor widget from the play store.
[Desire HD Android Development] KalZakath:
Odp: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

Can anyone confirm problem with ag staw wars? For mi after few games or when i tap on restart level game is switching off to homescreen.
[Desire HD Android Development] Mustaavalkosta:
I just installed MPE and it works fine. It looks like MPE uses basic adb connection to communicate with the phone through USB cable so check that you have USB debugging enabled etc.
[Desire HD Android Development] espmartin:
Hello a user, Can I ask you if you can start a new thread for your script? That way, I can follow it and download new versions without it getting lost in Mustaavalkosta's ROM thread. Or maybe host a website for it? I can see a noticeable difference in the performance of my HTC Inspire with your scripts, and I LOVE THAT!

:fingers-crossed:
[Desire HD Android Development] Mustaavalkosta:
I can take a look at logcat if you want to provide one. Sounds odd nevertheless.
[Desire HD Android Development] cingolat:
AWESOMW ROM as I said before, and now it's even better......very good work mustavalkosta......anyway I would like to see my cam focus while recording a video :crying:.....I don't know if it's a bug of the rom or maybe a strange feature of jb.....