yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 8.9 Android Development] StarkCity:
Very interested.....
[Galaxy Tab 8.9 Android Development] ibanezq:
Yummy! I :)
[Galaxy Tab 8.9 Android Development] gingernator007:
Awesome, I've been using this build happily for weeks. Looking forward to the update.
[Galaxy Tab 8.9 Android Development] pseudoheld:
ooh please do make a new version.

running cm10 on my razr and im very happy with it!
[Galaxy Tab 8.9 Android Development] boscorama:
Cold. :(
[Galaxy Tab 8.9 Android Development] RenoXDA:
Hi, good job.

Any chance to get last builds?
[Galaxy Tab 8.9 Android Development] C-o-M:
Don't give too hope in me. I can upload the latest ROM, but it's kind of useless. The kernel is not able to resume from deep sleep. Unfortunately I have no idea, where to look for the root cause is. Maybe some kernel hacker can help me. There are two problems:

With cable connected, the screen goes on, but the light stays dark (at least darker as it is normally). Touchpad doesn't work, no reaction on power button (I get those in dmesg 'input: [sec_power_key] P', so the kernel receives the key press, but it doesn't react). ADB fully works here.

Without cable connected, the kernel gets some 'Unable to handle kernel paging request' oops and the system reboots.

Also, it doesn't depend on which kernel I take, I get the same errors with Samsung's ICS kernel ...
[Galaxy Tab 8.9 Android Development] pseudoheld:
pershoot is THE man!

he helped kallt out a lot from what i heard and is one of the most active and well respected devs!

try and contact him, telling him that you are trying to continue kallts work. maybe he will help you out.

if anyone can figure it out its him. he's a f*cking jedi and very well versed with the 10.1 which is nearly identical to our tab!
[Galaxy Tab 8.9 Android Development] dknotty:
Right so after a lot of faffing I installed CWM 6.0.0.8 then flashed the ROM and now I have a scrolling screen.

