yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] HTCDreamOn:
[KERNEL][L] linux-tegra-nv-3.1-grouper [Beta 0]

Thank you everyone for your support, especially those who donated to [MENTION=2633638]Ziyan[/MENTION] enabling him to buy a N7 recently.

[MENTION=2633638]Ziyan[/MENTION] has begun updating nv-3.1 because we did it pretty messily before, and he's made amazing progress whilst doing a far cleaner job of it. I've uploaded his latest progress here, I guess we could call this Beta now. Please send useful things like logcats, last_kmsgs and dmsgs, and no, F2FS requests ARE NOT useful. Please see here for sources.

I'm not sure where [MENTION=2633638]Ziyan[/MENTION] has posted in this thread but please find a post of his and thank him as more than being a tremendous help in this project he's an absolute necessity and incredibly helpful. Btw no F2FS requests.

N.B. No F2FS requests.

N.B.2. No multiROM requests

EDIT: This will NOT work with CM12
[Nexus 7 Original Development] manulemaboul:
Working great, fast and smooth without any issues so far :good:
[Nexus 7 Original Development] käsebr0t:
Great News! ? Out of curiosity, I tried it on CM12 and it booted up fine and ran very smoothly. The only problem was: The home and recents buttons were gone. I'm back on 37.1 until I have thre time to flash another rom.
[Nexus 7 Original Development] decky006:
Tried it with today's xenonHD release. I also get the missing home and recent buttons.
[Nexus 7 Original Development] HTCDreamOn:
I didn't know for certain, it's just we've been chatting to the CM12 grouper/nakasi device maintainers a bit and they're changing the CM12 kernel for grouper quite a bit so warned it might break things quite badly if you use this:

"Tell users it doesn't work with cm12 if u did not Cherry picked commits for f2fs from cm kernel, otherwise they may corrupt their userdata partitions"

You've been warned.

awesome :good:

I assume XenonHD uses CM12 device tree then, see above for warning.
[Nexus 7 Original Development] n1kolaa:
cm now have diftent ramdisk, need just to change ramdisk :)
[Nexus 7 Original Development] nycelitemaster:
Thanks works great on stock 5.0.2.

Sent from my Nexus 4
[Nexus 7 Original Development] Dark_Balor:
I confirm it works great with Dirty Unicorn 9.1

I would enjoy having zram on the kernel.
[Nexus 7 Original Development] käsebr0t:
No problems on FreakSlimLP. Keep up your amazing work. This project shows what XDA is all about [emoji106]
[Nexus 7 Original Development] YellowMango:
working well with PA alpha 1
[Nexus 7 Original Development] USBhost:
I completely agree! :good:
[Nexus 7 Original Development] HTCDreamOn:
[KERNEL][L] linux-tegra-nv-3.1-grouper [Beta]

Beta 01. Got some problems atm, lots of spam from dmesg (tegra_set_latency_allowance: invalid Id=4) so help finding the source of this + solution would be very helpful. [MENTION=2633638]Ziyan[/MENTION] reckons it's from drivers/video/tegra/dc/bandwidth.c so far. Pretty close to finishing cherry-picks though, once again enormous thanks to [MENTION=4307430]n1kolaa[/MENTION] and of course [MENTION=2633638]Ziyan[/MENTION] is rapidly and smoothly cherry-picking thousands of commits for us so :good: :good: :good: to him!
[Nexus 7 Original Development] linuxxxx:
Remember this does not work on cm devices using f2fs. If ure on ext4 and u want to try out this kernel u'll need to flash just the zImage and keep the original ramdisk from cm. The next build should be cm compatible, and then once this is ready it will be used for official cm builds ;)

Sent from my A0001
[Nexus 7 Original Development] joaopaulo_:
The tablet does not charge when it is on. Only when turned off.

And tested in beta0 is normal, but it was detected in beta01.

I tried to send the log today.
[Nexus 7 Original Development] manulemaboul:
It charges actually, Android is not aware of it so no charging icon nor "in charge" status, but it charges, the battery % is rising while using it.
[Nexus 7 Original Development] n1kolaa:
fixed ramdisk for CM. this is only for cm users.

https://www.dropbox.com/s/7kz5tfr4c57mn2n/nv-cm.img?dl=0

i can repack it for others custom rom on reqvest. :)
[Nexus 7 Original Development] aoh1996:
Will it work on f2fs CM (data & cache) ?
[Nexus 7 Original Development] joaopaulo_:
No my friend. No f2fs suport.
[Nexus 7 Original Development] ccav2000:
Upgraded to Android 5.1, beta 00 of this kernel results in bootloop after the "optimizing apps" message. I had to flash boot.img that came with the factory image to successfully boot, so beware.
[Nexus 7 Original Development] namerke:
I hope the guys will patch up the kernel with the new sources shortly. They are doing a pretty good job so far :good:, hope we will actually see this project coming trough til 3.4 . Fingers crossed.
[Nexus 7 Original Development] Ziyan:
Thanks for the reports guys, I'll look into it on the weekend (I'm pretty busy during weekdays).

That dmesg spam about latency allowance might reduce the performance a bit, so you may see even better performance after I get it fixed, but I just didn't have the time last weekend for it :/

Apart from that, nv-3.1 is almost done. Currently, it's only missing the new usb udc platform driver and some other very minor commits. Once I get those merged (and the rest of the issues fixed), I'll start working on 3.4 immediately ;)
[Nexus 7 Original Development] Sultanxda:
Not sure if I missed something since I haven't looked at this forum in years, but I tried compiling the kernel from your GitHub and it doesn't boot out of the box :/ Had to make some critical changes to get it booting. Is it booting for you as-is?

EDIT: Your recent pinmux changes created a race condition at init time, which is why the kernel didn't boot on my device (my hardware sucks, apparently). I've sent you a pull request with a fix: https://github.com/Ziyann/android_kernel_asus_grouper/pull/2
[Nexus 7 Original Development] Ziyan:
Thanks, while I never experienced that, I can imagine it happening because the recent pinmux changes :) merged your pull request.
[Nexus 7 Original Development] n1kolaa:
With new changes from aosp. For 5.1 anroid only.

thanks to [MENTION=5451053]linuxxxx[/MENTION] for compiling zimage

https://www.dropbox.com/s/tfa4btagh75ee28/aosp5-1.img?dl=0

happy flashing :)
[Nexus 7 Original Development] manulemaboul:
Battery drain was driving me crazy on stock 5.1, thanks :).

It even detect it's charging now :good:
[Nexus 7 Original Development] linuxxxx:
Nice, i made no changes from last public release. Maybe it was a ramdisk prob
[Nexus 7 Original Development] HTCDreamOn:
Quick update, I realised being as [MENTION=2633638]Ziyan[/MENTION] is doing the main work on this now I ought to link his source in the thread so the source links in the first post now link here to avoid confusion + so you can see all the latest changes. Many thanks for everyone's help and support as usual!

EDIT: some things appear to be happening... ;)
[Nexus 7 Original Development] n1kolaa:
i didnt done changes to ramdisk, just pasted zimange inside boot.img :)

last compiled kernel for 5.1 link-dropbox
[Nexus 7 Original Development] amynjimmy:
Has anyone been using this kernel...any + or -
[Nexus 7 Original Development] HTCDreamOn:
Please refrain from asking such things in a development thread, there is a Q&A thread alongside this one. As you should be aware from reading the OP no promises can be made as to daily use as this is very much a WIP and purely development project, with only the end project and not the preceding test builds being presented as "usable" in any way.
[Nexus 7 Original Development] sunnyxiongster:
can i use it with paranoid rom?
[Nexus 7 Original Development] namerke:
As far as I know there is no official paranoid release based on 5.1 so therefore i guess you can not use this kernel on previous releases.

Also, for the theming engine they are using the kernel have to have some additional commits.

Without those commits you will face bootloop if you apply a theme.

