yashsingh1/xdaforums huggingface dataset:
[One (M7) Original Android Development] mynameisjon:
Thanks for the quick fix.

The default max clock speed on the GPU is 400mHz right?
[One (M7) Original Android Development] n3ocort3x:
Android Tuner Pro :)

nope, 320MHz wanted to keep lower clocks too. This is OC Kernel. u wont miss 400.. trust me. 487,5 wont consume any more noticeable battery and its faster then 400.. so why keep it... better keep 200 freqs for guys like me :p
[One (M7) Original Android Development] mynameisjon:
I was under the impression that the previous versions had the GPU locked in at 320 and didn't scale down.

Are there any steps below the 320?
[One (M7) Original Android Development] Schrotty35:
Install v40 on 10.2 and 3 dot remove not work. I use trickster mod for setup.
[One (M7) Original Android Development] n3ocort3x:
200

that has nothing to do with kernel, check ur build.prop and/or rom settings

op updated to v41

changelog:

fixed gpu scaling, freqs available 200 320 487,5
[One (M7) Original Android Development] mj084:
But why is 400MHz removed:o
[One (M7) Original Android Development] aamitabh28:
Increase in performance without affecting battery

Neo .. new kernel works great too thanks mate
[One (M7) Original Android Development] n3ocort3x:
I

[MENTION=3507415]Chezbel[/MENTION]

U can't do that.. In my flashable zip there is a script that removes mpdec. If no track my kernel u loose that script and therfore u have mpdec and that's causing reboots. But not all is lost... Listen.. In ur device tree in Ramdisk there is a file called in init. qcom. There u remove the service mpdecision and then everything should work. Simply grep in Ramdisk for mpdec string and remove everything that contains mpdec.

Cheers and happy building. Nice u use my kernel
[One (M7) Original Android Development] Chezbel:
Thanks for the good reply! I will try your suggestion. Always so much to learn and not enough time...
[One (M7) Original Android Development] eyosen:
[MENTION=3507415]Chezbel[/MENTION] and [MENTION=4635674]n3ocort3x[/MENTION], so great to see this positive attitude in sharing, it's really refreshing after seeing people trying to one upping each other. Thank you n3o especially for giving back in more than one way.
[One (M7) Original Android Development] n3ocort3x:
Man I would know nothing if there weren't a few people who were always friendly and helpful to me. That's the reason why I'm making this.. Meet new people get skills and give something back.

I'm tired of moaning and hating and this is better then that... I'm not interested anymore... I won't even reply...

Chezbel always helps and is a resident in Lords thread and he tries to learn... I know that feeling and I appreciated it a few months ago if people told me what to do.. That saves so much time... So Chezbel.. Fire up that machine and build :D
[One (M7) Original Android Development] Chezbel:
Thanks, really I appreciate your help. I'm way ahead of you, my PC is already cooling down after being fired up. I commented out the mpecision service and rebuilt and reflashed. We'll see what happens, but now it time for bed.
[One (M7) Original Android Development] n3ocort3x:
before building, do make clean, its a ramdisk change and it needs that. then do not repo sync again.. it will overwrite the changes again. best would be to make an independed git out of device tree, then u can keep ur changes :)
[One (M7) Original Android Development] Chezbel:
I meant to do a make clean, but forgot. I'll build it tomorrow.

EDIT: if the change will get overwritten on every repo sync then it will be more convenient for my build scripts to delete the system/bin/mpdecision file since I already unpack the ROM to remove other stuff and then rezip it.
[One (M7) Original Android Development] jok4h:
n3o,

Loving v41. Thanks for all the efforts you've put into it.

One question. Do u modify the I/O Scheduler?

If so which scheduler and readhead size settings do u use?
[One (M7) Original Android Development] n3ocort3x:
FIPOS / ROW (both are for arm/phones/small systems) . benchmarks showed me that 2048 kb are the best value for both :) there u get the best results.
[One (M7) Original Android Development] jok4h:
If my goal is 'balance between performance and battery"?

Would i use 1024kb? Or would you still use 2048kb
[One (M7) Original Android Development] semdoc:
Finally on LorD's Home Brewed CM 10.2 with your Kernel mate...

Let we see your Baby :D
[One (M7) Original Android Development] n3ocort3x:
finally... as said.. its a whatsapp workaround but it works...and u joined us.... hell yeah :D
[One (M7) Original Android Development] Chezbel:
My build has been stable all day, thanks again for your comments.
[One (M7) Original Android Development] superleeds27:
Noticed this in the Hyperdroid thread.

