yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Original Android Development] followmsi:
Thanks for the mentions .. and thanks for the "data".

I do have similar experience - but just with your kernel :(

After kernel installation and SuperSu installation it was hanging at google logo.

But the partitions were not borked or corrupted for me.

I just made a long manual reboot via the hardware buttons - and your kernel was booting fine too.

Compiled all the various kernel sources in the last days.

Google MSM, Quanta, ElemenatlX and your kernel.

But this problem does only occur with your kernel .. don't know why.

I did not test official TWRP, I did not test your official Installer package .. and I did always install SuperSu afterwards.

Always the same procedure .. with all kernels . e.g. boot.img

Did not test your official package but I do have this problem with my own compiled version too.

My boot.img is just the fresh compiled kernel binary and AOSP ramdisk bumped together - no special installer.

Did this for all the other compiled kernels in the same way .. no problems so far.

Not sure why your data and cache partitions got borked ?

Using my TWRP version for all the ROM / kernel testing .. I switched over to F2FS some days ago.

(data as well - before cache only)

No issues at all .. with all the tested kernels ,also with your kernel .. which is still running in the moment.

How did you notice the partitions were borked ?

Some users have reported similar boot-logo problems installing official kernel packages from elementalx and quanta .. only if they installed SuperSU aferwards.

Once they did not install SuperSU afterwards the kernel installation went fine without hanging or other issues ..

If I would know how to fix it on my side (TWRP) I would compile a new version immediately!

Still not sure if this is TWRP related at all .. ;)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5480152]followmsi[/MENTION]

I have a few things to try as I don't like to be left with no idea of what's going on, and I'll for sure share my findings if any. I'm frustrated not being able to get any tangible error or a clear way to reproduce the issue as of now. It could be a compiler flag I'm using that's generating strange code. I think the partitions going gnarly could be a track to follow. The SuperSU "double-boot" might be off help as well to get more clues on what's going on. Thanks for pointing this out.
[Nexus 7 (2013) Original Android Development] dictionary:
Bash2Wake works well with Smash2Sleep

After bashing to wake, the device either slips and smashes to sleep, or you get mad and smash it. Both are very effective with a high probability of working the first time, everytime. Experiences may vary
[Nexus 7 (2013) Original Android Development] MBQ_:
F it.

Let's invent Wake2Bake
[Nexus 7 (2013) Original Android Development] penguin449:
Or Bake2Wake, I'm sure the headphone jack could handle a blunt :p might reboot the first time it tries thou :p
[Nexus 7 (2013) Original Android Development] jordirpz:
Or Whistle2wake

Enviado desde mi Nexus 7 usando Tapatalk

---------- Post added at 08:32 AM ---------- Previous post was at 08:12 AM ----------

@Glitch.

About battery life extender. Less voltage = + or - life extender?

Thanks sur.

Enviado desde mi Nexus 7 usando Tapatalk

---------- Post added at 08:33 AM ---------- Previous post was at 08:32 AM ----------

*sir

Enviado desde mi Nexus 7 usando Tapatalk
[Nexus 7 (2013) Original Android Development] xbs:
Power button disables the touch wake fine but if I press the power button and close the magnetic cover after some time opening the cover doesn't wake the device anymore.

Pressing power, closing the lid and open works, it's only after some time that it fails to wake the tablet.

You guys seeing this?
[Nexus 7 (2013) Original Android Development] KingpinZero:
Sorry guys if this has been asked but, is this kernel compatible with stock rooted rom. Just got the 7 and its awesome, but i want to try this kernel.

If yes, is the AOSP version recommended?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
Less voltage will extend your battery lifetime. You can't add more than stock so this addition would be useless otherwise :D

I don't have the magnetic cover so I can't reproduce that, but I did read that this problem was present for (at least) many users with stock rom and stock kernel (I mean the cover not working as intended after the tablet was asleep for some time). Does it happen only when using the power button toggle function ? It may be something [MENTION=4684315]flar2[/MENTION] didn't see in his patch. I'll have a look.

