Develop Bugs

Correct way to charge and use SBC kernels?

I was wondering if someone could explain the correct way to charge kernels with SBC? I have been using the Tiamat 3.3.7 kernel with CM7 and Salvage-Mod and gotten great battery life but that was using it with a extended battery as of late I have been using my Standard Battery with Sense and CM7 using a SBC kernel on both and noticed that it rapidly plummets to the mid 80s in about a half hour of music play. What I was wondering is do SBC kernels not work with stock batteries and what would be the correct method to getting a full 100% charge? Any help would be greatly appreciated.
Sent from my PC36100 using XDA Premium App

Even with skepticism (INFO), I prefer SBC and have been for a while now.
This is what works for me...try at your own risk!
With battery monitor widget (from market) menu > settings > monitoring preference > hit monitor without widget, history update rate- 1min, battery capacity (whichever size you using).
charge...
Now, at times could never to get it to this point like it states here. So what I do is when the light turns green (it isn't fully charged), from monitor hit history, you'll see positive mA's getting smaller and smaller, when it hits zero unplug. (I usually hit calibrate [app from market] at this point if its a new ROM, kernel or battery). Should be good to go. I get it sitting on 100% with a 3500 mA for 3-12 hrs depending on use.
I can't keep track of the charge like that on a non SBC kernel.

Yep, the green light and the "100%" are meaningless. But the charge milliamps will not hit zero, at least not with my extended battery. They drop to 6-8 milliamps and that is drop dead full charge idle power.

Click on the link in my signature

Phone not changing battery capacity state when using extended battery

Hi,
I have come across a problem which has yet to be addressed.
It is touched upon in the thread at the end of this post but as yet there is no fix hence why I have started this thread to try get a solution
What I have found is that if you use an extended battery with the Desire HD, there is a slight problem. The system apparently reads from the kernel and system information the mha of the battery. So, the system reads 1250mha.
Problem
When using an extended battery (I am using currently Mugen 1500mha) the phone still displays a battery capacity of 1250mha and so charges accordingly hense removing any aspect of 'extended'
I have tried 2 battery calibration methods (app and the HTC suggested) also reset battery information using recovery.......still no change in figures, phone still stating 1250mha battery in use.
Have also tried different ROMs and it is not ROM specific it applies across the board
Is it possible to get a mod to change the battery capacity values in order for the device to recognize the mha and charge and use the battery correctly? Maybe even a flashable patch to update these values (one for 1500, 1800 so on)
I look forward to seeing where this goes
I have contacted Mugen and awaiting a response, will update you with my findings
Chow for now
http://forum.xda-developers.com/archive/index.php/t-818794.html
Sent from my HTC Desire HD (RCMix 3D v2.0) using XDA App

[KERNEL][4.0.3] Limited voltage charging for battery-saving paranoid and developers

This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mV and > 80%, and start charging again at 3990mV or < 80%.
Rationales:
Stock kernel: I value compatibility and stability. While the various mods and new features are undoubtedly very useful for many people, some of them are not well tested which results in lower stability. That is not to say stock Android is extremely stable (it is not), adding new features on top of which very often increases the likelyhood of crashes.
Limited charging: As a developer, my phone is virtually plugged in the computer all the time. As many of you are aware, leaving the phone charged greatly reduces battery life (Ref). This kernel frees you from having to unplugging and plugging in the phone repeatedly in fear of destroying your precious battery.
Visible differences:
Charging percentage will not increase after the phone is charged to 80% or more.
The phone never reports full charge, even if it's charged while being turned off. That means battery stats can accumulate which, after a while, makes it practically useless as the diagram is too compressed. This is a plus to me as I can see how I manage the battery over time, although I can make an alternate version which reports full charge whenever the phone stops charging under requests.
Perhaps I'm the only one who is paranoid about keeping battery charge between 10-90%, I wouldn't be surprised if no one is interested it this at all.
The kernel can be flashed using Odin or fastboot. If someone wants a CWM-flashable zip let me know.
Cheers.

You could have simply used my BLX mod.

Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
Glad to know I'm not the only one. When I was using the SGS2 I spent quite a bit of time looking for such mod to no avail. Searching for "android|galaxy nexus limit charging voltage" turned up lots of posts about changing kernel voltage which wasn't what I wanted.
I like to keep the kernel close to stock, but thanks anyway .

Hey, an idea to you devs: what about a apk that schedules the charge limit? for example, if you use to charge your phone at night and you wake up at 7 that app could charge the phone @ 60% and at 6 start charging'till it reaches the 100%
With ezekeel BLX mod it should be easy to schedule modifying the file, but i have no idea on programming nor cron

Guzmanus said:
Hey, an idea to you devs: what about a apk that schedules the charge limit? for example, if you use to charge your phone at night and you wake up at 7 that app could charge the phone @ 60% and at 6 start charging'till it reaches the 100%
With ezekeel BLX mod it should be easy to schedule modifying the file, but i have no idea on programming nor cron
Click to expand...
Click to collapse
You can do that with Tasker, it is a bit on the heavy side but saves having another service running in the background while leaves the possibility to do a lot more. I'm not aware of other light-weight but user friendly solutions for managing scripts, perhaps others could chime in.

Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
agree with ezekieel...his Battery Life eXtender (BLX)do the same thing(via file /sys/class/misc/batterylifeextender/charging_limit default 100),without give up at all the tweaks,oc,color control etc. try that if you want.anyway thanks for the work,personally it not interest me,but certainly someone will find it usefull!

fnf said:
This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mAh and > 80%, and start charging again at 3990mAh or < 80%.
Rationales:
Stock kernel: I value compatibility and stability. While the various mods and new features are undoubtedly very useful for many people, some of them are not well tested which results in lower stability. That is not to say stock Android is extremely stable (it is not), adding new features on top of which very often increases the likelyhood of crashes.
Limited charging: As a developer, my phone is virtually plugged in the computer all the time. As many of you are aware, leaving the phone charged greatly reduces battery life (Ref). This kernel frees you from having to unplugging and plugging in the phone repeatedly in fear of destroying your precious battery.
Visible differences:
Charging percentage will not increase after the phone is charged to 80% or more.
The phone never reports full charge, even if it's charged while being turned off. That means battery stats can accumulate which, after a while, makes it practically useless as the diagram is too compressed. This is a plus to me as I can see how I manage the battery over time, although I can make an alternate version which reports full charge whenever the phone stops charging under requests.
Perhaps I'm the only one who is paranoid about keeping battery charge between 10-90%, I wouldn't be surprised if no one is interested it this at all.
The kernel can be flashed using Odin or fastboot. If someone wants a CWM-flashable zip let me know.
Cheers.
Click to expand...
Click to collapse
Source code?? It has to have a link.
Since you modified the kernel

Mikey said:
Source code?? It has to have a link.
Since you modified the kernel
Click to expand...
Click to collapse
Not much to speak of tbh. Here is the patch. You can build it from the stock branch 4.0.3_r1 . I changed the compilation flags so it better matches Cortex A9 but I'm sure there are rooms for performance improvements.
GLaDOS kernel has this value configurable as well so aside from being stable, this kernel is worse all around .

I assume you meant 4000 mV, not 4000 mAh? Considering that not even extended batteries I've seen exceed 3500 mAh?

Entropy512 said:
I assume you meant 4000 mV, not 4000 mAh? Considering that not even extended batteries I've seen exceed 3500 mAh?
Click to expand...
Click to collapse
Post amended, thanks .

fnf said:
This is a stock kernel for GSM Galaxy Nexus 4.0.3 with the following properties:
Root access with adb (a.k.a. insecure)
Charger is modified to stop charging at 4000mV and > 80%, and start charging again at 3990mV or < 80%.
Click to expand...
Click to collapse
Ezekeel said:
You could have simply used my BLX mod.
Click to expand...
Click to collapse
Greetings gentlemen! I've been testing wireless charging with Galaxy Nexus and Nexus 5, and while I like the technology, I'm not comfortable with two side-effects: higher battery temperature, and higher average battery charge voltage. I'd like to work around this by limiting the charge capacity to 80% / 4.0v.
I think the lost battery capacity will work for me because the way I'm using the wireless chargers is keeping the batteries topped up all day. By keeping wireless chargers by the bed and the main work space, the phones hardly ever run down! But this also keeps the battery at 100% constantly. Thus my 5-year-old bright idea to limit the voltage!
What's the state of the art of this problem solution? Should I ask a kernel developer to include https://github.com/Ezekeel/GLaDOS-nexus-s/tree/blx ?

Defy/Defy+ Battery Stats, Endurance and Advice

Me and My Battery
A comprehensive battery stat and tweak thread​
We all love our phone.
We all measure battery life.
And we all tend to post that battery life on the CM10 DEV thread.
Not any more!
This thread will aim to reduce the battery OT load on Quarx's CM10 thread...
Post whatever battery related stuff you want to in here.
Do you use an HF5 or an HF5X??
Are you a badas* and use an HF5X on a Defy?
How long does your battery last on the latest build?
How long did it last on stock MotoBlur?
How long did it last on CM7? On CM9?
How long did it last on that month old build nobody else uses now (except for you)???
How old is your battery?
How do you charge your battery?
Via wall-mount charger or via PC USB?
When do you charge it?
Every night?
Whenever it reaches below 15%?
After fully draining it up to 0%?
What are your battery temperatures?
Do you use Juice Defender or other apps?
Please feel free to post advice on how you increase battery life on your phone.
Post battery fixes if they are needed.
In short, use THIS thread for all the nitty-gritties of battery life.

inb4 y'all.

3rd
muffin approved this message.....

Reserved
____________________________________
ಇದು ನನ್ನ ಆಪ್ ಸಿಗ್ನೀಚುರ್
Nothing is True.. Everything is Permitted©

Seing as someones thrown their toys out of the pram on the dev forum ( it feels like walking on eggshells on here sometimes )
for me, The latter versions of CM10 have significantly shorter battery life than other roms such as cm7 and older versions of CM10.
this is across all of 3 my batterys, all of them varying in age, form as old as the phone to anout 8 months old.

Reserved
Great ideea btw had some info to share but didn't want to clog the dev thread.
Sent from my MB526 using xda premium

SleepyKrushna said:
Me and My Battery
A comprehensive battery stat and tweak thread​
We all love our phone.
We all measure battery life.
And we all tend to post that battery life on the CM10 DEV thread.
Not any more!
This thread will aim to reduce the battery OT load on Quarx's CM10 thread...
Post whatever battery related stuff you want to in here.
Do you use an HF5 or an HF5X??
Are you a badas* and use an HF5X on a Defy?
How long does your battery last on the latest build?
How long did it last on stock MotoBlur?
How long did it last on CM7? On CM9?
How long did it last on that month old build nobody else uses now (except for you)???
How old is your battery?
How do you charge your battery?
Via wall-mount charger or via PC USB?
When do you charge it?
Every night?
Whenever it reaches below 15%?
After fully draining it up to 0%?
What are your battery temperatures?
Do you use Juice Defender or other apps?
Please feel free to post advice on how you increase battery life on your phone.
Post battery fixes if they are needed.
In short, use THIS thread for all the nitty-gritties of battery life.
Click to expand...
Click to collapse
Is this post here only for Battery under CM10 or in General??????
I have problem with BF5X High-Capacity Gold Battery 2430 mAh (for Moto MB525) under 3 and 4MS2G ROM.
It is charging Up to 81% only and I have tried out Walter`s patch But nothing.
Under Stock FROYO it charges Up to 90%.
Please, ignore/delete if the tread is only for CM10!

I think that I found the culprit.. (maybe)
- install SetVsel
- check if the values are higher than than those on bootmenu
Can some one check this?
I had VSel1 to something like [email protected] or VSel4 on [email protected] ...
But bootmenu has much lower values..
so far, so good..

nedywest71 said:
Is this post here only for Battery under CM10 or in General??????
I have problem with BF5X High-Capacity Gold Battery 2430 mAh (for Moto MB525) under 3 and 4MS2G ROM.
It is charging Up to 81% only and I have tried out Walter`s patch But nothing.
Under Stock FROYO it charges Up to 90%.
Please, ignore/delete if the tread is only for CM10!
Click to expand...
Click to collapse
Hi, I am using the exact same battery as yours.
Using Quarx's new kernel in the 2nd boot version of CM10, that battery can charge normally to 100%...
Sent from my Nexus 7

axcoro said:
I think that I found the culprit.. (maybe)
- install SetVsel
- check if the values are higher than than those on bootmenu
Can some one check this?
I had VSel1 to something like [email protected] or VSel4 on [email protected] ...
But bootmenu has much lower values..
so far, so good..
Click to expand...
Click to collapse
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.

SleepyKrushna said:
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.
Click to expand...
Click to collapse
That's the problem... in bootmenu the values are lower than those, when andoid is running!
(and yes.. I used that app )
eg:
bootmenu: vel1: 300 @ 30
runtime: vel1: 300 @ 42
and thats is odd..

axcoro said:
That's the problem... in bootmenu the values are lower than those, when andoid is running!
(and yes.. I used that app )
eg:
bootmenu: vel1: 300 @ 30
runtime: vel1: 300 @ 42
and thats is odd..
Click to expand...
Click to collapse
This is on CM10 05.12?

SleepyKrushna said:
Just to make it crystal clear, the default boot menu values are actually OVER volted.
Calculate values for your frequencies either by using this app-----> http://forum.xda-developers.com/showthread.php?t=1815142
Or by using the formula (frequency)/20 ±2.
Use boot menu to set frequencies and voltages.
Keep 'Load all modules' OFF, and governor as Interactive.
Click to expand...
Click to collapse
I've been using SetVsel to adjust voltage. Should I be adjusting the bootmenu's instead? Why?
Cheers.
----
I have BF5X ... So what does this mean in comparison to HF5(X)?
Quarx 2012.11.18
Usually charge via wall-mount since PC-USB takes longer.
Usually have to charge overnight.
With semi-regular use, It's lasted 21hrs.
Usually lasts less than that with video/music/screen on constantly.
(With 3G-on, Brightness 25-50%, subsonic running playing music, getting a few texts, and messing with some settings/desktop I lost just under 10% batt in one hour. or 1-2% usage per 10 minutes.)
I only use SetVsel:
300/17
600/32
800/42
1000/52
up_threshold: 86%
Apply @ boot: Ticked.
Limiting Vsel2 @ 10%
up_threshold to 99% @ 10%

KicknGuitar said:
I've been using SetVsel to adjust voltage. Should I be adjusting the bootmenu's instead? Why?
Cheers.
----
I have BF5X ... So what does this mean in comparison to HF5(X)?
Quarx 2012.11.18
Usually charge via wall-mount since PC-USB takes longer.
Usually have to charge overnight.
With semi-regular use, It's lasted 21hrs.
Usually lasts less than that with video/music/screen on constantly.
I only use SetVsel:
Apply @ boot: Ticked.
Limiting Vsel2 @ 10%
up_threshold to 99% @ 10%
Click to expand...
Click to collapse
Why?? Coz you can....
using boot menu instead of setvsel just reduces the no of apps you need to use.
Why do a patch when you can program the system itself?
Plus, auto patches at boot increase the time it takes for the phone to become usable after boot.
AFAIK, BF5X and HF5X are the same... I don't know this for sure, but someone said this some time back on the dev thread...
18.11 was a good build... I got 4.5 hrs on continuous 3G use... and about 18-20 hrs on occasional use....

2Pints said:
Seing as someones thrown their toys out of the pram on the dev forum ( it feels like walking on eggshells on here sometimes )
for me, The latter versions of CM10 have significantly shorter battery life than other roms such as cm7 and older versions of CM10.
this is across all of 3 my batterys, all of them varying in age, form as old as the phone to anout 8 months old.
Click to expand...
Click to collapse
Ya, battery life is lesser and battery temperatures are higher on CM10 05.12 in my experience.
Its a bug of the latest build...
Let's wait to see what the next one does....

SleepyKrushna said:
Why?? Coz you can....
using boot menu instead of setvsel just reduces the no of apps you need to use.
Why do a patch when you can program the system itself?
Plus, auto patches at boot increase the time it takes for the phone to become usable after boot.
AFAIK, BF5X and HF5X are the same... I don't know this for sure, but someone said this some time back on the dev thread...
18.11 was a good build... I got 4.5 hrs on continuous 3G use... and about 18-20 hrs on occasional use....
Click to expand...
Click to collapse
Cheers.
Any other adjustments beyond Vsels I should adjust in the Bootmenu? i.e. the 10 batt options SetVset had.
What blows my mind is the phone I had before Defy was just a QWERTY keyboard sliding cellphone... freaking 2+ days of usage! Now I can barely make it to 24hrs! AGh!

KicknGuitar said:
Cheers.
Any other adjustments beyond Vsels I should adjust in the Bootmenu? i.e. the 10 batt options SetVset had.
What blows my mind is the phone I had before Defy was just a QWERTY keyboard sliding cellphone... freaking 2+ days of usage! Now I can barely make it to 24hrs! AGh!
Click to expand...
Click to collapse
You can do a lot in boot menu....
set thresholds, set CPU speed in sleep, on wakeup, etc....
its been months since i used setvsel, so I'll have to look up the options you're talking about..

Well, me and my battery are about to go our separate ways, I notice heavy drops lately, for example from 70% directly to 50%. I believe the battery is dying, so I ordered a 2400mAh battery from an amazon.co.uk reseller. My current battery is an BF5X original, nearing the 2 years mark now. I charged once every 2 days when in CM7, but often every day after heavy usage. With CM10 I have to charge every day, it drains more.

ccav2000 said:
Well, me and my battery are about to go our separate ways, I notice heavy drops lately, for example from 70% directly to 50%. I believe the battery is dying, so I ordered a 2400mAh battery from an amazon.co.uk reseller. My current battery is an BF5X original, nearing the 2 years mark now. I charged once every 2 days when in CM7, but often every day after heavy usage. With CM10 I have to charge every day, it drains more.
Click to expand...
Click to collapse
I'm a real heavy user.... most of the time my phone is plugged in, coz with the loads I put on the 3G antenna and on the processor, I only get 4-4.5 hours of use....

Pasting this here for safekeeping from main dev thread:
Suspend - no1 power consumer.
I second that. Using the same tools like GSAM Pro + ROM Toolbox and Android Toolbox from 3C, i managed to isolate the same process. Underneath it all this "suspend" belongs to the kernel and from a more detailed report it is allways accompanied by "loop#" processes. In my case, kernel and its processes is the no1 consumer, all the time.
The second consumer is Android System, mostly due to atmospheric sensors (i had no ideea the Defy+ has anything like this..probabily because it doesn't  but the processes are there anyway)
Even like that i get at least 30hrs between charges, permanently having wifi or 2G on.. .
My HF5X battery is 1yo(came with the phone) and is being charged with no concern whatsoever about preserving it's life ...so yeah, random times and random sources (pc or wall plug, even used my e-cigar ac adapter).
What i did so far was:
- I had problems with "media server" as a power hog. After searching the forum for a solution a thread gave me the right one.
I ran mp3 check and found several mp3 files that were broken. Fixed whatever i could and replaced what was irreparable (AC/DC-Thunderstruck, of course, was one of'em)
- Found and removed unnecessary start-up entries. Wherever this was not an option i disabled their receivers (i REALLY don,t need to have YouTube ready at boot time, having it started on youtube links is nice enough).
- Used many launchers to the day. The last one and by far the least RAM/CPU and power hungry is the current one - Lightning Launcher by PIERROX (see signature). Look at the download size in the Play Store (handsome title btw) Did i mention it's FREE?
- Keyboard was replaced with Perfect Keyboard Pro - low RAM footprint.
- I permanently use a live wallpaper that gives me an overview of the CPU, RAM, BATTERY and DIRECTION (compass is allways on but is literraly close to 0 in terms of power consumption)
-ALL the useless stuff was uninstalled or replaced.
- Using Android Toolbox i setup database and app load optimisations to run on boot.
- ZRAM is disabled, KSM on, SWAP (64mb) is on.
What i want to do:
- collect a full system dump, if possible. Get it analysed (in UNIX there's kdb for that purpose, i have no ideea what is the equivalent here)
Hope this helps/points/suggests an approach to someone. Furthermore, may i suggest a SEAL TS3 for those mild Siberian winter nights? IP68 & MIL-SPC860 should help 
Regards.
Sent from my MB526 using xda premium.

Battery charges to above 4300mV

Hi guys,
Today I've installed battery monitor app and saw that at full charge with the charger connector still attached I have a voltage above 4300mV. I know that Li-Ion are very stressed above 4200mV and this shortens the battery life a great deal (you are left with only 1/3 of the battery endurance that you would normally have). Do you think lg made this purposely so we would have a little more juice with the downside of a quick degradation of battery performance? Thanks

cojocar.andrei said:
Hi guys,
Today I've installed battery monitor app and saw that at full charge with the charger connector still attached I have a voltage above 4300mV. I know that Li-Ion are very stressed above 4200mV and this shortens the battery life a great deal (you are left with only 1/3 of the battery endurance that you would normally have). Do you think lg made this purposely so we would have a little more juice with the downside of a quick degradation of battery performance? Thanks
Click to expand...
Click to collapse
The battery is a 4600 mAh. Does the number not directly corelate?

sleekmason said:
The battery is a 4600 mAh. Does the number not directly corelate?
Click to expand...
Click to collapse
voltage (mV) is different from amperage (mAh)
think of electricity as a waterfall
voltage = height of the waterfall, how much potential energy a water droplet has
amperage = how much water is actually falling per second
anyways, those apps might not be accurate. also, battery charging has some profile/curve. 4.3V isn't particularly bad
http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
http://batteryuniversity.com/_img/content/ion2.jpg

I have another question. How long does your battery last? I'm on mahdi 2.8 with redkernel v9 and from 92% to 10% I only have 5h-6h screen on time with only browsing… Discharge rate measured with battery monitor is between 600mA and 1000mA. It seems an awfully short time. Others report more than 10h on a full charge… How's your battery life? Thanks

cojocar.andrei said:
I have another question. How long does your battery last? I'm on mahdi 2.8 with redkernel v9 and from 92% to 10% I only have 5h-6h screen on time with only browsing… Discharge rate measured with battery monitor is between 600mA and 1000mA. It seems an awfully short time. Others report more than 10h on a full charge… How's your battery life? Thanks
Click to expand...
Click to collapse
Six hours is the most I have ever seen on both of my Gpad tablets. I have not noticed much difference between any ROM or kernel. I have never seen anything close to 10 hours on the Gpad.
Sent from my LG-V500 using xda premium

I improved the battery a bit by undervolting (324Mhz -> 700mV, 1242Mhz->925mV) , reducing the freq of the cpu to 1242Mhz and reducing the gpu freq to 320Mhz. I gain 1h with these changes (I‘m only using the tablet for browsing/reading). I would buy a cover with a slot for an external battery but I didn't find one…

cojocar.andrei said:
I improved the battery a bit by undervolting (324Mhz -> 700mV, 1242Mhz->925mV) , reducing the freq of the cpu to 1242Mhz and reducing the gpu freq to 320Mhz. I gain 1h with these changes (I‘m only using the tablet for browsing/reading). I would buy a cover with a slot for an external battery but I didn't find one…
Click to expand...
Click to collapse
I am experimenting with my two Gpad's. I currently have both set up wit Mahdi ROM and Mani kernel. I have one underclocked both cpu and gpu. The other has stock settings. Interested in seeing how much difference it makes. I am not expecting much because the screen eats up most of the battery.
Sent from my LG-V500 using xda premium

mani kernel gave me sdcard unexpected unmounts while writing to sd and putting the tablet to sleep

Under clocking the cpu and gpu and under volting the cpu gained about 90 minutes of screen on time, but it was not worth the cost in performance… which was especially noticeable when switching between apps. The main reason for using a custom kernel (red kernel or mani) is to improve performance...not cripple it.
Sent from my LG-V500 using xda premium