yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] sheffzor:
Yes but that is a last_kmsg of recovery kernel.

Sounds like you rebooted from recovery to... recovery again.

The last_kmsg is the kernel log from the last boot, so if you have done everything as I said, it should show the kernel 3.4 kmsg, re-check the steps, they must be done explicitly in the way I posted.

Sent from my OPO
[Nexus 7 Original Development] dareino:
Not a huge deal but I do notice that my tablet does not respond when opening or closing the magnetic case cover ......

d
[Nexus 7 Original Development] wynstep:
Also in my case the magnetic cover does not respond
[Nexus 7 Original Development] mn.code:
I am experiencing some very strange things ever since I installed this ROM and tried to use OTG on it. Now my device is charging ONLY in this ROM, it won't charge even on stock :laugh: You have the animated icon and everything but battery stays at the same percentage (and on this ROM it's charging fine). I know that my device is not suffering from famous bad connector issue. Also, I lost OTG on every ROM, the external device is not being powered by Nexus and MTP connection works on every ROM. Either charging circuit is damaged somehow (but why is it charging in this ROM?) or it's locked out. [MENTION=2633638]Ziyan[/MENTION] [MENTION=4619263]sheffzor[/MENTION] Do you have any ideas what might be going on? I am ataching dmesg from this ROM when trying to use OTG.

EDIT: In other ROMs, bq27541 module is not "getting" current from charger, it's on 0 while charging:

bq27541_get_psp current = 0 mA

And when on USB connected to PC it's charging with 10-30mA :laugh:
[Nexus 7 Original Development] Ziyan:
Sounds like the newer drivers in 3.4 set the registers differently, and the older drivers in 3.1 didn't reset them - same thing happened on tuna in the past. The easiest solution would be to disconnect the battery for some minutes, so the registers get reset. We might release a new build later this weekend - DRM is now working, and we found out what's causing the sound and rotation lock issues, to expect those to be fixed as well. We'll try to fix OTG as well in that build :)
[Nexus 7 Original Development] mn.code:
Yup, that did the trick. Thanks a lot! About tuna, I miss that device, I think I am gonna get one again :)

Can you check if network geolocation works for you? It's the only thing I actually need to use this as daily driver,. I develop Android apps so I use a lot of Maps API...
[Nexus 7 Original Development] chall32:
Now that's weird. I had the exact same thing. 0mA charging according to Ampere

However, I just assumed that I had a loose battery cable and reseated it (remove back cover, disconnect battery and reconnect battery). Am now charging OK again (varies betweeen 300mA and 1120mA - which is normal for my grouper).
[Nexus 7 Original Development] Ziyan:
Did that happen for you after switching back to 3.1 from 3.4 as well?
[Nexus 7 Original Development] chall32:
Yes.

Tried 3.4; all good at first & then had permissions "fun and games" with Open GApps, so restored the CM13 nandroid backup I took just before wiping and installing the 3.4 ROM from this thread.

3.1 > 3.4 > 3.1 > charging problems > fixed with battery cable re-seat > charging OK now.
[Nexus 7 Original Development] :
Just flashed the 6.0.1 rom, and it's working more or less flawlessly for my purposes. The only thing I've noticed so far is that the automatic screen lock (got one of those magnet covers) doesn't work, and I get an occasional 'play services has stopped' message. Thanks a lot, this has given my tablet new life!
[Nexus 7 Original Development] The~Skater~187:
You guys rock!!#!#!#
[Nexus 7 Original Development] biondi53:
I followed the steps correctly .... I forgot to mention that in some cases after flash the rom and restarting, TWRP warns "not OS installed"...

Later I will try again, there is some keyword inside the log to see if it works?
[Nexus 7 Original Development] sheffzor:
Flash the latest twrp release and then try again, no OS installed means /system partition isn't correctly flashed.

Sent from my OPO
[Nexus 7 Original Development] biondi53:
I'm on TWRP 3.0.0, I tried with system mount&unmount. Now I will try again before flash other rom to solve the battery charge issue...