Welcome then ;)

Yes you can use this kernel with stock rom and you indeed have to use the "AOSP compatible" version.
[Nexus 7 (2013) Original Android Development] KingpinZero:
Whoa, from the man itself! Thanks man :)

So i guess before i do anything stupid, the needed file is glitch-flo-20131013-r05 right? Seems the last updated one.

Thanks again!

Inviato dal mio Nexus 7 con Tapatalk 4
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=4602121]KingpinZero[/MENTION]

You're right, this is the one :)

Enjoy !
[Nexus 7 (2013) Original Android Development] KingpinZero:
Outstanding, cant wait to tweak this little beast. Thanks man, i already know that this is going to be my loved kernel.

Keep up the good work!
[Nexus 7 (2013) Original Android Development] coolek33:
Running great with latest slimbean 4.3.1 Thanks Glitch
[Nexus 7 (2013) Original Android Development] MBQ_:
Ooh an update. Yay :D
[Nexus 7 (2013) Original Android Development] xbs:
I didn't saw it before the power button toggle options, I'll try finding out more about it.

Thank you so much for your work.
[Nexus 7 (2013) Original Android Development] dillis:
loving the frequent updates and the kernel is spot on! you have the best features and the easiest installation,favorite kernel thus far on the n7(both versions) cheers!:good::good::highfive:
[Nexus 7 (2013) Original Android Development] galaxykeks:
I have one Q. Maybe a stupid one, but I didn't find an answer...

What is this aroma or where do I find some info?

Send from the N7²
[Nexus 7 (2013) Original Android Development] coolek33:
It will appear when U start installing this kernel for example. IT will help U choose what features from this kernel U want.
[Nexus 7 (2013) Original Android Development] TunedFish:
3d Mark benches are lower on Oct 13 kernel, regardless of GPU speed.
[Nexus 7 (2013) Original Android Development] MBQ_:
So?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2840770]TunedFish[/MENTION]

Next build will come with many performance fixes.

-------

And yes, Asphalt 8 will now run as intended ;)
[Nexus 7 (2013) Original Android Development] gautampw:
You mean 30fps all the time on high graphics? And this will be without overclocking?
[Nexus 7 (2013) Original Android Development] followmsi:
Just one more input from my side ..

I did compile it using my "standard" toolchain (4.8) .. no compiling errors just a fine zimage .. similar size .. all seems to be fine.

But this kernel binary was boot-looping while Android was booting .. (at bootanimation)

Did not make dmesg ..etc.

Just made another compilation using your toolchain ..

CROSS_PREFIX="gcc-linaro-4.9-2016.02-x86_64_arm-eabi/bin/arm-eabi-"

This one had the known problem at the supersu double-boot .. later on it's just booting fine .. still use your kernel today.

No issues with F2FS .. nor partitions at all.

Hope this helps ...

Thanks a lot for your work and your sources !
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Launched bonsai benchmark thousand and one times, the problem has disappeared)

"Crime can be considered completely disclosed, dear Holmes ")
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5480152]followmsi[/MENTION]

"Double boot" is considered the normal behavior from chainfire himself so that's not the issue here but I think it might help to get some logs out of it. I'll try.

[MENTION=7890918]boom1982[/MENTION]

That's refreshing news mate :)
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Ok. Thanks for investigating, much appreciated...?
[Nexus 7 (2013) Original Android Development] followmsi:
Yes - the "double boot" is normal behavior on first boot after SuperSu.zip installation.

Thanks for all your work !
[Nexus 7 (2013) Original Android Development] followmsi:
[MENTION=3847629]Tk-Glitch[/MENTION]

Hi .. again !

Made some futher checks on my side .. :(

The following commit was reverted on my fu***** local branch .. for whatever testing.

The revert of the revert of the revert :)

https://github.com/omnirom/android_bootable_recovery/commit/a52891b6b313525925c57d840fc56fee63591130

To make it short ..

For this reason I was still using the prebuilt "/sbin/sh" binary inside TWRP and not the symlink to busybox.

This has strange impact on certain installer scripts - especially for the more complex ones.

Once the symlink to busybox is active, like it should be in 3.1.0, all the scripts are working fine again.

Had similar issues on Pixel C devices .. only certain scripts were not working.

Now all are working fine ...

Not sure if this was related to your borked partitions ?

Or any other problem you faced .. ?

To my understanding the boot-hang with your kernel is not related here ..

My old script was not complex at all .. was working all the time.

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

Jsut wanted to let you know ...

Cheers
[Nexus 7 (2013) Original Android Development] craezee:
I am getting the "json configuration error" in synapse on purenexus N rom with v544, I will try with other versions to see if it works
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5480152]followmsi[/MENTION]

Thanks man. The issue I got was with using my own scripts, and if you check them you'll see they are kinda complex compared to just boot.img extraction so this part should most definitely be fixed by your changes. I've been searching for issues on my side as well and found a few "known" problems related to compiler optimizations and specific flo tree issues regarding reboot cases and CPU initialization. I'll be stress testing all the changes but it has fixed GCC5+ power consumption issues I had I could only explain by the fact that the generated code was buggy (and that was the reason for me to go back to GCC4.9 as it didn't create such issue). Thanks to [MENTION=7890918]boom1982[/MENTION] who pointed out breakfast kernel tree as a few commits in there got my attention regarding that matter after our last talk. Hey [MENTION=7890918]boom1982[/MENTION], if it's fixed I'll have to add you as a contributor mate :highfive:

[MENTION=6494091]craezee[/MENTION]

You can try to clear synapse data and run it again. It may also need to be killed then relaunched after that. Once you get it to load once you should be good to go. I've had a few quirks with Synapse and it fixed it every time. That's funny though, I'm working on consolidating Synapse initialization for next release.
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

But it was not me

https://xdaforums.com/showpost.php?p=71518636&postcount=2781

:)

Clean aosp

https://xdaforums.com/nexus-7-2013/orig-development/rom-unlegacy-android-project-t3578301

Root Explorer works)

Problem only on slim rom. So the investigation is not necessary
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

What did I win ? Indeed that was a fail, sorry mate. See what the lack of sleep can do ! [MENTION=7485561]228aye[/MENTION] You'll most definitely get a cookie.

Did you report your issue with rootexplorer in the slimrom thread ? ;)
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

They do not listen and do not answer)

Tell me, does it work for you Sweep2sleep ?
[Nexus 7 (2013) Original Android Development] followmsi:
Have made some more investigations ..

I do testing with lazyflasher v5.1 now - no supersu "double-boot" topic at all - as we are already rooted and don't change the ramdisk again.

More or less just kernel binary replacing.

Tested latest ElementalX, Qunata V14 and your latest version ... including the changes you made a few days ago.

All with the same lazyflasher v5.1 config, just a new zImage.

I did boot into TWRP and installed first kernel, booted into system to check, booted back into TWRP and flashed next kernel binary.

Always back to system to check the system works still as expected.

Again it's only your kernel which is hanging at google logo .. :(

This time I waited much longer on the google logo, then I made manual reboot via hardware keys.

But it did not boot into system this time and it was hanging on google logo again.

Guess what happened now ..

Booted into TWRP and the /cache partition was fully borked and strange errors from /data partition too.

Had to reformat both partitions wiht F2FS.

The fist time my partitions got borked at all, never had this before .. also not with your kernel.

After complete restore I did test with Elemental X and Qunata V14 only .. same procedure .. multiple times.

No issues at all ..

Made a new ROM today (enabling Night Mode) .. for this reason I did some more flashing.

No issues .. changed both kernels via lazyflasher .. did wipe cache .. rebooted into system.

