yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Sorry guys, I'm out of thanks atm :p

[MENTION=7918241]qlver[/MENTION] Interesting. Sounds like it may have to do with the bootloader then. Are you running the latest (04.05 it seems) or an older one ? Thanks :)

[MENTION=7213002]coremania[/MENTION] Ok, that tends to prove that default settings for the backlight dimmer will end up giving different results depending on your panel model. I'll add a notice about that and disable it by default in next release. Thank you !
[Nexus 7 (2013) Original Android Development] boom1982:
Maybe, it was saosp n rom)
[Nexus 7 (2013) Original Android Development] qlver:
According to the bootloader screen, mine is 04.08, and now I pick a stable OC setting to prevent my device from a random reboot which may cause bootloop.

Now I can enjoy a powerful flo.

I believe that it's the best situation I can get, haha. :D
[Nexus 7 (2013) Original Android Development] boom1982:
Can I use this driver. It improves performance gpu?

https://xdaforums.com/nexus-7-2013/themes-apps/marshmallow-qualcomm-adreno-gpu-drivers-t3228000
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

Depends on the rom you are using. If you're on 7.0 or newer, your rom already has a newer driver and you will most likely get a bootloop trying to replace it with these old ones.

[MENTION=7918241]qlver[/MENTION]

My bad, I'm on 04.08 as well. Google wasn't a friend on this one !
[Nexus 7 (2013) Original Android Development] boom1982:
rom slim 7.1.1 , opu 1512, gpu 450 - old driver

look at 3d test score

http://www.picshare.ru/view/7944338/

and how many score you have?

p.s. I use this driver https://yadi.sk/d/xo4msNLw3EjzBA

it works fore android 7.1.1 and 6.0.1
[Nexus 7 (2013) Original Android Development] borxnx:
The thread you linked above states that it is for the December 2015 Marshmallow ROM for N7, build number MRA58. The ROM you are on is over a year newer. I would assume that whatever you have is newer than the one you linked. But if it works, then great! Report back if it does!
[Nexus 7 (2013) Original Android Development] boom1982:
it works)

driver - link in the previous post

Please tell me,when should I do reflash the kernel (for f2fs), before or after change partition format?

That to internal storage remained intact

Sorry for my English :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

Indeed some older adreno binary drivers did work and gave a bump to some benchmark scores. I couldn't measure performance gains in the few games I installed but definitely worth a try if encountering stutters in some specific games I suppose.

About your f2fs question, the kernel installation script detects the partition layout (and depending on your rom, will prevent system to be set as F2FS for compatibility reasons), so you should reflash the kernel AFTER modifying your partitions for their format to be detected. The recommended/optimal layout is system as ext4 and cache+data as f2fs.
[Nexus 7 (2013) Original Android Development] 228aye:
[MENTION=3847629]Tk-Glitch[/MENTION] hello! thx 4 your nice and fast kernel, use it with LineageOS, F2FS. settings default kernel suitable for productive work of the tablet? What hotplug and governor should I choose for performance?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7485561]228aye[/MENTION]

For speed, msm_hotplug is definitely the fastest on the hotplug side. For the governor, interactive or ondemand are really close. Ondemand will most likely give better benchmark scores though interactive will "feel" smoother overall. You should try both for a little while and keep the one you prefer.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Hello TK, this is nothing to do with the above message, but I'd like you to maybe help me with an issue. After flashing an N ROM last night, then as usual, I flashed r543 that resulted in a bootloop. Now, the only thing I'd changed was TWRP (version 3.0.3.3 unofficial). When I reverted to 3.0.2.0 everything was ok.

It has been suggested to me that your kernel may need an updater script/update binary update to allow flashing on TWRP version 3.0.3.3.

Does this sound right to you?

Many thanks for all your hard work...
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Hello [MENTION=5863767]SHABBYLEA[/MENTION] !

Thanks for letting me know. Yes, it's definitely possible. I'll check and update accordingly.
[Nexus 7 (2013) Original Android Development] boom1982:
My favorite file manager is not working ...Root Explorer

stock kernel - working

r543 - does not work..

I'm thinking about suicide :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

I'm using it daily without issue on lineageOS nightlies so that's strange.. Is your rom secondary or something ?
[Nexus 7 (2013) Original Android Development] boom1982:
one rom - slim 7

Probably it's in it ..)

Now I use Solid explorer, it works
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

Maybe something to do with a specific root method/manager ? I'm not home but I'll check asap. Thanks for reporting :)
[Nexus 7 (2013) Original Android Development] boom1982:
maybe)

I use superSU 2.79 (stable)

The application just "hangs" And does not work

Thank you for your reply)

p.s Try the driver for which I gave a link - it's better with them :)

https://yadi.sk/d/xo4msNLw3EjzBA

(but the first kernel load should be without them)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks TK...?
[Nexus 7 (2013) Original Android Development] Olivier V:
Great kernel but, and I know this is a pretty minor issue, when installed with the latest Lineage OS it freezes everything when I open the camera app. Both the Google and the one provided with the ROM. Only a reboot could fix it.

I've gone back to the standard lineage kernel and the problem is gone.

Am I the only one who had this problem?
[Nexus 7 (2013) Original Android Development] xaforib:
Just tested out this kernel, so far so good.

I got tablet installed in my car, USB pin #5 (ID) is permanently shorted to ground to force OTG mode all the time, I'm using kind of "Y" OTG cable to charge the tablet & power devices.

Tablet gets power when I turn the key, there's USB hub with flash drive and DAC connected to it.

So there's the request; can you make charging + OTG enabled for fixed installs? Completely disable powered OTG.

Kind of like ElementalX in version 5.16 or Timur's Kernel, if you know what I'm talking about.

Thanks and sorry for asking
[Nexus 7 (2013) Original Android Development] boom1982:
Remix Rom - Root Explorer works good)

But I noticed a feature of the work gpu, in Bonsai benchmark

stock kernel (RR) - all is well

r543 - Begin lags and drawdowns FPS

(I did not use my driver, only default r543)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5088575]Olivier V[/MENTION]

There has been some updates on the kernel side for LineageOS lately. Merge's done and r544 will be available in a few. Please keep me aware if your issue isn't fixed after updating to it. thanks :)

[MENTION=4146736]xaforib[/MENTION]

I suppose the switchable hack available through aroma isn't working properly/good enough for such an installation ? I'll have a look at flar2 and timur's sources then ;)

[MENTION=7890918]boom1982[/MENTION]

I tried to make this kernel as "universal" as I could, but since it's based on LineageOS, different roms may or may not be affected by some compatibility issues depending on the base used or added mods. Some specific adreno binary drivers combinations may lead to corruptions or strange behavior (I've got some video playback corruptions after a few days with one of the latest binaries in the thread you linked previously using LineageOS for example). RR kernel may differ in some ways on the GPU handling or driver interaction compared to the LineageOS kernel base, leading to your results. I'll investigate further.

[MENTION=5863767]SHABBYLEA[/MENTION]

I'm stuck with a very strange configuration right now on my N7 and I'll not be able to flash a different recovery until I'm done with it so I tried to find some information on your issue. I have found some bug reports about TWRP 3.0.3+ recovery on two fronts regarding aroma compatibility issues as well as failing busybox calls. Supposedly, 3.0.3-3 should have fixed aroma issues, but busybox calls seem to still be a problem as of 3.0.3-4. Since I'm using some busybox calls on both my packages, would you mind if I ask you to send me some installation logs to try to understand better what's failing ? Hopefully it'll be explicit enough. Thanks !
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Will do...

Thanks.
[Nexus 7 (2013) Original Android Development] boom1982:
But RR based on lineage os.. :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

I was able to get a friend to try flashing r544 with [MENTION=5480152]followmsi[/MENTION]'s latest TWRP 3.1.0 with both full and pure packages multiple times and he was able to boot smoothly. So whatever happened with 3.0.3 seems to be fixed with 3.1.0.

[MENTION=7890918]boom1982[/MENTION]

Just tried Bonsai benchmark and got no fps drop. Your settings could be unstable. Try to lower overclocks if any (especially GPU and cache/L2) and try using ondemand governor if you're using interactive. Definitely not a kernel issue.
[Nexus 7 (2013) Original Android Development] boom1982:
I did not notice the update))

Maybe it will be better with him)

I do not really understand the point in the installer

"Enable max suspend frequency"

Is this the maximum frequency when the display is off?)
[Nexus 7 (2013) Original Android Development] xaforib:
I never looked into android/kernel development, but can you completely disable powered OTG mode? The problem is that tablet will go into powered OTG mode all the time, ignoring that it has power.

From my tests it seems that if I apply power and then connect OTG cable it will work fine. However for such installation otg cable is connected all the time, and power is applied only when car is running.

Thank you so much for replying!
[Nexus 7 (2013) Original Android Development] coremania:
Thx buddy, 544 awesome as usual, flo is flying on latest tesla, great :)
[Nexus 7 (2013) Original Android Development] Olivier V:
Thanks for the update, sadly the problem that the whole system freezes when I launch the camera app is still there.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5088575]Olivier V[/MENTION]

Any OC ? While I wasn't able to reproduce your issue on my own device, I was able to with a very high cache/L2 OC on another one. If your L2 is overclocked you might want to try with a lower setting. Too much GPU undervolting could also cause this.

[MENTION=4146736]xaforib[/MENTION]

I see. The so called thing the original N7 was better at. It looks like it'll need a specific kernel branch. I'll push some updates in this thread depending on my results as I will not be able to test this myself.

Exactly. Your device can have some work to do even when the display is off, like updates, notifications, music playback, etc. This setting prevents your CPU to clock up past the frequency you set to help with battery consumption. Depending on the workload you may or may not want to use it, but for "normal" use it should most definitely be on.
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

And what max frequency is used when this point is turned off?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

The maximum stock CPU frequency: 1512MHz.
[Nexus 7 (2013) Original Android Development] Olivier V:
I re-installed it with a more conservative OC and the Qualcomm drivers. Everything seems OK now, no more crashes :good:
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5088575]Olivier V[/MENTION]

I'm glad you got it fixed :)
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Thank you for your answers)

If there is time, tell me - what is the difference between:

upthreshold

upthreshold any cpu load

upthreshold multi core? :)

If there is no time, I'll understand)

I found the answer!
[Nexus 7 (2013) Original Android Development] 228aye:
Hello again! I'm trying to set up R544 For maximum performance. L2/OC - glitchy, GPU OVERCLOCK - GLITCHY 627 MHz. The processor frequency is only 1728 MHz, (it is stable) because the tests take off at 1890 MHz. I do not think that further increase in frequency will be stable, and will provide a strong increase in performance (correct me if I'm wrong). Now I'm trying to pick up a governor. Interactive and ondemand are good, but only for Governor elementalx has a special settings for smoothness as gboost/boost/etc. But for example, in Google Calendar, scrolling does not have smoothness. Can you advise what kind of settings governor elemental X will be able to minimize lags?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7485561]228aye[/MENTION]

You may be able to push the CPU further with lower L2 OC, but it won't change anything regarding Google Calendar scrolling smoothness. I've not seen it run smooth on any device I've used at this point to be honest. My korean G3 with snapdragon 805 CPU and Adreno 420 GPU and faster/more ram is much faster in every way possible than any - not LN2 cooled - fully overclocked N7 could be and Google calendar, while smoother, is not anywhere near smooth. So there's nothing you can do really, except switching to a different calendar app if it bothers you that much (older Google calendar builds were perfectly smooth for example).

The msm_hotplug driver already has a CPU boost mechanism so the elementalx governor has only gboost as a plus, though I don't like it. It's been slower than both interactive and ondemand for me, with various stutters only happening with this governor. It's been added after multiple user requests but it definitely doesn't suit my needs and I'm not/won't be using it. So after saying that you now know that I'm unable to give any advice regarding this governor except not to use it, but well, it's been requested enough for me to add it so it must be useful to some people I suppose ? I hope so !

The one who can give the best advice is by far flar2 himself.
[Nexus 7 (2013) Original Android Development] 228aye:
Ok! I will try to accept with this laggy Google Calendar, its not your problem. about the Governor, I still went back ondemand, and a one-time acceleration to the settings of "glitchy" I was very scared because of the strong batterydrain. moreover, the practical application of this power I still don't see it, this is just an experiment. also, wanted to mention one Russian developer kernel for FLO. He argues that the acceleration OC/L2 on our CPU only has a negative impact on performance. If you're interested in this - I can provide descriptions and kernel for your exploration.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7485561]228aye[/MENTION]

From my own testing, stability is key for performance as these devices tend to not crash unless stability is VERY VERY bad. Most people who are overclocking their Android device(s) are using unstable settings and then are asking why they have stuttering in game X, frame drops in game Y or low scores in benchmark Z. I've made the choice to give a large range of OC settings for my users to play with but reality is that a good 95% of them who are overclocking won't use such power correctly and will just brainlessly push everything or so to the max available until the device is able to boot and call it a day. I'm facing some so called "kernel issues" related to such behavior every single day and have to give the advice of using ElementalX kernel instead of mine in most cases.

I've been playing with this device for almost 4 years now, and I have measured in many ways and on multiple Android iterations some performance gains using overclocked L2. Though if I'm pushing it too far, I'll get performance drops, stuttering and heat issues leading to throttling, leading to more performance drops. Yeah, my device won't crash, but it cannot be considered stable either as the performance is lower than stock. From better GPU and I/O performance to plain CPU efficiency, as long as I'm using stable settings for my very own devices, I'll get measurable gains. So unless he can explain to me how performance is lower when - everything - is consistently faster and smoother, I'm so sorry but I won't bother reading his theories :D. That being said, anybody using my kernel is free to use stock clocks if they want to, or overclock only what they want to. I'll conclude by saying something I may add to the OP (even though this device is day by day closer to death from a community standpoint, it stays true for any device) : IF YOU HAVE NO IDEA WHAT YOU'RE DOING, EITHER DON'T DO IT (stay safe), OR DO IT VERY CONSERVATIVELY (if you're feeling adventurous).

