yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] zaclimon:
I thought that at first too but I saw that trickster can modify the values as well. I hope it will be added to fk.u sometime soon. :)
[Nexus 7 (2013) Original Android Development] osm0sis:
Yeah they likely added it when faux did it originally on his kernel.

Found the sysfs directory for the new color control: /sys/devices/platform/DIAG0.0/

Not 100% sure how to use them though. The RGB one didn't update immediately like I expected it to when I edited it.
[Nexus 7 (2013) Original Android Development] hardwareadictos:
Calm down, i was reporting a bug

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] xfrancis14:
Anyone know when gamma control will be available? It's the only thing keeping me to faux
[Nexus 7 (2013) Original Android Development] zaclimon:
It is already available though franco haven't updated his stuff yet to modify the values. That said, I think you can use either faux app or trickster atm to modify the colors of your screen.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] xfrancis14:
Okay thank you, I'll just wait till francos app supports it
[Nexus 7 (2013) Original Android Development] Mahennemaha:
Ups, wrong thread…
[Nexus 7 (2013) Original Android Development] dud3me:
Can you explain more as do why this boosts performance? I'm trying it out but it'd be nice to know more about what I'm actual changing :D
[Nexus 7 (2013) Original Android Development] osm0sis:
They make the GPU ramp a lot more aggressively.
[Nexus 7 (2013) Original Android Development] gknnn':
[MENTION=2918197]The Gingerbread Man[/MENTION] do you have your old settings (from last weekend - before r13 release) somewhere saved? These settings been perfect balanced between battery saving and power for me.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Nope sorry I only keep my current settings saved in my post in my sig.
[Nexus 7 (2013) Original Android Development] sd_matto:
Any chance that this "fixed" version works with N7 LTE (deb)? Would prefer to know before I flashed. :)

Thanks to you (and Franco) for your good work.
[Nexus 7 (2013) Original Android Development] osm0sis:
Reread what you quoted there. ;)
[Nexus 7 (2013) Original Android Development] sd_matto:
Problem is that I don't fully understand what I quoted. Specifically, does your fix of "Added . . . telephony-msim.jar" (which suggests an LTE device issue fix) resolve the non-booting Franco kernel from prior versions?

I guess that I should have better identified what my misunderstanding was. :)
[Nexus 7 (2013) Original Android Development] psyren:
Flashed r13 fixed on Carbon ROM, still having issues with smart cover not working properly.
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Similar setup. All good here.
[Nexus 7 (2013) Original Android Development] psyren:
This was my install process:

Clean wipe (/system and /data) > Carbon (latest nightly) > GApps (Banks' package) and Calendar sync package > SuperSU > boot once > flash fixed r13.

My device seems to have issues with deep sleep - it won't come out of it unless I use the power button, and it kills my open apps (Aldiko reader), even though I hardly use anything that requires a lot of memory (literally, just the reader app).
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
I wiped everything except internal storage, when I flashed carbon for the first time, followed by gapps,fk and supersu. I don't think this is related to the cover.

You might want to try a different rom kernel combo or just stock for a while if you really think the issue is with your device.
[Nexus 7 (2013) Original Android Development] psyren:
I reflashed the original Carbon kernel to test. I seem to be having the same issues. Weirder still is that the screen does come on when I open the cover... about 10 seconds after I do so. What the hell is going on?
[Nexus 7 (2013) Original Android Development] osm0sis:
Ah.. Well notice I said "even though this device is Wi-Fi only" in that sentence and then later on "made it check to make sure the device is a flo before flashing."

So flo only and it won't even let you install it on a deb. ;)

I'll take a look later this week to see if I can figure out what we'd need to make deb compatible.
[Nexus 7 (2013) Original Android Development] poondog:
btw ak managed to fix it in ramdisk
[Nexus 7 (2013) Original Android Development] habylab:
This kernel could realllllly do with FauxSound I feel

Sent from my Omni 4.4 Galaxy S3. Proud Googy Beta tester.
[Nexus 7 (2013) Original Android Development] sizzlers:
Is there thermal control cause while gaming it's getting unbelievably hot.
[Nexus 7 (2013) Original Android Development] silvan g:
Yes, you can manage thermal control in the Franco kernel app
[Nexus 7 (2013) Original Android Development] shreddintyres:
Faux sound is something from faux's kernel as is you can boost sound values through fku failing that you can just install v4a and let that boost and handle your audio.
[Nexus 7 (2013) Original Android Development] EvanA:
R13 breaks open source superuser. I suspect the ramdisk is missing the su daemon start.
[Nexus 7 (2013) Original Android Development] osm0sis:
Correct. That's actually r1 through r13 though; use my fixed version. ;)

http://v.ht/osmod

Go back a few pages for the details. :good:
[Nexus 7 (2013) Original Android Development] habylab:
Just realized the Taken reference in the op. Doh!
[Nexus 7 (2013) Original Android Development] psyren:
Got a soft reboot when closing/opening my cover while plugged in last night. I think the case hates me. I tested it with a friend's tablet running stock everything, and the same thing happened where the tablet wouldn't take up when the cover was opened.
[Nexus 7 (2013) Original Android Development] pan.droid:
Phucks the MD5?
[Nexus 7 (2013) Original Android Development] mdamaged:
Phucks the world!
[Nexus 7 (2013) Original Android Development] xfrancis14:
Anyone have any suggested color settings?
[Nexus 7 (2013) Original Android Development] morbidj:
This kernel does not have screen color profiles AFAIK? At least not in FKU beta..
[Nexus 7 (2013) Original Android Development] xfrancis14:
You can use fauxclock or do it manually. Color profiling was supposed in the last kernel update just not in the app yet
[Nexus 7 (2013) Original Android Development] morbidj:
Oh... Nice! Thanks for the info [MENTION=4831807]xfrancis14[/MENTION] On my N5 I use either "perfect 2.2 or volmerbalanced".. I'm going to have to mess around tonight.
[Nexus 7 (2013) Original Android Development] tetakpatak:
LOL :D this is the funniest OP I've read so far on the forum! I think I'm gonna buy N7 flo next week just for this, FF ! (I'm serious)

tetakpatalked from my P5110
[Nexus 7 (2013) Original Android Development] habylab:
Colour support is coming soon to the app!!
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
[MENTION=4544860]osm0sis[/MENTION] when flashing you fixed kernel the device goes into a bootloop, searched around a guy had the same problem.Flashing stock boot.img fixes this? Kinda lost on what exactly to do since searching for nexus 7 2013 stock boot.img lead me to googles website, so is the stock boot.img like the kernel or returning back to stock? Btw can the .img be flashed using flashify?
[Nexus 7 (2013) Original Android Development] mdamaged:
Assuming there isn't another reason for the bootloop, yes, and yes. It's a ramdisk thing.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
So I would flash using flashify a file from here ? Or just use the nexus root tool in the dev thread..
[Nexus 7 (2013) Original Android Development] mdamaged:
No need for NRT, the boot.img from the factory image is perfect. Obviously, make sure you grab the right one. You want razor for Nexus 7 2013 wifi, not nakasi, nakasi is for the old Nexus 7.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
Just flashed the boot.img, still get a bootloop. This only happens with this kernel. Don't know what could it be.
[Nexus 7 (2013) Original Android Development] mdamaged:
If you flashed the correct boot.img (the razor is the one you want for nexus 7 2013 wifi), and it is still bootlooping with the stock kernel, there is something else wrong. My guess is you will need to flash system.img too, francos kernel also messes with system. Really, before doing any kernel flashing you should always nandroid at least your present and working system and boot partitions before doing any flashing, that way you could simply revert. If you do not have nandroid versions of your system, you will have to use your ROMs stock one.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
I flashed the stock kernel just fine it booted up. I only get the bootloop with the franco fixed one.
[Nexus 7 (2013) Original Android Development] mdamaged:
Oh, I misunderstood. But the stock system may also need to be flashed, I would nandroid the system you have right now, then flash the stock system then flash the stock boot.img again, allow it to boot fully to verify it's all good, then flash the fixed franco.
[Nexus 7 (2013) Original Android Development] morbidj:
[MENTION=2918197]The Gingerbread Man[/MENTION] just curious I am using your settings for the flo from your Sig.. It seems when ever I set hot plugging load threshold to 0 I get scrolling lag I soon as I set it to 60 it's smooth again. Is there another setting I can adjust to smooth out the scrolling using 0?
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
So I managed to flash the system like you said, I tried starting from scratch using NRT but I just couldn't get it to recognize my device even though it's what i was using to flash the files in the first place. Since I flashed the system some apps are crashing and the home button doesn't work. I'll try flashing the custom rom I was using(PA) and then francos.
[Nexus 7 (2013) Original Android Development] mdamaged:
PA? is that CAF? I think it is based on CM directly, so that is why it won't work.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
Wait what? I have PA on nexus 5 with franco.
[Nexus 7 (2013) Original Android Development] mdamaged:
franco is not a CAF kernel, I think there was a franco that did work on CAF...this one doesn't.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
I'm at a lost here, to my understanding paranoid android isn't based on caf. Like I said, I have pa for the nexus 5 with francos kernel and had no issues.
[Nexus 7 (2013) Original Android Development] mdamaged:
I found some posts in that thread that seem to indicate that PA for N7 2013 is directly sourced from CM, which makes it CAF.

Source: http://xdaforums.com/showthread.php?p=46268376&highlight=caf#post46268376
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
That explains it. I thought all PA were the same in the sense of not being based on caf. Sorry for the troubles. Care to recommend a good rom ?
[Nexus 7 (2013) Original Android Development] mdamaged:
That question is rather taboo on XDA, but if I had to answer, I'd say that I tried a lot of ROMs using MultiROM, and disliked them all, the best for me is stock ROM with xposed and gravitybox, it beats them all, hands down.
[Nexus 7 (2013) Original Android Development] DudeWatsThat:
Cool,thanks. Haven't given that combo a try. As long as it works with franco I'm good.
[Nexus 7 (2013) Original Android Development] Moudii:
Thats the combo I am trying out atm too. So far so good!
[Nexus 7 (2013) Original Android Development] TheMrcool212:
To clarify everything, PA uses AOSP.

That post was old, before the release of KitKat.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Curious, seems fine to me but you could try increasing input boost freq. With hot plug set to 0 that turns on all 4 cores on so I'm surprised to hear your performance is decreased
[Nexus 7 (2013) Original Android Development] osm0sis:
Instead of 0, try it at 1. Could behave better with a non-zero value.
[Nexus 7 (2013) Original Android Development] osm0sis:
Just discovered that somehow, with the really minor changes I made, that dalvik-cache rebuilding is broken. Looking into what specifically is causing it but either revert to "original recipe" r13 or don't wipe dalvik-cache for now or you'll get stuck at the bootanimation.

---------- Post added at 08:38 PM ---------- Previous post was at 08:13 PM ----------

Huh, so somehow adding "import /init.superuser.rc" after on post-fs-data in init.rc broke it. No reason that should happen (and it doesn't on other devices, like grouper or tuna)...

Working around it now, then I'll look into the deb support AK added. :good:

Edit: AK is just AnyKernel - that means ramdisk should have fixed it for us when Franco added it. :confused:
[Nexus 7 (2013) Original Android Development] osm0sis:
Fixed-Fixed up. :p

http://v.ht/osmod

Decided to run the root services from the fkbootscript.sh instead.

Also put up a test r13 version with a deb ramdisk. I based it from the latest deb KVT49L Factory Image. Hopefully someone can let me know if it works or not. If not, I'll start grabbing AOSP ROM kernels and seeing what the differences could be. :good:
[Nexus 7 (2013) Original Android Development] sizzlers:
Where exactly is the thermal control In the FKU app. Someone said it has but still can't see

---------- Post added at 09:03 AM ---------- Previous post was at 08:26 AM ----------

Also is it normal cpu to stay at 918 mhz and not to go down to 384?how to fix
[Nexus 7 (2013) Original Android Development] pietropizzi:
Thanks osm0sis !

Confirmed DEB Kernel booting up on Stock KT49H. I have Multirom so I can test on my dayly Rom (Slim) too if you want.

EDIT: OK, played with it for half an hour. Realized with Trickster CPU on all Kernels at 1728 when sceen on. Seems it booted up with performance-governor (!)

Tried to change to interactive --> Blackscreen --> forced Reboot.
[Nexus 7 (2013) Original Android Development] poondog:
Have you got USB otg mounting? It's not in stock but I believe the ramdisk overwrite from this kernel has broken my otg on slim

Thanks ?
[Nexus 7 (2013) Original Android Development] osm0sis:
OTG should work on Fixed-Fixed since I just started from r13 and added my tweaks again. Unless it never worked?

Deb probably won't because stock doesn't have that. That performance issue is weird, I'll see what I can figure out. Maybe a permissions thing that's fixed in AOSP, but not so in Stock. But hey, at least I got it booting! :D
[Nexus 7 (2013) Original Android Development] RobbieL811:
You are gonna have to install "Stick Mount" & the latest version of "SuperSU". That will get your OTG going. That's how I do it on mine. With FK, it will no longer auto mount like it does with the Slim kernel.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] hardwareadictos:
For troubles with OTG you can watch this video of my youtube channel, its in spanish but i hope it helps you :) : Conecta un USB a tu dispositivo Android | OTG: https://youtu.be/RTdnxAkOgEc

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] masri1987:
Can I use this on Vanir?
[Nexus 7 (2013) Original Android Development] tetakpatak:
Hello, guys! I was damn serious :D

So, now I'm part of the family here- moving a bit from the Samsung threads here to.

I'm enjoying the 4.3 kernel so far on rooted stock. Thanks for sharing, FF, and big compliments.

The stock ROM with r4 feels good, so I'm gonna tweak it with few frameworks and figure out more about my new Nexus.
[Nexus 7 (2013) Original Android Development] osm0sis:
Yup, it was never there in f.K-flo to begin with. On it. ;)

