yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] carlos67:
[MENTION=4684315]flar2[/MENTION],

Do you keep your phone in your trouser pocket a lot? If so, is the screen facing your leg or do you have the screen facing away? I think this is important from a battery life point of view.

I've noticed that when I have it facing away from my leg whilst in pocket, the battery drops slower than when it's facing/touching my leg.

It's easy to say "well just keep it facing away" but, it feels more natural with the screen against the leg because of the curved back of the phone. It's also safer with the screen against your leg if you bump into anything - no risk of screen damage.

I thought that pocket detection(which I have enabled) is supposed to negate the screen touching leg scenario??? Shouldn't pocket detection prevent your screen from detecting leg touches?
[One (M7) Original Android Development] Thug_4_Life:
Indeed, the phone keeps waking up when the screen is facing your body. Couldn't quite find a reason.

Sent from my HTC One
[One (M7) Original Android Development] flar2:
ondemand is more battery friendly. simple ramps up quickly.

I have it in my pocket all the time but I don't pay attention to which way I put it in.

Pocket detection prevents the phone from waking up in your pocket. It doesn't prevent touches from being detected. That would require the proximity sensor to be on all the time.

Basically, when sweep2wake or doubletap2wake are enabled and the screen is off, the touch sensor is asleep but ready to wake up if there is a touch.

If a touch is detected, it only wakes up (the screen is still off, just not in deep sleep) for a split second while the touch is occuring and goes right back to sleep. Literally right back to sleep.

If dt2w is enabled and the touch is a doubletap in the area where doubletap2wake is allowed, or if s2w is enabled and there is a sweep from back button to home button within the proper time window, it will move to the next step.

The next step is to check if the proximity sensor is covered. If it is covered, it goes back to sleep, otherwise the screen turns on.

So if you have thin pocket linings your leg might register as touch events on the screen. Most of my pants have thick enough pocket linings that it doesn't register as a touch. I guess if you have thin pocket linings and notice battery drain, you should face the screen outwards. I can't imagine this would drain too much, at least I've never noticed it.
[One (M7) Original Android Development] carlos67:
Thanks for the detailed explanation Flar. My jean pockets have very thin linings so I guess lots of screen-off wakes being registered and hence higher battery consumption. Guess I'll just have to face phone outwards and just be carefull not to collide with anything. Either that or buy a new set of pants lol.

It's a pity really because without this issue the battery life is stellar just like the performance. With screen against leg after 2 hours battery can drop by as much as 10%:eek: however facing away from leg drops maybe 1-2% in 2 hours.

Apart from this I love your kernel. :good:
[One (M7) Original Android Development] Breki:
Is this real???

In the first post includes: Kernel for Google play edition and Sense-based Roms. I would like to install for Razer Lite Rom

Brekii
[One (M7) Original Android Development] killman2659:
Technically GE is considered Sense ;)

But yes it will work with Razer Lite as it is based off the Google edition :good:
[One (M7) Original Android Development] Breki:
Thanks!
[One (M7) Original Android Development] Tableuraz:
Oh, ok, I though there was a radio in your kernel, dunno why... I will start looking for a rogue app of some sort then...
[One (M7) Original Android Development] Matt:
My benchmarks for this kernel:

If you don't care then don't look, but some people will care (:
[One (M7) Original Android Development] carlos67:
Strange!

Hmm, strange??

Following on from my previous post about wake-ups in pocket due to screen touching leg, I decided to use volume wake/sleep instead (through Venom tweaks) and disable s2w & DT2W so I re-installed elemental 3.2 this time unselecting those options and rebooted. However, even though elemental.conf file shows them as not activated, they are still active :confused: How so? I have even rebooted a second time as recommended by Flar2.

How can sleep to wake/sleep and double tap 2 wake still be working when I un-selected them in kernel installation and also elemental.conf confirms they are un-selected?

Flar, anyone?

Edit: would wiping cache and Dalvik help?

Edit2: Iv'e just noticed that the DT2W is not working (as it shouldn't :)) but the sweep to wake and sweep to sleep IS still working (when it shouldn't be:()
[One (M7) Original Android Development] champofthesun:
Any one having this issue with this: whenever I reboot the phone the volume default to max volume

I'm on ARHD Google Edition 2.0
[One (M7) Original Android Development] gianton:
No such problem here, more of a ROM related bug rather a kernel one.
[One (M7) Original Android Development] los318:
I'm using this ROM and Kernel. No issues at all. Interesting issue though.
[One (M7) Original Android Development] carlos67:
Guys, I figured out my problem with sweep 2 wake/sleep staying enabled when it was disabled in the kernel. I had it enabled also in Venom tweaks Doh. :o:rolleyes:

Now it's disabled I can finally get great battery life even when the thing is hugging my leg like a limpit :D

Volume up to wake/volume down to sleep is a great alternative and doesn't cause wakes when in pocket.
[One (M7) Original Android Development] LiquidSolstice:
The Google Edition ROMs are not AOSP. You can consider them fully unskinned Sense ROMs.

Looks can be deceiving ;)
[One (M7) Original Android Development] daffie:
I have the same issue using ElementalX with VenomViper 1.2.1.
[One (M7) Original Android Development] flar2:
I'm using viper as well.

