02-22-2012 04:40 PM
155 1234 ...
tools
  1. twistedpc's Avatar
    Accelerometer doesn't seem to be working with the browser
    04-16-2011 09:50 PM
  2. drezliok's Avatar
    How does this new Kernel compare with Xionia kernels?
    04-17-2011 12:11 AM
  3. picasticks's Avatar
    How does this new Kernel compare with Xionia kernels?
    This gets discussed in the thread for the S version of the kernel. Zefie has a rec on page 7 to go with this kernel for LG-based ROMs and Xionia for Cyanogen-based ROMs. Which also makes sense to me, so I put it in the top post.

    The project goal is "stable with high performance" and compatibility with the LG kernel and OS. So, less experimental and smaller than Xionia.
    04-17-2011 01:45 AM
  4. BiafraRepublic's Avatar
    I'm gonna give this a try now... Anyone try and use this with aospCMod?

    Sent from my LG Optimus V using Tapatalk
    04-17-2011 01:50 AM
  5. picasticks's Avatar
    Accelerometer doesn't seem to be working with the browser
    If you think this is related to the kernel, please provide full info including ROM, cpufreq governor and max clock rate, and steps to recreate the problem (what you were doing and what happened).

    Just reread the thread and saw you're running AOSP ... see top post, the kernel is recommended and only "officially" supported for LG-based ROMs, not Cyanogen. You're welcome to post more info here but you will not be getting any attention from the developer, sorry.
    04-17-2011 01:50 AM
  6. drezliok's Avatar
    Cool, smaller could run cleaner?

    I'm having issues so I am going to give this a try... RIGHT NOW!!! lol

    First boot
    Rodimus Rom's Boot Animation works now!!!! It's very pretty, lol.

    My Button's got swapped.

    Second Boot
    Boot Animation starts slow, then speeds up then BOOM Into the phone, AKA FAST BOOT!! Way faster.
    04-17-2011 01:51 AM
  7. drezliok's Avatar
    I was using Xionia 013, before this, and so how do I fix my swapped buttons lol.

    Flashed mmarz fix from his thread

    http://forum.androidcentral.com/opti...13-2011-a.html

    And it didn't work.
    04-17-2011 02:14 AM
  8. picasticks's Avatar
    I was using Xionia 013, before this, and so how do I fix my swapped buttons lol.

    Flashed mmarz fix from his thread

    http://forum.androidcentral.com/opti...13-2011-a.html
    See obijohn's post back a page or two ... he posted the original thunder_keypad.kl which you can put back on your phone to restore the original button mapping. My kernel is built from VM source so no button-swap is necessary, unfortunately lots of people have already swapped their buttons!

    Anyway I am going to put out a version that puts the original thunder_keypad.kl back in place, but it won't be out for another day or two.
    drezliok likes this.
    04-17-2011 02:51 AM
  9. drezliok's Avatar
    See obijohn's post back a page or two ... he posted the original thunder_keypad.kl which you can put back on your phone to restore the original button mapping. My kernel is built from VM source so no button-swap is necessary, unfortunately lots of people have already swapped their buttons!

    Anyway I am going to put out a version that puts the original thunder_keypad.kl back in place, but it won't be out for another day or two.
    I'm tried to flash it. No Signature.

    not too sure as to how to get it to where it needs to be and I am up past my bed time. My kids will be up in 4 to 5 hours and I need my sleep.
    04-17-2011 03:07 AM
  10. LeslieAnn's Avatar
    I'm tried to flash it. No Signature.

    not too sure as to how to get it to where it needs to be and I am up past my bed time. My kids will be up in 4 to 5 hours and I need my sleep.
    In recovery where you flash the zip, disable signature check, it should work then.
    drezliok likes this.
    04-17-2011 03:12 AM
  11. drezliok's Avatar
    Good thing I decided to refresh before going to bed.

    Damn... FAILED


    *****
    Another post lol, don't want to spam.

    I can overclock alot more now too but I will do further testing later.
    04-17-2011 03:16 AM
  12. drezliok's Avatar
    Accelerometer doesn't seem to be working with the browser
    Mine stopped all together.
    04-17-2011 03:53 AM
  13. twistedpc's Avatar
    Mine stopped all together.
    Yea same here. Noticed it right before I went to bed.
    04-17-2011 09:45 AM
  14. drezliok's Avatar
    Reflashed RodimusRom, my accelerometer works just fine now. The button swap is still here but I will live with it, this kernel is very smooth and faster. My benchmarks are not as good as Xionia but real time use faster and more stable.
    04-17-2011 10:25 AM
  15. obijohn's Avatar
    I'm tried to flash it. No Signature.

    not too sure as to how to get it to where it needs to be and I am up past my bed time. My kids will be up in 4 to 5 hours and I need my sleep.
    That's not a flashable zip. Just unzip it to get the thunder_keypad.kl file (I couldn't attach the .kl file directly since that's not a recognized attachment extension by the board). Remount /system as rw, then put it in /system/usr/keylayout/.
    picasticks and drezliok like this.
    04-17-2011 02:13 PM
  16. drezliok's Avatar
    SetCPU Force Closes if I try to make any adjustments.
    04-18-2011 12:26 AM
  17. picasticks's Avatar
    SetCPU Force Closes if I try to make any adjustments.
    Well, that's definitely weird. Does it show 748 MHz and ondemand when you first start it? If not, what?

    Can you just change scaling to "performance" or does even that kill it?

    My guess would be this is an incompatibility with the ROM. I don't have a V so don't run Rodimus but just looking at the feature list it mentions "Screenstate scaling added (written by flohimself. this removes the need to have a SetCPU profile for screen-off. saves battery)" and "Fixed processor staying at 100%". So if they are doing things to the scaling on boot it may be something that SetCPU doesn't like. Or they may be changing things that are Xionia-specific. If you could, what is in your init.qcom.post_boot.sh file?

    (The next question I would ask is for you to cat out the contents of all the files in /sys/devices/system/cpu/cpu0/cpufreq after the phone boots, if you know how to do that (together it would show the full cpufreq configuration post-boot). If not then hopefully I'll get the info from the other questions.)
    04-18-2011 12:58 AM
  18. drezliok's Avatar
    That's not a flashable zip. Just unzip it to get the thunder_keypad.kl file (I couldn't attach the .kl file directly since that's not a recognized attachment extension by the board). Remount /system as rw, then put it in /system/usr/keylayout/.
    Learned how to adb... RomTools is nice but I should have learned it to do it right from scratch anyways. but I got my buttons fix up and I'm happy.
    04-18-2011 01:09 AM
  19. drezliok's Avatar
    Well, that's definitely weird. Does it show 748 MHz and ondemand when you first start it? If not, what?

    Can you just change scaling to "performance" or does even that kill it?

    My guess would be this is an incompatibility with the ROM. I don't have a V so don't run Rodimus but just looking at the feature list it mentions "Screenstate scaling added (written by flohimself. this removes the need to have a SetCPU profile for screen-off. saves battery)" and "Fixed processor staying at 100%". So if they are doing things to the scaling on boot it may be something that SetCPU doesn't like. Or they may be changing things that are Xionia-specific. If you could, what is in your init.qcom.post_boot.sh file?

    (The next question I would ask is for you to cat out the contents of all the files in /sys/devices/system/cpu/cpu0/cpufreq after the phone boots, if you know how to do that (together it would show the full cpufreq configuration post-boot). If not then hopefully I'll get the info from the other questions.)
    It does boot at 748 MHz but it says interactive. If I try to do anything other than look at it it FC on me. Scale up or down, min or max, change the governor, and also mess with the sampling. I've tried to reset the program by clearing it's data. I've wiped my cache and Dalvik to see if that worked. Nothing!

    I have a idea though. It worked before I put the theme on it which I when installing it I wiped the Dalvik and Cache.
    04-18-2011 01:17 AM
  20. picasticks's Avatar
    It does boot at 748 MHz but it says interactive. If I try to do anything other than look at it it FC on me. Scale up or down, min or max, change the governor, and also mess with the sampling. I've tried to reset the program by clearing it's data. I've wiped my cache and Dalvik to see if that worked. Nothing!

    I have a idea though. It worked before I put the theme on it which I when installing it I wiped the Dalvik and Cache.
    Thanks, that is already helpful. Since it is interactive, which is not standard, that already tells us the ROM is making changes via the cpufreq interface. If you do "adb pull /init.qcom.post_boot.sh" you can get that file, hopefully it's making the changes in there (you will see it is cat-ing a bunch of values to /sys/devices/system/cpu/cpu0/cpufreq). Please post if you can, it's only like 20 lines.

    Or if the other thing makes the problem go away, that's good too. As far as I can guess this isn't a kernel bug anyway. (>200 downloads at this point and most of them probably by people using SetCPU ).
    04-18-2011 01:57 AM
  21. mmarz's Avatar
    Well, that's definitely weird. Does it show 748 MHz and ondemand when you first start it? If not, what?

    Can you just change scaling to "performance" or does even that kill it?

    My guess would be this is an incompatibility with the ROM. I don't have a V so don't run Rodimus but just looking at the feature list it mentions "Screenstate scaling added (written by flohimself. this removes the need to have a SetCPU profile for screen-off. saves battery)" and "Fixed processor staying at 100%". So if they are doing things to the scaling on boot it may be something that SetCPU doesn't like. Or they may be changing things that are Xionia-specific. If you could, what is in your init.qcom.post_boot.sh file?

    (The next question I would ask is for you to cat out the contents of all the files in /sys/devices/system/cpu/cpu0/cpufreq after the phone boots, if you know how to do that (together it would show the full cpufreq configuration post-boot). If not then hopefully I'll get the info from the other questions.)
    I was worried about that too, the "Screenstate scaling", because of the testing I did that showed underclocking hurting performance. You can find the original script mark used here: [INITSCRIPT] screenstate_scaling - switch CPU freq governor on screen state change - xda-developers

    But it was dropped from Rodimus in the later releases. I'm not sure if it is an accidental omission or it was left out on purpose because the change log does not state when it was removed. Either way, it shouldn't be an issue with the latest Rodimus.
    04-18-2011 01:58 AM
  22. drezliok's Avatar
    Thanks, that is already helpful. Since it is interactive, which is not standard, that already tells us the ROM is making changes via the cpufreq interface. If you do "adb pull /init.qcom.post_boot.sh" you can get that file, hopefully it's making the changes in there (you will see it is cat-ing a bunch of values to /sys/devices/system/cpu/cpu0/cpufreq). Please post if you can, it's only like 20 lines.

    Or if the other thing makes the problem go away, that's good too. As far as I can guess this isn't a kernel bug anyway. (>200 downloads at this point and most of them probably by people using SetCPU ).
    I think this bug was on me.

    I pushed the apk from Romtools. Took me a while to dig it out of there. tried the cmd adb way but finally resorted to a "root uninstaller" from the market. wiped my dalvik and then reinstalled from my SDcard and it works fine.
    04-18-2011 02:27 AM
  23. picasticks's Avatar
    I was worried about that too, the "Screenstate scaling", because of the testing I did that showed underclocking hurting performance. You can find the original script mark used here: [INITSCRIPT] screenstate_scaling - switch CPU freq governor on screen state change - xda-developers

    But it was dropped from Rodimus in the later releases. I'm not sure if it is an accidental omission or it was left out on purpose because the change log does not state when it was removed. Either way, it shouldn't be an issue with the latest Rodimus.
    Thanks for the info!

    I think every kernel/ROM dev (me included) has to relearn these same lessons re: frequency and voltage scaling. This post sums up the situation pretty well:

    UV & UC to save battery isn't really feastible as all freq 245mhz to 480mhz use same voltage on any msm7x27 processor (less than 245mhz is too slow for the phone to wake up for calls etc.) 600+ uses the max voltage. Max voltage is level 7 on this processor and voltage level of 3 is the minimum the phone can use to be operational. Voltage levels 3-6 have the same output so no savings there.
    Nevertheless people keep clocking down to 122 and rediscovering that it doesn't work.

    People need to read up on the MSM7600 chipset and realize this is an older (when I pulled the datasheet it, was (c) 2006) SoC design, that is a phone-specific cpu from Qualcomm, and some of the things that are possible with the general-purpose ARM cpus that are in most higher-end devices are not with the MSM7627, because stuff like voltage levels is hardwired in (and we can't just port some HAVS patch HTC wrote for a different chipset). Or, put another way, some things are "possible" (i.e. clocking from 480 or 245 down to 122) but there's no benefit and/or bad side effects.

    The good news is that there are some easy wins, like overclocking, disabling features, enabling JIT or reducing the wifi poll interval to save battery.

    I have gone through, built and tested 10x the number of kernel config changes, CFLAGS (fpu-related) and patchsets that I have actually wound up putting into this kernel, and with almost all of it there was either no testable improvement or (usually) a regression of some kind. LG has done a really solid job on the kernel (especially where it really matters for performance, in the cpu-specific MSM arch sections) which I'm sure comes from years of working with this chipset.

    And the community has been hacking on it for a long time, too.
    04-18-2011 11:38 AM
  24. jmel's Avatar
    That's not a flashable zip. Just unzip it to get the thunder_keypad.kl file (I couldn't attach the .kl file directly since that's not a recognized attachment extension by the board). Remount /system as rw, then put it in /system/usr/keylayout/.
    This would be great if someone could make it into a flashable zip...
    04-18-2011 12:19 PM
  25. Eollie's Avatar
    This would be great if someone could make it into a flashable zip...
    Yes lets make everything super easy and flashable so, oh I dunno, it takes no knowledge of how or where to put things via root navigation or adb push commands.
    04-18-2011 12:24 PM
155 1234 ...

Tags for this Thread

LINK TO POST COPIED TO CLIPBOARD