yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] hamdir:
Awesome changes thanks a lot, love your work man :good:

just we need to put a reminder to everyone complaining of fps dips in games (outside GPU bugs)

always remember quad core CPUs will need boost for certain games
[One (M7) Original Android Development] Hiro Nakamura:
Is the ondemand governor broken in elementalx 4.2 ?
[One (M7) Original Android Development] jerrylzy:
bus oc is inactive in 3.8 it seems?

Is it because bus oc can change some other things related to bus freq which will cause a 487mhz gpu performs like a 400mhz gpu?
[One (M7) Original Android Development] flar2:
There was no option in the installer, I had it set to oc the bus by default. I wanted everyone to take the bus oc, just to see if it was stable on a range of devices.
[One (M7) Original Android Development] flar2:
I have an idea about how to modify the ondemand cpu governor to automatically adjust for gaming. May not come out till next week though. Starting tomorrow I will be out of town for six days.
[One (M7) Original Android Development] skulldreamz:
Hey bro enjoy your time off and I mean that. You do so much for the community, thanks sincerely

Take some awesome photos..lol
[One (M7) Original Android Development] carlos67:
+1. Forget about kernels for a few days dude. You deserve some R&R.

Come back fresh and raring to go in a week or so! We love you man. You've made a huge difference to my mobile experience.
[One (M7) Original Android Development] mwr666:
I don't get it... So why the gpu performance is lower than stock since elemental overclocks the gpu. If ondemand has no diff with stock then what else can be broken? ...when i use faux its same low performance. I even thought my gpu cant handle the OC so i used stock mhz and the performance is lower too

EDIT

... i'm not talking about benchmarks only... i'm talking about games
[One (M7) Original Android Development] flar2:
There is nothing broken, overclocked GPU performance is considerably higher than stock on benchmarks. eg, 46 fps vs. 40 fps on GLXBench and ~6800 vs. ~6100 on Antutu 3D test.
[One (M7) Original Android Development] mwr666:
6800 in antutu? Me and some other users get 5200 or lower. There r some people that confirmed the low gpu performance and there r some that confirmed better performance. Can you tell me what ROM u r using and firmware so i could try ur setup to see if the scores will be close to yours??
[One (M7) Original Android Development] GelullaBarr:
in quadrant 14300. second test 13900, so it is overclocked, maybe he needs to reflash, I did the same, first time I was not satisfied, and now it is excelent.
[One (M7) Original Android Development] flar2:
If you're getting scores that low, it could be that your chip can't handle the oc and it's making errors. Or it may be getting too hot.

I'm on Viper
[One (M7) Original Android Development] mwr666:
i was talking about it earlier. i thought same and lowered mhz to 400 and still got lower performance than stock. yesterday i've tested trips kernel and i've got 6900 gpu score in antutu so the problem isn't in my chip

edit

got low performance gpu only with ur kernel and latest faux
[One (M7) Original Android Development] iElvis:
I would bet you've got other configurations that are making it run too hot and thus getting throttled.
[One (M7) Original Android Development] flar2:
I don't know?

I just ran the antutu 3d test right now and got 7002

Using ondemand for both gpu and cpu, 1728MHz for all cores, gpu at 487.5MHz

Looking back, my highest ever is 7644. I can't remember how I acheived that, it was back on Android 4.1.2
[One (M7) Original Android Development] jerrylzy:
My 3D is over 7k. @487.5mhz
[One (M7) Original Android Development] SleemLDJ:
What's a recomemded read ahead buffer size for I/O control please.

Also what's a recomemded scheduler?

Rigtht now I am on FIOPS

....Sent from my HTC One

the Android Revolution HD way....
[One (M7) Original Android Development] flar2:
Default is recommended.

That is, fiops and readahead 128
[One (M7) Original Android Development] :
We speak about this two pages back: http://xdaforums.com/showpost.php?p=45030016&postcount=4505

I use also SIO, seems good to me (Deadline too :D). You need to test them but for me these 3 i/o schedulers works well. Maybe a preference for SIO for me.

:)
[One (M7) Original Android Development] Bellitsch89:
3.9 Beta works great!!! :thumbup:

Sent from my HTC ONE using ViperOne and Tapatalk 2

sry for my bad English :D
[One (M7) Original Android Development] fanbogo:
I agree, much better than 3.8
[One (M7) Original Android Development] revthanki:
I think I might know what's happening to the GPU. I installed 3.9, with GPU set at 400 MHz and then spotted all programs from changing kernel settings. On reboot I noticed that max GPU speed had been lowered to 200 MHz. This caused stuttering. Once I used Faux's app to set max back to 400 at boot everything worked perfectly.

