yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] celkin:
Hmm, maybe i will (after assessing current battery life) take a back step a few days on the nightlies... Have grown quite accustomed to 7-9 hours screen on time with tap to wake... The power button on the Nexus 7 is awkward and poorly placed. Quite irritating to use actually :(

Sent from my i337m rockin Kangabean
[Nexus 7 (2013) Original Android Development] GSLEON3:
Yeah, between Flar's wonderful kernel & Paranoid Android, well, I'll take those two over CM & their corporate move any day of the week. PA will continue to grow & expand, while official CM moves more towards trying to please OEM's & carriers. Oh well, I am thankful that CM was around to help inspire PA into what it is becoming.
[Nexus 7 (2013) Original Android Development] iammodo:
Can the kernal be updated to work with cm? Really want the slide to wake feature to keep working.
[Nexus 7 (2013) Original Android Development] GSLEON3:
No. It would take a separate build, which then means maintaining two branches for each device. I mean it is possible for Flar to build one for CM, just a PITA to have to do everything twice for each device. Then again, all you can do is ask Flar, the worst thing that happens is you get an answer you may not like.
[Nexus 7 (2013) Original Android Development] klaust58:
This kernel don't work with Carbon (CM) after last nightly?

:crying:
[Nexus 7 (2013) Original Android Development] -viperboy-:
A user just confirmed this at the top of this page.
[Nexus 7 (2013) Original Android Development] flar2:
Fragmentation.

Unfortunately, I don't think I have enough time to maintain a separate cm-based kernel. The real problem with that is I like to work from a stable base, which I get from Google/AOSP. The cm source is now constantly changing and potentially unstable or broken at any point in time. I bought this Nexus device because I know I will always get the real, actual complete, totally stable kernel source on the day it is released. No constant messing around trying to fix stupid broken stuff like on HTC phones. No questions about whether the kernel will work on this ROM or that ROM. Now Cyanogenmod goes and breaks that nice situation.

Cyanogenmod is in my bad books now.
[Nexus 7 (2013) Original Android Development] Philaphlous:
Just updated busybox for the first time after rooting this, hopefully that'll stop my random reboots.

Odd thing, anyone else gets failed updates? Says the zip wasn't installed but it actually does install I believe... Well tahats what twrp says...
[Nexus 7 (2013) Original Android Development] Slavon-93:
I've got two questions about this kernel.

1. After installing latest PAC Rom for Deb, latest GApps and ElementalX-1.6, I can't change the frequencies. Trickster just says "Applied successfully" but after I close it and reopen, it shows 1026MHz for screen off whatever I set before. Everything else changes successfully. This problem doesn't seem to be on v1.4 though I'm not sure anymore.

2. After flashing any version, AROMA closes and Nexus actually seems to reboot, but unsuccessfully. I mean the screen turns off, and nothing happens. I have to hold the power button for some time and after that everything seems to be ok. Is it normal? Sometimes (after I flash the kernel again without any wipes) the AROMA closes and I see buttons in TWRP like Reboot system, home etc.
[Nexus 7 (2013) Original Android Development] nrage23:
Aroma is notorious for not finishing or going back to recovery properly. It is not the kernel just something with Aroma itself. Aroma has been quirky on every device I have used it on. On my old Rezound the device had to be laying flat or the Aroma installers would not work right.
[Nexus 7 (2013) Original Android Development] dud3me:
Just installed the latest beta and noticed that the stock settings in aroma over clock gpu to 450mhz. Is gpu oc dangerous? And is it running at different steps throughout different usage? Like it will go to max when playing demanding games etc. but runs on lower steps otherwise?

I'm asking cause I've never oc'd gpu before and was wondering. It will probably deteriorate gpu faster over time but I doubt that's too bad at this low oc. I'll probably just stick to stock 400mhz anyway since I'm not really a hc gamer. Oh and the kernel is running great too! ;)
[Nexus 7 (2013) Original Android Development] tni.andro:
Battery Life Extender

