yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] ngyurov:
I'm getting better battery life than previous version with SlimKat and 1.6 max freq and mc set to 2, haven't used undervolting and lowing min. Freq. After 2 hours of web browsing and being connected to a WiFi network in standby for another 10 hours my tab is at 77% which is a very good result for me.
[Nexus 7 (2013) Original Android Development] SuperSmashedBro:
8 hours screen on time at 50% WiFi on majority of the time
[Nexus 7 (2013) Original Android Development] optimusG:
What use do you guys do and you have 50% remaining time with 8 hours of sot? Google gives only about 8-9 hours sot with stock settings.

My tablet looses about 10-13% per hour of sot. And I have used many combinations of roms/kernels.

Sent using Tapatalk
[Nexus 7 (2013) Original Android Development] SuperSmashedBro:
Mostly reading textbooks and the occasional web browsing. I also got my n7 like a week ago, that probably has something to do with it
[Nexus 7 (2013) Original Android Development] sizzlers:
Big drain with this kernel
[Nexus 7 (2013) Original Android Development] papikev:
Any battery leaching apps installed? Have you checked? What are your settings? Oveclocked? S2W activated? Any wakelocks? Play alot of games? Details, details, details. Or is it all the kernels fault?
[Nexus 7 (2013) Original Android Development] SickBeast:
I ran at 1.94ghz with the l2 cache maxed out and the gpu at 600mhz. S2w was on. All I was doing was browsing the web. My Nexus got quite warm even under minimal load and the battery drained at about twice the speed that I am accustomed to. I also had to increase the voltage 4 steps for each of the overclocked frequencies.
[Nexus 7 (2013) Original Android Development] sizzlers:
It's same settings applied as in previous version. Just overnight it got big drain. I'm strictly watching apps and controlling them and I think it's the kernel side. Either way it is I'm stuck with it since Franco doesn't offer UV and this one does have more features then elemental and greater battery while gaming.
[Nexus 7 (2013) Original Android Development] danaff37:
My battery life is just as fantastic as ever.
[Nexus 7 (2013) Original Android Development] SickBeast:
I just realized that I stupidly had mp-decision enabled along with intelli-plug. I have now disabled mp-decision and things seem better. I will report back later once I have more information.
[Nexus 7 (2013) Original Android Development] thelossa:
I had pretty bad battery drain on 142, CM11 as well. Betterbatterystats didnt show any wake locks but it still drained at 2.5%/h in deep sleep.

I had it OC at 1.6Ghz, everything else pretty much default, did deactivate s2w though.

CM11 stock kernel doesnt drain. Lost 0% on 15h deep sleep...
[Nexus 7 (2013) Original Android Development] markd0wn:
Not here, cm-11-20140228-NIGHTLY-flo & Glitch-N7-r142-CM11, all default settings (Glitch's default, not stock's default - everything as the installer suggests except the sweep functions which are disabled). Still at 100% battery after 9 hours and 6 minutes (flashed it 9 hours ago, it was idle since - just 5 minutes screen on time)
[Nexus 7 (2013) Original Android Development] habylab:
I meant intelliactive I mean!
[Nexus 7 (2013) Original Android Development] SynnyG:
I've just installed the latest AICP with Glitch and I had the same issue as yours, black screen after bootanim... From the Glitch install, I've removed dalvik and bionic optimization and now I can boot into AICP ! That's the issue ;)
[Nexus 7 (2013) Original Android Development] papikev:
I switched to omni, but with the new aicp release tonight, I will go back and run Glitch. Thanks man.
[Nexus 7 (2013) Original Android Development] farenteria:
No, it doesn't. Glitch will probably put it in a future release
[Nexus 7 (2013) Original Android Development] nokiagye:
My battery..GPU 500 CPU 80-1700 ondemand on all mp enable CPUs min 1 Max 4
[Nexus 7 (2013) Original Android Development] 3dawg:
Identical problem here. Except I'm OC'd to 2.0Ghz. Idle battery is much worse than it was a few versions ago.
[Nexus 7 (2013) Original Android Development] Sh0X31:
Have the Glitch Kernel multirom support?
[Nexus 7 (2013) Original Android Development] xanthrax:
Yes... Read the OP please

sent from my Darkside of Nexus 4
[Nexus 7 (2013) Original Android Development] Lazy Rich:
No problem with standby here. I haven't used the tablet for 2 full days and I only lost 10% in 48 hours, so for me this looks more than good.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Blizzard300:
Did you use the aosp version of the glitch kernel? I am not sure which one to flash...
[Nexus 7 (2013) Original Android Development] nokiagye:
We have kexec patch but we haven't space for 2cond ROM ..only 1.5 left..crying..
[Nexus 7 (2013) Original Android Development] xanthrax:
speak for yourself pal, I've got a 32 GB device ;)