So it's either kernel default setting that's broken or something weird being done by Viper.

In any case 3.9 is the best kernel for this device I've used. Snappy, tons of deep sleep and ice cold with extra thermal throttling. Thanks flar.
[One (M7) Original Android Development] flar2:
There is something in Sense ROMs that tries to set the GPU max at boot (not specific to Viper).

That's why I have a delay in my init script for the GPU setting. If you overclock GPU and the delay is not long enough, sometimes when you boot you will end up with 200MHz max.

Definitely something to check if you have bad GPU performance.
[One (M7) Original Android Development] threetwentyfizzle:
Thanks for the updates Flar, if I've read properly, has the 450 gpu on previous releases really been 487 the whole time? And by choosing 487 gpu option, is battery life going to take a hit compared to 3.4 with 450 gpu? Thanks!
[One (M7) Original Android Development] flar2:
Correct, and battery life will be the same.
[One (M7) Original Android Development] Bellitsch89:
Quadrant and Antutu with 3.9 Beta:

Sent from my HTC ONE using ViperOne and Tapatalk 2

sry for my bad English :D
[One (M7) Original Android Development] xmegapixelx:
what configuration do you use?
[One (M7) Original Android Development] Bellitsch89:
Max cpu0: 2160mhz, other cpu's 2033mhz, GPU 487, min cpu 384mhz, max cpu screen off 384mhz, fiops, Read ahead 2048, uv -75mv, ondemand...

Sent from my HTC ONE using ViperOne and Tapatalk 2

sry for my bad English :D
[One (M7) Original Android Development] Unoath:
Heres my Antutu benchmark..
[One (M7) Original Android Development] Finagle69:
Quick question. is 4.0+ for Android 4.3 and 3.9- for Android 4.2.2?

I'm on ViperOne which is still on 4.2.2.
[One (M7) Original Android Development] :
Hi,

Yes:

So you can use the last 3.9 version with your ROM.

4.* version (actually 4.2) is for Google Play Edition with Android 4.3 (not Sense).

:)
[One (M7) Original Android Development] OneCheekyDevil:
IR broken with 3.9

I'd hate to rain on your party Flar2, but IR stopped working with 3.9.

I flashed 3.8 to test if it was still working, and it was.

Flashed back 3.9 to prove it wasn't a fluke, and yes, it's not working.

Maybe you missed a switch/option or forgot to include a branch during compiling?

Can anybody else confirm it isn't just me?

(Testing with Smart Remote app)
[One (M7) Original Android Development] iElvis:
Mine works perfectly. Clear all caches, then try a flashing another kernel and then back to 3.9.
[One (M7) Original Android Development] Johnny424:
I think just you bro. Working fine here and haven't seen any other reports..maybe a reflash of your rom of choice
[One (M7) Original Android Development] gzsmooth:
Where do I download 3.9 to try out?
[One (M7) Original Android Development] :
Hi,

Here:

:)
[One (M7) Original Android Development] skulldreamz:
Page 449 at the bottom :)

Sent from my Renovated One
[One (M7) Original Android Development] OneCheekyDevil:
Well....:o

After downloading a fresh copy of 3.9 just now and flashing, everything seems to work.

Dont know what went wrong this morning when i tried using the Smart Remote app.

Sorry about the false alarm fellas.

... and thanx for confirming it was just me :P
[One (M7) Original Android Development] siemz:
Just flashed this over my stock 4.2.2 with sense 5, i tried to keep the 3 buttons home button but sadly it does not work.

Any idea why? I cannot find the option any longer under settings, and the "htc" logo still does not function as button. Sweep to wake is functioning perfectly tho, thankful for that!
[One (M7) Original Android Development] djskarpia:
with viper 2.1.0 , installed elementalx latest stable, set in aroma overclock 450mhz gpu, at every boot i have max gpu freq: 200mhz and the ui is not smooth... why??? now i set manually with faux123 but ... what's wrong?
[One (M7) Original Android Development] N0wy0ud1e:
After I install this kernel, the camera stops working.Opening the camera app is fine but then it's black, and the options to change to the front camera is shaded in gray.
[One (M7) Original Android Development] gGabi:
Setting max speed (frequency lock) in trickstermod., does it apply to all cores ? Or just to first core ?
[One (M7) Original Android Development] miten_sheth:
Some tests I did with 3.9 with Antutu

Fiops - 22412

Sio - 21930

Cfq - 21770

Noop - 21662

Row - 21628

Deadline 21269

Intellidemand governor, ondemand gpu, read head buffer size - 128

Extra cool thermal throttling.. Battery savings profile.. Power saver on..
[One (M7) Original Android Development] hamdir:
This is not true, i just tried Sense TV with an LG tv its fully working

I would say 3.9 is the most stable since 3.4

finally the GPU is fully working with no issues

i'm almost using my own script manager scripts to make sure no underclocks after reboot and switch between governors

stickies are the worst thing in HTC kernels :rolleyes:
[One (M7) Original Android Development] s_o_r_e_n:
Hi. I have some problems with instalation...after configuration in aroma, flashing starts but phone suddenly restarts and boots into system. Of course kernel doesn't flash. I tried installing Rom with full wipe, didn't help. I'm on ARHD 13.3 Wright now. Any ideas?
[One (M7) Original Android Development] Artius89:
Has anyone tryed ElementalX 4.2 on the new sense 4.3 roms?
[One (M7) Original Android Development] Denpech:
ElementalX 4.2 for Android 4.3 GE!!

Kernels on Android 4.3 are not present! An exit today base: 3.09.401.1 - props [MENTION=494185]LlabTooFeR[/MENTION] I think it will accelerate process of their working out .
[One (M7) Original Android Development] akarol:
Can anyone else confirm that volume wake is not working on VR2.1.0 with 3.9? Just noticed it today.
[One (M7) Original Android Development] N0wy0ud1e:
I'm on 4.1.2 Sense 5 stock ROM (rooted) and am using Sense 5 Android 4.1.2 ElementalX-m7-1.1 and it breaks the camera as soon as I install it. I have to re-flash the stock ROM again just to get the camera back. This sucks :(
[One (M7) Original Android Development] Johnny424:
Isn't volume wake a Rom feature though?
[One (M7) Original Android Development] Thijssie909:
How to debug dt2w issues? I think my phone sleeps to deep or something, because it fails many times...
[One (M7) Original Android Development] igor7:
Installed this kernel on Android Revolution HD 13.2 - work great! Especially CIFS support. But I have some problem,- files with Russian names appears with ???? signs. In order to fix this issue I need nls_utf8.ko module for this kernel. Somebody can point me where I can get it? Thank you in advance, Igor.
[One (M7) Original Android Development] wmg316:
When you notice DT2W not working, is it during usage that does not involve calls (just texting, browser, etc)? Or do you notice it not working during times where calls are being made (specifically after calls are finished)?
[One (M7) Original Android Development] akarol:
Indeed. But even after enabling and re-enabling it, it doesn't work. Didn't have any issues until I updated to 3.9 from 3.7 yesterday.
[One (M7) Original Android Development] Thijssie909:
No specific circumstances, it just often isn't waking the phone. I'm not using the sweep functions, just dt2w and l2w. I assume it has something to with the sleep state but I'm not sure.
[One (M7) Original Android Development] wmg316:
I am on ViperOne 2.1.0 and my volume wake is working with ElementalX 3.9
[One (M7) Original Android Development] akarol:
Just noticed that it is back up. What the F man! Mind of it's own...

Thanks anyways!
[One (M7) Original Android Development] wmg316:
I am using S2W, DT2W, & L2W and have no problems with any of them. On ElementalX 3.9 & ViperOne 2.1.0.
[One (M7) Original Android Development] Thijssie909:
Enabled s2w, see how it goes...
[One (M7) Original Android Development] ChasedMonkey:
Has anyone tested this on the Verizon HTC one? Since it's sense based it should work, right?

Such is life
[One (M7) Original Android Development] flar2:
Disable pocket detection.

No idea. Is Verizon cdma?
[One (M7) Original Android Development] ChasedMonkey:
Verizon is cdma

Such is life
[One (M7) Original Android Development] outta757:
Camera broke for me with 16 went back to 13 rather have OC
[One (M7) Original Android Development] tfouto:
What's the problem with HTC? It's because it's old code and we dont have the source code yet? Do we have to wait for HTC to release the latest HTC source code Kernel?
[One (M7) Original Android Development] flar2:
Maybe, maybe not. Last time the camera broke it was fixed by copying the older firmware. There might be some combo of camera libs/firmware/camera app that works this time as well. If not, we wait for HTC to drop some new source code.