https://github.com/CyanogenMod/andr...mmit/4a0f112e22f5118787d6b6ce0d777259161350e2

Syncing up things between the flo and deb ramdisks and then I'll upload new versions. :good:
[Nexus 7 (2013) Original Android Development] osm0sis:
Done. New r13: flo-fixed and deb-test up.

http://v.ht/osmod

Native USB-OTG working (ie. no app required), and hopefully fixed the governor issues with deb to make it fully functional (disabled mpdecision service and added interactive permissions tweaks to match the flo ramdisk).

[MENTION=1123267]pietropizzi[/MENTION] [MENTION=4379011]poondog[/MENTION] [MENTION=3292224]franciscofranco[/MENTION]
[Nexus 7 (2013) Original Android Development] dimebagdan65:
We have GOT to get you a Nexus 5 dude... Would love to see you work your magic on Franco's work there!
[Nexus 7 (2013) Original Android Development] osm0sis:
:D
[Nexus 7 (2013) Original Android Development] poondog:
Cheers man ill flash when I get home :)
[Nexus 7 (2013) Original Android Development] pietropizzi:
Thanks osm0sis, it booted up fine with the fixed deb! Interactive was default and the FREQ-Range is fully used. I'll play some more with it but it looks good till now ! ?

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 (2013) Original Android Development] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION] Achievement Unlocked: Deb Support! :cowboy:

Someone go quote me in the N5 thread so he sees. ;) :laugh:
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Looks like I can update my learner lounge thread now then ?
[Nexus 7 (2013) Original Android Development] justibasa:
Reboot on r13 fixed running carbon. Was sitting on the table not being used when it happened.
[Nexus 7 (2013) Original Android Development] osm0sis:
Logs or it didn't happen. :p

Please post a /proc/last_kmsg or you posting that a reboot happened is absolutely useless. :good:
[Nexus 7 (2013) Original Android Development] justibasa:
Yeah my bad. I got the log and then forgot to post it. Here it is. http://pastebin.com/EW5NXsbX
[Nexus 7 (2013) Original Android Development] osm0sis:
Looks like it was something to do with that emergency remount stuff. Not sure what it's about. The fstab options are the same as the lastest AOSP ramdisk. For now we can chalk it up to random derp. Let us know if it happens again/frequently. :)
[Nexus 7 (2013) Original Android Development] justibasa:
Will do. Thanks for looking at it my friend. ;)
[Nexus 7 (2013) Original Android Development] tommi.a:
The possibility for flo in r13 to have a really low back light minimum is great.

I'm searching for a way to switch between these few very low levels via script because with the backlight slider it's almost impossible to select the back light between these low values.

How can it be configured? Can it be accessed from sys file system?
[Nexus 7 (2013) Original Android Development] tetakpatak:
There is a great little app called Root Dim.

Try it, you may like it ;)

tetakpatalked from Nexus 7
[Nexus 7 (2013) Original Android Development] habylab:
Also, Twilight, and Chainfire has redone his CF.Lumen app.

Sent from my CM11S Galaxy S3. Proud Googy Beta tester.
[Nexus 7 (2013) Original Android Development] tommi.a:
Thanks, that works!

However, I still would like to know if I can access the setting from a one line script.