sent from my Darkside of Nexus 7 LTE
[Nexus 7 (2013) Original Android Development] papikev:
AICP=AOSP version of the kernel. Have not tried it again yet since that last user reported that it works without enabling dalvik/bionic optimization.
[Nexus 7 (2013) Original Android Development] Blizzard300:
Thanks, i can confirm that it works on aicp. Just flashed r.142 - everything is fine :)
[Nexus 7 (2013) Original Android Development] SickBeast:
I'm no longer experiencing the battery drain issue. I'm getting about 10% drain per hour of screen on time and the idle drain is negligible.
[Nexus 7 (2013) Original Android Development] just lou:
I tested mine last night just to make sure my battery drain was fine, and I only lost 2% in 10 hours or so. Running stock ROM.
[Nexus 7 (2013) Original Android Development] tibere86:
I get the same idle battery. I usually lose 5% per 24 hours. Connected to WiFi 100% of the time. No issues here.
[Nexus 7 (2013) Original Android Development] matcho13579:
Do you have S2W, DT2W (or this kind) enabled?
[Nexus 7 (2013) Original Android Development] tibere86:
Nope. I always keep S2W and DT2W disabled as well as all other screen mods.
[Nexus 7 (2013) Original Android Development] matcho13579:
Maybe that's why you got so great battery life.

You got LID disabled, too?
[Nexus 7 (2013) Original Android Development] Shillopellos9:
Is this kernel or rom related? anyway have a look:

http://xdaforums.com/showthread.php?t=2665832

New adreno drivers
[Nexus 7 (2013) Original Android Development] matcho13579:
Edit: nvm, found out what I needed to know

Tried that on Mahdi and on same setup I got 1250(old) vs. 1595(new) on 2D and 5108(old) vs. 6742(new) on 3D in Antutu, so definitely better performance
[Nexus 7 (2013) Original Android Development] SickBeast:
I got a small performance boost as well on the stock rom.
[Nexus 7 (2013) Original Android Development] mus1mus:
There is gain but not this drastic as you reported.

Not too sure though as you have a different ROM.

:D
[Nexus 7 (2013) Original Android Development] matcho13579:
Don't know, I just ran an Antutu test :D But I didn't play any game since I flashed that drivers, will test today
[Nexus 7 (2013) Original Android Development] MadMatt89:
Hi,

Is anyone else having lags? I'm not too sure if it's a kernel or hardware issue: sometimes when I play clash of clans or use the browser the screen starts to lag and is no longer responding immediately. If I pull from the left to the right I see a cut in the screen picture and it takes some ms to look right again (sorry I don't know how to describe it better).

Rebooting helps sometimes but it comes back.

Anyone familiar with this?
[Nexus 7 (2013) Original Android Development] Alex1911:
Lag's and Freezes ???

Hi, i have similar Problem's, except the Screen-cut-Problem you described.

My Nexus freezes and lag's, until i change the CPU-Governour (was interactive, changed to Smartmax) but comes the weird part:

It look's like the CPU is clocking tooo low sometimes and causes Freezes, i proved it by CPU Stats and it occoured very rare.
[Nexus 7 (2013) Original Android Development] MadMatt89:
Good point I'm on smartmax right now, maybe I should try the default ondemand
[Nexus 7 (2013) Original Android Development] akaHardison:
OTG went bad in r142,and very high battery drain.Go back to r140.2
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Otg is working fine for me and I am getting 10+ hours of sot.
[Nexus 7 (2013) Original Android Development] nokiagye:
On the new slim 3.4 they implemented bionic patches and I can't flash the kernels patches anymore if anyone find a solution on this please post.

The reason I post this is the low bentchmarks scores. The rom working like before.
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
If the rom/kernel feels fine does the benchmark score matter? It just seems people are obsessed with benchmarks rather than enjoying their devices. (not referring to you, just in general)
[Nexus 7 (2013) Original Android Development] nokiagye:
Yes I know but is nice to see high scores just for fun.
[Nexus 7 (2013) Original Android Development] just lou:
OTG works fine for me, and I have no battery drain issues.
[Nexus 7 (2013) Original Android Development] Lazy Rich:
Same goes for the latest Purity update, doesn't boot up when ticking bionic patches etc. Just bootlooping.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] airon11:
This kernel is fantastic...great battery life and smoothness with my setup...thank you to the dev for the great work
[Nexus 7 (2013) Original Android Development] menissalt:
Some benchmarking

Here's my first test with Antutu.

CPU @1998000

GPU @ 627 (trickster wouldn't let me max it out)

RAB @ 4096

I noticed a lot of stuttering so I took the GPU down to 600 with great results.

Then as a final test I put RAB (read ahead buffer) to 2048 with even better results.

::EDIT::

Forgot to mention I'm on PACman RC2. Had to factory reset to stop it from bootlooping, then restored data from nandroid.
[Nexus 7 (2013) Original Android Development] thunderger:
I suggest to set default thermal limit to 74 and read ahead to 2048 using ROW. :) And min freq should be 384 instead of this 1 ghz step it is at the moment.

Does anyone know how the core "binding" is realised in N7 SoC? It seems to be a renamed S600 SoC. My N4 can run two cores with same voltage and frequency but N7 perhaps can set up and shut down! each core.

I think about a scenario in which I set up usage profiles. Running desktop, internet, reading books, etc. only one core with max freq 1.0 GHz is running. The other three are "off" and can't be activated. After starting a video or a game, the other cores are "on" sporting max needed performance.

In times of my S2 I set up such a behaviour with setcpu, in trickster and faux I don't find such options. At N4 I use "init.d" scripts with short cuts but this isn't comfortable.
[Nexus 7 (2013) Original Android Development] ptesmoke:
oh man......oh man....haven't had glitch goodness since my captivate days....oh man...its like Christmas!!!
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4183085]thunderger[/MENTION]

