yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Philaphlous:
IMHO is there a chance of further development on the GPU side? Possibly a more mild overclock on the GPU? seems like 487MHz seems to throttle alot for me. Is that possible?

.8 seems workin good for me! Love the development! Great work sofar!
[Nexus 7 (2013) Original Android Development] flar2:
That problem is caused by something else. Look at the changelog, all changes since 0.6.1 have been extremely trivial and mostly not to the kernel itself. Other than the sweep2wake adjustments, the only other change to the actual kernel was adding the ability to disable the magnetic on/off function.
[Nexus 7 (2013) Original Android Development] jerrylzy:
Hi, flar2! The New Nexus 7 equips 64bit DDR3L 800MHz RAM, but its bus freq is only 533mhz. If I remember correctly, only when the bus freq equals to memory clock, at least on Pentium 4, can the bandwidth of both be fully utilized.

I looked through Samsung E330S's source code and found that msm8974's bus freq is 931mhz while the RAM clock is 800mhz.

So is there a way to boost the bus freq higher, especially the gpu bus freq, or the snapdragon 600's bus freq is different from that of Pentium 4 so that there is no need to overclock the bus freq high? For high memory bandwidth contributes greatly to 3D performance.
[Nexus 7 (2013) Original Android Development] situman:
Ok. Just find it weird that this doesnt happen on .6.1 after reverting back. Shrug
[Nexus 7 (2013) Original Android Development] Kevin Goot:
Anybody have any battery saving tips?
[Nexus 7 (2013) Original Android Development] flar2:
I've decided to add the same thermal throttling solution as I use on my HTC One kernel. It works very well, but I still have to fine tune the temperature settings for this device. I think they are a bit conservative now, meaning it will still throttle pretty easily. I will provide options on the next release (run cool, default and run hot)

Note that /system/bin/thermald is moved to /system/bin/thermald.bak by the installer. So if you go back to stock kernel, you'll need to move that file back.

I also want you guys to be really sure if you report serious problems like reboots. All the code I've added to the kernel is very well tested and I believe it to be 100% stable. If you have a reboot, you need to wipe and start with a nice fresh install and see if it happens again. Also provide /proc/last_kmsg.

Download:

ElementalX-flo-0.10 *BETA*

Changes:

-add kernel-based thermal solution
[Nexus 7 (2013) Original Android Development] Malvarose:
Do you think this would solve my issue of benchmark apps crashing?

Sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] jlevy73:
Maybe, depends on what you clocked your CPU and GPU at. Some devices just can't handle being OC'd too much otherwise the benchmark will crash. Typically throttling will not cause crashing but result in lower scores because throttling will downclock the chip to reduce heat.

What is your CPU binned at? PVS?
[Nexus 7 (2013) Original Android Development] djdarkknight96:
I gotta say I'm usually a stock kernel guy because I really don't have time to play with the settings to get the best performance vs battery...been flashing Android since Donut and I must say this is the very first kernel I'm going to actually keep! Double tap wake feature has impressed me! The speed of this device was already great but DAMN MAN THIS KERNEL MADE IT FASTER! Like putting nitrous in my tablet....keep up the great work and congrats on being the ONLY kernel developer to win my love!

DJ

Sent from my Sexy Nexy 7 dressed in ClearJelly and Clear Apps!
[Nexus 7 (2013) Original Android Development] MetalWych:
I agree with your statements. This kernel is simply amazing. It makes this baby scream (mine never gets hot either, and i play the hell out of games on it). Plus, I Love double tap 2 wake and the short swipe to wake.

Thanks...
[Nexus 7 (2013) Original Android Development] Philaphlous:
I feel like in order to prevent thermal throttling, people put their tablets in the fridge for 10minutes or something..lol

In a plastic bag...ive considered it..lol probably corrode all the internals if there's condensation. lol

But I'll definitely give this a try! Seems .8 is finally breaking the 20k antutu again...

Edit, results

For some reason antutu has the wrong day...,says the 12 but its the 13..?¿
[Nexus 7 (2013) Original Android Development] jlevy73:
So I've been testing the poo out of the last beta and I've got nothing but great things to say. Sure, the kernel still throttles but that's nothing new with Krait/QC based chips. Everything is buttery smooth and I find battery life to be excellent, considering most of the usage on my tablet is either games or media.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Throttles back to 1.51ghz at 69c and back up to 1.7ghz at 65c.

Nice change! I get 11k on CPU test alone! Highest sofar
[Nexus 7 (2013) Original Android Development] djdarkknight96:
Wow!

