Android V4.4

[Kum Filteau]

Soif you need to create an android 4.0.3 version simulator, I still recommended you to use the Android Studio, the Official IDE for Android. It will be quite simple to create such a simulator.

When you install Android Studio, you could you could use the already installed Android SDK, because there's no need for you to download it again. I have written an answer about it and I write it here again:

I am having a similar problem, I have an Officejet Pro 7590, connected to my home wired network, and I am trying to print from my Android 4.4.4 devices, a tablet and a phone. I have both the HP Print service plugin and the HP ePrint app installed.

Both services are able to see and recognize my printer, however when I select print with the Plugin service, the print job just sits in the que, saning sending. Or there is a message that says the printer is unavailible.

I'm not sure what you mean by "wired". Suggest as the last post implied that you check the suitability of your printer on the HP website. If it is OK then make sure you have the latest firmware installed - this is downloadable from the HP Website. Then as I did and as a precaution, recycle power on your android device.

I forgot to say that the statement " E-All in one printer can only print on a mobile device" from another post could be misleading. My Laserjet was not sold as an eprinter (but was wireless) - the firmware update made it so.

4.We have done the notification align with android 10 permission rule (cannot start activity in background), that is we are sure of that we zoom is randering in a launched activity and there will be a foreground notification binding to it in the meeting life circle.

Thanks for the post and thank you for providing all the information. As you have mentioned that your users are in China, and you are using Custom UI, did you implement the real-name SMS authentication part?( -sdk-android/blob/master/mobilertc-android-studio/sample/src/main/java/us/zoom/sdksample/inmeetingfunction/customizedmeetingui/view/RealNameAuthDialog.java).

Thanks for the reply. Could you provide the SDK log so that we could further investigate? Are you using Zoom default UI or Custom UI? Is the meeting that has issues locates in China? Is this happening on certain devices or all devices?

It happen on all the devices, creating a meeting seems to be ok but all cannot join. We did nothing but just upgrade sdk from v4.4 to v4.6. Assuming the log feature is enable, how can I see the log from zoom? which tag should I filter?

Thanks for the reply. The log feature could be enabled at SDK initialization, and you may find the instruction here: -sdks/android/mastering-zoom-sdk/sdk-initialization#2-log-feature, once you enable it and encounter the issue, please send us the log file so we could further investigate.

Thanks for the reply and the log. Yes, the log is encrypted to protect your privacy and we will only decrypt it for troubleshooting purposes. I will forward this to the engineering team to investigate and get back to you shortly.

Glad to hear the problem was resolved. You could get the error code(and all other info) shown in the log from the return value of each interface. You could simply print them out and troubleshoot from there. Happy Zooming!

When attempting to open Firefox after this morning's update, I received only a message saying this version (armeabi-v7a.15) won't work. I've searched the site for advice about what to do, but the only relevant stuff I've found indicates that it should work on Android 4.0. I don't know what to do next - other than give up.

Actually, I've been trying to do that this morning, in the hope I could revert to an older version which would work. But I can't even find out how to uninstall things! None of the settings screens are giving me the option to do that. There must be a straightforward way to do this, which would be easy on my desktop, but I can't find it.

I too have had exactly this problem today. I run an A500 tablet on Android 4.0.3. Its old but firefox always ran fine until today. I checked the firefox version=53.0. So I uninstalled it, went to Play Store and downloaded FF. V53.0 came down and installed without error and I am back to the error msg quoted above. Any ideas? My wife cant order stuff!!!

Oh. So, even if I'd managed to find out how to uninstall it, I would still be having the problem. Now I'm also feeling somewhat cheesed off that several of us seem to be having this problem and we're out on our own here. Can't Mozilla help? I'm reluctant to check with Android in case this is all part of G*****'s world domination plan...

Almost 100% certain its not an Android problem and I have confidence Mozilla support will sort it. It must be tricky to check every FF change against every version of Android out there. The FF check to see if its running on a supported OS must have a very simple to fix buglet esp. as the error msg erroneously indicates it thinks it running Arm architecture.Your tablet might have its original browser still available for use till the problem gets fixed.ps My wife says the error msg started yesterday evening not today. If I get time I might try installing FF 52

You obviously understand more than me about the error message. You're right, I can still use the original browser, up to a point - I downloaded Firefox when the browser couldn't cope with various tasks, so it has its limitations. I'll be interested to hear how you get on with installing FF52.

well as expected reverting to firefox 52 got rid of the problem. I have also altered google play so it doesnt auto update back to 53 again. Pity it just updates and breaks FF without warning + gives a msg indicating I have downloaded the wrong version ! Looking at bug info It looks as though this wont be fixed so its either go back to 52 and stop updates, move to another browser, or junk your tablet

Finally managed to uninstall FF53, but FF won't let me reinstall an older version. Further investigations on this site, via my old browser on the tablet, have shown lots of people cheesed off with FF53, some for the same reason as me, some for several other reasons. Fingers crossed, it seems to be working OK here on the desktop, but I'm sorry to be bidding farewell on my tablet.

Once you've uninstalled FF53, google for firefox 52 APK and download that, then install it. I think I got FF52 from androidapksfree.com/ apk/firefox-apk-for-android-latest-version-download/once I had avoided all the adverts in other places. (scroll down to see the older versions). Uninstalling FF kept my favourites etc.Check FF52 works ok, then goto Play Store and set it to stop updates (It will stop all updates which doesnt matter too much on old Tablets if you ignore the lack security updates!My wife has confirmed FF52 is fine..it must be as she has resumed ordering stuff.

I was hopeful that James's reply would solve this and fell to seeking the option he suggests. Alas, it's taken me way beyond my level of technical competence - I have simply no idea what to do with the array of files and blocks of code presented to me in the archive. I'm also conscious of how much time this has already taken, and resentful that Mozilla didn't give me the option of checking more truthfully whether the update would work on my tablet and therefore the option of retaining the previous version that was working just fine. So the ultimate result is just making me think 'Bye-bye Firefox'. Grrr.

I spoke too soon. Went this morning, full of cheer, to open up yesterday's succcessful download, and - guess what? - just got the message that Firefox no longer supported this version on Android. That would be fine - all I needed was the version that used to work perfectly OK. I really, really am going to give up now. But thanks again to everyone who has aimed to help. It's not your fault.

In my case, it's not so easy to simply give up FF on my Samsung GT-P7300 with Android 4.0.4 because I had it synch'd to the FFs I use both on on my Linux Ubunto and on my Android Lollipop. Isn't there a case for asking for FF53 to be made backward compatible to accommodate those of us with older tablets? Aren't we in this thread identifying a design drop-off in FF53 that needs to be corrected? Or what about introducing this backward compatibility in a new FF54?

As per my earlier entry above, I downloaded the last version of FF that worked, stopped the tablet updating apps/programs so you dont finish up with the same problem again, and we have been ok ever since. Also if your tablet is anything like ours, we dont need updates to all the stuff we've had on it for ages and dont use so its now a little faster as it does have to keep downloading and updating

3a8082e126