yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Original Development] adstraylight:
He's busy with the N4, but I'm sure he'll get to us in time. Personally I don't mind the wait, especially as my other device is an N4.....??

I have noticed a few comitts for the tegra3 going into the 8.0 repository though, so hopefully the grouper won't be too long?
[Nexus 7 Original Development] abhifx:
whew... lots of commits pertaining to tegra. lets hope grouper is getting O goodies
[Nexus 7 Original Development] Motorhead1991:
Glad to see you guy got this working ziyan. Sorry I disappeared when I did, I just couldn't take the BS anymore (not in this group, but elsewhere).
[Nexus 7 Original Development] dirtyreturn:
Has anyone been able to get signature spoofing enabled with this rom somehow?
[Nexus 7 Original Development] sheffzor:
Yeahh, we aren't sleeping! :eek:

... After a painless war against gralloc, I got it working, so what I've to say after that is that Wifi, NFC, Bluetooth, and 3G(tilapia variant) aren't working.:victory:
[Nexus 7 Original Development] abhifx:
Didn't knew the progress was this huge when i saw commits on gerrit. good thing our old device will / Can get Oreo.

can i ask if we will get enhanced bluetooth codec? cause that is the only interest i have in Oreo.. and faster boot.. cause that will be a bonus on our old device.
[Nexus 7 Original Development] ameinild:
Hi. Can you please post a new link for the twrp-3.0.2-0-grouper-k3.4-20170111.img files, the link is not working. Thanks :)
[Nexus 7 Original Development] DumF0rGaming:
download official TWRP
[Nexus 7 Original Development] sheffzor:
Just to keep the progress here, we already have Bluetooth and wifi working, I'll work on NFC, radio(tilapia) and a sporadic crash from gralloc next week.

We should release and experimental build next week.

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] ameinild:
Ok thanks. :)
[Nexus 7 Original Development] adstraylight:
Just saw the sensors commit on the gerrit, it looks huge! Thanks so much for the effort you guys are putting into bringing O to our humble groupers!
[Nexus 7 Original Development] abhifx:
the open commits are filled with grouper / tegra 3 commits. :D
[Nexus 7 Original Development] adstraylight:
I know, I've been watching - feels a bit like looking over somebody's shoulder, but I can't help it....?
[Nexus 7 Original Development] adstraylight:
Loads of cve patches added to the tegra3 kernel yesterday....maybe a prelude to an upgrade?.....
[Nexus 7 Original Development] abhifx:
Good thing three developers are working on tegra 3. Lots of grouper commits are still pending to me merged. Sadly Bluetooth LE didn't work or something like that. Mmmm..,
[Nexus 7 Original Development] adstraylight:
Yeah, still feels like nerdy voyeurism, but good fun none the less ? As you say, it's a good thing there is so much support for the tegra3...

To change the subject, or maybe not, has anyone else noticed that the system is very slow to react to a change of power state ie plugging/unplugging the charger, and also that it is slow to wake on occasion?

I believe AndiSa has noticed a similar thing on his build, and may even have a solution...

Edit: I've just found where he mentioned it:

[MENTION=2633638]Ziyan[/MENTION] - sorry to disturb you, but is this helpful?
[Nexus 7 Original Development] AndDiSa:
[MENTION=2583740]adstraylight[/MENTION] it's very difficult to find the reason for the strange behaviour of the charger(s) with our device, but this discussion is going on for almost 6 years now :)

For me it's sometimes reacting very fast, increasing the charging power step by step until it reaches a certain limit (currently on m device it's always around 650mA-700mA). Sometimes in contrary it doesn't show any reaction ... it stays on 50mA, probably goes up to 150/200 but goes down again :(

I came to the solution that there are several factors influencing this behaviour

1) the power and voltage the charger can provide on a stable base. There are chargers who claim to provide 2.5A/5V but when connected to the device the voltage goes down. The AICL notices the voltage drop and reduces the current it is requesting from the charger leading to slower charging. This process continues until there is a stable voltage available.

2) a stable and conductive connection as on the charger side as on the USB port side and a high quality cable. If the resistance is too high, voltage goes down and leads to slow charging

3) the age / status of the battery itself (my battery e.g. shows some voltage jumps from time to time and this is influencing very much the charging rate as AICL is reacting on the voltage change)

