ARCHIVED: [OC Kernel] Xionia Kernel 2.6.32.33 (v013)

[zefie]

After installing 013_bootimage on a stock ZVD ROM, mounting USB seems to be slightly broken.

Steps to replicate

1) connect USB to computer
2) select "USB connected" from notification drawer
3) press "Turn on USB Storage" button
4) press "OK"
5) observe that SD card is mounted on computer as expected

Unexpected behavior

1) Android USB icon on phone screen remains green
2) notification that "SD card safe to remove" displayed in notification drawer
3) after unmounting SD card from computer, it must be manually remounted in phone via Settings->SD card and Phone Storage

Note, observed on a Mac...I will update later with results of same test on windows.

Thanks for the great kernel, recovery, and CM7 port...I ain't *****ing, just thought you would like to know.

i noticed that and was wondering if it was just me. strange. something from the upgrade to 2.6.32.33 must have done it. kinda afraid to mess with it though because the performance increase is kinda worth the weirdness lol

 

[00_wrath_00]

Iagree if its fixed cool if not its not a big deal the performance is worth it awsome job

 

[zefie]

i am trying to figure out what caused it but no luck so far.

 

[deathangel1496]

Hey Zefie, just felt like thanking you for finally resolving that blank screen issue, I havent been able OC my optimus because every kernal didnt havve the updated drivers in it. now with me running cwma, thundeROM, and this kernal, my phone feels like a completely new phone, im playing toon warz at atleast 25fps, any tips you can give to maximize my phones performance?

 

[bigsupersquid]

