• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Homeless Kernel 1.0

Kanaida can you make one for zvc since it is possible to root that now? PG said that a kernel alone would most likely cause bootloops so to be safe it would be better to have a kernal made for zvc. Thank you for your hard work and that would be great for a lot of people.
 
That's good news. Somehow I missed that the C Firmware had been rooted :D anyone got a link?

I'll download the source and re-compile a new kernel in a day or so after my girl leaves my house lol, Tweaking her startup routines and plugging in peripherals comes first hehehe... :D
 
This is working nicely so far. 6 hours of normal use took me down to 43%...

Then I chickened out and plugged it in. Need the phone to work tonight & I won't have access to a charger.

So it should have lasted 10 or 11 hours, which is great for me :D
 
Flashed the kernel last night while charging then unplugged @ 100%. 17 hours and 30 minutes and counting at 32% with stock battery and JuiceDefender Ultimate. Went all night on standby and only used about 4 percent of battery compared to almost 10/hour normally. Light usage (web browsing, Youtube watching, a bit of Samurai II and Angry Birds). Anything requiring web was done on 4G as my home internet wasn't working. Will post a screenshot later before I plug it in for the night.

Also wanted to thank Kanaida for making this kernel and giving us some relief to the dismal battery life the Esteem is known for. It's not like my Optimus was but with this kernel it's pretty darn close.
 
As promised... about the same usage as my earlier report. Stock battery.

screenshot.jpg
 
LOVE the battery life on this. I got 15 hours today comfortably on 4g. It's exactly what I need.

Anybody else getting really slow performance though? Web surfing is almost unbearably slow. Is there a way we can choose to boost performance just a bit? I know it's always a tradeoff with battery, but it's pretty hard to surf right now.

Great stuff!
 
nice job kanaida battery life is real good especially with extended battery ,and I still got good speed thx!!!!!!!
 
drtobaggan said:
LOVE the battery life on this. I got 15 hours today comfortably on 4g. It's exactly what I need.

Anybody else getting really slow performance though? Web surfing is almost unbearably slow. Is there a way we can choose to boost performance just a bit? I know it's always a tradeoff with battery, but it's pretty hard to surf right now.

Great stuff!
Click to expand...

I haven't noticed a speed difference at all. If I played games maybe but I can't tell a difference from the 1.2 that I was running with plague extreme kernel.
 
I dropped mine to cap at 806 MHz and I still don't notice a difference in responsiveness. I also can get 10 plus hours of light use and come home to 65% without this kernal on a regular battery just by using Juice Defender. I put this kernal on last night and will see how much better it works for me.
 
i like the low battery drain...(..batt life is about 12hrs as promised..) but i did get a couple of random reboots and twice i got reboot loops that keep going until u take the batt out and hold the power button for like 30 secs to discharge all the capacitors. I mean im gonna stick with this kernel, its just i would really love if it was slightly tweaked for stability...... ( no pressure ofcourse ) ;)
 
ghostridernyc said:
i like the low battery drain...(..batt life is about 12hrs as promised..) but i did get a couple of random reboots and twice i got reboot loops that keep going until u take the batt out and hold the power button for like 30 secs to discharge all the capacitors. I mean im gonna stick with this kernel, its just i would really love if it was slightly tweaked for stability...... ( no pressure ofcourse ) ;)
Click to expand...

I am seeing the same issue battery life has been super but the phone has been a little unresponsive and lag at times other than that thanks kanaida I'm running optimizer too
 
You guys that are having stability issues: did you wipe cache before flashing? I did and this kernel has been running flawlessly for me. I never had the reboot issue to begin with, did you have them on your stock phone?
 
revogozoom said:
You guys that are having stability issues: did you wipe cache before flashing? I did and this kernel has been running flawlessly for me. I never had the reboot issue to begin with, did you have them on your stock phone?
Click to expand...

no rebooting on mines but did not do the wipe of cache before installing the kernel I'm running gingeresteem I guess would i wipe now or start the whole process again?
 
revogozoom said:
You guys that are having stability issues: did you wipe cache before flashing? I did and this kernel has been running flawlessly for me. I never had the reboot issue to begin with, did you have them on your stock phone?
Click to expand...

I agree. Mine has been running flawlessly as well, feels just as fast as OC @ 1.2 i'd say.
There is some bug somewhere (not the kernel) wich causes response lag that's only cured by reboot, i only noticed it once when i snoozed an alarm by clicking the icon in the notification pulldown. It does this very rarely though. Perhaps it's a driver bug. My Optimizer app makes this happen much less often than it occurs normally, even though the cause is still proving elusive. It's not such an issue not that it's not a 3 minute boot time though :)

I'd try clearing the cache and dalvik cache to see if that helps.
 
kanaida said:
I agree. Mine has been running flawlessly as well, feels just as fast as OC @ 1.2 i'd say.
There is some bug somewhere (not the kernel) wich causes response lag that's only cured by reboot, i only noticed it once when i snoozed an alarm by clicking the icon in the notification pulldown. It does this very rarely though. Perhaps it's a driver bug. My Optimizer app makes this happen much less often than it occurs normally, even though the cause is still proving elusive. It's not such an issue not that it's not a 3 minute boot time though :)

I'd try clearing the cache and dalvik cache to see if that helps.
Click to expand...

Im running pretty smooth just a couple of lags here and there but other than that im luving it : )
 
whats the average battery life you guys are getting with this kernel, and what do you keep on and off as far as your settings are concerned(4g,wifi,etc).
 
Today my battery life is even more ridiculous for some reason, maybe a little less use than yesterday. :D, I just re-calibrated my battery this morning, so that might have had something to do with it. I'm not using anything except the optimizer as far as battery saving apps, no cpu controls, just stock 1Ghz On Demand, no task killers, wifi and bluetooth enabled the whole time.

I'm at 90% left and it's been on battery for 3h 34m 51s, I have a funny feeling the 90% still has some juice left before changing to 89% too LOL

I've found a new development too. com.android.DunServer is using the remainder of the phone's juice. That 79ish percent identified as android_system in the battery screen. I think there is some sort of bug, or modification that LG made to that app that's different from stock google code. If anyone knows Java and can look at the source for that APK we can finally truly unleash the beast... :cool: I'm talking theoretically like maybe 10% battery would give is 6 hours. To an unbelievable 60+/- hour battery life.

I only have one clue:
The following events keep getting fired, but my logic says this should only be fired when the cable changed from plugged to unplugged. It may be a message getting attention over and over for no reason.

I/dun_service( 118): Post event 1
I/dun_service( 118): received event: DUN_EVENT_USB_UNPLUG
I/dun_service( 118): received event(DUN_EVENT_USB_UNPLUG) in state(DUN_STATE_USB_UNPLUG)
I/dun_service( 118): Ignoring the event DUN_EVENT_USB_UNPLUG in USB_UNPLUG_STATE
I/dun_service( 118): Moved to state(DUN_STATE_USB_UNPLUG)
 
kanaida said:
Today my battery life is even more ridiculous for some reason, maybe a little less use than yesterday. :D, I just re-calibrated my battery this morning, so that might have had something to do with it. I'm not using anything except the optimizer as far as battery saving apps, no cpu controls, just stock 1Ghz On Demand, no task killers, wifi and bluetooth enabled the whole time.

I'm at 90% left and it's been on battery for 3h 34m 51s, I have a funny feeling the 90% still has some juice left before changing to 89% too LOL

I've found a new development too. com.android.DunServer is using the remainder of the phone's juice. That 79ish percent identified as android_system in the battery screen. I think there is some sort of bug, or modification that LG made to that app that's different from stock google code. If anyone knows Java and can look at the source for that APK we can finally truly unleash the beast... :cool: I'm talking theoretically like maybe 10% battery would give is 6 hours. To an unbelievable 60+/- hour battery life.

I only have one clue:
The following events keep getting fired, but my logic says this should only be fired when the cable changed from plugged to unplugged. It may be a message getting attention over and over for no reason.

I/dun_service( 118): Post event 1
I/dun_service( 118): received event: DUN_EVENT_USB_UNPLUG
I/dun_service( 118): received event(DUN_EVENT_USB_UNPLUG) in state(DUN_STATE_USB_UNPLUG)
I/dun_service( 118): Ignoring the event DUN_EVENT_USB_UNPLUG in USB_UNPLUG_STATE
I/dun_service( 118): Moved to state(DUN_STATE_USB_UNPLUG)
Click to expand...


Are you sure it's not just the power required for the hungry beast we know and love called LTE?
 
twistedriku said:
Are you sure it's not just the power required for the hungry beast we know and love called LTE?
Click to expand...

I think it's responsible for data and firing off some usb related events, but i'm not 100% sure.
Either way, data isn't always in use so during this period we should try to use as little cpu cycles as possible to allow the phone's hardware to enter deep sleep modes. It's definately required from what I can tell for proper operation, I just think the code has room for tuning.

by looking at those debug messages, it looks like it can be tuned a bit by something like this:

If Not UsbStatus = 'UNPLUGGED' then
Fire Event
End if

as opposed to just firing it all the time regardless if it's already in the new state or not, unless there's a valid reason for that. If that event is fired, there could be other routines handling that event and doing more work for nothing each time it fires, even worse triggering even more of their own events like a chain reaction.
 
kanaida said:
I think it's responsible for data and firing off some usb related events, but i'm not 100% sure.
Either way, data isn't always in use so during this period we should try to use as little cpu cycles as possible to allow the phone's hardware to enter deep sleep modes. It's definately required from what I can tell for proper operation, I just think the code has room for tuning.

by looking at those debug messages, it looks like it can be tuned a bit by something like this:

If Not UsbStatus = 'UNPLUGGED' then
Fire Event
End if

as opposed to just firing it all the time regardless if it's already in the new state or not, unless there's a valid reason for that. If that event is fired, there could be other routines handling that event and doing more work for nothing each time it fires, even worse triggering even more of their own events like a chain reaction.
Click to expand...


...fix it...FIX IT!!!!!
 
You must log in or register to reply here.
Back
Top Bottom