yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] rm83855:
Suppose this is the downside of the aluminium, i could use my Sony Xperia Z for hours on end without this happening... kinda makes me want to stay clear of metal because at the end of the day i should be able to watch a video without my phone overheating.

How can i identify the background process?

---------- Post added at 06:53 PM ---------- Previous post was at 06:50 PM ----------

I think your right about the heat damaging the battery, i just unlocked the phone and its ran out of battery, after being fully charged 2 hours ago at work...
[One (M7) Original Android Development] spinoza23:
I haven't heat problems on my HTC one m7, check governor frequency and voltage settings
[One (M7) Original Android Development] Ktan188:
It depends on what you do with your phone. If you stream videos or play graphic intensive games over time, your phone will heat up.
[One (M7) Original Android Development] ABQNM:
What network were you using? Wifi/3g/LTE? What is your signal strength? Were you charging at the same time? What frequency do you have the GPU clocked at? And the CPU?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] donmarkoni:
You are wrong. There is nothing better then aluminium for heat dissipation. It look to me that you already damaged your battery with improper use.

There you go. Your battery seems FUBAR.
[One (M7) Original Android Development] ABQNM:
Aluminum is great for the phone, not the user. It is fantastic at keeping the internals of the phone cool and dissipating heat quickly. The problem is where the heat dissipates to--your hands. This makes people think the phone runs much hotter than it actually does.

This phone dissipates heat so much better than my Galaxy S3 and Galaxy Nexus did. My S3 didn't pass the heat along to the user though. It just got hot and slowed down, while the case was just warm. The Galaxy Nexus LTE was just an inferno though. That phone could become hot enough to burn the hell out of your face as the glass was the only real way for it to dissipate the heat.

Aluminum bodied phones are awesome for keeping the insides cool. If it gets too hot for you, just wear gloves. ?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] Mikanoshi:
Burning battery is a kernel/ROM issue? OK... :D
[One (M7) Original Android Development] rm83855:
Precisely, ive never experienced this level of heat on ANY smartphone before and should have mentioned the screen was also extremely hot. Although the phone was only measuring 57° it felt a lot hotter. Definately unusable as theres no way you can hold it in your hand. But as for gloves, no lol. If what i read about the LG G3 is true in that it has the aluminium brushed look but uses plastic i may be inclined to upgrade. I would like to be able to watch a video without scalding myself!

---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------

Sorry what does this mean, are you asking me or telling me its not? The kernel allows for overclocking and undervolting which in turn affects battery life. It also provides features such as DT2W which I presume requires some part of the screen to always be active so I thought this could be part of the problem.

---------- Post added at 11:09 PM ---------- Previous post was at 11:02 PM ----------

No just 3G. Signal strength is OK at work not great, I do realise the phone may have been overcompensating for a weaker signal and using more power and yes it was charging through PC at work. Do you know if the fast charge feature would cause overheating?

GPU: 450

CPU Min: 384

CPU Max: 384

CPU max screen off: 1134

Global voltage: 0 mV
[One (M7) Original Android Development] Ktan188:
Charging your phone will always produce heat. Its not good for the phone to do high intensive things on it while charging. As you could tell, it kills the battery. Also your max cpu is 384? That is way too low and will make battery life worse.
[One (M7) Original Android Development] rm83855:
I chose default settings upon install but chose run cool and battery savings?
[One (M7) Original Android Development] gruntparty:
Your CPU max 384 but screen off is 1134?
[One (M7) Original Android Development] DanteGR:
I believe he wanted to say screen off 384mhz and max cpu @ 1.134mhz :)
[One (M7) Original Android Development] ABQNM:
1.134mhz? I don't think it even goes that low. ?

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] DanteGR:
There is the option in aroma to set max cpu with screen ON @ 1.134 mhz
[One (M7) Original Android Development] ABQNM:
I think you mean 1.134GHz...

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] DanteGR:
1.134 Mhz is 1,1 Ghz my friend :)

Sorry the comma in Europe is the equivalent to the dot in the US.

Misunderstanding :)
[One (M7) Original Android Development] ABQNM:
Wow. Not talking about the comma vs period.

You seem to be missing the point. MHz and GHz are FAR from the same thing. 1 megahertz (MHz) is 1/1000 of 1 gigahertz (GHz). So, 1.134MHz = 0.001134GHz.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] poondog:
Does it even matter :D

