[KERNEL][14 OCT] [P93x|SU640][OC/UV][3.0.100] Wind Kernel [ICS|JB]

[mattman86]

I've noticed that after a few hours, my max is set back to 1566. Anybody else having that problem?

 

[lyfkevin]

Re: [KERNEL][12 FEB] [P93x|SU640][OC/UV][3.0.62] Wind_Kernel [ICS|JB]

I promised it wont be laggy. :]

By Sensation developer, mpdecision bug was fixed by setting min voltage to 800mV:what:.
This approach sacrificed the UV feature, so I didnt use. Temporily dun set min freq to 192Mhz. Everything is fun.

Sent from my LG-SU640 using xda app-developers app

-----------------------------------------------------------------------------------------------------------
EDIT:
192Mhz bug is not caused by this kernel.
It's CM bug.
I just updated to latest CM10.1 nightly with CM kernel. Got this problem too

 

[lyfkevin]

Re: [KERNEL][12 FEB] [P93x|SU640][OC/UV][3.0.62] Wind_Kernel [ICS|JB]

I've noticed that after a few hours, my max is set back to 1566. Anybody else having that problem?

http://forum.xda-developers.com/showpost.php?p=37634427&postcount=991

I will check by overclocking above 1566Mhz.
It might be caused by intellidemand setting. Try to set LMF max freq same as cpu max freq.
You can also set it via Kernel Tuner

Sent from my LG-SU640 using xda app-developers app

 

[chatnever]

@lyfkevin thanks for your Kernel, I'm currently using Wind Kernel 3.0 for Stock ROM. Very fast speed and long life battery.

When cm10.1 stable is released, I'll have a try with your cm10.1 kernel.

Btw, are you Chinese/Taiwanese? I want to say "Happy snake year!" to you

 

[lyfkevin]

@lyfkevin thanks for your Kernel, I'm currently using Wind Kernel 3.0 for Stock ROM. Very fast speed and long life battery.

When cm10.1 stable is released, I'll have a try with your cm10.1 kernel.

Btw, are you Chinese/Taiwanese? I want to say "Happy snake year!" to you

Thx for your encouragement. I just merged other developers' great works into our device kernel. Credits should belong to them.
If you guys found useful features (Governors& I/O Scheduler etc) from other devices, suggest it and I will try to add.

Happy Snake Year too! I am from Hong Kong, a small city in China. :fingers-crossed:

 

[mohitomish]

This kernel has elevated the nitro to whole new level!!!!! Thanks a lot buddy

 

[kenship]

Thx for your encouragement. I just merged other developers' great works into our device kernel. Credits should belong to them.
If you guys found useful features (Governors& I/O Scheduler etc) from other devices, suggest it and I will try to add.

Happy Snake Year too! I am from Hong Kong, a small city in China. :fingers-crossed:

Good to see dev. ppl from HK! I left there probably before you were born LOL!

Let me share a bit of my experience in using this kernel: I'm switching in between stock (v20f), CM10.1 and Quattrimus CM10.1

No problem at all with v20f, nothing to say about it

CM10.1 - fast, fast, fast and smooth, but battery drain is insane

Quattrimus CM10.1 - as fast as CM10.1 but somehow battery life is excellent (as good as stock with wind kernel). BUT for some reason LTE doesn't work for me at all (as a toggle or as network mode) in Canada, hope there will be some improvement on this, plus GPS doesn't work at all.

So I'm still stuck in stock...wonder if CM10.1 can resolve the battery drain problem or Quattrimus can resolve the LTE and GPS problem.

 

[just1nsama]

Good to see dev. ppl from HK! I left there probably before you were born LOL!

Let me share a bit of my experience in using this kernel: I'm switching in between stock (v20f), CM10.1 and Quattrimus CM10.1

No problem at all with v20f, nothing to say about it

CM10.1 - fast, fast, fast and smooth, but battery drain is insane

Quattrimus CM10.1 - as fast as CM10.1 but somehow battery life is excellent (as good as stock with wind kernel). BUT for some reason LTE doesn't work for me at all (as a toggle or as network mode) in Canada, hope there will be some improvement on this, plus GPS doesn't work at all.

