-
Notifications
You must be signed in to change notification settings - Fork 603
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ALARM_COUNT expected Integer but value was a java.lang.Long - GPSLogger stops #337
Comments
If you change that line from
to
Does it work? Also, what's your phone/OS? |
No, same error, |
OK very unusual, the alarm manager is simply what the OS delivers to the application. It should always be integer. What phone and OS are you using? |
I run android studio on arch linux, with a moto g lolilop phone. |
So I haven't been able to find anything on this. Everything points to this field being an int so there's no reason for it to behave differently. I tested this on a coworker's MotoG, no problem. If you are still debugging this it might be worth changing the line to I had a thought that the value might be 231-1, but that would require over 68 years of pending alarms. I'm pretty sure Android hasn't existed that long. That value might hold some clue. |
Thanks for your efforts,
If I changed getInt to GetLong, I have now
They say they returned 0, but when I watch it, it is 1, (but the logging In both case it is the same error, weird! |
I am seeing the same problem here:
and nothing is recorded. My phone (a Moto G 2nd gen with lollipop too):
|
Two Moto Gs, similar problems. Hmm. Was your device asleep for a while when this happens? |
What I always do: start gpslogger, close it (it keeps running in background) and then I lock the phone. |
Thanks but no need for that, the documentation says one thing, the phone does something else. 😭 I've put a try catch around that bit, it's the best I can do. Here is a test APK if you want to try it. https://www.dropbox.com/s/m74rez6qlserqfe/gpslogger-65-logview.apk?dl=0 Note that this is from my working branch so... there may be a few features not yet released. |
Will test it and get back to you later. |
I have this error:
The error appears only one time in the logs, after that nothing seems to happen and no point are recorded |
Indeed, still seeing this:
|
(Deleted my previous comment please see this instead): Did the log file show a Let's try again - new APK: https://dl.dropboxusercontent.com/u/51905631/gpslogger-65-logview3.apk To be sure it's the right version, the General menu version should show |
Nop I don't have that in the log file On 15/08/2015 09:08, mendhak wrote:
|
Do you have the right version - General menu should say "GPSLogger version 65-logview3" |
yes of course, On 15/08/2015 11:19, mendhak wrote:
|
If you are still playing with the code, can you try this, go and change
to
This treats the value like an object, compares to string. |
I can't compile the APK but I can test without any problem if you create one. |
OK I've uploaded a new APK: https://www.dropbox.com/s/4btz34gowc4ja77/gpslogger-65-logview4.apk?dl=0 Make sure that the version says |
Haha that makes sens, but now it works !! On 16/08/2015 20:21, mendhak wrote:
|
Seems good too. |
OK if that works I'll just... leave it in there for the next release. I even had a hunt through the Android source code to see what's going on - it's an int. It insists it's an int. Theoretically nothing should be different in MotoG Lollipop. They should do an X-Files episode on this. |
v66 released |
The app doesn't work anymore for me, it logs the first point, and some passive points but doesn't wake after the delay it should.
When I debug the code, the problem is
So problem in conversion line at com.mendhak.gpslogger.GpsLoggingService.HandleIntent(GpsLoggingService.java:283)
The text was updated successfully, but these errors were encountered: