I've got an app that was built for Android Marshmallow, but crashes on Nougat & Oreo. Given a rooted phone, is there some way to "emulate" an environment on a newer Android phone, such that the app would still work? I know I can emulate it on PC via something like Android-x86, but that's not the issue here - it's an app that I'd really like to use on-the-go, on my phone - not at home on the PC.
Possible or impossible?
inyerested too
metal450 said:
I've got an app that was built for Android Marshmallow, but crashes on Nougat & Oreo. Given a rooted phone, is there some way to "emulate" an environment on a newer Android phone, such that the app would still work? I know I can emulate it on PC via something like Android-x86, but that's not the issue here - it's an app that I'd really like to use on-the-go, on my phone - not at home on the PC.
Possible or impossible?
Click to expand...
Click to collapse
I also have one that's since been discontinued so there's no chance of a newer os version of it either. I tried to find it, but even the latest apk of it is a 4.4android and as such i can't install.
has anyone aince been able to find any solution?
Don't think that is possible. Just imagine how much resources a phone would need to have to achieve this.
Contentum said:
Don't think that is possible. Just imagine how much resources a phone would need to have to achieve this.
Click to expand...
Click to collapse
Really? There are some *super* low-resource android devices out there. After all, you can emulate Playstations & stuff on Android phones, so why not Android on Android?
metal450 said:
I've got an app that was built for Android Marshmallow, but crashes on Nougat & Oreo. Given a rooted phone, is there some way to "emulate" an environment on a newer Android phone, such that the app would still work? I know I can emulate it on PC via something like Android-x86, but that's not the issue here - it's an app that I'd really like to use on-the-go, on my phone - not at home on the PC.
Possible or impossible?
Click to expand...
Click to collapse
Same problem here, there is an app that works until nougat, when i updated my note 8 to oreo it didn't work anymore, it says connection error and can't login. It would be great if there was a chance to get it to work again emulating an older version of android, I think that smartphones like note 8 or anything recent can surely run it smoothly.
Hyperplaner said:
Same problem here, there is an app that works until nougat, when i updated my note 8 to oreo it didn't work anymore, it says connection error and can't login.
Click to expand...
Click to collapse
If it's a connection error and login failure it may be relying on an Internet server that doesn't exist anymore. This is not the same problem as above: the app not being possible to install or run because it's incompatible with newer versions of Android itself.
VMOS Virtual Machine Operating System - Double Your Android System
VMOS is an APP software based on Virtual Machine. VMOS can be installed in the form of a normal APP to Linux or Android system through VM technology. That is to run another complete Android system through an application and is out of control of the host system.
www.vmos.com
Related
Hi.
I'm new to Chinese phones and I recently purchased an Elephone P9000. Its great and have no real problems except I cannot get my banking app to work with NFC card payment as the app says my phone has been modified and it says that the kernel is @root however I have not rooted it nor have root access but it seems this is normal from other forums I have read.
Is there anyway to get my phone to say Unmodified so my NFC card payments will work?
Also, has my system been modified? When I first turned it on it did the normal setup of apps however it didn't run through the normal user setup, asking which country I live in and language I want etc. even after OTA updates and factory reset. It also says custom build version. I have attached a screenshot of my about device.
If this phone has been modified, can I and how do I get my phone back to stock.
Mick
mabrady85 said:
Hi.
I'm new to Chinese phones and I recently purchased an Elephone P9000. Its great and have no real problems except I cannot get my banking app to work with NFC card payment as the app says my phone has been modified and it says that the kernel is @root however I have not rooted it nor have root access but it seems this is normal from other forums I have read.
Is there anyway to get my phone to say Unmodified so my NFC card payments will work?
Also, has my system been modified? When I first turned it on it did the normal setup of apps however it didn't run through the normal user setup, asking which country I live in and language I want etc. even after OTA updates and factory reset. It also says custom build version. I have attached a screenshot of my about device.
If this phone has been modified, can I and how do I get my phone back to stock.
Mick
Click to expand...
Click to collapse
The kernel string says @root because it was built either by the root user of the compile machine or because the machine name was root.
This has nothing to do with the Android OS being rooted.
Jonny said:
The kernel string says @root because it was built either by the root user of the compile machine or because the machine name was root.
This has nothing to do with the Android OS being rooted.
Click to expand...
Click to collapse
Can you provide any light on why my banking app says my device is modified?
mabrady85 said:
Can you provide any light on why my banking app says my device is modified?
Click to expand...
Click to collapse
Possibly the people behind your banking app don't realise that a kernel string of @root doesn't mean the device is rooted. There are lots of misconceptions about what root is and unfortunately it appears the app maker(s) have fallen for one of them.
If you would be willing to root Your device, it might be possible to solve Your issue by using XPosed and the modules/App devicefaker and Rootcloak. That's the way I was able to use boon (its a prepaid NFC Payment App, available in some European countries)
Gesendet von meinem P9000 mit Tapatalk
After latest OTA update my bank apps now work. ?
I don't want to upgrade and risk destroying my phone
Pro4TLZZ said:
I don't want to upgrade and risk destroying my phone
Click to expand...
Click to collapse
That doesn't make any sense. I'm on the latest stock ota upgrade and my phone is fine. Not going to say which banking app I use but it's still working fine without without root. But some makes are more strict about this sort of thing.
Hello
I have an Xperia Ray and was running a 4.4.4 ROM based on CyanogenMod till a few weeks ago when I started to realize that many of the newer versions of different apps caused strange troubles. Some of them crashed most file explorers I tried just on loading the icon from the downloaded APK. Some I managed to install nonetheless only to have the same problem with the launcher/drawer itself. Every time it tries to display the icon of the app it dies. Looking for a solution I discovered that CM13 got ported for my phone and was happy to be able to change to Android 6.0.1.
Sadly the troubles did not go away. The apps that showed the above mentioned symptoms on 4.4.4 have similar effects on 6.0.1. Only that now these apps are crashing the whole phone forcing a reboot and that the launcher app does not load at all anymore. Only solution is to uninstall the app manually in recovery mode via adb shell.
After a lot of tinkering, experimenting, talking to other app devs, and rebuilding open source apps I found that the problems appeared with the update to Android Studio 3. It seems that without changing anything code wise for these apps only the update from gradle wrapper 3.5 to 4.1 seems to cause these troubles. On the other hand I can build my own apps with the newest Android Studio with everything up to date without these problems showing up. So I guess it is some library, API, or whatever in combination with the newer gradle versions that causes these troubles.
Well, it seems that there is a bug in the CyanogenMod ROMs, as far as I know by now. It's not a Xperia Ray specific problem as people with other hardware running CyanogenMod have the same problems. For example this thread here. And I got confirmation from an app developer team that they were able to reproduce the problems on a Galaxy S2 running CM13.
It's also not Android version related as updating to 6.0.1 did not help at all.
Have you experienced what I'm talking about and maybe found the solution for that problem? I think there is a bug in the CyanogenMod system somewhere but I'm not skilled enough to find it.
I fear that these problems will render my phone incompatible with more and more upcoming app versions and would really hate to have to switch to a bulky modern phone.
Here are some log files showing the errors. Maybe you can read something useful from them.
Thanks in advance!
EDIT:
Here some additional info that came as answer from a dev team I contacted regarding this issue:
The issue you have reported tends to only occur in devices with the older memory layout used by manufacturers for devices that run Android 2.x onwards, such as the Galaxy S2 - this layout still sticks around even when upgrading to custom ROMs with newer android versions. A unified internal layout for Android devices only started to appear in 2013 and it became the de-facto layout in 2014 or so.
In the old layout, you have both an Internal System Partition (1-2GB) and then an Internal System Memory (the rest of the device's advertised internal memory - its seen as emulated "External memory" - an external SD card then becomes "SD2" in these devices when running a custom ROM). This causes problems for apps that are created and compiled with the unified memory layout in mind, even if the old SDK is the target, because the system will not direct them to an accessible storage area to store user data.
The apps that do not have problems were the ones that have been around since android 2.x; they will instead have their own set of problems for newer devices and versions of Android.
Right now I'm not sure what to think of this...
Push...
push too , if i use a non cyangenmod based rom like paranoid android (6.0 Android MarshMallow Pure AOSP for Google Nexus 7 2012 WIFI), is this prob fixed then ?
i have nexus 7 (2012) wifi only device , i have cyanogenmod 11 (20141112) / android 4.4.4 ( this tablet has no SD card slot so no SD2 assignment )
Not Sony Xperia,..
Only a cheap Haier A16C3H with CM13 Nightly...but..
Yes the trouble is exactly the same in my experience here. I don't know what to do for the solution, except perhaps one of:
# "keep/looking for & install - only the old version of apps, or
# buying a new phone (if I can)
Sad
Nothing new
Push
Nothing new from my side, except that I think twice before updating an APP by now.
So far I've managed to get around with my old Xperia, but would be nice if someone more knowledgable could look into this matter.
Thanks.
Anyone figured out how to fix this? or even a workaround?
My problem was the cm13 based rom I am using on my LG G3 Beat had this problem with newer versions of apps, but someone made a cm14 based rom that fixes this problem but in exchange it created another problem, lag in the touchscreen, playing games where you have to do combo/multiple taps became impossible.
I got so frustrated that I just went back to stock lol.
I just installed a virtual machine with Android 5.1 on my Android 9.1. But the app I needed doesn`t work on it. It requires at least Android 6. Does anyone have the know-how how to produce such an Android VM? The problem is that I use P20pro of the mighty-user-NOT-friendy Hwieiiaiiewwaaiei and they really destroyed the camera app some months ago. It cannot be downgraded (I`ve got no root rights), the app cannot be downgraded, tried several ways, adb, appdowgrader, tried factory it returns to 9.1, tried hisuite downgrades to 9.0, I`ve got the camera apk that worked perfectly fine, but it cannot be installed because it`s an older version and I though that after I uninstall the current camera version all be good - but hardtimes led to no avail - it still cant be done... I couldn`t change the APK version because one does not simply recompiles a huwauwuwuuwuwwwwwiee`s app.
So my last resort is a VM with the good Ol` Android 8.0/8.1 (just in case) - but I don`t know how to create it.
I recently updated to One UI 3.1 and it's performing much worse than it was on Android 10, especially with one of my games constantly crashing when trying to enter the main menu.
I want to know if there's a way to revert the update somehow... so that at least I can get things keep running for the time being until GSIs can be made working.
EDIT: Okay... I finally managed to log back in to the game in question after about 100 tries over the past hour... what an effort... it's getting more and more difficult to login lately...
EDIT 2: Guess I'm asking for the impossible... and as for the game in question, I suspect it was a known Unity-related issue caused by permission changes introduced in Android 11. I'm considering rooting the device to test if that's the case as I cannot just grant the permission since the app itself didn't declare it in the manifest. But in overall, it doesn't change the fact that the tablet is performing much worse on Android 11 than it was on Android 10.
EDIT 3: It seems even with root I cannot grant a permission an app didn't request... so I really can't test if the permission in question is indeed the cause of the crashes...
EDIT 4: Downgrading is no longer possible since build BUC1. Samsung has incremented SW REV on this build so you can no longer downgrade once you upgraded past this version.
LSS4181 said:
I recently updated to One UI 3.1 and it's performing much worse than it was on Android 10, especially with one of my games constantly crashing when trying to enter the main menu.
I want to know if there's a way to revert the update somehow... so that at least I can get things keep running for the time being until GSIs can be made working.
EDIT: Okay... I finally managed to log back in to the game in question after about 100 tries over the past hour... what an effort... it's getting more and more difficult to login lately...
EDIT 2: Guess I'm asking for the impossible... and as for the game in question, I suspect it was a known Unity-related issue caused by permission changes introduced in Android 11. I'm considering rooting the device to test if that's the case as I cannot just grant the permission since the app itself didn't declare it in the manifest. But in overall, it doesn't change the fact that the tablet is performing much worse on Android 11 than it was on Android 10.
EDIT 3: It seems even with root I cannot grant a permission an app didn't request... so I really can't test if the permission in question is indeed the cause of the crashes...
Click to expand...
Click to collapse
Most apps should work fine on Android 11, but some may have issues and need updates.
Downgrading to Android 10 is technically possible. Download the Android 10 firmware and flash it with Odin on a PC via USB cable to your device.
But I would prefer running on the newest firmware version and trying to get an update of the app. And there will be updated if Android 11, too ... which optimizations of stability, performance, etc.
It_ler said:
Most apps should work fine on Android 11, but some may have issues and need updates.
Downgrading to Android 10 is technically possible. Download the Android 10 firmware and flash it with Odin on a PC via USB cable to your device.
But I would prefer running on the newest firmware version and trying to get an update of the app. And there will be updated if Android 11, too ... which optimizations of stability, performance, etc.
Click to expand...
Click to collapse
Thanks, but it's not really that relevant now as the crashing issue was finally fixed by the developer.
However, on Android 11 things are indeed performing worse than on Android 10. Frame rates are much lower, and touch issues (erratic or sudden delay/loss of touches) become more frequent. Ironically, when I used GPUWatch (from Developer Options) to diagnose the sluggish frame rates, I found that neither CPU nor GPU was maxing out while playing.
Now that I've rooted, I'm considering looking for some alternatives as the stock ROM is indeed terrible regardless (a good example would be that it's tough to take logcats here, as the system itself spams logs at an incredible rate I've never seen before). However, I'm yet to get a GSI to boot.
I have this old app "GolfSense" that was designed to work on "Android OS version 2.3.3 +".
It will not work with my S9+.
I ran across VMOS to run older apps, and downloaded it.
I uploaded the app "GolfSense" into VMOS, and ran the app. It seems to work well, but cannot get the BlueTooth to work properly. It says it is Paired, but doesn't turn blue..
Does anyone know of a site that has old verions of Android ROMs, specifically "Android OS version 2.3.3 +"? I will install it on VMOS,
Or does anyone know of issues with BlueTooth, and how to overcome them?
Thanks to anyone that can help.