yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] flar2:
I don't think so, it's needless complexity and probably not necessary on a tablet. From my testing, having dt2w or s2w enabled only drains an extra 0.2 or 0.3% battery per hour.
[Nexus 7 (2013) Original Android Development] cobyman7035:
i just checked the OP to see if any newer then v2.6 final, don't really have time or too lazy to read through all threads lol, maybe i'll for 3.0 final! 2.6 is pretty good to me, overlocked to 1.7 and undervolted a bit and it runs like a beast with OK like stock battery life:good:
[Nexus 7 (2013) Original Android Development] Cryptecks:
If you literally just read the few posts RIGHT above yours, you'll see that flar2 has released 2.9, and it's lean and running well on my tablet... but to each his own I guess.
[Nexus 7 (2013) Original Android Development] xda890:
Ok, guess it wil have to do, thx... :)

BTJ
[Nexus 7 (2013) Original Android Development] Orihalcon:
Sweet. New updates :)

2.9 loaded on cleamrom. Running like a beaut!

Thanks flar2!
[Nexus 7 (2013) Original Android Development] waz675:
Cheers to commentary about thread title. 2.9 is working nicely so far on my flo, even though I've only installed it, used it for 10 or so minutes, then slept. Now I've used it for about a similar time, stomach still feels a bit average so not crash hot on using my androids.

I'll do more testing when I take the kids to a local "indoor play centre" so they get to run around and not destroy our house (win!) while my wife has gym and some other chores. It seems cool so far, but early days obviously for battery and user experience from the kernel change.
[Nexus 7 (2013) Original Android Development] Sensamic:
Went back from 2.6 to 2.4, where I had amazing battery life.

Been on 2.6 for 2 weeks and battery life was much worse than on 2.4.
[Nexus 7 (2013) Original Android Development] konradsa:
Flar2, I am on 2.9 now, and it still seems dimmer, compared it to 2.7. ? Anybody else can confirm?
[Nexus 7 (2013) Original Android Development] flar2:
Really? I went back and forth from stock a few times and couldn't tell. It should be the same if backlight_dimmer is 0.
[Nexus 7 (2013) Original Android Development] konradsa:
Well, in my case definitely. I use the Lux app, and even with a 20% bias it's not as bright as before. When installing the kernel, I deselect all the s2s/s2w/dt2w options, but don't think it's should have anything to do with that.
[Nexus 7 (2013) Original Android Development] manueltts:
First time flashing this kernel, over stock first and then over PA 4.2beta1. I'm playing around and enjoying features. Specially 2wake/2sleep stuff, battery charge 93% limit. Performance & battery drain I'll test tomorrow while in normal use. I flashed only the 2.9 version, and have the issue mentioned above both times (TWRP 2.6.3 & 2.7). Besides the scary BSOD moment, seems everything works like a charm.

Cheers!

Manuel
[Nexus 7 (2013) Original Android Development] paaaulo:
Make sure if automatic brightness is enabled. For some reason it turned itself off on my device.
[Nexus 7 (2013) Original Android Development] konradsa:
Like i said, using the Lux app for auto brightness. Dont have a reference point for the normal auto brightness, haven't used it in months, but with lux the screen is much darker now, so bad that i had to go back to 2.7.

Flar2, i was one of the probably few ppl that had installed the initial 2.7 (not 2.8!) release that had the dimmer bug where it was enabled by default. Is there maybe a bad file left on my device causing this? The value in the cfg file is set to 0.
[Nexus 7 (2013) Original Android Development] cobyman7035:
i've downloaded v2.9, but not installed yet... hows battery compared to previous eXs? thx
[Nexus 7 (2013) Original Android Development] waz675:
Second days use, battery at 83% with 2hours and 2 minutes screen on time, 3 or 4 hours since I took it off charge. So far its looking good for me, has been good (projected) battery. Kids and wife out tomorrow so I'm home alone, if I'm still too unwell to ride my motorbike, I'll spend most of the day sussing out the tablet while I'm not doing website work.
[Nexus 7 (2013) Original Android Development] GSLEON3:
Set the low reference point in lux (Backlight zero point) to a higher level & adjust your profiles. I use Lux & it works superbly for me & the excellent dim mod make night reading soooo much more comfortable. No issues at all with this Kernel & Lux on the N7 or the N5,
[Nexus 7 (2013) Original Android Development] opee:
I have force closes since 2.7 in real racing! After reboot the game start correctly... What can I do?

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 7 (2013) Original Android Development] mdamaged:
Are you overclocking the cpu or gpu and/or undervolting?
[Nexus 7 (2013) Original Android Development] opee:
Nope!All stock! With 2.6 all things are good!

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] Leviatano:
What versione is better 2.6 or 2.9 in smoothness and battery life?
[Nexus 7 (2013) Original Android Development] konradsa:
OK, but I should not have to mess with my lux settings at all with bld=0, behavior should be the same between 2.7 and 2.9. Anyways, since I seem to be the only one with this problem, I will try and wipe boot and system on the weekend, reinstall the kennel, and see if that fixes it.

