yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] a user:
ok, seems low threshold below 8 kills the touch screen. though it actually only disables it because it permanently detects "NEAR".

it seems that the detection of NEAR is only possible if you come very close to the sensor. but at least it seems to work to adjoust when to detect FAR, i mean when you have the sensor covered and remove the finger slowly again, the point at which it detects far is a different at which it detectged near when you got closer.

this would help to keep the screen off once it went off, while you are telephoning.

---------- Post added at 12:53 AM ---------- Previous post was at 12:48 AM ----------

@MusikMonk:

what do you?

you raised the two thresholds BY 5-7 or -to 5-7?

what were their values before and what are they now?

mine where 15 and 16 (or was it 18?) by default and i lowered now only the lower one to 10.
[Desire HD Android Development] MusikMonk:
I've meant that I raised them from the test values and now I have them as 5 and 7. But either way disregard the actual values because it varies between devices and I see you've found yours.
[Desire HD Android Development] a user:
you raised them from the test values? what test values? do you mean the default values?
[Desire HD Android Development] evronetwork:
Problem!

Hi all,

Yesterday I've encounter a problem. After I installed some themes, apps and stuff I saw this weird thing(look at the picture right top corner)

So anyone can help me out sort this? btw today its even worse, I can't even see the gear(and I've uninstall almost everything that I installed yesterday to make sure no app or theme was doing this)

EDIT: flashing is the last thing I wanna do(and need, I'd like to find a solution so if this happen in the future I'll know its solution)
[Desire HD Android Development] famewolf:
Anybody using link2sd or any other app2sd methods with these builds? I want to create an ext4 partition but didn't have much luck getting twrp or link2sd to recognize it on my inspire 4g as the mount points have changed.
[Desire HD Android Development] t0mas_:
hi!

just got a freeze, i think it was only screen, since shell still worked.

logcat attached...
[Desire HD Android Development] Jimps:
also had my first freeze on SR1 - lit up and rang but couldn't use screen to answer an incoming call - battery pull job, otherwise all funky atmo
[Desire HD Android Development] Mustaavalkosta:
Looks like PMEM ran out and that brought down the system. Not sure why that happened though. First time I'm seeing this kind of errors.
[Desire HD Android Development] Mustaavalkosta:
Wrong log tag for those AudioHardware7x30 prints. They should be tagged as debug prints instead of errors.

This has nothing to do with previous quote but:

TS issues: I try to find a moment to test more thoroughly my psensor hack this weekend. I'm quite exhausted from the work stuff though. 8 hours of paid programming a day is more exhausting than 12+h of my own projects... :confused:
[Desire HD Android Development] walent:
Are new maps working ok for everyone? I get screen glitches, the picture is moving, etc.
[Desire HD Android Development] linkit87:
Hi I'm on SR1.

Two questions:

1. I can't find the new cynogen privacy option.

2. I'm using the kernel with the fix for synaptic touch freeze, is it possible to combine this version with perf one?

Thanks
[Desire HD Android Development] eryunt:
Gps problem

Hi all,

I discovered my phone could not see any GPS satellite.

Tried with Sygic, AndroTsGps and GPS Status, with no luck..

Also configuring ntp server with Fasterfix didn't help..

With my previous ROM 7.2 GPS was working great.

Any advice from You on how to fix ther problem?

PS: same problems with GoogleMaps as all the others, even after the last update of te app...
[Desire HD Android Development] Mustaavalkosta:
1. Privacy Guard is not available on SR1/CM 10.1.2, only on nightlies.

2. Today's perf kernel has the same

possible

fix and some more (nothing very major though).
[Desire HD Android Development] Mustaavalkosta:
FasterFix hasn't been doing anything since Android 4.0 because ntp server address was moved to frameworks from gps.conf. People has been suggesting slightly pressing the flash cover among other things (be careful with dd command as it has quite high brick risk if you misstype the partition number). I haven't noticed any problems with my gps recently so at least it's nothing universal.
[Desire HD Android Development] t0mas_:
would some other log help? if it happens again :)
[Desire HD Android Development] a user:
haha, just my thoughts.

---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------

that'S a google maps issue. many (even official) roms are affected. if i remember right even nexus 4 with stock rom.
[Desire HD Android Development] gc_geforce:
I have been using "mounts2SD" but it will put all your apps to the SD ext4
[Desire HD Android Development] hacktrix2006:
I use Mount2SD also and i find its the best on out there. Download the Beta Version 3.0.2 install and away you go after setting it up.It also includes the SDCard tweaks and internal EMMC tweaks too.
[Desire HD Android Development] Doctor !:
That is Awesome !