Sent from my Sexy Nexy 7 dressed in ClearJelly and Clear Apps!
[Nexus 7 (2013) Original Android Development] flar2:
^^ I'm liking the way the thermal is working now.

It throttles to 1512 (stock) first, but touch boost is still active, so if you touch the screen it can still ramp up to max freq in the first level of throttling. If it reaches the second stage of throttling it does down to 1350 and touch boost is disabled. The third level of throttling is 918. You could see this level of throttling with something that uses all four cores for an extended time. If it gets past that, it throttles to 384. But I'm willing to bet it will never get to that point unless you leave your phone running stability test in a hot car or something.

The temperature limits and throttle frequencies are fully configurable. Next version I will add simple aroma options for three presets.

I'm not a gamer, so I only ever get throttling when I do benchmarks. So if any of you guys find it running too hot let me know.

Totally different architecture from the Pentium 4. I'm not sure if you can get any more performance out of this SOC, I think the tolerances are pretty tight.
[Nexus 7 (2013) Original Android Development] Artood2s:
Im on .9 with a 1.6 OC, Ultra CPU optimization, GPU OC, -50 UV all around (stock setting in Aroma), and the default ondemand parameters. I just played Bard's Tale for 45 minutes and my battery went down 14%. Pretty good in my opinion.

For the love of Android. What ROM, settings are you running? How is battery life?

Sent from my One X
[Nexus 7 (2013) Original Android Development] djdarkknight96:
CM10.2 everything set the way I flashed stock aroma settings except oc to 1900. Battery life is incredible!

Sent from my Sexy Nexy 7 dressed in ClearJelly and Clear Apps!
[Nexus 7 (2013) Original Android Development] jlevy73:
Makes sense now, for some reason CM is benching much higher than stock or CleanRom by a good 5000 points or so. I just got 21K, running at 1.836ghz, 487GPU, L2 on ulta on CleanRom.

That being said, compared to version 0.9, I was only getting 18K so with the new thermal throttle settings I'm getting a 3K increase. Damn good.

Geekbench = 3125

GFX: Egypt offscreen - 45fps

Egypt Onscreen - 44fps
[Nexus 7 (2013) Original Android Development] amynjimmy:
Loving the kernel.... Great job...

MB865/ST-ATT/4.4.2/BMM

ZLP- SM-N900W8/Att-ST/OxO/CWM/ViSiOn ND-5_4.4.2, snapkat 3.1

Nexus 7 (2013) stock, rooted, Elemental X Kernel*
[Nexus 7 (2013) Original Android Development] mdamaged:
Not sure if you're asking me also, but, no change in rotation that I can notice, it's more or less immediate, though I never timed that. Also, I'm on a 16G wifi model, not sure if it matters.

Edit: right now it takes less than a second to rotate either way, so no discernable delay here.

Edit2: have any of you having issues come from another kernel other than stock?
[Nexus 7 (2013) Original Android Development] brenty108:
Same as him. My screen rotation is normal I guess but not hanging to switch or anything. Takes longer to boot though
[Nexus 7 (2013) Original Android Development] znhel:
rotation with the same timing of the stock kernel
[Nexus 7 (2013) Original Android Development] fruity101079:
Strange because I just tried, and it appears to be ok today.

Maybe something in the process the other day that reduce perf .

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] Snap Shot:
Hello :)

I'm happy to flashed this kernel

so smooth and battery friendly

some question please

i just chose stock options in aroma

but i i flashed this kernel again and choose default options and recommended choices

like undervolting , gpu and cpu freq

is it okay . is it gonna harm my hardware ?

thanks :)
[Nexus 7 (2013) Original Android Development] darzur:
Do you mean rotation or boot time?
[Nexus 7 (2013) Original Android Development] fruity101079:
Rotation!
[Nexus 7 (2013) Original Android Development] bantamdraper:
Getting increased boot time as well when using elementalx with both CleanRom and Purity. Nothing that I would call drastic, and it's not anything I can't live with. 20 seconds difference. (43 seconds with elementalx vs 23 seconds with stock kernel in Purity ..timed from when the Google logo appears until the lockscreen shows up). Roughly the same with Cleanrom and the stock kernel. Not a huge deal, but still kinda curious why there's a difference.
[Nexus 7 (2013) Original Android Development] flar2:
I think it's been mentioned already, it's fstrim.

