Sirkay, just want to report that if we flashes your kernel, we should flash doomlord superuser package again. It seems that because of superuser problem, samba filesharing (which I use) won't successfully release its wakelock. It's better to keep superuser separated from kernel but keep the recovery intact.
sent from my white ray using XDA App
Want to be careful here - until this one we've all been running kernels that mask superuser-mode busybox mount etc with kernel version.
If you get issues from that, it's because busybox in the ROM is at fault, you've just never been able to use it before. But now, binary upgrades will actually stick.
If love to hear from an Android kernel guru if the path is the optimal way of avoiding binary masking.
Want to be careful here - until this one we've all been running kernels that mask superuser-mode busybox mount etc with kernel version.
If you get issues from that, it's because busybox in the ROM is at fault, you've just never been able to use it before. But now, binary upgrades will actually stick.
If love to hear from an Android kernel guru if the path is the optimal way of avoiding binary masking.
Umm after flashing sirkay kernel, still got the busybox from busybox installer though (still names 1.19.4-STericsson and no duplicates. the problematic one is superuser. First when i ran TB, it gives me a warning about permission issue. I don't know how Samba works, but it seems like Samba server (or Wifi driver) is not working correctly (wakelocking) with flawed superuser. Don't know why but now wakelock problem seems more problematic than before after flashing this kernel, so my suspicion is based on superuser issue.
That's DooMLoRD's autoroot.sh script, which intrusively messes with superuser binary.
I don't like the script myself, but you should ask DooMLoRD why its doing what its doing.
Its also setting permissions wrong:
Code:
26 /sbin/busybox chmod 4755 /system/xbin/su
As you know from TB, should be 6755.
Perhaps we need updated script.
Personally I'd prefer for kernel not to mess about with my superuser, but that's just me, its sirkay's kernel. But IMO the script is for using kernel on unrooted SEMC ROMs, not our custom ones.
Yes, but after flashing the ROM, I updated busybox to 1.19.4 and booted into
the ROM...updated SU to v3.1 and then booted into recovery and flashed the
adreno drivers from arcatarc. Not sure if you need the busybox or the adreno
drivers, there is a busybox in KA08 and I didn't see the adreno drivers in the
changelog.
BUT....you really will want the SU update....especially if you are going to run the
V6supercharger script....or even TB for that matter.
That's DooMLoRD's autoroot.sh script, which intrusively messes with superuser binary.
I don't like the script myself, but you should ask DooMLoRD why its doing what its doing.
Its also setting permissions wrong:
Code:
26 /sbin/busybox chmod 4755 /system/xbin/su
As you know from TB, should be 6755.
Perhaps we need updated script.
Personally I'd prefer for kernel not to mess about with my superuser, but that's just me, its sirkay's kernel. But IMO the script is for using kernel on unrooted SEMC ROMs, not our custom ones.
Yes. that's why i prefer kernel with recovery as such, and keep superuser package as additional download.
Yes. that's why i prefer kernel with recovery as such, and keep superuser package as additional download.
Agreed.
Well, the kernel only kind of doesn't come with superuser.
It doesn't have su in /sbin, which is good, but it does have that unnecessary script, since we're using it on custom roms. Again, I can see why DooMLoRD would package it on kernels for stock ROMs, but that's just not our usage case here.
*cough* should really pull it from /sbin, remove it from init.rc, and clean out its files while we're at it. *cough*
Well, the kernel only kind of doesn't come with superuser.
It doesn't have su in /sbin, which is good, but it does have that unnecessary script, since we're using it on custom roms. Again, I can see why DooMLoRD would package it on kernels for stock ROMs, but that's just not our usage case here.
*cough* should really pull it from /sbin, remove it from init.rc, and clean out its files while we're at it. *cough*
*pokes sirkay*
as per request, ive uploaded kernel with autoroot disabled. not yet update the link. will do when get home
Not too long ago, we talked about how Sony was continuing its AOSP efforts on … more
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?
Introducing XDA:DevCon – A Conference For Developers By Developers
>
[xKERNEL|ICS&JB|27/11] xKernel v9.587-D | another version that not released
Print
Email
View Profile
View Forum Posts
View Facebook page
Visit Homepage
Follow on Twitter
as per request, ive uploaded kernel with autoroot disabled. not yet update the link. will do when get home
Linear Mode