Repeated the steps with both kernels .. no issues at all.

Sorry for my "bad" news .. still want to test and use your kernel too .. :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5480152]followmsi[/MENTION]

The patches I was talking about earlier aren't yet pushed. I'll also add a few changes in the default configuration as flashing the zImage with a clean ramdisk (so not using my flashing scripts) will make mpdecision interfere with the in-kernel msm_hotplug driver and can generate very strange issues like power consumption skyrocketing to random reboots and who knows what else. I'll push the changes soon as it's been a few days testing without encountering an issue. I'll check for [MENTION=7890918]boom1982[/MENTION]'s S2S problem as well.

Update : [MENTION=7890918]boom1982[/MENTION] S2S definitely working here on r544.

-------------------------------------------------------------

r561 released ! If you want to get init.d to work, you'll have to reflash your rom before applying this update to refresh ramdisk.

27/03/2017 - r561 :

- Synced with latest LineageOS 14.1;

- Backported high-resolution support for sched-clock;

- Fixed CPU detection on subsystem_restart;

- Make rpm clocks sleeping clocks;

- Pushed updates from franco kernel regarding GPU, CPU freq and video;

- Added Zen I/O scheduler (pretty nice sched to say the least);

- Enabled I/O is busy flag for msm_hotplug driver by default (boosts CPU freq during heavy I/O load -> big smoothness gains in many apps and games);

- Added compiler fixes and optimizations from alesaiko (breakfast kernel);

- Moved to latest Linaro GCC 6.3.1 compiler (as the changes above fixed high power consumption issues on GCC5+);

- Consolidated Synapse support. The path of the generated config file is now /data/synapse instead of ramdisk to keep it safe during rom upgrades and reboots. If you get a "No UCI support" message on first Synapse launch, just kill the app and relaunch it. It'll not happen again after that unless you wipe data or I'm forcing a regen in a future update.

- Fixed init.d injection not using the correct path for busybox since a few releases and updated the execution process to N standards;

- Changed the way we get rid of mpdecision to prevent the service from starting in the init process instead of renaming the binary. This enables the possibility to enable or disable mpdecision on the fly after boot, even if using msm_hotplug as default hotplug driver.

- Fixed missing options in Synapse;

- Added various smaller performance patches and optimizations as well as a few more variables to play with for nerdz and lolcats (see github commits);

- Tweaked debugging config;
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

I thought that the next number would be 545))

Thanks for the update!

What program can you advise to configure the kernel?

I'm using EX manager

ps You were right, I got excited, when said that msm hot plug on the battery side)))
[Nexus 7 (2013) Original Android Development] followmsi:
Have tested your offical PURE version -> no problems to install and no problems on boot.

Compiled a new binary using 6.3.1 linaro -> there are no problems on boot anymore !

Thanks a lot for all your work !
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=5480152]followmsi[/MENTION]

Friend, your quotes are long as life :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

The release number is linked to the number of testing phases. The bigger the changes, the more chances it'll need more test-builds before considered stable and/or polished enough for public release. 17 dev-builds between r544 and r561 means large changes and many days of testing, debugging and fine-tuning (and wipes and ROM flashing :( )

The best "app" is definitely Synapse as my custom support will give you more kernel-specific options than anything else.

[MENTION=5480152]followmsi[/MENTION]

Thanks to you as well ! Your findings and thoughts have been helping much more than you'd think. You did contribute to this kernel's enhancement. I'll gladly add you to the contributors, it's well deserved.
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Please give me a link. In the play market there are several)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

It is the one from Andrei .F. A black/dark grey circle with sliders on it. Can't get the link right now sorry.
[Nexus 7 (2013) Original Android Development] boom1982:
Ha, I can not even run it)

Probably not my Option :)
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

What's the issue ? I mean, what's happening when you run it ?
[Nexus 7 (2013) Original Android Development] boom1982:
The application requests the root, I agree and it hangs
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