I believe we are all talking about the same step
[One (M7) Original Android Development] DanteGR:
So 1 Gigahertz is 1000 Megahertz right?

1,134 Gigahertz is 1134 Megahertz
[One (M7) Original Android Development] c-prodigo:
Link for .11 is down...
[One (M7) Original Android Development] ibby2606:
would you guys say the battery life is better on this kernel or Bulletproof?
[One (M7) Original Android Development] rockyseenu:
+1 Appreciate if someone could upload somewhere else :confused:

edit: nvm, it's working now!

Sent from my HTC One
[One (M7) Original Android Development] Hussainally:
Me too... Didn't have such issues on team seven kernel
[One (M7) Original Android Development] jureca:
I can not download your kernel, link does not work
[One (M7) Original Android Development] jaythenut:
I lost 1% in 7 hours last night on beta 11:cool:
[One (M7) Original Android Development] flar2:
Are you guys with Bluetooth problems undervolting?
[One (M7) Original Android Development] janarp:
Ur settings please and how u use ur phone at the same time?
[One (M7) Original Android Development] jaythenut:
CPU 2144 all 4

Uv 750

Guvnor on demand

Io schedule flops

Sd card 2080

GPU 450
[One (M7) Original Android Development] BrickL0rd:
Same here . Audiolink car thingy
[One (M7) Original Android Development] ibby2606:
How long would you say your battery lasts on this kernel with moderate usage? Say using music, browsing the web and maybe playing a couple games?

When I flashed this a couple days ago I couldn't even get a day out of it, but maybe I didn't allow it to settle in enough.
[One (M7) Original Android Development] jaythenut:
I have music on all day for work phone calls lots of Internet a little youtube no games for about 7/8 hours go down to about 50/40%
[One (M7) Original Android Development] Fidelio_o:
Can anyone upload latest beta? Link is down.
[One (M7) Original Android Development] inffy:
I chose the first UV option in aroma yes.

The sound gets scramblrd ince in a while. I have only noticed when using BT
[One (M7) Original Android Development] chaostan:
This kernel is great but after installed, my camera is not working anymore. Any chance to fix it?
[One (M7) Original Android Development] Hopie:
forget the camera fix in aroma?
[One (M7) Original Android Development] jhericurls:
Is there a way to disable double tap to wake?
[One (M7) Original Android Development] EnIXmA:
I have a weird problem, everything was working fine until today morning. No matter what I do my max frequency changes to 9 ghz by itself. I have tried kernel tuner, trickster etc and it doesn't seem to stick for max. Was working fine for a week until today.

Edit:- nm, reflashed the kernel and it's sticking now
[One (M7) Original Android Development] FitAmp:
Yes 1ghz = 1000mhz
[One (M7) Original Android Development] flar2:
Cultural misunderstanding

1.134 in many languages is equivalent to 1,134 in English

commas are used for decimals in other languages

(It's like that in Québec, which is where I work;))
[One (M7) Original Android Development] shopsdesire:
Version14 work's well here

viperd m7 409.11 elemental kernel= one happy flasher.
[One (M7) Original Android Development] nikolaxxx:
+1
[One (M7) Original Android Development] khandelwalsiddharth:
Audiomix wakelock is eating my battery. Please help!
[One (M7) Original Android Development] Mikanoshi:
Stop listening music)
[One (M7) Original Android Development] khandelwalsiddharth:
There is Not even a single track on my phone. lol.
[One (M7) Original Android Development] spinoza23:
lol
[One (M7) Original Android Development] Mikanoshi:
Then something is using audio all the time) But I can't imagine how it is possible.
[One (M7) Original Android Development] Hoffmanns:
Audiomix is active with every sound from your phone ;) ringing, gaming, alarm, listening music, replaying videos from gallery...

Its normal :cowboy: :good:
[One (M7) Original Android Development] khandelwalsiddharth:
:confused: I dont know man. its really draining my battery.
[One (M7) Original Android Development] tiny4579:
I don't think it is. How are you gauging it as the culprit for draining battery? It may hold a wakelock even with the screen on, and touch sounds may be triggering it. As long as your phone is properly hitting deep sleep, it's fine.
[One (M7) Original Android Development] Osama Zabin:
As said by [MENTION=5469132]Hoffmanns[/MENTION], it's being triggered whenever the phone's speaker plays a sound.

Fix:

