yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] jelmer-p:
Works flawless on ARHD 71.1.

The wake-up gestures too, but something with pocket detection is not working, it wakes up all the time in my pocket today I called my boss 5 times $ my sister 2 and my and a friend I have no contact with for a long time until today $$$

Verstuurd vanaf mijn HTC One met Tapatalk

---------- Post added at 01:30 PM ---------- Previous post was at 01:29 PM ----------

Maybe it's because I use Lux to monitor the brightness?

Verstuurd vanaf mijn HTC One met Tapatalk
[One (M7) Original Android Development] mrwilly:
I use Lux also and have no issues with mines waking up in my pocket on ARHD 71
[One (M7) Original Android Development] kami2k:
can u please tell me how many / which type of gestures available with this kernel?
[One (M7) Original Android Development] descenpet:
4 direction swipes, double tap and logo long press so 6
[One (M7) Original Android Development] kami2k:
in air swipes or with touching?
[One (M7) Original Android Development] descenpet:
Touch
[One (M7) Original Android Development] Mikanoshi:
Available actions:

http://sensetoolbox.com/6/modslist#wakegestures
[One (M7) Original Android Development] arooni:
Hey everyone:

HTC One M7 (AT&T variant). Unlocked bootloader & s-off. TWRP 2.7.0.0. HBoot 1.44.

I had Maximus 30.00 ROM on my phone up until last night. Then I downloaded Whats app plus on a questionable site application; it looked like it was taking forever to finish; so I went ahead and restarted the phone. That was a bad mistake.

The phone started boot looping. I tried in vane to reinstall the same ROM and then whatever ROM. It turned out the /data/ partition was corrupted. So I reformatted it with mkfs4 thanks to these instructions. Then I was able to install Maximus 40.00 and got the phone unbricked (yay). But I found two problems:

1) The phone battery wouldn't charge past 77%... nor did it seem to discharge.

2) The phone battery wouldn't charge when I first turned the phone off. The amber LED light would just hold constant.

I tried running that ROM with elementx kernel with no results. So I installed the latest version of this ROM (Android Revolution 71.0) with a full wipe of everything. /data/system/cache/dalvik cache etc. Still had both problems.

Then I tried installing ElementX kernel (with the fast charging option checked) with this ROM which led to the second problem going away. However the first problem still exists. I also tried clearing battery stats with no effect. Also tried doing a fastboot erase cache with no effect.

I'm not sure if the battery is really at 77%; but I have turned off the phone and am watching it charge with the same charger I've always had that charged it to 100% before... but its been going for 15-20 minutes without going up one percentage. It also doesn't seem to drop at all.

Any idea how I can try to get rid of this quite annoying problem? Thanks very much in advance! I would be happy to provide any additional information you might need.
[One (M7) Original Android Development] iElvis:
Sounds like that cracked app you downloaded may have included something nasty in addition. I would do a full RUU back to stock and start over.
[One (M7) Original Android Development] shpitz461:
arooni, did you try to flash an RUU and get back to stock? Maybe that will clean all your issues...
[One (M7) Original Android Development] CamoGeko:
Never had issues with WhatsApp+ on any of my devices.

Doubt its that.
[One (M7) Original Android Development] iElvis:
As he said, he downloaded it from a "questionable site."
[One (M7) Original Android Development] sohojmanush:
thats normal...what i was saying that in my case it gets warmer when it was in my pocket doing nothing.
[One (M7) Original Android Development] Legitkrillin:
Thanks a Million!

Just updated to the latest kernel excellent work guys!!! Flashed with no hassles thanks a million and keep up the grate work!
[One (M7) Original Android Development] olvrick:
everything fine here also
[One (M7) Original Android Development] syanide:
Havent been able to get the wake up gestures to work in ARHD 71.1. Did a full wipe, installed ARHD, then when everything was up and running, flashed ElementalX. Have tried reflashing EX a few times to see if it makes a difference but no dice. Wake up gestures are turned on in Sense Toolbox and I have tried changing them and rebooting but they still wont work.