EDIT: This was my last attempt, I surrender.
[Nexus 7 Original Development] KawaiiAurora:
Did TWRP install the ROM correctly? It sounds like it didn't...
[Nexus 7 Original Development] aquavalanche:
uh, you typed "lat_kmsg" instead of "last_kmsg" there
[Nexus 7 Original Development] wynstep:
Is there a fix for the auto screen lock issue (with magnetic cover)?
[Nexus 7 Original Development] everesee:
Wonderful! I'm looking forward to this update :)
[Nexus 7 Original Development] Bert98:
Has development stopped on this?:(
[Nexus 7 Original Development] Ziyan:
No man, it's just that I have more projects going on at the same time, and I'm also busy with school...

I don't get why so many people think it stopped. Stop worrying, it won't stop, but we might take some breaks while working on other projects. I have to maintain two other devices as well, and (not that it matters really, because part of me does this for fun) there are much more users waiting for development on those other devices. For some reason, it seems like very few people is interested in 3.4 on grouper, and I don't really know why... all the work until now was done by me and [MENTION=4619263]sheffzor[/MENTION], without any help or interest from other developers :(
[Nexus 7 Original Development] Sage:
i am patient - and grateful! been watching this thread for months. Such amazing work.
[Nexus 7 Original Development] chall32:
+1 !!!

Cant wait to try 3.4 kernel with other roms (CM13 etc etc etc)
[Nexus 7 Original Development] NeoPreacher:
right here in original dev area appeared a DU 10 with 3.4 kernel. flashed it and checked with kernel adiutor, it really shows 3.4.67 :confused:
[Nexus 7 Original Development] Ziyan:
That's sad. It's not my problem if people switching back from that rom to a 3.1 kernel based one won't be able to charge their devices and won't know what to do though... and once again, we didn't get any credits at all.
[Nexus 7 Original Development] NeoPreacher:
yeah you told more than once that it is in a quite experimental state and also they doesn't give credit for that i recognized too, which was the reason to get you informed. and to get rid of if this ones got your blessing. but it doesn't. so it got wiped as a matter of respect.
[Nexus 7 Original Development] everesee:
After this kernel, my device isn't charging anymore. I see charging icon, but I can't boot my device (Maybe Super-slow charging?) Is there any solution for this?

I don't recommend anyone to use this kernel, you can face with same problem.
[Nexus 7 Original Development] biondi53:
Disconnect and reconnect the battery, be careful
[Nexus 7 Original Development] everesee:
Thanks! It's charging without problem now :)
[Nexus 7 Original Development] tomskra:
Hi, yesterday I turn off tablet with 100% of battery. I had your ROM and 3.4 kernel. Today I want to turn it on, but tablet doesn't work. When I connect it to PC I see APX device. Have anyone advice what can I do? I tried this:

1. Plug in the usb into computer

2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds

3. The bootloader should show up.

4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.

But with no success
[Nexus 7 Original Development] reynard80:
Can't find it in the thread really, but does this kernel support f2fs?
[Nexus 7 Original Development] namerke:
Not yet, first thing first it should be stable with the basic features.

We are still waiting for an updated build with audio + auto rotation + charging fixes.

Fortunately the audio issue can be solved by setting a menu option and the overall experience is pretty good so far. :good:

I was thinking about building it for myself to play around with some features but i would need some guidance to fix the above mentioned problems first , i guess they need more work than just some cherry-picks.
[Nexus 7 Original Development] KawaiiAurora:
I would suggest looking at DC Kernel since this kernel is not exactly finished.

There are dangerous charging problems as of now so don't use it even with ext4.

This kernel will be out soon enough so stay tuned for that! ^^
[Nexus 7 Original Development] hcorion:
Support for F2FS?

Hey all.

I'm assuming (with my limited knowledge of kernels) that a kernel doesn't neccesarily need to support an operating system. Am I right? For example, if you built a kernel when android Jelly Bean came out, and I used that kernel with Android Marshmallow, it should, in theory, work, right?

Thanks, hcorion.
[Nexus 7 Original Development] Juste Dan:
the kernel will be released the day that the grouper wont support the smallest gapps package, i donated lots of money on devs and i never seen any jobs get done, im done with xda
[Nexus 7 Original Development] sheffzor:
Juste, will be easy to accomplish a script to resize system partition, its just not our focus now.

Sent from my OPO
[Nexus 7 Original Development] Ziyan:
You probably noticed that 90% of the work is done, based on people's reports in this thread... please, just try to be more realistic - I got just enough money to buy a used grouper (I don't remember the exact amount, but it was around $100). I spent hundreds of hours bringing up 3.4, here's how far it came. Do you really expect me to do things faster, with less bugs, and of course be sorry that I'm slow? Remember that we're still working for free... and not only for grouper, but for two other devices as well.
[Nexus 7 Original Development] um.z:
EDIT: Just realised this is only a rant. Initially thought the poster didn't know where to get a sufficiently small gapps package from.
[Nexus 7 Original Development] namerke:
[MENTION=2633638]Ziyan[/MENTION] & [MENTION=4619263]sheffzor[/MENTION] I hope you guys realize that most of us are actually grateful for your work, even if we donated we are not banging the door for updates every other second.