- Since last build you have much more thermal settings and it's higher by default anyway so you can't need more than that unless you're planning to melt the back cover :D.

- Read ahead 2048 why not, it's a non-issue since you can tweak it up to 4096, but I do agree.

- Min freq is already 384, it's just mpdecision in action, moving low freq dynamically (and trickster/fauxclock can't see it). Try not to force 384 as min freq and you'll see it'll still drop to 384.

About your idea, it's unoptimal and a waste of time IMHO as it's faster and more energy efficient to run a few cores at lower speed than one at full speed anyway. By the way mpdecision works perfectly fine by default and will shut off cores if load is low. I don't see any scenario where your idea would actually help in any way to be honest.

-------------

Here's what the device can do @ 2.05 GHz :
[Nexus 7 (2013) Original Android Development] penguin449:
[MENTION=3847629]Tk-Glitch[/MENTION] this is what it does at 1.89GHZ :p

Sent from my N7 2k13
[Nexus 7 (2013) Original Android Development] menissalt:
OK, share with the class.. What settings are you running? I'm running @ 1.99 and couldn't hit 26000.
[Nexus 7 (2013) Original Android Development] penguin449:
Okay, I have got the highest benchmarks ever at HTC Desire C and Samsung Galaxy W! Now I hope to keep it like that over here too, but I can't boot higher then 1.89 otherwise antutu just fcs on me when it runs at the highest frequencies :( however, I'm using ondemand @ 1.89ghz, GPU @ 545mhz no mpdecision, no fsync, throttling starts at 95 degrees.. Running carbon, stripped, and apps hibernated.. Get around average 40fps, lowest 35, highest at about 52fps.. Row and 1024 with Westwood.. The bus is on fastest, and the 850UV.. Plus, just broke the 28k more comfortably..

Sent from my N7 2k13
[Nexus 7 (2013) Original Android Development] rubene66:
This is definitely the best kernel for gaming runing 1.89 and 600 gpu stable
[Nexus 7 (2013) Original Android Development] sader2202:
This what I got, I'm running it at 2052 max and 486 min but for some reason the gpu won't go above 487 even though I try setting it higher and antutu always cause a reboot when ever I run it. It get to 14% and then it shuts off.
[Nexus 7 (2013) Original Android Development] Crwolv:
Suggestion.... Read ahead I put at 6114 ,and interactive governor is a MUCH BETTER governor and battery saver at the same time. Interactive governor ramps down much much much faster than on demand governor. That's where you get your battery saver and interactive governor ramps up to wherever it needs to be at the same speed as on demand governor does. So see with interactive governor you get the same performance but battery saving because it works Les because it gets down to the bottom Hertz faster much faster. Also snapdragon processors love and run best on cfq. Just so you can see with the attached picture I am NOT overclocked at all I just have the settings I just mentioned running. Oh and by gosh make sure Mpdecision is off. Actually XDA premium is telling me I need to login to attach a picture even though I'm already logged in writing this message I will try to attach picture and another message below this
[Nexus 7 (2013) Original Android Development] Crwolv:
Here it is I am NOT overclock I just have the settings in the above message
[Nexus 7 (2013) Original Android Development] penguin449:
No difference bro :p

