Locus Crashes & Reboots periodically

[Menion]

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, but not much useful at all ...

[wldbest]

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.

[Arcadia]

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?

[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. 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

[Arcadia]

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)

[rijackson741]

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.

[wldbest]

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)

[Menion]

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

[wldbest]

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.

[Menion]

did you read first post on this page from rijackson? he have 2.3.4 OS, so try to update if you can ...

[wldbest]

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.

[Arcadia]

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)

[Menion]

hi,
  as was mentioned before, read please this link. Let me know if this error occur also after update

[Arcadia]

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.

hi,
  as was mentioned before, read please this link. Let me know if this error occur also after update

[Menion]

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