Contrary to what Google says, it does not seem to run on its own, at least not very often.
[Nexus 7 (2013) Original Android Development] darzur:
Is it possible to fix it? Or at least disable temporarily to check if it'll help?
[Nexus 7 (2013) Original Android Development] mdamaged:
You don't want to disable fstrim, like flar2 pointed out, google states it runs on its own, and it might very well do so, but only under certain conditions, it is possible that some usage scenarios would prevent it from running as often as needed, you might want to run it on your own, I've been using a script along with tasker which runs 20 seconds after screen off.

See links for more info:

Full thread: http://xdaforums.com/showthread.php?t=2670675

Running it manually: http://xdaforums.com/showpost.php?p=51222354&postcount=26

My tasker solution: http://xdaforums.com/showpost.php?p=51314187&postcount=32
[Nexus 7 (2013) Original Android Development] flar2:
Delete the fstrim lines from /etc/init.d/99elementalx

If you do this, make sure to reset the permissions to execute for /etc/init.d/99elementalx or none of your settings will be applied (in some apps the execute bit is unset after editing a file)
[Nexus 7 (2013) Original Android Development] mdamaged:
Oh, I misunderstood your post I think, I never realized fstrim was ran from your script. But other than storage size, why would this affect some and not others? The 16GB and 32GB make that much of a difference?
[Nexus 7 (2013) Original Android Development] darzur:
Just commented fstrim out but it didn't helped at all. Still have 120-140s boot time. It must be something else what causes such a big boot delay. I don't know it's a problem with AOSPA or my device but on stock kernels it boots fast.

--

darzur
[Nexus 7 (2013) Original Android Development] flar2:
It shouldn't take very long, but it depends how much your filesystem has changed. On mine it usually only takes 2 or 3 seconds.
[Nexus 7 (2013) Original Android Development] James_Feltham:
I am running stock with this kernel and I have the same boot times as the stock kernel
[Nexus 7 (2013) Original Android Development] darzur:
So maybe it's AOSPA related, but I hope it'll be solved in some future release.

--

darzur
[Nexus 7 (2013) Original Android Development] mdamaged:
Maybe you might need to see whats running at startup. Use autoruns or something. Maybe start in safe-mode and see if it starts up normally, if it does, then it's some app.
[Nexus 7 (2013) Original Android Development] darzur:
Nope. Stock AOSPA kernel - 40s, ElementalX - 120s without any change but kernel flashing.

--

darzur
[Nexus 7 (2013) Original Android Development] James_Feltham:
That's weird, I don't know what you guys have done differently
[Nexus 7 (2013) Original Android Development] flar2:
When I start on the next version I'll take a look at the boot times. Hard to say what else could be going on.

That said, I don't think my N7 has been rebooted in more than a month. Probably since I released the last version of the kernel.
[Nexus 7 (2013) Original Android Development] James_Feltham:
Hmmmmm, what's weird is that the increased boot times only affect some devices O.o
[Nexus 7 (2013) Original Android Development] boxcar8028:
Can anyone please recommend a good App for tweaking this awesome kernel or is it best to reinstall and reset. GREAT JOB DEVs. Thanks. :good:
[Nexus 7 (2013) Original Android Development] mdamaged:
Yes, I use Faux123 Kernel Enhancement Pro, great app, but if you want free, you can use Trickster.
[Nexus 7 (2013) Original Android Development] boxcar8028:
sounds good, I'll give it a try. thanks, man.
[Nexus 7 (2013) Original Android Development] darzur:
If it'll be helpful you can find my dmesg logs here. It's clearly visible that something wrong happens at ~37s and ~76s.
[Nexus 7 (2013) Original Android Development] digitalbot:
Hello, i play an intense hd graphics mmo on my nexus and we have wars that consist of 200+ people in a room, im looking for the optimal quality for setting up this kernel but without too much power, there are a few things i dont understand,

- what is thermal throttling?

Should i go more throttle if ill be clocking at 1.7 mhz? With a GPU clock of 477mhz?

Also confused on readahead buffer size

Would 256 make sense for

1.7mhz and

477mhz gpu

Maybe any other settings ive missed for improved performance? Am not too concerned on battery life.

Hope im not very confusing, or too scatterd here, Thank you

Heres a pic ill post of the intensity of the game
[Nexus 7 (2013) Original Android Development] flar2:
I would say go with the default settings. If you need a performance boost, go with 1.7 max CPU freq. Default thermals are probably best for gaming.
[Nexus 7 (2013) Original Android Development] AarSyl:
+1. From what I understand, thermal throttling relies on processing power. More throttling would keep your device cooler, at the cost of a little performance.

Less throttling might allow for more speed, but for an intense gamer, you might not want to do that. The tablet gets pretty hot near the top left corner.
[Nexus 7 (2013) Original Android Development] digitalbot:
Thankyou for the responses so think i should go for 1.7 And keep read ahead buffer normal also?
[Nexus 7 (2013) Original Android Development] flar2:
Readahead probably won't make much difference, I've been using 512. Stock is 128.
[Nexus 7 (2013) Original Android Development] AarSyl:
For games, read ahead isn't going to change anything, except for the game's load time, but that's a big maybe.
[Nexus 7 (2013) Original Android Development] ReWegar_:
hi

What am I doing wrong? (

I have a nexus 7 2013 LTE (deb) I installed CM-11-20140504-SNAPSHOT-M6

Then upload ElementalX-N7-2.10.1-cm followed by a restart. Bot CM logo is broken and the long boot time everything is much too slow and orange colors.

Thank you very much for your help!
[Nexus 7 (2013) Original Android Development] ReWegar_:
Shoot me! By mistake, I always chose to install the stock and not cm!! omg

I apologize for my inability to
[Nexus 7 (2013) Original Android Development] boxcar8028:
I'm just wondering what are some of your settings are. last night I bump up the GPU to 577 and all got messed up. Lots of FC and random reboots. Had to reset to default and all was well again. Right now my settings are all default but with fast USB charging and CPU set between 1800-2000. This seems to be vary smooth and stable. So just curious what is working well for you guys. Thanks
[Nexus 7 (2013) Original Android Development] James_Feltham:
Doesn't it say its not recommended to overclock your GPU that much? ;) So that would be the reason why it would be unstable.

Another question though, is there any danger to USB fast charging? I've never used it before because I thought it might be risky :)
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
I haven't found any benefits to overclocking the gpu over 450 myself.
[Nexus 7 (2013) Original Android Development] flar2:
There is no risk to the tablet. The risk is to your PC. USB ports are designed to deliver 0.5 amps, fastbcharge lets it charge at 1A. I have not seen any USB ports that can't handle it, but they may exist. Some USB ports limit the current anyways, in which case fastcharge has no effect.
[Nexus 7 (2013) Original Android Development] boxcar8028:
oh, I see. That's why I didn't really notice any improvement in my USB charging time with my laptop. thanks OP:good:
[Nexus 7 (2013) Original Android Development] a1317931279:
Nice kernel,thank you:good:

Is it possible to update to the latest Adreno V66 driver?

And,I think it would be useful if you add 200MHz for CPU and 128MHz for GPU.

Also,if the GPU voltage could be lowered,that would be nice.
[Nexus 7 (2013) Original Android Development] BWA80:
Hi!

Will this work on PAC rom?

Thanks!
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
If PAC uses caf/cm based ( i think it is?) , download the kernel with the -cm tag.
[Nexus 7 (2013) Original Android Development] Medel-Silver:
If you want new adreno drivers flash this https://www.dropbox.com/s/1ghrcgot7kb48ch/UPDATE-adreno-drivers-n4&n7.zip :good:
[Nexus 7 (2013) Original Android Development] James_Feltham:
Anyone tested this? And if so, have you noticed a difference?
[Nexus 7 (2013) Original Android Development] Araan45:
Flashing it now

---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------

Seems to be a quite large improvement on processing graphics.
[Nexus 7 (2013) Original Android Development] drawde40599:
I've been using it for few weeks , I don't notice anything on N7 or 5
[Nexus 7 (2013) Original Android Development] Medel-Silver:
Me, on both, n4 & n7(2013), it's compatible with ext4 & f2fs (I make this based on a zip by barome, thanks barome)
[Nexus 7 (2013) Original Android Development] a1317931279:
the new driver may only fix some bugs,no performance improvement found.
[Nexus 7 (2013) Original Android Development] a1317931279:
Another thing that I noticed is,the 4.7.3 version of GCC is too old,update to 4.10 may help.
[Nexus 7 (2013) Original Android Development] Snap Shot:
up for this please
[Nexus 7 (2013) Original Android Development] GialanG:
Why do you think default options may harm your tablet? No way
[Nexus 7 (2013) Original Android Development] Snap Shot:
just asking . cos in gpu stock freq is 400 and default option is 450mhz
[Nexus 7 (2013) Original Android Development] Medel-Silver:
And this is not enough? ;)

It depends on your firmware version, with march 31 performance is improved, if you have that version yet april 17 is basically a bug fix version, if your version in older than march 31 you will see performance improvement and bug fixes
[Nexus 7 (2013) Original Android Development] a1317931279:
Well,I actually found some improvement,compare to V53,the 3D benchmark score rose,from 6334 to 6809,and the UI became a little more smooth,don't konw whether it's my psychological effects or not.:p
[Nexus 7 (2013) Original Android Development] waz675:
It's called placebo ;p
[Nexus 7 (2013) Original Android Development] Kiszonyogor95:
Any plans with updating kernel any time soon [MENTION=4684315]flar2[/MENTION]?

TaPaTaLkEd from my Nexus 7 v2
[Nexus 7 (2013) Original Android Development] mdamaged:
Asking ETAs are a no-no, besides what's wrong with the kernel that it needs updating? It works fantastic for me.
[Nexus 7 (2013) Original Android Development] Kiszonyogor95:
Just being curious that's all :)

It is perfect for me too, but I believe that it would be even better in future.

Didnt mean to insult anyone :)

TaPaTaLkEd from Galaxy SIII
[Nexus 7 (2013) Original Android Development] flar2:
It might not be until 4.4.3 comes out. But I do have some potential improvements in mind, just haven't had time to try them out.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
Anyone else has music stutters when the screen is off? Or am I the only one? Anyone knows a fix?
[Nexus 7 (2013) Original Android Development] mdamaged:
No issues here, but I may not be using the same apps or playing the same formats. What app and what format (of the music, mp3, ogg, flac, etc) are you having issues with? ...also, what ROM?
[Nexus 7 (2013) Original Android Development] flar2:
Disable or increas the max screen off frequency
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Aaron, do you have any plans of merging upstream with Linux kernel 3.4.88 ?
[Nexus 7 (2013) Original Android Development] karanrajpal14:
It seems to be better now. But I have a question and I hope you don't mind answering it. This is a bug with android right ? I mean its present since KitKat. I've faced it on stock too. Don't you think we should report it to the bug tracker so that it may be fixed in the future versions?

---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------

The music player really doesn't matter. I've tried them all. As for the format I mainly use mp3. PA with elementalx but I face the same issue on stock pa or even the stock ROM. And the annoying part is that its happening on my nexus 4 too which is why I may have ruled out hardware issues.
[Nexus 7 (2013) Original Android Development] uchihakurtz:
Anyone experiencing wonky touch screen when you enable the magnetic cover thing? I noticed the screen turn off by itself even though my case doesn't contain any magnet stuff. And usually when I charge my flo, the touch seems jumpy as I can't pattern unlock my flo. When I reinstall the kernel and disable all the magnetic cover stuff everything seems fine (so far).
[Nexus 7 (2013) Original Android Development] mdamaged:
Dunno then, I use stock ROM with ElementalX and have 0 issues with mp3s (streamed or local) while screen off. I know that some people had issues with flac files on different custom kernel, the fix was as flar2 posted.

Maybe you have some app or service that is hogging the CPU while screen is off, Maybe boot into safe-mode, and see if it helps, I also read where another user suggested you go into dev options and change the background processing limit to 2 or 3, a user later reported that helped them, YMMV.
[Nexus 7 (2013) Original Android Development] karanrajpal14:
I'll try the background process limit and report back here. I did speculate that it was due to some app at first which is why I flashed the factory images. The issue was present then too. But it's comparatively better on stock. I'm not sure what to make out of this. A few of my friends seem to be facing this issue too.
[Nexus 7 (2013) Original Android Development] flar2:
I have a magnetic cover and it works great. Maybe there is something slightly magnetized in your case? Or the charging thing makes me think there may be a grounding issue (which is hardware)
[Nexus 7 (2013) Original Android Development] mdamaged:
I also read where using high quality mp3s sometimes made this happen. i.e. VBR or 320khz, can't say that's your issue, but just throwing that out there.
[Nexus 7 (2013) Original Android Development] yukkio:
I've problems with magnetic too. It only works when I open the cover. Is there any setting to disable it when you close the cover?

BR.
[Nexus 7 (2013) Original Android Development] flar2:
The magnetic sensor is either totally enabled or totally disabled.
[Nexus 7 (2013) Original Android Development] James_Feltham:
My magnetic sensor works fine for both opening and closing my case :)
[Nexus 7 (2013) Original Android Development] XperiaE:
work on all rom?
[Nexus 7 (2013) Original Android Development] AarSyl:
Works on all AOSP roms. CM roms need CM kernels.