I have used project 64 for years but I have been out of the loop since 2012. I heard wonderful things about Mupen64PLus Emulator. Unfortunately mine will not start any ROMS. It says it requires Vulkan 1.1 Support. I am unsure if this is why it will not start. I am unsure if my computer is able to use Vulkan. dxdiag shows Direct X12 (Standard for Windows), but it does not show any information on Vulkan. I can't tell if my CPU supports Vulkan or doesn't. Regardless I did start the process of installing the SDK for it.
My Questions are based off the info from this video:
Fix Vulkan 1.dll Missing
1. Where can I look on my PC to make sure it supports Vulkan API?
Best dumbed down Video/Article recommendation for Questions 1 A-C?
1 A. Is Vulkan only AMD Specific or just derives from their software knowledge?
1 B. Can Intel users still put Vulkan on their laptops?
1 C. Is it the CPU (Processor) what needs to support Vulkan (If I understand how API's work)?
2. I need a safe backup site for the .json and runtime file.
The site lunarg no longer has working links for either. I get a 502 Error.
3. Does Mupen64Plus run at all without Vulkan? Can it be another issue?
Related
im not sure i get whats going on with this new winp7 rom thats been posted.
has anyone run it on an emulator? if not how do you know its even real? and when you guys are talking about dumping it what exactly does that meen, sorry for nuub questions but im not that up on the dev scene
Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.
StevieBallz said:
Well, it can't be run in the Emulator, as the Emulator uses x86 ROMs, while actual devices are based on the ARM architecture, so basically as of now no one can say for certain if it is real (although some things look promising).
As the ROM is intended for use on a not yet known device it also can't be flashed to a device anyone owns.
Dumping means that they are trying to extract the files which are contained in the ROM image, which is difficult as the format is different from WM6.5 and no documentation exists for it.
If they can extract the files they then could be repackaged to known formats which then could be flashed - nobody knows if that will boot on any existing device though.
Click to expand...
Click to collapse
ahh ryt. i get the emulator part, i actually have the visual studio 2k10 for win phone so i understand that there is a difference between computer based roms and mobile roms. but i thought maybe there was a tool out ther that could use mobile roms, lik a virtual box for phones, i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone
96edwy said:
... i know that people know the hardware specs for win phone 7.. 3 buttons, 1g processor, capacative touch screen etc etc so i thought maybe sumone had used it through a virtual phone
Click to expand...
Click to collapse
No, we've been told the minimum specs by MS.
Casey
Perhaps the old Emulator from the WinCE6 SDK might be able to run it, as it had to support native ARM Code, it had to emulate the CPU architecture, but most likely features of newer ARM Cores are missing and WP7 seems to be using them.
But obviously (as seen from the emulator) there is a way to compile the System to the x86 architecture, so maybe Intel gets around to include a decent graphices core and we might see some ULV Atom powered WP7 phones - or not ;-)
Ok, so...
At first I found a ReactOS offical ARM port.
It is here(delete spaces, forum still prevents me from inserting any link): htt p:/ /ww w. rea cto s.or g/wik i/ARM_ Port
At second I don't understand it at all so if anyone are good in this type of thing, tell us is it possible to have it working UNDER HARET?
And finaly at third If yes, is it will be possible to run any applications excluding a orginals one?
And that's all
P.S. There is already a topic here(ht tp:/ /foru m.xd a-deve lopers.co m/sho wthre ad.php?t =791800 ) but it is quite old and not for our device.
Ew, why would you want React on your phone...?
i'd say ehm.. for the heck of it?
don't really think there is a point tho in rOS, both windows that comes natively and android have a massive userbase and for a 'full OS' there is already someone building linux version of Ubuntu.
beside that, the React OS makes use of 'windows' binaries (from what i read on their website.) which are in x86 format as far as i believe, running them on an ARM processor isn't likely to work.
if i'm incorrect please correct me
Not really, all the binaries were written by ReactOS Team and they are open source... So in practise we can compile it and have it running on ARM processor.
And why? Simply. If all the dll's and files can run exe files we should be able to run normal applications like firefox, flash, etc. Maybe not at maxiumum speed(because of alpha build of ReactOS) but still it can be quite useful.
I didn't managed to build it. As far as I read it is imposible beacause of compiler which doesn't compile it correctly, or at all.
If anyone have any ideas how to do it tell us...
P.S. The full source of ReactOS + additional appliactions included is avaible at ReactOS main page.
Well ReactOS to my knowledge doesn't run that well on x86 machines, so I doubt our tired old phones will run it very well...
Rhodbuntu isn't good enough...? I'd say that's your best hope - in theory it will run FF & flash...
ReactOS of course is not the faster system ever but it it a only(actualy) operation system that is in open source and have a fully rewritten binaries, etc.
And BTW you still can't have a flash and Java(SE) running on armel(rhodbuntu)
mafiu95 said:
ReactOS of course is not the faster system ever but it it a only(actualy) operation system that is in open source and have a fully rewritten binaries, etc.
And BTW you still can't have a flash and Java(SE) running on armel(rhodbuntu)
Click to expand...
Click to collapse
Ah didn't realize. What makes you think it'll work on React? lol
Theres a possibility. But as I test the recent version out, there are problems with it, so I dont think its a good idea to port. There are issues from clicking to how things are displayed to windows sticking & not listening to me when I click close or minimize/maximize.
Good day -
I am looking for the best open-source method to root my new Android 7.0
AGM A8 (qualcomm 425 snapdragon chipset, 4x AARCH64 cores) when it arrives.
I am a programmer (not a mobile device expert) with latest Android Studio + NDK
installed with Android 24 & 25 platforms for aarch64, on a Linux x86_64 Workstation.
I do not run Windows, though perhaps WINE might be a possibility; I can run Java, of course .
I will not root my device until I can assemble the source code
/ scripts and build an unlocking tool that I can read and understand - I do not want to
put my entire device security in the hands of a closed-source application that I cannot
read or build - especially one that risks bricking the device.
Please, does anyone know of an open-source rooting tool that will work for my device that I can build
and run with Android Studio ( IntellIJ Idea + SDKs + NDK + LLDB ) - on Linux ?
I also have Qt5 Designer & latest Java tools & gcc-6.3 & glibc-2.25 & binutils-2.28 & many frameworks installed .
Any suggestions gratefully received .
I have found : https://github.com/android-rooting-tools/*.git
but it looks like these take some time to learn how to use & are potentially dangerous
and not likely to work for Android 7.0 .
Ideally, I'd like a tool I can read (in C, C++ , Java, or Python or PERL or shell scripts) , build on Android Studio, run under emulator for testing,
and then push to device and run on device . Is there any such out there ? If not, it may be a long road, but I will follow till I get there / find one / write one.
Thanks & Regards,
Jason
Since windows can already run on snapdragon 835,i want to try it out on my mi6.
Is it possible and if so how to do it?
xpirad said:
Since windows can already run on snapdragon 835,i want to try it out on my mi6.
Is it possible and if so how to do it?
Click to expand...
Click to collapse
We need to have bios for our devices to boot it directly and since we don't have one, our best choice is to wait for a project on xda (I don't remember the name well but I'm pretty sure you can find easily if you search for it) that ports bios for android devices.
But to be honest even if you can run windows on mi 6 there are 2 bad news for you:
1) The vast majority of windows applications are written for x86 architecture and we have arm architecture, so to run them you should emulate either os or run the app in an emulated sandbox - so no good performance.
2) As I said in 1st one, emulation is a must (if you aren't planning to compile all those apps for arm architecture). Also windows 10's capability of running x86 apps on arm is based on that very emulation method, it runs them on a WoW (Windows on Windows) so there's clearly a hit on performance.
I suggest you to not to expect to have a decent windows system running on your arm device but if you need/want to run more basic windows apps, you can try Limbo PC Emulator. That way you can run some older or stripped down versions of windows with no heavy performance loss. For most of the basic things I find MicroXP project enough but don't expect to be able to run Photoshop on that I hope this answers your question.
I see, thank you ccelik97 for your clear answer.
Hello all Intel atom owners,
I am the owner of a device destine for the trash heap (e-waste sucks) but I'd like to save it from that fate. My device is a z2560 soc asus Trio TX201LA. Its tablet half is what has been deemed ewaste by asus & id like to save it from that fate. Windows 10 has also ended support for clovertrail now so that also SUCKS..
This thread is being started to talk about development on these devices that intel gave up on. Android is primary focus but I don't want to limit it to that cuz the soc can do more. I'd like to discuss the following:
1. How the device boots? In what order? What files are used? Variations per device? Similarities between asus & Dell and Samsung (3 largest intel atom inside device makers during 2011-2016)?
2. What tools are available to us to save our devices and in save I mean upgrade.5 tools Ive found that are so interesting are the following:
2A. Intel Manufacturing Flash Tool lite (For dual booting devices specifically?)
2B. Intel Platform Flash Tool Lite (For both atom & intels Edison devices): https://software.intel.com/en-us/articles/flash-tool-lite-user-manual
2C. Intel xFSTK Downloader (rescue flasher, seems to be primarily for bay trail but also clovertrail)
2D. ASUS Flash Tool, not sure about this one, I bet its only for zenfone, have to check.
2E.. Flashall for Edison devices only, so useless for atom tablets: /docs/DOC-25154 https://communities.intel.com/docs/DOC-25154
4. I'd also like to look at droidboot ver 2.0 and 2.1, whats the difference? It seems droidboot is intel and is intel own way of getting android to boot. What is also interesting is that some devices running android 5 got an update that changed droidboot a lot. So much so that it has a uefi partition (dell venue 7, asus memo pad 7 & maybe others) & after that update boots android differently using what seems to be a more generic x86 android (like a pc image).
5. Intel DnX (download and execute) mode. This seems to be a product of Device updates beyond droidboot 2.1 and android 5.0. Id like to discuss if its possible to add DnX to devices that don't have it. It runs from an image off the main disk just like droidboot and even android. So the theory is it could be simply added to other images & devices?
6. Alternative OS options (Reference: https://communities.intel.com/thread/120652):
6A. Sailfish OS devices that are atom based such as the Geeksphone Revolution & Jolla Tablet have sailfishOS, but so do dual boot atom devices including CHUWI hiboot, Hi8, a bunch of Lenovo devices, to many to mention here.
6B. Ubuntu this is possible but only if clovertrail can gain either DNX, droidboot 2.1 or uefi (my theory) .
6C. Remix OS see: https://forum.xda-developers.com/remix/remix-os/release-remix-os-pc-32-bit-t3305916 Remix OS can be run on our devices but again only if we can gain droidboot 2.1, uefi & or DNX (again my theory)
6D. MultiROM for intel (unknown) see: https://www.xda-developers.com/install-use-multirom-xdatv/ There is also support for galaxy tab 3 10.1 a fellow z2560 soc device. So getting multirom support could be added for almost all z2560 devices via this support see: https://www.getdroidtips.com/dual-boot-galaxy-tab-3-10-1-dual-boot-patcher/
6E. Others including second stage bootloaders. Google that term and many come up.
Ok so that is about it. I did not include a lot of links here purposefully, almost every term I used here can be googled for the info I found. The x86 android devices are flexable and able to do more but have primarily not been developed for because intel sucked at advertising them, failed to get them into apple devices and killed them off early. So we are where we are but intel is also very open. There are so many tools to develop for this platform if you know and understand x86. I believe I could rebuild my entire tablet image using the Intel Manufacturing Flash Tool include the newer droidboot 2.1, dnx image, and a updated kernel and system image of android with my device specific drivers and be up and running to a point where I could then dual boot other OS's. I theorize that if you tried this and failed you could still use the Intel xFSTK Downloader to rescue the device completely. Yes I'm a noob & its why I want to learn more via this thread. Think this development is a waste of time, see: https://www.asus-zenfone.com/2015/07/asus-zenfone-2-running-windows-7.html
I'd love to see other intel owners join and discuss these ideas, grab your intel device dust it off and join me in experimenting.
Bumpy boompop shazam.. Hello Atoms not DEAD yEt.. https://www.pcworld.com/article/315...m-chip-in-panasonics-2189-android-tablet.html
Yep, I'm still working on trying to get unsigned stuff to work myself.
pcwizzy37 said:
Yep, I'm still working on trying to get unsigned stuff to work myself.
Click to expand...
Click to collapse
Any progress? Its a shame such a great device is meant to die...
UPDATE. I found this topic.. https://groups.google.com/forum/#!topic/android-contrib/t6AEhwaILUs
Interesting..
madhits45 said:
Any progress? Its a shame such a great device is meant to die...
UPDATE. I found this topic.. https://groups.google.com/forum/#!topic/android-contrib/t6AEhwaILUs
Interesting..
Click to expand...
Click to collapse
Nope, no progress, my backlight also got messed up pretty bad by a diode being defective and letting current pass both ways, so now I cannot change brightness, or else the screen turns off. But nope, still stuck.
pcwizzy37 said:
Nope, no progress, my backlight also got messed up pretty bad by a diode being defective and letting current pass both ways, so now I cannot change brightness, or else the screen turns off. But nope, still stuck.
Click to expand...
Click to collapse
Bummer, What tablet do you have? I have a Asus TF201LA its also know as the transformer trio. The tablet half has android 4.2 and its basically useless, the screen of the tablet is shared with windows 10 dock which I am still using daily. The atom z2560 cpu in the tablet is still pretty fast with 2gb of ram, but no updates or i should say no unlock keeps it useless.
madhits45 said:
Bummer, What tablet do you have? I have a Asus TF201LA its also know as the transformer trio. The tablet half has android 4.2 and its basically useless, the screen of the tablet is shared with windows 10 dock which I am still using daily. The atom z2560 cpu in the tablet is still pretty fast with 2gb of ram, but no updates or i should say no unlock keeps it useless.
Click to expand...
Click to collapse
I have an Acer Iconia One 7 (B1-730HD), which has the Z2560 as well, but a pitiful 1GB of RAM.
pcwizzy37 said:
I have an Acer Iconia One 7 (B1-730HD), which has the Z2560 as well, but a pitiful 1GB of RAM.
Click to expand...
Click to collapse
VERY exciting info to come. I am working with a zenfone hacker who hopefully will help me adapt his bootloader unlock to my device. Ill update when I get something and document everything for you.
Keep us updated. I have a Asus VivoTab ME400c.
Any updates? I have an HP Elitepad 900 G1 with a Z2760.
I have ASUS Memo Pad 7 (K017) with atom Z2520, which is no calling edition with FE170CG...
I have found some new information and ideas for this.
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card
http://www.linuxium.com.au/how-tos
I am trying to understand how you boot from droidboot to a SD card or via USB. I'm willing to try some of these because they do not evolve flashing a recovery which does not match mine. I also found a CWM recovery for the memo pad 10 FHD but whats the point without a new rom. If I can boot linux I could boot x86 android.
I have an acer w3-810 with some (fairly buggy) uefi firmware.
Since this is a windows device I've been able to disable secureboot and play around with unsigned uefi programs. If for some reason your device doesn't disabling secureboot, you might be able to change the variable in your firmware file via uefitool (popular in the bios modding / hackintosh community) and then reflash it if there's no signature checking pre-flash.
On the linux side I've basically gotten no where. The graphics module / kernel params should be set up similar to cedar trail (from my basic research clover is just a lowend version of cedar). But unfortunately that doesn't get me anywhere. Disabling uefi via the kernel param noefi or disabling uefi runtime services gets the display to spazz black and white lines. Going to try to compile a custom kernel later though and see if I can get preboot early efiframe buffers working for earlyprintk.
Interestingly the tablet (through some trickery (force it to boot to a non-present device)) will let you switch the graphics mode of operation between pci and agp