yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] DroidIt!:
Have you tried with different rom's or different versions of the kernel. I've only used ultra but across different rom's. It used to not happen to me very frequently but seems like it has gotten worse. I've tried it on most recently Vanir, CM Kanged, and SlimBean, just going off the top of my head. But I've always used ultra. I like my max at 1.72 and did have my min set at 162. I know faux says that's low, but I never had any problems with it, my tablet handled it just fine. I recently started getting the SOD's so I upped it a little bit into the 300's, but keep getting them and like I said I noticed this last time that my max setting had dropped to match my min value on it's own :confused:
[Nexus 7 (2013) Original Android Development] Jake-CT:
I am suspicious of chrome beta too. I wonder if also cause of some green screen on nexus 4 with faux. Guess next step is to change out to stable on both devices and try it.

My sod have always come after some chrome use and a little while after putting the device down.

---------- Post added at 09:02 PM ---------- Previous post was at 09:00 PM ----------

Oh and tried 484 minimum but didn't work.
[Nexus 7 (2013) Original Android Development] DroidIt!:
Hmmm, that is strange. Had chrome beta the whole time. Maybe I try swapping out just for the sake of trying to swap. I just notice that sometimes after picking up my tab, sometimes I hold down the power button for 10 to 15 sec, sometimes it boots right up. Other times it does a full reboot after holding the power 3 or 4 times. :confused:

sent with both my braincells
[Nexus 7 (2013) Original Android Development] Crwolv:
Tactile feedback duh, not only does it not vibrate the letters don't even show me what im typing and there's no settings at least some ROMs have it.

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

Used supposed best kerne

And no screen control?which kernel has it.used faux and trickster apk,s
[Nexus 7 (2013) Original Android Development] Crwolv:
Very limited screen control popped up after restart . rgb only up to 255 .will anyone get up to 400 rgb for lcd screens. U can for oled which actually makes oled very superior. Next n7 should have one
[Nexus 7 (2013) Original Android Development] ÜBER™:
Um are you trolling?

"Very limited"

Its very new, the last N7 never received color control... Be happy with what you have.

"RGB only at 255, will it ever be 400?"

No.

"OLED is superior, the next nexus should have it"

