yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] randykzc:
10.3 works really good..when i played fifa 14 i didnt have my micro stutters..

it wasnt a serious micro stutters before that...just that u will feel its not so smooth..

but now with 10.3, things have never been smoother..

just my own observation on my phone..
[One (M7) Original Android Development] Magpir:
yr link is not working.......
[One (M7) Original Android Development] Etshooter:
AROMA INSTALLER version 2.70B6

(c) 2013 by amarullz xda-developers

ROM Name : ElementalX

ROM Version : 10.3

ROM Author : flar2

Device : HTC One

Start at : Sat Dec 7 21:15:32 2013

Installing ElementalX...

about to run program [/sbin/busybox] with 3 args

Wiping /cache

Creating filesystem with parameters:

Size: 671084544

Block size: 4096

Blocks per group: 32768

Inodes per group: 8192

Inode size: 256

Journal blocks: 2559

Label:

Blocks: 163839

Block groups: 5

Reserved block group size: 0

Created filesystem with 11/40960 inodes and 5137/163839 blocks

Max CPU0 freq 1890MHz

Undervolting to 800mV

GPU overclock to 410MHz

run extra cool

mpdecision default

BLN enabled

Max screen off frequency enabled

fsync enabled

Logo2Wake enabled

script aborted: file_getprop: failed to stat "/tmp/aroma/vibrate.prop": No such file or directory

file_getprop: failed to stat "/tmp/aroma/vibrate.prop": No such file or directory

Installer Error (Status 7)

End at : Sat Dec 7 21:15:34 2013

---------- Post added at 09:15 PM ---------- Previous post was at 08:50 PM ----------

Not selecting a wake option worked thank you.
[One (M7) Original Android Development] iElvis:
Aroma crashed when I got done flashing 10.3, and my capacitive buttons were dead when I when booted up. Reflashing fixed it. Looks like the button issue may be related to Aroma.
[One (M7) Original Android Development] flar2:
That's an installer bug, thanks for posting the log.
[One (M7) Original Android Development] nukeman239:
Do I need to clean flash the kernel again if I want to change settings or will a dirty flash do?
[One (M7) Original Android Development] Thijssie909:
I have simular problem on GPE, but in my case I think it's because DT2W is on the whole screen and accidentally activates when on a call. Because the phone also vibrates when this happens. I guess I prefer DT2W only on the bottom of the screen.
[One (M7) Original Android Development] alandd86:
I did s dirty flash and its good ;)
[One (M7) Original Android Development] nukeman239:
Any other way to change kernel settings without flashing anything?
[One (M7) Original Android Development] alandd86:
i personally tried to use trickster mod but whenever i change something it reverts back after reboot ,, so reflash the kernel is better :good::good:
[One (M7) Original Android Development] sweetnsour:
Have you tried enabling the "set on boot" option? Slide from the right in the app and you will find it.
[One (M7) Original Android Development] eyosen:
You can edit the conf file and reboot. Look to OP for location and instructions
[One (M7) Original Android Development] alandd86:
yes i did that but still the same !
[One (M7) Original Android Development] FitAmp:
Hey flar otg doesn't seem to be working for me. I have a generic otg cable which has worked on my nexus 7 and I have tried using 2 usb flash drives both formatted to fat32. Tried to use stickmount as well and it didn't work either

On KK sense 5.5 with elementalx 10.3 btw. Last_kmsg in link below

http://www.mediafire.com/?o7tpsaykfkd29oc
[One (M7) Original Android Development] xfish:
10.x is meant for 4.4 based Roms, stay with 8.1.

The error should be due to hboot 1.56 which you updated to with the firmware. Downgrade to 1.55 should help.

Have a look at post #7203 and the days before, around 1.December, when this error popped up.

Flar, please take care, doesn't makes sense that the stormy ocean of updating is affecting your lustzone and playing with your health maybe, even though top-notch.
[One (M7) Original Android Development] peri25:
when the display is off and I want to do it on, then the always takes a while until it goes on, can i speed this up?
[One (M7) Original Android Development] Nekromantik:
yup that link is broken
[One (M7) Original Android Development] jerrylzy:
I guess there are some heavy loaded apps running at background. even though flar capped max clock at 1134, its performance should be very sufficient.

my suggestion is, download wakelock detector and see what app(s) is/are eating ur cpu.