1) Settings > Sounds > Turn off or un-tick the last 5 options (keypad touch sounds, touch sounds, screen lock sounds, Pull to refresh sounds, and vibrate on touch.

2) Settings> Language & keyboard > HTC Sense Input > Set "Sound Feedback" to NONE, and "Vibration Feedback" to OFF (not sure about vibration option here but try it)

this fix had reduced AudioMix wakelock for me, but wasn't totally eliminated, and I believe it's Ok to have certain amount of this wake-lock.

Check below threads for more info::

3rd post in below thread under PARTIAL WAKELOCKS, it's same as (AudioOut_1, AudioOut_2)

http://xdaforums.com/showthread.php?t=1827676

http://xdaforums.com/google-nexus-5/help/partial-wakelock-audiomix-n-t2520406/page2

Good Luck
[One (M7) Original Android Development] tiny4579:
Wakelocks when the screen on don't hurt your battery, if they're touch sounds they don't keep the phone awake.
[One (M7) Original Android Development] flar2:
Battery drain issues are not due to the kernel.

I'm on day two since I last charged it and still have 40% left.
[One (M7) Original Android Development] khandelwalsiddharth:
Man what are your settings ?? Rom ??

I hardly get 3 hr sot. My battery life is not good.
[One (M7) Original Android Development] ahmedhzaki:
Can undervolting cause touch problems ? Sometimes the screen won't respond and will only get fixed if I reboot.
[One (M7) Original Android Development] Osama Zabin:
Yes it cause mobile to freez and sometimes to reboot.

Try increase voltage and see if it's fixed, keep increasing until you find optimal value for your device.
[One (M7) Original Android Development] soosoolhastam:
Hey guy, my battery was draining excessively with 14.0. I realized my phone wasn't idleing. I had to turn off my cpu settings in viper to fix it. Now my phone idles. Battery drains normally.
[One (M7) Original Android Development] mitas35:
Mine drains very fast as well i am on ARHD 62 any idea how to fix it??:confused:

Thanks.
[One (M7) Original Android Development] gruntparty:
H guys. This is going to be off topic but maybe related to kernel:

My issue is with the sensor output data from the ambient light sensor in our phones. Our light sensor only reports back these values:

10,40,90,160,225,320,640,1280,2600,10240

When I use the app Sensor Explorer, it reports back that our sensor has a resolution of 1 lux. Yet the list above is the only values reported back.

Is the kernel restricting the values reported by the sensor or is the rom responsible?

Could a developer or someone with knowledge on this issue shed some light as to why this is happening and how it can be changed to allow for continuous data?

I've spent about 2 hours trying to figure this out with no sucess :confused:

Reference
[One (M7) Original Android Development] niteNarmor:
Just need to ask a question. First, I am in the U.S. and travel through out the continental U.S.

Second, just received this device and it is rooted, S-Off (thanks to firewater), custom recovery (latest twrp), and custom ROM (slimkat).

I am not a noob when it comes to flashing or some programming. Most would consider me a ROM junkie.

Just have questions on why different kernels? I mean, what's wrong with stock or better yet what improvements are made over stock? Will it help with signal improvements? I get the battery improvements which are dependent on governor settings.

Just need a little clarification. That's all. Not doubt anybody's work as obviously they know 1000 x's more about this than I do.
[One (M7) Original Android Development] DanteGR:
The screen wake options (double tap to wake etc) alone make custom kernels worthwhile for me. Apart from that there are also performance and battery life improvements. Imo they are definitely worth a shot :)

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] niteNarmor:
With that being said, do you know if this will work on SlimKat and does it depend on carrier?
[One (M7) Original Android Development] DanteGR:
This kernel is for Google Play Edition and Sense based roms.

As for carrier dependency please refer to the first post in this thread.

Everything explained there.

Swiftkeyed from my Renovated HTC One
[One (M7) Original Android Development] niteNarmor:
Thank you. So since my ROM is not Sense or Google based that means no for me. Thank you for the info.
[One (M7) Original Android Development] DanteGR:
There are kernels for AOSP that you could try though.

For example the following one and others.

Just search a bit ;)

http://xdaforums.com/showthread.php?t=2236121
[One (M7) Original Android Development] lawyerone:
how do you do that? and can it also be applied to the bulletproof kernel? If not i' m willing to switch to the ElementalX and follow your settings to try, who knows it will work. My phone also drains and it's starting to bother me. Even when the screen is off, it still drains some juices.