---------- Post added at 05:51 PM ---------- Previous post was at 05:37 PM ----------

Flar2, I noticed that the name of the option in the config file has changed from BL in 2.7 to BLD in 2.9. Could that somehow have messed it up for me?
[Nexus 7 (2013) Original Android Development] El Nino1977:
Using 2.9 and RR3 works fine, I'm addicted to that game and only had issues with it FC'ing when I UV'd too much.
[Nexus 7 (2013) Original Android Development] flar2:
I don't think there is anything else that would change that setting.

You could look at /sys/module/msm_fb/parameters/backlight_dimmer and see what the setting is

I had to change the config name because BL already appeared for the battery life extender BLE and those two settings were conflicting. Should be fine in latest version.
[Nexus 7 (2013) Original Android Development] konradsa:
Yes, there is an issue: on the second 2.7 release, where I don't have an issue, the value is N, but on 2.9, the value is 7, even though the conf has BLD=0.

When I do an echo 0 to the value, the brightness becomes normal.
[Nexus 7 (2013) Original Android Development] flar2:
For me, it's 0. I think I know why you're getting a value of 7 and others aren't.

When I compiled the kernel, I forgot to change the default value of the backlight_dimmer to 0, I left it at 7, which is what I felt would be a good default with it enabled. If the init.d script is not running at boot, the backlight_dimmer will default to 7. The init.d script needs to run for it to be changed to 0.

My guess is that there is something wrong with your installation of busybox. There was one version of busybox that had a problem running init.d scipts. You need to reinstall the latest busybox from within the busybox app (not just from the Play Store).
[Nexus 7 (2013) Original Android Development] konradsa:
I think you hit the nail on the head, thank you! That would also explain why s2w is always enabled, even though I deselected it in the install script. I always have to turn it off with Trickster.

But it looks like I have the latest busyox installed, 1.22-1, there is no update available in the app? Any other idea why init.d may not run? The only thing I can think of is that I tried out glitch kernel for a couple of days, but went back to ElementalX afterwards.
[Nexus 7 (2013) Original Android Development] mdamaged:
When you switched kernels, did you go back to stock kernel first before going back to ElementalX?
[Nexus 7 (2013) Original Android Development] konradsa:
Nope, I didn't. Probably should flash boot I guess and reinstall ElementalX.
[Nexus 7 (2013) Original Android Development] mdamaged:
Yup, I would try that, due to the possibility of ramdisk changes, along with system.img (in your case either the one you used with ElementalX or the stock), you should have made a nandroid of system and boot before moving to glitch, if you did not, then you will have to flash stock boot and system, and redo your changes (like xposed, etc if applicable).

I always flash stock kernel AND system.img before changing custom kernels, just in case, like in the case of ElementalX it changes system, and so does franco, and Glitch might too (not sure). So when you just change boot you may still have a system partition that is missing or has extra things in it.
[Nexus 7 (2013) Original Android Development] flar2:
It could be a problem with the ramdisk, as this is where the command to run init.d scripts is.

You should always start off with the kernel that came with your ROM because I will reuse the ramdisk from the currently installed kernel. I don't know about the Glitch kernel, but it definitely causes problems if you install this over franco kernel.
[Nexus 7 (2013) Original Android Development] semdoc:
First of all .. I would like to thank you for your great work :)

I have a little bit stupid question...

Is there a way to enable backlight dimmer using any 3rd party app?
[Nexus 7 (2013) Original Android Development] mdamaged:
Any app that can echo a number in /sys/module/msm_fb/parameters/backlight_dimmer will work, for example, Franco's Per-App mode app allows you to add configurables. I think that's what you meant.
[Nexus 7 (2013) Original Android Development] konradsa:
Yep, that was it. After going back to stock boot/system and reinstalling elemental, everything is working as expected now. Thanks again for your help.
[Nexus 7 (2013) Original Android Development] morbidj:
[MENTION=4684315]flar2[/MENTION] are you able, or have you considered the time out trigger for double tap wake? I really love that feature on your N5 kernel!
[Nexus 7 (2013) Original Android Development] El Nino1977:
Flar, something funky going on... Stock rom and your v2.9 installed, no uv and aroma installation with recommend setting applied. In gplus app I get a weird gfx glitch. I'll investigate more later, ofc to work now.
[Nexus 7 (2013) Original Android Development] Bobbi lim:
I tried to install this kernel on my nexus 7 2013 but it seems like installation keeps getting aborted. At first I thought it was due to CWM than swapped over to TWRP and still face the same issue. Can someone advise me on what should I do to be able to flash this kernel?
[Nexus 7 (2013) Original Android Development] El Ha$on:
When I installed 2.9 on stock ROM at the very end of the installation, pretty much when the installation is over the tablet would shut off completely. I rebooted into recovery and tried again and the exact same thing happened. So I just preceded with booting into the OS and everything was fine. It installed correctly not sure why it shut down at the end of installation.
[Nexus 7 (2013) Original Android Development] rom08:
It's a twrp recovery problem. You have to disable screen timeout in it.

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] teddy0209:
It happens with twrp, just wait a little more and it will come back to life with unlock screen of twrp...
[Nexus 7 (2013) Original Android Development] Ellobo24:
It just happened to me too..with version 2.6 and 2.8 but what i did was i delete delvik cache and cache and 2.9 fix the problem for me..so what you should do when it happens is turn it back on with the power and down bottom turn it on so you can go to the bootloader and restart it to the TWRP and do it again untill it flash correctly..hope this help ;)
[Nexus 7 (2013) Original Android Development] balekoglu:
Where is the link for 2.9?

Nexus 7 cihazımdan Tapatalk kullanılarak gönderildi
[Nexus 7 (2013) Original Android Development] mdamaged:
http://xdaforums.com/showthread.php?p=51170584#post51170584
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
[MENTION=4684315]flar2[/MENTION] I have had two random reboots so far on 2.9. Please take a look and advise. Last boot reason : watchdog . https://www.dropbox.com/s/rn0qyps0kw35dm2/last_kmsg.log
[Nexus 7 (2013) Original Android Development] flar2:
I can't see drop box until I'm home from work, but if it's watchdog, it could be something in the system.

I also have suspicions about the gamma control, it was giving a few people problems on HTC One. I have a solution for that.

My other question: are you using CM/CAF based ROM still? There may be additional commits necessary to make it completely stable. On the other hand, I've been running 2.9 on CM for the past week and it's been rock solid.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
What do you think is the issue? System meaning the rom?

No, I'm running Carbon, which is aosp based. And btw, there are additional commits needed for cm, but the two you've added to your source just fixes the colors. There are multiple other commits and it is tedious to find and add all of them, you'd better off forking cm's and then adding your stuff over it, like I've seen a lot of devs do.
[Nexus 7 (2013) Original Android Development] flar2:
Lots of things could cause watchdog to reboot, no idea. I couldn't find any kernel errors in the log.
[Nexus 7 (2013) Original Android Development] flar2:
This should be the last change for a while (until google sends an update)

Download:

Stock/AOSP:

ElementalX-N7-2.10

Cyanogenmod/CAF:

ElementalX-N7-2.10-cm

Changes:

-make color/gamma optional
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Ok. I was using non-stock settings, trying 2.10 with all stock/default settings.

Question : If I wanted BLE set to charge till 98%, how much voltage do I set? will it work since you've configured it only upto 93% ?
[Nexus 7 (2013) Original Android Development] Gareee:
Late to the party, but 209 non caf on linareo cm was giving me really bad video playback issues, and I finally had to go with the stock cm kernal.

I'll try 2.10 and post if those issues are now gone.
[Nexus 7 (2013) Original Android Development] SickBeast:
Interesting kernel, thanks very much, flar. I'm stable at 1.7ghz whereas I was not with the glitch kernel. This kernel also seems faster than the glitch kernel even though it overclocks the gpu and the cache much higher.
[Nexus 7 (2013) Original Android Development] LinearEquation:
I'm running odex SinLess ROM 4.4.2 with 2.10 ElementalX and I can run my Nexus 7 at the highest clock setting stable. Combined with bumping the GPU clock I run mid 29's on a bench. I don't put a lot of weight into that kind of test but it is fast. Unrealistic for daily use though.
[Nexus 7 (2013) Original Android Development] syu78:
Thanks for a great kernel! I've been running every version of this kernel since 2.6 and everything's been great along with SinLessROM v3.2.2. However, after upgrading to 2.10, I noticed two things.