Sent from my N7 2k13
[Nexus 7 (2013) Original Android Development] asrah:
1.836GHZ CPU/545MHZ GPU. 2048 RA buffer, no UV, no MP Decision, max L2 OC.

Interesting issue with the kernel. After a bunch of FC's and soft reboots after flashing the kernel properly, it runs stable at 2.3GHZ/627MHZ OC. So boot troubles, but its completely stable during gaming. I play Nova 3, Critical Strike Portable, Asphalt 8, NFS MW, and BF BC2.
[Nexus 7 (2013) Original Android Development] thunderger:
My N7 runs well with 1,9 GHz, 487 MHz GPU. Fast enough for everything, little UV. :) One thing I wish to have is faux color interface support.

As I noticed this fake S4 is a fixed variant so all C-states are working well and my N7 can "deeply" sleep without any issue oder sleep of death. :)

Nice work, perhaps there will be a first stable variant in the near future and after this a new beta version with some patches from later linux kernels or other tweaks from other s4 / s600 kernels, e.g. N4...
[Nexus 7 (2013) Original Android Development] jordirpz:
+1

Enviado desde mi Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] penguin449:
Is the snapdragon S4 pro, yet another cpu which is built with variants/qualities, because i can't even boot at 2.3ghz, and even if i do, if i try run antutu at anything above 1.89ghz it just reboots, and then gps wont work, and gapps stop, then any higher and sys ui stops? Using Carbon.. is it a Rom issue? or a kernel issue?
[Nexus 7 (2013) Original Android Development] asrah:
We had a PM conversation about this. Ive narrowed things down a bit, and it looks like the device wont boot properly fi certain CPU settings are AVAILABLE, even if they arent active. i brought my max CPU down to 1.89GHZ, and ive had no boot troubles. Unfortunately, it seems like were stuck booting with max 1.89GHZ available setting. I was gaming on my device for a good 4 hours the day i talked to you. Had the CPU at 2.3GHZ, and the GPU at 627. There was no instability except at boot time. Played Critical Strike Portable at max graphics at 30-50FPS. Thats amazing performance considering CS:P has the GPU render every single bit of the map at the same time. It does that to help with FPS stability.

I had 6 hours screen time on the 100% charge from that morning. Thats some nice, stable gaming with great battery life on auto brightness. Keep in mind, its rather bright in Texas, during the day.

*$M3RT$* Just reflash the kernel, and remember to wipe cache/dalvik cache, and fix permissions each time you flash a kernel. Eventually the kernel will retain the settings you apply.

Try gaming at 2.3GHZ and whatever max GPU OC you can set. I couldnt get antutu to work, either. Quadrant worked perfectly, at max OC, though. Im not exactly sure why i could game at max OC settings, but he device wouldnt boot properly.

*$M3RT$* do you wipe cache, dalvik cache, and fix permissions after you flash the kernel? If you do those steps enough times, eventually the kernel will retain the settings. It took me a few flashes to test settings, and the settings randomly started keeping after reboot.

Thunderger, the S4 in this device isnt fake. There were some tweaks and specs changes so the CPU would perform better in a tablet.
[Nexus 7 (2013) Original Android Development] penguin449:
Why can't you ditch the Aroma installer? It's forever crashing! instead of setting max OC why not just make a multi freq, because at least then we can choose after and it will only stick at stock on boot? UV to 850, and Fastest L2 and Bus.. like a performance variant, i hate aroma, i prefer just being givn the boot.img because it means you can set, and see what instabilities you have?

Please you could make a performance variation of Glitch? Like have it as no Aroma. multi freq, no/little UV, fastest L2 and bus, ondemand/interactive/performance/cfq/row/sio? Full GPU OC but set as stock for boot? allow d2w and s2w/s2s and that from trickster?
[Nexus 7 (2013) Original Android Development] asrah:
That would be nice. I would prefer no UV. Some devices might have random reboots at otherwise stable settings. I tried the 850UV with my current 1.89/545 settings, and i got a couple reboots during gameplay. If you dont game, it should be fine. I personally want to utilize this amazing tablets hardware to the fullest.