But I might be wrong, maybe someone will confirm my opinion.
[Nexus 7 Original Development] jgramkow:
Is there a flashable zip of this for 5.1?
[Nexus 7 Original Development] manulemaboul:
You can use flashify, or rename it boot.img and paste it in an existing kernel zip. And please use the Q/A thread for, you know, its purpose: questions :)
[Nexus 7 Original Development] HTCDreamOn:
Ah yeah if you've had a look at the grouper-nvidia github org you may have seen the anykernel repo, notn sure if that's working yet I'll have a look tonight but if not I'll post a regular agnostic it just means you won't be able to use on cm12 as usual of course. As manulemaboul suggests you can flash the boot.img although you can't do that yet as we haven't posted one yet ;) so just wait around a bit cos I want to let you guys test out on 5.1, its much better than 5.0 so should make analysing the kernel less of a pain.
[Nexus 7 Original Development] jgramkow:
I used flashifly. I find the battery life to be amazing! It has also been lag free! Thanks to all! I am looking forward to the next one!
[Nexus 7 Original Development] manulemaboul:
Back to not detecting the charge on the latest one tho, it's making funny stats.
[Nexus 7 Original Development] USBhost:
That's vary good battery

Lol
[Nexus 7 Original Development] HTCDreamOn:
Sorry guys forgot I promised to upload and haven't had a chance, here's [MENTION=2633638]Ziyan[/MENTION]'s latest sources compiled. Android 5.1 ONLY.
[Nexus 7 Original Development] adstraylight:
Running great so far on the latest build of Frank:good:
[Nexus 7 Original Development] Libertunas:
On FULLF2FS partition, the 5.1 kernel stuck on Google Logo.

Can we easy fix it?
[Nexus 7 Original Development] joaopaulo_:
this is not f2fs compatible.
[Nexus 7 Original Development] Harpratap:
Flashed this with stock 5.1

Battery life and smoothness is amazing!

But there's an issue, although minor, I see minor visual artifacts once in a while. A part of screen turns completely white for a tenth of a second and turns normal again. Never faced in on stock kernel or Franco's Kernel.
[Nexus 7 Original Development] HTCDreamOn:
The guys were talking about this a few weeks ago, can't remember the exact problem now. [MENTION=4800121]Sultanxda[/MENTION] [MENTION=2633638]Ziyan[/MENTION] any input?
[Nexus 7 Original Development] manulemaboul:
If it can help, they seem to be gone since I've switched to the chroma grouper ROM maintained by sykopompos wich use 5.1 r3.
[Nexus 7 Original Development] 1haumann1:
Can you link me please? [emoji16]

keep calm and have a Nexus :D
[Nexus 7 Original Development] manulemaboul:
https://www.androidfilehost.com/?w=files&flid=28739
[Nexus 7 Original Development] snowfire88:
Thank you!

Was initially running Franco kernel r82 on stock, but faced insane lags and stutters after a week even after switching to F2FS. Stumbled onto this kernel while poking around XDA. Chroma Rom plus this kernel have made my Nexus 7 normal again! Accepted it doesn't fly like it used to, nor can I multi-task much, but I can at least browse articles on chrome, use reddit or read an epub file without having to wait for loading screens. Thank you! :) :good:
[Nexus 7 Original Development] Sultanxda:
These fix 99% of the visual artifacts:

https://github.com/sultanxda/androi...mmit/e8d6f27fcdc157d204627d06465116dbb89de8d5

https://github.com/sultanxda/androi...mmit/8dd549b80d060d96f2299e6597284cea8a273e56
[Nexus 7 Original Development] nruri:
I have the same setup and can't thank you guys enough! this kernel made my tablet usable again! :)
[Nexus 7 Original Development] joaopaulo_:
Please, someone could compile this kernel with cm12.1 ramdisk? I really like of the performance of this kernel, but I wanna try this with cm12.1.
[Nexus 7 Original Development] qualitymove13:
I cant for the life of me find that flashable zip. Is that not that type of party? TIA!
[Nexus 7 Original Development] Targaeryan:
http://xdaforums.com/showthread.php?p=59760431
[Nexus 7 Original Development] anzi2001:
Still any work on this kernel or nah?
[Nexus 7 Original Development] Ziyan:
I had to take a break from this project, but I'm back ;)
[Nexus 7 Original Development] anzi2001:
Yees i cant wait to finish this project so we can get 3.4 kernel :D

Also how did you not make it able to port 3.4 kernel to our nexus 7 but a guy did it for huawei ideos x5 and is working on a 3.10 kernel atm ?
[Nexus 7 Original Development] Ziyan:
That's a completely different SoC. They probably have better support for 3.4 - remember, there aren't much Tegra 3 devices running 3.4 :rolleyes: though that's probably because the lack of dev support, because it should be entirely possible to make it working. I wasn't war away from booting it back in time on another Tegra 3 device, but I had to abandon that project (couldn't get hands any more on that device) :crying:
[Nexus 7 Original Development] anzi2001:
I doubt they have better support for 3.4 kernels cause the phone is made for 2.3 gingerbread with kernel 2.x.35 (i dont remember the version where is the x) and it now runs lollipop with 3.4 kernel and the only guy working on it is blefish...he is the only one left so i dont think they have better support but since you are the developer here and i cant even cherry-pick a commit (gives me an error for no bloody reason) i will say you are right :D
[Nexus 7 Original Development] Ziyan:
That phone uses an msm7x30 SoC, which is widely supported - several 3.4 kernels are available for it, and a lot of phones use that SoC. On the other hand, only a few devices use Tegra 3 SoC, which is why our job is much harder :) however, before I arrange all my resources to 3.4, I'm working on fixing up the nv-3.1 kernel. Remember, this is also a huge step forward - more than 1000 new Nvidia commits! Not only it feels smoother, benchmarks also prove that it's more efficient than the old-ass Google kernel ;)
[Nexus 7 Original Development] anzi2001:
And why does google not upgrade the kernel to newer versions?
[Nexus 7 Original Development] USBhost:
a 3year old tab is not high priority

also google doesn't really update kernels of 3.1

only 3.4 / 3.10
[Nexus 7 Original Development] anzi2001:
So how do you then port a kernel that no tegra 3 device has? Sorry for the noobish questions im fairly new to this :)
[Nexus 7 Original Development] USBhost:
its hard
[Nexus 7 Original Development] anzi2001:
Well if you can please explain it fast and simple...if you cant ill just have to deal with it :D
[Nexus 7 Original Development] HTCDreamOn:
Yeah Galaxy S Plus has 3.4 at least. And yes the advantages we've got from the nv-3.1 are so significant that even if a working 3.4 is never achieve we should be happy with the progress made with 3.1.10.
[Nexus 7 Original Development] käsebr0t:
Man, the good old S Plus. Unfortanately mine stopped working, but I can confirm that kernel 3.4 did a lot for this device. It even got Lollipop 5.1.

Sorry for little OT, I was just feeling some nostalgia [emoji28]

Also, it's good to see that this project is still alive. Keep up your amazing work [emoji106]
[Nexus 7 Original Development] anzi2001:
htcdreamon just to inform you your source is giving me troubles...it gives me an error when compiling without modifications...no addons... it gives me this:

scripts/Makefile.build:311: recipe for target 'drivers/gpio/gpio-janz-ttl.o' failed

make[2]: *** [drivers/gpio/gpio-janz-ttl.o] Error 1

scripts/Makefile.build:441: recipe for target 'drivers/gpio' failed

make[1]: *** [drivers/gpio] Error 2

Makefile:945: recipe for target 'drivers' failed

make: *** [drivers] Error 2

make: *** Waiting for unfinished jobs....