FYI, kernel patch for Battery Life Extender functionality:

http://xdaforums.com/showthread.php?p=46160175
[Nexus 7 (2013) Original Android Development] jugster:
How does it deteriorate?

Signature? Signature!
[Nexus 7 (2013) Original Android Development] poondog:
Overclocking can be bad for the CPU/GPU if done too much. Because factory spec is different and you're pushing boundaries
[Nexus 7 (2013) Original Android Development] tni.andro:
Transistors/chips age; that process is faster with higher frequencies/voltage/heat. E.g. for technical background:

http://spectrum.ieee.org/semiconductors/processors/transistor-aging/0

That's generally not a problem. What may be a problem is thermal cycling. When overclocked, the processor/GPU will heat up faster and that increases stress on solder joints, which may fail over time. There have been graphics cards and phones with high failure rates due to solder joints going bad.

Anyway, my CPU and GPU are overclocked, I'm not sufficiently worried.
[Nexus 7 (2013) Original Android Development] jugster:
That entire text does not address the question at all actually.

OK, thank you!

For me the danger with overclocking is mostly about frying the chip altogether actually. I've never been to concerned with a CPU operating out of specification as long as it is operating. I think the extra wear is so small, the chip will be outdated before it has any effect.

All chips are unique though and your mileage will vary.

Signature? Signature!
[Nexus 7 (2013) Original Android Development] vcallas:
Have downloaded and installed ElmentalX beta 1.6 and so far is running great. Thanks for all the hard work.:)
[Nexus 7 (2013) Original Android Development] Crwolv:
Turn off mpdecision.

Sent from Pimped N7 (2013) XDA PREMIUM

---------- Post added at 09:35 PM ---------- Previous post was at 09:33 PM ----------