Any idea what I'm doing wrong?
[One (M7) Original Android Development] flar2:
clear sense toolbox data, uninstall it, reboot, and reinstall the toolbox
[One (M7) Original Android Development] KOJANHQ:
flar2, can you add /sys/android_camera_awb_cal/awb_cal replacing feature to you kernel (More info here: http://xdaforums.com/showpost.php?p=52615200&postcount=4510)? I think it somewhere in https://github.com/flar2/m7-Sense/blob/ElementalX/arch/arm/mach-msm/htc_awb_cal.c file, but I don't know how to read file as need object.

Thanks advance!​
[One (M7) Original Android Development] Mikanoshi:
Sense 6 Toolbox 1.2.5

Has some fixes for Wake Gestures. Download links are in the Toolbox thread OP.
[One (M7) Original Android Development] Nikos2k:
how to disable the haptic feedback of S2S?
[One (M7) Original Android Development] chickentuna:
Using your favorite root explorer app, go to /system/etc and open elementalx.conf. Look for the line that says VIB=1 change it to VIB=0
[One (M7) Original Android Development] TAL1962:
install aborted after aroma

Hi,

I'm on ARHD rom 4.4 sense 5.5 .

on flashing with twrp 2.6 I get Aroma with all selections.

on the last screen I click "install" and the flash is aborted > black screen > auto reboot.

I searched the thread and found some solutions, none worked for me:

fix permissions, wipe cash...

what am I missing?
[One (M7) Original Android Development] ibrahimh:
Hi,<br />

I'm on ARHD rom 4.4 sense 5.5 .<br />

on flashing with twrp 2.6 I get Aroma with all selections.<br />

on the last screen I click "install" and the flash is aborted > black screen > auto reboot.<br />

<br />

I searched the thread and found some solutions, none worked for me:<br />

fix permissions, wipe cash...<br />

<br />

what am I missing?<br/>

Make a nandroid

Restore nandroid

Then flash kernel
[One (M7) Original Android Development] ahmedhzaki:
How do I get swipeup2wake to work ? Ever since the sense toolbox integration it hasn't been working for me
[One (M7) Original Android Development] TheUndertaker21:
So, I'm guessing this is not for aosp? We have like a million kernel for sense only rom in the Aosp section smh
[One (M7) Original Android Development] tiny4579:
Correct, it's only sense and GPE.

Off topic:

I've been debating starting a cm11 kernel but I ROM switch too much to want to be dedicated to an AOSP kernel. There are a few outdated ones. I'm sure others are disappointed in lack of AOSP kernels as well but we should continue via pm if you want to talk further.
[One (M7) Original Android Development] iElvis:
This isn't the "AOSP section," it's the Original Development section. That can include Sense kernels if they are built from source, as this one is.
[One (M7) Original Android Development] TheUndertaker21:
Yeah, most AOKP kernels are outdated. Its hard to find a good kernel when I switch ROM,I switched ROM a lot.
[One (M7) Original Android Development] Matze1904:
Had similar issues, stuck at 10% or reboot after reaching 10%. I dirty flashed (new) arhd rom (71.1) and flashed kernel (14.8) afterwards without system reboot.

I dont know why no other solution worked for me but it was the same when I flashed arhd 62.0 and elementalx 14.0.
[One (M7) Original Android Development] tiny4579:
Seems to be a corrupt /system or aroma bug causing the issue. It may be a device related issue with recovery. Since I flash Roms often enough (which wipe /system), I don't run into this.
[One (M7) Original Android Development] Matze1904:
Is there a solution? I have trwp 2.6.3.3 and as far as I can see no other problems after flashing Rom and kernel as mentioned before.
[One (M7) Original Android Development] flar2:
Reflash your Rom

Or do a nandroid backup and restore it

Or mount and unmount / system in recovery (might work)
[One (M7) Original Android Development] Matze1904:
Thanks, I will give it at try when next update is available since everything's working fine right now
[One (M7) Original Android Development] cygnus56:
some tips to improve the battery with this kernel?

the first cycles I have spent 3.5% per hour, and even using all the time battery saving mode, it seems excessive, but I really can not live without wake gestures :fingers-crossed:
[One (M7) Original Android Development] Ktan188:
You can't promote roms here. Each phone is different, and each Rom works differently on each.
[One (M7) Original Android Development] flar2:
Do a full wipe and reinstall.

Doesn't matter what ROM you use, any Sense ROM is fine. Battery should be excellent, if not something is wrong.
[One (M7) Original Android Development] cygnus56:
rectified

---------- Post added at 10:11 PM ---------- Previous post was at 10:07 PM ----------

the problem is that in general it is clear that using gestures wake consume more battery than with a stock kernel, then I want to know some tips to save battery, for example I found a tutorial where "wakelock Terminator" is used to filter Google Play services.

look like.
[One (M7) Original Android Development] fcjan:
use Greenify to hibernate any app you don't use all the time, go to Settings > Location and switch to Battery saving mode if you don't use your GPS that often and also turn off Location Reporting in Google location settings if you don't use that feature, use lowest possible screen brightness (auto brightness option is to bright IMO)..

there is a lot of ways to improve your battery life, explore options
[One (M7) Original Android Development] flar2:
I've tested extensively and there is no drain from the gestures. And battery life should be noticeably better than stock. I don't do any greenify or anything and easily get two days on a charge.

If you're not getting good batter life there is something wrong with your system.
[One (M7) Original Android Development] kshastryp:
True. I only see like 8-10% usage for kernal. Great job [MENTION=4684315]flar2[/MENTION]. Thanks!!
[One (M7) Original Android Development] Jogistyle:
hmmm... i can't install :confused: it stops by 0% and reboot himself.. and nothing will be chanced:rolleyes: i've done a chace wipe on fastboot but it doesn't help for me... how can i fix it ?? i will not do a fullwipe or so
[One (M7) Original Android Development] jerrylzy:
[MENTION=4684315]flar2[/MENTION] I saw your new hack method of system writing protection in M8's kernel which maintains compatibility with htc's texfat. Can we implement that hack on m7 as well, as exfat is not as good as texfat?
[One (M7) Original Android Development] Osama Zabin:
Did you try:

1.Dirty flash your ROM, then kernel again

2. Do nandroid backup and restore it
[One (M7) Original Android Development] flar2:
Two separate issues.

I had to redo the write protection hack on m8 because HTC changed some stuff up in the kernel. The write protection still uses the same method but there is no longer an available function I can call to turn it off. In the new hack, I have to hook a different function and force it to return something else in order to disable the protection. In practice there is no difference, I just had to jump through more hoops to do it.

For exfat, on the m8 it is essential that exfat work because of the removable sdcard, so faux hacked the open source exfat driver to work with HTC's hardcoded mount options. I thought I already added those changes to the m7? Is it not working?
[One (M7) Original Android Development] TheMathMan:
Pocket detection is still flaky here. Have to have it disabled for consistent use.

Kernel 0.11 on ARHD 9.3
[One (M7) Original Android Development] Bonely:
Did some quick benchmarks and cache size settings. Not going to do a write up because I'm too lazy and you should probably do it yourself to find out what works best for your device. But using the default elementalX scheduler (don't know if it matters or not) the sweet spot is either 1024 or 2048. This will improve both the sd card read/write without compromising ram copy (don't know why ram is involved but whatever). Personally I think I will use 1024 because the ram copy was the highest out of all of them with modest gain in the SD read/write.

EDIT: I looked over the numbers again, and I am going to have to think about what settings I'm going to use.
[One (M7) Original Android Development] Aetherhole:
I'm having a weird issue since using the latest version 0.11. Sometimes after turning my on my phone the touch screen stops working. I have to restart the phone but even then it randomly happens again... anyone encounter this same problem?
[One (M7) Original Android Development] tiny4579:
This is an issue with the kernel source that every custom kernel is using. Nothing to do with this particular version of the kernel or the kernel itself.

Nevermind you meant the screen as a whole. I was thinking the button response issues.
[One (M7) Original Android Development] TheMathMan:
Neldar's BLN app says I haven't got the module installed but I definitely selected it in aroma
[One (M7) Original Android Development] Aetherhole:
Yeah it's not the capacitative buttons, it's the screen itself... it only happens with 0.11. On 0.10 it is just fine.
[One (M7) Original Android Development] albatnawy91:
yes, i am having the same problem too, and could you please add hold to wake ? if its possible thanks
[One (M7) Original Android Development] flar2:
Has anyone figured out how to fix the camera on latest AT&T yet?

I don't think that app is compatible with the One.

***************************************************

I think I know how to fix the unresponsive touch screen some people are having (not the button issue, the problem being reported on the latest version). Not sure when the next release will be, I have to travel for work this week. I'll try to have an update next weekend.
[One (M7) Original Android Development] inffy:
Did some testing yesterday considering the bt audio problem. It seems the UV was the culprit on my part. With Stock voltages the audio works fine.

EDIT: Still seems to be a problem now that I tested a little longer, but it's definately much smaller amount of times the music gets scrambled. Will do more testing today.
[One (M7) Original Android Development] Magpir:
anyone have screen on time?
[One (M7) Original Android Development] EnIXmA:
Loving this kernel, very smooth and good battery life
[One (M7) Original Android Development] doraemon6688:
Would help many people if you can share the settings you chose in the kernel installation and what ROM you are running. Thanks.
[One (M7) Original Android Development] c5satellite2:
Have had problems with UV and BT with this phone, HOXL, and Inspire 4g. Nothing new. WiFi and BT get even worse when using both simultaneously. Stock or even overvolting a little makes a difference.

I can run all three phones with the lowest voltage and they are fine until multiple radios are in use and the device is being pushed harder. Just because it seems stable at lower voltages doesn't mean it will run well when it starts being asked to do a lot of work.

I am running at stock voltage currently and OC to 1.9. Still get awesome battery. Had it UV for a few days and the battery was about the same. Might be little or no real benefit to UV.

V=IR is good for describing a single circuit, but really bad when trying to apply to a SoC as a whole.
[One (M7) Original Android Development] dhingra_vinay_in:
when s2w enabled i faced the same problem in bulletproof kernel...just migrated to this kernel today itself to taste some uv n oc..when the touch screen is not responding when power button is used to wake the device up..just swipe the capacitive button for s2w and the touch screen works..try once n lemme know :)
[One (M7) Original Android Development] Thijssie909:
The same here, sweeping brings it back again...
[One (M7) Original Android Development] m0nz:
Flar,

