Database Info

Battery issues

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am getting strange battery life.. I'm running kp1 modem with andromeda and speed mod kernel, and my battery will not last me a day with light usage. (some xda browsing, tweetdeck, texting) I've deleted battery stats and fully discharged and then recharged and that is what these screen shots are from. Any ideas?
Sent from my SAMSUNG-SGH-I897 using XDA App

Well for what ever reason, a Kernel/Modem/ROM setup on one device might not have the same "Super Battery Sipper" effects on another.. It's all about trying out what works best for YOUR device.
So start playing with Kernel/Modem combo's unless you want to change your ROM.
Unfortunately there is no set science for some reason

If you're using an older version of speedmod, make sure the battery tweaks are enabled under the recovery menu.

I've tried everything, I've used jpy, jj4, and ji6 based roms, cognition, perception, andromeda, cezars... And I am using the most up to date kernel from hardcore. I'm using the kp1 modem for now but I've tried all the other modems and only jk4, jl2 and jk3 work well. I'm also using the lowest brightness setting and juice defender. I get about a day out of out with light usage..
Sent from my SAMSUNG-SGH-I897 using XDA App

Quadrant score for Desire S

What should be "normal" for Desire? I constantly get around 2000+ with no overclock. On my former Legend oced to 806 Mhz I was hardly getting 1400. I know the processor is better in Desire S but still the difference is big. Could be a bug with Quadrant?
Using CM 7.1 stable, interactive governor, 1024 mhz, standard CM kernel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from nowhere over the air...

That's good you should be happy with a higher score... Whats wrong with that
Sent from my HTC Desire S using xda premium

I am happy...there's no doubt about that. I was just wondering if these are the usual values for Desire since in the Legend section there was such a topic with benchmark results and here I couldn't find any.
If values are not resulting from a bug of Quadrant and are correct, it's great. I was just surprised by the difference that's all and wanted to compare the results with other's. I don't see now any reason for which I should overclock the Desire S. Maybe ICS will demand more power, but I think has enough for now. Everything works smooth and fast, no lag, temp does not raise above 35-37 degrees...it's great
Sent from nowhere, over the air...

Yep, no need to OC
Those results are normal for AOSP ROMs, (like cm7)
Sent from my HTC Desire S using xda premium

Undervolting - Am I doing it right?

I was looking at the glitch kernel thread and saw that the max UV for the kernel was -200 for 200mhz, and around -50 for 1Ghz.
Well I'm managing almost -200 for all of the speeds and I haven't faced any issues so far. What's going on? Is my phone not actually undervolted?
Here's a screenshot...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(sorry for the horrible image quality).

Silencer96 said:
I was looking at the glitch kernel thread and saw that the max UV for the kernel was -200 for 200mhz, and around -50 for 1Ghz.
Well I'm managing almost -200 for all of the speeds and I haven't faced any issues so far. What's going on? Is my phone not actually undervolted?
Here's a screenshot...
(sorry for the horrible image quality).
Click to expand...
Click to collapse
Undervolting increase battery life at the cost of some performance loss, especially when multitasking

ROMMaker said:
Undervolting increase battery life at the cost of some performance loss, especially when multitasking
Click to expand...
Click to collapse
No -_- it doesn't.
Sent from my SAMSUNG-SGH-I897 using xda premium

Overclocking

Question....what is the fastest anybody has been able to overclock, without boot-looping? I know there are a lot of variables involved, but I was just curious. I managed to get 1280mhz out if it, but, not really sure if I can push it higher.
Sent from my MB865 using xda app-developers app

I'm running at 1.25GHz stable with additional ram speed and net speed tweaks, along with a few select build.prop tweaks. Any higher and I get freezes and/or random reboots. It seems to vary from device to device, as some users have been reported to run as high as 1.3GHz or slightly higher, while others have issues running at 1.2GHz or even lower..
Edit: If you'll notice, I've also underclocked to 240MHz which is probably a good idea when running the CPU at 'mot_hotplug' or 'ondemand' settings other than 'performance' so that gives the CPU a lower frequency scale to fall back to, when not running at the full frequency scaling.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MB865 using xda premium

Thanks....I have it @ 1300 mhz now, with no problems showing up, so far, but I'm going to scale it back to 1150, and underclock it too, dont need it that high for everyday use. I just wanted to see how far I could go.Thanks for the input.
Sent from my MB865 using xda app-developers app

[Q]Frequency steps with Trinity Series Kernels

Hey guys. I was soley a faux user for months, and recently started using Trinity several weeks ago.
I was wondering if any other Trinity users have noticed this:
While just observing frequency steps, Trinty quite often steps to frequencies that are actually not part of it's main 8 steps, like 750, 1000, 1100, but steps to odd in betweens such as 299.9, 667.56, etc etc
I never observed this odd inbetween stepping with faux, faux lists its on one of its main, available steps.
Just curious if anyone else has observed this on ANY Trinty series kernel.
G2x-CM7 Weekly 12/09/12 Build, Trinity T15 Kernel

example
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
G2x-CM7 Weekly 12/09/12 Build, Trinity T15 Kernel

Yeap i noticed too. Dont know why
Sent from my LG-P999 using xda premium

I'm not sure if I'm correct, but I think those speed steps are put in place so that the phone doesn't SoD.