How do I actually get this rom working???
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
I would give so much, to have a stable and smooth CM10 build for my Galaxy Tab 8.9 :(

But development has stopped :(
[Galaxy Tab 8.9 Android Development] C-o-M:
You've flashed a ICS Stock rom before, haven't you? Try the experimental build, it should work. Sorry, that was the CM9 build. If you have that rolling screen issue, you probably have to downgrade your bootloader to get this running.

Yes? What would you give?
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
I would catch a gerade foooor yaaaaaaaa yeeeah yeah yeeeeah :)
[Galaxy Tab 8.9 Android Development] :
any chance to see a release with 3.1 kernel now that you're back kk? ;)

as said in the cm9 thread, skip it and continue with your awesome cm10 builds. thx for all
[Galaxy Tab 8.9 Android Development] C-o-M:
I'll gave it another try and switched back to your kernel. Then the tab reboots when it tries to go to sleep. Kernel messages look always the same:

[ 75.520891] request_suspend_state: sleep (3->3) at 75509651002 (2012-10-07 20:53:21.952521999 UTC)
[ 75.523601] [TSP] melfas_ts_early_suspend
[ 75.524426] melfas_touch_power_enable off
[ 75.531588] acc_con_early_suspend
[ 75.532340] dhd_early_suspend: enter
[ 75.533073] dhd_set_suspend: enter, value = 1 in_suspend=1
[ 75.534072] CFGP2P-INFO2) wl_cfgp2p_p2p_listen_suspend : enter
[ 75.535104] dhd_set_suspend: force extra Suspend setting
[ 75.549226] + cmc623_suspend
[ 75.630043] Unknown PRIVATE command SETSUSPENDMODE 1 - ignored
[ 75.961362] - cmc623_suspend
[ 76.293895] sync_system +
[ 76.295161] active wake lock sync_system
[ 76.330387] PM: Syncing filesystems ...
[ 76.331588] sync_system -
[ 76.336513] done.
[ 76.337516] Tegra cpufreq suspend: setting frequency to 216000 kHz
[ 76.361729] Freezing user space processes ...
[ 76.376891] [Keyboard] sec_keyboard_disconnect
[ 76.379737] ------------[ cut here ]------------
[ 76.382048] WARNING: at drivers/tty/tty_ldisc.c:474 tty_ldisc_close+0x28/0x54()
[ 76.383154] Modules linked in: dhd
[ 76.386075] [<c0013a60>] (unwind_backtrace+0x0/0xe8) from [<c0049e58>] (warn_slowpath_common+0x4c/0x64)
[ 76.387728] [<c0049e58>] (warn_slowpath_common+0x4c/0x64) from [<c0049e88>] (warn_slowpath_null+0x18/0x1c)
[ 76.388752] [<c0049e88>] (warn_slowpath_null+0x18/0x1c) from [<c0277398>] (tty_ldisc_close+0x28/0x54)
[ 76.390159] [<c0277398>] (tty_ldisc_close+0x28/0x54) from [<c02773f4>] (tty_ldisc_reinit+0x30/0x50)
[ 76.391824] [<c02773f4>] (tty_ldisc_reinit+0x30/0x50) from [<c0277944>] (tty_ldisc_hangup+0x1d0/0x290)
[ 76.393371] [<c0277944>] (tty_ldisc_hangup+0x1d0/0x290) from [<c0271544>] (__tty_hangup+0x110/0x340)
[ 76.394798] [<c0271544>] (__tty_hangup+0x110/0x340) from [<c02717f4>] (disassociate_ctty+0x74/0x1fc)
[ 76.395856] [<c02717f4>] (disassociate_ctty+0x74/0x1fc) from [<c004dc1c>] (do_exit+0x200/0x634)
[ 76.397269] [<c004dc1c>] (do_exit+0x200/0x634) from [<c004e0e0>] (do_group_exit+0x90/0xc0)
[ 76.398663] [<c004e0e0>] (do_group_exit+0x90/0xc0) from [<c004e120>] (sys_exit_group+0x10/0x18)
[ 76.400128] [<c004e120>] (sys_exit_group+0x10/0x18) from [<c000dcc0>] (ret_fast_syscall+0x0/0x30)
[ 76.401604] ---[ end trace a6c5c53fefc4bf62 ]---
[ 76.421683] (elapsed 0.05 seconds) done.
[ 76.423125] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done.
[ 76.443395] Suspending console(s) (use no_console_suspend to debug)

No errors detected
[Galaxy Tab 8.9 Android Development] mngarogore:
Is there paranoid android for this jellybean for this tab
[Galaxy Tab 8.9 Android Development] pseudoheld:
no + wrong thread!
[Galaxy Tab 8.9 Android Development] Jnn1:
Hew .. so KK has his GTab 8.9 back repaired? That is the happiest news in this community in a long time! Last month, after waiting and waiting, I finally tried out Samsung's ICS, and though it was much smoother than I had anticipated, I just couldn't bare the chaotic and random color scheme. It really "bleeds my eye out" as nexus_g said. So, I've returned to KK's CM10, and just hoping and hoping for an update!!
[Galaxy Tab 8.9 Android Development] sbE:
FULL ACK!

I'm also very very happy that KK is back in business! I hope we can try soon a reasonable ROM for our lovely 8.9.
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
I just tried using the latest stuff pushed for the p4wifi and I still have the sleep problems.

I think the stuff we see in kmsg is just what always happens on sleep. The last line says:

[ 76.443395] Suspending console(s) (use no_console_suspend to debug)

That means nothing more will be printed on the console so whatever happens when it's sleeping won't print.

What I am doing now is compiling a new kernel with the no_console_suspend option added to see if I can find any new clues.
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Tried disabling CONFIG_DEBUG_SLAB which change the behavior a bit. Now it usually turns back on but the crashes shortly after. So whatever memory corruption that CONFIG_DEBUG_SLAB detects when suspended seems to cause a crash later when you awake it from sleep.