I get much better ALMOST EVERYTHING with it off lol. Unless your a kernel settings noon:(

Sent from Pimped N7 (2013) XDA PREMIUM
[Nexus 7 (2013) Original Android Development] gravedigger76:
[MENTION=4684315]flar2[/MENTION]

Is there any chance to get the multiboot patch added to this awesome kernel?

Here is the thread for MultiBoot

And the Patch: Here

this would be totally awesome!

thank you
[Nexus 7 (2013) Original Android Development] tiny4579:
It is there in v1.6 - beta - already.
[Nexus 7 (2013) Original Android Development] gravedigger76:
Sweet! excelent!

Is it pretty stable? 1.4 is running just perfect for me..
[Nexus 7 (2013) Original Android Development] tiny4579:
I'm not running it yet. On slimbeans kernel right now. Just trying to help.
[Nexus 7 (2013) Original Android Development] BigJPNut:
I think Trickster is buggy. It say 1026 MHz low frequency for me too, but CPUSpy app shows me spending time at lower frequencies. And I believe mpdecision is on by default that's why you get better EVERYTHING.
[Nexus 7 (2013) Original Android Development] El Ha$on:
Not sure if this is kernel related. But all of a sudden my USB-OTG isn't working anymore. It was working perfectly but haven't used it in a couple days. Plugged it in today to find out its not being read.

I was on the beta 1.6 but since it wasn't working I tried the last stable build 1.4 and nothing either. Currently on CleanROM Any ideas??

To ensure it wasn't the cable I plugged into my DNA and its works perfectly.

Sent from my Droid DNA on 4.3!!!
[Nexus 7 (2013) Original Android Development] Crwolv:
I just TOLD you I get better everything with mpdecision OFF,i clearly stated that,makes me wonder if you cant understand me........mpdecision ,its what keeps lower frequency set so high,follow Franco and faux suggestions there awesome peeps(many others also). Lol

Also I've used trickster for a loong time and have never had a problem,he even supports a device soon after requested. Get the premium,its most likely user error or kernel error because I am aflashaholic on 6 devices and faux kernel apk and trickster apk are STELLER.

Sent from Pimped N7 (2013) XDA PREMIUM
[Nexus 7 (2013) Original Android Development] gravedigger76:
It sux, CM is doing this. there has been a lot of chatter about this. Hope they will change their minds at least for flo/deb and other pure nexus devices!

What are the changes of that?

:good:
[Nexus 7 (2013) Original Android Development] -viperboy-:
Zero.
[Nexus 7 (2013) Original Android Development] nikr123:
Don't know but have you checked if you have host mode charging enabled?
[Nexus 7 (2013) Original Android Development] rocksyjj:
Using the 1.4 version on clean rom this is very snappy indeed

keep up the great work on this looking forward to test 1.6 when it hits stable
[Nexus 7 (2013) Original Android Development] nikr123:
I don't think you would have a problem upgrading to 1.6 even if it's beta. 1.6 works fully as it should. You can read the changelog and see what the difference is.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Why is there 1.6beta when 1.5official isn't out

Via my Iconia™ A200 tablet using tapatalk²
[Nexus 7 (2013) Original Android Development] Kebb42:
Been running 1.6 all weekend, no problems to report so far.
[Nexus 7 (2013) Original Android Development] nikr123:
Because they are mostly the same. Read the changelog.
[Nexus 7 (2013) Original Android Development] dud3me:
Flar himself recommended keeping it turned on, so you may understand the confusion. I checked with FKU as I had it installed and it also showed 1026 as min frequency.

Edit: that was on cleanrom with undervolting. On stock everything and PA min frequency is 384 as it should. But mpdecision is OFF as you said. Has Flar implemented an alternative? Weird that it's turned off on PA but ON on Cleanrom.
[Nexus 7 (2013) Original Android Development] tni.andro:
That's nonsense for ElementalX. You really want to leave mpdecision enabled.

mpdecision is responsible for powering up/down CPU cores. Without it, cores will remain powered up or down in whatever state they were when you disabled it. Franco and faux have alternate implementations for taking care of that.

ElementalX installs an init script (/system/etc/init.d/99elementalx) that sets the lowest clock frequency to 384Mhz. Unless some app/ROM is overwriting that, it works just fine.
[Nexus 7 (2013) Original Android Development] BigJPNut:
Dude you need to educate yourself before popping off at the mouth and spreading advice about something you think you know because you read it in Franco's thread lmao. Two totally different kernels bro....
[Nexus 7 (2013) Original Android Development] ckisgen:
+1

was just about to say this when I scrolled down and saw that you already said it.
[Nexus 7 (2013) Original Android Development] AL2000EX:
How does thermal throttling works? Does it affect battery or performance?
[Nexus 7 (2013) Original Android Development] xboxfanj:
Based on how hot the CPU and battery are, cores turn off, the frequency goes lower to try to make it cooler again. A CPU and battery running hot impact battery, so making them cooler should help. Performance could get worse, but shouldn't be dramatically affected.
[Nexus 7 (2013) Original Android Development] khaoskosmos:
Been running the 1.6 beta and I'm fairly impressed by the everyday performance. Combined with CarbonRom, I'm in heaven. Here are some benchmark scores for those that care about those things using my typical everyday settings.
[Nexus 7 (2013) Original Android Development] Spyr0s:
Hello and thank you for this great kernel, i have a problem which is not really a problem but more of a hassle. When i swype down Quick Settings most of the time the tablet locks due to sweep2sleep. Is there any fine tune setting, eg activate swype only on bottom of the screen? I have the same problem when i drag fb chat heads to delete them. Im on Elemental 1.6 beta and JSS15R.
[Nexus 7 (2013) Original Android Development] flar2:
RE: mpdecision

It should be on.

The mpdecision daemon is started from the ramdisk. When ElementalX is installed it uses the ramdisk from the existing kernel on your tablet. If the previous kernel for some reason had mpdecision disabled in the ramdisk, mpdecision will be off. I don't know if any of the kernels that come with ROMs do this or not. Just tossing out a possibility.

To check if mpdecision is running or not, open terminal or adb shell and type:

ps mpd

If /system/bin/mpdecsion is listed, then it is running.

RE: 1024 min freq

Don't worry about this, the actual min frequency is 384MHz. You can verify with CPUSpy.

I've been thinking about fine tuning s2w/dt2w, I will have some new options on the next release.
[Nexus 7 (2013) Original Android Development] cobyman7035:
Is it safe to do ota install update?

Via my Acer Iconia A200 on Xda premium app
[Nexus 7 (2013) Original Android Development] jetaw03:
Hi! I have a noob question. just got my FLO yesterday and i haven't actually tinkered with it. but i am not new with android custom roms and kernels because my previous phones are android. i just want to make sure that what i am doing is correct. ;) can i install this kernel in stock JSS15R Rom? this kernel is already rooted, right? thanks guys!
[Nexus 7 (2013) Original Android Development] flar2:
It's probably okay, but it might fail, and you'll probably have to reinstall the kernel after.

Yes, I'm using the stock ROM. Just install through recovery.
[Nexus 7 (2013) Original Android Development] jonhy25:
Who wants to share his kernel settings (gov, frec, io, etc)? Thx
[Nexus 7 (2013) Original Android Development] nklenchik:
Here ya go
[Nexus 7 (2013) Original Android Development] jetaw03:
thanks! i'll try this later..
[Nexus 7 (2013) Original Android Development] alawadhi3000:
[MENTION=4684315]flar2[/MENTION]

Is there any max charging current set in the kernel?? Even with a Samsung 2A charger the tablet won't charge faster than ~1.1A which may point to a 1.3A (1.1A after efficiency drop) limit set somewhere in the rom/kernel/controller ..etc.

For people like me who use the tablet in the car, charging speed is important as the tablet should still be able to charge even at full brightness.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
Forcing it to charge at a higher amperage than stock may damage the battery and will certainly shorten it's life.
[Nexus 7 (2013) Original Android Development] alawadhi3000:
I'm aware of that, and I honestly don't care about how long it'll last, I'll replace it if it dies, simple as that.

BTW a 3950mAh battery should have no problem being charged @ 2A, the Galaxy S4, Note II and Note III charge at 1.6A and the old Nexus7 had a 2A charger with it, I can't see a problem if we can raise the charging current a bit.
[Nexus 7 (2013) Original Android Development] tni.andro:
Power comes in via a smb345. It's configured for a 1200mA input current limit. Wireless/Qi is set up for up to 500mA input current.

It's hard-coded in the driver - to increase the limit, you have to modify the smb345 driver.
[Nexus 7 (2013) Original Android Development] alawadhi3000:
So I guess I have to go to /drivers/power/smb345-charger.c and look for the variable that defines the charging current and change it from 1200 to like 1500 and recompile the kernel??
[Nexus 7 (2013) Original Android Development] tni.andro:
It's not the charge current, it's the input current - everything is powered via this chip.

It's set in a few different places (for various charger state changes). Look for:

smb345_set_InputCurrentlimit(client, 1200);

It's entirely possible that it won't really make a difference. There is no datasheet for smb345, but the smb346 is limited to 1250mA charge current.

The charge current limit is configured to the maximum that's possible - whatever that may be.
[Nexus 7 (2013) Original Android Development] NoobieExtraordinare:
Work with Carbon?

I know Carbon is at least partially based on CM, but I believe I am running the Oct 3rd nightly with Elemental 1.4 without issues. So am I safe to flash 1.6? Any insight would be appreciated.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Carbon discarded cms caf commits a while ago. V1.6 should be good to flash.

Sent from my Nexus 7²
[Nexus 7 (2013) Original Android Development] akaempf:
I am using ElementalX 1.6 on latest daily and uses it with Oct 3 and on with no problems. Very stable...
[Nexus 7 (2013) Original Android Development] whoamanwtf:
Is there any difference between the new 1.6 postedand the beta that was up a few days ago that was also 1.6? Meaning should I reflash this if I was on the beta or just leave it?
[Nexus 7 (2013) Original Android Development] flar2:
It's the same. Whenever there's an actual change, I change the version number.

I just moved its status from beta to stable
[Nexus 7 (2013) Original Android Development] whoamanwtf:
Alright, thank you :) Been running it for a while then with no issues... I have it on two Tablets one running PA official and one running CleanRom 1.7 both functioning flawlessly.
[Nexus 7 (2013) Original Android Development] flar2:
I have some good improvements to s2w and other stuff coming
[Nexus 7 (2013) Original Android Development] timrock:
looking forward to it.
[Nexus 7 (2013) Original Android Development] Spyr0s:
Waiting patiently :good:
[Nexus 7 (2013) Original Android Development] kingston73:
I haven't been using this long enough to compare the battery life but I noticed an immediate difference in the responsiveness to double tap wake. Not sure if you did something different vs. other kernel devs but seems like your double tap works much better than other's I've tried. Thank you!:good:
[Nexus 7 (2013) Original Android Development] TheMrcool212:
Delete, wrong thread.
[Nexus 7 (2013) Original Android Development] Ivanbarker:
Kernel noob here, is this a CAF kernel?