For sure also the kernel charging driver / battery driver / power management component have some influence, but probably less then we are all expecting ...
[Nexus 7 Original Development] adstraylight:
I agree with all of the above, but was wondering what causes the slow reaction within the system to the current status of the charging situation, not the physical rate of charge. My dock/charger combination reliably charges the battery, but the system settings don't reflect this when I first connect the tablet, there is a significant lag between placing the device in the dock, and the system saying "charging on AC", equally it can take a long time for the system to recognise that it has been disconnected. I have been considering trying to lower the oom priority of system ui, as a possible fix, but doubt it will help.

Also, it can sometimes take a long time to wake from deep sleep when it has not been on charge at all, but this may be a separate​ thing.

This seemed to be what you were referring to in the post I quoted, but this may have been wishful thinking on my part? as aside from this, and system ui still very occasionally crashing in instances of high background load, everything is running remarkably well. Especially now that I avoid using the Google app (chrome's search widget is so much faster), have stopped playing with Maps, and have given up on the YouTube app entirely (won't run, I suspect a local issue unique to my setup).

Thanks for your comprehensive and thoughtful reply in any case☺️
[Nexus 7 Original Development] AndDiSa:
[MENTION=2583740]adstraylight[/MENTION] I didn't want to go too deep into implemetation details. Yes, you are right, there is a significant lag between pluging in an USB cable and the reaction on charging. There are several constants distributed over several places which block / delay cable type detection. I noticed e.g. that cable type detection is quite fast on battery side (dmesg | grep bat) and almost immediately the correct cable type is detected but the charging limit is not set immediately, but with a huge delay. Sometimes it may take minutes until the charging limit is increased from 900mA to 1800mA (dmesg | grep lim) but you can notice, too, that immediately after the new limit is set, the charging current is jumping upwards.

We need to find a way to reduce that lag ... question is how to.

Beside that, my charging rate never reaches / comes near to the maximum of 1800mA ... I have the impression that the current which is currently used by the tablet (display, cpu, wlan, ...) is subtracted from the charging power and the battery is charged only with the remaining power. Probably there is a way to change that behavior, but I am lacking some deeper knowledge.
[Nexus 7 Original Development] adstraylight:
So, if the dmesg is broadcast promptly, then surely the fault lies with the the reciever (system ui? Settings?) perhaps either not being loaded or awake at the time of broadcast. This was why I was wondering if causing an element of the system to remain memory resident permanently might fix the issue (oom value of -17). I think this approach maybe how Nova launcher avoids redraws with its aggressive desktop option...or perhaps it is simply a doze thing, ie taking the relevant process out of battery optimisation?

To me, both of these options seem like fairly blunt tools to use against a very specific problem, that may have unintended consequences and miss the issue entirely.

It could equally be that the system is doing the right thing and waiting for the charging current to become established before reacting. I'm sure this didn't happen in previous versions of android though, so it's probably down to a change in the aosp code... thinking some more suggests that what is being listened for has changed to more accurately reflect the charging state to the user, but that our hardware is perhaps too slow to make this viable...this accords with how the 'not charging' message is new to andoid N...

This is where my knowledge\speculation fails also....?

Maybe we'll get lucky and this will be\is fixed in O...?
[Nexus 7 Original Development] abhifx:
libsensors are merged... hurrah. one more giant step for O in Grouper
[Nexus 7 Original Development] Servo260:
Hi, I have a grouper 32gb with the latest build and opengapps pico, latest version also, and I can't make skype to work. It just hangs and never open... Happens the same with the camera app (with camera M app too). Are there some fix for this issue?

In general, the system is quite unstable, specially play services wich stop working all the time. But it runs so smooth I don't want to go back to a 3.1 kernel.
[Nexus 7 Original Development] adstraylight:
The camera seems to be broken in these builds, I suppose it's not that hgh a priority, particularly now as the main focus looks to be oreo. I posted logs about it some time ago, so hopefully it will be addressed when 8 is released...
[Nexus 7 Original Development] Ziyan:
Camera is a known problem, but play services should not stop! Verify that you installed them correctly; use https://xdaforums.com/showpost.php?p=71808422&postcount=2 as a guide (you'll probably need pico gapps) :)
[Nexus 7 Original Development] abhifx:
any experimental build in sight?
[Nexus 7 Original Development] yaro666:
can anyone upload twrp, link is broken for grouper
[Nexus 7 Original Development] adstraylight:
You can use the standard 3.1 TWRP to flash this ROM. This confused the hell out of me at first as the OP is unclear, it also has not been updated for some time.
[Nexus 7 Original Development] abhifx:
Too much of silence in this thread