So I'm still stuck in stock...wonder if CM10.1 can resolve the battery drain problem or Quattrimus can resolve the LTE and GPS problem.

I have the same problem with LTE in Canada with CM10.1, but i toggle it off anyways because of battery drain, in CM10 it would drop 10% per hour with LTE on. Might be a problem with Canada users ..

 

[kenship]

I have the same problem with LTE in Canada with CM10.1, but i toggle it off anyways because of battery drain, in CM10 it would drop 10% per hour with LTE on. Might be a problem with Canada users ..

I think I tested it w/o LTE, still draining like crazy. So with my experience in using Quattrimus could it be that the failure of LTE is actually a blessing to battery life? I have the same battery issue with HyperSonic 10

 

[radhames562]

original xda post
move to this for better mangement
bbs.gfan.com

disclaimer

*
 * your warranty is now void.
 *
 * i am not responsible for bricked devices, dead sd cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this rom
 * before flashing it! You are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, i will laugh at you. Hard. A lot.
 */

device support

• su640 (i_skt)
• p930 (i_atnt)

features

• based on lg stock ics kernel source(ics version)
• based on latest cm10.1 kernel source(jb version)
• latest linux kernel 3.0.y source
• cpu [email protected] max clock 1.94ghz (not all device can handle 1.94ghz)
• gpu [email protected]_320mhz 2d 266mhz
• undervolting support(700mv-1450mv)
• l2 performace boost
• integrated init.d (by ryuinferno)
• smooth as butter :]
• some tweaks, fixes
• and something i missed (discover it ! )

View attachment 1708354

installation instruction

1. copy *.zip to external sd card
2. boot into recovery mode
3. flash *.zip
4. reboot and enjoy it!

optional

• nandroid backup before flash
• wipe cache/dalvikcache,fix permission after flash

hi

please help me every time i try to instal this kernel the phone boot but a few seconds later it reboots and that happens again and again

im using cm10.1

i try to instal liquid nitro v6 that include this kernel and im doing a clean install what im doing wrong?

 

[lyfkevin]

hi

please help me every time i try to instal this kernel the phone boot but a few seconds later it reboots and that happens again and again

im using cm10.1

i try to instal liquid nitro v6 that include this kernel and im doing a clean install what im doing wrong?

Check reply #34
http://forum.xda-developers.com/showpost.php?p=37745058&postcount=34

 

[miji2]

Check reply #34
http://forum.xda-developers.com/showpost.php?p=37745058&postcount=34

Same situation here. I have one of those flaky P930 which is fine in Gingerbread but really suffers from BSODs and reboots under ICS or greater. In general, CM10.1 is quite stable actually. And when I say stable, I mean random reboots are kept to under 2 to 3 per day and only sporadic BSODs. Flashing the 1.1 Wind kernel on top of Feb 10 CM10.1 nightly just makes this phone freak out like a lunatic. Uptime of about 1 minute. That being said, commenting out the voltage table override in the init script fixes the immediate stability issue.

 

[lyfkevin]

Same situation here. I have one of those flaky P930 which is fine in Gingerbread but really suffers from BSODs and reboots under ICS or greater. In general, CM10.1 is quite stable actually. And when I say stable, I mean random reboots are kept to under 2 to 3 per day and only sporadic BSODs. Flashing the 1.1 Wind kernel on top of Feb 10 CM10.1 nightly just makes this phone freak out like a lunatic. Uptime of about 1 minute. That being said, commenting out the voltage table override in the init script fixes the immediate stability issue.

（LGSU640(Optimus LTE)_Andorid_ICS_SU640v20d\SU640_ICS_Kernel\kernel\arch\arm\mach-msm\acpuclock-8x60.c)

