The boss noticed that my app doesn't work on his 4.1 device, so I tried it out on a 3.0 (we agreed to have API level 11 as minimum) AVD and yes, there were issues but more with the AVD itself after fixing the class not found stuff.
the AVD started in landscape
the keyboard was in chinese (with eclipse - stuck with chinese in android virtual device 's solution not working)
the contacts app crashes (yeah, I need a contact for my app but I can trick that as opening in incoming emulated sms allows me to edit the contact of that sender)
dragging apps to the home screen locks up the phone
even maps.google.com does not work in the browser
the homescreen menu does not work (at all. The buttons show but no matter which one I click, it just doesn't do anything)
… and yeah, there are issues with my app, but how can I assume they are related to my app and not to the totally borked avd?
If these symptoms ring a bell, please let me know as I'm kind of stranded. I already wiped ADT from my Eclipse and ~/.android from my file system and installed all newly to no success.
Edit:
Many of these bugs also appear in 3.2 although 3.2 is not landscaped.
4.2.2 works "fine". It only took 2 minutes to open the apps screen but on the first boot I won't complain.
Related
Persistent error on Samsung Galaxy Note 5
this is a weird issue that i am having for almost a year now, i'll try to be brief.
background story (What i think happened)
I own a Chinese aftermarket car infotainment system, running android 4.4. So, being the obsolete piece of **** that it is, i started digging around, and found out that it has something called Device link or something along those lines.
you have to download an app called EasyConnection from the play store, enable developer mode, and enable usb debugging, i know that's not the safest thing to do with Chinese stuff, but that's the only option i have at my disposal, so i have to manage.
anyway, it worked flawlessly for a year or so, then suddenly it refused to connect, with an endless connecting message. and my phone started giving me the Attention message, this was a year ago, and never worked since.
Attention
The connected device is unable to access data on this device. Reconnect the USB cable and try again.
Android File Transfer or Samsung Smart Switch must be installed on Mac OS X devices. To download Android File Transfer, go to https://www.android.com/filetransfer, or to download Samsung Smart Switch, go to https://www.samsung.com/smartswitch.
Phone behavior
Since then, whenever i connect my phone to my PC, either running windows or linux, it displays the Attention message. i can access files on my phone no problem, and it is not driver related, as this happens regardless of what driver is installed, or in the case of linux, no driver is required.
Android development
Now, a couple of months back, i decided to dabble in android development , as i have a couple of sysadmin years under my belt, and a beginner level knowledge of a couple of programming languages, so i thought android development would be fun, but here is the problem.
While my device is hooked up to android studio, i get this aforementioned error on random long intervals, but i am able to run my apps from android studio to my phone no problem. So i started to link everything together, and thought to seek help here on reddit after some fruitless internet diving.
note
I did a factory reset for my phone a month or so ago, so the only step remaining in my mind right now is to re-flash the stock firmware (i'm on stock for security reasons), but i am reluctant to do so because of the hassle of re-configuring my device again.
I'm hoping to accomplish the following :
Resolve the cause of the error.
See if my car system works with my phone after the error is resolved
Any help would be greatly appreciated.
I've Samsung S3 (GT-I9300) with Omega v60 ROM (Android 4.3) and Boeffla Kernal 5.8 (3.0.101).
I was using SuperSU and in the one of it's updates, it messed with the ROOT so my device now went from ROOTED to NON-ROOTED.
My device was working normally today, and sometimes when it's loaded, the phone feels like it restarted when actually it didn't restart, and Boeffla notification says that I'm missing root which is obvious for sure.
I didn't wait for the phone to finish it's frozen status and make this restart-like thing, so I forced restart it by long-pressing the power button.
The device was stuck at the loading screen for two times until I removed the battery for like 5 minutes and then re-inserted it and powered on the phone to see that it's behaving like I've installed a new fresh ROM.
I had a long list of To-do in my GO Note widget and now I'm not able to recover this list.
Is there any way to restore the GO Note widget list ?
I was thinking that since I did't format or anything, I may access that list in a form of RAW data.
When I try to add an account as maybe I had cloud backup or something, it gives me an 403 error with disallowed_useragent error so maybe I can work my way from there.
Thanks in advance.
I am having a strange issue ever since I installed eclipse on my mac mini (switched from windows machine). I am developing an opengl app on android and if I launch the app from eclipse, the android-opengl method OnSurfaceCreated() will be called randomly trashing the game (not supposed to happen). If I launch the game from the phone without eclipse this never happens. Also I have to unplug and replug the phone every time I want to build and launch from eclipse or else the phone doesn't appear as a choice. So I am suspecting there is something wrong with ADB. Any ideas? I have a samsung galaxy SIII. Is there a driver I need to install?
This happens to me too on Eclipse installed on my mac. I had to replug the device every now and then. The problem is only of the UI. If you drag a border on the device chooser UI, it will show up. See https://stackoverflow.com/a/26425489/1306419 answer on Just upgraded my OS X to Yosemite, Android Device Chooser not showing device - what to do? .
Also regarding OnSurfaceCreated() issue, please share the error that appears in LogCat.
I have some problems with SmartWatch2:
Sony Xperia Z1:
Accessory Version:1.0.B.0.60;
Host Application Version:1.0.12;
Smart connect: 5.4.8.
Verizon Samsung galaxy note 2:
Smart connect: 5.4.8.
My two apps do not show up in the installed application list in Sony Smart Connect. I really don't know what to do!
Does anyone have problems like this and solved it?
Many thanks.
Update:
I use "Sony add-on SDK 2.0" and SmartExtensionAPI, SmartExtensionUtils from this pack as linked libraries in my apps. Also "Sony add-on SDK 2.0" marked as a target platform for apps.
Update 2:
Another user with SmartWatch 2 write me that my app didn't listed on his phone smart connect app list.
I assume that you have tried the extension yourself on real HW and it works for you? Couple things you can tell them to try:
Uninstall the extension and reinstall it.
Unpair the bluetooth connection to SW2 and re-pair it.
Make sure:
Your SmartWatch2 extension gives the correct dimensions about itself
(i.e. the dimensions of the SmartWatch2 screen)
Your application maps correctly those dimensions, and transfers the control to your
extension
That was in case your extension never appeared on the SmartWatch2 screen. If it did, but does no more, restarting your phone normally helps. In more difficult cases, uninstall the SmartWatch2 app from your phone (it will be reinstalled once you pair your SmartWatch2 again).
I have a similarly problem but related to the development process. I'm working on a control extension app for SW2, and I was able to compile the code and see the app on the SmartConnect Installed Apps and then test it in the real device (i.e. SmartWatch 2).
After a couple of iterations on Edit code > Compile > Test, the app stops to show on the SmartConnect App list and on the SmartWatch 2 too.
I don't understand why this happens and its not clear what is the solution for this. Rebooting, uninstall, etc. Its like a random try&error solution, and leads to o much time lost on getting the app running again.
Sony SDK Team should give one word on this...
I am testing an Android apk in my JellyBean tab (Its a relatively new one in the market, I cant get the drivers and their technical help is also quite useless).
The problem is :
I want to see the log/trace files.
LogCat or any other similar apps can't see the log in Jellybean.
I can't see my tab under adb devices.
The Power + Volume button pressing stops the tab.
Is there any way I can see the log, without rooting the device (I am fairly new to Android, and don't feel very confident doing so)
I can see a “Select debug app” and “Wait for debugger” menu in the tab. Can they be used to debug the application?
Is there any way I can see the log, without rooting the device
No, other than to get and install the ADB driver for your device from the manufacturer.
The version is 4.1.1, I think the developer mode is from 4.2
The change to READ_LOGS was introduced in Android 4.1 IIRC.