Ok, I have searched and searched and cannot find a single person who has this same issue as me.
I use "content://com.android.calendar/instances/where" to get back instances based on the start date between values. I have a Nexus S with CM9 installed and this works great. My friend's Evo 4G with CM7 2.3.7 installed cannot. His says this is a bad url.
I had to resort to using events url and this is fine. However, his phone doesn't have the "availability" column. Also, events that might have changed start/end times seem to still come up in my query for just those starting in the next 15 minutes, for example, when they are starting the next day or later. I want to use instances but seems like I cannot.
Am I missing something here? I know they are undocumented apis but that doesn't stop anyone else from trying to use them as well. I just hope that there is some way to get the level of detail I need.
Any ideas? Thanks in advance!
So I found out by loading up CM7 on my second Nexus S that "instances" are indeed present. Possibly a RC or earlier then stable revision of CM7 had a bug in it. My friend loaded the latest and was able to get instances without issue.
Hopefully anyone else who might run into this issue will find this question helpful in their situation.
Related
I have an android application that's working fin in my tablet Galaxy TabA with android version 10, my application was tested in some other android version like 9,8.1 and 7. it all works well. after releasing the app to others, the app will not work on some devices that are exactly the same type "Galaxy TabA android version 10". however the application will work after doing one of these two options
factory reset to the device
debug one of these devices and adding a breaking points the application will work and the issue
will disappear even after running the application without debug.
Both ways the issue will not happen again at all.
This is very confusing and really I have no idea why such behavior will happen, I really hope anyone can help me in this. for information I'm using OpenCV 4 in this app ,tesseract 4, and com.google.android.gms:play-services-vision:15.0.0:15.0.0
I have finally managed to find the source of the issue, the problem I had was the implementation of TextRecognizer in google-vision-API. TextRecognizer.isOperational() API always returns false, and therefore my program crashes after that. The difficult part was, the code was successfully installed in multiple devices since I implemented this API, and only after few months my app was published, so I totally didn't expect the issue to be from there.
Here are some links that suggest how to solve such issues.
TextRecognizer.isOperational() API always returns false
Google Vision API Text Recognizer is not working
So I am one of several developers developing a GPS-app with the help of HERE SDK for Android.
This is a project that has been in the making for some time and it has been a somewhat smooth ride, until yesterday.
We have a couple of tablets to test our app with, and yesterday when building on the Samsung Galaxy Tab A(2016) the routing always gave us "GRAPH_DISCONNECTED" as an answer.
It doesn't matter what route I try. From current location. From a set location. The destination doesn't matter either.
So we have a CoreRouter.Listener that overrides the onCalculateRouteFinished-method and no matter what I do routingError seems to beceome GRAPH_DISCONNECTED.
I have tried to uninstall the app and install it again. Same result.
I have tried deleting the cache for the app. Same result.
The weird part? It has been working on the tablet for well over a year.
And if we use any other tablet, like the Xperia z4 tablet there is no problem with the routing.
Okay, so problem found!
Apparently, we had the wrong settings for the vehicle. It was too big to go from the positions we tried with, and that's why HERE couldn't make a valid route.
The strange part is that this route has worked with those vehicle settings before. So some construction must have come up all of a sudden that stopped me from making the same route.
Testing on Samsung Galaxy Note Edge, Android 6.0.1
PLEASE NOTE - this issue happens only on Samsung Phones with pre-installed "Smart Manager". If you have no experience with that constellation, please read in detail whats the real issue. This is irregular, not a usual debugging thing. Please don't expect a code snippet right now, there cant be one. At this point I cant post any reasonable line of code because the origin of those errors is COMPLETELY UNCLEAR. I have only 4500 lines, and 25 classes, but absolutely no clue where to pick a meaningful snippet from without any hint what Smart Manager complains concretely. It says just one word: "ERROR", but not when, not why, not what ... Mission Impossible 😩
I've researched a lot now, but found almost nothing being of help. My app is compiling fine without errors and running smoothly (and very fast!) as desired. I cant feel anything about "performance degradation", but Samsung "Smart Manager" has this very weird issue with my app...
Battery lasts for days on standby, no heat, nothing notably.
No information what kind of error should have been occurred at all. No more details to open, simply nothing!
My app does definitely not run in background. It stops, pauses and resumes without issues. No issues, no errors during building (Android Studio 2.2), no warnings about Smart Manager performance issues, this error pops up ONE WEEK LATER, or two or three. That's why I you have no chance to create a link between error and possible root cause to start tracking down. In that time you made lots of code changes before you get notified from SM the first time, lots of Git commits, but which one contains the change this external tool complains? That makes it a real hell.
I also let it connected for 5 days to USB, collecting tons of logs, crawling the logcat like crazy for any relevant events, but SAMSUNG's Smart Manager doesn't seem any need to log at least one word when it counts its ominous errors.
What I've found on the net, nobody really knows how to debug this, just very time-consuming guesses which I followed where applicable - without success.
What I've already tried:
Exceptions - all caught and handled
Removed all debug logging output
Checked for infinite loops
Checked for missing or damaged resource files
Disabled auto-translation
Checked for whatever could be irregular, suspicious or extraterrestrial 👽
And after making changes I must wait days or weeks if it will finally pop up again or not...
Could there be any way to catch those Smart Manager error count events and attach some whatever sort of logging to it? There is no documentation from Samsung anywhere, no support for this pre-installed app, no help at all.
The error message is very clear, 10 crashes in 1 week. I would clearly say that the app is sub standard.
You should start with implementing a Global Exceptional Handler or start using some specialized service such as "Crashlytics" in you App to understand what is going on.
I was wondering if there were any places to look for help on how to make a custom ROM for my Droid X. I do not know where to start though. I know some JAVA and am learning more. I just do not know how to code it. Where to start AOSP, Stock edits, or 2nd init? Any tips welcome! I will also later code for the Galaxy Nexus, when I get it. Thanks!
2nd Init is the way to go. In order to this do though, you have to make sure that you have a pretty beastly comptuer as compiling the code can take upwards of 24 hours depending on your system.
I am trying to wrap my head around Android Widgets, using the sample provided here: http://code.google.com/p/wiktionary-android/
I have corrected the strings.xml but the plugin will not work properly, neither on the emulator nor on the actual phone. It installs fine, but it never updates.
But at least on the simulator i get some DDMS output, telling me, that the API-response could not be parsed, so I assume, that the Wiktionary API has probably changed.
However, on my phone, the public void onUpdate(...) method doesn't even seem to get called at all when I install the Widget. I have inserted Log.i(...) lines for debugging and while they all show up when I use the Widget on the emulator, none of them seem to come up when it actually runs on the phone.
The phone is a Samsung Galaxy S II running android 2.3 but that hardly matters I think.
has anybody encountered this before and knows anything that might help?
EDIT I was told it might be a permissions issue, but could not verify this.
OK. Just in case anybody else ever comes across this. There is a strange thing with android widgets when the throw an exception... just uninstalling isn't always enough one hast to restart the phone.
Can not explain why that is but it always did the trick.