Thanks.
[Nexus 7 (2013) Original Android Development] bokagavrilov:
No you have the answer in the op
[Nexus 7 (2013) Original Android Development] Ivanbarker:
Thanks!
[Nexus 7 (2013) Original Android Development] El Ha$on:
Just had a random reboot here's a last_kmsg

Doesn't usually happen but figured this would be helpful.

http://goo.gl/qN62AV
[Nexus 7 (2013) Original Android Development] jwong.hhf:
noob question: read ahead buffer size is much higher then original 256. why so high:confused:
[Nexus 7 (2013) Original Android Development] dirwdirw:
does s2w eat more battery significantly than stock？
[Nexus 7 (2013) Original Android Development] flar2:
Yes

I have a partial solution coming in the next update
[Nexus 7 (2013) Original Android Development] sevenslugs:
Thanks for everything Flar still running like a charm...is the volume able to be boosted at all with this kernal?

Sent from space. now Free
[Nexus 7 (2013) Original Android Development] OperVil:
Had the same issue, so I rolled back to stock.
[Nexus 7 (2013) Original Android Development] flar2:
What were you guys doing when it rebooted?

I haven't been able to look at the last_kmsg from El Ha$on yet (because I'm busy and google stuff is blocked on my work computer), but I'm thinking it's an isolated thing as there have been many thousands of downloads of this kernel and basically only these two reports of reboots (not counting the older reboot issues caused by Chrome browser).