The volume is independent of the kernel, check your Rom settings.
[One (M7) Original Android Development] wmg316:
I'm on ViperOne, OC to 1890, all wake options turned on (S2W, DT2W, L2W, Volume to wake in Viper Tweaks), 3 email apps with three different email accounts set to push, Facebook sync, Twitter sync, WiFi on 24/7, just everything on! Running Elemental 3.4...and my battery is doing quite well....only second cycle.

I have gotten up to 30 hours with 3 hours screen time on flar2's kernel.

My ROM is "settled", in that it's been about two weeks without flashing anything (except flar2's betas).

Having NO problems with any of the kernels wake options.

And last night during bed time, I had the phone fully charged, and I woke up with 6 hours of the phone being on all night, and it was still at 100%!!

I share this because I just wanted flar2 to see a "positive" post! You do AWESOME work! This is the ONLY kernel for me!

Thanks flar2 fir all you do!
[One (M7) Original Android Development] wmg316:
AND.......

Here is a token of my appreciation!

Confirmation number: 0E28640541923551Y
[One (M7) Original Android Development] jamexman:
Would 3.4 run fine on a 4.1.2 ROM or is definitely for 4.2.2 ROMs only?
[One (M7) Original Android Development] mrwilly:
4.2.2 only
[One (M7) Original Android Development] CheesyNutz:
what is this htc color tweak its new to me
[One (M7) Original Android Development] tyraelasd:
Your beer sir. 3R88930784712872V

You and the team venom are the only kernel and rom I will use from here till I change my device, I promise.
[One (M7) Original Android Development] Luisit0:
HTC made some enhancements to the reds and greens so they look a bit more saturated and vivid, that color tweak removes that saturation so colors look more natural.. that's what flar2 said himself when I asked him a couple of days ago
[One (M7) Original Android Development] CheesyNutz:
thanks for the info

id like to see a screenshot of each :P
[One (M7) Original Android Development] wmg316:
Here is my setup:

CPU @ 1890

Undervolt 850

GPU OC 450

GPU Governor Simple

Thermal: default

Mpdecision: default

Enable L2M

Enable Screen off max frequency

Enable USB Fastcharge

Disable HTC Color Enhancement

Restore 3 dot menu

Enable S2W

Enable DT2W

Enable L2W

Enable Pocket Detection

Stronger Vibration

Home button timeout = 5

Changes in Trickster:

TCP Congestion control: Westwood

Read ahead buffer 2048

Governor control:

* up threshold 40

* up threshold any gpu load 70

* up threshold multi core 60
[One (M7) Original Android Development] c5satellite2:
3.4 has been much better as far as s2w. Everything else is working as expected. Fast smooth and great battery here.

Side note:just updated fw to 2.24 from 2.17(skipped 2.19) and WiFi performance at range is definitely improved.

Thanks again Flar for your awesome work!
[One (M7) Original Android Development] brpqzme:
Just realised the DT2W and S2W don't seem to work if I'm in a dark room. Is this a known issue? :)
[One (M7) Original Android Development] wmg316:
No. Not an issue. I just went into a pitch-black closet and both worked fine.
[One (M7) Original Android Development] eRajesh:
What does DT2W and S2W have to do with a dark room?
[One (M7) Original Android Development] rnrstar:
phone's light sensor. for testing phone wake options.
[One (M7) Original Android Development] c5satellite2:
I have the same problem with pocket detection. Reinstall kernel without pocket detection.
[One (M7) Original Android Development] jlevy73:
Thanks for that, solved my DT2W and S2W not working.
[One (M7) Original Android Development] Stephan_X:
Is this option included into the kernel? Or how did you get volume down to sleep?
[One (M7) Original Android Development] wmg316:
No. Not in kernel. In ViperOne ROM tweaks.
[One (M7) Original Android Development] nickabbott:
Try and install android sensor box from the play store and check your proximity sensor with the flower part of that app. It should shrink and grow with your hand moving over the proximity sensor