added SIO scheduler, made it default (much better performance)

Is it something you've looked at or? not worth it?
[One (M7) Original Android Development] ess.boyer:
I'm running the v41. I tried out the smartmax_eps gov, but started getting wild reboots. Managed to switch back to regular ol' smartmax and all was well again.

This is flashed over the latest PAC ROM, and v38 of this kernel.

If it would be of help, I cab try to reproduce and capture the dmesg.
[One (M7) Original Android Development] semdoc:
Dalvik & cache wiped after flashing ? Just in case...

Sent by my ONE
[One (M7) Original Android Development] ess.boyer:
Yep, always wipe cache after any flash.
[One (M7) Original Android Development] semdoc:
Maybe UV too much?

Sent by my ONE
[One (M7) Original Android Development] ess.boyer:
I'm using whatever default is, not applying tweaks after. And like I said, it seems to only be the smartmax_eps gov that's causing issues.
[One (M7) Original Android Development] dc4:
In running smartmax_eps with 100 uv on slimbean 4.3 beta 4 and all is well.
[One (M7) Original Android Development] Absolut`:
boyer, i was having the same problems on PAC, told neo... i'm on hyperdroid now and smartmax/sio is running superbly on it...
[One (M7) Original Android Development] dirtbikerr450:
With this kernel the camera does not work with hyperdriod AOXP
[One (M7) Original Android Development] mj084:
Builddate of this Rom?

The Rom must be up2date, then everything works fine....
[One (M7) Original Android Development] Smoothface:
Sounds like you are running a rom with the recent Google edition changes. In clockans thread neo said he will release an updated kernel for it soon.
[One (M7) Original Android Development] n3ocort3x:
jup... thats correct.. guess on evening, already have everything ready.. just need time to test before release. Some guys in here are tooooo fast for me... lord and kris... i look in ur direction :D
[One (M7) Original Android Development] n3ocort3x:
Iǘe updated post number 4 for u guys with a battery life test + Settings in Trickster Mod. :) Hope it helps one or another !

http://xdaforums.com/showpost.php?p=40323043&postcount=4
[One (M7) Original Android Development] semdoc:
Lol... Great stats :)

Can we tune smartmax governor? Or It is enough to stay with default setings?
[One (M7) Original Android Development] mj084:
[MENTION=4635674]n3ocort3x[/MENTION]

thx for posting this pictures...

Can you add a picture with all voltage steps, some are missing;)

What kind of CPU do you have (cause you UV a little bit more than your stock kernel)
[One (M7) Original Android Development] superleeds27:
Latest kernel... will post config later if people want it!?
[One (M7) Original Android Development] lbroksle:
Awesome battery life. Thanks for a great kernel.
[One (M7) Original Android Development] DanRyb:
Glad to see you're already working on it. Should have guessed. :) Flashed CM 10.2 latest nightly this morning and of course your kernel and camera stopped working. Had to flash nightly again to get rid of your kernel so cameras work. Missing your kernel big time!!!!!! lol :)
[One (M7) Original Android Development] bbgt2:
Running this great kernel on CM 10.2 and can't figure out how to or what button to press to get to see my recent apps. DT home brings up Google search.
[One (M7) Original Android Development] nicksmizzle:
long press home
[One (M7) Original Android Development] gilbus:
You can change the behaviour under settings ;)

Gesendet von meinem One mit Tapatalk 4
[One (M7) Original Android Development] n3ocort3x:
Steve Kondik just fixed POWER ON Delay, syncing kernel sources now, update incoming on evening. Legend.... Hats off :)
[One (M7) Original Android Development] bbgt2:
General Settings or do I need Trickster Mod app ? If its in general settings I cannot find it.

---------- Post added at 08:39 AM ---------- Previous post was at 08:38 AM ----------

No worky.
[One (M7) Original Android Development] mitrx:
First I'd like to say thanks for your awesome work :)

That delay was doing my head in! I've only had my phone for a few days and couldn't remember if the delay was there stock or if it only appeared after I started messing with things. Glad you cleared it up and I can relax now
[One (M7) Original Android Development] n3ocort3x:
OP updated:

teaMsevenAOSP_v42_CM 10.2

- huge patchset from GE 4.3 source, intervigil, CM (for using 4.3 blobs)

- updated panel drivers - Steve Kondik, CM

- patched panel drivers - Steve Kondik, CM

- reduced lag while Power ON (screen lag) - Steve Kondik, CM

- reduced lag while scrolling (adjusted Hotplug Control)

- reduced lag for bringing up recents even more faster

BE ADVISED: UR ROM HAS TO BE up2date before using this kernel, otherwise

Camera will be borked, broken, and will explode

Those stuff is from gerrit and not merged atm, I tested and its indeed faster.

BUT dont think its sense nivieau now. Its not. Also LorD reported to me that when device is longer not touched

the lag gets bigger. I cant reproduce it but he does. ALL my credits for this patches goes to Steve from CM. There is

also another huge patch on gerrit that should makes the device even more smoother, but LorD reported the

patch makes the phone hard reboot. so its not merged.
[One (M7) Original Android Development] eyosen:
[MENTION=4635674]n3ocort3x[/MENTION] is this the same as the one in LorDs cm10.2 build?
[One (M7) Original Android Development] n3ocort3x:
Nope lord tracks stock cm kernel just with the logo and touchscreen stuff added. :)

noNeedForAsig
[One (M7) Original Android Development] superleeds27:
Probably not using the attest 4.3 blobs...
[One (M7) Original Android Development] n3ocort3x:
not needed.. they are using old blobs maybe.. i did a pac build on my own which is working flawlessy... dont excpect i open a new thread.. i share this only when necessary: LINK_PAC-M7UL_02092013 also i dont want anyone to report in other thread "This build from n3o works, why not here?" They will start working when they update their blobs too. If i see some posts like this... it was the last time i share something.
[One (M7) Original Android Development] ess.boyer:
Cheers for this, man! If I encounter any issues with it, I will report them here. Does this build include the v42 version of the kernel baked in, or should I flash it over separately?

In addition, I am finally motivated to fix my build env and start doing my own PAC builds. I will also be (attempting, at least) to fix some bugs and submit them to the gerrit.
[One (M7) Original Android Development] n3ocort3x:
No need to report bugs for rom here. Won't support it. Have enough to do with kernel stuff. Don't get me wrong but that would be too much. Kernel is not included. I recommend flashing rom.. Boot into system one time and then flash kernel. :)

noNeedForAsig
[One (M7) Original Android Development] ess.boyer:
Fair enough. I guess I meant I'll report any low-level stuff, that would more likely be kernel related. Sometimes, without having the codebase(s) handy it's hard to tell whats what.

update:

N3o, your build/kernel combo is so far so sweet! Running very smoothly. Sleep/wake are quite fast, recent apps is very fast (and love the new feature in there!).

Camera is working, an so far, not a single complaint. Great work my friend!
[One (M7) Original Android Development] n3ocort3x:
Thanks. But remember.. i only compile those things and change really small things to rom (like dialer, phone, contacts, backgrounds) All the heavy liftign is done by team pac and CM :)
[One (M7) Original Android Development] ess.boyer:
Just noticed that logo2menu isn't working with v42 and n3o's PAC.

Should also mention, it's the BACK_MENU_HOME version of v42.

Also, after discovering the no menu button, I re-flashed the kernel. I also noticed in the PAC Settings, there is an option to enable remapping of the menu short/long press actions. Just in case, I enabled button remapping, and assigned the action for both short/long to "open/close menu".

No dice.
[One (M7) Original Android Development] GuyInDogSuit:
Flashed this an hour ago and my One has rebooted about 20 times since then.
[One (M7) Original Android Development] expertzero1:
works here on aoxp...

---------- Post added at 03:49 PM ---------- Previous post was at 03:48 PM ----------

make sure your running a rom that is currently up to date. AOXP/Lord clockan home brewed rom
[One (M7) Original Android Development] ess.boyer:
This happens to me too if I select the smartmax_eps governor. Not sure why, as it doesn't seem to do it for anyone else.

Try switching to the regular smartmax gov (or any other, really) and see if that helps. Otherwise, I haven't had a single random reboot with this kernel.
[One (M7) Original Android Development] GuyInDogSuit:
It worked, set it on smartmax and haven't had a single reboot. It wasn't on smartmax eps, though, it was ondemand. Weird.
[One (M7) Original Android Development] n3ocort3x:
As u guys remember.. i´ve posted a PAC 4.3 build yesterday (or the day before yesterday ??, no clue) it had a few issues with trebuchet and dialer. As i dont want to stay anyone on this broken build, I did a new one today that fixes theses issues. Grab it here and as always: Dont report any bugs from this build in PAC thread. If u still encounter any issues let ME know here. Thanks :)

http://tunsd.de/downloads/PAC_43/

needs another 30 minutes until finished with uploading. Kernel is stock, if u do a clean install, boot it up with stock kernel and afterwards flash v42. it seems that some run into trouble when flashing the kernel immediatley after fist installation without even booting one time into system :)
[One (M7) Original Android Development] SwayART:
Any chance to get fauxsound to work with this kernel?
[One (M7) Original Android Development] qkall:
Just flashed this and HTC menu button is not working...
[One (M7) Original Android Development] lbroksle:
This Pacman ROM won't work with att right?
[One (M7) Original Android Development] kravguy:
Downloading now. I've never had any issues before with flashing the kernel before first boot. Is that something with this particular build or something that's been happening in general?

Btw, been running that last build so thanks for putting it up. Out of curiosity, can I ask why you're building pac? Is there anything different than the builds in the pac thread?

Sent from my One

---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------

Should work fine. Just remember to select the right apn.

Sent from my One
[One (M7) Original Android Development] n3ocort3x:
I just shared last time I updated kernel an updated rom version with new blobs. Unfortunately it had some issues which are solved in this build. I track some other stuff for rom then official nightly but aside from that it's the same. I won't update the rom further in public .. I just wanted to share because of new blobs.

noNeedForAsig
[One (M7) Original Android Development] aamitabh28:
The latest kernel v42 with smartmax and balanced hotplug values is the best ive tried.. Trust me guys carbon with this kernel feels as smooth as my flo with a great battery life.. No strutters at all.. Super gaming expereince.

Perfect.

Thank u so much
[One (M7) Original Android Development] cchant:
I didn't get a screen shot because the phone died as I was trying to but yesterday I got 5 hours and 45 minutes of screen on time with Lord Clockan's CyanogenMod. Used balanced hot plug settings and smartmax. All day use was on LTE.
[One (M7) Original Android Development] ess.boyer:
I can confirm this issue for myself, too. I checked, and the keylayout included with the kernel between v41 (menu working) and v42 (menu not working) are the same. I don't know where to look beyond there, and don't have time to comb through Github to see what changed between then and now (because Github browsing is VERY slow for some reason).

I can also, happily, confirm that both the dialer and camera are both working flawlessly with the last of n3o's PAC builds, and v42 kernel.

I always flash the kernel right on top of the ROM. I use TWRP 2.6.0.1. I choose "Install" and select the ROM zip. Then I "Add more zips" and add the kernel. Haven't had a problem yet. YMMV.

[MENTION=4635674]n3ocort3x[/MENTION]: Do you know if the official PAC maintainers will be updating the blobs on the official builds? Also, in which project in the Git can I find where the blobs are, so I can watch the changelog for them.

Thanks again for putting this build out, and for the very fast fixes :) I was just about to roll back to the v40 kernel and an older nightly, and I'm glad I don't have to now :)
[One (M7) Original Android Development] cchant:
Have you checked in trickster mod that l2m is enabled?
[One (M7) Original Android Development] ess.boyer:
Oddly enough, I was just coming on here to say that I found the setting in Trickster Mod (which I only just now installed), turned it on, and it is working perfectly now!
[One (M7) Original Android Development] n3ocort3x:
often are the easiest things the trickiest... lol :p i remember back when i bought trickster i ALWAYS forgot to hitt apply. glad u solved it.

Good news for those who follow [MENTION=1184673]LorD ClockaN[/MENTION] [MENTION=1795993]kristofpetho[/MENTION] and me:

LorD managed to compile AOKP 4.3 :D M7 -> AMAZING

kristofpetho solved whatsapp voice issue -> AMAZING

and i stuck on 128kb broadband and a dualcore processor and have to wait for downloads and for compiling processes :D -> RIDICOLOUS
[One (M7) Original Android Development] superleeds27:
:D
[One (M7) Original Android Development] qkall:
Can someone point me in the direction of older kernel releases... Newest nightly looses cam on install but HTC menu button works now... Weird.
[One (M7) Original Android Development] willew4:
This is a valid request, imo. Had I not still kept former versions, v42 would have really killed my official CM nightly installation from 9/2/13. The screen wake options were inconsistent, and the phone would randomly go into sleep mode, while in use. After rebooting into recovery, and flashing v40, all was back to normal again.
[One (M7) Original Android Development] n3ocort3x:
older kernels for non up2date roms:

http://tunsd.de/downloads/teaMseven_AOSP_4.3_KERNELS/
[One (M7) Original Android Development] formula84:
What was the fix for whatsapp?
[One (M7) Original Android Development] SwayART:
Anybody have issues with camera not working with latest kernel and PA 3.99?

Ok ya. Flashed v41 and it's all good now. Loved wake lock did though :( haha
[One (M7) Original Android Development] n3ocort3x:
U can record and send stupid voice notes now and it will be recorded properly. High priority fix :P but it was interesting to work with Kristof and watch what he did to fix it so we learned out of it. Even it's a low priority fix :)

noNeedForAsig
[One (M7) Original Android Development] raycaster3:
Thanks for the PAC build. Its weird though it won't read my sdcard from the gallery and I had to out notifications into sdcard/Notifications just to have a ring tone. Would be nice to run, but having the device read partitions properly is kind of a big deal. Smooth as silk though. Kernel is money.

Sent from my One
[One (M7) Original Android Development] aamitabh28:
There is a problem.. Gpu sits idle at 320 mhz when not in use and rarely does it go to 200 mhz
[One (M7) Original Android Development] n3ocort3x:
then there is a load that prevents it from scaling down. just tested and working fine. Just another fact: i use GPU at perfromance 487,5 MHz and i have the same battery as with 200 Mhz... so enjoy that everything stays smooth and dont belive every urban legend here in XDA :) I will rework GPU in next release anyway as i want to bring back 400 MHz freq
[One (M7) Original Android Development] cchant:
+1

I get 4 to 5 hours screen on time with 487 Mhz GPU
[One (M7) Original Android Development] superleeds27:
Working great on Lords AOKP builds
[One (M7) Original Android Development] formula84:
Thanks, i knew of the bug, I was curious what the fix was... Link to commit?
[One (M7) Original Android Development] Absolut`:
Neo, what are your thoughts on adding the SIO i/o scheduler in your kernel? It is running pretty damn smooth with smartmax on hyperdroidAOXP stock kernel.
[One (M7) Original Android Development] n3ocort3x:
http://review.cyanogenmod.org/#/c/49792/ its abandoned but lord keeps it in his builds and as i track his device tree my builds also include it. dunno what cm will make on official side

Ok, but why, i mean we have to I/O scheds which are optimized for small arm system (row, fiops). Will read a bit tomorrow about it and then i decide if it comes into or not :) dont want to make the kernel bigger without knowing why :p
[One (M7) Original Android Development] formula84:
See the comments... http://review.cyanogenmod.org/#/c/49764/ is the patch that is merged that did the same thing with less code.
[One (M7) Original Android Development] tbalden:
Thing is, when i tried your kernel i just fastboot boot zimage-ed it, not flashed, thats why it worked for me. So it will be a ramdisk or kernel offset problem.

IMHO best thing is to pack it manually with python scripts, instead of kitchens. Later when i get home, i'll send you my packing python scripts.
[One (M7) Original Android Development] n3ocort3x:
AHHH now everything is clear :) thanks my friend... I remember we had the same problem on oneX a while ago.. then we started to pack with kitchen and it started working... I come back to on gtalk on evening about these python scripts... i use a perl script to unpack and mkbootimg to repack (but as said, one onex we had the same) now i have compiled 2 other versions and repacked with kitchen

I have here now 2 testversions and i need someone to test:

1 version:

boot.img: http://d-h.st/BlJ

modules: http://d-h.st/xXB

2 version:

boot.img: http://d-h.st/maC

modules: http://d-h.st/NNB