Does anybody know?
[Nexus 7 (2013) Original Android Development] dimebagdan65:
About to flash Osm0sis' fixed version however I remember last time that flashing it over Franco causes bootloops and the remedy/recommended method is to flash stock kernel then Ozzy's fixed version. Is this still the case?
[Nexus 7 (2013) Original Android Development] tommi.a:
Thanks, but I only asked for reducing back light (which saves battery in addition), not adding a color filter.
[Nexus 7 (2013) Original Android Development] osm0sis:
I've never heard of that. ;)

Flashing stock kernel would make zero difference since both have ramdisks. Maybe if we were talking AnyKernel.. :)

I always flash right over through f.Ku. Do it.. :p
[Nexus 7 (2013) Original Android Development] dimebagdan65:
Straight from the horse's mouth! And a'flashin' we shall go! Thanks bro ?
[Nexus 7 (2013) Original Android Development] znhel:
No hope of Franco kernel version N7 2013 DEB?

Thanks

P.S. Unfortunately, not knowing the English language it is impossible to read all 3d using google translator as well as the translation is very rough

---------- Post added at 11:28 PM ---------- Previous post was at 11:26 PM ----------

No hope of Franco kernel version N7 DEB? :p

Thanks

P.S Unfortunately, not knowing the English language it is impossible to read all 3d using google translator as well as the translation is very rough :confused:
[Nexus 7 (2013) Original Android Development] RobbieL811:
I'm not absolutely sure but I think that 0smosis got a FK version working on the Deb just this past week! I think that there is now a Deb version.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] znhel:
Ahhh ... that's great news!

Could someone confirm this?

Buy you a drink to those who pass me a link to Franco kernel for N7 2013 version DEB

Thanks RoobieL811:good:

Unfortunately, not knowing the English language it is impossible to read all 3d using google translator as well as the translation is very rough :confused:
[Nexus 7 (2013) Original Android Development] RobbieL811:
http://d-h.st/users/osm0sis/osmod
[Nexus 7 (2013) Original Android Development] znhel:
:good:

One more question .. you can flash the kernel linked on the N7 2013 stock rom (Kitkat4.4.2)?

I'm no expert and I would not combine a mess .... I've already combined a lot! :p

We are grateful ;)
[Nexus 7 (2013) Original Android Development] RobbieL811:
I don't know that I understand your question. The only kernel that I would flash would be the one that's marked for the Deb.

Edit - This one. http://d-h.st/a13. Are you asking about what you should flash to revert to stock?

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] znhel:
the kernel is compatible with stock rom 4.4.2?

I only ask this!

I ask again sorry for my english but the google translator does not help an Italian who does not know English .. I am ashamed to even ask, but I'm 60 years old and in my time not studying languages
[Nexus 7 (2013) Original Android Development] RobbieL811:
Lol. Sorry. I understand now. Yes. It should be compatible with stock ROMs & AOSP based ROMs. It will not work with any CAF based ROMs. Hope I helped some.

Sent from my Nexus 5
[Nexus 7 (2013) Original Android Development] morbidj:
Hey all... Could some one tell me the console command or text string to add to an init.d script to disable screen dimming? I really wish Franco would update his app to include full function support for this device kernel!
[Nexus 7 (2013) Original Android Development] averagegeek:
My Nexus 7 2013 is draining more with Franco kernel. Battery drain is around 14 percent /hour when I simply browse using Chrome, while battery drain is much more less on stock kernel. I am using interactive governor with deadline scheduling.

Can you help me to solve the issue?

---------- Post added at 03:35 AM ---------- Previous post was at 03:29 AM ----------

My Nexus 7 2013 is draining more with Franco kernel (r13). Battery drain is around 14 percent /hour when I simply browse using Chrome, while battery drain is much more less on stock kernel. I am using interactive governor with deadline scheduling.

Can you help me to solve the issue?
[Nexus 7 (2013) Original Android Development] tetakpatak:
Since how long are now using the franco-kernel? You should try to test both kernels by the same screen brightness to be sure. Fix the brightness to maximum or to 50% and try both kernels (stock and franco) under the same circumstances.

tetakpatalked from Nexus 7
[Nexus 7 (2013) Original Android Development] AndyYan:
Wow, so [MENTION=4544860]osm0sis[/MENTION] is here as well...

Quick question: if Franco isn't compatible with CAF ROMs (like official CM), what else kernel does (aside from Glitch, that one's not updated as of lately)? Isn't there any sort of "modified Franco" that goes with CAF ROMs, as seen on Nexus 4?

Sent from Google Nexus 4 @ CM11
[Nexus 7 (2013) Original Android Development] averagegeek:
Sure, I will try that