If it doesnt then your phone may be faulty or the sensor isn't working for some reason.

Mine works fine in bright and dark light so yours should do too.

Try the lux light sensor test too and see if that's working alright.
[One (M7) Original Android Development] brpqzme:
Tried the app. The flower grows to 9cm with no hand, and to 0cm with my hand right by the sensor. There's no in between values, either 0cm or 9cm. Is that how it's supposed to be?
[One (M7) Original Android Development] old_benj:
Can anyone suggest, if I install this kernel with 1350 MHz, what is happening when I activate power saving mode?

Sent from my HTC One
[One (M7) Original Android Development] nickabbott:
Yeah that's exactly right. If that works fine in bright and dark rooms then I'm not sure why you would have trouble with things unless flar2 implements something with the light sensor as well?

Or you're running an app that might be causing a conflict somewhere.
[One (M7) Original Android Development] gianton:
Power Saver mode is disabled in this kernel.
[One (M7) Original Android Development] old_benj:
So, it is just the icon in this case. Thanks!

Sent from my HTC One
[One (M7) Original Android Development] jacobwind:
Installation problem

I dont know if it got solved, but here is my solution.

I had the same problem. It hung at 0% and never got further.

I deleted the elementalx.conf at etc/ and the 99elementalx at etc/init.d/

Reboot to recovery and install. This worked on my phone.
[One (M7) Original Android Development] CheesyNutz:
I'm running power saver with this new kernel is it really needed with the new battery saving tweak

Sent from my METAL PHONE not some plastic phone bloated phone
[One (M7) Original Android Development] cpufrost:
Great kernel. This is coming from a KT user on S4 btw...

I do like sweep to wake/sweep to sleep and prefer to turn off pocket detection as I use the device in the dark a lot and figured it out pretty fast. No issues with that at all now.

Tried setting ridiculous clocks with performance gov basically battery killer settings (2.05GHz all cores) and got a crazy Quadrant score!

Even my daily driver settings with good battery life net low 13s or high 12s depending on the programs mood. Its flaky if you ask me!
[One (M7) Original Android Development] gianton:
Power saver mode does nothing if enabled, it's disabled in the ramdisk of this kernel. Set the max freq at 1134MHz if you want that's what power saver mode does anyway.
[One (M7) Original Android Development] CheesyNutz:
O.o but its still controls the brightness and data features correct?

Sent from my METAL PHONE not some plastic phone bloated phone
[One (M7) Original Android Development] maverick1103:
Phone locking up

Ok so I'm running Viper 1.2.1 and have been since it came out, I flashed the 2.2 EX kernel almost 2 weeks ago and have been running the 3.4 version over the last 2 days....now today my phone has locked up twice, I just unlocked it with the lock button (even though I have s2w enabled) and it just locked up. I have ASOP lockscreen enabled and the screen just wasn't responding, buttons work fine as I held power down and I did a reboot, upon reboot it was fine. My phone did lock up a few weeks ago only once but I put that down to a one off....is anyone else having problems?

Is there anything you need off me info wise?

Thanks
[One (M7) Original Android Development] carlos67:
Is 3.4 as snappy and smooth as 3.2? I know the simple GPU was tweaked to be a little less aggressive in 3.4 and just wondering if anyone who has used both kernels has noticed any performance hit?

Need to know before upgrading to 3.4 but don't wanna lose any of the butteryness from 3.2 even if it squeezes a tiny bit more from the battery.

Smoothness and being lag/stutter free are my top priority.
[One (M7) Original Android Development] Ardmanz:
I installed this yesterday an all is great with it (logo to wake is very useful to me)!

If I use the default settings in aroma installer will I still benefit from battery savings? If not, what are the recommended settings while still keeping a decent speed?
[One (M7) Original Android Development] jlevy73:
All works properly so not a faulty sensor. Not sure why removing pocket detection works (except for guesses on my part as to how pocket detection works), but once removed DT2W and S2W work.
[One (M7) Original Android Development] SleemLDJ:
While using this kernel, which is superb btw, I like to conserve full battery when I'm outta the house.

Is it allowed or okay if I combine by turning on the "power saver" inbuilt with HTC as well.

Will there be any clashes?

Edit: I should also mention that I use the fauxclock kernel app and in the SoC control, I have C0, C1, C2 and C3 all on.
[One (M7) Original Android Development] flar2:
I feel like there must be hardware variations. Mine has always worked in the dark or light, never an issue. I also don't have that thing where the screen stays off after calls.

It will do all the same things as normal except it won't reduce the cpu frequency to 1134.

Not disabled, just doesn't reduce the frequency to 1134.

Yes

I don't know how much of a difference it makes, I haven't tested it. It just sets mpdecision to be less aggressive at bringing cores online.

That's not the cause of the installer hanging. It just happens randomly. The solution is simply to restart recovery and install again.

Without those files your settings will not work. It's very important to have those files. For example, if you overclock the GPU and don't have those files your GPU will always run at 200MHz.

The kernel is 100% rock stable. You need to do a full wipe or install with less overclock/undervolt

It should be just as smooth, possibly smoother.

The default settings in the installer are my recommended settings. They should give you good battery life, if you want better battery life you'll have to experiment to find the settings that work best with your phone.
[One (M7) Original Android Development] gianton:
Not important to mention, but you're right.
[One (M7) Original Android Development] jacobwind:
You might be right about the install problem.

I tried to install the 2.4 kernel 3 times and the 3.4 kernel 3 times with no luck. Then deleting those files and installing the kernel worked. The files are installed with the kernel i belive? im fully aware that those files are needed.

Just wanted to help.
[One (M7) Original Android Development] Sneakyghost:
I think my battery issues must either be 3g related or the phone just needs a few cycles before it settles.

I had poor battery yesterday when at work with constant switching between bad 2G and bad 3G and bad Wi-Fi. Today I'm home with good Wi-Fi and the phone send to run a lot longer than yesterday. I rebooted it before beginning to charge it last night.

I've now got 15 hours out of it with 2 screen on hours and am at 50%.

Mobile post
[One (M7) Original Android Development] maverick1103:
I've not overclocked or undervolted, everything is as default...I will try restore and see what happens...I did just read that someone had the same problem in the Viper thread and it was after a call he said it was to do with the proximity sensor fix that is in venom tweaks, I've unticked it and will see how my phone performs as mine also locked up after a call.
[One (M7) Original Android Development] Grand_Goblin:
I think it's already described on the 1st post (see the pic attached by OP) that powersaver mode only exist in bulletproof kernel, which is in this kernel powersaver mode doesn't effect the cpu speed
[One (M7) Original Android Development] brpqzme:
Cool, I'll try it out like that. Thanks a lot for the help :)
[One (M7) Original Android Development] Reiki13:
Hello,

I know it was already mention but I still think that a patch would be welcome Callrecording :angel: even if it is flashed to separate :p

I know Incall recorder works ... but the audio quality is disgusting! :eek:

Enjoy :fingers-crossed:

Bêta 3.4 work great for moment, i use in 1,5Ghz and power saver :)
[One (M7) Original Android Development] bldysurgeon:
HI [MENTION=298610]Flar[/MENTION]2.

congradulation for getting the new vergins into signed vergins'i flashed this kernel today and would probably try the bulletproof latter.i like you kernels and will keep supporting your works.

just you have to tell team venum to update them the the venum hub.

is it possible to compyle it to HTC one x????

you welcome

---------- Post added at 01:35 AM ---------- Previous post was at 01:33 AM ----------

+1
[One (M7) Original Android Development] zopostyle:
Camera not working with android 4.1.2 - 1.29.1540.17 CID: BS_US001

We still got no updated...anyone knows how can we enable S2W ?
[One (M7) Original Android Development] dgtiii:
Why not just update to a custom 4.2 rom and the newest (3.4) version of this kernel? No camera problems then like there are on 4.1.2 and custom kernels. Just a thought...
[One (M7) Original Android Development] zopostyle:
I thought about that.. but I realized that the update also update the hboot to different versions.. So i'm afraid that in the future I may have some problens having different hboot and official htc roms for my hardware...

Even my PN is different... I changed my cid and mid once..everything seemed to work..but I'm afraid :( .. lol
[One (M7) Original Android Development] mrwilly:
hboot does not get updated from flashing a 4.2.2 Rom, it only updates if you decide to update the firmware
[One (M7) Original Android Development] bldysurgeon:
better to consult [MENTION=4684315]flar2[/MENTION] 1st. kernels are too complicated to play with.
[One (M7) Original Android Development] flar2:
Seriously guys, don't do that. It does not solve that problem and v will cause much bigger problems.
[One (M7) Original Android Development] zopostyle:
I know, I didn't say about flashing a 4.2.2 rom but getting oficial OTA..
[One (M7) Original Android Development] bldysurgeon:
im terribly sorry. at 1st i thought it was a sort of cleaning resedual files at the phone. after all you r the expert.

you welcome
[One (M7) Original Android Development] Shadow Samurai:
I used to run 4.1.2 before I upgraded to 4.2.2 two days ago and had no problems whatsoever with the older kernel. The guy did something wrong.

Sent from the one and only HTC One
[One (M7) Original Android Development] zopostyle:
I'm running a diferent base..it's just that...

Maybe a repack can make it work?
[One (M7) Original Android Development] Luisit0:
I believe u had to take out a file that said something about "lib" and "camera" before flashing the kernel... or flash a fix someone posted on one of the kernel threads, I don't remember if it was flar2's or tbalden's.
[One (M7) Original Android Development] c5satellite2:
Some 4.1.2 roms require a camera file to be deleted. Flar has posted this fix several times in this thread. Search for it, it is here.
[One (M7) Original Android Development] Hussainally:
Guys what governor do I choose to have efficient battery usage? I am using on demand with mpdecision on but all my cores are online and doesn't go off on low usage ..please advice..tks
[One (M7) Original Android Development] bpdev:
[MENTION=4684315]flar2[/MENTION] Would it be possible to incorporate the pocket detection into the button light notification feature to conserve battery?
[One (M7) Original Android Development] flipmatthew:
Is there anyway to change MHL back to 1920x1080@30hz? On this or bulletproof kernel?
[One (M7) Original Android Development] SleemLDJ:
Lil help guys. Using fauxclock kernel apps, does this setting have any effect on elememtalx kernel?

Does it have the features built in? Any performance changes?

Thanks.
[One (M7) Original Android Development] flar2:
If the cores aren't going off there is something wrong, check that mpdecision is running and that apps like Trickstermod or Kernel Tuner haven't put them online.

I don't think so, it doesn't drain much anyway.

No, but I was going to see if I could make that an option, just forgot. Next version.

I think the first one is like doing "sync && echo 1 > /proc/sys/vm/drop_caches" and should be harmless

Second setting looks like it's part of faux's dynamic fsync. Back in the old days of linux and slow hard drives, disabling fsync was a common performance tweak. I used to disable fsync in my kernels, but there is no performance gain and you could lose data if your phone crashes.

Swappiness doesn't apply to ElementalX, because there is no swap (not necessary on a phone with 2GB of RAM)

The last three can be tweaked, but I suggest leaving them alone because you could actually make performance worse.
[One (M7) Original Android Development] kosique:
I tried the 3.4 version two times now with the same settings as the 3.3 and any prior version. The phone gets really hot with 3.4. Does anyone else experience this?

I always dirty flashed over the prior version on ARHD 12.1.
[One (M7) Original Android Development] Luisit0:
for me it only gets hot when im playing intense games or using data on a warm room
[One (M7) Original Android Development] kosique:
Mine is getting hot even just viewing the home screen. It's about 54 degrees, the 3.3 version is about 37 degrees typing this text...

Weird.

Looking forward to what the stable version of the 3.3 successor will be...
[One (M7) Original Android Development] MrKudinGTO:
For me, FB'ing, internet browsing, Instagram, musics, and the CPU temp itself just around 37-43°C... Not more than that unless I do heavy task like gaming etc. I'm on ARHD 12.1 w/ ElementalX 3.4 too.

Sent via my HTC One™ using XDA Premium
[One (M7) Original Android Development] FangorX:
Could someone who knows more than me please tell me what this last_kmsg means? I pasted the relevant part here.

Also anyone know why it shows these lines at boot even though my device is supercid?

androidboot.cid=TELUS001
androidboot.devicerev=3
androidboot.batt_poweron=good_battery
androidboot.carrier=TELUS