No, its not. Its drastically incorrect in color reproduction. Terribly hard to see in sunlight and sucks for battery on anything other than black. While contrast and black reproduction is the only thing it has going for it.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 7 (2013) Original Android Development] Crwolv:
Am i trolling? Are u kidding me? An opinion and a comment! And no oled isnt incorrect if the settings are right and when the color miltipliers and bumped up to 320 320 and 400 screen is brighter(my nexus vs my lgog)white is perfect and cuz pixel is off black is perfect .im very happy i was just challenging faux cuz his kernels are awesome. What the heck uber? I dont troll , jeez man. Wow cant believe u would say that, chalange my opinion and sorry if it sounded off or something but trolling. I have the new n7 and was just spouting an opinion. Im a good person and that accusation wasnt cool. Sorry if my statement was taken wrong but trolling.....jeez dude:(
[Nexus 7 (2013) Original Android Development] habylab:
Back on topic please?
[Nexus 7 (2013) Original Android Development] Windsor1959:
I have just flashed the mainline kernel and installed faux clock. I have been trying to apply the recommended settings for battery from faux's second post. I can't find snake charmer anywhere! It could be right in front on me, I suppose. Where is that snake charmer, anyway? Thanks.
[Nexus 7 (2013) Original Android Development] DroidIt!:
You need the faux clock app for that, you won't see it anywhere else. If you do have the faux clock app it should be right on the first screen that pops up, the cpu tab. Should be a toggle right at the bottom that says snake charmer ;)
[Nexus 7 (2013) Original Android Development] Windsor1959:
Thanks for your reply. But this is strange. I have the faux clock app. I've installed his mainline kernel. I go to the app, and I'm on the CPU tab. The lowest toggle I see is eco mode. Weird. I tried rebooting. Still the same. I'll look again later.
[Nexus 7 (2013) Original Android Development] DroidIt!:
What Rom are you on? I would try redownloading the kernel just to be sure you got a good download and go back to recovery and flash and wipe dalvic/cache and reboot. Never not had it work for me, so out of ideas if that doesn't work.....:rolleyes:
[Nexus 7 (2013) Original Android Development] natezire71:
What does "Snake Charmer" even do? :p
[Nexus 7 (2013) Original Android Development] Windsor1959:
I'm on CleanROM. I tried your suggestion. Still no snake charmer. No big deal, but it's odd. Maybe this isn't a feature of mainline? Or maybe I have a weird device
[Nexus 7 (2013) Original Android Development] PiggySmalls:
Try force stopping faux clock, then clear data and cache in the app manager, then restart your tablet. You'll have to redo all the settings, but it may make snake charmer show up.

Sent from my SPH-L720 using Xparent Skyblue Tapatalk 2
[Nexus 7 (2013) Original Android Development] malukiz:
Hi,

Just a feedback to say that mainline is more smooth with games (minion rush) that ultra combo which is laggy on my N7.2
[Nexus 7 (2013) Original Android Development] faux123:
Maybe ultra combo is throttling too much
[Nexus 7 (2013) Original Android Development] Windsor1959:
That didn't smoke out the snake charmers, either. And my friends think that I live a charmed life...
[Nexus 7 (2013) Original Android Development] faux123:
Lolz.. Make sure busybox is installed and working... The charmer will come out.
[Nexus 7 (2013) Original Android Development] ÜBER™:
Speaking of snake charmer. It seems with on demand snake charmer doesn't work properly. All other cores still go to 1.9 while core0 is actually locked at my max of 1.7.
[Nexus 7 (2013) Original Android Development] habylab:
I had this top, since flashing too another kernel and then flashing back.
[Nexus 7 (2013) Original Android Development] Windsor1959:
Thanks. I have busybox, 1.20.2. It seems to be working. Still no charms!

BTW, based on first impressions, battery life is pretty impressive.
[Nexus 7 (2013) Original Android Development] PainfulLover:
Weird, I'm on clean ROM and mainline, no issues.

By the way, just noticed there is a newer version of busybox out, v1.21 something. Give it a try?!
[Nexus 7 (2013) Original Android Development] Windsor1959:
I've upgraded busybox successfully. The snake charmer toggle is still nowhere to be found. As everything seems to be working fine otherwise, I'll end the hunt, unless there's a significant benefit to using snake charmer. Thanks again.
[Nexus 7 (2013) Original Android Development] MasterJam882:
Dunno if this has been asked (I assume yes):

Will there be a kernel Version for DEB (LTE Version)?

Thanks

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 (2013) Original Android Development] joeyddr:
just got a sod after being ok for a day or 2.... using mainline https://www.dropbox.com/s/t7k1skf8imzgm0m/last_kmsg
[Nexus 7 (2013) Original Android Development] airmaxx23:
I have busybox installed but no matter what I do I get "busybox was not found or functional" when I open FauxClock. Other apps see it as installed and working fine.
[Nexus 7 (2013) Original Android Development] shreddintyres:
Did you try clearing cache after installing? Also which super user app are you using (supersu or koush) i've gotten this issue before or atleast similar on my gnex, depending on the app you used to install busybox your super user binaries may need to be updated sometimes busy box doesn't play nice with koush su, if you are using supersu go and update su from within the app, reboot to recovery wipe cache and dalvik (not sure if necessary but i always do it for good measure) and reboot hopefully this will remedy your problems

- Cheers

Ps for those who are still experiencing sods since i Uninstalled chrome beta (has been more than 48 hours since I Uninstalled) I have yet to experience any new sods. Almost all of my settings mimic those of faux's second post with some slight modifications (read ahead buffer set to 512 and min freq set to 810MHz since i feel that the benefit of having tasks finish quicker out weighs the minor increase in power consumption this is pre uv)
[Nexus 7 (2013) Original Android Development] DroidIt!:
I've always gone to this source to get the most up to date supersu in place while I'm flashing the rom http://download.chainfire.eu/351/SuperSU/UPDATE-SuperSU-v1.65.zip As I said, I just always flash the rom, gapps, supersu zip from the link, and kernel all together in that order. Then wipe cache/dalvic afterwards then reboot. Never had a single problem with supersu or busybox then :good:

Edit: oh and that same link always has the latest update posted on it :)
[Nexus 7 (2013) Original Android Development] faux123:
there are no difference between WiFi and LTE for kernel.
[Nexus 7 (2013) Original Android Development] xfrancis14:
Any chance that the voodoo display app will ever work with this kernel? It says it's not compatible with this kernel when you open up the app
[Nexus 7 (2013) Original Android Development] ÜBER™:
This kernel already has color control. Voodoo is for Samsungs anyways.

Sent from my Nexus 7 Flo with Tapatalk 4
[Nexus 7 (2013) Original Android Development] mystifiyer:
Will highly advise u to read up on it first before commenting.

