Database Info

Accelerometer to detect Walking or Driving

Ok, so i have a tracking program i made for my phone in C#, basically it uses my GPS gets coords stores in db then uploads then to a server which tracks me on gmaps.... now we have little icons for a car or a person walking... but no way to tell the difference, so my idea was to use the Accelerometer to tell if i was walking or driving, but i have no idea where to begin or if this is even possible? ideas?

I don't know about the accelerometer but you may just want to put a speed cap on the "icons"
ex if your tracked speed is less than 10 miles an hour your icon would be a person, if higher than 10 your icon would be a car (maybe specify a time so that every time you stop at a light your icon continues as a car)

Tracks from Captivate Compared To Other Devices

Using JH3 with SuperRooter and lagfix.
Did play with LBSTestMode and change settings, but those settings did not change "jupiter.xml" which I believe is where the GPS stores its settings, since that is where we turn off the GPS Log File.
Even with decent locking, tracking doesn't follow very well. Attached images show the differences between the Captivate (Yellow Pins) and Treo Pro (White/Black Squares).
Will try a few things that I've seen and post up some more results after I drive to work in the morning.
Does anyone know name of a good NMEA logging app, to log the NMEA statements directly.
Attached images are snippings from google earth, showing tracks...

Only changes made is used Epic 4Gs jupiter.xml file from this thread:
http://forum.xda-developers.com/showthread.php?t=759641
I did see some improvements in tracking, previously all recorded turns or even lane changes resulted in an overshot track by over 100 ft, that took 10+ seconds to return to active track. These are from today's test with above changes, I drive 45 minutes to work, interstate, US Hwy, and city streets so its a decent test.
(EDIT) Red is Treo Pro recording NMEA with VisualGPSce / Blue is Captivate running GPS Logger from market (/EDIT)
Cap 1 is the only truly overshot at speed turn, at about 40 MPH, but the previous turn was perfect (in the same image)
Cap 2, only appeared on interstate @ 70 mph (on there 11 miles), had about 3-4 lil bumps like this that went off track by about 100-150 ft and returned, seems to last about 6 seconds but could be enough to throw navigation program off track
Cap 3, examples of improvements
Cap 4, examples of improvements

Joe, what's the red and what's the blue tracks? That way we can compare properly

dougp.me said:
Joe, what's the red and what's the blue tracks? That way we can compare properly
Click to expand...
Click to collapse
Edited post, that kind of slipped my mind since I knew the colors, but others need to know too DUH...
If anyone wants to know I used gpsvisualizer.com to convert the NMEA and GPX file to a track/waypoint based KML. I know I could get KML from GPS Logger, but I wanted to files with same format

Good research...
For comparison purposes do you also have a tracks of the PRE-Fix??? Like to see how much the GPS actually fixes it, that's not a placebo effect?

TexUs said:
Good research...
For comparison purposes do you also have a tracks of the PRE-Fix??? Like to see how much the GPS actually fixes it, that's not a placebo effect?
Click to expand...
Click to collapse
I didn't save any tracks before laying around in the 1472365 (LBSTestMode), but I believe any changes made in test mode are only a placebo affect. The first post is before changing jupiter.xml. I'm playing on the angle that that menu/program is exactly what it says, a "Location Based Services Test Mode" for testing different settings. Changes made there are saved in system.db but not in jupiter.xml
From the fact that you have to edit jupiter.xml to disable GPS logging in JH2/JH3 means that settings are definatly being pulled from that file.
I'm actually going to change the SUPL settings in jupiter.xml to the google ones and see what happens.

The first set of images is pre-fix and the second is post-fix?

TexUs said:
The first set of images is pre-fix and the second is post-fix?
Click to expand...
Click to collapse
Yes but last night record some more data and it was back to the tracks over shooting turns and accuracy being off by up to 100 feet so not sure what's up with this thing.
Can see all the satellites with decent signal, so I doubt its a hardware issue but more likely firmware or drivers depending on where the calculations are done.
I know the devs over in the kaiser and vogue forums did work to improver gps accuracy in the kernel.. It may just end up being a wait and see since we don't have source for the samsung kernel
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Governor app that can set profile for "text input active"?

