Install Older Version Of Bluestacks
Athenasby Regalado
I have personally tested the latest Eufy apps on both V4 and V5 of Bluestacks and they both work correctly. V5 needs a few more tweaks to get setup correctly but after initial setup it runs fine. V4 has been running for over 2 years with only one hiccup of a couple of weeks when Eufy made a code change.
I double checked the settings I got online, creating a new instance ABI set to x86, ARM 32-bit.
Did a fresh installation of Eufy Security app.
But it just keeps showing white blank screen as before.
Switch the Eufy app on Blustacks to older version 4.6.1_1655. Whatever they did to more recent app versions has caused the white screen at startup. Havent had time to dig around and search for a better workaround.
Hi everyone I'm trying to install an apk that I've designed with minsdk version of 14 and target of 19 onto bluestacks and its failing. What's weird is that I installed an app with the same api version of 14/19 on this very same bluestacks player a month ago(I deleted it now though to swap it with the new apk). Please let me know what api I should be developing in for bluestacks. Here's my xml
I downloaded the .exe two times. Once from filehippo and once from the official website. Both are behaving the same way. I double click/run as admin then it starts extracting and after that the windows asks me to allow the changes. After clicking OK nothing happens.
I rebooted my system a couple of time. I tried removing temporary files. C: drive have more than enough space free. 8GB RAM. I am installing it as admin and have no virtual machine software installed.
I haven't figured out how to install it yet, but if you have 7 zip, just right click and select "extract here." Apparently the built-in file extractor doesn't work. Now to find the installation file. . . look for exe obviously
first download bluestacks 4 then just got to show folder and shift it from the following folder to desktop.Extract it over there, then right click and click 'extract here' the just install bluestacks.
What you need to do is install an older version of BlueStacksX. So if the built in extractor doesn't work in the latest version, it should in an older version. Attached below is a link to an archive of older versions of BlueStacksX. I used 5.8.0 and it worked fine.
1.) Try sideloading older (working) Wyze app version manually into Bluestacks
2.) Try downloading and running Wyze app on Android Studio AVD emulator
3.) Try using 3rd party viewer software: TinyCam
I have found the TinyCam app to be slightly buggy on getting connected, but once it does it is good. To fix your issue, temporarily disable 2FA and connect all your cams up, make sure you can view all your streams. Then turns 2FA back on again in your Wyze app and exit Wyze app. Finally, load TinyCam again which will then attempt to connect to your previously-working streams and TinyCam should pop up a dialogue for you to enter the 2FA code that Wyze texts you.
Also, if you want in-app ads removed from the free TinyCam I highly recommend running AdGuard Pro ( buy it for cheap from here, I have personally purchased this deal myself: AdGuard Family Plan: Lifetime Subscription StackSocial )
First i downloaded the app control screen rotation by ah_apps in google store. Set the app so that it can start service as well as display notification. Set the rotation to portrait from the drop down notification menu then enter the app.
Get to the camera screen then from their use the drop down notification menu to change the orientation to landscape. Going back to the previous screen caused it to undo, so you will need to do the same steps again (Portrait first then rotate to landscape) but has worked every time for me since installing the other app.
Problems: After enabling SVM and IOMMU, using either Bluestacks, Nox or Memu (android emulators) causes BSOD crashes. Enabling Hyper-V or Hypervisor only speeds up the BSOD happening. On screen it says 'System Service Exception', delving further I find stopcode 0x000003b, caused by driver nostkrnl.exe.
The problem persists. The same BSOD code, clean installed the drivers, ran a DISM and SFC (if I recall correctly) and nothing comes up. I can play videogames, run a benchmark but only the android emulator causes the BSOD. If I can't find a fix, I may need to return everything I've bought and try a completely different build, but I really prefer to get this working.
Before giving up on the card..why don't you try the settings exactly like I suggested? Set Wattman back to factory defaults first. Then change only the manual temperature settings and the Power Limit..click apply. Leave everything else at default...which is Automatic.
1) Download the correct AMD Full Set of drivers from AMD Support. Make sure your Windows is fully updated via Windows Update. Windows Must be fully updated because the latest AMD Drivers requires all the latest "Optional" and "Recommended" updates to be installed.
2) Use Windows Uninstall to uninstall current AMD driver and software and disconnect the internet from your computer. Then use DDU (Display Driver Uninstaller) Display Driver Uninstaller (DDU) from Wagnardsoft Forum in Safe Mode. This will eliminate all traces of the AMD driver and software from your computer.
4) Try reinstalling the AMD FULL SET OF DRIVERS that you have downloaded manually. Make sure you disable the Internet to prevent Windows from installing a newer version. So configure windows to prevent it from updating drivers via windows update. So it has been mentioned to disable any anti-virus programs before installing AMD Drivers.
It's the same graphics card as I had on my old build, where it never caused problems, so I hadn't expected the graphics card itself to be the issue. I've reinstalled all drivers, including a system restore (my system wouldn't start after amd cleanup utility, so I had to), with no luck. I'm gonna try and install an older version of the driver now. I'll also try the other things you mentioned. Thank you for your comment.
Since the Asus Ryzen ABBA bios update on my B350 (Ryzen 3600), no overclock, I been having BSOD Service Exception Error, IRQL, and all kinds of driver error. This stems from Virtualisation need for my Android Emulators like Nox and LDPlayer. Have read through entire forums, Reddits, etc. The BSOD is random but is triggered when an emulator is trying to write to memory and gets stuck or a random error. When the ABBA Ryzen bios was in beta, i tested it and went back to ABB due to the above, Now Asus released official ABBA and I installed it and the BSOD came back. at this stage I dont know what to do before I go back to the slow ABB bios. NB, I have tried all options including sfc scans, checkdisk, etc. No am using my emulators without VT, which is not ideal.
If you run ASIAIR on an Apple silicon Mac, you can also squirrel away each downloaded iOS app version (I even have the Betas saved away), and in the future revert back to using the older versions of the apps instead of the newest version. You can even copy the older copies to a different Mac that is also running Apple silicon).
I am no longer able to get a ethernet connection from my glinet Beryl to the Asi Air. Nothing is populating in the gateway area of the wired connection setup and Im not really sure what the settings should even be. I have been trying older versions of the ap today and no improvement. Now im wondering if it is a issue with the firmware, or even the glinet firmware. when it all did work it was incredible. I wish I never updated anything at all
For diagnostics, perhaps you can take the ASIAIR (wth 12V power) and connect it via Ethernet directly to your home router to see if you can see the ASIAIR in the router's table. That will check to see if the ASIAIR end has failed, or the gl.iNet end has failed. FWIW, the gl.iNet products appear to be a very solid pieces of gear; head and shoulders better than the Vonets stuff.
Another thing you can check is the RJ-45 pins in the ASIAIR -- (use a flashlight and) see if the pins in the jack are still springy, and are all lined up evenly when an RJ-45 connector is not plugged into it. I have seen RJ-45 connector pins that are crooked and fail.
w7ay Why didnt I think of that. Well, My home router is also Gli.net though so I hope it is not a glinet firmware issue. And you are right, they are really great routers, the Beryl when it was working was extremely fast with fps over wifi with some serious range.
Just make a copy of the firmware that you had archived back when you first received the ASIAIR. The ASIAIR app will update that firmware to the level that the app needs, when the app first connects to the ancient firmware.
If you don't have a copy, ZWO has reference copies of the firmware on their web site [edit: on a Goggle drive] -- but be aware that it take a loooong time to download the 32 GB image (compressed but still large).
If you have a third generation (or newer) ASIAIR (the one that uses eMMC memory), just press the black reset button on the ASIAIR box for longer than 5 seconds, and the ASIAIR will revert to that "factory default" firmware. And again, when you connect an ASIAIR app to the device, the app will update the firmware.
w7ay
I am trying to set my ASIair Pro to connect to an iOptron SkyHunter. ZWO tech support provided a link to a version for an EQ6R that can support the SH. When I installed it and when I used my Android S20 to connect to it, I got a message saying there was a version mismatch (8.48 vs 10.46). My S20 is at the latest version of Android ASIair. In this thread you have mentioned going back to the version initially installed. I checked and I backed up a file ZWO_ASIair apk from July 2019. I don't remember what I did back then. I owned the original and traded it in for the Pro. I subsequently bought an AA+. The AA+ supports the SkyHunter but I want to use it with my main mount and the AA Pro with my SH.
My question is this : can I install the firmware and somehow get the equivalent Android release from the apk file? Right now I am stymied and ZWO TEch support hasn't provided a solution to my problem.
c80f0f1006