if that issue still bothers u, u should try reinstalling the kernel and unselect the box of screen off max frequency, and choose ''stock'' when it comes to choosing voltages.

or add this line to /system/etc/init.d/99elementalx

echo 1566000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq;

Anyway, I don't think this is a kernel issue.
[One (M7) Original Android Development] flar2:
This one is experimental. I returned to the kitkat ondemand governor, but modified gboost to use an algorithm from the older version of ondemand and lower up_threshold for better gaming performance. Basically this is a hybrid of HTC's kitkat and jelly bean ondemand governors. When gboost is disabled it's the same as stock kitkat, when gboost is enabled, it works more like the jelly bean ondemand while gaming. The effect will be stronger if the simple GPU governor is used, because gboost kicks in when the max GPU frequency is used.

Download:

ElementalX-m7-10.4 *BETA*

Changes:

-gboost enables hybrid ondemand

-fix installer
[One (M7) Original Android Development] coelhooliveirar:
Does anybody know how to avoid the virtual buttons in some apps?

I get a black bar with home and back button like the Nexus bar and I don't know why it appears in some apps.
[One (M7) Original Android Development] Denpech:
yr link is not working :confused:
[One (M7) Original Android Development] metropical:
erase cache FastBoot

I have no choice to Erase cache in Fast boot.

My HBOOT is 1.55.

I'm unlocked and rooted via HTC but not S-Off.

I'd like to install ElementalX, but am a little cautious because I don't find the erase cache choice.

And I assume that the version for me to use: ElementalX-m7-5.6
[One (M7) Original Android Development] beanbean50:
did you enter usb fastboot

edit:

and use: fastboot erase cache
[One (M7) Original Android Development] metropical:
erase cache FastBoot - for OSX

figured it out.

enter Fastboot USB mode.

in Terminal:

cd Downloads/ One (path in my case, to my One folder)

get - drive name: path - user$

enter - ./fastboot-mac erase cache
[One (M7) Original Android Development] cocinci:
after installing 10.3 i get a boot loop :( im on sense5.5... s-off and everything

never mind!! my bad...its for KIT KAT im so outdated sorry! im still on 4.3 lol
[One (M7) Original Android Development] metropical:
all seems well

s2w works fine.

although long tap logo doesn't.

and remove 3 dot doesn't.

but no big in either case.
[One (M7) Original Android Development] shree.cse:
Your feedback for 10.3 or later?

Logo 2 wake and sleep both working perfectly for me on 10.3
[One (M7) Original Android Development] metropical:
no. 5.6 as the sig indicates.

I'm on the stock 4.3 ROM. Perhaps that's the issue?

l2w doesn't work with stock?
[One (M7) Original Android Development] jonas2295:
Settings max frequency via faux clock or trickster mod is still not working here using latest 10.4 beta :(

Renovated.
[One (M7) Original Android Development] flar2:
L2w works the same on every version. It needs a pre touch before it will wake.

It might work if you disable pnpmgr. I've always intended the max freq to be set in aroma.

Pnpmgr, mpdecision and ondemand all manipulate the frequencies

The good news is power saver is working again, so I suggest setting your desired max in aroma and using power saver when you want it lower.
[One (M7) Original Android Development] faisaldante:
It works perfect using axis project rom, working good and im using the gaming boost on it.
[One (M7) Original Android Development] hamdir:
Sweet did you get the chance to expose the hidden parameters?
[One (M7) Original Android Development] flar2:
They had no effect and I didn't end up using then at all
[One (M7) Original Android Development] randykzc:
can ask 1 question?

i read in the op that GPU is using the same voltage even we overclocked it..

is it also the same with frequency going higher to 491 and above?
[One (M7) Original Android Development] xmegapixelx:
since 10.0 there is some problem with double tap home 2 recent apps. I see that some other people had that issue too. I've been doing some testing and it seems that logo2menu breaks it. everything else is working fine. although every second time flashing kernel after pressing "finish" button black screen comes on and after reboot capacitive buttons don't work at all, at least reinstallation helps. Other than that everything is good, great work as always ;)
[One (M7) Original Android Development] flar2:
I sincerely don't understand the problem with double tap home for recent apps not working.

I always install logo2menu and double tapping home brings up recent apps just fine. I've never had a problem with it. I'm using InsertCoin right now.

Is this just a problem with certain ROMs? Are you guys changing some setting with the buttons? Or perhaps the ROM has modified options for the buttons?

In any case, the button functions actually have nothing to do with the kernel itself. For logo2menu to work, there is one change to the system: the menu button has to be added to a key layout file. This is what would be causing the problem. Although, as I said, it does not cause any problems for me.
[One (M7) Original Android Development] Johnny424:
Those are two features I have to use. Double tap recents and logo2menu..I haven't had an issue with either one though , sense jumping over to 4.4. I have seen the black screen after flashing though. Pretty sure it's a recovery issue though, only because I seen it after flashing roms to as well
[One (M7) Original Android Development] xmegapixelx:
I'm using ARHD 40.3 right now. I've always used ARHD with your kernels (with l2m) and never had any problem. From what I know, ARHD has stock options for the buttons. But if it works with other ROMs, then I guess this issue is related to ARHD on 4.4. Currently I'm running 10.4 without l2m and using long press home button 2 menu, so that's not a big deal :)
[One (M7) Original Android Development] metropical:
L2w