v013 works great on my Optimus V so far. Although after flashing it yesterday my woman got an MMS from me which only came through with the subject and no content (was long text-msg plus subject, only the subject was delivered)... repeated that again today with a short text-msg+subject with the same result. However, media attachments send fine, and all the text comes through with those, including subject. Not griping or anything, just mentioning a possible bug (bet it's in the CM7 not the kernel, though, since out-MMS still works as long as there is a media attachment.) I think v009 sent text+subject MMS ok, but I'm not sure... I'll test that later.
Thanks for the work!
<edit> ok, I'll test it on the stock ROM to verify, and add an edit to this post with the results. Sorry for the misplaced post. I did try to say I thought it was a CM7 bug not the kernel... Since I never had this issue until yesterday after flashing v013, I thought I'd mention it here.
I mostly just wanted to post that v013 seems to work fine on my V, and say thanks tons for all the work, zefie.
<edit again> ooh, stock-rooted-and-optimized ROM did not mix well with this kernel for me. Wouldn't boot past the android logo. Bricked my phone with the LG-style factory reset in xionia-CWMA into a reboot loop when I was thinking something stupid. Kinda fixed the device where it at least starts up again but I have to use a different recovery to backup/restore and then use the CWMA recovery to get the phone to boot. I'll have more time to play in a couple hours, then I'll test v013 with one of the other ROMS you mentioned. Hopefully I'm not spamming your thread too bad here.
<last edit> ok, my bad. the issue I posted is probably ROM-based, definitely not in the v13 kernel.
Works great with RevolutionRed's XioniaVM.zip. Profuse apologies for posting all this in the wrong place

 

[zefie]

v013 works great on my Optimus V so far. Although after flashing it yesterday my woman got an MMS from me which only came through with the subject and no content (was long text-msg plus subject, only the subject was delivered)... repeated that again today with a short text-msg+subject with the same result. However, media attachments send fine, and all the text comes through with those, including subject. Not griping or anything, just mentioning a possible bug (bet it's in the CM7 not the kernel, though, since out-MMS still works as long as there is a media attachment.) I think v009 sent text+subject MMS ok, but I'm not sure... I'll test that later.
Thanks for the work!

for the sake of whatever sanity is left in me can we plz keep CM7 bugs in the CM7 thread and if anything is even thought to be a kernel bug please test it on ThundeROM, nROM, Stock, or some other stable LGE-based ROM.

With that said I had no problem donating another $10 yesterday to the Red Cross using v013. Therefore both 90999 and myself were able to see each other's messages. I use ThundeROM.

Not trying to be mean or anything just sayin'

 

[gilbequick]

I use ThundeROM.

Have you found a certain version of the Xionia Kernel to work better with ThunderROM 1.8 than another? I'm really missing the OC ability in 1.8.

 

[zefie]

Have you found a certain version of the Xionia Kernel to work better with ThunderROM 1.8 than another? I'm really missing the OC ability in 1.8.

I use my latest of course.

 

[jstntp]

Have you found a certain version of the Xionia Kernel to work better with ThunderROM 1.8 than another? I'm really missing the OC ability in 1.8.

I'm running v013 with ThundeROM 1.8.2 Runs good and fast. Thanks again zefie.

 

[gilbequick]

Can I just flash this over top of what I have or do I need to wipe anything first?

What's the difference between the "boot.img edition" and the "Experimental AnyKernel Edition?

 

[omarnova]

Can I just flash this over top of what I have or do I need to wipe anything first?

What's the difference between the "boot.img edition" and the "Experimental AnyKernel Edition?

^^^^^ i have this same question im about to flash right now just waiting on the answer

 

[sfhub]

boot.img is xionia kernel+initrd+cmdline+base

anykernel takes xionia kernel and combines it with your existing initrd+cmdline+base.

In practical terms, use boot.img for stock ROM. For recent custom ROMs you are safer using anykernel or you could lose space if dalvik-cache gets moved back to /data

 

[omarnova]

boot.img is xionia kernel+initrd+cmdline+base

anykernel takes xionia kernel and combines it with your existing initrd+cmdline+base.

In practical terms, use boot.img for stock ROM. For recent custom ROMs you are safer using anykernel or you could lose space if dalvik-cache gets moved back to /data

thanks

 

[bigsupersquid]

Ok, I just wanted to mention...
v13 AnyKernel edition doesn't reverse the home/menu buttons on my V! I thought that this was an S-specific kernel and that those had an internal setting which swapped part of the keymap. does the AnyKernel edition dodge that issue somehow?
P.S. sorry about the misdirected post earlier. I've added corrections and more info as edits.

 

[mth411]

Zefie -
Any chance on remerging the multitouch patch again, it was lost in the rebase to VD.

xda-developers - View Single Post - [DEV][UPDATE: 2-10-11][Optimus One multitouch fixes]

Even just the msleep in the touchscreen driver would be nice, as without it my cpu seems to spike to 90% just for touchscreen, making GunsNGlory really hard

 

[gilbequick]

^^^^^ i have this same question im about to flash right now just waiting on the answer

Flashed with no wiping, working great thus far.

 

[zefie]

Zefie -
Any chance on remerging the multitouch patch again, it was lost in the rebase to VD.

xda-developers - View Single Post - [DEV][UPDATE: 2-10-11][Optimus One multitouch fixes]

Even just the msleep in the touchscreen driver would be nice, as without it my cpu seems to spike to 90% just for touchscreen, making GunsNGlory really hard

the multitouch patch does not work. I downloaded an multitouch test app and with and without the patch for v013 the dots always ended up on the opposite side of my fingers during a tricky pinch/twist. I'm assuming this is what you all mean.

As for the msleep I believe LGE patched this themselves in VD.

Ok, I just wanted to mention...
v13 AnyKernel edition doesn't reverse the home/menu buttons on my V! I thought that this was an S-specific kernel and that those had an internal setting which swapped part of the keymap. does the AnyKernel edition dodge that issue somehow?
P.S. sorry about the misdirected post earlier. I've added corrections and more info as edits.

Being as I completely trashed the old source and started clean from VD perhaps LGE has some sort of check for your model. Which is interesting if they are sharing kernels.

 

[Dassin]

the multitouch patch does not work.

It worked for me in v10 anykernel as long as I only crossed the axis one time (in the same direction). If I crossed it twice, it would invert as usual.

 

[hamagc]

Didn't seem to work for me either. First time they crossed they inverted.

Sent from my LS670 using Tapatalk

 

[sd_matto]

Ok, I just wanted to mention...
v13 AnyKernel edition doesn't reverse the home/menu buttons on my V! I thought that this was an S-specific kernel and that those had an internal setting which swapped part of the keymap. does the AnyKernel edition dodge that issue somehow?
P.S. sorry about the misdirected post earlier. I've added corrections and more info as edits.

Actually, v13 AnyKernel edition DOES reverse the home/menu buttons on my V! Just flashed it (and confirmed buttons reversed). I did a straight flash to a rooted stock (pure stock from store, NOT RevolutionRed's stock which has fix for reversed home/menu built into ROM, and which would mask a kernel-only button reversal). I wonder if the stock which is installed on your phone is RevolutionRed's stock (your prior post suggests that it might be, since you refer to XioniaVM (i.e., RevolutionRed's name for his based-on-stock ROM which has the key reversal fix))??

Which brings me back to an earlier question for Zefie in this thread: Any chance we will see some v13 love for the Optimus V (i.e., an updated to your Xionia goodies in the Optimus V thread). Would LOVE both an updated kernel (based on v13) and an updated CWMA recovery (based on v.6). Thanks in advance for an answer, Zefie.