If you force kill it after that, wait 5 seconds and relaunch it, will it still hang ?
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Thanks again for the update Tk. Most welcome as always...?
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=5863767]SHABBYLEA[/MENTION]

I hope you'll like it ! Till next one :D
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Does not help, tried several times ...

Unfortunately I found problems more serious - Watched the video in chrome, began to make a zoom and got a strong problem with the touchscreen. The same problem was on the kernel "breakfast"

I think this is not an accident. Let's wait if there are similar problems for others.

While remaining on r544

ps The developer of Breckfest said, that the case may be in the timed timing driver of the touchscreen. Until the end of the week he will look at this problem.
[Nexus 7 (2013) Original Android Development] DorianX:
S2W/S2S isn't working for me on latest (r561) was working on r544, first time I tried pure because I wanted my previous config, then tried full just make sure, same problem.

What kind of log do you need?

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=2185114]DorianX[/MENTION] [MENTION=7890918]boom1982[/MENTION]

Looks like another panel revision issue or something. I'm completely unable to generate any kind of issue related to zooming or S2S/S2W/DT2W on my two devices. My touchscreen is flawless on both r544 and r561, and S2S/S2W/DT2W are working just fine. Indeed it may have to do with timing but that's pretty sad it doesn't work for some of you as the responsiveness is just perfect on r561, much better than r544 to me. Since I can't test for the fix on my devices, I'll push a test build later today for you to try.

[MENTION=2185114]DorianX[/MENTION] I'm not sure any log will be of help here, but thanks.
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

I, too, was all excellent)

The problem can find itself, after viewing the video (30 minutes,chrome) in a landscape orientation :)
[Nexus 7 (2013) Original Android Development] DorianX:
Ok thank you so much

Enviado desde mi Nexus 6P mediante Tapatalk
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

As a user, I'm mostly using this tab for web browsing and watching online videos. I've been using these changes for about a week without a single issue, and used my sleeping troubles to do stress testing for 6-8 hours every day. Both my devices (very first N7 2013 batch) are clearly not encountering your problem. I'll push the test build in about 2 hours if everything goes according to plan.

Edit : [MENTION=2185114]DorianX[/MENTION] & [MENTION=7890918]boom1982[/MENTION]

Test builds are available for you to try. I'll be waiting for your results. Thanks !

Pure build

Full build
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

For the whole day of use, not a single problem.

Improved behavior in the bonsai bainchmark (on the slim rom), In comparison with r561

What changes have you made?)

At the moment I'm happy like an elephant :)
[Nexus 7 (2013) Original Android Development] DorianX:
Just reporting here S2W/S2S doesn't work at all, DT2W it's working, zooming is working in fact touchscreen feels pretty responsive.

By the way my panel is a replacement because I broke the original one, so no OEM panel here but on previous version of your kernel S2S/S2W was working

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
Yeah. Can confirm that TK. Tried reinstalling with various options but no joy.

Cheers.
[Nexus 7 (2013) Original Android Development] Tk-Glitch:
[MENTION=7890918]boom1982[/MENTION]

The only changes are panel wakeup/sleep related.

[MENTION=2185114]DorianX[/MENTION]

Okay. As strange as it may look, thanks to your last comment I was able to find the issue. I'll push an update very soon.

It'll fix the wake gestures timeout function as well (this one wasn't reported yet was broken due to the same issue).

Edit : Update up.
[Nexus 7 (2013) Original Android Development] SHABBYLEA:
That did the trick.

Many thanks TK...?
[Nexus 7 (2013) Original Android Development] DorianX:
Same here, everything is working know. Thank you so much! [MENTION=3847629]Tk-Glitch[/MENTION]

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 (2013) Original Android Development] boom1982:
[MENTION=3847629]Tk-Glitch[/MENTION]

Probably I felt the difference, because I changed rom and planner))

Is there any difference between r562 and r563?

Does it work for you "battery life" (when charging goes up to 93% or 83%)?