But don't forget to enjoy your device :highfive:
[Nexus 7 (2013) Original Android Development] 228aye:
thanks for the reply, now everything is clear. I agree with You about the acceleration of the L2 OC, is visible to the naked eye that the increase in some frequencies not only provides performance gains, but also causes frame drops and overheating. But back to the BREAKFAST kernel-from our Russian friend. the developer has not put forward any theories, he confirmed them in practice. I suggest this-because the developer did the most powerful of the ever-existing kernels on the nexus 5, and achieved incredible results(I can confirm personally, cause I have this device too, but it doesn't make sense). He delves deeply into the kernel, because it has experience with the device personally, and also engaged in the development of custom kernels. moreover, we have not so many kernels for FLO, if this guy includes a lot of interesting things in your kernel, in terms of optimizations. these code changes often are not used by other developers. For example, the acceleration of the timer interrupt and the acceleration response of the touch sensor. and this is just one of the things he did. I'm not imposing, I just want to help develop Your kernel and make it better. I hope You Express your opinion and we will finish/we will continue to discuss this kernel. THX!!!:good:

P.s. I'll just leave the link to GitHub - https://github.com/alesaiko/breakfast-flo
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7485561]228aye[/MENTION]

As condescending as I may sound at times, it's a role I'm trying to play. I'm the open-minded kind in the end, even though I shouldn't for reasons that aren't very interesting (health). I'll have a look at his source and see what could be useful for our beloved N7's ;) But I really need to get some sleep first. Btw, on a more general note, my source is available to anyone wanting to push things further or change stuff etc. It's not only there to respect xda rules, but more importantly to be used by anyone feeling creative. So feel free to do anything you want with it as long as you respect the same rule by sharing your source with the world. I'm gone sleeping for real this time :D
[Nexus 7 (2013) Original Android Development] hondansx:
been on r543 for weeks and it's smooth ass! thanks!!
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Well said TK.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

Between the fact that english isn't my primary language and my lack of sleep, I'm pretty sure it was a bit clumsy :D But most of you guys know how I am after a few years "together", so I had no fear of being misunderstood. Thanks for proving me right :good:
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Elementalx - good governer, if you use a small frequency (1458,1350...)

I am glad that it is present.

Thank you for the good kernel that I does not see any alternative!

p.s. Only a pity that Root Explorer does not work on aosp :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

I still didn't flash your rom to track down the issue with root explorer though it's really strange to me and I'll definitely check this out.

Anyway, I've done more testing with bonsai benchmark lately since your related post and found something interesting. With default msm_hotplug settings, it will stutter even with stable L2 and GPU settings, while msm_mpdecision is smooth. I've been able to track down the specific setting to make it smooth to the "IO is busy" flag. Bonsai must be I/O heavy as it's smooth sailing with just this setting enabled in msm_hotplug settings. This setting makes the hotplug driver aware of the I/O load as well to online cores as if it was CPU load, while CPU load is still taken into account. Sounds more power hungry, but it may be beneficial in the end to race to idle. I'll do more extensive testing but I may end up enabling it by default for next release.

[MENTION=5863767]SHABBYLEA[/MENTION]

I was finally able to try various recoveries and I've got some results. To begin with, I've flashed [MENTION=5480152]followmsi[/MENTION]'s unofficial TWRP 3.0.3 on top of the latest multirom 3.0.2 one and it was working without issue. Flashed a few kernels and stuff without problem. I then flashed his 3.1.0 with the same results, then 3.1.0-2, still without encountering a single issue. But, after a while, just by reflashing a stable kernel that was flashed with the exact same recovery before with no issue, I was unable to get past the Google logo. Back to the recovery to get some logs : no error. But I noticed cache and data partitions were borked. Going back to an older and stable recovery didn't fix it, nor moving to official 3.1.0. So I reflashed [MENTION=5480152]followmsi[/MENTION]'s 3.1.0-2 and repaired all partitions. Still not fixed. I then wiped all partitions and reflashed. Same result. I decided to flash official 3.1.0 and do the same (repair->wipe->reflash), and it booted again. I've flashed about 30 iterations of the "WIP next release" since (as well as multiple roms) and wasn't able to reproduce the issue on the official 3.1.0. I didn't find a clue on what happened with [MENTION=5480152]followmsi[/MENTION]'s recovery but well, he now has some data with the three mentions I made in this post :D
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

io_is_busy - must have the value "1"?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

Yes, that's right.
[Nexus 7 (2013) Original Android Development] boom1982:
Thanks)

msm_hotplug I like a lot more,

Given the age of the battery)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

The simple fact that it's configurable makes it much better to me :D

But yeah, since it's running on the kernel side it's an improvement in itself. Better latency, better performance, better control.. You name it.