tried the pre touch, still nada. But as I said, as long as s2w works, I'm quite happy.
[One (M7) Original Android Development] iElvis:
If you're having issues with your capacitive buttons, including logo functions, try reflashing the kernel. It solved my problems.
[One (M7) Original Android Development] blast0id:
also, don't forget the second reboot!
[One (M7) Original Android Development] GelullaBarr:
I had problem with double tap home for recent apps too, reflashing kernel didn't solve the problem, only after reflashing ROM and then it was ok. I don't know what cause the problem, maybe because I lowered the max freq off screen to 702Mhz, not 1134Mhz...
[One (M7) Original Android Development] Artc0re:
If i try to Flash 10.3 it 10.4 beta i get an error in Aroma that some prop is Not in the Aroma folder ans the installation is abored anyone know why?
[One (M7) Original Android Development] Ktan188:
Try reflashing it. If that doesn't work redownload the file and flash it again
[One (M7) Original Android Development] synt3k:
I am running 9.0 on the stock 4.4 GPE ROM on a Developer Edition that has been converted completely to GPE.

I've tried to install 9.0.1, but Aroma will stall at 0%, even after fastboot erase cache and reflashing my recovery (TWRP 2.6.3.4) even after numerous tries. Regardless, from what I can tell, there is nothing different in 9.0.1 from 9.0 aside from a small change to Aroma.

Is it possible to run 10.3, and if so, what are the disadvantages vs 9.0.1-GPE?

How do I set the CPU/GPU freq aside from Aroma? Running 99elementalx as root gives me this:

root@m7:/etc/init.d # ./99elementalx
./99elementalx[14]: can't create /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq: No such file or directory
./99elementalx[15]: can't create /sys/devices/system/cpu/cpu2/cpufreq/scaling_min_freq: No such file or directory
./99elementalx[16]: can't create /sys/devices/system/cpu/cpu3/cpufreq/scaling_min_freq: No such file or directory
./99elementalx[24]: can't create /sys/devices/system/cpu/cpufreq/intellidemand/powersave_bias: No such file or directory
0 Bytes was trimmed
0 Bytes was trimmed

./99elementalx[135]: can't create /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk: Permission denied
./99elementalx[163]: can't create /sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk: Permission denied

After making my changes to the config file. Usually I get more errors, but that's the output I just got. I'm new to the GPE ROMs and would prefer to use what I know (TricksterMod) but this seemed easy enough.

It just seems like all of the nodes are not being created in sysfs.
[One (M7) Original Android Development] kinetx:
[MENTION=4684315]flar2[/MENTION] - are there any ElementalX settings you are aware of which could cause my screen to go to sleep when connected via HDMI? I have Daydream turned off also.
[One (M7) Original Android Development] fcjan:
I think most of the problems related with capacitive buttons is because you guys didn't reboot after phone booted first time after installing.. I never had any problems on ARHD 40.2
[One (M7) Original Android Development] la041212:
If find dt2wake does not work

You can open TV

and you would find it work

This problem have occured since update to Android 4.3
[One (M7) Original Android Development] nukeman239:
What kind of a battery hit can we expect with the Simple GPU governor?
[One (M7) Original Android Development] flar2:
You can use it on stock, you probably have to remove /system/lib/oemcamera.so and /system/etc/firmware from the installer zip before you flash it or your camera won't work.
[One (M7) Original Android Development] nickabbott:
I'm not sure if you mean something behind the scenes or the bit where you hold the button and the screen turns on while holding the button.

