So this is a new type of issue I am currently facing, Recently I ran an APK of React Native Application I recently built on my system. After running that APK successfully. I started facing some issues regarding my phone's ** sound key **.
I tried restarting the device [Samsung], So it stopped showing the 1st issue. But after a few days a 2nd issue arrives.
1st issue => The volume up button stops working manually and starts increasing the volume automatically.
2n issue => Now whenever I write a new Text Message to someone it automatically starts increasing the font size of the text.
I gave a reboot to the device and even formated it, but nothing helped.
I want to know if it's a software side issue or hardware? So that before submitting the device to a Samsung store, If it's a software issue and if I can fix it. It will save me some bucks.
I actually solved this issue and that was due to the Hardware issue that has happened to my Android Samsung device and I researched it.
This type of issue was very common with users having that old version of smartphones and that is why new design keys for power and volume were introduced in most of the new smartphones which were launched in later 2016. This has actually reduced the key issues and if in case there is an issue, now it is easier to fix it since the keys are separated from the board as it was used to be earlier.
Also, some useful sources if someone is facing a similar issue in their old version android devices.
Volume Slider.
Volume button not working
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
I have been facing strange issue in my one of Android application with Motorola Defy device. I have been testing the same application on HTC and Samsung devices and it is running perfectly without any issue, however when I test it with Motorola device, it starts getting crashes.
All log files shows Adreno200-EGLSUB: : Format RGBA_8888 error. Let me add one more thing that I am using SurfaceView and surfaceHolder class.
Could anyone know what possible reasons might be and it can be sorted out?
Thanks in advance.
I met the same problem, I tried to set
getWindow().setFormat(PixelFormat.RGBA_8888);
But still returned the same problem. I run on several thousands times, no further error was shown related to this one.
According to answers Device specific error - s3dReadConfigFile "Can't open file for reading."
It will not affect the use of your application
i have it too,
just unlock your phone, and make it ready to use.
than run your app from software (Eclipse - in my case).
Ever since my Asus Transformer tablet was upgraded to Jelly Bean, I find that app and widget uninstalls are sometimes excruciatingly slow, as in taking several minutes instead of seconds. Could there be a reason for this?
The reason I'm posting this on Stackoverflow is that the apps I'm having the most trouble with are my own developed apps! As you know, when switching between debug and release builds of an app, you have to do an uninstall due to the different signing keys, so I do this on a regular basis and it's getting very annoying. Thanks for any hints on where to look for a solution -- if any.
I had this issue once, though it was in ICS and not Jelly Bean. The problem in my case was Google's app "Currents" which generated thousands of files as part of its cache. It took FOREVER to uninstall anything, or even get the size of any installed app because Android had to chug through all those thousands of files. Google has since fixed Currents, by the way.
So, I would guess that it's a similar issue, one of your installed apps is going nuts with creating files. If you open your app list and it takes a long time for the sizes to show up, that's further evidence that it's the same problem.
I had the same problem. In my case it was caused by SoundCloud's stream cache. After deleting it everything works fine again.
Same problem, also identified by extremely long time to calculate size of apps. In this case it was Google Earth App generating thousands of files (over 22000) on the local drive. Uninstalled that App
and it was fixed.
I'm testing on an HTC Sensation, running android 4.0.3.
I'm publishing using FlashDevelop 4.0.3 and using the Air Mobile AS3 App template.
All the application does is display a Rectangle using:
this.graphics.beginFill(0x00FF00);
this.graphics.drawRect(0, 0, 100, 100);
Just so I can see that its actually publishing something.
The app runs correctly if I publish to the desktop, however when I switch to publishing it to the phone, the problem I'm facing is that the application publishes and runs on the phone, but only for a few seconds.. usually about 4 seconds and then it crashes out.
The really weird thing is that it was working fine about a week ago.. I'm not sure what's changed since then, but yeah it started happening this morning, I tried everything I could think of... including stripping everything out of the app and also doing a factory reset of my phone... nothing seems to have helped...
has anyone else had this problem? or have any ideas on what might be causing it or how to fix it? any help would be greatly appreciated.
Cheers
Update:
it seems changing the render mode to "auto" instead of "direct" stops the crashing, which is great, however if you need to use direct for stage3d content this doesn't really help. anyone else having this issue?
Can you post the source code of your application? I do too have HTC Sensation but my firmware version is 2.3.6. It would be interesting to test it.
I just updated my XPERIA ARC to ICS and now I'm having problems with AIR apps as well. Seems the app is not getting the Click/Touch interactions. Some InteractiveObjects like TextInput gets the click and focus as it should, but Buttons are not working. And I'm using latest Flex/AIR sdks...
But I'm pretty sure we are in Adobe/Apache hands until they update the AIR with a fix.
Recently upgraded to the AIR 3.1 SDK and have run into a show stopping issue regarding InvokeEvent on mobile devices. The application is dispatching a new InvokeEvent each and every time you change orientation on the device. And it isn't clearing the "queuedEvents" array. Worst of all, the new event it dispatches each time is a clone of the last one recieved. In the case of our application, this would be parameters that tell the application to load certain data. So each time you change orientation, the application re-triggers that load sequence, causing lots of undersirable behavior.
The code is pretty simple to test out:
protected function preinitializeHandler(event:FlexEvent):void
{
NativeApplication.nativeApplication.addEventListener(InvokeEvent.INVOKE, onInvoke);
}
protected function onInvoke(event:InvokeEvent):void
{
trace(event.toString());
}
Now each time you change orientation you will see the trace statement and the event.target.queuedEvents collection continues to grow while never clearing any of the previously caught events out.
Rolling back to AIR 3.0 fixes this behavior. And I've been able to demonstrate that in two separate projects.
I'd love to hear of a fix or work around so we can release using 3.1, but either way, I thought I'd make others aware of this issue as I haven't been able to find anything about it through my searching.
For additional details on hardware: This doesn't occur in emulator or my LG Slate, but it does happen every time on both of our Xooms and our Samsung Galaxy Tab. It doesn't appear to be an issue with iOS.
UPDATE: Just updated to the 3.2 release candidate (3.2.0.2060) and the problem remains. Our software wont be able to update past 3.0 for the foreseeable future, which means we can't upgrade to Flex 4.6 SDK either, not without removing a significant feature of our application. This doesn't inspire us to the future of AIR in our company.
There are a few solutions and work around we might be able to employ to fix our specific feature, but there is still a concern over the effects of having an ever ballooning invoke queue that never clears. That could have additional issues over extended use of the application.
UPDATE 2: I put more details in the Adobe forum post. http://forums.adobe.com/message/4278518
Eric Jensen