I try not to add anything to the kernel that would cause instability and I leave things in beta for a long time before I deem them stable. I have never had a reboot even on test kernels.

Stability is the most important thing to me, so I take it very seriously when people post that they have had reboots. Make sure that you give me as much detail as possible.

Also make sure you're using a stable ROM and not overclocking and/or undervolting.
[Nexus 7 (2013) Original Android Development] flar2:
This is compatible with fauxsound, but I know that costs money.

I'll look into something free.
[Nexus 7 (2013) Original Android Development] El Ha$on:
I am over clocking. But like I said it doesn't happen often at all. That was like the first one in a while.

I no longer remember what I was doing but I am over clocked and undervolted which I'm sure was the reason I had my reboot.

Overall very stable for me and I'm extremely happy with kernel. Just wanted to share. I'm on CleanROM 1.7 BTW

Sent from my Droid DNA on 4.3!!!
[Nexus 7 (2013) Original Android Development] tni.andro:
Should I add another one? I've had a few crashes when turning on Wifi (I frequently turn it on and off), but that's entirely due to the stock Wifi driver (buggy regulatory domain handling).

[ 388.353607] CPU: 0 Tainted: G W (3.4.0tni-float-vlt-uV-ElementalX-1.4+ #25)

[ 388.353729] PC is at wlan_hdd_crda_reg_notifier+0xff4/0x1c24

[ 388.353790] LR is at vos_lock_release+0x11c/0x144

[...]

[ 388.392822] [<c090fd48>] (wlan_hdd_crda_reg_notifier+0xff4/0x1c24) from [<c0bd2c38>] (wiphy_update_regulatory.part.7+0x524/0x64c)

[ 388.392913] [<c0bd2c38>] (wiphy_update_regulatory.part.7+0x524/0x64c) from [<c0bd3918>] (reg_todo+0x5fc/0x7c0)

[ 388.393035] [<c0bd3918>] (reg_todo+0x5fc/0x7c0) from [<c00bdb40>] (process_one_work+0x128/0x588)

[ 388.393127] [<c00bdb40>] (process_one_work+0x128/0x588) from [<c00be4f8>] (worker_thread+0x1cc/0x484)

[ 388.393218] [<c00be4f8>] (worker_thread+0x1cc/0x484) from [<c00c3444>] (kthread+0x90/0x94)

[ 388.393310] [<c00c3444>] (kthread+0x90/0x94) from [<c0016418>] (kernel_thread_exit+0x0/0x8)

addr2line gives: drivers/staging/prima/CORE/VOSS/src/vos_nvitem.c:2363

I've switched to the latest CAF driver and that's been stable:

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

That regulatory domain stuff has been completely rewritten in the new Prima 3.2.3.x driver branch. (I'm not suggesting you should switch out the Wifi driver - there is a massive amount of changes and the new driver is not compatible with the stock firmware.)

(Google has an open bug for broken regulatory domain stuff.)

---------- Post added at 10:09 PM ---------- Previous post was at 09:26 PM ----------

ElementalX uses the default of 128kb.

find /sys -name read_ahead_kb -print0 | xargs -0 cat

results in:

128

...

128
[Nexus 7 (2013) Original Android Development] flar2:
Your reboot may very well be from overclocking/undervolting, since the error was reading memory. Possibly corrupted memory due to overclocking or undervolting.
[Nexus 7 (2013) Original Android Development] flar2:
For testing

Download:

ElementalX-N7-1.7 *BETA*

Changes

-update installer

-update config files

-add S2W power key suspend toggle

-add options to disable sweep2sleep in portrait or landscape mode

-show pvs number in sysfs

-add DVB support (requires modules add-on, coming soon)

-remove 128MHz GPU step and idle at 200MHz step

-add battery life extender (thanks tni_andro)

-boost CPU frequency only for touch input

-adjust bus bandwidth
[Nexus 7 (2013) Original Android Development] teh roxxorz:
For the testing!
[Nexus 7 (2013) Original Android Development] bsw11:
Please consider having 2 versions for the cm roms. Please.
[Nexus 7 (2013) Original Android Development] nikr123:
He has already said he stays with 1 aosp version. Look around in the thread. Anyway more and more ROMs are being changed from caf to aosp.

---------- Post added at 01:38 AM ---------- Previous post was at 12:58 AM ----------

Does the DVB support mean that we can buy a USB DVB receiver and plug it in through OTG to watch tv through programs like xbmc or is it something totally different?
[Nexus 7 (2013) Original Android Development] flar2:
Yes, it's for usb tv tuners, but before you buy wait for some people to test it. And it will only work with ones that are supported by linux.

I still have to upload a modules zip, there are a bunch.
[Nexus 7 (2013) Original Android Development] nikr123:
Should it support most TV tuners? Or is a special one?
[Nexus 7 (2013) Original Android Development] jlevy73:
I like the new functions of being able to temporarily disable S2W by using the power button, great idea. Just flashed so will continue testing and report back later.