Hello,
I use Locus Pro & Nexus one.
I have made 2 sqllite maps includes maps of korea, qingdao.
it has 2 categories and 50 + 40 POIs.
I rebooted the device and then ran locus and started tracking.
then switched to system home and/or lock screen, and then did nothing.
about 10-20 mins from run, it crashed and rebooted automatically.
sometimes it lasts about 30-40 mins.
I think it's not normal.
wierd thing is ..
I suspect that GPS turn on/off function has some defacts.
whenever i turned on LCD(press power btn) from system lock screen, locus always tries turn on GPS..
(whenever i don't use save tracking & location monitoring.)
I think previous version was much stable than today's new version.
While crashes all the time, I can't use this program ..
Please check the problem.
Thanks.
Hi,
hmm interesting. Are you using any custom rom? If is Locus trying to launch GPS, it have to be because when you ended Locus last time, you had GPS enabled. Anyway by your description I have no idea where to search for any mistake. You can help me, if you download program called CatLog, start it and from menu choose record, and let it run. And then try to crash Locus again. I hope that in log that CatLog program do, will be error that occur in the end.
Anyway really weird is that Locus cause restart of whole phone. It looks more on some system problem then on problem in my code
[attachment=0:1zbyad4g]2011-07-15-22-06-52.zip[/attachment:1zbyad4g]Here is the error log file.
When locus & system enters powersave mode(screen off),
the crash occurred ..
please check the file
----------------------------------------------------------------
last recoded lines before crash..
07-15 22:11:48.970 D/GpsLocationProvider( 92): android_location_GpsLocationProvider_read_sv_status+
07-15 22:11:48.970 D/GpsLocationProvider( 92): android_location_GpsLocationProvider_read_sv_status- :2
07-15 22:11:48.970 V/GpsLocationProvider( 92): SV count: 2 ephemerisMask: dffffffe almanacMask: fffffffe
07-15 22:11:48.970 V/GpsLocationProvider( 92): sv: 24 snr: 1.47 elev: 17.0 azimuth: 61.0 E A
07-15 22:11:48.980 V/GpsLocationProvider( 92): sv: 17 snr: 1.46 elev: 70.0 azimuth: 341.0 E A
07-15 22:11:49.889 V/libgps ( 92): DeferredActionThread pthread_cond_wait returned
07-15 22:11:49.889 V/libgps ( 92): ext status nmea report: $GPGSV,4,1,16,24,17,061,14,17,70,341,14,02,05,258,,04,45,274,*77
07-15 22:11:49.889 V/libgps ( 92):
07-15 22:11:49.899 V/libgps ( 92): DeferredActionThread pthread_cond_wait returned
07-15 22:11:49.899 V/libgps ( 92): ext status nmea report: $GPGSV,4,2,16,09,,,,10,21,202,,11,07,080,,13,07,136,*4D
07-15 22:11:49.899 V/libgps ( 92):
07-15 22:11:49.899 V/libgps ( 92): DeferredActionThread pthread_cond_wait returned
07-15 22:11:49.909 V/libgps ( 92): ext status nmea report: $GPGSV,4,3,16,20,48,057,,23,17,108,,27,,,,28,41,194,*4D
07-15 22:11:49.909 V/libgps ( 92):
and I dont use custom rom, it is genuine nexus one rom.
I use csipsimple, sometimes it gave me an error message - permission denied.
I have a Nexus One, and have not seen this problem. To check the latest version I recorded for 2 hours today. Everything was fine.
thank you for log file, unfortunately as you saw by your own, in the end of file is no error message. Nothing that should show something interesting and something that should help. I'm sorry for that but I'm worried that this have to be some problem with your phone. Did you noticed similar behavior in any other application that use GPS intesivelly as Locus? May you try another (My Tracks for example) application for track record?
you may also try another rom but by me, it's too much work :). So If you'll want, I can of course offer you refunding of your order, because in this case I probably will not have any solution .. unfortunately.
This sounds very much like the same problem I have been fighting with for the last 4 months. Refer my thread " Serious phone hang issue while recording - test results".
'wldbest' is saying "When locus & system enters powersave mode(screen off), the crash occurred ..". This is exactly what I observed dozens of times. After trying all kind of settings and tests, Menion recommended me to try another memory card. After I did that 4 days ago, I haven't had any problems at all.
Even though memory cards are speed classified, that class is minimum guaranteed speed. Because of production tolerances, there will always be a distribution of speeds of the actual cards from different production lots, some may be at the guaranteed minimum speed, but several will also be faster (I am designing integrated circuits and know these details very well, so trust me).
So my point is that if several processes are writing to the memory card at the same time, some writes may be queued and take longer time. If a process doesn't handle timeouts correctly, it will certainly crash. I am pretty sure that when you turn on/off the screen, there is some status writing to the memory card. That can explain why I found most crashes to happen when I turned on/off the screen. I was using a 32GB Class 4 card when I had all these crash problems. When I changed to an old Class 4 8GB card, I haven't had a single crash - so far (just 4 days of experience)! Even though same speed class, the actual speeds may be slightly different such that one card works smoothly and the other card causes crashes. I am now waiting for a new 32GB Class 10 card. That should at least solve any speed related issues, so I am crossing my fingers. You may want to try same thing.
Perhaps this is a little off-topic, but then again perhaps not. I am intending to get a new 32Gb card to replace my existing 8Gb card, and I have been trying to work out what speed class to get. Opinions about this on the web seem to be all over the place, with some claiming better performance with class 10, and some claiming class 4 has no benefit over class 2. In particular, it is claimed that class 10 cannot have any benefit over class 6 unless you have a high speed bus, because the bus will limit the throughput (see //http://www.sdcard.org/developers/tech/speed_class/). Perhaps as a chip designer you can address that point? Anyway, perhaps we can answer this question, and at the same time see if the card write speed is maybe the problem for Locus (which makes this post on-topic :) ) I installed this app: //https://market.android.com/details?id=ales.veluscek.sdtools&feature=search_result. On my current card (I forget what class it is, and it's not marked) I get 6.4Mb/s write and 22.7Mb/s read. So the question is, how does this compare to the speeds others are seeing when Locus does or doesn't have problems?
rijackson741 - your question is really, really good. When you want to buy a memory card for your devices, this big question always pops up: which speed class do I really need in this device? And it is almost always no clear answer, no device spec, no guideline. It is absolutely true that a higher speed memory card has no effect if the memory channel becomes the bottle neck. But flash memories are extremely slow devices when comes to band width. This is due to the semiconductor physics behind the storage technology. RAMs and flash memories are using completely different technologies. We use flash memories for two reasons: storage density and non-volatile capabilities (keeps stored data without power). So when you power on a device, it takes time because programs and data need to be copied into the fast working memory - RAM.
So back to the band width: class 4 = minimum write speed 4 M bytes. I do not know the bus controller used in the phones for the memory port, but to handle the 10MB speed of Class 10 devices is really a piece of cake. Compare to USB 2.0: channel speed 480 Mbit/s, i.e. about 60 Mbyte/s. These numbers are not exact due to overhead in bus operations and protocols. So I can't believe the bus controller to a memory card can be the limiting factor (but as I said, i do not know which controller is being used). You may not find phone operations faster with a class 10 over class 4, but you *may* solve burst write problems. I never had any phone crash problems before I instaleld Locus, and I don't know how/why Locus is involved in this. Menion has been very cooperative and did his very best to help me for a long time. The last thing to try now, was another memory card. And so far, that seems to make the difference.
What can class 10 do for you? You will certainly not need that bandwidth over time, but the point here is to be able to handle a burst of read/write requests. The a class 10 card will certainly be able to handle the queue in a shorter time than a class 2 device. When I bought my first 32GB card last December, I was even wondering if I needed class 4. There is a significant price step between the speed classes, and at that time class 10 was up in the skyes. The memory card issues that seem to be the root cause of my phone crashes, may not be the speed class, but could very well be initial production problems since I got hold of one of the very first 32GB class 4 microSD cards that became available on the market at that time. The web shop where I bought the card accepted a replacement without any further questions. And to rule out any possible bandwidth related issues, I decided to spend the little extra now between class 4 and class 10.
nice topic guys!
just a little information from my side :) ... I rewrote part that store data on card. Added some "batch" saving so only ten points at once will be stored and also with little bit different way, so please mainly wldbest, test next market version (maybe tomorrow because of some more fixed bugs)!
and you can continue with interesting discussion :)
svartbjorn: Thanks. What you say about the bus speed makes a lot of sense. I couldn't find specs for the speed on the web (which surprised me a little!), but I did find something on the Panasonic web site that implied it's 22Mb/s. That's consistent with the read speed I measured. For sure, unless the bus has different speeds in the two directions it must be able to handle 22Mb/s, because I can read data at that speed!
I am curious though. Did you measure the speed of the card that seemed to be causing problems with Locus?
Regarding read and write speeds - yes they are always quire different for all flash type memory cards. The speed class is always referring to guaranteed write speed. Read speeds are typically 5-6 times faster. This is due to the semiconductor physics how data are stored into the memory locations.
Regarding my 32 GB class 4 card - yes, I measured the speed to be exactly 4MB, so nothing more than min spec..l
Hello,
Here are new log files. (at least 2 times crash)
I have tested My tracks recording during 20 hours without stopping,
and I had no crash yet.
It seems that there are no problems in getting gps positon & writing on my device.
=========================
SD Card Test Result -
Writing Speed : about 6 MB/s
Reading Speed : about 13 MB/s
HTC Nexus One Bundled SD Card 16GB (SU16G)
Menion..
In my case, it seems saving is not so critical factor of crash.
I have tested more cases and got some more strange ones ..
Case Detail:
After reboot,
Just run Locus Pro,
- No Track Recording
- Just run in Offline Map Mode
- GPS Monitoring(Current Location) ON
- Turn Off the Screen.
DO nothing,,
After 3-10 mins,
The crash & reboot occurrs..
(No other apps make crash like this.)
I can reproduce this crash at any time.
Here is log files of those cases, but I can't find critical error messages causing crash.. :cry:
Unfortunately,
Updated version of Locus pro has the same problem.
Recently, I noticed a strange behavior of locus.
Whenever I turn on GPS Beep Option, it always beep !
I think it must beep only once after getting initial GPS signal.
But It constantly beeps while i can see 5~6 satellites in GPS window.
Is this a normal situation?
If it's not normal, please check gps modules.
****************
Hmm..
When I set GPS interval to 0, It beeped only once.
so It maybe a normal case.
I'll check more and report any findings later.
pretty interesting. I suggest keep this setting to default "0" value.
I also found one note
"If the device is rebooting, the interesting information will be in the kernel log. The log from the previous run is saved off and will be included in the "adb bugreport" output.
Look for /proc/last_kmsg and anything in /data/dontpanic/."
if you have rooted phone, or anyone with similar issue, may you look into this directory for some crash logs?
EDIT: also found this http://www.google.com/support/forum/p/G ... 7066&hl=en (http://www.google.com/support/forum/p/Google+Mobile/thread?tid=47e1e8be99b27066&hl=en), but not much useful at all ...
Here is a last_kmsg file.
I hope this is what you want.
A few months ago, I replaced my GPS module with mother board in A/S center.
because of bad GPS status.
So i suppose h/w is fine.
I have same problem like him.
I have made 2 sqllite maps includes maps of Korea(2 parts) and 2 categories.
But no POIs.
When I use 'Track Recording', small times later, my 'Nexus One' rebooted automatically.
(About 5 mins I think.)
What can I do for U, menion?
wldbest thanks for log. This error is my nightmare. Only I found from log is this topic http://forum.xda-developers.com/showthread.php?t=713841 (http://forum.xda-developers.com/showthread.php?t=713841). Unfortunately you say that you have no similar error in any other application ... and I have no idea what to change to avoid this.
it looks that this problem occur only with GPS on right? I'm looking to code of My Tracks and they create GPS connection in exactly same way. Damn
so
1) when you have GPS disable, no restart
2) when you enable GPS, (and leave track recording disabled), restart after few minutes
3) in other softwares no problem
is this correct?
So may anyone try Bluetooth GPS in Locus, to eliminate part of code? I'm anyway really worried that this will not be fixed
In my case,
1) when I have GPS disable, no restart - no trouble
2-1) when I enable GPS (and leave track recording disabled) and don't move(like walking) - no trouble
2-2) when I enable GPS (and leave track recording disabled) and move(like walking) - no trouble
3-1) when I enable track recording(GPS enabled before) and don't move(like walking) - no trouble
3-2) when I enable track recording(GPS enabled before) and move(like walking) - trouble. Restart Nexus One after few minutes
4) in other softwares(like My Tracks) no problem
My android's version is 2.3.3 (Korea, KT)
Quote from: "Arcadia"My android's version is 2.3.3 (Korea, KT)
In the link Menion posted above it says it was fixed (or at least something similar was fixed) in 2.3.4. //http://www.google.com/support/forum/p/Google+Mobile/thread?tid=47e1e8be99b27066&hl=en
What I have on my Nexus 1 is 2.3.4 (en-us), and I don't see this problem.
menion,
I figured out what was wrong.
My device has some defects in gps module,
so it generates some bad data periodically(about every 10~30 secs).
If you filter those noise out, I suppose there will be no more crash.
So please add some filtering module.
I tested Rmaps and OruxMap, they had the same problem.
But In Google Maps and MyTracks, there are no problems.
I suspect that filtering makes that difference.
Locus & OruxMap display popped data as normal(no popping track), but crash and reboot.
But Rmaps displays popped data as popping :), and crashes with an error message.
So i found out the reason.
Here are Rmaps error messages..
-------------------------------------------------
Your message:
RMaps: 0.8.7.3
Android: 2.3.3
Device: mahimahi google passion HTC Nexus One passion_kt
java.lang.RuntimeException: Unable to start activity ComponentInfo{com.robert.maps/com.robert.maps.MainMapActivity}: android.view.InflateException: Binary XML file line #77: Error inflating class <unknown>
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1647)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1663)
at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:2832)
at android.app.ActivityThread.access$1600(ActivityThread.java:117)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:935)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:3683)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:507)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:839)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:597)
at dalvik.system.NativeStart.main(Native Method)
Caused by: android.view.InflateException: Binary XML file line #77: Error inflating class <unknown>
at android.view.LayoutInflater.createView(LayoutInflater.java:518)
at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:568)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:623)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:626)
at android.view.LayoutInflater.inflate(LayoutInflater.java:408)
at android.view.LayoutInflater.inflate(LayoutInflater.java:320)
at android.view.LayoutInflater.inflate(LayoutInflater.java:276)
at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:207)
at com.android.internal.app.AlertController.installContent(AlertController.java:205)
at android.app.AlertDialog.onCreate(AlertDialog.java:251)
at android.app.Dialog.dispatchOnCreate(Dialog.java:307)
at android.app.Activity.createDialog(Activity.java:886)
at android.app.Activity.restoreManagedDialogs(Activity.java:871)
at android.app.Activity.performRestoreInstanceState(Activity.java:817)
at android.app.Instrumentation.callActivityOnRestoreInstanceState(Instrumentation.java:1096)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1625)
... 12 more
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.constructNative(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:415)
at android.view.LayoutInflater.createView(LayoutInflater.java:505)
... 28 more
Caused by: java.lang.OutOfMemoryError: bitmap size exceeds VM budget
at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:460)
at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:336)
at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:697)
at android.content.res.Resources.loadDrawable(Resources.java:1709)
at android.content.res.Resources.getDrawable(Resources.java:581)
at android.widget.ScrollView.setOverScrollMode(ScrollView.java:1395)
at android.view.View.<init>(View.java:1879)
at android.view.View.<init>(View.java:1921)
at android.view.ViewGroup.<init>(ViewGroup.java:292)
at android.widget.FrameLayout.<init>(FrameLayout.java:88)
at android.widget.ScrollView.<init>(ScrollView.java:145)
at android.widget.ScrollView.<init>(ScrollView.java:141)
... 31 more
-------------------------------------------------
Your message:
RMaps: 0.8.7.3
Android: 2.3.3
Device: mahimahi google passion HTC Nexus One passion_kt
java.lang.OutOfMemoryError
at java.io.ByteArrayOutputStream.expand(ByteArrayOutputStream.java:91)
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:216)
at java.io.BufferedOutputStream.flushInternal(BufferedOutputStream.java:190)
at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:83)
at java.io.FilterOutputStream.close(FilterOutputStream.java:60)
at java.io.BufferedOutputStream.close(BufferedOutputStream.java:157)
at org.andnav.osm.views.util.StreamUtils.closeStream(StreamUtils.java:62)
at org.andnav.osm.views.util.OpenStreetMapTileDownloader$1.run(OpenStreetMapTileDownloader.java:140)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1088)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:581)
at java.lang.Thread.run(Thread.java:1019)
hmm message you post here is some problem with image loading from server. OutOfMemory in some stream is probably on place where RMaps saves data to card ...
I think it have nothing to do with GPS issue
hmm..
Because of the bad gps data, It tried to read unusal tile areas at once.
GPS popped to some other places..
So I thought that can be some causes of problems.
did you read first post on this page from rijackson? he have 2.3.4 OS, so try to update if you can ...
Yesterday, I reset my device and then had installed only locus & rmaps.
But I experienced the same problem in both apps.
So, today I visited customer care and had explained errors in detail(that was a tough one).
They will replace my motherboard again.
Service guy said that my device has some unusual heat.
I think it was a problem of bad GPS output + software.
When I get repaired phone with new motherboard tomorrow, Locus may work fine.
Thanks for your patience,
I'll report the result later.
First, sorry to my bad english.
I think, I found it when Locus crashed.
I've tried a few different ways to test. And in some situations, make sure that the error had occurred.
(It just google translation. sorry.)
In my case, start Locus, then
1) GPS off, Track recording disable, Locus foreground work, Phone(Nexus One) screen on - no trouble
2) GPS on, Track recording disable, Locus foreground work, Phone(Nexus One) screen on - no trouble
3) GPS on, Track recording enable, Locus foreground work, Phone(Nexus One) screen on - no trouble
4) GPS on, Track recording enable, Locus background work, Phone(Nexus One) screen on - no trouble
5) GPS on, Track recording enable, Locus background work, Phone(Nexus One) screen off - trouble. Restart Nexus One after few minutes
*) in other softwares(like My Tracks) no problem
#Locus foreground work = I can see Locus in phone screen.
Locus background work = I can see homescreen(not Locus) in phone screen.
#Phone screen off = Android screen timeout.
Yes. This crash occurs only when the screen is turned off.
I use Nexus One. OS: android 2.3.3 (KT, Korea)
hi,
as was mentioned before, read please this link (//http://www.google.com/support/forum/p/Google+Mobile/thread?tid=47e1e8be99b27066&hl=en). Let me know if this error occur also after update
Sorry. I can't do that.
Because, Korea's carrier, KT do not support updates after android version 2.3.3.
(Nexus serise's OS support country's carrier. Korea's carrier is KT. Not Google.)
I asked them(= KT) and I got this answer.
They said, "We updated it as Gingerbread.
There is no critical bugs, so we don't have any further plans for update."
In my opinion, they will update 'Icecream sandwich' but there's no more update for 'Gingerbread.' in the future.
So, I hope. Please fix this crashes & reboot trouble on android version 2.3.3.
Quote from: "menion"hi,
as was mentioned before, read please this link (//http://www.google.com/support/forum/p/Google+Mobile/thread?tid=47e1e8be99b27066&hl=en). Let me know if this error occur also after update
I have no idea how to fix this. I use same mechanism as My Tracks (as I looked into their code about a month ago) for receiving GPS, so I really have no idea where is problem and mainly how should be solved
menion,
In my opinion, Locus only having troubles when the screen turns off. Like screen timeout.
Can you check this, track recording when the screen turns off?
... I understand that there is some problem only during "screen off recording" but I do nothing in Locus when I turn off screen, really. i only check immediately if I should turn off GPS or not, and nothing more. Isn't there rather chance to download somewhere update patch for your phone? N1, as official phone from google should have full support no matter of place you live