Hi [MENTION=4619263]sheffzor[/MENTION] & [MENTION=2633638]Ziyan[/MENTION]

Can we expect some test build with aosp oreo for our beloved but getting very old tablet?

We would love to give help in whatever way we can.
[Nexus 7 Original Development] sheffzor:
Hey guys,

It should be bootable but still, very unstable:

http://builds.unlegacy-android.org/aosp-8.0/grouper/

Sorry for taking too long, yet this is my hobby, as it is everyone in UA, I have other priorities in my life :P

The focus will be to bump to 8.1 and try to stabilize it there.
[Nexus 7 Original Development] abhifx:
Hi! Thanks for developing such hobby as every grouper user is getting benefit from it.

Looking at other forum, it seems many devises got broken again. Lets hope our tablet does better
[Nexus 7 Original Development] gabrielbsb:
any chance it will get OTG charging?
[Nexus 7 Original Development] Ophidian_DarkCore:
if you add it. it'll only take you a couple days to learn how to mod and hack around the source. you don't need to know C. You need common sense and problem solving skills. We would all really appreciate another dev.
[Nexus 7 Original Development] namerke:
I've got my tablet back for a few days to mess around, therefore I've cloned the sources and hard coded my pcbid and projectid which are the following:

As far as I understand this is the so called problematic 3rd board type so I didn't have my hopes too high.

Then the following happened, (almost ;) ) automagically:

Yeah, so it boots with the latest stock android and the ramdisk of the stock boot.img on top of it.

Unfortunately there are some display and audio (this one is acknowledged in the first post) glitches.

I've also encountered a rare hangup (kernel panic?) -> reboot after some usage, although it only happened like once or twice.

I'll have this thing with me for the next few days to play around, so [MENTION=2633638]Ziyan[/MENTION] hit me with anything you need to know to smooth out the kernel.
[Nexus 7 Original Development] fra9090:
Come on guys ;)

You Can do it!!
[Nexus 7 Original Development] sheffzor:
What was the change to put kernel working? Selinux permissive?

Enviado do meu A0001 através de Tapatalk
[Nexus 7 Original Development] 19dragon98:
I built with SElinux in Permissive mode [emoji3]
[Nexus 7 Original Development] Ophidian_DarkCore:
You can force selinux mode in defconfig ;)
[Nexus 7 Original Development] fra9090:
Come on guys! YOU CAN DO IT!!
[Nexus 7 Original Development] Indha Lezzio:
As i used to say to girls several years ago: "i'm not in a hurry but i really want to" :)

Success guys!

Enviado desde mi Nexus 7 mediante Tapatalk
[Nexus 7 Original Development] sheffzor:
Hi guys!!

Ok, after some days messing around with the kernel trying to put it working on my tilapia, I just failed... :(

BTW, I took some notes about i2c-2-0028(cap1106), that was failing to register due -16 code (device is busy, I think) but if I initialize misc module before i2c,spi and usb, it just does the trick and it don't fail anymore.

Can someone else check my kmsg e help me to debug the problem ?

I'm stuck on "BUG: soft lockup - CPU#1 stuck for 23s! [irq/118-max7766:34]".

Anyway, is it possible to debug in real-time having the code side-by-side with the running machine, like we do in eclipse with simple programs?

PS: Put SELinux to permissive mode didn't help...

[MENTION=2633638]Ziyan[/MENTION]
[Nexus 7 Original Development] Streetwalker:
Alright, finally got my tablet back, rebuilt CM and wiped it last night. I built this kernel this morning using arm-eabi-gcc 4.8 from AOSP, everything seems fine except for the screen which is very glitchy (edit: apparently it's alpha drawing or something, cause only shadow effects and text are affected). Will mess around a bit more. The only thing I changed was to disable SELinux because I hate it.

For the record: pcbid=0x009e (projectid=0x00), MAX77663.
[Nexus 7 Original Development] Ziyan:
Replace /system/lib/libnvrm.so with the one in the downloads section, and the glitches should be gone :)
[Nexus 7 Original Development] Streetwalker:
Great, thank you. Anything I could do to help ? Is there a todo list somewhere ?
[Nexus 7 Original Development] Ziyan:
Updated the first post ("What doesn't work / TODO") :)

