Running experimental_2 on TR 1.8. Wireless works fine, and can finally overclock again without losing 60MB of space
+1 working great with 1.8! Also updated recovery to .5, thanks so much for everything Zefie - so sorry to see you go.
ARCHIVED: [OC Kernel] Xionia Kernel 2.6.32.33 (v013)
- Thread starter zefie
- Start date
- Status
+1 working great with 1.8! Also updated recovery to .5, thanks so much for everything Zefie - so sorry to see you go.
+1 here too. Working fine and no loss in available space.
Out of curiosity, what do you guys have your settings set to in SetCPU? Min/Max? I'm currently at 844/320 and it seems to be fine. No lag or issues so far, but I can't get a Quadrant score above 596. Is that normal? I've tried several variations in SetCPU but nothing seems to get me higher scores. Is that normal?
Thanks again!
Out of curiosity, what do you guys have your settings set to in SetCPU? Min/Max? I'm currently at 844/320 and it seems to be fine. No lag or issues so far, but I can't get a Quadrant score above 596. Is that normal? I've tried several variations in SetCPU but nothing seems to get me higher scores. Is that normal?
Thanks again!
Last edited:
+1 here too. Working fine and no loss in available space.
Out of curiosity, what do you guys have your settings set to in SetCPU? Min/Max? I'm currently at 844/320 and it seems to be fine. No lag or issues so far, but I can't get a Quadrant score above 596. Is that normal? I've tried several variations in SetCPU but nothing seems to get me higher scores. Is that normal?
Thanks again!
I usally set mine to 245/748 and as for quadrant scores having stage fright enabled boosts it a lot because it glitchs it
Has anyone figured out how to use the Multitouch fix from XDA with this kernel, or at all on the Optimus S?
[DEV][UPDATE: 2-10-11][Optimus One multitouch fixes] - xda-developers
The bug is visible in multitouch games with joysticks, like minigore, krazy kart (with touch control), and most of the fps games. It is interesting to see it with the free app "yet another multitouch tester". Any time your fingers cross axis, the control inverts, so I am playing minigore, running from monsters while shooting them, and all of a sudden I am chasing the monsters and shooting away from them.
[DEV][UPDATE: 2-10-11][Optimus One multitouch fixes] - xda-developers
The bug is visible in multitouch games with joysticks, like minigore, krazy kart (with touch control), and most of the fps games. It is interesting to see it with the free app "yet another multitouch tester". Any time your fingers cross axis, the control inverts, so I am playing minigore, running from monsters while shooting them, and all of a sudden I am chasing the monsters and shooting away from them.
Does the issue still exist in 009? The file in question was completely re-written by LG. It is possible if I patch that, all the "black screen" issues may return.
gonna experiment with this and other things
Last edited:
TR1.8 w/ Xionia 9 Set to 749 with Overclock widget is blazing! I had issues with SetCPU putting my phone into an endless boot cycle. Had to pull battery and boot into recovery and reflash. Figured it was my settings in SetCPU but everytime I tried to configure, it would reboot show the LG splash and then stay on the boot animation. Left it cycling the boot anim for 30 minutes until I decided to pull the battery. Flashed nandroid backup in recovery(wiped data/cache/dalvik/battery/rotation before I flashed again) and installed Overclock widget set to 749 to 806 and it ran very very nicely for a few hours and then reset. Set it to 749 to 749 and have had no reboot issues. For me personally, I was not happy with the performance of TR 1.7 or 1.8 when compared to 1.6. I found them laggy and unresponsive BUT this... this is like taking the condom off!+1 here too. Working fine and no loss in available space.
Out of curiosity, what do you guys have your settings set to in SetCPU? Min/Max? I'm currently at 844/320 and it seems to be fine. No lag or issues so far, but I can't get a Quadrant score above 596. Is that normal? I've tried several variations in SetCPU but nothing seems to get me higher scores. Is that normal?
Thanks again!
It is super sensitive and quick, boots fast as hell, and scrolls super smooth. Any one on the fence... needs to jump in! You'll be happy you did! Just make sure you dont set anything to start on boot until your sure it is stable (wait a few days) or youll be sorry.Merged thunderg patches.. building to test now 
https://github.com/zefie/thunderc_kernel_2.6.32.26/commits/sprint/
https://github.com/zefie/thunderc_kernel_2.6.32.26/commits/sprint/
patched it but it still seems messed up. looks like their patch isn't compatible with the new lcd driver.
gilbequick
Well-known member
- Jul 13, 2010
- 306
- 25
- 0
To run this rom with TR 1.8 so I also need to run the Xionia recovery or will the ThunderRom recovery be ok?
The drivers/initialization for the new LCD came in VC from LG.
Which VC kernel did you use for CWMA 4 custom recovery? Reports from people with the new LCD say the kernel used there works with the new LCD.
Since you had it working there already, it may be quicker to figure out the difference between the CWMA 4 kernel and the kernel you used around that time for CM7. Might be as simple as some build ioption, some initialization routine, or changing some ifdef.
If CWMA 4 was using the stock kernel then ignore what I just said.
New Xionia Kernel/CWMA are all VD drivers not VC. Their patch for inverse made it inverse which makes me wonder if it was fixed my LGE. Please check in 009 if the inverse exists and compare to 010, I'm busy fixing CWMA to work with new NIGHTLY builds
I understand you are *currently* based on VD. What I'm saying is the drivers for the new LCD *first* appeared in VC (and I assume they still remain in VD). The issue I'm talking about is the LCD not displaying at all, not the inverse touchscreen issue.
Also I'm saying people have reported that the kernel included in Xionia CWMA 4 was able to display on the new LCD, so at some point you had it working.
Not expecting any thing to be done right away.
Just trying to be make helpful suggestions *if* one was narrowing down the LCD display issue.
I actually don't even have one of those units so don't have a personal interest nor can I test a fix. I have, however, followed other folks' experiences.
Last edited:
the touchscreen is the lcd driver and it was patched heavily in VC then patched heavily again in VD. Those not having problems with Xionia .5 and 009+ are using VD drivers. cwma .4 is actually not even xionia kernel but stock VC.
Ah, thank you, that completely explains why CWMA .4 is displaying on the new LCDs. I had mistakenly though you had it working in .4 with your custom kernel and just had to figure out what changed.
I'm referring the the LCD "issue" as in the behavior people with the new LCD hardware are seeing with both stock V9 kernels and the kernel you are using in CM7. When they switch back to stock VC or stock VD kernels, the display issue goes away.
The people with the new LCD hardware see the following behavior.
The phone boots fine. There is just no display picture. The touch screen works fine. They can unlock the phone and make phone calls. They just have to do this blindly as there is no picture on their display.
I can't really give more analysis as I don't have one of the new units.
Not expecting any immediate attention (it doesn't even affect me) but would just like to contribute to the discourse in case someone was interested in finding out the root cause of the problem.
So from what I can tell there is no point in using 010 unless you have the new LCD....that correct or were other changes made as well?
It attempts to fix the multitouch axis switch with a workaround. I've been playing around with it and it sorta works. I'm kinda bummed our multitouch sensor is so bad.
Okay, so I have the optimus with the new lcd screen, and I've installed lego rom after getting root on this thing eventually. Now I wanted this kernel for the over clocking capability, however, try as I might, every time I flash the kernel the lcd screen stays blank, though I can feel it working (haptic feedback and whatnot) and I am at a loss as to what to do next... I'd very much appreciate any advice given. Thank you!
- Status
Similar threads
- Locked
Facebook
Twitter
Instagram