Database Info

Kaisers Clock Speed lower than 400 Mhz?

When I go into TCPMP, this is what I see for Clock Speed
{
"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"
}
Why isn't my phone running at 400 Mhz?

the kasier processor slows done when not on full load as to save bettery. you would want your kaiser running at 100% all the time or it would be dead every 45 minutes

Yeah, that definitely makes sense. Thanks, austinsnyc.

I agree with austinsync... should be like that...
once it happened to me to have 410mHz, as well!

Gpx85 said:
I agree with austinsync... should be like that...
once it happened to me to have 410mHz, as well!
Click to expand...
Click to collapse
yea ive had 416mhz. it changes lol.

so if im running all kinds of programs like a movie, internet, gps, bluetooth, ect. the cpu speed can sometimes get over 400?

it automatically adjusts mine goes from 375mhz to 420mhz

I've been searching all over for a clocker also. There's time when I'm at work, and all I ever use the phone is for email, because I'm very mobile.
I barely play music, or watch movies, so I actually need something to limit the speed, there's time I need battery span, than speed at work.

[Q] Is this normal?

{
"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"
}
[/URL]
I'm rooted with the GB 2.3.3 update and stock battery with Juicedefender and Setcpu installed. Battery life has definitely made a difference over Froyo and I'm pretty satisfied with the fewer trips to the wall-charger. However, I was wondering why the camera and gallery takes up 46% of my battery I haven't used the camera and I've tried restarting it the phone, but they still persist in the battery list. Anyone with a similar issue?

I don't see an issue. That doesn't mean the camera is still running. It just means you havn't really used your phone for anything. With the power saving settings you have, and the fact that you hardly used the phone in two days, you could have used the camera for 3 minutes and probably would have counted for 20 %
You don't wanna know where this was sent from.

I thought about that too. I did put the phone into airplane mode over-night and also used it to play music with the screen off for a couple of hours, which it why the levels might indicate like I hardly used the phone. But that's the mystery, I never used the camera, at all over the past 2 days.

Trying to understand a supposed battery problem. Maybe wireless.

Alright so the past couple days I have been trying to determine and figure out more about why I am having SOD problems. Yes I understand there is a thread for the SOD but something still bugs me on account a friend of mine has no SOD problems with the same wifi model.
While I haven't had an SOD for a couple days something else hasn't been sitting well in my stomach and that's the battery usage... All of a sudden Android OS is using a significant amount of battery. Much higher than the screen and I don't remember that happening before...
So I downloaded better battery stats and let the tablet sit for about 30 to 40 minutes and her are the results. I am hoping someone will see something out of the ordinary and point me in a good direction.
One I thing I see is that the wifi is on a lot and ar6k_wow seems to to be on a decent amount too. Next test will be removing the Facebook app despite me having it set to no notifications or syncing and see how things pan out since I know the Facebook app is notorious for battery drainage.
{
"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"
}

Strange battery behaviour

{
"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"
}
When I use the phone the percentage only drops in 30s multiples or 1s close to that.
Is this how it's supposed to be? I've never seen something like this before.

trc13 said:
When I use the phone the percentage only drops in 30s multiples or 1s close to that.
Is this how it's supposed to be? I've never seen something like this before.
Click to expand...
Click to collapse
10 precent in an hours so what's the issue???

underdog_656 said:
10 precent in an hours so what's the issue???
Click to expand...
Click to collapse
Who's got that battery? 1 hour sot in 10 minutes? That's what I need. The better I get is 40 min while watching videos. The issue is the percentage drop seems locked and the better I get is 5h sot without playing any games, only using social apps like Twitter/Instagram and setting FH+ screen. I already wiped, installed the less amount of apps I could, updated to the last firmware and nothing has really changed.

GPS Altitude fluctuating by 100s of meters

Hi,
I use different apps for sports tracking, mostly for paragliding and each of them records highly fluctuating altitudes. Here is an 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"
}
Practically, this was a very constant descent, so it should be more or less a straight line. My girlfriend uses the same apps but on a Pixel 4a and gets smooth altitudes. Factory resetting the phone also didn't help... So I really think, this a general problem with my particular phone or Pixel 3as in general. Does anybody else have such problems? Or even a solution?

The graph you posted only shows the end result and the reason for the fluctuations could be many things.
I would think the app or graphing software you are using would ignore readings that are over a certain threshold, so check the settings. Or you can just upgrade to a 4a.

Thank you! As it affects all apps I really think that it must be a faulty output of the GPS. As those tracks are always recorded in an unobstructed environment (the air ;-) ) I can exclude almost all errors discussed in your linked article. They would maybe explain 10s of meters of fluctuation but not ~500m. Those are also not singular readings but a couple of readings in a row, so not really outliers. I just wanted to check if there are others with the same problem or if my phone is defect.