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

[swg0101]

Maybe I am just not used to the colors on the new VC LCD drivers... I think the colors are a little funny even on stock... It just seems like the whites are a little too white (but no big deal... everything still works... also the accelerometer )

 

[zefie]

Maybe I am just not used to the colors on the new VC LCD drivers... I think the colors are a little funny even on stock... It just seems like the whites are a little too white (but no big deal... everything still works... also the accelerometer )

now that you mention it.. its kinda trying to emulate an oled or something lol.

 

[RevolutionRed]

Extracted the boot.img from both the 006 kernel and the VC Rom. I didn't see any ramdisk included in either (seeing if I could get the accelerometer working on the V again by editing the init). Am I missing something? All I get is the kernel.

 

[zefie]

Extracted the boot.img from both the 006 kernel and the VC Rom. I didn't see any ramdisk included in either (seeing if I could get the accelerometer working on the V again by editing the init). Am I missing something? All I get is the kernel.

The ramdisk is lzma compressed instead of gzip compressed so perhaps your utility cannot find it?

Here is a tar of the new initramfs from stock (and xionia 006) and vcrom (custom xionia 006):

http://dl.dropbox.com/u/11516160/Optimus Test Files/LS670ZVC/ramdisks.tar.xz

 

[DoesItMatter]

I've been using stock sprint rom, then used NRom, never used Thunder or any others.

Been running NRom 1.4.5 with Xionia 005 kernel - no issues.

Upgraded to Xionia 006 kernel - wiped cache and dalvik just in case

DID NOT wipe data

Rebooted - phone works - no issues other than the Dalvik-Cache -> Cache no longer works.

Not a really big issue for me, but it looks like it worked first time.

 

[zefie]

I've been using stock sprint rom, then used NRom, never used Thunder or any others.

Been running NRom 1.4.5 with Xionia 005 kernel - no issues.

Upgraded to Xionia 006 kernel - wiped cache and dalvik just in case

DID NOT wipe data

Rebooted - phone works - no issues other than the Dalvik-Cache -> Cache no longer works.

Not a really big issue for me, but it looks like it worked first time.

flash the boot.img from VCRom and you should have dalvik to /cache again. Xionia uses a stock initrd now.

 

[cordell]

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.

The only real benefit to DarkTremor over native Froyo a2sd is the partitions the apps are stored on. The native Froyo a2sd stores apps in a special folder on your FAT32 partition on your sd card and has to go through some form of encryption/decryption to make it work (how I understand it). Darktremor a2sd script uses native Linux partitions to store the apps, our phones (android) are a form of linux. It also uses symbolic links (native to Linux) to redirect the files to the SD card, thus making the apps run smoother/faster. Some prefer native Froyo and that is fine, theres more than one way to skin a cat

 

[DoesItMatter]

flash the boot.img from VCRom and you should have dalvik to /cache again. Xionia uses a stock initrd now.

How do I do this?

I been trying - can't just flash the boot.img in a zip file

Any tips?

 

[zefie]

How do I do this?

I been trying - can't just flash the boot.img in a zip file

Any tips?

adb reboot recovery
adb push boot.img /
adb shell flash_image boot /boot.img
adb shell reboot

 

[DoesItMatter]

adb reboot recovery
adb push boot.img /
adb shell flash_image boot /boot.img
adb shell reboot

Tried flashing both of your VC Rom 003 and 004 boot.img files

No luck unfortunately - maybe some incompatibility with NRom?

Edlt: No luck activating the Dalvik-Cache -> Cache move

The adb commands work just fine

 

[zefie]

Tried flashing both of your VC Rom 003 and 004 boot.img files

No luck unfortunately - maybe some incompatibility with NRom?

Probably
look at system\etc\zefie.sh and system\etc\mkdalvik.sh in my vcrom zip.

try putting them in your system\etc\

 

[DoesItMatter]

Probably
look at system\etc\zefie.sh and system\etc\mkdalvik.sh in my vcrom zip.

try putting them in your system\etc\

W00T-Ness!

That did it...

So, to summarize

1) Flash Xionia 006 update

2) ADB flash the boot.img file from VC Rom 004 or 005

3) Copy the 2 files - zefie.sh and mkdalvik.sh from VC Rom 004 or 005 to \system\etc

4) Manually wipe any /cache/dalvik-cache and /data/dalvik-cache folders - then reboot

5) Profit!

Now... I don't see a bit of difference myself, between Xionia 005 and Xionia 006

Main Rom is still running NRom 1.4.5 which was an upgrade from Sprint Stock

Still running the V9 Radio

All in all - great learning experience, but not sure what I accomplished!

Fun Stuff!

Edit: Tools Used:

1) The Mind... tis a terrible thing!

2) Java Developer Kit build 23

3) Latest Android tools developer kit (tools module only)

4) Recovery 1.2.0 ( 1.1.0 should also work )

5) Root Explorer 2.13.x

 

[DoesItMatter]

Zefie - got a question

I did a nandroid backup with your 006 kernel, and then tried to do
a restore... and that did not go so good.

First restore - the dots kept filling up the screen for like 10 minutes,
so I knew something was wrong.

2nd time I did the restore, it only did a few dots then said to run

'nandroid-install.sh restore' from ADB

I did that, and it would not recognize the nandroid backup done with Xionia 006

Not a big deal, I just reverted to my backup before I flashed Xionia 006.

Informational Alert - my phone is still working.

 

[zefie]

Zefie - got a question

I did a nandroid backup with your 006 kernel, and then tried to do
a restore... and that did not go so good.

First restore - the dots kept filling up the screen for like 10 minutes,
so I knew something was wrong.

2nd time I did the restore, it only did a few dots then said to run

'nandroid-install.sh restore' from ADB

I did that, and it would not recognize the nandroid backup done with Xionia 006

Not a big deal, I just reverted to my backup before I flashed Xionia 006.

Informational Alert - my phone is still working.

Sounds like your sd card is going bad and some of the backup got lost.

Nandroid is run in the recovery kernel, which I don't have one of yet, so Xionia cannot be at fault there.

 

[farfromuman]

Zefie - got a question

I did a nandroid backup with your 006 kernel, and then tried to do
a restore... and that did not go so good.

First restore - the dots kept filling up the screen for like 10 minutes,
so I knew something was wrong.

2nd time I did the restore, it only did a few dots then said to run

'nandroid-install.sh restore' from ADB

I did that, and it would not recognize the nandroid backup done with Xionia 006

Not a big deal, I just reverted to my backup before I flashed Xionia 006.

Informational Alert - my phone is still working.

Low battery will set this off as well, try it with the phone plugged in to the charger.

 

[japn]

hi. im kind of technically deficient if you know what i mean, so im having some trouble finding this out: i was wondering if with ksmithinny's and beezy's thunderom 1.6.2 ROM for the LG optimus s i could use your 007 (or newest) kernel? sorry if the question's weirdly worded.....

thanks

 

[zefie]

hi. im kind of technically deficient if you know what i mean, so im having some trouble finding this out: i was wondering if with ksmithinny's and beezy's thunderom 1.6.2 ROM for the LG optimus s i could use your 007 (or newest) kernel? sorry if the question's weirdly worded.....

thanks

You can try. Just make a nandroid backup first

 

[japn]

same on S

zefie,

On the V the accelerometer doesn't work the latest build of Xionia, but does work with the beezy's kernel from Thunderom 1.6.2. I searched through the thread to see if this had been mentioned as a problem the S, but didn't see anything (sorry if I missed it). Since the hardware is identical, this seems strange. Have you verified that the accelerometer works with 005 on the S? And if so, any ideas why it wouldn't work on the V?

Subjectively, Xionia is faster and more responsive than beezy on the V, especially with regards to touchsreen lag, so I'd like to run Xionia if possible. I have no hard data to back this up, so it may be my imagination. Beezy's is still way ahead of the stock build and it's pretty amazing what you both have done, so thanks to you both.


UPDATE: Xionia works correctly if you do a clean wipe (EVERYTHING data, cache, etc.) and use the stock VM rom. So, it's not kernel related. Ignore this post.

i have the optimus s and it doesn't work on mine either. i was freaking out that something happened to my phone......

 

[zefie]

i have the optimus s and it doesn't work on mine either. i was freaking out that something happened to my phone......

it still doesnt work for you guys on 07? weird it works for me.. VC radio tho

 

[scifan]

it still doesnt work for you guys on 07? weird it works for me.. VC radio tho

I won't mess with this since I'm still working with your VC rom...

Sometimes when I see a flowchart for troubleshooting I think of this one.