on Viperone 6.1
[One (M7) Original Android Development] mitas35:
I have the same proplems ,on ARHD62 any help pls.

Thank you.
[One (M7) Original Android Development] Hoffmanns:
I have not any issue with battery on this kernel. I have ARHD 53 and 14.0 now. Its great combination.

If you have some problems? Do complete wipe and install new ROM and Kernel. Dont backup system data and apps.

This is the cleanest way for solving these issues ;) try it :)
[One (M7) Original Android Development] Shmi117:
Would also like some light shed on this situation. Is the sensors resolution messed up with this kernel?
[One (M7) Original Android Development] HzeMaffe:
So you want the sensor to report more frequently?
[One (M7) Original Android Development] mitas35:
Guys how can i check if my phone goes to idle?I have battery drain without touching the phone, ARHD62 ,elementalx 14.

Thanks
[One (M7) Original Android Development] Osama Zabin:
Check BBS thread:

http://xdaforums.com/showthread.php?t=1179809

I'm using same combination, my phone was idle last night for 99.7% during 8 hours ( Airplane Mode was on).
[One (M7) Original Android Development] gianton:
With CPU Spy app from Play.
[One (M7) Original Android Development] gruntparty:
I suppose so. Instead of reporting back fixed threshold values, it reports back all values the sensor is designed for.
[One (M7) Original Android Development] lateral18:
battery question

the rom the phone is using is android revolution 4.3 with sense 5.5 has elemental kernel (8.1) , the phone gets that type of battery life. but i notice i have to charge in recovery mode , to get the full 100%

i just wonder why ?
[One (M7) Original Android Development] DrRyder:
You need to update to the latest versions of everything before complaining about a problem. You're on an old ROM and Kernel. Its not surprising you're having issues.
[One (M7) Original Android Development] HzeMaffe:
Just a hunch, but it may increase battery usage as the screen needs to get adjusted / needs to read the sensor more frequently . :)
[One (M7) Original Android Development] gruntparty:
How does reporting thresholds minimize battery? If the sensor utilizes full 1-10240 range, then something restricting it to report back steps instead, probably for the built-in auto brightness to work according to those fixed step values.

Thanks for entertaining the idea with me. I want to find a way to modify those step values or make it use the full range. I dont know what is restricting it.
[One (M7) Original Android Development] donmarkoni:
If I were you, I would just drop it. ;)

It is useless for the following reasons:

1. Objective reason: if light sensor even has 10240 steps, display backlight probably has many times less.

2. Subjective reason: don't know about you, but I would go crazy if my display backlight would constantly change. I like it on auto, but I adjust it almost not to change when I'm inside, just when I go outside where is very bright.

Just my two cents, not trying to pick a fight.

Cheers mate. :)
[One (M7) Original Android Development] millicent:
The stock sense kernel reads and writes to my exfat otg usb properly.

Custom kernels support for otg varies, I found that in the past might work without additional modules or requires nfuse exfat modules thru stick mount or similar app.

However, all newer kernels, even though I check the exfat option in aroma, with stickmount or other apps it just doesn't work properly anymore. Is it the kernel or the exfat libraries, i dunno. Maybe somebody has some insight into this, with as what's the best and surest way to go about this?

Here's the relevant logcat lines when the error occurs:

04-21 10:31:37.582 I/exfatck (256): Repair finished with no repaired inconsistencies.

04-21 10:31:37.582 I/exfatck (256): File system is clean.

04-21 10:31:37.602 I/Vold (256): exFAT check/repair completed OK

04-21 10:31:37.602 I/Vold (256): system/vold/ExFat.cpp (doMount): Mounting with mount("/dev/block/vold/8:1", "/mnt/media_rw/usb", "texfat", MS_NODEV | MS_NOSUID | MS_DIRSYNC | MS_NOEXEC | 0x80, "discard,utf8,uid=1023,gid=1023,fmask=7,dmask=7")...

04-21 10:31:37.602 I/Vold (256): system/vold/ExFat.cpp (doMount): Return value -1 from exFAT mount.

04-21 10:31:37.602 E/Vold (256): /dev/block/vold/8:1 failed to mount via ExFAT (No such device)

04-21 10:31:37.602 E/Vold (256): Volume usb found no suitable devices for mounting :(

04-21 10:31:37.602 E/VoldConnector(981): NDC Command {9 volume mount_encrypted /storage/usb [scrubbed] [scrubbed] off} took too long (10203ms)

04-21 10:31:37.602 W/MountService(981): Insertion mount failed (-2)
[One (M7) Original Android Development] Rix70:
update version

scuse me..the 13.5.1 version is for 4.4.2?

EDIT: sorry..and sense 5.5... ..13.5.1 is the correct versione for me?
[One (M7) Original Android Development] flar2:
Exfat seems to be broken in recent versions. I think I can fix it tonight.
[One (M7) Original Android Development] Shmi117:
Your backlight would not constantly change. There is a threshold it checks (a % above and below your current sensor value) which determines if your display needs adjusting. (I think this is true, I'm not totally sure)

The light sensor itself may have 10240 steps, so why not get as accurate as possible? There have been a countless number of times where my brightness would be too bright or too dim at times using Android's autobrightness. I've switched to Lux to help remedy this problem, albeit still encountering difficulties due to the static number output the sensor gives me.
[One (M7) Original Android Development] mobileman88:
Cool... might get one of those otg microsdxc cards to do backup.
[One (M7) Original Android Development] Rix70:
for 4.4.2 adn sense 5.5 what is the correct version? ..i don't undestand in OP.. i do not wrong!
[One (M7) Original Android Development] Ktan188:
Use v14. The latest kernel
[One (M7) Original Android Development] flar2:
Minor update:

fixes exfat support, thanks to faux for working it out on the m8

Download:

Sense 5.5/6.0 Android 4.4.2

ElementalX-m7-14.1

Changes:

-fix exfat support
[One (M7) Original Android Development] joni2012:
Battery save?

Enviado desde mi HTC One mediante Tapatalk
[One (M7) Original Android Development] hp13:
After flashing this kernel, my screen was all black. I kept the sweep 2 wake off in my second flash and problem was solved. Running Google edition 4.4.2 ARHD 6.1 rom
[One (M7) Original Android Development] millicent:
Exfat works fine here, just like in stock. Amazing job, thank you.
[One (M7) Original Android Development] tiny4579:
You can only use the threshold values actually reported by the sensor which is about 10 or so values. There are definitely not 10240 steps. If you decompile framework-res.apk, you'll see the sensor levels in lux and brightness values for each level up to 255.
[One (M7) Original Android Development] miten_sheth:
Can Intellidemand be re-introduced please? I have been using ondemand and I definitely know that Intellidemand gave me more battery life than ondemand for the same usage..
[One (M7) Original Android Development] Beast Power:
Placebo Affect At Work Here !

http://xdaforums.com/showthread.php?p=51563183&highlight=intellidemand#post51563183
[One (M7) Original Android Development] Shmi117:
If you took 5 minutes to read up on what I was quoting you wouldn't have made a comment. Please go inform yourself.
[One (M7) Original Android Development] tiny4579:
I saw your post and the post you quoted and the one they quoted. I still don't think there's a way to read more sensor values if the 10 or 11 are the only reported. I'm not sure how the sensor works but I know autobrightness is based on light levels between about 10 different light values.

There was in cm7 a way to apply a filter to make light sensor changes a bit smoother and not so jumpy which seems an issue in stock.
[One (M7) Original Android Development] BuffMcBigHuge:
Any one know why the sweep to wake fails randomly? Also, my venom tweaks keeps reverting my max cpu to 384 Mhz and global voltage to -50.

Also, how does this kernel work with power save mode?
[One (M7) Original Android Development] Alfa Kenny One:
can not change GPU frequence

Hi

I can not change the GPU speed in TricksterMod. I have set 585MHz with installing in aroma. Why does the GPU still show 450MHz even when i change the frequence?

I this a cosmetic glitch?

Thanks

(Android 4.4.2 GPE stock)
[One (M7) Original Android Development] DanteGR:
Do you have pocket detection enabled?
[One (M7) Original Android Development] FauxAffliction:
No complaints at all :)
[One (M7) Original Android Development] kami2k:
with viper rom, the cell get high about 55C if i play games for more then 20 mintues
[One (M7) Original Android Development] ABQNM:
Did you reboot twice after flashing? The gpu changes won't stick on the first boot after flashing. This is why it advises you to start up, then reboot again on the last screen of the Aroma installer.

Sent from my brain using human to phone transport technology.
[One (M7) Original Android Development] remix92:
Normal ???

1,1ghz