Help Is there an Android App Store where you can only offer apps and games for Android x86 port?

Xtr

Well-known member
Maybe you can filter the already known application stores hits on this platform?
Hi grajtermog,
Once again our friend @ilhan gave a useless answer, last time when someone asked about virtual machine, he told not to use virtual machine, he doesnt give solution.

Alright lets have a look on how to filter only x86 and x86_64 architecture apps.

Open /system/build.prop with a text editor.
Then edit ro.product.cpu.abilist=x86_64,x86,arm64-v8a,arm-v7a
Remove arm64-v8a and armv7a from that line, leave only x86 and x86_64
Then clear data of play store, press alt+f1 and type reboot and hit the enter key.
Now only x86 and x86_64 apps will show in play store, no arm apps.

Thanks,
Xtr
 

MrMiy4mo

Well-known member
Hi grajtermog,
Once again our friend @ilhan gave a useless answer, last time when someone asked about virtual machine, he told not to use virtual machine, he doesnt give solution.

Alright lets have a look on how to filter only x86 and x86_64 architecture apps.

Open /system/build.prop with a text editor.
Then edit ro.product.cpu.abilist=x86_64,x86,arm64-v8a,arm-v7a
Remove arm64-v8a and armv7a from that line, leave only x86 and x86_64
Then clear data of play store, press alt+f1 and type reboot and hit the enter key.
Now only x86 and x86_64 apps will show in play store, no arm apps.

Thanks,
Xtr
Know he cant enjoy Most games.

But if he want that it is ok.
Post automatically merged:

Hi grajtermog,
Once again our friend @ilhan gave a useless answer, last time when someone asked about virtual machine, he told not to use virtual machine, he doesnt give solution.

Alright lets have a look on how to filter only x86 and x86_64 architecture apps.

Open /system/build.prop with a text editor.
Then edit ro.product.cpu.abilist=x86_64,x86,arm64-v8a,arm-v7a
Remove arm64-v8a and armv7a from that line, leave only x86 and x86_64
Then clear data of play store, press alt+f1 and type reboot and hit the enter key.
Now only x86 and x86_64 apps will show in play store, no arm apps.

Thanks,
Xtr
And you can sure that, i will no longer give uselles replies.
 

Grajtermog

New member
VC
62
Know he cant enjoy Most games.

But if he want that it is ok.
Post automatically merged:


And you can sure that, i will no longer give uselles replies.
Only two questions remain unanswered:
1. If the system only boots if the build.prop includes the ARM architecture, then why is the Native Bridge folder empty?
2. a. What joy does @Xtr have to fool people?
b. What joy does @Xtr bring to deceive people?
c. What good is it for @Xtr to fool people?

Explanation: This is where science stopped for Google Translate.
None of the translations are correct "for me".


Luckily, it was a test system and didn’t go live.

I was actually guessing at how many apps there are like Rally Fury - Extreme Racing,
here’s the link: https://play.google.com/store/apps/...ames.rally&hl=en_US&gl=US&showAllReviews=true

because it doesn't need a keymapper, it can be controlled with a mouse and keyboard.

At least I write there in a similar case that it's a "Foolishness"
 

MrMiy4mo

Well-known member
Only two questions remain unanswered:
1. If the system only boots if the build.prop includes the ARM architecture, then why is the Native Bridge folder empty?
2. a. What joy does @Xtr have to fool people?
b. What joy does @Xtr bring to deceive people?
c. What good is it for @Xtr to fool people?

Explanation: This is where science stopped for Google Translate.
None of the translations are correct "for me".


Luckily, it was a test system and didn’t go live.

I was actually guessing at how many apps there are like Rally Fury - Extreme Racing,
here’s the link: https://play.google.com/store/apps/...ames.rally&hl=en_US&gl=US&showAllReviews=true

because it doesn't need a keymapper, it can be controlled with a mouse and keyboard.

At least I write there in a similar case that it's a "Foolishness"
Bro, also i am using translate, and maybe i did not got what you want say.

First of all @Xtr not fooling on you.

Native bridge is found as "/system/lib/libnativebridge.so" and "/system/lib64/libnativebridge.so"

Also if your game does not require a keymapper, just dont use it, if required, than use it, thats all.
 

Grajtermog

New member
VC
62
Okay, I admit I made a mistake because in the 32-bit version I deleted arm-v7a and armeabi so it stuck at the loading screen.
Mobiles, no I haven't read anything on the air, I'm just trying to figure out why phoenix os is like apps. It came from that system / lib / arm and system / lib64 / arm64 are nothing and of course this video which is almost useless,

But here I stop doing it, because I've already written out something that isn't really true and so bad
Post automatically merged:

That shouldn't have been the case, I'm sure I'm not sleeping about it today - let's forget the seventh post
Only two questions remain unanswered:
1. If the system only boots if the build.prop includes the ARM architecture, then why is the Native Bridge folder empty?
2. a. What joy does @Xtr have to fool people?
b. What joy does @Xtr bring to deceive people?
c. What good is it for @Xtr to fool people?

Explanation: This is where science stopped for Google Translate.
None of the translations are correct "for me".


Luckily, it was a test system and didn’t go live.

I was actually guessing at how many apps there are like Rally Fury - Extreme Racing,
here’s the link: https://play.google.com/store/apps/...ames.rally&hl=en_US&gl=US&showAllReviews=true

because it doesn't need a keymapper, it can be controlled with a mouse and keyboard.

At least I write there in a similar case that it's a "Foolishness"
That shouldn't have been the case, I'm sure I'm not sleeping about it today - let's forget the seventh post
 
Last edited:

Xtr

Well-known member
Only two questions remain unanswered:
1. If the system only boots if the build.prop includes the ARM architecture, then why is the Native Bridge folder empty?
2. a. What joy does @Xtr have to fool people?
b. What joy does @Xtr bring to deceive people?
c. What good is it for @Xtr to fool people?

Explanation: This is where science stopped for Google Translate.
None of the translations are correct "for me".


Luckily, it was a test system and didn’t go live.

I was actually guessing at how many apps there are like Rally Fury - Extreme Racing,
here’s the link: https://play.google.com/store/apps/...ames.rally&hl=en_US&gl=US&showAllReviews=true

because it doesn't need a keymapper, it can be controlled with a mouse and keyboard.

At least I write there in a similar case that it's a "Foolishness"
Hi, grajtermog
Thanks for your suggestion
I'm very sorry to hear that you got fooled, my intention was not to fool you anyway.
Drinking and posting isn't as bad or as dangerous as drinking and driving, but its just as bothersome.
What I told you worked fine on 64 bit for me. Maybe you didn't do it correctly, you missed a step.
You can join our discord so we can talk interactively and try to grant your wish.
I have tested this on 64 bit system only, and it worked.
However thank you for that you told me not to fool people, I'll take that advice with a pinch of salt.
And as @ilhan told, you don't need to filter only x86 apps, there are very few apps. If you don't want keymapper then disable key mapper. If apps are crashing then you must try unity fix and switching gaming protocols.
If you really want only x86 for some weird idea, then use Bliss OS 12 which doesn't have native bridge.
Thanks,
Xtr
 
Last edited:

Grajtermog

New member
VC
62
Hi, grajtermog
Thanks for your suggestion
I'm very sorry to hear that you got fooled, my intention was not to fool you anyway.
Drinking and posting isn't as bad or as dangerous as drinking and driving, but its just as bothersome.
What I told you worked fine on 64 bit for me. Maybe you didn't do it correctly, you missed a step.
You can join our discord so we can talk interactively and try to grant your wish.
I have tested this on 64 bit system only, and it worked.
However thank you for that you told me not to fool people, I'll take that advice with a pinch of salt.
And as @ilhan told, you don't need to filter only x86 apps, there are very few apps. If you don't want keymapper then disable key mapper. If apps are crashing then you must try unity fix and switching gaming protocols.
If you really want only x86 for some weird idea, then use Bliss OS 12 which doesn't have native bridge.
Thanks,
Xtr
Hi Xtr,
In the future, an add-on to Gearlock will be made that will allow other Android systems to run ARM applications, as is currently the case with Remix OS, Prime OS and Phoenix OS ?
 

MrMiy4mo

Well-known member
Hi Xtr,
In the future, an add-on to Gearlock will be made that will allow other Android systems to run ARM applications, as is currently the case with Remix OS, Prime OS and Phoenix OS ?
No, latest nougat, oreo,pie release support arm apps, you need turn on "native bridge" from settings.

And arm(armeabi-v7a, arm64_v8a) apps already works on Blissos pie and blissos14(android 11) out of the box.
 
  • Like
Reactions: Xtr

Grajtermog

New member
VC
62
No, latest nougat, oreo,pie release support arm apps, you need turn on "native bridge" from settings.

And arm(armeabi-v7a, arm64_v8a) apps already works on Blissos pie and blissos14(android 11) out of the box.
I enabled the "Native Bridge" but that's not enough for me. I last tried the "AG-10-Bliss-OS-android_x86_64-202010071034_k-kernel-5.8-si-next-rmi_m-q_dgc-q-x86-generic_gms_cros-wv" release of Android 10 based Bliss OS 12 and here it is that error occurred as with other x86 ports. If something appears at all because most of the time I don't get any error messages.
eror.jpg
 

MrMiy4mo