Shooting off your mouth without knowing what's it for is plain wrong and silly.
[Nexus 7 (2013) Original Android Development] shreddintyres:
I would think its possible but potentially unlikely as Supercurio's calibration app depends on certain portions of the stock kernel. His implementation is targeted at working on any device n the easiest way for him to maintain the module is to base it off of the AOSP kernel drivers.

Given that the implementation is still in its infancy (supercurio's) i doubt that Faux would be willing to scrap his work on the display drivers for something as of yet unproven.

Here is Supercurio's comment regarding the issue:

[MENTION=3332811]faux123[/MENTION] if you are interested here is a link to the G+ community https://plus.google.com/communities/103123288128442067861

- Cheers
[Nexus 7 (2013) Original Android Development] ÜBER™:
Theres no need for all that.. A simple actually... then explanation would have been sufficient. As far as i can remember Voodo anything has only been on Samsung devices. Excuse me... :rolleyes:
[Nexus 7 (2013) Original Android Development] 0.0:
I have gotten screen of death multiple times. I finally decided to turn off UV earlier today. That didn't work. I left only c0 & c1 on, and it still happened. I made GPU to be ondemand. I turned off file dynamic syncing. Idk what else to do. Sorry I have no logs, as I couldn't get them :(

It could be the ROM, but I'm not too sure

sent from my Nexus 7
[Nexus 7 (2013) Original Android Development] habylab:
The exact same here. Now on Dan kernel or whatever it is.

Sent from my maybe one day to be CM i9300. That day won't come unless the camera improves!
[Nexus 7 (2013) Original Android Development] drms12:
Intelli Thermal doesn't working at all , on both es and m versions of v5.

I know how to use it and how to check it. On N4 it's working great. In fact, when using intelli thermal there isn't any protection.

All cores stay on and full speed even I've set it to disable all cores (1,2,3) at 50c, same for frequency. Even at 80c no throttle.

Governor used was intelli demand on both nexus 4 and 7.
[Nexus 7 (2013) Original Android Development] airmaxx23:
I got the busybox issue figured out. I used it for a few minutes this morning then went to use it again and had a sod on the mainline kernel.

Last_kmsg: https://app.box.com/s/20g9afml6f1cye5nv2ho
[Nexus 7 (2013) Original Android Development] asaqwert:
Sorry for the stupid question but can I use this with cm10.2 or is it for stock based roms only? Related to that....but how can I know if a given kernel can be used with a cm based Rom? Or can most kernels be used with most roms? Sorry for the newbie question and thanks for any help you guys can offer
[Nexus 7 (2013) Original Android Development] faux123:
All Nexus kernels, if built from AOSP source, will be compatible with all AOSP ROMs, however, CM has decided NOT to be an AOSP clone but a CAF (Qualcomm's version of AOSP) clone. This introduced compatibility issues for those kernels build from AOSP source like mine.

Yes, CAF versions have quite a bit of bells and whistles and supposedly more "optimized" than stock AOSP... but I personally do NOT agree with the decision to break away from AOSP on a Nexus device (for those ALL other NON-NEXUS devices, CAF AOSP is the only alternative like Galaxy S2/3/4, HTC One etc etc). Nexus devices should ALWAYS run AOSP clones... :(
[Nexus 7 (2013) Original Android Development] faux123:
There's nothing I can do if Supercurio only target stock or near stock kernels. My kernels are hybrids and will always be hybrids (because I like my Linux 3.8/9/10/11 backports). This will prevent his modules from loading on my kernel.
[Nexus 7 (2013) Original Android Development] asaqwert:
So the gist of this is....on my nexus 7, I cannot use your kernel, or any other kernel, unless it is specifically made for cm?

Similar to the way on my s3 I have to use tw kernels with tw roms and aosp kernels with those roms....is that a valid analogy?
[Nexus 7 (2013) Original Android Development] faux123:
this is a serious bug. The question is why isn't it working... Mako and Flo share the EXACT identical code for thermal driver and management... something weird is going on here...
[Nexus 7 (2013) Original Android Development] faux123:
yes.. similar... (AOSP and CAF differences aren't as great as TW vs CAF). My kernel will boot on CM and will work 90% with maybe 10% of small bugs and funny issues.
[Nexus 7 (2013) Original Android Development] natezire71:
[MENTION=3332811]faux123[/MENTION] Any plans to make your screen tuning modules a little more open so myself and others could use TricksterMod?
[Nexus 7 (2013) Original Android Development] drms12:
Hope you could fix it.

The tablet gets really hot when playing games. Especially Riptide GP 2.

After few races it reads 86c.

I wanted to ask you if qualcomm made it fine with these 80-90 temps, Because even at these temps the c1,c2 and c3 work most of the time, also at high clock speed. I tried to open the thermald.conf which have the throttle information but couldn't understand nothing with all of that sensors. It wasn't like that on older devices.

Another problem with your kernel, Slimport HDMI display isn't working at all with your kernel, not with aosp and not with CM10.2.

It working with the other kernels...

Hope you could fix it. I bought all of your apps and use all of the features you made available. Don't want to loose them all.
[Nexus 7 (2013) Original Android Development] faux123:
this is first time I heard about Slimport broken... Let me check it tonight.. (Thank goodness I bought the slimport adapter a while back to fix Mako issues :p )
[Nexus 7 (2013) Original Android Development] drms12:
Great :)

By the way Slimport work fine with N4 and 25m kernel.
[Nexus 7 (2013) Original Android Development] faux123:
I know.. just reviewed own code... there were NO changes in the video FB or HDMI or USB code for FLO :(

WTF... many things not quite working even though code is identical...

Can you check if HDMI is working with STOCK kernel...

also get me some logs... (I am at work.. so not much I can do except doing some code reviews)

do this if you have a chance.

with stock, using adb or terminal

su

dmesg > /sdcard/dmesg_stock_hdmi_before.txt

plug in HDMI

then do:

dmesg > /sdcard/dmesg_stock_hdmi_after.txt

with my kernel also do:

su

dmesg > /sdcard/dmesg_faux_hdmi_before.txt

plug in HDMI

then do

dmesg > /sdcard/dmesg_faux_hdmi_after.txt

I will do the same thing as above when I am debugging this issue, so if some1 can do this for me before hand, it would save me time...
[Nexus 7 (2013) Original Android Development] drms12:
It is have to be stock kernel or a kernel that have working Slimport logcat will do the job?
[Nexus 7 (2013) Original Android Development] faux123:
logcat is useless

it has to be stock since as I mentioned before, my code for slimport IS STOCK.. I am suspecting that stock DOES NOT work as well.
[Nexus 7 (2013) Original Android Development] drms12:
Writing mistake.

I have the dmesg from your kernel.

BTW right after plugging the slimport adapter system performance went down, like you made it max 162mhz.

FPS on the system is like 5 fps.

Unplugging the slimport fixed the issue right away.
[Nexus 7 (2013) Original Android Development] faux123:
I believe stock kernel is derped as well...
[Nexus 7 (2013) Original Android Development] drms12:
I have the stock dmesg.

As I said stock boot.img didn't work with my rom, After boot I couldn't even get past the lockscreen, all system services FC one by one.

I have one from the stock kernel of the rom, which is slightly modded with few features like Intelli Demand Gov, Faux Sound, etc.

Hope it would help you figure it out.
[Nexus 7 (2013) Original Android Development] faux123:
anything not stock is not stock no matter "how close it maybe"

anyways, which kernel did you use?
[Nexus 7 (2013) Original Android Development] Jake-CT:
Slimport is fine for me on 25U with PA 3.99.
[Nexus 7 (2013) Original Android Development] drms12:
Stock or not, It is working with that kernel

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

About PA I don't know.

But other CM/AOSP roms I've tried I couldn't get it to work with faux latest.
[Nexus 7 (2013) Original Android Development] faux123:
that's a CM kernel... it's NOT AOSP :( read my discussion above (CM is NO LONGER an AOSP clone but a CAF CLONE, this breaks many things... I bet HDMI is working on pure AOSP ROMs but on CM it maybe broken due to mentioned)
[Nexus 7 (2013) Original Android Development] drms12:
Like I said, I tried it also on AOSP rom.

For example, Yesterday I factory reset and Installed Carbon ROM which is AOSP.

I didn't install any apps, Tried Slimport with your kernel with no luck.

CM or not, hope you could give a solution for such needed feature.
[Nexus 7 (2013) Original Android Development] faux123:
there are multiple derps on the log.. try this

http://faux.androidro.ms/irc/beta/flo-jb-kernel-006b01.zip
[Nexus 7 (2013) Original Android Development] drms12:
ok

Will report back soon

Edit:

Just the same behavior, Same slow system,

dmesg attached
[Nexus 7 (2013) Original Android Development] faux123:
it fixed 1 derp :p there are many derps...
[Nexus 7 (2013) Original Android Development] drms12:
:eek:

Take your time :)
[Nexus 7 (2013) Original Android Development] Cuzz1369:
Carbon is technically aosp but they use A LOT from cm.

[MENTION=3332811]faux123[/MENTION] I know the deadlocks are ROM related but did you do anything to help them. In the carbon thread a lot of different users and myself feel it a lot less (even feels like they disappeared for the most part) using your kernel. Others on Franco(n4) and semaphore(n4) report them being frequent still.
[Nexus 7 (2013) Original Android Development] MrPhilo:
Any chance of making the screen control permanently stick (when I turn off my screen and back it goes back to default) like the Nexus 4? I don't mind re-applying but sometime it freezes after a multiply of time applying the screen thus having to hard reboot and sometime I lose data.
[Nexus 7 (2013) Original Android Development] Crwolv:
Thank so much for your hard work(and the privet message) your a great dev and a stand up person. Keep it up cuz you are highly appreciated.

---------- Post added at 06:43 PM ---------- Previous post was at 06:33 PM ----------

Wow I agree there is no need but maybe it was done cuz he is right and the same would have gone for how you treated me just cuz I asked a question. Sux doesn't it, how about everyone just concentrate on being nice to each other. We are all here to help each other and faux (who took no offense to my simple question b4 u went all ruse and asked if I was trolling) does not need the stress being as busy as he is doing the awesome work he does. Treat others the way you want to be treated.
[Nexus 7 (2013) Original Android Development] borxnx:
I have no problem running this kernel on the latest PAC Man nightly. Everything runs smoothly and battery is great. I haven't tried on other CM based ROMs, but everything's gravy here.
[Nexus 7 (2013) Original Android Development] Krowbarr:
+1

Owner/Operator Nexus 7

We were born in a time where if something was broken we would fix it and not just throw it away
[Nexus 7 (2013) Original Android Development] vagelis:
By the way, slimport works fine with your kernel and SlimBean b5.
[Nexus 7 (2013) Original Android Development] TheDoolster:
I haven't been able to get color tuning working on this kernel. Neither trickster mod nor fauxclock have any option for color tuning. :(
[Nexus 7 (2013) Original Android Development] natezire71:
Trickster won't because [MENTION=3332811]faux123[/MENTION] doesn't make it easy for Trickster's team to support it.
[Nexus 7 (2013) Original Android Development] TunedFish:
I've paid or donated to franco, eze, faux, koush, etc because they do it faster and more efficiently than I do. No pressure. But no disrespect, either.
[Nexus 7 (2013) Original Android Development] :
Ive been out of this loop with this kernel for a while, but can someone please answer if the kernel has s2wake or doubletap2wake yet?

I've been on Elemental for these reasons alone.
[Nexus 7 (2013) Original Android Development] TunedFish:
Long story short, color control works.

The colors on this Asus tablet aren't as good as the Samsung gnex, so if you want to fix it with the faux app, save your money, don't expect miracles, but color color control works and it's better than stock.
[Nexus 7 (2013) Original Android Development] Cuzz1369:
S2W works

Edit: Nope
[Nexus 7 (2013) Original Android Development] mystifiyer:
I try swiping around and couldn't get it to work.

Are you sure about this?
[Nexus 7 (2013) Original Android Development] Cuzz1369:
I am totally wrong. Apologies. The n4 has it but not n7. Sorry.
[Nexus 7 (2013) Original Android Development] mystifiyer:
No problem bro. Thanks for verification
[Nexus 7 (2013) Original Android Development] DroidIt!:
+ 2 :) No problems here either. Think I've tried just about every release of Ultra on most CM roms :thumbup:

sent with both my braincells
[Nexus 7 (2013) Original Android Development] AlderCass:
I flashed this kernel on PA 3.99 and applied the recommended settings in FauxClock and then later on I unplugged my N7 from its charger and did some web browsing while playing music, about 20 minutes later I checked the battery and it was still at 100%! :eek: So yeah best kernel I've come across hands down, I've been using it on my N4 for several weeks as well :good:
[Nexus 7 (2013) Original Android Development] crypticc:
Hi faux. This kernel spent work with Francois latest voodoo display project for this device. It reports kernel_debug & kallsyms_all disabled. Is that correct?

(EDIT seen you are working with François to get this nailed, thank you !)

Cheers

Chris
[Nexus 7 (2013) Original Android Development] catlog:
How is gamma control going along? Haven't seen any updates on it so I thought I'd ask.
[Nexus 7 (2013) Original Android Development] mystifiyer:
Curious where you seen this. Last I saw, he don't agree (a few posts away)
[Nexus 7 (2013) Original Android Development] stfudude:
He literally mistook faux's archenemy as faux himself.

BTW, as a follow up to my little experiment a few days ago (486 mhz as min clock, and C2 off), SOD doesn't occur anymore.
[Nexus 7 (2013) Original Android Development] crypticc:
Didn't see that. Was only out four one day, sorry