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

Status
Not open for further replies.
New 006 sends me into bootloops, coming from Lego. Tried nandroid and fresh flash and same thing, looped. Actually its not looping, its more of a freeze, the boot animation used to freeze when it reached its end but now the whole phone freezes.
 
New 006 sends me into bootloops, coming from Lego. Tried nandroid and fresh flash and same thing, looped. Actually its not looping, its more of a freeze, the boot animation used to freeze when it reached its end but now the whole phone freezes.

Delete your boot animation they are not compatible with the new graphics driver. (blame lg)

The bootanimation is failing a memcpy routine for the gpu. It spams the hell out of adb logcat and would presumably crash a weak system.
 
Delete your boot animation they are not compatible with the new graphics driver. (blame lg)

The bootanimation is failing a memcpy routine for the gpu. It spams the hell out of adb logcat and would presumably crash a weak system.

now it boot loops, I deleted the animation and stock animation is there but boot looping, on lego, Optimus S.

Logcat is filled with error like this...

C:\android-sdk-windows\platform-tools>D/dalvikvm( 1589): GC_FOR_MALLOC freed 796
7 objects / 482616 bytes in 42ms
'D' is not recognized as an internal or external command,
operable program or batch file.

C:\android-sdk-windows\platform-tools>E/AmitDaemon( 1191): [AMI304D] AMI304MID_I
OCTL_GET_CONTROL error
'E' is not recognized as an internal or external command,
operable program or batch file.
 
now it boot loops, I deleted the animation and stock animation is there but boot looping, on lego, Optimus S.

Logcat is filled with error like this...

C:\android-sdk-windows\platform-tools>D/dalvikvm( 1589): GC_FOR_MALLOC freed 796
7 objects / 482616 bytes in 42ms
'D' is not recognized as an internal or external command,
operable program or batch file.

C:\android-sdk-windows\platform-tools>E/AmitDaemon( 1191): [AMI304D] AMI304MID_I
OCTL_GET_CONTROL error
'E' is not recognized as an internal or external command,
operable program or batch file.

and you are clearing /data?
 
Have not tried clearing /data, but on the new one I'm having the same issue - I'm now down to 672kb of space.

Custom boot animation also worked on the first version that I downloaded (or at least, the phone was able to finish booting), this one would not boot with it like you said.

Going to do a /data clear and see what happens to my storage space :P

EDIT: Only have 121mb after clearing /data, which is odd. Tried restoring apps that I'd backed up with Titanium backup and ran out of space... but by the time I checked I had hit 12mb. Rebooted, I was at 18.6, now it's slowly climbing (18.71 right now)

Double checked and the apps I'd had saved to the SD card are correctly being moved to the SD card with Titanium upon restore, so I should be able to restore all of them unless this kernel chances something... heck, actually, even without the dalvik to cache mod I should still have been able to restore everything since I had 60mb free.

Ran through my remaining backups and could install some more apps... then I ran out of space again, but had 13mb free when I checked.

Gave up on that, and tested out the auto rotate function - does not work.

EDIT 3: http://www.mediafire.com/?eyd476xtcd62cna <- Logcat after rebooting the device from all that. Tried to get one after running everything, but aLogcat was having issues responding, and my phone kept disconnecting from adb (I think that's a Windows issue, not an issue with your kernel though)
 
Last edited:
To clarify, or at least on my phone, it is the sensor that is not functioning. Forced landscape is still there (Angry Birds).

Also the boot animation worked fine (loops through animation until home screen appears) on my phone, even after flashing version 006.

Reverted to version 005
 
Clearing data as in a wipe of the phone, if so than no. I have wiped cache and dalvik, running DarkTremors a2sd so I don't wanna reset that up. I did try a reflash of the script after kernel to restore any script files that may have been deleted.

Sent from my LS670 using Tapatalk
 
Clearing data as in a wipe of the phone, if so than no. I have wiped cache and dalvik, running DarkTremors a2sd so I don't wanna reset that up. I did try a reflash of the script after kernel to restore any script files that may have been deleted.

Sent from my LS670 using Tapatalk

You're going to want to get rid of DarkTremors a2sd, its known to kill SD Cards in the Optimus S.
 
You're going to want to get rid of DarkTremors a2sd, its known to kill SD Cards in the Optimus S.

Thats what I heard but I been running it for about 2 months now with no issues, knock on wood! I am using a pretty good card, also a class 6. In fact its the same one that I used for my Hero, also running DarkTremors a2sd. I know the issue is only with the LG not with all phones, so far so good though :)
 
Accelerometer no longer functioning on 006. Also about a 50MB drop in storage space on phone. Going back to 005 for the time being until those issues are handled.

- Not complaining, I appreciate the work being done on this phone; just stating my findings.

EDIT: Going back to 005 does not fix accelerometer issue. Still non-functioning.

EDIT 2: Doing a Nandroid restore to time before kernel change resolved the accelerometer issue. I'll just wait patiently until a revision is made. Thanks in advance, Zefie.
 
Last edited:
Thats what I heard but I been running it for about 2 months now with no issues, knock on wood! I am using a pretty good card, also a class 6. In fact its the same one that I used for my Hero, also running DarkTremors a2sd. I know the issue is only with the LG not with all phones, so far so good though :)

Beezy killed a class 10 card on his Optimus S :(
 
The new 006 has accelerometer fixed, or should, maybe something is caching the old one.

As for a2sd I ever officially nor will I officially support it as it is pointless in Froyo. Even apps that you can't move to SD card be forced there from an ADB command and still usually work great. App2SD was all the rage in Cupcake and Donut but is unnecessary here.

As for /data I have no idea without reverting my phone back to V9 radio to investigate it (then subsequently dealing with VC's BS again to work on VCRom).

I'm having no problem with 006 in VCRom. If you are having troubles please revert to 005 as there are no changes besides the VC Drivers, which may be causing all your trouble.
 
zefie,

006 works on the V, but still has the same problem as before with the accelerometer. Additionally, the phone occasionally stalls on boot (looking at the logs, it has something to do with wifi.. will let you know more details as I have them), requiring a battery pull to reset it. Then it starts up fine. Also, VPN does not appear to work. I've tried connecting to both my work network, and set one up at home, neither of which worked. I'm going through now and double checking everything.
 
zefie,
I did also have troubles after updating my phone using LG Update (V9 to VC), and using a nandroid to go back to my original settings (since everything was messed up after the update). Things after the nandroid update were still messed up (hands free activation, etc) - Flashing your v6 kernel made it worse with low storage space warning... only thing that fixed it was a Titanium Backup + reflash with VCRom - things seems to be working okay now, although I think the screen's colors are still a little weird... At least the phone works now.
 
zefie,
I did also have troubles after updating my phone using LG Update (V9 to VC), and using a nandroid to go back to my original settings (since everything was messed up after the update). Things after the nandroid update were still messed up (hands free activation, etc) - Flashing your v6 kernel made it worse with low storage space warning... only thing that fixed it was a Titanium Backup + reflash with VCRom - things seems to be working okay now, although I think the screen's colors are still a little weird... At least the phone works now.

Yeah, you have two choices. follow my restore to stock guide and when you update to V9, stop, and you will be able to use your nandroid backup again since you will be on V9 Radio

or

Stick with VCRom :P
 
It was really weird... After the LG update - although I lost root, custom recovery seems to be unaffected (it wasn't the stock LG recovery as expected)... After the update the baseband and SW ver was VC, then I tried nandroiding back to my saved state (since everything was messed up) - Baseband went back to V8, with SW version staying at VC (stuff was still messed up though, like handsfree activation)

Nothing really works to get the phone back to a working state, except flashing to VCRom in custom recovery, which I did VCRom + Deluxe Prop + Gingerbread Theme all at once w/ Wipe data, cache, dalvik... then Titanium restore... works great so far, except the colors are still a little bit overexposed (not too bad though) - thanks for the ROM!

Anyways - are you planning to incorporate the changes that are made in LEGO/ThundeROM in your VC ROM? I miss the features like "improved memory management" and all those battery tweaks! :)
Thanks.
 
It was really weird... After the LG update - although I lost root, custom recovery seems to be unaffected (it wasn't the stock LG recovery as expected)... After the update the baseband and SW ver was VC, then I tried nandroiding back to my saved state (since everything was messed up) - Baseband went back to V8, with SW version staying at VC (stuff was still messed up though, like handsfree activation)

Nothing really works to get the phone back to a working state, except flashing to VCRom in custom recovery, which I did VCRom + Deluxe Prop + Gingerbread Theme all at once w/ Wipe data, cache, dalvik... then Titanium restore... works great so far, except the colors are still a little bit overexposed (not too bad though) - thanks for the ROM!

Anyways - are you planning to incorporate the changes that are made in LEGO/ThundeROM in your VC ROM? I miss the features like "improved memory management" and all those battery tweaks! :)
Thanks.

If they expose what those tweaks are sure. lol. I don't know what tweaks they did.

Colors shouldn't be messed up but you are already going outside the norm by applying a theme from lego rom, now your framework-res and services.jar are from V9, mixed with VCRom's VC which may be causing your problems. Not sure. Colors are fine for me, I noticed no difference before or after the stock upgrade. And VCRom is just a rooted deodex'd stock right now.
 
Is there a file I can DL that could have gotten wiped causing my screen not to auto rotate? Not complaining one bit these things are part of the territory. Just wanting to DL that file to fix it if there is one.
 
Is there a file I can DL that could have gotten wiped causing my screen not to auto rotate? Not complaining one bit these things are part of the territory. Just wanting to DL that file to fix it if there is one.

No if the new 006 is not working it probably will not work outside of VC, not sure.

Please restore your nandroid backup and retain 005 for the time being.
 
  • Like
Reactions: jmzsctt
Status
Not open for further replies.

Trending Posts

Forum statistics

Threads
956,961
Messages
6,970,812
Members
3,163,673
Latest member
fergie