As usual the negative comments are always the loudest ones , but trust me, there is a silent majority.

Some of the users might be impatient , and excitement from their point of view is acceptable in my opinion.

As you mentioned 90% of the work is done and the remaining 10% basically means a step in to a much painless world with lollipop and marshmallow and... who knows after that.

If it were my "main" device for home entertainment I might get just as excited as some of us got.

I've playing around with the thought of setting up a build environment since I've been done some kernel modifications and rom builds in the past

but unfortunately it would be pointless because this project needs more knowledge then cherry-picking features from other branches.

I hope someday you'll find the time to finish the work on this project or at least to provide some guidance to other devs to fix the "charging issue".
[Nexus 7 Original Development] sheffzor:
Well, if you guys check our githubs you will find that we are working, globally, to the community, the grouper-aosp organization on github will be the place to release the stable commits.

https://github.com/ziyann/android_kernel_asus_grouper

https://github.com/apinela/android_kernel_asus_grouper

https://github.com/grouper-aosp/android_kernel_asus_grouper

As Zyan said, we aren't paid for this, we do it for love, not only by the community but essentially by the pleasure of developing those devices.

We still have a life and a job, so don't say that this is abandoned.

Google had 3 teams developing grouper board, Google, Asus and Nvidia, don't expect us to do the work of, 10-15 guys in a short period of time when we are only 2 without the access to information that those teams had in the grouper conception.

An example is the lack of datasheet for the smb347 charger IC, we are really hardworking to achieve the best, some times in a blind way...

Regards,

shfzr

Sent from my OPO
[Nexus 7 Original Development] ManoBros:
Hi, I installed DU 10 Grouper and can´t charge my Nexus 2012 ! yes i disconnected the battery and can charge it, but if discharge is the same... Tried to install 4.4 rom and is the same ... not charge !

Can you help me ?

What i do ?

Install a newer ROM that use your kernel 3.4 ?

recover i it using NVFlash ?

Thankx.
[Nexus 7 Original Development] jewshawn2:
Has anyone got this 3.4 kernel to work with any ROM(s) in the Nexus 7 Android Development forum?

I couldn't get the 3.4 kernel to work with the latest Pure Nexus Project 05/04/16 ROM. Cleared the cache but still won't boot after 10 minutes.
[Nexus 7 Original Development] sheffzor:
Disconnect the battery, press power on for 5 secs (it will not turn on obviously) just to discharge the capacitors, connect the battery cable, put it in charge, let it charge till battery is full.

You have to keep in mind that this is a major upgrade to the kernel, so there are some changes that are needed to the ramdisk too, so this is not only a kernel development, it is a whole device development, forget the kernel tree, grouper device tree and tilapia device tree as you know them for 3.1, those trees are completely reworked/re-adapted to the new kernel reality.

#######################

SO THIS IS A MESSAGE FOR ALL:

JUST DONT FLASH THE BOOT.IMG IN OTHER ROM OR EXTRACT THE zImage TO OTHER ROM, IT WILL NOT WORK

OR

IT WILL NOT WORK AS EXPECTED!

#######################

We have on our roadmap to release aosp-6.0, omni-6.0 and cm-13, so be patient if you don't have the ability to incorporate it by yourself OR if you have that ability, you can help us on the development...

Regards,

shfzr
[Nexus 7 Original Development] jewshawn2:
Thank you for the detailed reply. I thought I fully understood android mechanics but I guess I don't.

Good luck with everything you are working on.
[Nexus 7 Original Development] Dreamer...:
Thanks for your hard work!

What can you say about Vulkan support for GPU?

Or it's not kernel path?
[Nexus 7 Original Development] sheffzor:
From what I've searched only on L4T 3.10, so Tegra4 is the last compatible soc, we have no lucky on tegra 3 since the 3.10 got GPU drivers removed for that soc, but for some reason, nvidia kept a minimal support for cardhu board (tegra3), apparently it is bootable but without hardware GPU support, there are some cardhu dtb board spec files... Maybe nvidia will give a try on tegra3... But I don't think so, for now, if there is anyone that wants to have a pain work trying to forward port tegra3 GPU drivers from 3.4 to 3.10, there is chance to us to get kernel 3.10 for grouper in the future...