The easiest thing might be the touch boost, you might feel like the kernel is slower on gui taps than 3.1 until it's merged, as the default interactive governor won't ramp up the frequencies instantly without it, like 3.1 did - it's pretty lazy. After that, there's the android-3.4 merge, the sometimes slow resuming, the stuttering audio, and finally the non-booting kernel issue for 3g variants (?). While I have other projects going on atm, hopefully I'll have a little more time in the upcoming couple of weeks to work on this :)
[Nexus 7 Original Development] Streetwalker:
I just fixed audio with a userspace hack. I'll see if we can do anything from the kernel side, but the logcat spam while audio is playing led me straight to this : https://github.com/CyanogenMod/android_device_asus_grouper/blob/cm-11.0/audio/audio_hw.c#L714

Commenting that usleep out makes audio perfect.
[Nexus 7 Original Development] HTCDreamOn:
[MENTION=5150287]Streetwalker[/MENTION] nice one, thanks for exploring and finding a fix.

I've been looking at interactive but had problems with the kernel booting , then found it was my ROM, then had schoolwork in the way and haven't had time to start with a clean slate at the latest booting point and get some real work done.

If you've got audio fixed though, that interactive boost is the last major hurdle really before making sure everything else is properly up to date.
[Nexus 7 Original Development] Streetwalker:
W/audio_hw_primary( 145): out_write() limiting sleep time 2018374364 to 23219

That timing looks way off, my guess is that the kernel has some broken math. I'll look at the kernel side of things in a bit and see what's different from 3.1. Even the 23ms limit is huge for audio, no wonder why it was stuttering.

Did some testing, CM's 3.1 kernel does cause it to compute excessive delays as well but it works fine with or without the delay. I guess we'll have to expect ROMs to support this fix on their own side, and for stock just replace /system/lib/hw/audio.primary.grouper.so with a patched version based on AOSP.

Here's the change, it's really nothing but that's all I could find.

https://github.com/WalrusMod/androi...mmit/006e51829e9ec2c59c8cb2e0a16bf8ca98f2a50c
[Nexus 7 Original Development] anzi2001:
Hello guys :) im willing to contribute to this since i have loads of time but i nedd a guinea pig(for testing cause my nexus 7 broke a month ago) and some guy to teach me a bit more advanced kernel building but i do know the basics so

It wont be that hard :)
[Nexus 7 Original Development] sheffzor:
Guys, I've tried to understand what was soft-locking my device (pcbid=0x040e projectid=0x01 - HW Rev.: PR), tilapia, but my knowledge in kernel hacking isn't the most experienced, so anyone have an idea where to start?

The problem, apparently, resides in the max77663 driver.

Call stack:

I tried to revert some commits from max driver but it didn't help...

So... Ideas?
[Nexus 7 Original Development] Streetwalker:
I'm getting a lot of these crashes by the way (possibly related to suspend). https://gist.github.com/bd4fd69a5cbe06ce031c

The tablet is sitting next to me and constantly rebooting after a few minutes, but it wasn't crashing when the USB cable was plugged in.

Here's another log https://sr.ht/1kLY.lastkmsg
[Nexus 7 Original Development] gmikhail:
Thanks for you work!

Unfortunately 8 did not boot. Clear flash (full wipe/ext4) without gaaps. I waited about 20 minutes. Tablet has warmed up but nothing happened (only animated Android logo).
[Nexus 7 Original Development] DumF0rGaming:
last_kmesg and dmesg are required here. Please Google how to get those and share it with developer
[Nexus 7 Original Development] Displax:
So, here is dmesg.

last_kmesg not found.
[Nexus 7 Original Development] adstraylight:
So did anyone get the experimental build to boot?
[Nexus 7 Original Development] abhifx:
Nope.. but then i was already half hearted that this wont boot not didnt waited that long
[Nexus 7 Original Development] Ziyan:
We finally got around to update our ancient OP, to highlight that this stuff isn't experimental anymore (at least on Nougat). :)