can you fix it? i will be very grateful cause i tried a lot of things :D
[Nexus 7 Original Development] HTCDreamOn:
Apologies for the late reply, everything is fine for me so I suggest a 'make clean && make mrproper' and try again after updating sources. You are using the correct sources right? Should be on the android-tegra3-grouper-3.1-lollipop-release_tegra-l4t-r16-16.5 branch. Also I suggest you sync Ziyann's as mine is messy and has lots of experimentation piled up. So git remote add Ziyann https://github.com/Ziyann/android_kernel_asus_grouper.git then git checkout -t Ziyann/android-tegra3-grouper-3.1-lollipop-release_tegra-l4t-r16-16.5 then build as per.

While I'm here may as well upload this, of course mostly Ziyann's and sultan's work applying commits currently so massive thanks to them. This may be the last upload.... that's all I'll say ;) .
[Nexus 7 Original Development] anzi2001:
Nevermind i compiles...i was stupid...so are you working on 3.4 now? Cause i saw the thread and it looks amazing! :D
[Nexus 7 Original Development] manulemaboul:
the 4 cores are always on, is it the normal behavior ?

Also, my keyboard registered ghost touches all the time, went back to M-kernel a77 because of that.
[Nexus 7 Original Development] sakindia123:
Here is overclocked version of this kernel if anybody wants to flash...compiled with gcc 4.9.3 :good:

fastboot flash boot intelli.img
[Nexus 7 Original Development] manulemaboul:
Your build doesn't have the 4 cores always on nor the ghost touches on the keyboard, I'm gonna use it a few days to see how it behaves :).

So far, it feels pretty fast and smooth with max freq 1300 :).
[Nexus 7 Original Development] HTCDreamOn:
Guys, 3.4: http://xdaforums.com/nexus-7/orig-development/wip-linux-tegra-nv-3-4-bringup-t3128195
[Nexus 7 Original Development] dareino:
thxs for everything!
[Nexus 7 Original Development] käsebr0t:
When I install the latest version on Optipop, it gives me infinite System-UI crashes right after it booted :( Does anyone know why?
[Nexus 7 Original Development] käsebr0t:
So, I figured out, that it was just the ramdisk being incomaptible with Optipop. So just in case, anyone wants to run this kernel with Optipop (which is an awesome combination imho), I attached to .img-files. The first one is the standard kernel, which HTCDreamOn posted a few days ago, and the second one is the overclocked version by sakindia123. Both are repacked with Optipop's ramdisk, so use them only with this rom!

Greetings, käsebr0t
[Nexus 7 Original Development] Ophidian_DarkCore:
f2fs? otherwise i have to wipe
[Nexus 7 Original Development] käsebr0t:
Honestly, I don't know. But I don't think that HTCDreamOn and Ziyan built the kernel with f2fs-support, because they wanted to make a clean and stable base first, and I just repacked the image, so I did not add any features.
[Nexus 7 Original Development] closeRanger:
so you dropped lollipop ?

No linux 3.4 for LP ?
[Nexus 7 Original Development] käsebr0t:
Ok, so I noticed two things:

1. Sometimes I need to press the Power-Button multiple times to wake up device (I think this has been mentioned before).

2. Sometimes my Nexus 7 rebooted just a few minutes after I set it to Standby mode. It didn't happen often and I couldn't reproduce it, but it seemed to happen rather randomly.

Other than that it runs pretty smooth for a stock kernel.

Keep up the awesome job. This project can really do a lot for our good old Nexus 7 [emoji106]
[Nexus 7 Original Development] Ziyan:
If anyone has a spare (cracked or anything) Nexus 7, I'm willing to help with this project. I've updated the Galaxy Nexus kernel (exactly the same situation, I did 1000+ commits), and the Acer tegra 3 device's kernel too, which was a smaller job though, but hey...
[Nexus 7 Original Development] HTCDreamOn:
Thanks everyone for testing, bit of a status update: I've been very busy, nothing's changes since alpha 2, but if anyone could send some logcats and last kmsgs my way then I might be able to get to the bottom of these reboot problems etc. which seem pretty reproducible (I was getting them too). In the meantime I might push (lol) ahead with the commits and/or wait til Google updates their tegra kernel as there've definitely been some changes since KK - L.

EDIT: Alpha 3 building now.
[Nexus 7 Original Development] HTCDreamOn:
RE: [KERNEL] linux-tegra-nv-3.1-grouper [Alpha 0.3]

Alpha 0.3 Uploaded check Github for changes as usual.

I will not attempt to fix any problems myself as they may/may not be fixed in Nvidia's source so I don't want to screw things up until ALL the commits have been cherry-picked. For this reason your testing is still absolutely invaluable as I need to know if anything has broken/fixed between releases so I have a complete and correct to-do list by the time the cherry-picking is done. So a massive thanks to everyone testing + reporting once again.

You may have also noticed the "Donate to me" button under my avatar. I'm saving for a bigger hard drive & better specs so I can compile faster, as at the moment, although I can cherry-pick fast, the time it takes to compile, fix, compile, repeat, takes a long time. There are also many other Android projects I have stocked up to do (ROMs, apps, the usual) which I hope to share with you all when I can. Of course any help in any form, be it testing or simply a pat on the back, is still all I need to keep going and it is as always greatly appreciated.
[Nexus 7 Original Development] Monfro:
Thank you again for your precious work!

I agree that is better to wait to have all the commits cherry picked before starting fixing things.
[Nexus 7 Original Development] n1kolaa:
There are only net changes over Kk-l :)
[Nexus 7 Original Development] Monfro:
Tried to test Alpha 0.3 and i always had bootloops.

At first i repacked ramdisk to run it with Android L AOSP: bootloop

Then i restored a nandbackup of stock 4.4.4 (ready to install L OTA): bootloop

I then installed mkernel, then Alpha 0.3 over it: bootloop

Sorry i can't post a log atm
[Nexus 7 Original Development] HTCDreamOn:
Thank you for testing and replying so quickly! Fear not, this is in fact good news.... now we may have a chance to discover what was causing 3.4 not to boot all along. I've reverted the grouper specific commit and also another commit which might cause problems... if this doesn't fix it I may have to revert all the commits I picked yesterday and repick them one by one and compile after each :eek: I hope I won't need to do that though!

So yeah please try out this Alpha 04 and see what happens, logcat would also be helpful this time but I understand if you're unable too :good: thanks alot
[Nexus 7 Original Development] Monfro:
Tested Alpha 0.4: unfortunately only bootloop again
[Nexus 7 Original Development] fKm:
I flashed the Alpha 0.4 in TWRP, it booted but the kernel wasn't flashed. I still have franco. Tried this two times but still no luck.
[Nexus 7 Original Development] gptwarrior:
same for me when flashing in lollipop still shows as original kernel not alpha 3
[Nexus 7 Original Development] frantisek.nesveda:
That's a problem with agnostic-kernel, I'm working on Lollipop (and any AOSP/no-busybox ROM compatibility) now.

For now you can try installing busybox and then trying to install this kernel. Or, if you don't use F2FS, just unpack the kernel

zip and flash the boot.img with fastboot.

But then you'll still be stuck in a bootloop until you change the ramdisk to a lollipop one. And then it still won't work because alpha03 and alpha04 don't boot. So you'll need to do this with alpha02.
[Nexus 7 Original Development] HTCDreamOn:
RE: [KERNEL] linux-tegra-nv-3.1-grouper [Alpha 0.3]

Updated to Alpha 0.5. All I've done is reverted to Alpha 0.2, merged the new lollipop branch, and packed into the updated agnostic template. This is working fine for me on Lollipop ext4, f2fs testers would be welcome. It's gonna take me a while to pick these next batch of commits because as you know they broke something so I'm gonna have to go super slow. In the meantime, enjoy :)
[Nexus 7 Original Development] 19dragon98:
So for try if work f2fs we need to change partition to f2fs with TWRP? [emoji2]
[Nexus 7 Original Development] käsebr0t:
Exactly. But you will lose all your data.
[Nexus 7 Original Development] homerograco:
This is awesome! I have to test it!
[Nexus 7 Original Development] jstntp:
Works with /system ext4 and /data, /cache f2fs. So it should work if all partitions were f2fs.