yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] n0j0e:
No need to reflash Kernel with new GPU frequency settings.

etc/elementalx.conf

Change values, reboot!

Without reboot, reload init.d script 99elementalx in terminal app after changes in elementalx.conf!
[One (M7) Original Android Development] donkeykong1:
I know that, but I like to flash things :D
[One (M7) Original Android Development] zoological:
Thanks for the quick answers guys!
[One (M7) Original Android Development] Rad ryan:
I'm guessing you have Google chrome. Even though you don't use it, go to it's settings and turn off tilt scrolling.
[One (M7) Original Android Development] sinosuke:
Genious's question :D

Sent from my HTC One
[One (M7) Original Android Development] donkeykong1:
No I don't have it. I deleted it from system complitely. It's not installed at all
[One (M7) Original Android Development] Ktan188:
Is it me or do this kernel spend most of it's time at max frequency 1728mhz? I was just browsing the web and xda app. I checked Trickster and it showed it spending most of the time on max frequency. I hope its not draining my battery
[One (M7) Original Android Development] Rad ryan:
? Oh ? I don't know then. Sometimes that Wakelock can be caused by the sensors I believe. Get Wakelock detector from play, click the Wakelock and it should give you the pid and process(though not always) that is throwing the Wakelock, then long click on it and it will give you option to Google it for the specific pid throwing that Wakelock. Or you could get better battery stats from play for like 2.99 (well worth it) or from xda for free and hit the ? on side of the wakelock to Google it. There is also tons of info in both threads and if you can't figure it out the devs will get you to give your dump from the app and analyze it for you. But try yourself 1st bc they probably don't spend all day helping people figure out there Wakelocks and still make a living :)
[One (M7) Original Android Development] Osama Zabin:
It's not the same case for me, cpu 1.7 was rarely used in the past 16 hours.
[One (M7) Original Android Development] donkeykong1:
I know what you mean. I just asked if someone knew what it is because I didn't find any concrete answer. It looks like it really is related to l2w because since I disabled it I got only around 40 seconds of wakelock by the ssme thing
[One (M7) Original Android Development] tiny4579:
I just explained it earlier. It's related to a wake feature and pocket detection. Without pocket detection you won't see the wakelock but the screen would wake instead.
[One (M7) Original Android Development] amirjeegar2005:
If I install this kernel on the ROM Android Revolution HD 52.0 wipe the phone's data?
[One (M7) Original Android Development] alex6600:
Kernel does not wipe data ;)
[One (M7) Original Android Development] donkeykong1:
Yes you did and I followed your advice and it seems good now. Thanks again

---------- Post added at 01:17 AM ---------- Previous post was at 01:16 AM ----------

No if you don't select it in recovery
[One (M7) Original Android Development] amirjeegar2005:
In your opinion, is the best Android Revolution HD 52.0 kernel or kernel ElementalX?
[One (M7) Original Android Development] donkeykong1:
ARHD uses stock HTC kernel. I don't use ARHD but in my oppinion Elemental is far better than stock kernel. I use Elemental with stock ROM and difference in performance and battery life is huge
[One (M7) Original Android Development] guy4jesuschrist:
Does anyone know if there's a way of making a nandroid backup, that when restored days, weeks, or months later, won't overwrite new data? I want to try Elemental, but had issues the first time with the more stable Bulletproof kernel, and had to do a factory reset. I want to be able to restore the stock kernel and remove the extra files and settings that Elemental installs, but I don't want to lose texts and other newer settings that have been added in between the time of installation and possible need to revert to stock. Are there certain options that I need to choose when making a nandroid, to make this possible? Thoughts, [MENTION=4684315]flar2[/MENTION] and/or anyone else?
[One (M7) Original Android Development] Ktan188:
No need for nandroid backup. Just dirty flash your custom rom. It replaces the custom kernel with stock. It also let you keep all your data.
[One (M7) Original Android Development] simonjack83:
Could somebody help me with these wakelocks?

Inviato dal mio HTC One utilizzando Tapatalk
[One (M7) Original Android Development] guy4jesuschrist:
Won't it flash an older file that contains SMS/MMS texts that I received, which would then replace newer ones, as well as replace possible newer settings that I have made since trying the new kernel? Especially if I restore the nandroid months later, just to get my stock kernel back?
[One (M7) Original Android Development] Ktan188:
Dude, dirty flashing and nandroid backup are two different things. Nandroid backups restore your phone to the way it was the day you backed it up. Anything done after you backed it up will be gone like new sms or settings. Reflashing or dirty flashing your custom rom (ex. ARHD, ViperOne etc.) will leave all your data the way it is, it just replaces/ remove any kernels or mods/themes you put on the phone. All data like sms and music are left untouched.
[One (M7) Original Android Development] fanbogo:
i have very good battery life with last ver, Thank you
[One (M7) Original Android Development] guy4jesuschrist:
Oh, ok, I didn't read closely enough, and still had my original post about nandroid in mind. Also, from what I understand, dirty flashing won't remove some of the files that the Elemental installer puts there. I flashed the boot.img of my stock rooted ROM when I had issues with Bulletproof kernel, and had other issues afterwards, I'm guessing from other files that were left behind from the Bulletproof installation. I'm just trying to take all the necessary precautions and become educated enough before flashing, since I already had to go through a factory reset a week ago.

I tried searching through this thread with my Tapatalk app, but didn't return the answers needed for how to return to my stock kernel. I figured I'd be able to find a stock 4.4.2 sense kernel that I could flash via TWRP, and be good, but it's been more difficult than I expected to find the answers, probably because of the extra files that are installed.
[One (M7) Original Android Development] tiny4579:
Dirty flashing the Rom or a nandroid restore of just system taken from a backup prior to installing a custom kernel will keep your data and remove all traces of this kernel.
[One (M7) Original Android Development] Ian.P:
Hi everyone, I'm on 13.3, and start to play "HTC power to give"(it runs only when WiFi and charger is connected)

Then I found that cpu screen off frequency doesn't work, I limit it at 702mhz but the most using when I charging is 1026mhz...

https://www.dropbox.com/s/5i74tu42n1g6fpe/Screenshot_2014-03-15-08-24-42.png
[One (M7) Original Android Development] cyburke:
Thanks for all the hard work!
[One (M7) Original Android Development] guy4jesuschrist:
Oh, ok, thanks! I wondered if a nandroid of just boot and system would work, but I wasn't sure. Wanted to see if someone would suggest something like that or something even better.
[One (M7) Original Android Development] Rad ryan:
It really depends on HOW you are browsing. Downloading and constant page changing will use higher frequencies. But in general this is what ondemand does, it ramps to max when there is load placed on cpu and that is why I'm not the biggest fan of ondemand. But since it's better than the other governors in the kernel and tweaked a good bit by flar2 it's the best choice.

[MENTION=4684315]flar2[/MENTION] Do you think that you could get Powersave_bias working?

Also, is it possible to make it so that instead of jumping to max when there is load, it will split the difference between current frequency and Max and jump there then keep doing same thing until load is low or its at max frequency?
[One (M7) Original Android Development] tiny4579:
Sorry, I forgot boot.
[One (M7) Original Android Development] guy4jesuschrist:
Oh, it's ok. Thankfully, I've been flashing stuff since the EVO 4G, so I've learned a few things. But I know there's always a chance to learn more, especially from phone to phone.
[One (M7) Original Android Development] cyburke:
just wanted to say thanks to you for your settings info... i don't play games on my phone and mainly just use it for reading RSS, emails, and taking pictures. i'm going to try these out and see if i get a similar length of SOT.. over 5 hours would be insane.
[One (M7) Original Android Development] drsamratroy:
Also i have locaton turned off ( i use the location option in venom tweaks for the weather updates ). My wifi & auto-sync is always on. Just i have this problem with heating up with some moderate browsing & music playback. hope [MENTION=4684315]flar2[/MENTION] looks into it. :rolleyes:

[/QUOTE [MENTION=4684315]flar2[/MENTION] a request for whenever you make the next version... kindly add some more thermal throttling as summer is here & the temperature in my place is around 30-35C always now ...so the phone gets hot & uncomfortable even while doing 30 mins of browsing & playing music...btw my settings are uc to 1.5, GPU at 400, 750mv, gboost disabled, run extra cool & battery saving settings in aroma & i am getting over 5hrs of SOT easily. Hoping you look into it. Thanks for the awesome kernel.[/QUOTE]
[One (M7) Original Android Development] bebo_beta2002:
Thanks flar2 for the awesomeness of elementalx....using elementalx 13.3 i have the following battery life
[One (M7) Original Android Development] bebo_beta2002:
Forgot to mention 2 days ago i had this battery life which was better
[One (M7) Original Android Development] javikiller:
The version 13.3 has a bug, you should flash the version 13.4.
[One (M7) Original Android Development] bebo_beta2002:
unfortunately 13.4 has high battery drainage although i knw the update has nothing to do with battery life..but for me 13.4 was draining quickly..and i didn't experience any thing wrong with 13.3 till nw...what bug does 13.3 have mate?
[One (M7) Original Android Development] jayplusone:
Switched back to Elemental X after going to stock and a couple of other kernels. Love the updates in the last few months. Great job [MENTION=4684315]flar2[/MENTION]
[One (M7) Original Android Development] j1po:
Me too, after flash 13.4, charged my phone, 2 hours after charged, deep sleep 0s

Back to 13.3, I'm not use l2w too, so no prob

13.3 is the best battery life for me
[One (M7) Original Android Development] flar2:
Battery drain is usually caused by stuff other than the kernel, like cell reception, the apps you use, what your phone is doing in the background, etc.

There is no difference in battery life between those two kernel versions
[One (M7) Original Android Development] bebo_beta2002:
Exactly the same situation here my friend...i dunn use l2w alot so i dunn have lots of problems with 13.3...also the l2w wakelock is about 3 to 10 seconds in a day ...so 13.3 is the best so far

---------- Post added at 04:43 PM ---------- Previous post was at 04:41 PM ----------

yah i knw there's no difference in battery life but dunno why 13.4 is doing this... i use the same apps with the same background apps with same settings ..and phone with 13.3 lasts for 3 days with single charge but 13.4 lasts almost one day or half a day
[One (M7) Original Android Development] Toxicology:
I'm on 13.0 right now and ARHD 52.0. Battery with 13.0 is terrible, but where can I find the 13.3 version to dl? :)

Sent from my M7
[One (M7) Original Android Development] steve1996:
Use the search function please
[One (M7) Original Android Development] Toxicology:
Found it... Thx:)

Sent from my M7
[One (M7) Original Android Development] FauxAffliction:
I'm with you. 13.3 seemed amazing at battery life and it may just be a placebo but it seems there's higher drain on 13.4..I trust flar that there's no difference but you can't argue with results :)
[One (M7) Original Android Development] LibertyMarine:
I tested it on a clean 4.4.2 KitKat GPE ROM... The phone has a bootloop in bootloader... so I'm stuck in the splash image...

just as a bug report...

I also tested it on a rooted/busyboxed GPE ROM.... still this bootloop
[One (M7) Original Android Development] wmg316:
13.4 battery life is great for me.

Something worth a try...

The first time I flashed 13.4 I experienced a random freeze from the lock screen. The phone would wake, but nothing was responsive. When that happened I booted to recovery and reflashed 13.4, and haven't experienced that issue again.

Maybe just try reflaahing the kernel...no other special steps...just reflash. Do the recommended two boots afterwards, and give it a day to settle in.

IMO, 13.4 is the best version yet! Thanks Flar2!
[One (M7) Original Android Development] ghostryder12:
Some experienced users are saying battery life is not as good on 13.4 as is was on 13.3. Flar2 said that his update didn't do anything that would affect the battery. What have you noticed? I'm on 13.4 and after some extreme changes it cpu & gpu along with flashing 13.4 & I got 7hrs 20mins to 20% today with aggressive use. I'm impressed with 13.4. However I can't give an opinion on 13.3 because of my changes.

Just wondering what you saw.

