[KERNEL][exp: (3.1.10) #5] Firtecy Kernel - a modified Kowalski Kernel

How much Ramhack do you want to have?

  • No ramhack at all

    Votes: 25 15.9%
  • 16MB ramhack

    Votes: 12 7.6%
  • 24MB ramhack

    Votes: 16 10.2%
  • 32Mb ramhack

    Votes: 104 66.2%

  • Total voters
    157
Search This thread

Firtecy

Senior Member
Feb 14, 2013
123
1,124
I might have to correct you at this point, undervolting is not dangerous, it just makes your phone unstable but that won't hurt the hardware.
Also AFAIR from reading the datasheets the cpu voltage regulator can't go lower than 750mV so pengus77 set the limit there.

Thanks for the reminder about the dangerous term. I will correct it ;)
Can you please give a link to the datasheet or pengus77 answer where he stated, that there is no way to go lower than 750 mV. I did not found any restriction in the kernel and I think that in deep sleep the voltage will be even lower, but I might be wrong.
I will check the service manual again when I am back at home.

Gesendet von meinem LG-P990 mit Tapatalk
 

sev3n1985

Senior Member
Sep 4, 2013
276
464
Milano
Thanks for the reminder about the dangerous term. I will correct it ;)
Can you please give a link to the datasheet or pengus77 answer where he stated, that there is no way to go lower than 750 mV. I did not found any restriction in the kernel and I think that in deep sleep the voltage will be even lower, but I might be wrong.
I will check the service manual again when I am back at home.

Gesendet von meinem LG-P990 mit Tapatalk

Here the datasheet for tegra 2 TRM

http://iam.tj/media/notion-ink/adam/Tegra2_Interface_Design_Guidelines_DG05379001.pdf
 

Firtecy

Senior Member
Feb 14, 2013
123
1,124

Thanks for the data sheet, that will help a lot!

Here a quote out of the data sheet (from page 13)
  • ....
  • VDD_CPU adjustments from 1.0V down to 0.75V or lower
  • Adjustments should be in 25mV to 50mV increments
  • ....
And previously it was stated: "CPU voltage (VDD_CPU)"

For me that seems like it is possible to go lower than 0.75V. But it can be that the regulator used in the phone can not handle lower voltages, but i did not find any datasheets. The regulator used is the MAX8907C (See page 48 of the servoce manual for p990)
 

sudden36

Senior Member
Mar 5, 2013
223
308
According to page 48 the actual cpu core voltage is generated by the MAX8952, which makes sense because this is the rail with the most power drawn. The datasheet says 770mV to 1,4V in 10mV steps.
Of course it may be possible to set it lower, but the IC might not really set it or it could be unstable.
 

Firtecy

Senior Member
Feb 14, 2013
123
1,124
According to page 48 the actual cpu core voltage is generated by the MAX8952, which makes sense because this is the rail with the most power drawn. The datasheet says 770mV to 1,4V in 10mV steps.
Of course it may be possible to set it lower, but the IC might not really set it or it could be unstable.

Okay thanks :) You guys seems to have more luck when finding data sheets :D
Just take a look at this file and line:
https://github.com/Firtecy/kowalski/blob/exp/drivers/regulator/max8952r.c#L20

It seems like pengus77 introduced that one: https://github.com/Firtecy/kowalski/commit/a4e0768655b0cc73c4a87db6c278c6db36644aec . Before there was 77 as default value and I think that refers to the 770 mV. So that would mean it is not possible to go under 770 mV and all support for lower should be removed
 

sudden36

Senior Member
Mar 5, 2013
223
308
Okay thanks :) You guys seems to have more luck when finding data sheets :D
Just take a look at this file and line:
https://github.com/Firtecy/kowalski/blob/exp/drivers/regulator/max8952r.c#L20

It seems like pengus77 introduced that one: https://github.com/Firtecy/kowalski/commit/a4e0768655b0cc73c4a87db6c278c6db36644aec . Before there was 77 as default value and I think that refers to the 770 mV. So that would mean it is not possible to go under 770 mV and all support for lower should be removed

Jup I think max8952_set_voltage even checks for values <77 and limits them as far as I can tell.
 

Firtecy

Senior Member
Feb 14, 2013
123
1,124
So no uv under 750 or 770?default value for 216mhz is 750mv isn't?

Sent from my LG-P990

There is no undervolting under 770 mV, all lower values will not be applied to the hardware ;) I will change that in the next kernel release, so that those misleading values are removed ;)

Gesendet von meinem ASUS Transformer Pad TF700T mit Tapatalk
 
Last edited:

ivaneris

Senior Member
Apr 3, 2012
1,174
260
Blora
@Firtecy
I found this strange behaviour
gydedepa.jpg

I set min @216mhz but the device still goes to 120mhz...and i got can't wake bug before (need to pull iut battery),i make a logcat but i'm not sure if it'll help because i pull out batttery:(

Sent from my LG-P990
 

Firtecy

Senior Member
Feb 14, 2013
123
1,124
I set min @216mhz but the device still goes to 120mhz...and i got can't wake bug before (need to pull iut battery),i make a logcat but i'm not sure if it'll help because i pull out batttery:(

Sent from my LG-P990

I will take a look at that issue soon.
The "can't wake bug", does that happend after the phone was in deep sleep? And to answer the question, yes you should always provide a kmsg and if possible the last_kmsg ;)
 

Firtecy

Senior Member
Feb 14, 2013
123
1,124
Experimental Kernel version 3!
firtecy_kernel_exp-3 - 13.6.2014
Changelog:
  • tons of updates to zram/zcache (picked from faux123 tegra kernels)
  • crypto: added optimized AES and SHA1 routines
  • added permission checker for binder IPC
  • tegra video driver updates
  • Fixed the voltage table -> all values below 770 MHz are not supported by the regulator chip (thanks to all who helped researching! :) )

If you have any feature requests or wishes you can just post them in here and i will take a look at that ;) I will then write all wishes + my opinion on those into the second post ;)

Downloads as always at baskedbuild:
-> Option to use: No ramhack, 16Mb Ramhack or 32 Mb Ramhack!
https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/

Source at github:
https://github.com/Firtecy/kowalski
 

ivaneris

Senior Member
Apr 3, 2012
1,174
260
Blora
I think can't wake bug related to lockscreen...i disable lockscreen and no problem...just downloaded latest exp will flash it asap...

Sent from my LG-P990
 

lukino993

Senior Member
Nov 25, 2012
398
229
Syracuse
I have reboots with #3 kernel 32 MB rh maybe because i have dirty flashed last cm11 build?if i revert to #2 32 rh all is ok..

Inviato dal mio LG-P990 utilizzando Tapatalk
 
  • Like
Reactions: Mhden2x

Firtecy

Senior Member
Feb 14, 2013
123
1,124
I have reboots with #3 kernel 32 MB rh maybe because i have dirty flashed last cm11 build?if i revert to #2 32 rh all is ok..

Inviato dal mio LG-P990 utilizzando Tapatalk
Okay, but i need some additional information:
Do you have a last_kmsg?
Did you see the pink lg logo?
Did you change any values? So which values are not default?

If you don't have a last_kmsg (taken right after the reboot!) there is no real possibility to fix this issue, because then I have to guess what is causing the problems ^^
That means it would be very helpful, if you can give me a last_kmsg ;)

Gesendet von meinem LG-P990 mit Tapatalk
 

ivaneris

Senior Member
Apr 3, 2012
1,174
260
Blora
No prob for new kernel so far...but i set min 216 but it still goes to 120...strange...btw what's the advantage using 168/120mhz now that is the same 770mv like 216?

Sent from my LG-P990

---------- Post added at 09:53 AM ---------- Previous post was at 09:04 AM ----------

Got sod with exp 3,no uv,216-1000mhz,need to pull battery https://mega.co.nz/#!oAgRnRAZ!3-tnxq_Ff5ygg6eOlpzaYF0Ax-IhxwzP5JdAMZxn-24 here my last kmesg
----------------
Got twice reboot (the 2nd stuck at lg bootlogo) can't provide last kmsg...it's empty :(
Back to exp1 for now...most stable for me

Sent from my LG-P990
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 52
    This is an EXPERIMENTAL Kernel that continues the work of @pengus77, but with some additions i make. That means a huge thank to pengus77! Please check his thread http://xdaforums.com/showthread.php?t=2097788
    This kernel is completely based on his latest release.

    This kernel only supports newbl and will only work on roms with 3.1 support (these are atm only 4.4 (aka KitKat) Roms and tonyps TheRom that is compatible with the 3.1 kernel

    Features:
    Features from the kowalski kernel:
    • 3.1.10 Kernel Version
    • bcmdhd wifi driver
    • Dynamic FSync
    • Overclock to 1.5 GHz (Not all phones work well with 1.5 Ghz!)
    • Undervolting
    • MultiCore Sched PM
    • Auto Hotplug
    • Fast charge
    • Wifi PM
    • and many more ...
    Features added by me:
    • PKSM as enhanced KSM module
    • Built in ZRAM Modul (that makes it possible to use the android default zram solution)
    • Possibility to use deferred_timer for (P)KSM
    • 0, 16 or 32 MB Ramhack
    • Support for extra free kbytes tunable (more a ROM dev feature)
    • Custom vibration force/strength through sysfs
    • 120MHz and 168 MHz frequencies for more battery savings during wakelock

    Known bugs:
    • Camera Bug
    • Gyro does not work properly
    If you want to report a new kernel bug, you must describe your problem in detail, post your kmsg and last_kmsg (if available) (you can found them under /proc/kmsg and /proc/last_kmsg) otherwise the rule is: no log = no issue

    Downloads:
    This is more a personal kernel build. I have built these kernels for weeks for myself and used them in private. Now i just want to share them with you guys!

    You can download the kernels here: https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/ They are labeled like this: firtecy_kernel_X-N.zip where X is either exp for an experimental kernel release and stable for a stable kernel and where N is the build number (this number is always incremental!)

    Sourcecode:
    You can find the sourcecode at github: https://github.com/Firtecy/kowalski/ the branch is exp. The config file is: "kowalski_defconfig"

    The intention of this thread is to continue the 3.1 kernel development pengus started. Development related questions or discussions are appreciated
    Have fun!

    And to quote pengus77:
    On a side note... i'm not really responsible if you decide to test it and your phone melts... right?
    Thanks to:
    @hjunii for bringing up 3.1 Kernel
    @pengus77 for the kowalski kernel

    XDA:DevDB Information
    Firtecy Kernel - a modified Kowalski Kernel, Kernel for the LG Optimus 2x

    Contributors
    Firtecy, pengus77, hjunii, djnoxd
    Kernel Special Features:

    Version Information
    Status: Beta
    Current Beta Version: 3.1#5
    Beta Release Date: 2014-08-25

    Created 2014-10-31
    Last Updated 2014-10-31
    33
    Since I assume you're the only kernel dev left here I'll ask you....
    Is it possible to have the I2C clockrate reduced like its done now on the HH?
    Its from code aurora so I think it might be possible. It more or less doubles the battery life of devices with little to no effort at all, without sacrificing performance!
    Here's one of the Dev's G+ https://plus.google.com/app/basic/stream/z13rixbparibybpbe04cervoqxekxndb1us0k

    And I can prove it works. my HammerHead gets at most 4hour SOT and now I get 6 hours SOT without tweaking anything! I can get 7-8 if I can lower my usage!

    EDIT/PLUS:
    I hopefully its made for both the platforms (both AOSP KK & LG STOCK) because for odd reasons the LG Stock is much more smoother on my device...
    This sounds promising, I will take a look into that for the next release! :) Thanks for that info, I appreciate information like that and it really helps me with the developing.

    But for now: I do not have that much time to spend hours on kernel developing so I will release my current kernel base.

    Experimental Kernel version 5!
    firtecy_kernel_exp-5 - 25.8.2014
    • Added intellactive governor (thanks to @faux123) and powersave
    • Some bug fixes
    • Added sync framework and exfat support (but not active for the moment)
    • Added a "kowalski touch driver" and dt2w files (since they are not stable enough for now, they are disabled)
    The reason why I disabled those things is that I didn't had the time to test them. If you want to test them you have to build your own version. Especially for other developers that can be interesting.

    Downloads as always at baskedbuild:
    https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/

    Source at github:
    https://github.com/Firtecy/kowalski

    Status of double tap to wake:
    -It works but only for as long as the phone does not enter deep sleep
    -If I try to set an irq for the touch driver, those get reset and the phone won't wake up
    -I have tried at some point to reduce the cpu freq to 8MHz during screen off and to disable everything else, but that was still too much battery drain
    -Even if i disable lp1 or lp2 still the phone won't wake up.
    I think i have to research a bit more to find a working solution

    If anyone has some ideas I would be pleased to hear them.
    30
    Experimental Kernel version 3!
    firtecy_kernel_exp-3 - 13.6.2014
    Changelog:
    • tons of updates to zram/zcache (picked from faux123 tegra kernels)
    • crypto: added optimized AES and SHA1 routines
    • added permission checker for binder IPC
    • tegra video driver updates
    • Fixed the voltage table -> all values below 770 MHz are not supported by the regulator chip (thanks to all who helped researching! :) )

    If you have any feature requests or wishes you can just post them in here and i will take a look at that ;) I will then write all wishes + my opinion on those into the second post ;)

    Downloads as always at baskedbuild:
    -> Option to use: No ramhack, 16Mb Ramhack or 32 Mb Ramhack!
    https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/

    Source at github:
    https://github.com/Firtecy/kowalski
    29
    Experimental Kernel version 2!
    firtecy_kernel_exp-2 - 8.6.2014
    Changelog:
    • Added the possibility to change the vibration force (or vibration strength)
    • Added 120MHz and 168MHz as cpu frequencies
    • Enabled 600 mV as lowest undervolting value (undervolting can lead to instabilities Better stay at defaults)
    • Fixed a nvidia or lg cpu derp.
    • For security reasons it is not possible that the cpu will go underneath 216MHz when screen is on!
    • Option to use: No ramhack, 16Mb Ramhack or 32 Mb Ramhack!

    Vibration force:
    to change the vibration force echo a number between 0 and 127 to /sys/module/tspdrv/parameters/vibration_force. Where 127 is the highest and the default. 20 seems to be the last noticeable value.
    Code:
    echo [force] > /sys/module/tspdrv/parameters/vibration_force
    This option does not stick after a reboot. Rom support will be available (hopefully) soon. I'm preparing a patch for tonyps Rom, so that it is possible to change it in the Rom settings.

    120 and 168Mhz:
    These values are useful for the case where the phone helds a wake lock. This means because of the wake lock it won't enter deepsleep. The phone would run at 216MHz even if it isn't needed. Running at 168Mhz or even 120MHz should result in a better battery life.
    If you experience any problems, try to raise the voltage at this frequencies to a higher value and test again. If it is still unstable report it (with a description of the problem) and change the minimum frequency to 216Mhz.

    Downloads as always at baskedbuild:
    https://s.basketbuild.com/devs/firtecy/p990/kernel/3.1/

    Source at github:
    https://github.com/Firtecy/kowalski
    25
    The linaro gcc 4.9.1 version seems to work at least as good as the normal flirtecy 3.1.10 #5 kernel. It's much smaller, it might be faster when booting.
    It is basically smaller since my kernel control app is not included, but it should give some improvements because of the newer toolchain.
    What about the battery with the double tap 2 wake? Seems promising [emoji106]


    Sent from my LG-P990 using XDA Free mobile app
    Since it doesn't work properly it shouldn't make a difference ;) But I'm searching for a solution that works and doesn't consume much battery.


    On a side note: At the moment I have much spare time left and have because of that I can spend more time on the kernel than in the month before. :)

    Gesendet von meinem LG-D855