When changing the gpu setting in the /etc/elementalx.conf file, it doesnt seem to take effect on reboot. Kernel tuner still shows 450 in sys info, that is.

Just thought of point that out.
[One (M7) Original Android Development] inffy:
Seems like it. Sound is ok when the phone is on charger but when its not and by is on serving music, the problems start.

Will do some testing on different kernels.

Edit: Seems to happen on other kernels too...damn shame really
[One (M7) Original Android Development] CrazyCypher:
Do I need camera fix on ARHD?

Or I only flash kernel and everything is working ok?
[One (M7) Original Android Development] jaythenut:
Just flash kernel there's a camera fix option in aroma :)
[One (M7) Original Android Development] EnIXmA:
Arhd 9.3 Rom, underclocked at 1.5 ghz max all core, 350 min, undervolted by 75 mv for all frequencies, gpu 450,intellidemand governor, cfq scheduler, power saver on. Battery doctor app, locations on, brightness at 5 % for WiFi, 50% for data
[One (M7) Original Android Development] jerrylzy:
I didn't test the funcionality of exfat, but I saw someone posting in other thread stating that your version of exfat requires some 3rd party apps while faux's version doesn't require those apps. That's why I asked you that question:confused:
[One (M7) Original Android Development] flar2:
That used to be true. I added faux's changes several versions ago. When I tested it, it mounted automatically like stock texfat.
[One (M7) Original Android Development] goingcrazy614:
Any suggestions on TCP congestion governor?