Is there any speed-governor app for the Xoom that can be configured to lock the CPU to 1000MHz whenever the soft input area is active (or better yet, whenever Graffiti input is active), and/or a way to increase the digitizer sample rate?
Historically, Graffiti has been totally unusable on my Xoom. Literally, so low of a sample rate, and so many errors, that I just couldn't use it. I finally got around to unlocking and reflashing my Xoom to CM10 last night, and locking the CPU to 1000MHz makes it work a lot better... but the accuracy is still a cruel joke compared to even my creaky, old Hero overclocked to 711MHz.
It's pretty sad, actually. On the Hero, the digitizer seems to be reporting samples at least 4-16 times as often, and I can get nearly 100% accuracy without even trying. On the Xoom locked to max speed, it seems to do a tiny bit better than my S3 gets with stock, but the sample rate still appears to be absurdly low compared to what it was on the Hero, and feedback seems to lag the actual touch by at least 100-200ms. On the Hero, feedback was literally instant... stroke, and see the pixels turn white INSTANTLY under my fingertip. On the Xoom (locked to max), they start turning white a fraction of a second after I touch the screen, and I can see the last bit of the stroke render a fraction of a second after I lift my finger away. With the stock Xoom rom, it was more like, "draw the character, and see a jagged impression of it sputter into existence about a half-second later... maybe, MAYBE even getting recognized correctly about 70% of the time".
I'm guessing that either the Xoom's digitizer has a limited sample rate, or something in the kernel or driver is limiting the sample rate... but I'm still trying to find a straight answer somewhere about whether/how you can build a custom kernel without losing your ability to run paid Market apps. Or whether it's even necessary to go to that extreme, as opposed to something like a setting that tells Android to increase the sample rate, or not throttle the CPU when an input area is active, or maybe a way to let something like SetCPU identify "soft input area active" as a profile-triggering condition. I'm also pretty sure that the Xoom's kernel (if not recent versions of Android itself) try to treat the existence of a soft input area as an excuse to massively throttle the CPU, on the theory that it's just displaying a picture of a keyboard and waiting for a blunt press. HOWEVER, I'm SURE there HAS to be an equally-official way of defeating that behavior, if only because it would also screw up Android's ability to handle east Asian input methods.

[Q] Query about smartphone's accelerometer

Hi,
Is it possible to detect/measure car's acceleration or deceleration through a smartphone accelerometer ?
If yes, is it possible in all new smartphones ?
and how to implement it in android ?
Thanks

Depending on what you want to do, you'd have to figure out how best to filter out regular movement of a person just picking it up and putting it down, say - I don't know what the data on that looks like and how you could distinguish, et cetera. Or if the phone is sensitive enough to pick up anything meaningful beyond the sort of hard stop that would send it flying to the floor or whatever (they do seem pretty sensitive, but you'd have to test it).
You can determine speed using the GPS and it's pretty accurate (but this will use a lot of battery) and would naturally filter out small movements of a person using it within the vehicle. Implementation, I have no idea on that.

Increase Smart Phone Battery Life

Hi, firstly I'm sorry my english is a little bad )
Did you even harder to charge your smartphone is based on the first day? Here are tips that you fully based. Get away from the stress of the outside end charging of battery life and increase your phone.
1 - Home Screen Wallpaper and Theme you are using:
If you are using a smart phone with AMOLED screen, predominantly black wallpaper should be preferred. AMOLED technology while light colors such as white because it consume more power. LCD and SLCD screens, such a situation is not in question.
My suggestion is not to use an animated wallpaper for Android users in particular. Animated wallpaper, using the phone's hardware more. This is going to have to consume more power than the components.
Android users should note also displays add to the widgets. Widgets are always synchronized with the running and intense 3D graphics, as well as the equipment used for the data connection şarjınızı effects shot.
2 - Display Lighting:
It is best to leave the automatic setting of this area.
But I do not like to remain on automatic. If you need to talk I'm being honest, I always light at the highest level. Because all the ingredients here, and it will not have to perform the charging period will be longer.
But I do not want to go up to the maximum number of days gidebilecekse say it, my proposal is worthwhile to listen to. Big and wide screens of smartphones, especially in the light of day very well read. Do not force the phone to the light a little bit, then move to a higher level.
But it starts to get dark, shine your light, especially in the evening turn down the screen. Smart phones display lights to a minimum, even offers sufficient light in the evening. This is an effective tactic.
3 - Wireless Connections:
Smart phones are undoubtedly the most power-consuming units, wireless connections. WiFi, Bluetooth, GPS and 3G that are overviewed, 3G and GPS fully charge the enemy.
According to their attempts, with the closure of all wireless connections between all of them to be open to play at least half a day I've noticed.
For example, turn off the GPS. Only helpful both when business is active. Shortcuts available in Android and Symbian Belle. The option to turn on and off in a practical way. We also do not walk Bluetooth is on. It is also charged unnecessarily waste.
A clear grasp of 3G and WiFi when it is, let's not say conect. When connecting to open it. If you say'm going to necessarily turn off syncing on Android.
Sync / Sync, for a certain period of time it şarjınıza negative effect on the data are drawn. When you use the most sense to synchronize.
4 - Your RAM (temporary memory) Operate the program free to leave and at the bottom:
Most are at fault here. If you open up the application on the phone and waiting at the bottom. E, the processor is running at full speed all the time. The conclusion is obvious.
And then they were going at the charge of the phone as well as the complaints are coming slowly. Take a notebook and a lot of that time in the program's run, so let's wait. Let's see what is going to charge?
There are applications for the program terminates, especially Android. But most of these applications 24/7 has an adverse effect charging them for trying.
I would recommend this program to Android users. Download this app. Click on the widget closes all running applications. However, if you open the program by clicking the icon, you can see and what you want Implementations running off. I would recommend this method.
When you close all the system applications to open them again, the power turns off, and then spends the processor. Here you can download the program[/URL]
5 - Efficiently Manage Your Smart Phone Processor:
This section applies to users Root'lu. Root evaded users have this right, they do not die. Linux-based smartphones, especially those driven into exile in the market with a certain processor speed settings.
In general, the phones are set to OnDemand, the processor can adjust the speed according to the amount of use. For example, a 1 GHz processor that the phone does not work all the time at 1 GHz.
Their phone for the sake of example, a 1 GHz - 265 MHz range is running. I changed speeds. If you charge the phone and the maximum to withstand reduced from 500 to 128 can do. But later in your job will be completed on the processor to use 100% of himself. This will mean that the screen backlight to stay on and wait for you. I mean, at least let it charge the struggle, suffering Pull spend more charge.
I phone 1190 - 450 range using the. I can do my work as well as installing and getting faster. Charging time is important, 1190 - 128 range I choose.
Forget! Reduce the processor speed on the phone, when trading amplify şarjınızı. Because it is trying to slow the processor 100% to use and work will be completed on your screen light will stay open late.
6 - When charging the phone's battery Full Fill:
Do not say we already have would remove 100% charge to fill it. Phone software does not fully charge the battery. Leaves a certain margin of tolerance. Here we also benefit by it. In particular I saw that HTC Desire'da tried and successful. Each company's share of each model, it will not stop. But you can be on your left. Does not hurt to try.
Explaining the steps for:
-Phone up to 100% of full charge.
-Turn off the phone, remove and charge the phone.
-Install and charge the phone again, wait until bekleyebildiğiniz. (1-3 hours)
-Turn your phone into the phone, and remove the charge.
-Wait for your phone to do nothing between 2-5 minutes after opening. (Not attached to Sharjah)
-Turn off your phone again and again for at least half an hour into charging.
Remove and use the phone in the normal-charging. The procedure is finished.
This method has been calibrated with the battery is charging and fully. Enough to do this once. And then he goes to full charge.
7 - Special Edition Operating Systems Aim for:
Android users who root for in this Article. Made by the manufacturers of Android devices, phone skins, chargers doing negative effect on life.
TouchWiz, Sense interfaces, such as, the system is more tiring, as they lower the charge time. So we have the benefit of using a pure version of Android.
With pure Android versions like CyanogenMod custom Android versions sure to use similar interfaces. The term of charge with a very stretched. Will be surprised.
Of course, I do not recommend this method to anyone. Aware of the change and the risk of all the phone's Android software will recommend it to our readers.
Suggestions useful to you?

Thanks!!! i will follow these tips :good: