Even if he has a VC-based ROM, after he installs the v010 kernel, the LCD display problem will come back. The problem is in the kernel, not the Android portion.
ARCHIVED: [OC Kernel] Xionia Kernel 2.6.32.33 (v013)
- Thread starter zefie
- Start date
- Status
The kernel has the same driver as stock VD that is impossible. I would have to venture a guess it has to do with the ramdisk.
It is easy to test that theory out.
His Lego V2 is VC-based. Prior to installing Xionia Kernel his LCD is displaying picture.
If he installs Xionia Kernel v010 AnyKernel edition, it will take your kernel and use his existing initrd, cmdline, and base.
If there is still an LCD problem, then it must be the kernel, because that is the only thing that changed on an AnyKernel install.
Reinstall Lego.
Boot into Lego/Android, verify the display works.
Boot into recovery.
Install Xionia Kernel v010 AnyKernel edition.
Boot into Lego/Android.
Report whether the display is working.
I have done this with both lego and thunderom now, and lcd has no picture, and I can confirm there is haptic feedback from the screen though there is no visual information, so I know besides the screen, everything is peachy lol.
Thanks Zefie!
Multitouch patch helps quite a bit, still some inversion, but a lot less.
Looks like its faster too, that msleep patch in their touchscreen-driver seemed to help.
Multitouch patch helps quite a bit, still some inversion, but a lot less.
Looks like its faster too, that msleep patch in their touchscreen-driver seemed to help.
As long as you were using the AnyKernel edition to install Xionia Kernel, you have now proved the problem with the LCD not displaying is in the kernel and not anywhere else.
Zefie will need to chime in.
My suspicion is this is either a problem with build configuration, build parameter, ifdef or LG has somehow not given out enough to compile support for the new LCD hardware. There is also a small chance there is a problem with interaction between the initrd and the kernel but the problem definitely is triggered by the kernel change, since that is the only thing changing on an AnyKernel install.
Last edited:
Indeed. Well, until a working Xionia comes about, I very much like ThundeRom, and will enjoy its lone company for now 
Last edited:
I'm not too sure of why this is happening. Which version of recovery are you using? If you are using CWMA .5 you have Xionia 10 and if that works that makes this more interesting.
One test to completely rule out initrd would be to make a nandroid backup and flash the boot.img edition. if it works it will fill up your /data but you can just restore, we just want to see if you have video.
Zefie, as I mentioned before, I don't suffer this problem. I don't have the new LCD hardware. I have just been following other peoples' experiences and doing light analysis into where the problem could be.
Anyway, CWMA .5 uses v010 Xionia kernel and it suffers the same problem of no picture on the new LCD hardware.
As I mentioned earlier, CWMA .4 works with the new LCD hardware and you confirmed to me that it was *not* using Xionia kernel, but the stock VC kernel, so that explains why it was working.
In short, I haven't seen anybody mention that any version of Xionia Kernel (in all its forms, CM7, CWMA, and standalone kernels) works (shows picture) with the new LCD hardware. They all suffer from the same problem problem of everything is completely functional (including touchscreen), except nothing is being displayed.
So CWMA .5 with v010 Xionia kernel and abbreviated recovery initrd = no display
TR1.8/Lego2(VD/VC-based) works with new display. Change out only the kernel and keep original initrd, cmdline, and base = no display.
CM7 with v009 Xionia kernel (presumably VC-based) and full initrd = no display.
It is worth testing v010 bootimage for completeness, but given the above 3 datapoints, I think the chance the display will work with Xionia kernel v010 bootimage version is very very remote.
I do indeed have CWMA .4, as that's the only one that works with the new hardware. I will try the bootimg when I get home from work in about 15-20 minutes, then report in, but I am not optimistic.
Last edited:
Updating Virgin Mobile Xionia Kernel to v10?
Wondering if it is in the works, or even applicable?
Love your kernel, so would love to have the VM version be updated (if applicable).
Thanks for all your hard work.
Wondering if it is in the works, or even applicable?
Love your kernel, so would love to have the VM version be updated (if applicable).
Thanks for all your hard work.
I have no idea what would cause this to happen if the stock VC kernel (CWMA .4) works but the VC driver Xionia (008) does not.
I would need one of these new devices to develop any further. Though even that might not help. >.>
try to get a log from the kernel.
1) Boot android without working LCD
2) in cmd prompt run (without quotes) "adb shell dmesg > dmesg.txt"
3) attach dmesg.txt to post.
I'll get on that, but just for reference, I do have the CWMA .4 recovery, but my phone is VD, not VC. I also used Xionia 010, not 008... should I give that one a try instead?
try the 008 boot edition.
See here are the kernels used:
in CWMA .4 I just compiled what LG released for VC
in CWMA .5 I used Xionia 010.
In Xionia 008, I patched in drivers from the code LG released for VC
in Xionia 009, I overwrote the VC code with VD code
in Xioni 010, I tried those axis patches or whatever mentioned. Which I think made things worse. So try 009 and then 008. If none of them work I just need a dmesg from 010.
okay, sooo 009 and 008 did NOT work, both flashed over fresh ThunderRom 1.8.
So, attached is the dmesg from 010 boot.img and from experimental anykernel edition.
So, attached is the dmesg from 010 boot.img and from experimental anykernel edition.
do you mean from like standard thunderom? That and lego both run fine and I can get a dmesg in about 20 minutes from now.
- Status
Similar threads
- Locked
Trending Posts
-
-
-
-
-
PERMANENTLY disable wifi to switch to mobile data on INFINIX phone
- Started by stonefruit
- Replies: 7
Facebook
Twitter
Instagram