First, USB fast charge is not enabled even though I selected it during installation. I can change it in the elementalx.conf and fast charge is enabled after a reboot.

Second, it looks like my system defaults itself back to deadline scheduler from ROW after about 15sec from a reboot. I selected ROW and confirmed it in the elementalx.conf file, but it keeps switching back to deadline. I have the Trickster app, but I don't have it set on anything during boot (I actually have it set on boot to change the scheduler from deadline back to ROW for now.)

Any suggestions? Thanks in advance.
[Nexus 7 (2013) Original Android Development] waz675:
I use trickstermod with a 45 second delay to change stuff on boot and that holds settings for me
[Nexus 7 (2013) Original Android Development] Ivanbarker:
Perfect update. Makes my lux auto brightness perfect. Thanks very kindly!
[Nexus 7 (2013) Original Android Development] Gareee:
I tried this with the linaro version here:

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

and got nothing but sluggish boot screen, and no actual boot.

Is there something funky going on between these two?

(I've been running 2.6 with it fine)

2.9 gave me slow video playback issues
[Nexus 7 (2013) Original Android Development] Brembo109:
Correct me if i'm wrong, but as I understand PA for Flo is CAF because of its CM base. Right? I can't find this info in the PA threat so I tested both versions and the non-CAF version of this kernel works with PA and the CM/CAF version not. So, is PA no longer based on CM? Maybe I missed that info

Gesendet von meinem HTC One mit Tapatalk
[Nexus 7 (2013) Original Android Development] Gareee:
Now I'm confused.. I'm wondering if I shouldn't be trying to use the cm version of element x on the version of cm I'm using. Anyone know for certain?
[Nexus 7 (2013) Original Android Development] Marescallus:
PA is AOSP, not CAF.

If you're using straight up CM, use the CAF version.
[Nexus 7 (2013) Original Android Development] Brembo109:
Okay thanks. So my confusion is cleared :D

Gesendet von meinem HTC One mit Tapatalk
[Nexus 7 (2013) Original Android Development] Dan1234567890:
Sorry for noobing, flar said that for gamma control we should use faux clock app, but on the playstore I can only find this one... Is this faux clock app? It is called faux 123 kernel enhancement apphttps://play.google.com/store/apps/details?id=com.teamkang.fauxclock
[Nexus 7 (2013) Original Android Development] mdamaged:
Yes, it is.
[Nexus 7 (2013) Original Android Development] Marescallus:
Yes it is.
[Nexus 7 (2013) Original Android Development] Dan1234567890:
Thank you for the quick answers! [emoji2][emoji2]

In the app there are no color profiles, do you have some profiles that look good on our N7...?

Like Iphone5 or bundi for N4 or something like that?

Thank you once again! [emoji106]
[Nexus 7 (2013) Original Android Development] mdamaged:
Actually, I just bought the app recently, have not had a chance to run through my calibration video kit yet. I use videos from here to calibrate, along with this manual, not sure how much of it will apply to the settings I'm limited to but it's somewhere to start from.

I don't have an iphone5 to compare either.
[Nexus 7 (2013) Original Android Development] Gareee:
Originally Posted by Gareee View Post

Which does not work with the cm version I'm using

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

It sounds like the author removed screen setting options, and that might be causing the instability issues. 8(
[Nexus 7 (2013) Original Android Development] NovaSlim:
Have you checked the screen timeout settings? You need to disable screen timeout for the aroma installer to work.
[Nexus 7 (2013) Original Android Development] Marescallus:
I'm pretty sure you can use either, because of what the OP says. As for your instability issues, I have no idea.
[Nexus 7 (2013) Original Android Development] flar2:
Of course it's not normal. Check your frequency and voltage settings.

I've never had a random reboot even during testing. The kernel is 100% stable.
[Nexus 7 (2013) Original Android Development] Mr. Droid:
Ya will check but my tab just died on me it kept rebooting and now i just have a black screen.

Tablet is not turning on, anyway to hard reset ?

Power button + both volume to reset?

EDIT:

Tablet is back on, going to restore the Faux kernel and reset settings then flash this
[Nexus 7 (2013) Original Android Development] flar2:
Make sure you try stock settings to rule out overclocking and undervolting.
[Nexus 7 (2013) Original Android Development] boykomac:
Thanks guys, I just installed this kernel. The swipe to lock / unlock feature is awesome!
[Nexus 7 (2013) Original Android Development] L1lyksd@ddy:
This is a build quality issue, search the general section. I returned my first one to best buy that was pure stock and flickered intermittently.

Deffinately not a kernal issue.

By the way, flar all of your kernals are rock solid! Love your work.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Looks like I've got the reboot issues too. Flashed it this morning. V.9. Rebooted while listening to spotify. Stock frequencies, no l2 oc, no other mods, stock ROM. No undervolt.
[Nexus 7 (2013) Original Android Development] p4rot:
No screen flickering here neither, I only got a random reboot , not sure if it as something to do with the kernel.
[Nexus 7 (2013) Original Android Development] flar2:
I will need to see /proc/last_kmsg.

However, I didn't change anything substantial in 0.9 that would cause reboots. The only thing I can think of are heat issues. I changed /etc/thermald.conf to allow it to get hotter. Overheating can certainly cause reboots.

I recommend people stick with 0.8 for now.
[Nexus 7 (2013) Original Android Development] flar2:
I forgot to answer this earlier...

The advantage is faster memory. The risk is the same as with any overclocking. There is no specific risk of data corruption.

The risk of data corruption on PCs when overclocking the FSB is an old thing that comes from the PCI clock being tied to the FSB clock. Increasing the FSB frequency would increase the PCI bus frequency where hard disks used to be connected. And you would get data corruption.
[Nexus 7 (2013) Original Android Development] usoppp:
the screen flicker wasn't an issue with the kernel after all, i tried installing every other kernel but it didn't fix it, so downloaded factory image, rooted and installed this kernel back. no issues so far. thankgod i didn't have to return this back. anyway awesome kernel! looking forward to more updates :good:
[Nexus 7 (2013) Original Android Development] p4rot:
I think I will stay with 0.9 but if many reboots occurs I will go for 0.8
[Nexus 7 (2013) Original Android Development] acdcking12345:
Installed this for the first time. I gotta say that it gave me back the one thing I missed from my Sony Xperia Z Tablet. Double click to wake. Absolutely missed that feature. Thanks you for the great Kernel!

Oh and two question. I assume that if we select to accept the GPU OC, it will auto OC without an app?

And in regards to the OCing of the CPU, DO we still need to use an App to designate the governor\CPU settings? Or is that all set directly within the kernel?
[Nexus 7 (2013) Original Android Development] boykomac:
I have been playing etrernity warriors 2 for hours on 0.9 and did not experience any reboots at all so far. The device does get hot but not much hotter than with the stock kernel.
[Nexus 7 (2013) Original Android Development] masri1987:
Was wondering if we can get smartmax governor
[Nexus 7 (2013) Original Android Development] BFirebird101:
I'm sure this has been already posted, but how are you guys recently doing on battery life in comparison to the stock kernel?
[Nexus 7 (2013) Original Android Development] masri1987:
Oh and may we please add dynamic fsync?
[Nexus 7 (2013) Original Android Development] thecdn:
I initially used 0.8 then went to 0.9. Double tap is working great but swipe to wake has never worked. Is there a switch or setting I'm missing?
[Nexus 7 (2013) Original Android Development] Artood2s:
Anyone getting the max CPU freq when streaming video? What governor/settings do you guys recommend to reduce this behavior? I don't think all that processing power should be necessary.

Sent from my One X
[Nexus 7 (2013) Original Android Development] flar2:
Sorry, I won't be adding those. I only add essential stuff. There is no performance gain on modern ssds by disabling or delaying fsync. It's so fast you won't notice it. Disabling fsync is an old trick from the days of slow hard drives.

Check out the video in the second post. It works 100% if you sweep in the right spots.

This is probably the default behaviour, I'll have a look.
[Nexus 7 (2013) Original Android Development] thecdn:
I was using to short a sweeping motion. Works great, thanks.
[Nexus 7 (2013) Original Android Development] djbenny1:
Been using the kernel with clean rom for about a week now. Battery life has been very poor tho and as I said in the clean rom thread, im not sure whether kernel or rom settings are to blame.

I get 30 hours with virtually no use, wifi on from full charge to 0.

Any tips or things to look for?
[Nexus 7 (2013) Original Android Development] mdamaged:
Install BBS and see what's doing it.