yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] Luisit0:
[MENTION=4684315]flar2[/MENTION] I recieved a call today from my gf. Initially the sensor was working fine, not a single problem. Then I took the phone away from my ear to get something to drink, the phone turned on like normal and the display dimmed after a couple of seconds and turned off, like it normally does to preserve battery. I pressed power to turn on the screen and make sure the call was still connected, and it was. I took the phone and put it next to my ear but, surprise surprise, the display wouldn't turn off. The same issue I described yesturday started to happen, the very same way. I then put on my headphones to continue with the call and connected the phone to the pc via usb cable and ran the two commands u told me yesturdat (adb logcat > logcat.txt and adb shell cat /proc/kmsg > kmsg.txt). I tried waving my arm over the sensor and even put my hand right on top of it, I even covered the entire top left part of the phone to see if it would turn off, but it didn't. I also exited and re-entered the call screen (browsed around messages app and home screen and then back to the phone app where the call is displayed), but still nothing... I uploaded the logcat.txt and kmsg.txt files to dropbox and pasted the links here, so you can check 'em out whenever you can and have the time to. I hope these files are of some help and that there's a fix for this, else I'm just gonna have to suspect it's my device :crying: anyways, thanks for your support! Hope all is well :fingers-crossed:

https://www.dropbox.com/s/b3ny0kpn98y1wc2/logcat.txt

https://www.dropbox.com/s/6nvdfrdgpkxl338/kmsg.txt
[One (M7) Original Android Development] Dperks88:
Do you have to be S-Off to use this?
[One (M7) Original Android Development] Luisit0:
Nope
[One (M7) Original Android Development] Dperks88:
Thanks dude, Just wanted to be safe.
[One (M7) Original Android Development] alphamale99:
If we did mostly stock settings except for OC'd to 18xx and the screen off max CPU, and use power saver, will it cause anything to mess up?
[One (M7) Original Android Development] runganwt:
Testing 3.4 for about 12 hours with latest Radio 4A.17.3250.20 (TMOUS), It is running great so far. Battery about the same as 3.3.

Can help but wonder, what's the good to bring up CPU clock for scrren off from 438 to 702 ?

Will keep monitoring. One thing I notice, I accidentally set max CPU to 438 and use my phone for FB and whatapps for about 3 hours. Battery just drop 3% (1% per hour) Amazing. :D:D:D:D
[One (M7) Original Android Development] brpqzme:
Sometimes when using DT2W, I have to tap 4 or 6 times, not 2. Is this normal, or do I have a model with the described bad proximity sensor?
[One (M7) Original Android Development] runganwt:
I have no problem at all, but it will a little delay like 0.5 sec before it wake. Only 2 taps every time. :o
[One (M7) Original Android Development] flar2:
There are limits on the time between taps and also the location of the taps. This is necessary so that it doesn't accidentally wake from handling the phone. Just try tapping to wake a few times until you find a way to do it that works consistently.

I moved the screen off frequency to 702 so it completes tasks faster. If it completes the tasks faster, it can get back to sleep faster. 702 is fairly fast but still has a low voltage and should use less power than if it were to ramp up to 1728 or whatever your max is.
[One (M7) Original Android Development] kazemitsui:
so im on 3.4 and reverted to my old radio

unplug at around 820am it is now 1110. im at 86%. thats a bit better for now same usage as usual this time no music on the way to work.

hopeuflly things will settle down in the next couple cycles

I did notice this in BBS though. under processes I have this *wakelock* thing and it took up most of my processes. what is that?

Also under Partial Wakelock I have, NLPWakelock and NLPCollectorWakelock. anyone know what those are? they take up most of my wakelock times and compared to item 3 they are nearly 20x higher!
[One (M7) Original Android Development] iElvis:
3.4 is looking good. Not having any issues with s2w.
[One (M7) Original Android Development] sensationfan623:
Definitely worth it! It is amazing what you have done here flar. I'm blown away! A lot of well worth it hard work :)
[One (M7) Original Android Development] SleemLDJ:
This kernel is the shizzle! Thanks flar2
[One (M7) Original Android Development] FangorX:
[MENTION=3325837]kazemitsui[/MENTION]

That's Network Location Provider, and it's caused by Maps or Google Now. To stop the wakelock you have to disable background location reporting in the Maps app, as well as turn off Google Now. You can still use location services, it will just only run when an app requests it. There's no way to stop it if you leave these services enabled.
[One (M7) Original Android Development] kazemitsui:
yea i just noticed that my gps was on automatically or something. also I never really disabled them earlier, but now all of a sudden im seeing the NLP wakelock a lot more often. did something change with google to maps recently? this has only been the last 3-4 days last week my drain was srsly minimal as I said earlier 100-90% over the course of 5hrs

but those same 5hrs is now 100-80%...
[One (M7) Original Android Development] jlevy73:
Oddly I'm having issues with S2W and double tap to wake. After flashing it worked for about 8 hours and now both are not. Volume keys still wake the device but no combination of tapping or swiping works. Will keep troubleshooting to see what the issue it.
[One (M7) Original Android Development] FangorX:
Yeah maps was updated recently. I got wakelocks from Maps even on 4.1 though, so I've always had background location disabled and Maps greenified.
[One (M7) Original Android Development] solidsebazz:
Awesome kernel, really nice job, but, can i install this with ARHD on an AT&T phone?
[One (M7) Original Android Development] Wolf:
Yes you can.
[One (M7) Original Android Development] Prockkaii:
I'm having the same issue using cwm v6.0.3.1

Does anyone has any tips ?
[One (M7) Original Android Development] yeahimdukenukem:
Hey flar2.

Thanks again and again for this great work.

But why is the 3.4 still Release Candidate? I'm a little bit afraid of Betas and RCs. Will you release the 3.4 unchanged or will there be changes or even a 3.5?
[One (M7) Original Android Development] Giblet-dono:
You could try installing it using TWRP instead of CWM

It might be the problem, altough I haven't used CWM in a long time, So I can't be sure
[One (M7) Original Android Development] yeahimdukenukem:
Or try using the latest CWMR:

http://xdaforums.com/showthread.php?t=2173863
[One (M7) Original Android Development] Sneakyghost:
Hey guys,

When 2.7 was released I managed to suddenly get 30 hours with 4 hours screen on time. At the same time I also disabled NLP and killed Gnow. I put the doubled runtime down to that.

Now, it is still disabled but ever since 3.2 or 3.3 I'm back to 15 hours max.

Could it be a kernel thing? It almost looks like that to be honest.

The runtime I get now is pretty much what I got with stock setup when I first unpacked the phone 2 month ago.

I'm running the 2.24 base and viper on it.

Anything I can provide to help find out what is causing this difference?

I've seen there seem to be others with similar experiences?

Mobile post
[One (M7) Original Android Development] Prockkaii:
Thanks, just tried with TWRP.

But the device still restart itself at 10% during the installation.

Something is wrong with my phone..

---------- Post added at 08:12 AM ---------- Previous post was at 08:00 AM ----------

I'd also tried with that recovery but it failed :crying:

By the way, I'm on ARHD 12.1

EDIT : finally it's working !! This is what I did :

- nandroid

- factory reset in CWM

- factory reset in Bootloader (might be useless)

- flash the kernel to see if it's working and it did

- restore the backup

- flash the kernel again

Thanks for your help
[One (M7) Original Android Development] hlenforcer:
i tested most kernels now but ran all your latest versions as daily driver and for me it is the best kernel so far.

i get best undervolting results, since the hsic wakelock fix is included battery drain is awesome, it is very smooth even underclocked and i get best thermal results aswell with this kernel.

the freq selection in aroma is really a plus, i often saw problems with underclocking through oc apps at other kernels which does not have this aroma selection.

the benchmark results are very constant whatever config i run (underclocked and undervolted or everything oc´ed)

i also does not see any major thermal throttling problems, but i have SoC with PVS=5, maybe this is the reason.

only problem i noticed so far is an overall reduced vibration strenght.

to cut a long story short: great kernel and it would get even greater with some lower freq steps to make this kernel even more battery friendly :fingers-crossed:

edit: i forgot to say that your sweep2wake implementation is awesome! it is that responsive, i tested this on another kernel for htc One and it was really bad while your solution works perfect. i tested this a lot on htc sensation at the time show-p1984 invented this for pyramid and it was never that great like on the One with your kernel ;)
[One (M7) Original Android Development] jonas2295:
here you go flar, i made the material as clean as possible and removed the htc one text. Enjoy!

Credit:

Template i used
[One (M7) Original Android Development] gianton:
With which app can I control the kernel settings?
[One (M7) Original Android Development] GuyAdams:
As usual great work Jonas mate, that is stunning.
[One (M7) Original Android Development] ali1984:
The kernel its great ... Hope more fore the future :)