No idea what causes this and why it only happens with JB and not with ICS.
[Galaxy Tab 8.9 Android Development] dafzuka:
Keep up the great work with the troubleshooting. We're grateful to have a dev of your caliber on the case.
[Galaxy Tab 8.9 Android Development] C-o-M:
OK, it seems like CPU1 is not willing to sleep (in fact, that is not completely true. CPU1 seems to be sleeping, but slab fails to clean up the memory of the processes that used CPU1). So it might help to let CPU1 alive by disabling CONFIG_HOTPLUG_CPU.

Edit: Mmh. Maybe then suspending will fail at all:

---------- Post added at 05:11 PM ---------- Previous post was at 04:48 PM ----------

Can you post the kernel message from that crash?
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
pershoots says sec_keyboard is causing the trouble. Removing the sec_keyboard service seems to have fixed the problem for now.
[Galaxy Tab 8.9 Android Development] C-o-M:
Keyboard dock. Didn't even know that this exists. Maybe I'll buy one and fix it :D

Edit: Damn. I should have seen this earlier. I was always wondering where that console /dev/ttyS0 is. Now I now it: it's sec_keyboard.
[Galaxy Tab 8.9 Android Development] safariking:
Are we able to intergrate the new Android 4.1.2 in CM10?
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Here's a P7310 build without the sec_keyboard service: http://www.mediafire.com/?lkp24imp9w4es41
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
@kallt_kaffe when we could expect a new JB build or eben JB nightlies ? I don't want to rush you !! Take the time, the project needs.

I just want to say: we put all hopes on you, because you are (so far as i know) the one and only dev for our tab. :victory:
[Galaxy Tab 8.9 Android Development] C-o-M:
@Straßenapotheker: Guess what he posted 10 min before?
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
Ok, so please tell me what "without the sec_keyboard service" means. What are the differences to the Version of the 08-08 ?

I can still use my keydock ?
[Galaxy Tab 8.9 Android Development] C-o-M:
Thanks, but I already built my own. Let's see if it's running better. I never thought it could be a f**ing blob that kills the tab.

---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------

No. Keydock is now dead for a while.
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
I means the sec_keyboard service is disabled. According to pershoot it is needed for the keyboard dock.

It uses the new Linux 3.1.10 kernel instead of the old 2.6.32 kernel. That means it is faster and both cameras works.

Likely not, but I do not have one so I cannot test. My bluetooth dock is working fine though. Actually I thought the keyboard dock worked as an USB keyboard so I never thought it needed a special binary to work. Perhaps it will work, maybe it's only purpose is to send keyboard dock events. If you flash the new version, then please report if the keyboard dock works or not.
[Galaxy Tab 8.9 Android Development] sbE:
Nice to see that we have 2 guys who work with passion on a CM10 Release....i love you so much. :)
[Galaxy Tab 8.9 Android Development] _strauch_:
@kallt kaffe is it Android 4.1.2?
[Galaxy Tab 8.9 Android Development] pseudoheld:
so any reports? is it working for everyone?

if so could you maybe please compile a 7300 version? :D
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Yes

Here: http://www.mediafire.com/?7tiux22yrhux04u

However it is missing 3 libs, but I'm not sure if it matters. I'll upload new builds tomorrow.

These are the missing libs, you can copy them from the P7310 build:

system/lib/libwvm.so

system/lib/libWVStreamControlAPI_L3.so

system/lib/libwvdrm_L3.so
[Galaxy Tab 8.9 Android Development] pseudoheld:
awesome mate! downloading it now.

have to recharge my tab before flashing but then i will let you know!!!!
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
This is good news, I try to split the little time I have for this between improving my keyboard app and making CM builds and I sure won't mind others working on this too.