sent from Viporized ElementalX HTC One
[One (M7) Original Android Development] jerrylzy:
the default one of linux is cubic but every dev seems to use westwood.
[One (M7) Original Android Development] cygnus56:
usually few hours with screen on you in a cycle?
[One (M7) Original Android Development] flar2:
3 to 3.5 is about max for me on a cycle. That would take a couple days because I don't often have the screen on for more than 1.5 hours per day.

Lately I've been focused on m8 and Nexus 5, As of this morning, my m7 has just been sitting there for 3 or 4 days and still has 74% left with about 15 minutes of screen time.
[One (M7) Original Android Development] cygnus56:
thanks for the information, I have been giving me 3 or 3 ½ hours per day of screen, there are users who comment that reach 4 ½ hours.

I'll see how these days it behaves
[One (M7) Original Android Development] psycho2k9:
Hmm am I the only one who's lost root? Read through the thread and it seems I've lost root with insertion 3.0 and elmx 14.8 :(

---------- Post added at 04:27 PM ---------- Previous post was at 04:23 PM ----------

Okay.. Nevermind.. It seems to have randomly come back after spending about 10 minutes of reading the thread.. Sorta weird lol nice work again flar2 :)
[One (M7) Original Android Development] rm83855:
Screen flicker

Occasionally my screen will flicker on and off a few times and then a toast notification displays 'Ad'. Im running Google Play Edition Android 4.4.2

ElementalX-m7-11.7 kernel. Anyone experienced this cant find anything about it online?
[One (M7) Original Android Development] donkeykong1:
After flashing 14.8 on ARHD 71.1 my phone gets too hot. CPU temp is always 45℃ and more. I wiped everything and reflashed ROM and kernel again and it's the same. One more thing I noticed that confused me because it shouldn't be kernel related - google services cause a lot wakelocks. After flashing 13.4 all is back to normal, no heating and no google services wakelocks. Any thoughts?
[One (M7) Original Android Development] rbrandser:
14.8 still running smooth here on arhd 71. System is very stable, no weird behavior.