Hi Guys ,

I installed this rom yesterday and so far i havn't had any issues !

Everything works perfectly and most important it is Blazing Fast !

Many Thanks Mustaavalkosta for spending your precious time on this Rom and giving it free to us ! :good:
[Desire HD Android Development] eryunt:
Thanks Mustaavalkosta, I upgraded from RC5 to SR1 and now GPS works again :good:

This ROM is AWESOME, really A GOOD JOB !!!

The only thing I can't find are settings like "call barring" or "call diverting" of GSM section :rolleyes:
[Desire HD Android Development] FireBlast:
Hi Mustaa

I've got a problem discribed here http://forum.cyanogenmod.com/topic/75128-wifi-seems-to-disconnect-after-some-time-of-inactivity/ and I can't find

a solution. Do you have any idea? I've already posted here about it but there was no reply. Can you help me?

Found this http://code.google.com/p/android/issues/detail?id=40792 but I'm lost as nobody here is reporting about this issue on dhd. Is it only me? Can we make some investigation?
[Desire HD Android Development] rjand:
Quit it and then go back into it and our should be okay as long as you don't pull down any menus or go into another app.
[Desire HD Android Development] famewolf:
Can someone provide an alternate download location? I've downloaded the rom 4 times in my browser because I can't use wget or jdownloader to get the files (403 forbidden) and every time the md5sum has not matched:

227aaa9e16320cc8198965a73bec8d32 cm-10.1-20130719-UNOFFICIAL-ace.zip

It should be:

76456491e2caee07eab91a10a12cb9ef /mnt/iscsi-r710-local_storage/homes/mustaavalkosta/cm/out/target/product/ace/cm-10.1-20130719-UNOFFICIAL-ace.zip

*update* Firefox managed where Chrome could not. ;)
[Desire HD Android Development] famewolf:
xps8300:/workarea/android # adb -s HT15TT201809 remount

remount failed: Operation not permitted

This rom doesn't support remounting the system partition as r/w so you can push system apps?
[Desire HD Android Development] a user:
sure it does. no idea what you did there, but this rom supports remounting system partition.
[Desire HD Android Development] WordsworthESP:
It's a theme issue. That gear/settings toggle is not present in CM10.1. I know you said you've uninstalled every theme, but have you gone to Theme Chooser to ensure that the default theme is selected?

Sent from my Inspire 4G w/CM10.1
[Desire HD Android Development] woti23:
the default boot.img has

ro.adb.secure=1

ro.secure=1

in /default.prop

that's the reason adb commands as root do not work
[Desire HD Android Development] ADB100:
But you can enable this in the developer options - Change Root Access to 'Apps and ADB'
[Desire HD Android Development] woti23:
yeah, well, with default boot.img and "Apps and ADB" enabled in developer options

adb remount

won't work for me whereas

adb shell su -c "mount -o remount,rw /system"

does work
[Desire HD Android Development] ultimate-tester:
Weird problem I experienced today:

I was charging my phone, it was turned OFF.

While working, I noticed my key backlights turned on. Freaked me out lol.

I tried to turn on the screen (power button press) but it was definitely turned off. I pressed it a little longer and it started booting.

So basically, the key backlights turned on while charing while having the device turned off...

Running latest nightly.
[Desire HD Android Development] perern:
init.d OC

OC'ing with init.d doesnt work for me I named the file "99tweaks" and moved it to etc/init.d Set the same permission as the other files

#!/system/bin/sh

echo "1305600 1275" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

echo "1401600 1300" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

echo "1516800 1325" > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels

My fault, for this command I don't need the first line, so I removed that and it worked and I'm back at 1.5GHz
[Desire HD Android Development] d9vabder:
Unexpected freezes to where i have to remove battery on the new SR1 release and perf kernel. I also have the imspiremod + gps fix flashed ( did same to my moms phone and it seemed to stop her freezing).

Any ideas, or ways i can send logs? What program do i use to create a log?

**edit** i just realized i never flashed the inspiremod +gps fix on my phone. Now gps locks super fast and overall better performance. Just for future use, how can i create a log of how my phone is running? Thanks
[Desire HD Android Development] Z_0r10n1S:
You can use alogcat or log extreme.
[Desire HD Android Development] evronetwork:
It wasn't a theme issue(I've uninstall all themes and all programs I've installed in short period and it was still there after several boots) but is just stop appearing after a while(2 days), anyway thanks for trying hopefully I won't get it in the future