/* SCPLL frequencies = 2 * 27 MHz * L_VAL */
static struct clkctl_acpu_speed acpu_freq_tbl_slowest[] = {
  { {1, 1},  192000,  ACPU_PLL_8, 3, 1, 0, 0,    L2(1),   800000, 0x03006000},
  /* MAX_AXI row is used to source CPU cores and L2 from the AFAB clock. */
  { {0, 0},  MAX_AXI, ACPU_AFAB,  1, 0, 0, 0,    L2(0),   825000, 0x03006000},
  { {1, 1},  384000,  ACPU_PLL_8, 3, 0, 0, 0,    L2(1),   825000, 0x03006000},
  { {1, 1},  432000,  ACPU_SCPLL, 0, 0, 1, 0x08, L2(1),   850000, 0x03006000},
  { {1, 1},  486000,  ACPU_SCPLL, 0, 0, 1, 0x09, L2(2),   850000, 0x03006000},
  { {1, 1},  540000,  ACPU_SCPLL, 0, 0, 1, 0x0A, L2(3),   875000, 0x03006000},
  { {1, 1},  594000,  ACPU_SCPLL, 0, 0, 1, 0x0B, L2(4),   875000, 0x03006000},
  { {1, 1},  648000,  ACPU_SCPLL, 0, 0, 1, 0x0C, L2(5),   900000, 0x03006000},
  { {1, 1},  702000,  ACPU_SCPLL, 0, 0, 1, 0x0D, L2(6),   900000, 0x03006000},
  { {1, 1},  756000,  ACPU_SCPLL, 0, 0, 1, 0x0E, L2(7),   925000, 0x03006000},
  { {1, 1},  810000,  ACPU_SCPLL, 0, 0, 1, 0x0F, L2(8),   975000, 0x03006000},
  { {1, 1},  864000,  ACPU_SCPLL, 0, 0, 1, 0x10, L2(9),   975000, 0x03006000},
  { {1, 1},  918000,  ACPU_SCPLL, 0, 0, 1, 0x11, L2(10), 1000000, 0x03006000},
  { {1, 1},  972000,  ACPU_SCPLL, 0, 0, 1, 0x12, L2(11), 1025000, 0x03006000},
  { {1, 1}, 1026000,  ACPU_SCPLL, 0, 0, 1, 0x13, L2(12), 1025000, 0x03006000},
  { {1, 1}, 1080000,  ACPU_SCPLL, 0, 0, 1, 0x14, L2(13), 1050000, 0x03006000},
  { {1, 1}, 1134000,  ACPU_SCPLL, 0, 0, 1, 0x15, L2(14), 1075000, 0x03006000},
  { {1, 1}, 1188000,  ACPU_SCPLL, 0, 0, 1, 0x16, L2(15), 1100000, 0x03006000},
  { {1, 1}, 1242000,  ACPU_SCPLL, 0, 0, 1, 0x17, L2(16), 1125000, 0x03006000},
  { {1, 1}, 1296000,  ACPU_SCPLL, 0, 0, 1, 0x18, L2(17), 1150000, 0x03006000},
  { {1, 1}, 1350000,  ACPU_SCPLL, 0, 0, 1, 0x19, L2(18), 1175000, 0x03006000},
  { {1, 1}, 1404000,  ACPU_SCPLL, 0, 0, 1, 0x1A, L2(19), 1200000, 0x03006000},
  { {1, 1}, 1458000,  ACPU_SCPLL, 0, 0, 1, 0x1B, L2(19), 1225000, 0x03006000},
  { {1, 1}, 1512000,  ACPU_SCPLL, 0, 0, 1, 0x1C, L2(19), 1250000, 0x03006000},
  { {1, 1}, 1566000,  ACPU_SCPLL, 0, 0, 1, 0x1D, L2(19), 1275000, 0x03006000},
  { {1, 1}, 1620000,  ACPU_SCPLL, 0, 0, 1, 0x1E, L2(19), 1300000, 0x03006000},
  { {1, 1}, 1674000,  ACPU_SCPLL, 0, 0, 1, 0x1F, L2(19), 1325000, 0x03006000},
  { {0, 0}, 0 },
};

Here is the LG stock voltage table, u still found instability, try setting voltage according to this table

 

[miji2]

Here is the LG stock voltage table, u still found instability, try setting voltage according to this table