Anyway, I just noticed something interesting, a guy posted a picture of his system information, 1.29.401.12 firmware. His battery had a charge of almost 4.3 volts.

I remember my phone used to charge to 4.3, but somewhere along the road, after a update, it began charging to only 4.0 volts. What part of the firmware/software controls this, and how can we hack it? :)

(σˋ▽ˊ)σ
[One (M7) Original Android Development] Mikanoshi:
adb shell top -m 10 -d 2 | grep -v top

adb shell dumpsys cpuinfo

and Google Services is just crap.
[One (M7) Original Android Development] kazemitsui:
for all you guys who get so much screen on time. it amazes me haha.

i can just about reach 2hrs if im lucky, but i leave everything on except nfc and bluetooth. auto sync is always on unless im on data. but yea. 2+hrs screen on time would be a dream for me :p
[One (M7) Original Android Development] descenpet:
Are you going at full brightness or so? :p
[One (M7) Original Android Development] kazemitsui:
i regulate between the automatic and the first bar lite up from the quick toggles
[One (M7) Original Android Development] DeathAngel66669:
I found a good balance between battery life and performance:

TCP:westwood

Readahead:3072

I/O Scheduler:fiops

[cpu]

Min:384

Max:1890

Off Screen Max:702

Governor: ondemand

[gpu]

Max:450

Governor: ondemand

Undervolted CPU by 62.5, Min:812.5
[One (M7) Original Android Development] khandelwalsiddharth:
What are these commands for ? :)
[One (M7) Original Android Development] donkeykong1:
Log
[One (M7) Original Android Development] Jogistyle:
thank you... i've install the Rom again and before start, i've install the elementalX kernel...and everything is workin fine :good:
[One (M7) Original Android Development] Gerton:
Hey,

I am coming from Bulletproof and I like the features from this kernel.

Why is the phone running hotter, ( standard settings in aroma) as with Bulletproof?
[One (M7) Original Android Development] Mikanoshi:
Well, the cause of Toolbox's Wake gestures not working was found - new input event device for gestures doesn't have the same number on all devices...
[One (M7) Original Android Development] flar2:
By default, EX has less thermal throttling.

Install with the extra cool option if you find it too warm.

Use the handle instead of hard links

/sys/class/input/inputX/name
[One (M7) Original Android Development] Mikanoshi:
and how to find X?) scan all inputX and find the one with wake_gesture name?

all those files are owned by root, bad solution :) system owned will be a lot better

BTW java class doesn't see that new input device
[One (M7) Original Android Development] flar2:
System owned would be a bad thing to do in the kernel, subverting all conventions.

What about getDescriptor ()? This looks like it would find the handle and give you the correct input device.
[One (M7) Original Android Development] Mikanoshi:
Wake gesture device is not visible in that class at all. Available devices are (id, name, descriptor):

-1 Virtual a718a782d34bc767f4689c232d64d527998ea7fd
1 apq8064-tabla-snd-card Headset Jack 9e68f1d70457a01a032dc217c75c6266c8a980f1
2 apq8064-tabla-snd-card Button Jack db07212d213438566449709b3ea207d5e793b808
10 synaptics-rmi-touchscreen 39bd9849898f1573eef8b8858a9b3c6318fa6a79
11 keypad_8960 65a3a5d3cec1963a17956a98f9c8dc45cb088c58
12 rcp_events c50988e5af9987167e785d36aef29f1842852180
13 h2w headset a89f20dc199f264bd848a74e69f59562f0f4df4e

Looks like device should send KEY events to appear there or has some other specific properties.
[One (M7) Original Android Development] flar2:
I think I know what to do. I'll send something to you tonight.
[One (M7) Original Android Development] cygnus56:
someone could tell me that it is the "msm_hsic_host wakelock" is there anyway to block it?

---------- Post added at 09:16 PM ---------- Previous post was at 09:10 PM ----------

Enviado desde mi HTC One mediante Tapatalk
[One (M7) Original Android Development] jmb6420:
It happened to me once right after flashing rom. Rebooted and it's never shown up again. It kind of spooks you when it happens though.
[One (M7) Original Android Development] cygnus56:
actually have two days I've done a completely clean install, maybe it's that.

Yesterday I did 3 1/2 hours of screen, even with wakelock that, and I guess the delete will achieve more.