P.S. The gear appears in certain situations although I can recall them now, if I do I'll post a reply
[Desire HD Android Development] rajkos:
I am on SR1. After flashing hotfix I had the same problem with non responsive screen.

I installed DHD Proximity Sensor Recalibrator 1.10 from http://xdaforums.com/showthread.php?t=951858 and adjust the High and Low threshold (in my case 14-16) and problem gone. I have not issue last 4 days.

Thank you Mustaavalkosta for great ROM.
[Desire HD Android Development] Mustaavalkosta:
Yeah, the in-call hack relies heavily on working proximity sensor. I probably guessed wrong the function that is run when OS turns psensor off as I intended to force resuming of handling touch input when psensor is turned off. Finding the proper function should make synaptics screen less affected by proximity sensors that don't work correctly on in-call situations. Sysfs setting to enable/disable in-call hack could also be an option to be able to choose which problem you want to live with: touch screen (sometimes without s2w or all the time with s2w) being active during calls or a bit hazardous psensor code. :)
[Desire HD Android Development] a user:
some other notes from me (i know i came up with a lot :P )

1. my lowmemorykiller tweaks are actually not active. they get ovveriden by the system init.rc. reason is that it sets the properties after it called the scripts from init.d

but my lowmemorykiller settings were a bit to high anyway. will fix that

2. i tested KSM (kernel same page merging) again. i reported some days back that i had issue with it while having it activated during booting it slowed the phone down till being unusable after a while. now i didn't booted with and it works fine. will also test with booting later.

it is worth to note that it actually can give quite a lot of free memory. you can directly see how you lose the momory again when unchecking KSM and how it slowly frees up a lot again after checking it.
[Desire HD Android Development] Mustaavalkosta:
Either via fastboot:

fastboot flash recovery recovery-clockwork-touch-6.0.2.7-ace.img

or you can try GUI tools such as this: http://xdaforums.com/showthread.php?t=1827723

Edit: And remember to change the default backup type from tar to dup to use the incremental backups.

I can't really say. You need to consult synergye about kernel issues.
[Desire HD Android Development] Uli321:
Some more facts and experiences I want to share with you:

- GPS was not working and even had no icon in my statusbar.... I then decided to again flash a stock rom, activate GPS in it and then clean flash of CM10.1 (V Jan 18). Now, GPS is working quite well and shows its icon again

- I flashed radio some day ago (12.65.60.29U_26.14.04.28_M) and I re-get the adressbook via Bluetooth connection into my car (didn't work before)

- Battery drain is very good these days.

Uli
[Desire HD Android Development] a user:
can anybody explain me how i can see recent commits to the source of this rom in the links available in post 1? in the past i was on several github sites with a nice overview of recent commits. but these ones are very strange. seems everything is months ago while it somewhere states last change is 5min ago. i don't get it. also a lot of projects most month or years old.
[Desire HD Android Development] Daimonion1980:
I have installed the same radio but i don't get the contacts synchronized via Bluetooth. Which Radio do you have installed before?
[Desire HD Android Development] Mustaavalkosta:
I made the changes as you suggested. They'll be in tomorrow's build. [github commit]

Edit: There'll be also this: https://github.com/CyanogenMod/andr...mmit/e7f60fef58f755788cd61aea8acbd9051f914214

Maybe it helps those who still have problems with BT and car kits, I don't know.

Edit2: ^^^It was merged today although it says 12 days ago (the day it was submitted to CM gerrit).
[Desire HD Android Development] Uli321:
Hi,

before I had stock radio (12.56.60.25U_26.10.04.03_M).

Uli

---------- Post added at 05:46 AM ---------- Previous post was at 05:35 AM ----------

Hi,

is anyone using CM10.1 able to sync to MyPhoneExplorer via Bluetooth?

USB works, but BT always fires an error (see log).

In MPE forum its said, that this is a known issue of google's android, however (since I really like the BT sync) I would like to investigate further.

Greetz

Uli

14:48:18.06 Avaiable Ports: COM3=\Device\BthModem8; COM4=\Device\BthModem9;

14:48:18.06 Neue COM-Bibliothek wird verwendet

14:48:18.06 SPort Properties set, opening COM3

14:48:18.17 After OpenPort

14:48:18.17 Settimeout: RT=5000 WT=500

14:48:18.67 Port 3 wurde geöffnet !

14:48:18.67 bOpened=Wahr

14:48:18.68 [TX]: AT+CGSN

14:48:23.69 Got no Model, close port

14:48:23.69 Port 3 wird geschlossen

14:48:23.79 Port wurde geschlossen

14:48:23.80 Telefon konnte nicht identifiziert werden

14:48:23.80 Refresh ComDescriptions...

14:48:23.81 PORT: COM3 Enumerator=BTHENUM Displayed='HTC ulrich' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&0001000F_PID&1200\8&2C0A9608&0&1CB0946FE866_C00000009

14:48:23.81 PORT: COM4 Enumerator=BTHENUM Displayed=Standardmäßgige Seriell-über-Bluetooth-Verbindung InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&2C0A9608&0&000000000000_00000014

14:48:23.81 ErrMsg: Verbindung zum Handy konnte nicht aufgebaut werden:

Telefon konnte nicht identifiziert werden

14:49:06.00 Refresh ComDescriptions...

14:49:06.00 PORT: COM3 Enumerator=BTHENUM Displayed='HTC ulrich' Bluetooth-Port InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_VID&0001000F_PID&1200\8&2C0A9608&0&1CB0946FE866_C00000009

14:49:06.00 PORT: COM4 Enumerator=BTHENUM Displayed=Standardmäßgige Seriell-über-Bluetooth-Verbindung InstanceID=BTHENUM\{00001101-0000-1000-8000-00805F9B34FB}_LOCALMFG&0000\8&2C0A9608&0&000000000000_00000014

<<

>>
[Desire HD Android Development] Daimonion1980:
Okay, so it should be in the upcoming nightlies?
[Desire HD Android Development] Mustaavalkosta:
Re: [ROM][UNOFFICIAL] CyanogenMod 10.1 Nightlies

Starting from 0122, yes.
[Desire HD Android Development] damac:
I've found the BBQLog link to be useful. I click on it, then select HTC->DesireHD(Ace) and that brings the most recent relevant changelog. Does this not work?

http://changelog.bbqdroid.org/#ace/cm10.1/next
[Desire HD Android Development] Mustaavalkosta:
Sorry, I missed this yesterday. CM changes can be easily viewed on BBQlog as stated in previous post by damac. I'd use some officially supported device to filter the noise from every officially supported device repo. Repos I use in local_manifest.xml can currently only be tracked manually as they are so spread around.
[Desire HD Android Development] a user:
jsut a short feedback on 22th build. so far no issues. relatime does not have a negative impact on io performance, just as i expected.

oh and btw. KSM feature works even after rebooting without issues and gives a good amount of free memory. note: the mentioned extra cpu time used to find them is not a problem because this is done asynchronously and with low priority. i would really recommend to everybody to turn this vrey nice feature on.

p.s. i also use this remove unused images from memory feature without problems, though i can't tell if it actually gives any memory back. at least it seems to not cause any harm.
[Desire HD Android Development] rjand:
I've been playing with Synergye's cfx 4.2 ROM since the start and had started to use it as my daily driver once bluetooth was fixed because everything just worked. It unfortunately has a few problems with slow screen updates to changing some cfx Settings and I started getting UID's inconsistent error messages after a couple of reboots even though I full wiped and installed all apps directly from the Play Store without restoring any data.

So I decided to give this ROM a go and it is amazing. Everything just works, no bugs (nothing major anyway, and very few minor bugs too - I can't remember coming across any through my normal use or customising yet), great work Mustaavalkosta.

I am very interested in the work you and a_user are doing to improve the performance of this ROM. Is there any way to get a list of a_user's recommendations and what Mustaavalkosta has actually incorporated into the ROM?

PS.

The one feature I miss from the CodefireX ROM's is the prop.modder, but I guess I just have to edit build.prop and init.d myself.

Thanks again to all the devs working on this ROM.
[Desire HD Android Development] a user:
first of all, my contribution is very minor. there are just some old tweaks i posted here as a very small addition to this rom.

secondly, as far as i know what has been added directly to the rom are:

1. my tcp network settings

2. using the ext4 modules deffault relatime instead of noatime for /data /cache and /devlog

all other tweaks from me are in my userinit scripts available here:

http://www.wuala.com/stefan3141/public/

though the contained lowmemorykiller tweaks are actually not working (they get overriden by the system upon boot). they aren't actually to much anyway. i probably will remove them in a next version.

this reminds me that Mustaavalkosta could at this directory link to its first post instead of a direct link to a versioned zip file. so people can check for new versions on thair own ;)

EDIT: oh i forgot something: i wrote here a post explaining how to customize my tweaks. i will copy that informations into a readme file and put that into the public directory i mentioned above. but not before i am back home ;)
[Desire HD Android Development] Daimonion1980:
Great I will check it this evening!
[Desire HD Android Development] Mustaavalkosta:
Yeah, these 2 projects have a bit different goals. Where this ROM is very strongly focused on overall stability (which is why I'm quite hesitant to do any changes that could jeopardise that goal), the codefireX is more about constantly testing something new which often doesn't go hand-in-hand with stability. I don't mean to say cfX doesn't aim to be stable but bleeding edge and stability rarely fit in the same description. :)

For a free PropModder alternative I can only offer ROM Toolbox Lite. Only downside is the static ad banner at the bottom.

I changed the previous link now point to your site.

@All: I plan to release M-Series build later today for those who don't have time to keep up with nightlies. Stay tuned...
[Desire HD Android Development] rjand:
It's funny 4.2 can be called stable already, but it is better than 4.1 was - less bugs already.

I don't mind ads (if they help developers), but ROM Toolbox Lite looks like overkill for a prop modder, I'll just diff the build.prop between this ROM and the CodefireX 4.1 nightly (CM10) and pick out the interesting looking bits.

Looking forward to the "M-Series", although I'm running the 22/01 nightly at the minute - what's left to fix?
[Desire HD Android Development] dron39:
What does it mean? M-Series...
[Desire HD Android Development] Mustaavalkosta:
http://www.cyanogenmod.org/blog/cyanogenmod-10-m1

As this will still be unofficial build it won't fit the description 100% but as the meme goes: close enough!
[Desire HD Android Development] Mustaavalkosta:
M-Series

So, here it is: the first M-Series build for ace. It goes without saying that it's still unofficial build. It's built with the M1 manifest supplemented with my local manifest. Don't expect huge differences between nightlies and M-Series as M-Series is just a monthly snapshot of nightlies aimed for those who desire a little less hectic pace of updates. Enjoy!

Download M-Series

From CyanogenMod:
[Desire HD Android Development] famewolf:
If I've installed the 07/19 nightly is the source the same as the cyanogenmod 07/19 nightly? The reason I ask is koush implemented some pushsms changes on 07/01 that along with the babel app allow you to use any app to send sms but the sms is sent via google voice...babel has to be pushed as a system app.....but when I run babel it fc's right away. On my HTC HD2 with identical type setup and rom it works as expected.

Details here:

http://www.androidpolice.com/2013/0...-now-be-sent-through-the-stock-messaging-app/
[Desire HD Android Development] Mustaavalkosta:
Yeah, CM repos are synced before building the nightly but this doesn't mean any particular nightly from CM has the exact same state of source code as they don't build all their nightlies at the exact same time as codefi.re build server does. Commits that are live at ~00:30 GMT are pulled in.

Logcat could provide more ace specific details.
[Desire HD Android Development] WordsworthESP:
I haven't seen a gear icon on the statusbar since earlier versions of JB, maybe 4.1.2. The statusbar doesn't change in 4.2.2 aside from accessing Quick Controls.

Sent from my Inspire 4G w/CM10.1
[Desire HD Android Development] famewolf:
Logcat is attached from when I had the babel apk in system/app and enabled in accessibility services. It closed alot as you'll see from the log.
[Desire HD Android Development] paulb_nl:
I think it's a better idea to turn off s2w when sensor is near then skipping touch handling like you are doing now.

Since without s2w touch wont work at all when screen is off.

The worst thing what could happen then is that s2w stops working which is better than the whole touch screen dying. :)

Remove lines 562,563 and change to something like this at line 89:

static inline bool s2w_active(void) {
if (!proximity_status) {
return false;
}
else {
return s2w_switch || dt2w_switch;
}
}

---------- Post added at 11:09 AM ---------- Previous post was at 10:52 AM ----------

Looking at your log I can see you missed this: https://plus.google.com/110558071969009568835/posts/f7A32zWAgb8
[Desire HD Android Development] famewolf:
Thank you. I'd hit the button but I've used up my quota for the day...I guess I'm now "thankless".
[Desire HD Android Development] famewolf:
New logcat attached using babel-beta3 apk.
[Desire HD Android Development] paulb_nl:
You seem to be having an issue with your dalvik cache now. Try to format the /cache partition.