Gesendet von meinem HTC One
[One (M7) Original Android Development] flar2:
[MENTION=3640615]hlenforcer[/MENTION]

Thanks!

Awesome work, that will be the new elementalx logo. Thanks!
[One (M7) Original Android Development] MBentz:
This kernel is perfect with my AT&T version of the One running TrickDroid 5.3. Thanks flar2!
[One (M7) Original Android Development] anilkuj:
I feel the exact same way , tried so many kernels but had one or the other issue, but with this kernel everything works perfectly . Love the Aroma for configuring the UV and OC settings. Thanks for your wonderful work.
[One (M7) Original Android Development] chakra:
Working great on t mobile stock rooted, over clocked to first notch up 1835 or whatever it is, also under volt to 850 no GPU over clock , getting over13500 quadrant scores and good battery so far.
[One (M7) Original Android Development] wmg316:
I am still running the stock, odexed, dev edition ROM that came on the phone...on AT&T network. Would your kernel work with this setup?
[One (M7) Original Android Development] jlevy73:
Trickster Mod, kernel tuner are the two I use most.
[One (M7) Original Android Development] flar2:
The kernel will work.

If all the settings aren't applied properly, you might need to install busybox. There is an init.d script that needs to run at boot to apply all the settings.
[One (M7) Original Android Development] wmg316:
Thanks. I have tried to install busybox from the play store but was not successful. I've searched unsuccessfully for a flashable zip of busybox. Would you happen to have one?
[One (M7) Original Android Development] gianton:
Could you please share this script? Is it for all the settings?
[One (M7) Original Android Development] flar2:
The script is in the install zip. It only applies some of the settings. Most of the settings for this kernel are baked into the boot.img.
[One (M7) Original Android Development] gianton:
Could you post most/all of the settings that can be applied by script and the correct paths?

Thanks mate! :good:
[One (M7) Original Android Development] flar2:
I don't have it.

Why doesn't it install?

An alternative is to add this to the bottom of /etc/init.qcom.post_boot.sh

./system/etc/init.d/*
[One (M7) Original Android Development] wmg316:
Most likely it won't install through market because I am still on stock kernel. I don't think the system is writable unless I flash through recovery.

I've been hesitant to flash anything with Aroma on this device since my power button-hold-off does not reboot the phone.

EDIT: My power button restart problem if you would like to give input: http://xdaforums.com/showthread.php?p=41055251
[One (M7) Original Android Development] gweurk:
Hi guys,

I have noticed a strange issue with my ONE. I have no clue what the root cause is but first things first:

- International Htc one 32gb

- running Trick Droid

- ElementalX 0.6 Kernel, no GPU overclock, Ondemand

- chip with PVS=3

@1700Mhz I get a score of 22500 in antutu latest version

@1890Mhz I get a score of ~24000 in antutu
[MENTION=1463427]1999[/MENTION][/MENTION]Mhz I get a highly lowered score of ~20000 in antutu

The device is not really geeting hot even at 1999Mhz therefore I'm not sure if that is due to thermal throtteling.

Has someelse the same issue?

Thanks
[One (M7) Original Android Development] flar2:
A low benchmark means you're overclocked too high and it's starting to make computation errors. 1890 is the limit for mine too (PVS=2). You could try increasing your voltage a bit, but there is a cost in terms of heat and battery life.

btw, that is how we report issues. Thanks for the detailed post :good:

Ah yes, that's probably it. You need to grab the wp module to lift write protection. Check out the last post in my thread in the development section, I think someone posted a zip for the developer's edition. http://xdaforums.com/showthread.php?t=2230341&page=6
[One (M7) Original Android Development] Flasher8:
Latest version I get less battery life compare to previous 3.3. Same setting as before but the battery really drain very fast.

Attached photo for previous battery result.

Edited: attached 3.4 version battery life.
[One (M7) Original Android Development] Forsh:
Hi,

I'm experienced in flashing custom ROMs from back in the HD2 days and more recently with S2 and i've just upgraded to the M7. I followed the stickied guide to flashing a custom kernel - and flashed CWM original and then ElementalX 3.4 which went perfectly. At the end of the process CWM asked me if I wanted to root, and I selected yes.

But .. phone storage is unavailable now. I can't copy files over using USB, downloaded apps can't download extra data (unwritable SD card error), the camera won't work (unwritable SD card error) and most worryingly I can't flash a stock ROM using the HTC rom update utility.

The play market also stopped working (crashed on startup), though I reflashed the kernel and its working again now. Strangely, I can download and install apps using the play market.

I can't access file system using either android commander (Win GUI of USB connected android root system) or CM File Manager - both give me inaccessible error.

I CAN flash .img via fastboot, but i'm not aware of a stock kernal .img I could flash to try and revert.

Can anyone help?

Thanks

:EDIT: Also, i've tried reflashing CWM, fixing permissions and wiping all kinds of cache and data.
[One (M7) Original Android Development] kosique:
Thanks flar2.

2T609220B91598408
[One (M7) Original Android Development] baudy2:
Hi Sneaky !

How did you disable NLP and Gnow ? Explain, plz in details as they make me boring really.
[One (M7) Original Android Development] Wingzer:
Can't install this touch doesn't seem to work in the aroma installer, can't press next.

Anyone any ideas ?
[One (M7) Original Android Development] yeahimdukenukem:
Use the volume and power buttons instead.

Which recovery do you have?

And which firmware?

---------- Post added at 11:55 AM ---------- Previous post was at 11:53 AM ----------

Which ROM and Firmware do you have? And which version of CWM?
[One (M7) Original Android Development] gianton:
Re worst battery life with 3.4, you should give it some days and after some charge cycles will be better. It only released yesterday.

From the few hours I installed it battery life looks to be the same as previous releases with the same setup on Viper ROM.
[One (M7) Original Android Development] Forsh:
I haven't touched the ROM or firmware, it's stock 1.29 UK. I've tried the latest versions of all the recoveries, CWM original, touch and TWRP.

I tried to install Revolution ROM 12.1 (the only one I have handily downloaded) via sideload, and it copied ... but then hung.

I'm pushing it now, and it appears to be copying ... will have to see if it works!!

:EDIT: New ROM copied and installed and boots perfectly :) Completely forgot about push, its good to have a phone that brings me back to basics again! I'll try flashing ElementalX now and see if its all OK ....

:EDIT 2: It works! For anyone else who experiences this problem - push a new ROM via ADB in recovery, then install that :) Not sure why it happened in the first place though ....
[One (M7) Original Android Development] lichti1901:
Same here, but it's still to early to compare the difference between 2.7 to 3.4 for me. I'll run 3.4 for a few days to let the Kernel settle and then i'll post my results here.

I still think it can be the temperature outside .... We will see

Sent from my HTC ONE running ViperRom
[One (M7) Original Android Development] Wingzer:
2.24.401.12

And CWM none touch version.
[One (M7) Original Android Development] yeahimdukenukem:
Good to see, that it works now, so have fun :)

---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------

That's weird.

Have you tried using volume and power buttons?

Maybe the touch driver is not loaded for AROMA if you don't use a touch recovery, but I'm not sure.

Have you tried CWM Touch?
[One (M7) Original Android Development] Wingzer:
Not yet, managed to struggle through with the buttons, quite strange as I've used aroma before with 0 issues.
[One (M7) Original Android Development] Alex1_kgr:
Hello,

I have S-OFF to install the kernel?

I have unlocked bootloader.
[One (M7) Original Android Development] yeahimdukenukem:
If I understand you right, you don't need S-OFF to install the kernel. Just install from custom recovery.

---------- Post added at 01:18 PM ---------- Previous post was at 01:16 PM ----------

Mmhh, I don't know then.

I'm using CWMR Touch 6.0.3.3 and I have just installed the kernel.

[MENTION=4684315]flar2[/MENTION]: Again, it works so great :)
[One (M7) Original Android Development] RiceDie:
Running new 3.4 on Viper One 1.2.1

CPU stock UV 725

GPU 450Mhz

Running good will do some 3DMark benchies latter
[One (M7) Original Android Development] yeahimdukenukem:
I see you also have UV set to 725 mV.

Do you hear sometimes the voices a bit crackling on calls or is everything just fine?
[One (M7) Original Android Development] los318:
I'd like to report I'm running super smooth on 3.4 also.

Stock options (no defaults), OC'd GPU 450, Simple Gov, no sweep/wake options enabled, BLN off, on ARHD 2.0 GE
[One (M7) Original Android Development] RiceDie:
Havent noticed voice crackling. I did UV 725 back on ElementalX 3.2 didnt notice voice crackling
[One (M7) Original Android Development] yeahimdukenukem:
Ok, then it is a carrier related problem, thanks :)
[One (M7) Original Android Development] RiceDie:
No problem Sir! I did clock CPU above standard speed by AnTuTu came back with a lower score even when clocking above 2Gh'z. At 1.8Ghz didnt yield better then stock... will play around more with frequencies
[One (M7) Original Android Development] yeahimdukenukem:
I've read that OC the CPU does not make so much performance increase.

But please report your results, would be appreciated. :)
[One (M7) Original Android Development] Tableuraz:
Well, with the new version, my 3g connexion is now very unstable and slow as ****...
[One (M7) Original Android Development] tiny4579:
The kernel doesn't affect that. There are other factors at work here.
[One (M7) Original Android Development] flar2:
When overclocking, if you get lower benchmarks at higher clocks, it means you've gone too far. Low benchmarks can be a sign of instability.

The other possibility is thermal throttling. Running the benchmark twice in a row can be enough to cause throttling, especially in the summer.

If you have a stable overclock and are not overheating, you absolutely will get higher benchmarks.

Just FYI, my phone is unstable past 1890. I suspect that for most people, anything much past that will be either unstable or cause heat issues.

Shouldn't make any difference, that stuff is never touched in my kernels.
[One (M7) Original Android Development] Tabtoub:
So I set TCP Congestion Westwood or Vegas?

Sent from my HTC One
[One (M7) Original Android Development] frankcck:
I'm using ViperOne 1.2.1 with Elemental X 3.4.

Did anyone have experience about "optimal freq"and "sync freq" cannot be changed. To be more exact, it could be changed by Faux app, but if I turned off screen and woke it up the settings would be restored to 918000 for both.

Btw, I have checked the governor settings,the settings are different between after installed and after first reboot. Despite I didn't change anything by any applications.

Sent from HTC One by ViperOne Pro Black
[One (M7) Original Android Development] flar2:
I never mess with that, you probably won't notice a difference.

Those settings are changed dynamically by the Android system.
[One (M7) Original Android Development] frankcck:
Thanks for your awesome job.

I would like to know that it is because of Ondemand? Because when I used both teamseven-smartmax and faux-intellidemand could be adjusted by faux application. Is the problem about ramdisk?

Sent from HTC One by ViperOne Pro Black
[One (M7) Original Android Development] Luisit0:
What I referred to when I said Vegas was a kick-ass game that always naturally lagged too much, but after flashing elementalx it barely lags! This kernel made it playable! Also, I only set it to westwood cause I read some posts by a couple of users saying that westwood was great for performance and such, I really have no idea if it's true but my device sure is fast and lag-free, so I just run along with it ;)
[One (M7) Original Android Development] Tabtoub:
Okay thank you Guys ^^

Sent from my HTC One
[One (M7) Original Android Development] PrinceShiva:
Will this work with Paranoid? If not, is there a version for non-Sense (no pun intended) ROMs?

Thanks.
[One (M7) Original Android Development] WinGzZ:
Has anyone noticed a difference in battery life between using Double Tap 2 Wake and Swipe 2 Wake? I feel like Double Tap may use more battery since there's more space that needs to be powered? I could be wrong though.
[One (M7) Original Android Development] iElvis:
No, this is for Sense-based roms only.
[One (M7) Original Android Development] Beremus:
I noticed that with s2w abd d2w, my phone stay awake way more often than with thoses disabled. I reflashed and disabled them. Now my battery life flies.
[One (M7) Original Android Development] WinGzZ:
What do you mean by "stays awake more often"? Shouldn't it only wake when you touch it?
[One (M7) Original Android Development] brpqzme:
Thanks :) I think I just have to tap it HARD rather than gently, then it mostly works!
[One (M7) Original Android Development] Beremus:
I had 4h of awake time within 8h unplugged. I reflashed without them and I got 1h of awake time in 10h unplugged. I didnt, installed any apps between and used only lte, but in the exact same place.
[One (M7) Original Android Development] WinGzZ:
That's not good.. I'm seeing these other reports of good battery life with s2w. Can anyone verify they are indeed getting really good battery life with either dt2w or s2w???
[One (M7) Original Android Development] flar2:
The wake IRQ is enabled for the whole surface, there is no separation of the buttons from the rest of the screen. That means there is no difference using s2w versus dt2w.

I am.
[One (M7) Original Android Development] tyraelasd:
What are the advantages of simple governor on GPU over ondemand? I've read that it's more battery friendly at cost of performance, is that correct? I installed the kernel with ondemand, I wonder if it's any good that simple gov.

Thanks )