yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] shreddintyres:
The reason i say reproduce the reboot is because this file resets and only contains information from the latest reboot. You have a couple ways to do it, if you have a computer available the easiest way (after the tablet has completed booting (immediately following the random reboot)

adb pull /proc/last_kmsg <local_directory_where_you_want_this_stored>

Make sure the directory you are trying to store the file does not have any spaces in it or the command will fail and youll have to redo the command.

so just to be clear, flash franco kernel r1 allow the random reboot, on next boot pull last_kmsg

EDIT whoops i just read bootloop again, i somehow overlooked that, well in either case for anyone else who might experience a random reboot ^^ my apologies :good:
[Nexus 7 (2013) Original Android Development] shreddintyres:
wipe data and cache for FKu app then reboot, the app will automatically reset to stock Franco Kernel settings
[Nexus 7 (2013) Original Android Development] thecapitalr:
Sorry for the newbie question. Will r3 of this kernel work with the newest pac man builds? Thanks in advance for any help!
[Nexus 7 (2013) Original Android Development] OJ in Compton:
I know franco is busy working on the update to his app, but when r4 releases I think it would be really helpful to add a section in the FAQ regarding the CAF sources "situation" and which ROMS use/don't use it.
[Nexus 7 (2013) Original Android Development] creeve4:
Is it just me or is Fast Charge not working? (I tried searching, but search has been down for a little while).
[Nexus 7 (2013) Original Android Development] borxnx:
Si

---------- Post added at 12:26 AM ---------- Previous post was at 12:20 AM ----------

This is the responsibility of the user, not the dev, and frankly is not very difficult to understand or keep up with. Plus it has absolutely nothing to do with Franco's kernel. Plus you can always just ask someone.

Perhaps you could do some research and draw up a compatibility table and write up a CAF/AOSP compare/contrast for us in the FAQ section?
[Nexus 7 (2013) Original Android Development] shreddintyres:
Agreed, Moreover, you can always look at the github accounts for the rom you use if its not specifically stated in the description whether they are CM (CAF) or AOSP based. There are certain aspects of AOSP which pull from CAF but is nevertheless AOSP this has also been endlessly discussed here on XDA as well as many tech blogs if you wish to learn more about CAF vs AOSP. If you dont know if your rom is compatible with this AOSP kernel ask your rom dev if its a CM/CAF base or AOSP.
[Nexus 7 (2013) Original Android Development] OJ in Compton:
last edit: looking back at how I worded my post, yeah I agree that a list of Roms is excessive. Faq#2 does need to be changed though, perhaps a sentence saying this kernel is built for AOSP-based Roms and may have issues on roms using CAF sources? Only use the last bit if you're feeling generous ;)
[Nexus 7 (2013) Original Android Development] Warbuff:
Cm broke compatibility with kernels because of CAF changes
[Nexus 7 (2013) Original Android Development] droidroidz:
I dont think it is working correctly either.

sent by my android.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Am I correct in thinking to get back to the latest 'stable' Franco app I have to uninstall it and leave beta testing and reinstall? I want to try it to see what other options there are on my flo.

Also just read about Franco teaming up with super curio to get this beta display mod out I'm physced to try it when I'm home! Is there a way the colour control settings in the fku can link to open super curios app? Like how system monitor does? Obviously the free version and opens the paid one if licence is detected
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Right. Leave beta testing. Uninstall and reinstall.

There's no color control on fku. But there's support for supercurios app which can be bought on play.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
I see, the colour control tab is just there but with nothing built in as its aplha still, makes sense.

As a pretty pretty please feature request Franco would you consider letting your app open the free version of super curios app and allow it to behave like how system monitor does currently? When its ready and if super curio allows ;)
[Nexus 7 (2013) Original Android Development] dud3me:
Anyone else get these weird battery drops? I get one from 34% to 23% almost every time I leave the screen off at close to 35% and then just let it sleep. I've tried to "calibrate" the battery by doing a full discharge/recharge but now it's back. I'm using unofficial PA from Android development sub forum. Sometimes it even goes up 2 or so % :confused:

I'll try with a different kernel to see if I can reproduce. Hate to leave Franco, though, as it seems to work smoothest for me. :(
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Can we not just say cm is not supoorted anymore? I follow Franco on gnex, n7, n7 2013, n4 and littetally all you hear about is stuff going wrong with cm or cm based roms. If these users want the refined product of Franco then they should use aosp rom or stock rom. Cm just keep going off doing things in ways that don't work in compatible ways, starting with colour control last summer I believe. Since then it has gone on to them using completely different drivers for certain Qualcomm chips and frankly if everyone moves to keep things compatible with cm then there won't be time for new development. So I propose you make your bed and lay in it if you choose cm based roms or be happy with aosp. Its splitting android into further fragmentation. Cm are now a buissness, they have gone corporate leaving bed room devs behind
[Nexus 7 (2013) Original Android Development] kecinzer:
[MENTION=3295693]dud3me[/MENTION]

Yes, I have this drops too :).
[Nexus 7 (2013) Original Android Development] dud3me:
Have you noticed it on other kernels as well?
[Nexus 7 (2013) Original Android Development] mrbradeli:
Still dealing with wifi issues after doing a complete wipe and going back to stock w/ franco r3, but I guess that's unavoidable on any rom/kernel combo. The randbom reboots seem to be gone though.
[Nexus 7 (2013) Original Android Development] Nexus11:
Did Franco ever add fast charge?
[Nexus 7 (2013) Original Android Development] poondog:
I have it slightly on my device too, but it is 100% stock bootloader still locked. Sometimes I come back to it and battery has gone up a bit, sometimes it goes down a bit. I'd say it's normal
[Nexus 7 (2013) Original Android Development] dannaoj:
is the kernel for flo and deb the same here?

i cant seem to see any download for deb

thanks in advance
[Nexus 7 (2013) Original Android Development] poondog:
http://xdaforums.com/showpost.php?p=45632882&postcount=2

Same kernel works for both
[Nexus 7 (2013) Original Android Development] creeve4:
I'm getting looping force closing of com.android.phone after flashing Franco kernel on a self compiled AOKP build from yesterday. Anyone else?
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
Me too. aokp includes changes from cm, which need a corresponding modification in the ramdisk of francos, or any other kernel using a custom ramdisk. Its just a few lines of code to be added, I'm gonna edit it and test now. Will post here if it works fine.

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] creeve4:
Why does AOKP use ANYTHING from CM for a nexus device!?!
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
OK. So I modified franco's ramdisk ( just a single line edit ) to add compatibility with roms using upstream commits from cm ( Carbon, aokp... ). Tested working on aokp. Solves force closing of com.android.phone.

Download here... http://www.mediafire.com/download/sx1dr4pcluvpnxn/franco.Kernel-nightly-r3-patched.zip

thanks to [MENTION=4544860]osm0sis[/MENTION] for his nice ramdisk tool :)

[MENTION=3444353]creeve4[/MENTION] no idea mate. that's something you have to ask the aokp team. Seems all roms ( except PA,omni) are cm dependent now.
[Nexus 7 (2013) Original Android Development] zaclimon:
Where I could have this tool osmosis made? I would like to add a line to add compatibility for new pac roms as well! :)

EDIT: Nvm I found it but looks like I need windows in order to use it...

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 7 (2013) Original Android Development] kecinzer:
Because of better cdma support.
[Nexus 7 (2013) Original Android Development] creeve4:
Deleted, off topic
[Nexus 7 (2013) Original Android Development] creeve4:
What change was required?
[Nexus 7 (2013) Original Android Development] notoriouspk:
this works well with 25oct nightly working good thanks
[Nexus 7 (2013) Original Android Development] franciscofranco:
r4

* Merge KEXEC patches to work with MultiRom from Tassadar

* Merge all the work on the Hotplug driver from Mako

* Merge all the work on the GPU governor from Mako

* Merge my latest touch boost implementation directly from Mako

* Disable AVS to allow for true undervolting (with AVS enabled it would regulate the voltages back to its default values internally)

* Enable Module support for TouchControl

* Should work fine with the latest PAC and Carbon rom nightlies

* Other misc changes available on github repo

I was hoping for 4.4 to hit earlier, so I was holding off this release, but I'm glad I did because I could merge my latest codes from Mako. Hope you like it!
[Nexus 7 (2013) Original Android Development] Hanny:
Miasmic landed on Flo

Flo mpdecision kernels vs r4 gaming test

mpdecision ondemand timer_rate = 20000

Beach Buggy Blitz

Average FPS = 35

Real Racing 3

Average FPS = 30

r4 interactive default timer_rate = 25000

Beach Buggy Blitz

Average FPS = 35

Real Racing 3

Average FPS = 30

Let's decrease FK timer_rate to 20000 (better for gaming!) and also make the test fair

r4 interactive modified timer_rate = 20000

Beach Buggy Blitz

Average FPS = 38

Real Racing 3

Average FPS = 32

Behaviour

mpdecision = 2 cores constant 1512, others 2 offline, oh wtf

FK = 4 cores, a lot of 384 and 486, still smooth + significantly cooler

Just got asphalt 8 and im not bothering to do anymore mpdecision test again ^^
[Nexus 7 (2013) Original Android Development] TheDarkDefender:
https://github.com/franciscofranco/ramdisk_mako/commit/af4db582c5959672a30690bd174e9d039f1c1ff4

Sent from my Nexus 4
[Nexus 7 (2013) Original Android Development] ktkr:
[MENTION=3292224]franciscofranco[/MENTION] Is there an alternative method to get FKU other than Google play store? I don't know why but every time I tried to purchase FKU Google cancels the order but I can purchase other apps normally.
[Nexus 7 (2013) Original Android Development] Kumczak:
Does this kernel have usb-ethernet dongle drivers? I suppose it doesn't, so would it be possible to add this drivers in one of the next releases?
[Nexus 7 (2013) Original Android Development] Warbuff:
Posted wrong info. Please delete.
[Nexus 7 (2013) Original Android Development] dud3me:
Okay, I did some further testing and here's what I found. Battery drops from 33% to 23%, always to 23% while sleeping. Happened on r4 too. However, I did not notice it on latest elementalX :confused: Same rom too.

To be fair I just installed back to franco, so I'll have to see if it happens again. Oh and the battery might go back up 1% or so but not much more and it it still drains normally.
[Nexus 7 (2013) Original Android Development] poondog:
I think this might answer your question/problem :)

http://xdaforums.com/showthread.php?p=46733968#post46733968
[Nexus 7 (2013) Original Android Development] dud3me:
Well that sucks. Strange though that I didn't (presumably) have it on elementalX. And the fact that it's always the exact same jump. Will have to do a complete stock test once kitkat hits :( However, if there really isn't anything wrong with the battery, then it's a struggle for me to get 5h screen on time (in <24h of on battery) with moderate usage.

On the other hand deep sleep battery has been amazing on this device. Barely get any drain during the night.
[Nexus 7 (2013) Original Android Development] poondog:
I had 6 hours screen time in just under 3 days, mostly playing light games and browsing internet/xda plus watching videos using stock streaming player

This is with the battery spikes so personally I don't see them as a problem.
[Nexus 7 (2013) Original Android Development] dud3me:
Well, I wouldn't be complaining either if I had that kind of battery life. ;)

Antutu scores are down on r4 around 1000 points compared to previous release. Scores lower than stock aosp for me. This was on stock Franco settings, gets a little higher with ondemand if someone cares.

Can't really say about actual performance but [MENTION=3614073]Miasmic[/MENTION] post seems promsing :p

Edit: Just had fps drop super slow, seemed like slow mo but still usable. Was especially noticeable in app drawer scrolling. Reboot solved it, though. Btw, what's the most useful log for kernel developers in case of an error?
[Nexus 7 (2013) Original Android Development] creeve4:
With AVS disabled in r4, can we expect worse battery life if we don't undervolt? Can AVS be enabled for those of us that don't wish to undervolt?
[Nexus 7 (2013) Original Android Development] franciscofranco:
No.

No, its disabled in the Kernel config.
[Nexus 7 (2013) Original Android Development] goldflame09:
Best log is last_kmesg
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
I played asphult 8 earlier. Was very smooth, ran real nice in with high level of graphics. The fps seemed quite constistant although I didn't measure or measure CPU freq or how many online. Was a pleasure to play, this update is great thanks
[Nexus 7 (2013) Original Android Development] habylab:
For some reason, root access has gone after update, never had this happen before, odd!
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Just flash supersu 1.65 again in recovery and you will be sorted
[Nexus 7 (2013) Original Android Development] franciscofranco:
?

I'm on stock, using SuperSu, flashed a bunch of Kernels, root works fine :/
[Nexus 7 (2013) Original Android Development] franciscofranco:
Yeah don't bother measuring anything, just flash and forget, it works as it should :)
[Nexus 7 (2013) Original Android Development] habylab:
I know, did that straight away, thank you!
[Nexus 7 (2013) Original Android Development] bobloadmire:
So now that cm is no longer supported, what's a good romantic to use with this? Stock rooted?
[Nexus 7 (2013) Original Android Development] sevenslugs:
Headphone boost/gain are not sticking in r4 ...works fine in r3
[Nexus 7 (2013) Original Android Development] goldflame09:
stock, modded aosp, pac, anything using an aosp base
[Nexus 7 (2013) Original Android Development] droidroidz:
rasbeanjelly!!!!

sent by my nexus.
[Nexus 7 (2013) Original Android Development] Marescallus:
Are you talking about after a reboot, or just after a certain amount of time? Does it just go away?
[Nexus 7 (2013) Original Android Development] sevenslugs:
Even after reboot...I'll change the default gain, open up the settings for it again and its always the default value.
[Nexus 7 (2013) Original Android Development] GialanG:
My battery drops crazily in idle time (wifi off, bluetooth always on to make sure the Nilkin cover works all the time) after updating to r4, 30-40m 1%, compared to 4h 1% of r3. I'm running MultiROM, PA 3.99 as secondary. Now I'm back to r3 already, waiting for the next update...
[Nexus 7 (2013) Original Android Development] Nbsss:
Is anyone having issues with usb-otg?

It works well but if I turn off the screen, the power supply cuts off ie lights stop flashing and so I have to remove and reconnect.
[Nexus 7 (2013) Original Android Development] Cruiserdude:
For anyone having issues, make sure you're on an AOSP rom. This has been discussed extensively, but many roms are CM/CAF based, and therefore not AOSP. Find one that is true AOSP, and confirm with the dev that they in fact pull only from AOSP sources, or learn how to diff the source yourself. Stock or Flonaro (stock with true Linaro -o3 optimization) are all I've used, and with GravityBox I don't need a rom.

I know most of you know this, but I'm just making sure, as Franko only needs to hear about your issues if you're using a rom that his kernel is designed for.
[Nexus 7 (2013) Original Android Development] bokoy:
So are you saying r4 is only for AOSP roms? Seriously?

If it is like that franco should say it in first post or many users will find big issues like me. I read the changelog and says merged with AOSP, not just for AOSP.

I have been using this kernell since r1 whithout an issue and as franco says it works with al roms, I was stock rooted with twrp and ever worked fine, r4 mess all up, mainly in games. I had to restore the tablet.
[Nexus 7 (2013) Original Android Development] goldflame09:
Stock is aosp btw.

You can try it on a caf rom and see what happens. Might work or might not
[Nexus 7 (2013) Original Android Development] bokoy:
I don't want caf, just stock but r4 was a nightmare, I will not try it again. Is there any kernell cleaner for flo?
[Nexus 7 (2013) Original Android Development] borxnx:
If you're stock rooted then you're on an AOSP ROM. Can you provide more info related to your issue and setup?

Edit: didn't see last page here. You can get a pure stock rom and flash in twrp, that will wipe /system and thus "clean" your kernel. Or restore stock in fastboot.
[Nexus 7 (2013) Original Android Development] bokoy:
JSS15R, unlock+super su 1.65+TWRP 2.6.0.3 and franco kernell r1, r2 and r3, all worked perfect with no issues at all. Installed r4 wiping cache and dalvik and all woked fine till you launch a game FF6, jungle heat, dead trigger 2 all like 2-10 fps, it was like if the graphic card was totally broken and maybe the processor. I must say I just install the kernell and leave it stock, I don't change any value.

After restoring with the one click restore problems are gone with the kernell.
[Nexus 7 (2013) Original Android Development] dud3me:
I think I had the same on AOSP based rom as well, only mine happened when scrolling in app drawer. Reboot solved it. I also ran with the default settings.

Here's my second battery cycle with r4 and I'd really like opinions on it. Especially note the erratic behavior of battery %. It went down to 22% from about 31%, then it went up one and again down and at 19% it went back to 20% but only 1% ups.

Basically if it's just shi*** battery gauge, I should get normal battery life? The thing is, I usually charge it when it reaches 20% and tells you to connect charger :p

This was quite heavy usage, around 40min playing fpse and then some youtube and browsing with dolphin, falcon, fb and xda. I guess I'm wondering how the hell some people get around 10h of screen on time :D Screen was on 50% brightness.

Other, then the low benchmarks and that one bug, the kernel seemed to run fine. Although, I don't really know if gaming was any smoother and franco has always run cooler than stock.
[Nexus 7 (2013) Original Android Development] Marescallus:
http://xdaforums.com/showpost.php?p=35648172#

Try this. It's written by osm0sis, who helps out a lot in the Galaxy Nexus thread for Franco. I've used it on mine, and it's worked. Make sure to back up your stuff though, just in case.
[Nexus 7 (2013) Original Android Development] SupWiz17:
I also have to say I have enjoyed all of the releases for this device but r4 is very choppy especially in game play. I'm going to try and go back to on demand and see how it is there. I'm sure he just changed some tuneables to get even better battery life out of this device and that is causing the sacrifice of performance.
[Nexus 7 (2013) Original Android Development] droidroidz:
r3 default gov was ondemand..r4 is interactive which seems to be scaling back to 384 much better than ondemand does. Ondemand likes to hang out at max it seems which might be the reason for lower gameplay in fps intensive games.

I would suggest changing some tunables in interactive to ramp up max faster and scale back slowrer. Or change back to ondemand as suggested above

sent by my android.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
I don't understand how for you guys gameplay isn't working well. This kernel is basicly exactly the same as 193 for nexus 4. New hot plug algorythem, GPU has had a interactive governor written for it by Franco. You guys should clear your Franco app data and reboot. Or think about getting some better games, I have spent a good few hours on asphult 8 and dead trigger without issue
[Nexus 7 (2013) Original Android Development] ortrigger:
Asphalt 8 is smooth as butter for me as well. I'm using interactive governor also.
[Nexus 7 (2013) Original Android Development] mrbradeli:
Loving r4 so far. One thing really weird that I noticed was video playback suddenly looking a lot better. Before it seemed that there was some kind of black crush issue or whatever its called but it just cleared up sometime between flashing back to stock and updating to r4. Weird.
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Yup, I'm just using the default values, expect a bit of headphone boost and gain. Everything else as it is,using fku app so I know trickster app isn't pulling any funny **** where some things like GPU gov may not be written in it.
[Nexus 7 (2013) Original Android Development] ortrigger:
I used to use trickster but it always had some kind of glitch. Recently purchased fku and love it. This is probably the best kernel I've used for my Nexus 7. You can't beat the simplicity and performance.
[Nexus 7 (2013) Original Android Development] Hanny:
If anyone is not satisfied with gameplay, tune timer_rate from 25000 to 20000 in governor control and set on boot as you wish. Yes I noticed observable stutters since r191 on mako but the setting of 25000 has been receiving a lot of positive feedback about battery life improved, though it is already good before.

So as an extensive gamer and tester, that's what I did on both mako and flo. ;) And that does not have really big impact on the battery in my opinion.
[Nexus 7 (2013) Original Android Development] threepwood960:
Flashed, but where can it be configured? Sorry I don't find it. :confused:

Enviado desde mi Nexus 7 usando Tapatalk 4
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
You need to either use terminal commands or buy francos app from play store which i beleive is currently on sale
[Nexus 7 (2013) Original Android Development] creeve4:
What is the difference between the Volume Boost and Gain settings? I have somewhat of an understanding of these terms in the context of an amplifier, but how do they apply specifically to a mobile device like the N7?

Also, I noticed in franco's kernel source for the flo that there is no support for audio gain... currently only headphone volume boost is supported (unless I am missing something).
[Nexus 7 (2013) Original Android Development] threepwood960:
Thanks. Can't I activate sweep2wake from other place?
[Nexus 7 (2013) Original Android Development] The Gingerbread Man:
Im not sure it works on this device, theres an app in play store you could check compatibility or search on google or xda
[Nexus 7 (2013) Original Android Development] AnarchoXen:
Swipe to wake along with tap to wake work on this devise. You need a kernel to support it. Three is a mod of this kernel that does it. It is in a different section.
[Nexus 7 (2013) Original Android Development] franciscofranco:
Freebie: AOSP 4.4 for Flo. Don't flash any Kernel on top of this or hell will break lose: https://plus.google.com/u/0/106873500108976028532/posts/diQ8u2UbKPH