In the first version i only changed repack method

the second version is repacked with kitchen and compiled with linaro

please test both and report back guys if they boot or stuck at splashscreen :)
[One (M7) Original Android Development] biohaufen:
I will test it in about 3 hours ;)
[One (M7) Original Android Development] n3ocort3x:
that would be AWESOME.. I´m really excited what happens now :p
[One (M7) Original Android Development] tbalden:
sorry, right, i use perl too, mixed up with python...damn, these scripting languages :D

but its important to have the correct offset in it.
[One (M7) Original Android Development] biohaufen:
Seems that it doesn´t work, but I will try again with 1.29.401.13...
[One (M7) Original Android Development] Trekest:
Out of curiosity (I haven't gotten my One yet), I noticed that v3/3.1 are now absent. Has something gone wrong with them?

I've re-read the entire thread and couldn't find a mention of why.
[One (M7) Original Android Development] n3ocort3x:
If u read the entire thread then u would know that i have serious problems with repacking... :) the kernel seems to work if u fastboot boot it but if u flash entire boot.img it seems to stuck on splashscreen and i have no clue why because in the meanwhile i tried several repacking tools and nothing work :(

still need reports from versions mentioned in my last post
[One (M7) Original Android Development] biohaufen:
Jep both kernels do !not! boot :( Stuck at splashscreen :/