On another note, take a look at how this tablet compares to the HTC One at my current settings. 1.836GHZ CPU/545MHZ GPU. 2048 RA buffer, no UV, no MP Decision, max L2 OC.
[Nexus 7 (2013) Original Android Development] vince2008:
I know how that fun feels like if you achieved high scores...comparable with snapdragon 800 chipsets.
[Nexus 7 (2013) Original Android Development] XsceneXhippieX:
for general reference, i can no longer successfully flash bionic/dalvik libs from the moto x on my N7 (2013) or my N4 after about 3 days ago with literally any ROM updated since then, regardless of the aroma install or not. no idea what happened but when i stopped installing the libs, i stopped getting boot loops on both devices, and ive been installing them on top of every rom for months now with no issues.
[Nexus 7 (2013) Original Android Development] kingston73:
For everyone complaining about the bionic option not workng anymore, maybe your rom has integrated it? And did you really notice a difference in everyday use? IMO benchmarks are useless.
[Nexus 7 (2013) Original Android Development] nokiagye:
Exactly the same here on two devices

---------- Post added at 07:37 AM ---------- Previous post was at 07:32 AM ----------

Yes the rom have it but the roms patches are not the same I lose 3000 of quadrant

Yes the scores means nothing but for some people like to beat more powerful devices

As I say it have fun
[Nexus 7 (2013) Original Android Development] killflaker:
2D score 3000pts?? How??

Normal 2D score is 1500/1700pts with or without overclock
[Nexus 7 (2013) Original Android Development] SickBeast:
Maybe the new beta driver.
[Nexus 7 (2013) Original Android Development] matcho13579:
No way, I flashed the drivers and I cannot achieve 2D score like this. But you know what? Screw the Antutu score, my tablet runs great and that's what I want
[Nexus 7 (2013) Original Android Development] nokiagye:
For what drivers you talking?

---------- Post added 7th March 2014 at 12:21 AM ---------- Previous post was 6th March 2014 at 11:45 PM ----------

I have one reboot yesterday https://www.dropbox.com/s/l7ht6pthqkjedys/bugreport.zip

And one today is from rom kernel I don't know so I post here

https://www.dropbox.com/s/l7ht6pthqkjedys/bugreport.zip

For the first log a friend from rom threat say me that the reboot reason is power button pressed but I didn't press it
[Nexus 7 (2013) Original Android Development] SickBeast:
Dalvik and bionic patches?
[Nexus 7 (2013) Original Android Development] SickBeast:
I have discovered that overclocking beyond 1.9ghz is completely pointless on this tablet. I get the same scores in geekbench and sunspider even at 2.1ghz. I think that we are limited by heat and thermal throttling.
[Nexus 7 (2013) Original Android Development] matcho13579:
No, I was talking about new Adreno drivers
[Nexus 7 (2013) Original Android Development] SickBeast:
I realize that; I was wondering if the Dalvik/Bionic patches were the reason for the higher score. I have also noticed that Dalvik gets much higher scores in Antutu compared to ART.
[Nexus 7 (2013) Original Android Development] apicia:
That's strange. I get better real world performance using ART over dalvik on my devices (measured by how smooth a 3D game called Golfstar runs).
[Nexus 7 (2013) Original Android Development] SickBeast:
Real world usage is much faster with art but for some reason antutu gets higher scores with dalvik.
[Nexus 7 (2013) Original Android Development] Trevomader:
I used to underclock to 1026000 at r141 by changing the config file directly.

But in r142 if i do that all cores stay permanently online at 1026000 clock even at idle with ondemand governor, other governors doesn't seem to have this issue.

Using Trickstermod doesn't work because the clock keeps raising to 1512000 even though the max is set to 1026000.

So anyone know how to underclock at r142 using ondemand governor without making it behave erratically?

Thanks in advance.
[Nexus 7 (2013) Original Android Development] MadMatt89:
It seems like I don't have these lag issues on Elementalx...
[Nexus 7 (2013) Original Android Development] kingston73:
It's people like you who make devs want to quit helping the community. What's the point of your post? Who are you helping by saying that?
[Nexus 7 (2013) Original Android Development] just lou:
Then go use it.
[Nexus 7 (2013) Original Android Development] danaff37:
And this one is by far the smoothest on my nexus. Please leave the thread if you're going to act like that
[Nexus 7 (2013) Original Android Development] kingston73:
I just want to confirm before buying, slimport works with the caf version of this and cm11?
[Nexus 7 (2013) Original Android Development] 3dawg:
Yes.
[Nexus 7 (2013) Original Android Development] creeve4:
[MENTION=3847629]Tk-Glitch[/MENTION] any plans to add cifs support?
[Nexus 7 (2013) Original Android Development] thereal_bigjake:
Sounds like your hardware is failing, better send it in for a replacement as this kernel is fast, smooth and battery friendly :o
[Nexus 7 (2013) Original Android Development] apicia:
I just received one and was very disappointed. It had the red and blue spots. Also, I was very disappointed with the contrast and black levels. What good is all that delicious resolution if the display is washed out with monochromatic blacks.