I've updated my latest repos to https://github.com/kalltkaffe now. Bluetooth audio didn't work for me when I tried to stream Spotify music to my Bluetooth speaker but everything else (that I've tested) seems to work fine. Also Google Maps doesn't seem to crash CM10 like it does with CM9.

Keyboard docks (non-bluetooth) are likely not working properly (or not at all) since we had to kick sec_keyboard out of init.p3.rc. Pershoots says he's working on it since the 10.1 ports are affected by this too.

I really would like to hear from someone with a (non-bluetooth) keyboard dock that has tried the new build that can report if the keyboard dock works at all with the sec_keyboard service disabled.
[Galaxy Tab 8.9 Android Development] :
Gj kaltkaffe and com1, aswell as pershoot (gotta love this guy). But same question here: does this mean no keyboard support? What are the differences?

EDIT: Wow my post is waaay to late..
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
@kallt_kaffe

i'll test your next build (tomorrow) and post the result here in this thread.

information: my keydock
[Galaxy Tab 8.9 Android Development] C-o-M:
The Samsung keyboard dock won't work (although I have none yet, I'm pretty sure). It doesn't use bluetooth nor usb. Instead there is a serial port in the 30pin connector. The sec_keyboard service seems to be the user space part of the serial keyboard driver.

I'm wondering if we could use that serial port for some fancier features ...
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
It should only affect people with Samsung keyboard docks like the one on the picture above.
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Found the source for sec_keyboard. It's in Platform.tar.gz that comes with the kernel source. I do not have time to look at it now but I sent a PM to pershoot just in case he has not found it (but my guess is that he already has).

Actually it is a really small program:

/*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License as published by
* the Free Software Foundation; either version 2 of the License, or
* (at your option) any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
*
* Should you need to contact me, the author, you can do so either by
* e-mail - mail your message to <vojtech@ucw.cz>, or by paper mail:
* Vojtech Pavlik, Ucitelska 1576, Prague 8, 182 00 Czech Republic
*/

#include <linux/serio.h>
#include <sys/types.h>
#include <sys/stat.h>
#include <sys/ioctl.h>
#include <sys/time.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <fcntl.h>
#include <termios.h>
#include <string.h>
#include <assert.h>
#include <ctype.h>

void setline(int fd, int flags, int speed)
{
struct termios t;

tcgetattr(fd, &t);

t.c_cflag = flags | CREAD | HUPCL | CLOCAL;
t.c_iflag = IGNBRK | IGNPAR;
t.c_oflag = 0;
t.c_lflag = 0;
t.c_cc[VMIN ] = 1;
t.c_cc[VTIME] = 0;

cfsetispeed(&t, speed);
cfsetospeed(&t, speed);

tcsetattr(fd, TCSANOW, &t);
}
struct input_types {
char name[16];
char name2[16];
int speed;
int flags;
unsigned long type;
unsigned long id;
unsigned long extra;
int flush;
int (*init)(int fd, long *id, long *extra);
};

int main(int argc, char **argv)
{
char c = 0;
int ldisc = 0;
int type = 0;
int flags = 0;
int speed = 0;
int fd = 0;
long id = 0;
long extra = 0;
unsigned long devt = 0;
int ret= 0;

flags = CS8;
speed = B9600;
type = 0x3c;

if ((fd = open(argv[1], O_RDWR | O_NOCTTY | O_NONBLOCK)) < 0) {
perror("err : serio attach failure");
return 1;
} else
fprintf(stderr, "%s is opened\n", argv[1]);

setline(fd, flags, speed);

ldisc = N_MOUSE;
ret = ioctl(fd, TIOCSETD, &ldisc);
if(ret) {
fprintf(stderr, "can't set line discipline - %d\n", ret);
return 1;
}

devt = type | (id << 8) | (extra << 16);

if(ioctl(fd, SPIOCSTYPE, &devt)) {
fprintf(stderr, "can't set device type\n");
return 1;
}

while(1) read(fd, NULL, 0);

return 0;
}

I wonder... sec_keyboard is run as "system" but /dev/ttyS0 only allows root to read and write to it. I think we might just need to fix the permissions on /dev/ttyS0
[Galaxy Tab 8.9 Android Development] Der Straßenapotheker:
aarg that would be awful ! I use the dock like my finger when i use the tab ..
[Galaxy Tab 8.9 Android Development] Stamgastje:
Great, thanks! I just installed it and so far it is very responsive and smooth!
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
I cannot test this myself right now but try adding:

/dev/ttyS0 0660 root system

to init.p3.rc
[Galaxy Tab 8.9 Android Development] safariking:
Could you upgrade to 4.1.2?
[Galaxy Tab 8.9 Android Development] jackofspeed:
I can sadly confirm that the keyboard dock pictured does not work with the new build. I had hoped the standard keyboard keys would work, but some of the Samsung specific keys would not. However, no buttons work. Otherwise, running brilliantly!
[Galaxy Tab 8.9 Android Development] pseudoheld:
mate look back one page! cm10 is based on 4.1.2....so this rom is also 4.1.2

i really wish people would read the last few pages before posting questions...:(
[Galaxy Tab 8.9 Android Development] C-o-M:
It is already 4.1.2
[Galaxy Tab 8.9 Android Development] boscorama:
According to that code, it won't get past the initial open of the device if the permissions are wrong. It would simply exit with an error.

It's a strange little program that exists purely to keep the serial device open with the speed, bits and line discipline configured. I wonder if it needs some sort of cpu affinity set for it?
[Galaxy Tab 8.9 Android Development] C-o-M:
Doesn't work, still crashing (and sec_keyboard is running as root, so it really makes no difference)

Can you (or Strassenapotheker please try the following):

Connect to the keyboard dock (not powered!), open Terminal and type the following:

su
/system/bin/sec_keyboard /dev/ttyS0

Now the keyboard dock should work. Then just wait until the screen goes off and let it sleep for a while. Then either it crashes and reboots or we only have the problem while no dock is connected.

---------- Post added at 12:36 AM ---------- Previous post was at 12:17 AM ----------

Originally, that was

* inputattach.c
*
* Copyright (c) 1999-2000 Vojtech Pavlik
*
* Sponsored by SuSE

See for http://packages.debian.org/sid/inputattach for a recent package.
[Galaxy Tab 8.9 Android Development] pseudoheld:
Just reporting back.the latest Version is working great!

Sadly 3g isnt working. Otherwise all is great. Both cams working and all seems smooth
[Galaxy Tab 8.9 Android Development] kosmepe:
I also installed it and it seems that modem is missing. Propably we should install it on top...

Edit: I installed the modem of tracid and still no 3G :(

Anyway, many things are still missing... continue your efforts KK, we are with you :highfive:
[Galaxy Tab 8.9 Android Development] kallt_kaffe:
Pershoot sent me a PM letting me know that the sec_keyboard problem has been fixed. I just got out of bed so I haven't had time to look at yet but I'll try to get some builds ready tonight.
[Galaxy Tab 8.9 Android Development] pseudoheld:
take your time.

i did some more testing with the current rom and appart from the modem not working i couldn't find anything to complain about!

youtube works fine even in HD (something even Samsung ICS had problems with) deepsleep works, hardly any battery drain. really this is a great rom! definately my new daily driver!

is there anything you want me to try out? anything modem related? just let me know!
[Galaxy Tab 8.9 Android Development] C-o-M:
I'll give it a try now. But at least 10 days ago when I did the last builds, his solution broke sdcard.
[Galaxy Tab 8.9 Android Development] Stamgastje:
After some testing yesterday evening and a full charge overnight, I can conclude that the two problems I experienced with the 2.6 kernel (reset on charge, front camera not working) are gone now! Thanks again!

Funny by the way that I now have JB 4.1.2 running on the Tab 8.9, while my Galaxy Nexus phone is still on 4.1.1. :)
[Galaxy Tab 8.9 Android Development] dafnis:
I've been switching from CM9 to CM10 back and forth and now, with both cameras working, I think I'm not going back. The only thing that I find strange is a band that appears at the top of the frames in 720p videos recorded with the tab; in my experience this is not present in CM9.

Glad kk fixed both his car and his tab.

edit: would include a screenshot if I could figure how to make the volume down + power thing work.

---------- Post added at 10:39 AM ---------- Previous post was at 10:32 AM ----------

Agreed.
[Galaxy Tab 8.9 Android Development] C-o-M:
As I said before, pershoot's solution does not work. (OK, maybe it works on encrypted devices, but on nonencrypted devices it's definitely not).

Let's look into some sources to see why:

In his commit, pershoot says:

This is not true. In fact, it does not matter in which way you start sec_keyboard. If it's running, the tab doesn't suspend. The only reason why this change seems to fix the problem is the following. Here is how sec_keyboard get's started:

# serial keyboard daemon
service sec_keyboard /system/bin/sec_keyboard /dev/ttyS0
class late_start
group system

When you look into system/core/rootdir/init.rc, you'll see that there two points where services in class late_start gets started:

on nonencrypted
class_start late_start
...
on property:vold.decrypt=trigger_restart_framework
class_start main
class_start late_start

The first one (on nonencrypted) is called by do_mount_all() in system/core/init/builtins.c when it detects that /data is not encrypted. But do_mount_all is the function that is called when you use fstab:

on fs
mount_all /fstab.p3
setprop ro.crypto.fuse_sdcard true

So going back to ICS mounting method means that nonencrypted never gets triggered.

The other entry point (property:vold.decrypt=trigger_restart_framework) gets fired by cryptfs_restart() in system/vold/cryptfs.c, which is executed by the command "cryptfs restart", which is called by MountService::decryptStorage (in frameworks/base/services/java/com/android/server/MountService.java), which gets executed after you entered the encryption key.

Conclusion: (on nonencrypted devices) late_start services are only executed if you use fstab. So using the ICS mounting method means that sec_keyboard never gets started (and sdcard as well, therefore you don't have externel storage). Thus it obviously cannot prevent the tab from sleeping. But it doesn't solve our problem.

Edit: Nevertheless, I've just ordered a keyboard dock. Might help for debugging.
[Galaxy Tab 8.9 Android Development] pershoot:
good catch. i will fix this up (an oversight on my part).
[Galaxy Tab 8.9 Android Development] pershoot:
ill investigate tty_ldisc a bit more in depth later (was busy getting the other devices up to par), to see of the root cause of this WARN and device death for sec_keyboard.
[Galaxy Tab 8.9 Android Development] pershoot:
just thinking forwardly. if this investigation/rectification takes too long, i could attempt to up-port the method/stack from .36 for sec_keyboard and do away with this daemon.

will keep it on my mind.
[Galaxy Tab 8.9 Android Development] pershoot:
i believe i have this worked around (for now), until a more permanent fix can be put in place. this is similar to the adb root bandage i put in place for .36 where lockups on gadget disconnect would ensue.

i can increase this if need be to attenuate. 100ms worked ok, but i increased it a bit more for device variation.

the warning is still there, but it shouldn't cause device death. ill work towards patching this up, but for the interim this should be ok.

root@ubuntu:/home/root/build/galaxy-31# git diff

diff --git a/drivers/tty/tty_ldisc.c b/drivers/tty/tty_ldisc.c

index a76c808..ce761a9 100644

--- a/drivers/tty/tty_ldisc.c

+++ b/drivers/tty/tty_ldisc.c

@@ -471,6 +471,12 @@ static int tty_ldisc_open(struct tty_struct *tty, struct tt

static void tty_ldisc_close(struct tty_struct *tty, struct tty_ldisc *ld)

{

+ /* Put a sleep here to wait for sec_keyboard disconnect.

+ * WARNING is still present but it shouldn't cause device death.

+ * To be fixed...

+ */

+ msleep(150);

+

WARN_ON(!test_bit(TTY_LDISC_OPEN, &tty->flags));

clear_bit(TTY_LDISC_OPEN, &tty->flags);

if (ld->ops->close)
[Galaxy Tab 8.9 Android Development] C-o-M:
Can you give me a hint where you did those changes?
[Galaxy Tab 8.9 Android Development] pershoot:
which? the temp sleep? its listed in the git diff. in-kernel.

i'd rather not up-port (this is a slippery slope once you start on this journey, as you've seen with all the madness that went on in .36). we should get this perma fixed up on the new sauce.