Still, let us know if there are any problems (other than a reported 3G specific issue).
[Nexus 7 Original Development] abhifx:
well well... finally title of the project reflects whats really inside the thread.

apart from sluggishness after a while of usage, grouper seems to work just fine (every hardware functions as it should).

BTW, why the OP says android version as gingerbread?
[Nexus 7 Original Development] adstraylight:
Well if I were to be pedantic, the new OP says nothing about the known issues with the camera.....??

Thanks for updating it though ☺️
[Nexus 7 Original Development] Ziyan:
Can you send a logcat about the camera issue? I can't test at the moment, but I think I have an idea about what's wrong :)
[Nexus 7 Original Development] adstraylight:
I posted one sime time ago : https://xdaforums.com/showpost.php?p=73620287&postcount=930

The errors are still the same, and they run continuously in the log. I have never used the camera much (occasional skype maybe), but I think these errors must be impacting overall performance by their regularity and frequency.

Thanks for looking into it.
[Nexus 7 Original Development] adstraylight:
Here's one from today..
[Nexus 7 Original Development] Ziyan:
Interesting - I didn't have such errors after the initial 7.1 bringup. It must be something since then - I'll try fixing it before the end of the year.
[Nexus 7 Original Development] chemahg7:
Hi, first of all thanks for keeping alive this precious piece of hardware

So i try the 8.0 build and like others said the tablet doesn't boot, here is some log till the rescue party reboot it in recovery mode, hope it helps
[Nexus 7 Original Development] adstraylight:
Thanks again ☺️

I always do a /system wipe along with dalvick and /cache when updating, and I'm currently running 20171214, so I doubt it's anything local, unless I have a hardware fault....

Does anyone else have a problem with the camera?
[Nexus 7 Original Development] Ziyan:
Alright, I got around to do a bit of testing today. Camera is indeed messed up. Today's build fixes the continuous camera crashing in the background, but it's still not working if you try taking a photo - working on it :)

I'll also take a look at power management. I think it's a bit too aggressive at the moment, causing stuttering here and there.
[Nexus 7 Original Development] min1968:
Any chance to get Oreo on tilapia?
[Nexus 7 Original Development] adstraylight:
Thanks!

I noticed the difference in the log spam, now it looks like the system is searching for a camera flash unit, which of course our grouper doesn't have, could this be why it still fails?
[Nexus 7 Original Development] dirtyreturn:
Hi there XDA, within the past few months or so the builds.unlegacy-android.org has been flagged by McAfee as having something wrong with its certificate. I don't know if something is wrong or even if it is important. Would you please advise.
[Nexus 7 Original Development] AndDiSa:
[MENTION=4217078]dirtyreturn[/MENTION] I do not see any problems in accessing the site with chrome and the certificate looks as a valid one issued by Let's encrypt
[Nexus 7 Original Development] AndDiSa:
Deleted ... double post
[Nexus 7 Original Development] dirtyreturn:
Ok, just didn't know. It is accessible with data, my home WiFi just does the flagging. Idk. So everything is cool then I suppose?
[Nexus 7 Original Development] slybunda:
tried installing this today along with open gapps pico. once it boots up and goes into setup after selecting language and choosing setup as new it keeps crashing saying: "Setup Wizard Keeps Stopping" and just an option to close the app and it keeps doing this.

any ideas?
[Nexus 7 Original Development] JT1510365:
I am downloading and flashing your 6.0 and 7.1.2 legacy builds and i will report back to you thanks so much for your hard work you are giving to the community we appreciate it so much:)

Cheers:)
[Nexus 7 Original Development] sinkoo1979:
same problem.
[Nexus 7 Original Development] warpurlgis:
McAfee is trash.
[Nexus 7 Original Development] temuulenchoi:
Had the same problem. Install it with beans gapps. If you're lucky, it'll boot up with play store.
[Nexus 7 Original Development] dirtyreturn:
Gotcha! Thanks.
[Nexus 7 Original Development] mn.code:
Here is a little workaround for setup wizzard crash:

1. Connect the tablet to PC

2. Use adb to enter following command

adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings

3. Wifi settings should be opened now on your tablet, turn on the wifi (and connect to a network if you want)

4. Return back to setup wizzard (by pressing back) and you are good to go ;)