Sent from my OPO
[Nexus 7 Original Development] um.z:
Is there a guide for downgrading from the 3.4 kernel to a 3.1 rom anywhere? Heard this may/will cause charging issues.
[Nexus 7 Original Development] Ziyan:
Open up the device with the help of your your fingernails, and disconnect the battery for a few seconds. This will reset something that causes the issue (possibly some registers), so charging on 3.1 will work again. Speaking about that, this seems to be the only remaining big issue (we've got sound and rotation fixed since like a month now), but it really slows us down - finding out what exactly is breaking charging on anything non-3.4 is pretty time consuming :confused:
[Nexus 7 Original Development] Sage:
Cant wait. You guys are awesome.
[Nexus 7 Original Development] namerke:
Hi again [MENTION=4619263]sheffzor[/MENTION] .

I want to compile the sources to play around a bit and see what can i squeeze out this little slice of silicon.

I can see that on the dev branch you've switched to the upstream battery driver.

Did this results in any improvements regarding the charging issues mentioned in previous comments?

Or is this for some debugging / reverse engineering purpose?

If the device can charge on 3.4 properly that would be enough for me, i don't want to switch back to 3.1 anyway for a while now.

Also, could you explain commit 029b26b9c97ce9ee7afefb659cb80365296fc6d6 ?

I mean , reverting the commit that this commit reverts can result in performance degradation.

Am I wrong here? Is this for debugging also?

Would be glad if you could share some insights.

Thanks in advance.

:highfive:
[Nexus 7 Original Development] sheffzor:
Our goal is to keep this kernel the most straight possible to the mainline, if you check the asus bq custom driver, it is a mess, so we are trying to keep the things clean.

For now the only improvements we got were a few more battery properties that was not being manipulated by the asus bq driver.

btw, do you have charging issues on 3.4 if the battery capacity is above 5%?

This is just for testing and debugging proposes, just checking a new way to configure the hotplug, but from what we tested, we will revert it.

Next weeks we will try to get the charging platform and the docking handling stable, after that we will be ready do another release + some surprise :D

Regardz! :)
[Nexus 7 Original Development] WoolTomb:
This kernel works on Ziyan's CM13 for galaxy nexus?
[Nexus 7 Original Development] sheffzor:
WTF? Do you realize that this is a kernel for Nexus 7 1st gen?

Sent from my OPO
[Nexus 7 Original Development] WoolTomb:
Ops....sorry
[Nexus 7 Original Development] sheffzor:
Guys, just a taste.

[IMG="tilapia on CM-13.0 with 3.4 kernel"]https://i.imgsafe.org/a031d49.png[/IMG]

:victory::victory::victory::victory:
[Nexus 7 Original Development] DevUt:
What are the changes in the ramdisk :confused:

And BTW congrats :svetius:
[Nexus 7 Original Development] Reptilez_DK:
Awesome work guys !!! :highfive:
[Nexus 7 Original Development] sheffzor:
Check the sources, we had to change a lot.

Sent from my OPO
[Nexus 7 Original Development] DevUt:
https://github.com/Grouper-AOSP/android_device_asus_grouper ???
[Nexus 7 Original Development] sheffzor:
Yep.

If you have tilapia, must look @ android_device_asus_tilapia too.

Sent from my OPO
[Nexus 7 Original Development] DevUt:
Actually i don't have any nexus :p I have a HOX for which i m looking to update it to 3.4
[Nexus 7 Original Development] sheffzor:
Well, in that case, I think that this project won't help you, mainly because, this project focus the asus tegra devices from tegra2 to tegra3, so tf101 and tf201 could easily be a fork of this project.
[Nexus 7 Original Development] DevUt:
The HOX is also based on tegra 3
[Nexus 7 Original Development] DevUt:
Have you applied this patch http://dmitry.gr/index.php?r=06. Thoughts&proj=04. Android M on Grouper ???
[Nexus 7 Original Development] Ziyan:
No, if you take a look at our trees, you'll notice that we came up with less hacky fixes than those ;)
[Nexus 7 Original Development] DevUt:
Can you plzz plzz pplz plzz point me to them :laugh::laugh:
[Nexus 7 Original Development] sheffzor:
Check the OP.

Sent from my OPO
[Nexus 7 Original Development] DevUt:
Sorry I couldn't find please help :fingers-crossed:

---------- Post added at 11:26 AM ---------- Previous post was at 11:01 AM ----------

What about the kernel patch , I saw you hex edited libnvos.so but what about the kernel patch ?:confused:
[Nexus 7 Original Development] Ziyan:
The kernel patch isn't needed on 3.4 (and not mandatory on 3.1, but good to have).
[Nexus 7 Original Development] DevUt:
So if we need we can also apply to 3.4?
[Nexus 7 Original Development] Ziyan:
No! Our 3.4 kernel has the kernel/common android-3.4 branch merged in, meaning it's ready to go with the latest available Android versions.
[Nexus 7 Original Development] DevUt:
This is my kernel : https://github.com/DevUt/android_kernel_htc_endeavoru/tree/MM

This is the commit :

https://github.com/DevUt/android_ke...mmit/adf885cf57af0c19ea890006f4f6293c12db131f

So while giving it a 3.4 update should I revert the commit ?
[Nexus 7 Original Development] DevUt:
Is this the commit which started Linux 3.4 : https://github.com/Ziyann/android_k...mmit/335aa5f5de3b969b7411abea8be4c52ddb28473a
[Nexus 7 Original Development] sheffzor:
The first steps to get endeavoru on 3.4 kernel is to fork the latest 3.4 kernel from nv-tegra.nvidia.com, and then start trying to boot the device after update the board files (arch/arm/mach-tegra/board-endeavoru-*) and the common tegra plaform files, then you must focus on pushing the drivers for kernel 3.1 to kernel 3.4 and do all the adaptations to match 3.4 kernel changes.

It's a pain in the ass.

Maintaining a device its a completely different job in comparison to major kernel upgrade, its literally like developing the device from the scratch, with the diference that we already have alot of work done to be based on.

So good luck, and focus on arch/arm/mach-tegra/* directory. :P
[Nexus 7 Original Development] DevUt:
OK I went to nv-tegra.nvidia.com but couldn't find 3.4 it had 3.10

Edit : found http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=summary
[Nexus 7 Original Development] sheffzor:
http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=summary

Nvidia started the 3.4 heads on the 2.6 repo... :P
[Nexus 7 Original Development] namerke:
[MENTION=4619263]sheffzor[/MENTION]

To answer your question, no. Actually I don't have any issues when I start charging from a bigger percentage then 5%.

And it's on the latest build published by you guys. (grouper)

Looks like I have to watch out not to completely drain the battery while playing games / watching some movies. :)

BTW looking forward to the build that you just recently teased.

I was gonna commit the latest available patches for F2FS and experiment with zRam and lz4 compression in zRam to see if they can have a boost on performance like they did on some of my older devices.

But now I would rather wait for a base that is judged stable by you guys.

Thanks for your effort.
[Nexus 7 Original Development] everesee:
Any news? I'm still following this thread, hope It will be released some day :)
[Nexus 7 Original Development] PJBrs:
[MENTION=4619263]sheffzor[/MENTION], [MENTION=2633638]Ziyan[/MENTION], thanks for you work, it's an inspiration! I'm trying to port the Lenovo A2109 to kernel 3.4. It's a tegra3 device, a lot like grouper. I was hoping that perhaps you might have some tips. Also, dmesg output for 3.4 on grouper might be very useful!

I've studied your grouper changes as well as nvidia's changes to arch/arm/mach-tegra/board-kai* (Lenovo changed the board-kai files for A2109), I ported all the drivers (two cameras, light sensor, accellerometer, touch screen) as well (I'm not entirely sure that I did so correctly, but hey!)

Now I've hit a snag. My kernel comes quite some way to booting (I use a twrp image in which I changed the kernel). The twrp flash screen pops up, stays for a while, and then disappears. After that - nothing. No adb, no /proc/last_kmsg.

If I change the kernel config to use IOVMM_SMMU instead of IOMMU_SMMU, then I hit a kernel bug in nvmap, before the twrp ever shows up. Did you have similar experiences? Perhaps tips for how to get dmesg after all? Anything might help. My sources (it's the A2109-linux-tegra-nv-3.4-SLOPPY branch).
[Nexus 7 Original Development] PJBrs:
[MENTION=4619263]sheffzor[/MENTION], [MENTION=2633638]Ziyan[/MENTION], still hoping to hear from you. In the meantime, I have added a kernel panic work queue:

static void mykmod_work_handler(struct work_struct *w);
static struct workqueue_struct *wq = 0;
static DECLARE_DELAYED_WORK(mykmod_work, mykmod_work_handler);
static unsigned long onesec;
static void mykmod_work_handler(struct work_struct *w)
{
printk("PAAAANNNNIIIIICCCCC...\n");
panic("force-panic");
};

If I wait 2055 msecs before panicking I still get dmesg, after that only hard hang.

So now at least I have dmesg with IOMMU_SMMU as well. I'm attaching my /proc/last_kmsg in the hope that something might stand out to you. And if anyone would be so kind as to post dmesg for 3.4 on grouper I'd appreciate it very much!