Hi,
today i used my SGS2 for comparing my cars instrument with gps-speed. While driving with cruise control i got 122,4 km/h (this is around 75mi/h). This value was very stable, after a minute or so there was 118,x for some seconds and then 122,4 again. No values in between . That looks very strange to me, anyone experienced the same effect? (using Lightning ROM 1.3, with both "GPS Test" and "Maps (-)")
...Alex
Speeds as low-res steps
I'm having the same experience with mine and this behavior appeared suddenly. It doesn't matter what speed I'm going in or what app I'm using for measuring speed, they all show speeds in clearly divided steps with low granularity. In Locus Pro, the speed chart shows clear steps in recorded speed (I cannot post screenshot yet due to rookie status)
Both SpeedView and Ulysse Speedometer have the same behavior, though the jumps differ a bit. If I remember correctly some of the steps in Ulysse was (in km/h): 76, 80, 83, 86, 90, 94. Nothing between these.
Browsing through the recorded tracks in Locus I can point to the date this behavior started, but I have no idea what I did that day, unfortunately.
yesterday i've used runtastic, it works like expected, while the other two mentioned earlier still fail...
...Alex
Hi,
This is also something I've noticed. Using GPS Test I've found the "resolution" of the reported speed from the GPS to be 1 m/s, which is equal to 3.6 km/h. This explains why some applications seem to have steps of 3-4 km/h on the speed rating.
Fixed somewhere between ke2 and kf3
I upgraded my phone to from ke2 to kf3 today and this issue seems to be fixed now. Otherwise, see this thread for a similar discussion.
Related
I was curious about the max temperature for the CPU as I see many of these profiles setting up a reduction in OC if > 40. My problem is that I cannot maintain a temp below 40 with anything higher than 480 yet I see many people running 600-729. Could anyone shed some light on this for me.
skrumzy said:
I was curious about the max temperature for the CPU as I see many of these profiles setting up a reduction in OC if > 40. My problem is that I cannot maintain a temp below 40 with anything higher than 480 yet I see many people running 600-729. Could anyone shed some light on this for me.
Click to expand...
Click to collapse
The sustained max temperature you will see depends on what you are doing. Particularly if you have one or more radios going, you will experience high temperatures. For instance, streaming audio over the Mobile network or using tethering (WiFi tethering is the worst), it is trivial for the battery temperature to go above 50 C.
I saw 55 C once on my phone with a stock HTC 2.1 ROM (528 Mhz max) - I was streaming music, running a WiFi wardriving app, and also running the Nav app simultaneously on a 3 hr drive - in warm weather.
Unless someone on this board works as a thermal design engineer for HTC, it will be impossible for them to tell you what is too much - they would have to know what the thermal path from the processor to the battery is, and that's pretty much an impossible thing to guess at without pretty detailed calculations.
I set my temperature clamp profile to kick in at T > 50C; below that temperature, my phone runs at 768Mhz when it is fully charged. I would say that using the phone "normally" (as in extended internet browsing (reading, not video), texting, short phone calls), I rarely see my battery temperature above 40C.
bftb0
All application show wrong reading in temp it show abot 3.5 degree Celciuss and it's just not real..
Why >? how to fix that ?
The phone does not have a thermometer (Would be cool though) so you just need to specify the correct location but turning on GPS and Wireless network locations. If the correct location is set, there is nothing to do except for obtaining the temperatures from the server you determine your temperatures.
He is talking about CPU and battery temperature sensors. Mine doesn't work neither. Seems that only works in Fahrenheit.
I don't know how to fix.
Senate from my LG-P500h using XDA App
The fault is with the phone. When using certain battery apps, you're supposed to multiply the degrees by 10 to get the actual figure. So 3.5C = 35C
you do the same with 'v' except use 1000 so it'l be 4.000
and why exactly do it do that?, from what i've expirienced i figured it's a hardware problem, cuz i tried a lot of software modifications and got the same temperature readings.
So I have been using my phone to record my flights, and I have to say that I am impressed with the capabilities of the Galaxy S2 GPS receiver, it manages to keep tracking during the complete flight!
One problem though, the altitude reported by the GPS "saturates" around 6000m (20000 feet), it doesn't go any higher.
As anyone experienced the same behavior?
Wasca
I guess the altitude is set using setGpsAltitude function in Camera.Parameters Class used by our cam.
http://developer.android.com/reference/android/hardware/Camera.Parameters.html
I don't understand your answer, I am not trying to take a photo!
What I am saying is that, when tracking my position during a flight, the altitude reported by applications like GPS test and GPS status never exceeds 6000m!
Hope I made my myself understood.
Wasca
Ok. I don't know why i thought of camera
Afaik, GPS system has an altitude limit of 60,000 feet. Don't know why is it limited to 20,000 feet in your case.
Since GPS system uses a rough spherical model of earth to calculate our position, it works best when we are on the ground. But altitude calculation is a different story, since there is no surface as a base of calculation.
Altitude is calculated by measuring the distance from the centre of the earth and the radius of surface model (spherical model of earth). This way, it calculates distance/altitude from the surface of the earth. This calculation is affected by factors such as density of earth crust (relates to gravity), distance from GPS satellites, (~12,500 miles) etc.
For safety reasons, and to try and make calculation more accurate, GPS system uses an error bias towards the direction of earth. This way, on higher altitudes, GPS will tell you, you're lower than your actual position. That is why it says you are at 6000 m even when your altitude is higher than that.
If you notice the accuracy reading of your location at higher altitudes, error in altitude is roughly 3 times that figure.
Hope this helps.
Thanks for this information, it was also new for me.
I wouldn't say it is an accuracy problem. In this case, measured altitude seems to be ok until the plane reach 20,000 feet, then the altitude just stops increasing.
I think that google has flown the nexus up to 10km altitude, and the GPS kept measuring altitude.
It looks to me it's a bug of the GPS of our phone.
Wasca
Hello,
I have recently used my galaxy SII on several flights. Initially I had a Locus Pro tracking running, switched the Galaxy to flight mode but forgot to turn the power off during start. I noticed this during the cruise at an altitude of >10000m. At this time the GPS was still on, but the track had stopped at 5487m at a speed of 832 km/h.
During the cruise the GPS seemed to be still working, 10 sats were received (could also watch the varying signal strength). However, position and altitude didn't update.
Now turned off the unit completely and starting it up. After some time a plausible (current) position was shown, however, with a wrong altitude (<6000m) This position froze again. I used several other GPS Apps, all with the same result.
My conclusion from this is:
The Sirf GPS chip seems to works well at this altitude and speed.
Either the Android 4.0.3 and/or the Samsung SW must have a setting to limit the use above 6000m .
I have contacted Samsung several times to get information about the maximum Height and Speed spec. of the Galaxy SII. The answer was always that they will contact the specialists - but never came back.
What I would like to do is to find this limiting setting, modify it to be able to track the flight with my Galaxy.
Any similar experiences?
Same problem with other smartphones?
Any suggestion?
Thanks
Dietrich
Something to think about guys.
To start, let me tell you that my WiFi + bt speed is very reasonable, even at some distance from the router. My internet speed is 20mb.
Noticed yesterday that my WiFi went well below 1mb when paired with bt, and half my usual speed with bt off.Long story short, I realised that I changed CPU governor to userspace day before in System Tuner and forgot to change it back. Switching back to interactive brought my speeds back to where they were. While its not really useful info, I wonder why does CPU governor affecting WiFi speed with or without bt on.
Anyone?
Sent through the wormhole from my CoinInserted Sensation OG.
That is very interesting.. could just be a coincidence though.
I just switched to a newer TP, C2 serial and my wifi is a bit better but far from great. I do get those extremely weird spikes of extreme low and extreme high speed. I recently changed my router the a much higher end model (not high end but better, D-Link Dir 655 Xtreme) and it helped a bit but I still have a strange dead zone in my house that only affects the TP and no other devices. That and those moments were the speed decreases greatly.
I never could figure out what caused it. Could it be the governor adjusting itself on its own? Maybe related to Performance vs standard settings?.
As a new owner of the Z5C (rly impressed so far ) I couldn't help but notice the heat, courtesy of the SD810 I assume.
So i've started monitoring the temps for the past few days with CPU-Z and Cpu Temperature.
For the most part while doing everyday tasks such as phone calls, news, music, Whatsapp and so on the temperature is around 30-40ish which seems reasonable and causes no concern.
Whilst doing something more intense such as running a game, installing/updating app, or recording video the temperature jumps to around 45-60 which again seems reasonable.
There are sudden momentary (2 second) spikes to 70's 80's usually while doing heavy R/W tasks such as installing an app.
Battery temps usually hover around high 20's to mid 30's whilst doing normal tasks and during more intense tasks can jump up to around 40ish.
I was wondering if other users here who also bothered to monitor their thermals are experiencing similar results or not?
Also am curious to know if someone knows what the msm_thresh threshold is for the Z5C i've noticed mine topping at around 41..
Thanks
I have been getting pretty much similar results, albeit a bit lower temps due to disabling a few cores. Those temps are perfectly fine, as long as the battery dosen't get to the high 40's. The throttling stats when the battery reaches 43°C and clears when it get down to 41°C, you can find the throttling thresholds in the file called thermal-engine.conf located in /system/etc/