Via Project Deep-Dig; Appropriation of your info since 2001 via the NSA van parked outside
[One (M7) Original Android Development] wmg316:
I honestly don't see a difference in battery life between 13.3 and 13.4. The point of my input and my post is that I am a believer in a "bad flash". I've been flashing ROMs for a long time, and have had occasions of unexplainable situations where just a simple reflash cleared things up. I do feel that 13.4 is better than battery was on 13.2, which I was running for a while.
[One (M7) Original Android Development] ghostryder12:
Thanks, I've seen you and read your different posts thru the yrs. I have learn from you and other senior users this exact lesson. that if a flash is not responding when you select load or if the mod/rom is way out in left field, the best thing to do is reflash cuz the first flash was corrupted somehow. 99.9% of the time, a reflash fixes just about everything.

Via Project Deep-Dig; Appropriation of your info since 2001 via the NSA van parked outside
[One (M7) Original Android Development] erbse:
here the same but 11.5 works.
[One (M7) Original Android Development] bebo_beta2002:
hmmm..after i read ur post mate am gonna try to reflash 13.4 again and reflash it after first reflash cause as u said it maybe corrupted with the first flash...but i remember something..when flashing 13.4 for first time using aroma the aroma installer was slow..like laggy or something..so maybe that's the case...am gonna try and tell u with results my friend...also u said give it a day to settle down..u mean dunn judge results from the start and start judging after 1 day? or u mean dunn use my phone at all for 1 day and then start using? cause i flashed nw 13.4 and nearly lost 30 percent in 1 hour using wifi only which is really bad battery for me :(
[One (M7) Original Android Development] crnkoj:
I came from 13.0 to 13.4 and saw aome laggyness, a weird reboot/bootloop and slow performance myself, which i havent seen on 13.0 before. I wiped dalvik and cache when installing and the install went smooth. After reading this i reflashed 13.4 again and rebooted 2 times and since than its not laggy and i havent had a reboot yet, but its only approx 8 hours since i have reflashed it. All the settings on 13.4 are the same as on 13.0 before woth arhd 51.0. I will report back with further findings.
[One (M7) Original Android Development] flar2:
It drives me nuts in kernel threads when people install something and say it's laggy or there's battery drain without using it for a day or two. Half the time they don't even try rebooting, which almost always fixes things. There are a thousand and one things that cause lagginess and battery drain, the kernel is usually not one of them.

-if you see worse battery drain in 13.4 compared to 13.3 or 13.2, it's complete placebo effect or caused by something else. From the kernel perspective, the code is the same, the battery is the same. Period.

-lag is caused by all kinds of things. For example, apps being updated in the background, a rogue app using resources, etc. Same goes for excessive battery drain. Nine times out of ten it's Google stuff or a game that did not complete shut down. Nine times out of ten you can fix it by rebooting.

-All ElementalX kernels for the One are 100% stable. You should never have reboots, ever. If you have a reboot, fix your system because it's not the kernel.
[One (M7) Original Android Development] ghostryder12:
R

Thank you Flar2, huge help so I better understand kernel vs system issues.

Edit: Not wanting to sound completely noob cuz I've only been playing with Android for a few yrs, what type of issues would a kernel cause? I'm asking so I can learn more. Thanks

Via Project Deep-Dig; Appropriation of your info since 2001 via the NSA van parked outside
[One (M7) Original Android Development] ONDR4SH3K:
I found error

I found error, but I don't know, if is by kernel.

Swipe from back button over HTC logo to home button (from upper). Vibrates three times (home button, htc log and home button) and shows popup error.

Link to video: http://youtu.be/_2q4qIvK20w

Kernel version 13, Android 4.4.2, HTC Sense 5.5
[One (M7) Original Android Development] guy4jesuschrist:
I'm guessing this also applies to your Bulletproof kernel all the more? And if so, is there an easy way of figuring out what would cause random reboots after flashing the kernel, when I wasn't receiving them previously on the stock kernel? I'm now currently back on stock kernel anyways, but I'm just curious. I'm still considering flashing ElementalX, but have been reading feedback first, before deciding to flash the version that gets the most positive feedback.
[One (M7) Original Android Development] tiny4579:
You can start by getting last_kmsg if you have reboots. It is definitely more helpful than just reporting an issue on a kernel.

If you have reboots because of undervolting, then either increase voltages slightly or keep with stock voltages. It's not a kernel issue if you get reboots due to undervolting.
[One (M7) Original Android Development] guy4jesuschrist:
Ok, thanks for the advice!

I had kept default values on Bulletproof, when installing it. It sounds confusing though, to say it's not a kernel issue if you get reboots due to undervolting, since those are settings you make when installing a kernel. I know there is an explanation for why it's not the kernel's fault, but to most people, claiming it's not the kernel's fault, when you have random reboots only after installing said kernel, doesn't make logical sense.

But based on what you said, in relation to undervolting, I'm guessing it's considered user error if that make settings to the kernel that cause issues after installation. With that in mind though, it could still mean that the kernel is not 100% stable if the default values are used when installing the kernel, and issues of system instability are experienced after installation, if the user has rebooted a few times and allowed the kernel to "settle in" so to speak. That, or it was a corrupt flash or zip that was flashed. Please correct me if I'm assuming incorrectly. Just trying to make sure I understand things correctly.
[One (M7) Original Android Development] real77055:
[MENTION=298610]Flar[/MENTION] is it possible through the kernel or something turn off one of the loudspeaker? i have an issue with my upper loudspeaker
[One (M7) Original Android Development] tiny4579:
With a default undervolting of 850 it's possible some devices can't handle it and reboot. While I agree it's not the kernel's fault, the default settings should be 100% stable for all and undervolting is known to cause reboots.
[One (M7) Original Android Development] Wolf:
Every phone is going to behave differently. There are always acceptable tolerance ranges in production. Elemental kernels are made for users who want to tweak and experiment, and possibly push their phones to certain limits. Not all of the default options given during installation are HTC stock settings. There are some slight tweaks that Flar2 feels are completely safe, but that does not mean that 100% of the phones in the world will react the same to these changes. Change the options to HTC stock settings, and you will have Bulletproof. You can experiment with one setting at a time in small increments to see how it affects your particular phone. If your phone does not like any change, and 99% of the other phones in the world have no problem with it, then you have to unfortunately accept that something concerning your phone is not compatible with certain tweaks. It is a lottery when you purchase a new phone. The person buying the same new phone right after you may be able to under volt and overclock to double the original values with no issues, where as you or I may have instability if we under volt or overclock by 5%. Not fair, but it is also not the fault of the kernel. Blame all of the different manufacturers of all of the different parts that go into a phone, computer, TV, etc. I have had the same experience that you have had and I just had to find the right balance for my phone.
[One (M7) Original Android Development] flar2:
Undervolting would be the only thing causing reboots. It would be relatively few people who have reboots with the default undervolt, and Bulletproof does not undervolt by default. Some versions of Elemental have had 15,000+ downloads and I very rarely hear about reboots.
[One (M7) Original Android Development] ZaneChua:
I searched the thread for anyone who posted settings to get the best battery life but only one and it's for trickster mod and looks to be a little outdated. I wonder if you guys can help me?

1. If I'm on the stock GPE 4.4.2 KitKat ROM, do i use ElementalX 13.4 or 11.5? I am assuming 11.5.

2. Anyone have settings for Faux app or TricksterMod for the best battery life? Not interested in Graphic performance since I rarely game on the One.
[One (M7) Original Android Development] duhhh:
Look at page 966
[One (M7) Original Android Development] guy4jesuschrist:
I agree, especially if the kernel is not supposed to be considered at fault and it also has stock settings as default. I'm only referring to the experience I had with Bulletproof, as I haven't tried ElementalX yet.

Thanks for the clarifications. The reason I tried Bulletproof first is because it was said to be the safer option for better battery life and performance, in relation to the stock kernel.

Ok, that makes sense. The reason I was puzzled about the reboots with Bulletproof, was because it still has the stock kernel settings and I didn't change any of the default settings during installation. Which is what has made me be more cautious and so inquisitive about ElementalX before taking the plunge. After reading more of the recent posts in this thread, it may have fixed the reboots if I had reflashed the Bulletproof kernel. At any rate, thanks for your hard work and being patient in answering questions.