It was almost too good to be true to have this week or so where everyone was free to try out different kernels and ROMs.
[One (M7) Original Android Development] elloar:
Cam is not working with the new Fw 192.401.16 and custom kernels. Just stock works. ;(
[One (M7) Original Android Development] Skizzy034:
What effect does the "cool thermal" option have on the device? Does it just make the device run cooler?
[One (M7) Original Android Development] tiny4579:
I think it is known by now you have to use stock on the new base for working camera.
[One (M7) Original Android Development] flar2:
Good question :good: Nearly 600 downloads of version 0.8, I'm surprised nobody has asked yet. It uses lower trip points for the thermal throttling. If you choose "run cool," when your device is under heavy load it will run about 5C cooler than the default option. The "run hot" option will let it get about 5C warmer before thermal throttling kicks in.
[One (M7) Original Android Development] tfouto:
But the cpu/gpu continues to run at the same speed? Isn't it this dangerous/unstable or diminish the lifetime of the phone?
[One (M7) Original Android Development] flar2:
No. The thermal throttling will never let it get to dangerous temperatures. No matter what you choose, the throttling kicks in way before dangerous temps are reached. Dangerous temps are like 90-100C. My throttling kicks in between 58-65C
[One (M7) Original Android Development] poczynek:
Yesterday got a non responsive screen - so couldn't unlock, couldn't do anything - had to restart for it to work again. Happened again just now. Not sure if my fault, ROM problem (TrickDroid) or kernel problem (ElementalX)??!!
[One (M7) Original Android Development] flar2:
Unfortunately this is a known issue affecting all custom kernels. Seems to only affect some phones. It's never happened to me and I haven't seen any kernel logs from when this happens so I have no idea what's causing it or how to fix it.
[One (M7) Original Android Development] Skizzy034:
So does that mean it will feel cooler to the touch more often?

---------- Post added at 08:48 PM ---------- Previous post was at 08:46 PM ----------

Hasn't happened here either (yet).
[One (M7) Original Android Development] flar2:
The cpu will stay slightly cooler but I don't know if it would be noticeable to the touch. This phone feels warm most of the time, just because the aluminum body conducts heat very easily.
[One (M7) Original Android Development] eliasadrian:
I know this will sound lame, but I'm going between this and teamSeven's kernels, but I can't remember which one I'm on right now, haha. Is this this kernel or the other? Thanks!
[One (M7) Original Android Development] Blue1k:
Noticed my phone is running very cool with this kernel. On stock kernel it was noticeable to the touch. I did down clock to 1.3GHz though.
[One (M7) Original Android Development] flar2:
It's this kernel
[One (M7) Original Android Development] soul44:
Flar2, I sent you a pm regarding game pad support in your kernels. I'd be interested to either try and port this to the Sprint model, or use it as a learning experience at least. I was unable to locate a relevant change using diff to compare files. Maybe the international version has some different filenames and I'm missing something. Any guidance would be very much appreciated. I apologize if it's against etiquette to have messaged you directly. Thanks in advance!
[One (M7) Original Android Development] lovepump:
I miss your kernel :'( cannot wait for 16 compatibility
[One (M7) Original Android Development] c5satellite2:
Flar, this kernel on ARHD8.0 breaks the camera. Any ideas on why or how it can be fixed?

Thank you for your time.
[One (M7) Original Android Development] eliasadrian:
ARHD 8.0 uses a new base (.16) from what I've been reading, and so far any custom kernels will break camera.
[One (M7) Original Android Development] flar2:
Oh great, HTC decides to release 4.2.2 source code just as I'm about 2 hours from leaving on vacation.

Look for an update next week
[One (M7) Original Android Development] Thijssie909:
Doesn't disabling pocket detection bring other problems?
[One (M7) Original Android Development] flar2:
No, this is why I made it optional. Some people have flaky proximity sensors and need to disable it in order to user s2w/dt2w/etc...
[One (M7) Original Android Development] Mr Djoegoe:
They wanna keep you hungry, Ghehehe ^^
[One (M7) Original Android Development] ChasedMonkey:
Yes it is, and so is Sprint. So the sprint version should work?
[One (M7) Original Android Development] flar2:
Probably not, but someone could give it a try.

Check that the partitions are the same first
[One (M7) Original Android Development] iElvis:
I don't suppose there's any hope we could cobble together a working 4.3 Sense kernel from this and the 4.3 GE source?
[One (M7) Original Android Development] skulldreamz:
+1 was thinking the same thing

Sent from my Renovated One
[One (M7) Original Android Development] ChasedMonkey:
What adb command is that?
[One (M7) Original Android Development] perfectslim:
Thanks flar2!.....

4.3 source code in 2014.....maybe....:D
[One (M7) Original Android Development] EnIXmA:
Hehehehe. True
[One (M7) Original Android Development] FAT4LITY87:
Hi guys, does "ElementalX-m7-4.2.Zip" work with Sense 5? or only work with Android 4.3?

Cheers :thumbup:

Sent from my Nexus 7 GSM
[One (M7) Original Android Development] :
Hi,

Only for Android 4.3 Google Play Edition, so no it's not for Sense 5 based ROM...

Uses the 3.* version for Android 4.2.2 Sense 5 based ROM...

The OP seems clear however...

:)
[One (M7) Original Android Development] FAT4LITY87:
Yeah I know, but since the 3.* version for Android 4.2.2 is at 3.9 and in the OP it says 3.4 I get confused :p

Thanks,

Cheers :thumbup:

Sent from my Nexus 7 GSM
[One (M7) Original Android Development] :
Re,

3.4 is the last stable version and the 3.9 is a beta... Actually the 3.* versions (stable or beta) are for Android 4.2.2 and Sense 5 based ROM's (or Google Play Edition but only for Android 4.2.2).

We will need some new version numbers in the future... :D

:)
[One (M7) Original Android Development] ChasedMonkey:
I found the Sprint and Verizon partition list, posted by other members and they are almost similar.

This is the Verizon list:

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 8bfffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 2ffffe00 00000200 "cache"
mmcblk0p37: 660000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"

and here is the Sprint list:

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p36: 00fffe00 00000200 "recovery"
mmcblk0p35: 01000000 00000200 "boot"
mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p33: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p29: 00040000 00000200 "skylink"
mmcblk0p30: 01900000 00000200 "carrier"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p32: 034ffa00 00000200 "reserve_2"
mmcblk0p34: 05fffc00 00000200 "reserve_3"
mmcblk0p31: 04729a00 00000200 "reserve"

The only difference is that spring has 2 more partitions:

mmcblk0p29: 00040000 00000200 "skylink"

mmcblk0p30: 01900000 00000200 "carrier"

The partitions are all the same size except for; system, cache, userdata, and reserve.

And I believe that the Kernel is installed to /boot, which is the same size on both devices.

Source:

Verizon: http://xdaforums.com/showthread.php?t=2416038

Sprint: http://xdaforums.com/showthread.php?t=2236254
[One (M7) Original Android Development] flar2:
Different partition numbers don't try flashing without modifying the installer
[One (M7) Original Android Development] wmg316:
You can always postpone that vacation!! :silly: :laugh:

JUST KIDDING!!!! Have a great break!
[One (M7) Original Android Development] ChasedMonkey:
Oh ok, ill look into that.
[One (M7) Original Android Development] threetwentyfizzle:
Anyone experiencing faster battery drain on the new betas post 3.4? I know the kernel is still baking in, but I'm using pretty much the same settings as 3.4 just the change in the gpu from 450 to 487, and I'm currently experiencing about 30% less battery life these last 2 days. Going from 18 hours with 3 hours screen time to about 12 hours and 2 hours screen time, same usage, same greenified apps. I'll give it a couple more days to see how it's going but thought I'd ask everyone else how there battery is in comparison to 3.4.

My settings:

1836 cpu

487 gpu

Run cool,

Stock cpu mp decision

750 uv

Screen off max @ 700 mhz

Thanks for the insight
[One (M7) Original Android Development] jerrylzy:
That means 4.3 OTA is coming. HTC won't release current kernel sense source until the next OTA pushes to devices. I really don't understand why they do this while stating that they always support developers' community. Annoying.
[One (M7) Original Android Development] flar2:
This developer won't be getting anymore HTC phones
[One (M7) Original Android Development] threetwentyfizzle:
Also, having high wakelocks from Google play services, nlpwakelockcollector seems to be causing quite a bit of wakelocks on this charge (over 1000). Maybe this is the source of my high battery drain

Edit: actually I was wrong. Over 1000 wake ups according to GSAM, and over 3500 wake locks!! Whoa!
[One (M7) Original Android Development] gGabi:
+1, I've noticed this since 3.7...

I'm back on 3.4 and battery life is indeed better.