Haha .. I was just about to start messing with that. Thanks!

 

[miji2]

Here is the LG stock voltage table, u still found instability, try setting voltage according to this table

So I've looked at several samples across versions. And wow ... it's fascinating to see how the voltage table changed from version to version. Gingerbread had higher voltage up until about 1GHz, then ICS had higher voltage above that frequency. JB is lower than ICS. Combine that with bad silicone, this may explain why I'd get kernel faults. For my crazy device, I've combined those from GB with those in ICS, to create the worst-of-both-worlds battery-punisher voltage table (attached here). Battery life aside, let's see how much this enhances stability on top of all the other fixes you kindly included in your kernel. Thanks!

View attachment init.qcom.post_boot.sh.zip

 

[lyfkevin]

For those who not satisfy with the power consumption on CM10.1, Try to use BetterBatteryStats to track the sources of battery drain.
I think this is great approach to solve battery drain source one by one. Share ur result

I tested different cases overnight(8hrs)
flight mode 1% drop
data and wifi off 5% drop
wifi turn on 3x% drop

In my device, found "wlan_rx_wake" in kernel wakelock dominates the most.
I googled the solution and implemented into upcoming kernel. Need more time to test the result. Report later

 

[mpsantiago]

For those who not satisfy with the power consumption on CM10.1, Try to use BetterBatteryStats to track the sources of battery drain.
I think this is great approach to solve battery drain source one by one. Share ur result

I tested different cases overnight(8hrs)
flight mode 1% drop
data and wifi off 5% drop
wifi turn on 3x% drop

In my device, found "wlan_rx_wake" in kernel wakelock dominates the most.
I googled the solution and implemented into upcoming kernel. Need more time to test the result. Report later

I posted this in the CM10.1 thread, but I guess I'll post it here (since I'm using Wind) to get the ball rolling on results:

To get a baseline for BBS, last night before bed I charged my phone to 100% and then took it off the charger at 12am. By 7am it had lost almost 30% battery life. BBS showed a near-constant partial wakelock from the process 'AudioOut_2'. This is a fairly clean CM10.1 install, no games or any audio related apps.

After turning off touch sounds (Settings > Sound > Touch Sounds) the wakelock went away. Battery drain seems to have subsided. I need to test more to make sure though.

I let my phone charge back up to 100% and here's where it is at right now, with fairly steady use (calls, browsing, texting, etc):

*I use Green Power to keep data off when the screen is off, but it turns it back on periodically so the phone can sync. I am using SmartAssV2 governor at around 1400mhz.



edit: sorry for the ginormous picture, I'm used to forums that auto scale them down!

 

[lyfkevin]

I posted this in the CM10.1 thread, but I guess I'll post it here (since I'm using Wind) to get the ball rolling on results:

To get a baseline for BBS, last night before bed I charged my phone to 100% and then took it off the charger at 12am. By 7am it had lost almost 30% battery life. BBS showed a near-constant partial wakelock from the process 'AudioOut_2'. This is a fairly clean CM10.1 install, no games or any audio related apps.

After turning off touch sounds (Settings > Sound > Touch Sounds) the wakelock went away. Battery drain seems to have subsided. I need to test more to make sure though.

I let my phone charge back up to 100% and here's where it is at right now, with fairly steady use (calls, browsing, texting, etc):

*I use Green Power to keep data off when the screen is off, but it turns it back on periodically so the phone can sync. I am using SmartAssV2 governor at around 1400mhz.



edit: sorry for the ginormous picture, I'm used to forums that auto scale them down!

It seems to be ROM-related problem.
I found this commit and not sure whether it applied to our device. I have no experience with ROM.
http://review.cyanogenmod.org/#/c/24052/2/
may tdmcode help?

 

[mpsantiago]

It seems to be ROM-related problem.
I found this commit and not sure whether it applied to our device. I have no experience with ROM.
http://review.cyanogenmod.org/#/c/24052/2/
may tdmcode help?

That sure looks like my problem.

 

[lordcheeto03]

That sure looks like my problem.

/android_device_samsung_d2-common is the GS3 I believe.