Then reverting it back to where you hold the button, remove your finger and then the screen turns on?

I think the way it is now is best, if it can be fixed or improved to work more consistently? Because with this way you know if it hasn't worked when the screen doesn't turn on! But if the other method works a lot better then it's a difficult decision.

I don't know if it's just me but sweep2wake seems to be much more consistent to work than any other methods. Maybe there's something different in the coding, different buffer times or longer check times to see if the buttons are still being pressed? Sorry just guessing here, might be completely off!
[One (M7) Original Android Development] B-Man2005:
flar you got a pm
[One (M7) Original Android Development] nickabbott:
Really wish I had more time to investigate this.

Looking at the source sweep2wake is an extern void which is called in other modules or classes. Yet the other methods are set to static I think and are only called within the synapyics file.

Not sure how it all ties together and stuff but if anyone else can confirm sweep2wake works better than other methods from deep sleep etc it might be a starting point to look how sweep2wake differs from the other methods.

Maybe these methods are extern for debugging reasons or something I'm not sure of but hopefully people who know what they're doing might have inspiration from my ramblings!!
[One (M7) Original Android Development] Flow-Wolf:
Thanks flar2 :D

I unzip the file, remove the files and the rezip it with uzip? and that's done? :)
[One (M7) Original Android Development] D_Magic:
I swapped my gs4 for a HTC one and am happy I did, this phone is better in every way except for one thing, this phone charges so slow. The gs4 goes from 1 to 100% in 1 hour and 50 minutes and has an 2600mah battery...the HTC one takes 3 hours and 20 minutes to get to 100% and has 2300mah...especially that last 15% takes a long time to charge.

Any plans on enabling a fast charge for wall charging in the future?
[One (M7) Original Android Development] godofwar424:
That's not right, install Gsam battery monitor and see if one app is hogging your phone. For me Facebook 3.0 and later causes constant cpu usage making the phone warm all the time and making it takes ages to charge. Once I uninstalled and went to Facebook 2.2 the phone charges up now within 2 hours from empty
[One (M7) Original Android Development] D_Magic:
That's not right, I don't have facebook and tested it with stock Rom and no apps installed...it takes 3 hours and 20 minutes. With arhd or trickdroid...stock kernel or this kernel or other kernel...with and without apps installed...it takes 3 hours and 20 minutes.

From 0 to 85% it's ok and takes a little more then 2 hours.. that last 15% takes ages.

And I have gsam and great battery life, I get 24 hours with around 7 hours screen on time so no apps that drain my battery

Even whit the phone turned off it takes more then 3 hours!
[One (M7) Original Android Development] godofwar424:
Thats strange, it should charge slightly faster with the phone on if I recall correctly.

But what charge are you using? I am using an old Nokia 1200mAh charger and it charges quick enough for me :s
[One (M7) Original Android Development] D_Magic:
When phone is off it takes 3 hours and 10 minutes...whit phone on it takes 3 hours and 20 minutes

I use the htc charger that came with the phone witch is a 1a charger.

I also tried it yesterday with my girlfriend's gs4 charger witch is a 2a charger and it's recognized as a ac-charger but it charges at the same rate as the 1a charger from HTC.
[One (M7) Original Android Development] godofwar424:
Thats a weird one, I do remember the first few days being painfully slow to charge, but then after a few days it seemed much quicker.

Not sure, maybe give it a few more charge cycles and see how it goes?
[One (M7) Original Android Development] aber82:
normal behave.

htc decidet to charge slow to get the longest batterylife over the whole phone lifetime.

kernel devs will not include faster charge on wallcharger , cause of less betterylife.

thats ok.

and charging time over three houres is normal.
[One (M7) Original Android Development] D_Magic:
Uhm I have this phone for 2 weeks now and charged it more then 14 times.

The only way to get a faster charging rate is when a kernel dev enables it...like is already done with the usb-fast charge
[One (M7) Original Android Development] godofwar424:
Fast charge doesn't actually work yet. Also the QuickCharge by Qualcomm won't be implemented by devs due to HTC legitimately disabling it to prolong battery life. I am sure one dev eventually might do it, but I don't think it will be anytime soon.
[One (M7) Original Android Development] D_Magic:
I know that already, that's why I am asking the kernel dev if he's planning on doing that in the future.

If not, well then there is one thing the gs4 beats the htc one with :eek:
[One (M7) Original Android Development] godofwar424:
This very question was asked awhile ago, when this kernel was initially released, but the dev said its not important as of yet also he was unsure due to HTC deliberately disabling it.
[One (M7) Original Android Development] D_Magic:
They probably disabled it cause it's a non replaceable battery so people who use this phone for 2 years or longer it should help a little.

I'm not using a phone for years, I change to a new phone in 6 to 12 months and I'm sure I'm not alone so for me it would be great if the fast charge would be enabled cause more then 3 hours is insane, my Note 2 charges way faster then that lol...so that's the reason I asked the dev.

I'll just keep hoping someone will activate it :)
[One (M7) Original Android Development] godofwar424:
Im certain somebody will enable it :) Maybe a patch and then it can be implemented into any kernel as an option at install. Not sure how long it will take though. Who knows, HTC might enable it themselves :p
[One (M7) Original Android Development] jerrylzy:
Nice scores:D

1890mhz cpu+450mhz gpu+row
[One (M7) Original Android Development] Nekromantik:
woah!

fully charged me phone and unplugged it before bed.

10 hours later I wake up to find battery down to 90%!

Checked better battery stats and it shows deep sleep for 10 hours.

Im using max screen off default, max cpu 1.5ghz and intellidemand.
[One (M7) Original Android Development] vizzy:
This is myself every day lol.
[One (M7) Original Android Development] jonas2295:
Ah thanks for the heads up regarding working power saver! Will use it to lower the max frequency :)

Renovated.
[One (M7) Original Android Development] Mikanoshi:
And what else does it show? What consumes battery? Radio I guess. I get such drain only if a lot of sms come in during the night.

Deep sleep should be not more than 1% in 7 hours, even with overclocked CPU and ondemand governor, but screen off freq should be limited (for me it's 702MHz).
[One (M7) Original Android Development] flar2:
It has nothing to do with the max screen off frequency

reflashing the ROM is a good idea if doubletap home doesn't work anymore.

You could try a dirty flash of your ROM, or nandroid backup of /system and restore it to fix installation stuck.

Don't use 10.x on GPE edition ROMs because it will have the wrong ramdisk.

Those nodes in sysfs only exist when the core is online, those errors are normal and those lines aren't strictly necessary.

The max_gpuclk permission denied is because permissions have to be restricted when overclocking the gpu, otherwise pnpmgr will change it to 200 max.
[One (M7) Original Android Development] Nekromantik:
I had no SMS during the night.

I didnt check the wakelocks as deep sleep was showing it was not waking up often.
[One (M7) Original Android Development] hamdir:
guys guys stop asking how to change the clock frequency there is only one way with stock pnpmanager

you need to enable powersaver to change it! and then lock it after that

echo 1 > /sys/power/powersave
chmod 666 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1566000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
chmod 444 /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 0 > /sys/power/powersave

but this will lock only the maincore, it is harder for the other three cores

the last line is optional, if you leave power saver on, the other three cores will continue locked at 1134mhz, if you echo 0 to disable powersaver, the maincore will stay locked but the other three cores will go back to the max clock you have set in AROMA

---------- Post added at 05:11 PM ---------- Previous post was at 04:13 PM ----------

the way the new governor works is super weird, i tried every parameter exposed and no go

I understand nailing the smoothness of the UI further (very noticeable in the notification quick settings area) but what really boils my blood is the constant gaming performance regression in Android flagships (which is already bad in previous stock governor) thanks to software updates, i mean really this the area where iOS will forever rule

the only excuse is the possible drive for better multicore usage, in that case its a shared blame with game devs, still still i mean HTC's beta testers what games do they test on? angry birds! (high end gaming is an advertised feature of the One series, not to mention HTC's presence in the last GDC to promoted ES3.0 usage on the M7)

sorry for the rant, but i have been chasing game performance for two years now with HTC Flagships and this is not the first time that they even break our root gaming boost fixes (the One X JB update broke ondemand governor boost as well) at this point im starting to believe in your theory do they actively counter our efforts? :rolleyes:

anyway i have been very happy with 10.3, old governor and my previous scripts, after the ROM settles well the JB governor is equally smooth

on to testing your 10.4 concept, im guessing it will not longer need boost just a script to switch to simple governor plus higher GPU clocks on the fly, i will report back about actual gaming