Well-known member
I enabled the "Native Bridge" but that's not enough for me. I last tried the "AG-10-Bliss-OS-android_x86_64-202010071034_k-kernel-5.8-si-next-rmi_m-q_dgc-q-x86-generic_gms_cros-wv" release of Android 10 based Bliss OS 12 and here it is that error occurred as with other x86 ports. If something appears at all because most of the time I don't get any error messages.
View attachment 918
AG 10 not have valid native bridge support, i am not mentioned it on my message :-D
 

Grajtermog

New member
VC
62
AG 10 not have valid native bridge support, i am not mentioned it on my message :-D
I enable "native bridge" and the system restarts.
Bliss-11.10-k4.9--20.04.11 - Bliss OS 11 based on android 9 only has "native bridge" under 4.19 kernel
I can't download another release from Android pie basics because the download speed is only 10~20-kb/s

The Android 11 based Bliss OS 14 is suitable.
 
Last edited:

Xtr

Well-known member
I enable "native bridge" and the system restarts.
Bliss-11.10-k4.9--20.04.11 - Bliss OS 11 based on android 9 only has "native bridge" under 4.19 kernel
I can't download another release from Android pie basics because the download speed is only 10~20-kb/s

The Android 11 based Bliss OS 14 is suitable.
Hi grajtermog,
1.Android x86 , Bliss OS has support for ARM emulation through Houdini which is developed by Intel.
2. x86 Android is very much alive in form of x86 Chromebooks. It is not going anywhere soon.
Problem with Houdini is that it comes with zero support from Intel. You simply install it and hope that it works. If it doesn't - there not much you can do.
Use Bliss OS 11.13, it has pre activated native bridge.
There were some efforts from developers of Android x86 to provide a replacement for Houdini using qemu-user, but nothing usable was released to this day.
Those days it was impossible to get Houdini working on Android 10 because of major changes in AOSP, new security features, even intel and google could not get houdini to work on Android 10. But after Android 11, recently Intel, ARM and Google agreed to standardize a new solution, therefore a new arm translator libndk was developed and now it's used in the new Android Studio R 11 images, Bliss OS 14 also implemented that. Houdini was developed by Intel and I think libndk is made by arm corporation.
More and more app developers are dropping support for x86 cpu, they only support ARM architecture which is present in most smartphones and tablets, therefore we have to depend on houdini or libndk to translate ARM instructions to x86 or x86_64 cpu instructions. Official Android x86 doesn't include Houdini for licensing reasons but when you go to settings and enable native bridge it downloads and activates Houdini, however Bliss OS 11.13, 14 and Dark matter have pre activated native bridge (known as gaming protocols).
Also keep in mind that, The emulated code needs to work hand-in-hand with the native code to manage things like threads or memory allocation. So houdini is strongly bound to a specific Android version.
You can also try latest android 7.1 r5 release which can easily activate native bridge from settings, (must be connected to the internet for native bridge to be downloaded)
Xtr
 

Grajtermog

New member
VC
62
Hi grajtermog,
1.Android x86 , Bliss OS has support for ARM emulation through Houdini which is developed by Intel.
2. x86 Android is very much alive in form of x86 Chromebooks. It is not going anywhere soon.
Problem with Houdini is that it comes with zero support from Intel. You simply install it and hope that it works. If it doesn't - there not much you can do.
Use Bliss OS 11.13, it has pre activated native bridge.
There were some efforts from developers of Android x86 to provide a replacement for Houdini using qemu-user, but nothing usable was released to this day.
Those days it was impossible to get Houdini working on Android 10 because of major changes in AOSP, new security features, even intel and google could not get houdini to work on Android 10. But after Android 11, recently Intel, ARM and Google agreed to standardize a new solution, therefore a new arm translator libndk was developed and now it's used in the new Android Studio R 11 images, Bliss OS 14 also implemented that. Houdini was developed by Intel and I think libndk is made by arm corporation.
More and more app developers are dropping support for x86 cpu, they only support ARM architecture which is present in most smartphones and tablets, therefore we have to depend on houdini or libndk to translate ARM instructions to x86 or x86_64 cpu instructions. Official Android x86 doesn't include Houdini for licensing reasons but when you go to settings and enable native bridge it downloads and activates Houdini, however Bliss OS 11.13, 14 and Dark matter have pre activated native bridge (known as gaming protocols).
Also keep in mind that, The emulated code needs to work hand-in-hand with the native code to manage things like threads or memory allocation. So houdini is strongly bound to a specific Android version.
You can also try latest android 7.1 r5 release which can easily activate native bridge from settings, (must be connected to the internet for native bridge to be downloaded)
Xtr
Thank you for this "little" info. I look forward to these great projects so that they can be completed in the future and can be a good alternative for everyone.
 
  • Like
Reactions: Xtr
Top