Emulating x10 camera and app from rom 2.1 in 2.2/2.3 - XPERIA X10 Android Development

Hi Developers
I thought I would share an idea I had with the developers on this forum in regards to the issue with the x10 camera not functioning on 2.2 or 2.3 roms. I am an experienced developer, but honestly am not very familiar with the android platform to be able to attempt this idea. Don't shoot me down, this is just an idea but it may be worth investigating.
I understand that there are issues in porting items such as the camera over from a 2.1 rom over to 2.2 or 2.3 due to the change in the android camera api. Instead of rewriting drivers, etc, it may worth investigating or attempting the method I am about to mention.
I have noticed that there have been alot of emulators written to play games on the android, which emulate neogeo, psx, etc. Why dont we emulate aspects of the 2.1 run which can be run in 2.2 or 2.3?
For example, create an app which will emulate the camera from 2.1 rom by emulating the camera api's from 2.1. When you load up your phone and run the 'camera' app, it would actually emulate the camera app from 2.1 within the 2.2/2.3 rom by using the required 2.1 camera api's? I believe this would be the best way of resolving the issue. Plus, this app which emulates the camera from 2.1 would actually just be an app which can be easily installed to work on 2.2, 2.3, or any other future rom releases....
Developers, let me know what your thoughts are on this. If this works, we may be able to always use native features from the x10 already written and developed for the 2.1 rom.
neomira

Thats a very good idea mate,make an 2.1 emulator for 2.3 and up. But mate thats not the problem,its not the camera app itself thats not working,its the inside libs(drivers so to say) that were written in 2.1 (Lets say Windows 98) language and now to switch them to 2.2/2.3 (Windows 7 so to say) is a problem cause those libs(drivers) arent compatible in the operating system,as Android changed ALOT from 2.1 to 2.2 and specially 2.3. You see,Z got the camera ongoing but with software decoding not hardware decoding,thats why you can make a photo but not a video,making a video is too much job for Software emulation (Try it with illusion pro,you'll result in a laggy 15fps 640x480 vid). What they are trying atm is to rewrite the camera driver in a way that it could cope with the hardware decoder . Cause the election is eigher camcorder or video-watching,and 90% want Video decoding rather than the Camcorder.
The camera itself is recognized and stuff but because the camera driver is very old already,it wont work on the new OS's.
Emulation is a good idea but still wont work alright afaik,its like trying to emulate a old windows 95 printer to your windows 7,yes you can emulate windows 95 but you wont be able to use the printer cause windows 7 doesnt know what it is or what to do with it,because the OS that handles the Hardware is the base one,not the emulated one.PSX and so on emulates the remote control cause Android base system knows the hardware that the software translates and makes you be able to use it and can interact with it (touch screen),but that happens because the base OS has and recognizes it,imagine if the base OS wouldn't know the touch screen.Having the buttons displayed on your display would be pointless cause you cant use them as they dont even exist for the base OS which is the important one.
EDIT : Thats why its called Emulation,cause it just Emulates the hardware,doesnt actually use it,has it or recognizes it ,its all software that translates from a unknown hardware to known software for the Base OS,but in our case if the base OS doesnt know the camera,its pointless that the Emulated OS does cause an emulation first needs an input to work,if that input isnt there it just wont work.
EDIT 2 : So its not the camera app,its the camera driver(libs),and there is no way you can use windows 95 drivers on windows 7 unless you rewrite them. (Heck,i remember i couldnt even use W95 drivers on WMillenium,and they had the same base kernel 9x so imagine).
But thats my thought,maybe there is something else i dont know and it could work.
Respect

xtrmshadow said:
Thats a very good idea mate,make an 2.1 emulator for 2.3 and up. But mate thats not the problem,its not the camera app itself thats not working,its the inside libs(drivers so to say) that were written in 2.1 (Lets say Windows 98) language and now to switch them to 2.2/2.3 (Windows 7 so to say) is a problem cause those libs(drivers) arent compatible in the operating system,as Android changed ALOT from 2.1 to 2.2 and specially 2.3. You see,Z got the camera ongoing but with software decoding not hardware decoding,thats why you can make a photo but not a video,making a video is too much job for Software emulation (Try it with illusion pro,you'll result in a laggy 15fps 640x480 vid). What they are trying atm is to rewrite the camera driver in a way that it could cope with the hardware decoder . Cause the election is eigher camcorder or video-watching,and 90% want Video decoding rather than the Camcorder.
The camera itself is recognized and stuff but because the camera driver is very old already,it wont work on the new OS's.
Emulation is a good idea but still wont work alright afaik,its like trying to emulate a old windows 95 printer to your windows 7,yes you can emulate windows 95 but you wont be able to use the printer cause windows 7 doesnt know what it is or what to do with it,because the OS that handles the Hardware is the base one,not the emulated one.PSX and so on emulates the remote control cause Android base system knows the hardware and can interact with it (touch screen).
But thats my thought,maybe there is something else i dont know and it could work.
Respect
Click to expand...
Click to collapse
Thanx for your feedback. I think you may have misunderstood me though. I understand that the drivers, classes, etc have changed since 2.1. My idea is to emulate the old kernel , api's and camera app from 2.1 onto 2.2 or 2.3. Basically writing an x10 2.1 rom emulator, which will only emulate 2.1 camera. It wouldnt emulate the entire 2.1 system.
Think of a neogeo emulator...you load in the neogeo bios and you load in the game rom. Hey presto, u have a neogeo on your mobile...well not really...just emulated..
In the idea i have of emulating the camera from 2.1:
Your bios rom = 2.1 kernel, camera api and x10 camera driver..
Your game rom = camera app from 2.1.....
However, when u would run the app everything would be built into it and u wouldnt have to specify anything. It would load up looking just like the camera app....
Kinda like Wine on linux but only intended for the camera....to save on resources.
Just an idea....
I dont know what would be easier or quicker - to emulate the camera from 2.1 or to rewrite the drive on 2.2/2.3....however, you may need to rewrite it 2.4, 2.5, etc....as api's are always changing. An emulated camera wouldnt need to be rewritten with each new android release. We will always have to wait for someone to rewrite drivers if not emulated.
What do you think? Just an idea....
Sent from my X10i using XDA App

I Understand your idea mate,and im not saying its impossible, it might aswell be very possible and really apreciate your intention ,who knows ^^
But it doesnt sound like it would work for me,cause if its a hardware the base OS doesnt recognize,i doubt the emulated camera would work,cause when the emulation requests to contact the hardware to the base OS,it would just recieve a "unknown/incorrect request".Cause remember,emulations cannot direct-access the hardware,it first has to pass through the base OS.And thats why to emulate a machine as simple as the 33MHz PS1/PSX , you need at least 500MHz CPU to even try to run it,cause it cannot go to the CPU and simply do the chores.
Thats my point of view tho.
Respect

Ah now that you mentioned Wine on Linux.
What happens when you try to play a 3D accelerated game on Wine that tries to access the Graphics Card and you havent installed the graphics card drivers on Linux?It would just fail cause the base OS , Linux doesnt understand what the Emulator is telling it.
EDIT: Also dont know if you know Compiz-fusion for linux (or Beryl),its a Window Manager that gives you alot of effects and stuff on windows and many things(search beryl on youtube) but if you dont have a graphics driver installed ,it would just say "Hardware Graphics Card not detected,it cannot continue" so obviously you cant use VMWare to create a virtual machine and emulate the drivers on that VM cause for it,it wouldnt even exist as "Unknown" ,it wouldnt even exist at all.
Hope that helps you understand it more.
Respect

xtrmshadow said:
Ah now that you mentioned Wine on Linux.
What happens when you try to play a 3D accelerated game on Wine that tries to access the Graphics Card and you havent installed the graphics card drivers on Linux?It would just fail cause the base OS , Linux doesnt understand what the Emulator is telling it.
Hope that helps you understand it more.
Respect
Click to expand...
Click to collapse
hmmm you may be right. what about virtual pc though? that is probably a better example. you can actually use hardware....for example, i could get a soundcard working properly on windows xp so i installed windows 98 via virtual pc....bingo, it worked....i could keep making music without buying another $1800 soundcard for ages.
therefore, have an app called "x10cam" which is emulates the 2.1 rom just like virtual pc....when you click on it, it would load emulate 2.1, but a completely cut down version with no apps, just the camera app and maybe even go straight into the camera app. on exit of the camera app, it quits the emulation and goes back to your 2.2/2.3 rom or home screen.
i dont know....sounds like it may work but might take some time...however, it may benefit in the long run though as the cam driver wont have to be rewritten each time of a new android release.
thanks for your replies too. i do appreciate it. someone may read this posts and come up with an alternate idea which would work

xtrmshadow said:
EDIT: Also dont know if you know Compiz-fusion for linux (or Beryl),its a Window Manager that gives you alot of effects and stuff on windows and many things(search beryl on youtube) but if you dont have a graphics driver installed ,it would just say "Hardware Graphics Card not detected,it cannot continue" so obviously you cant use VMWare to create a virtual machine and emulate the drivers on that VM cause for it,it wouldnt even exist as "Unknown" ,it wouldnt even exist at all.
Hope that helps you understand it more.
Respect
Click to expand...
Click to collapse
Thanks for mentioning Beryl, i actually wasnt aware of Beryl until you mentioned it. Much appreciated.

neomira said:
hmmm you may be right. what about virtual pc though? that is probably a better example. you can actually use hardware....for example, i could get a soundcard working properly on windows xp so i installed windows 98 via virtual pc....bingo, it worked....i could keep making music without buying another $1800 soundcard for ages.
therefore, have an app called "x10cam" which is emulates the 2.1 rom just like virtual pc....when you click on it, it would load emulate 2.1, but a completely cut down version with no apps, just the camera app and maybe even go straight into the camera app. on exit of the camera app, it quits the emulation and goes back to your 2.2/2.3 rom or home screen.
i dont know....sounds like it may work but might take some time...however, it may benefit in the long run though as the cam driver wont have to be rewritten each time of a new android release.
thanks for your replies too. i do appreciate it. someone may read this posts and come up with an alternate idea which would work
Click to expand...
Click to collapse
Well,creating a VM (Virtual Machine = Virtual PC) might be able to make it work if the developer of the base ROM can at least make the OS Recognize the camera and access it (eventhought no image cause of the 2.1+ incompability),yes that might be possible . But still gotta write at least some basic drivers for the Cam.Lets say for exemple Z's 2.2 might perfectly be able to do what you've said cause the OS has 100% access to the camera,but cannot camcord cause of the base OS but the emulated one might aswell.
Yes that is a good idea as long as at least basic drivers are written.
And about you beeing able to Virtual PC that sound card,means that the base OS could already access it but it just didnt know how (Its like when you go on "Device Manager" and you see your device in "other" and it says the name it just cannot correctly interact with it cause of limitations)
Eventhought a Virtual Machine on our 280Mb of RAM wouldnt go too smooth but yes its a very good possibility.
Respect mate

sounds like a good idea and it will work in HD with the nice SE user interface .... it may take a long time to boot into camera app.... but still better than switching between roms for camera....

xtrmshadow said:
Well,creating a VM (Virtual Machine = Virtual PC) might be able to make it work if the developer of the base ROM can at least make the OS Recognize the camera and access it (eventhought no image cause of the 2.1+ incompability),yes that might be possible . But still gotta write at least some basic drivers for the Cam.Lets say for exemple Z's 2.2 might perfectly be able to do what you've said cause the OS has 100% access to the camera,but cannot camcord cause of the base OS but the emulated one might aswell.
Yes that is a good idea as long as at least basic drivers are written.
And about you beeing able to Virtual PC that sound card,means that the base OS could already access it but it just didnt know how (Its like when you go on "Device Manager" and you see your device in "other" and it says the name it just cannot correctly interact with it cause of limitations)
Eventhought a Virtual Machine on our 280Mb of RAM wouldnt go too smooth but yes its a very good possibility.
Respect mate
Click to expand...
Click to collapse
Yes, you are right. The only issue I can see is that a VM for just the camera functions would have to be a VERY VERY cut down version of 2.1 due to the 280mb of RAM. Otherwise it would be so slow.
Thanks xtrmshadow for the positive feedback. Maybe somebody might use this thread as an idea for something.

hemo1001 said:
sounds like a good idea and it will work in HD with the nice SE user interface .... it may take a long time to boot into camera app.... but still better than switching between roms for camera....
Click to expand...
Click to collapse
thanks hemo1001. much appreciated feedback.
that is my thought exactly, to prevent having to switch roms entirely just for the cam. also, if you think about a completely cutdown VM of 2.1 to access the cam, i dont think it would be cut down to only run what is necessary for the camera to function. I think it would be a better alternative than switching roms.

neomira said:
Yes, you are right. The only issue I can see is that a VM for just the camera functions would have to be a VERY VERY cut down version of 2.1 due to the 280mb of RAM. Otherwise it would be so slow.
Thanks xtrmshadow for the positive feedback. Maybe somebody might use this thread as an idea for something.
Click to expand...
Click to collapse
Agreed ^^ , Making a VM program for Android would be fairly easy as there are loads for Linux (VMWare,VirtualBox + more) and a very core version of 2.1 with only the necesary things for the task(No launcher,drivers for anything but camera,no apps etc).
Also i agree hemo1001 ,well said mate haha.
Hopefully someone that is very experienced with Android (Im only experienced on C++ and Hardware ><) takes a look into this and thinks about it ^^
Respect.

xtrmshadow said:
Agreed ^^ , Making a VM program for Android would be fairly easy as there are loads for Linux (VMWare,VirtualBox + more) and a very core version of 2.1 with only the necesary things for the task(No launcher,drivers for anything but camera,no apps etc).
Also i agree hemo1001 ,well said mate haha.
Hopefully someone that is very experienced with Android (Im only experienced on C++ and Hardware ><) takes a look into this and thinks about it ^^
Respect.
Click to expand...
Click to collapse
I hope so too mate. It would be great.
Sent from my X10i using XDA App

the client on a vm depends on the hardware and drivers from the host. you can't emulate hardware on a client that doesn't work on a host.

At least we can emulate it in 2.2 freex10
Sent from my X10i using XDA App

Using New Drivers
The cameras for the new sony models are different. But maybe there is a chance that
we can modify their libraries and use them on our phones.
I am not familiar with the camera libraries so I don't know how hard it is to modify the new libs in the xperia arc to match our hardware but it should be possible right?

i have read the complete discussion..phew...amazing amazing u guyz are u ll gave me a triggering pulse which straight away took me o my Embedded System Lectures from College..!!! Jokes apart i think the logic of Emulator is a better option as of now..atleast get a working camera..lets hope..all our experts are actually working hard hope for teh break through very soon..m not good with programming and stuff..so unfortunately i cannot even think but the whole logic behind Emulators was actually cleared after 2 yrs since i finished my Engineering in IT..lol..great stuff guyz..Proud to be on XDA since 5 yrs now sorry for going off topic..

camera - email.apk
hello,
i think since two month ago, if i write this or not ...
now, it's looking good for this information, but i dont know,
if this could help the camera-problem.
i'm working as an admin in a firma with some developers.
during android V1.6 - V2.1 we could sync exchange-server with no "device-limitation" by given all 5 minutes a device-code in.
since android V2.2 the email.apk changed very hard ... now we have to give all 5 minutes a device-code in. but the devices are not devices from the firma, so we dont sync anymore. but the info-lost is sometimes very critical.
one of our developers making an email.apk or find an email.apk with no exchange-securitas. the result was that barcodescanner and all other aps with camera inside dosnt work. although the camera.apk
now there is an email.apk outside with NO-EXCHANGE-Securitas and NO-Camera-PROBLEM.
i am glad to use the email.apk since 2 ore 3 weeks without any problems and securitas.
i dont belive that is only a driver/lib-problem because i used a htc leo and have the probs (and solution) that i above describes.
what i mean is, that could not only a driver-problem ... that could be a securitas-problem like ... "if you manipulate email than your cam doesnt work!"
i hope this is not for 1000% to trash and my bad english will automaticly changed to good-english by a developer with bad-english too (bad + bad = good
okokur

okokur, i didn't understand a thing you wrote but it was a very interesting read! i hope someone woth more knowledge picks it up.
this is a great thread guys, love your outside of the box thinking, brilliant!
sorry for going OT, best of luck, peace

Cool! The app works on Froyo & Gingerbread.. problem is in the drivers for the camera and kernel, which are being prioritized in jerpelea's gb build..
Imagine if something similar to virtualization took place at boot time?

Related

windows 95 on HD2 (for real)

Have you guys tried Windows 95 on HD2? It is a Bochs emulation, I can get it full screen (only VGA though) but can't get the mouse work. Although it is freeware, I saw it on a warez site and I don't know if it is legal or so, hence I'm not posting any links. Just google it if you're interested.
why would you do such a thing?
yngvebn said:
why would you do such a thing?
Click to expand...
Click to collapse
Why not ?
(curosity killed the cat)
me too
yeah im trying this too, i have to move the bochs windows around the screen, if you go on config, then misc and tick mouse then go on vga keyboard and press f12 and make sure the mouse is ticked it should eventually work, mine did.
anyone who gets it to work please fill us in on the blanks lol love the HD2 and it would be cool to get this bochs working, once we have this working we can simply use the configured settings and make our own win98 image
qemu
You should try Qemu instead, there is a russian port of it for WMobile, i have tested it on the HD2 with windows 95 and works surprisingly good,muuch faster than bochs, only issue is the small keyboard (BSB with pinchzoom helps lots though) and mouse implementation is no good...
I think if this port evolves and matures focused in the multitouch ( a bit like FPSECE is heading with v1.0) it could be one of the nicest surprises on our HD2!
Also played some games, Starcraft being one of them and its quite playable,even the intro and cd sound works (though lags a bit) Its by no means as fast as the pocketstarcraft port, but this is the real thing, all units and bloodwar expansion on it so its quite a nice
Windows itself works pretty fast once the vga drivers and all components are properly installed,there is one issue with the mouse icon,and few other glitches, but still nice and usable.
Im having lots of fun just installing stuff.
If there was any developer over this great forum working on the interface mainly, it would be amazing!
with some free time i will try to post a quick video in youtube if anyone is interested
miko3d said:
You should try Qemu instead, there is a russian port of it for WMobile, i have tested it on the HD2 with windows 95 and works surprisingly good,muuch faster than bochs, only issue is the small keyboard (BSB with pinchzoom helps lots though) and mouse implementation is no good...
I think if this port evolves and matures focused in the multitouch ( a bit like FPSECE is heading with v1.0) it could be one of the nicest surprises on our HD2!
Also played some games, Starcraft being one of them and its quite playable,even the intro and cd sound works (though lags a bit) Its by no means as fast as the pocketstarcraft port, but this is the real thing, all units and bloodwar expansion on it so its quite a nice
Windows itself works pretty fast once the vga drivers and all components are properly installed,there is one issue with the mouse icon,and few other glitches, but still nice and usable.
Im having lots of fun just installing stuff.
If there was any developer over this great forum working on the interface mainly, it would be amazing!
with some free time i will try to post a quick video in youtube if anyone is interested
Click to expand...
Click to collapse
I would be interested if you could post a little guide for Windows 95 on QEMU or a video. Thanks.
Many thanks for this tip miko3d!
LOL!! HoMM2 are fully playable on my HD2 using this russian pack. This is superb-completely-amazing!
I see great potential there, sadly looks like this project is not going to be developed further..
All the details are there (just use google translate):
http://forum.pdaprime.ru/index.php?showtopic=45356
Hey that Qemu solution seems a lot better than the Bochs one indeed... got both my Win95 and Win98 images to run, and the mouse is even useable!
I didn't get the keyboard though, there are the couple of keys at the bottom, but is there a way to get a full onscreen keyboard within qemu, or do we have to play with the hardware button to show/hide SIP trick?
guys, this seems interesting.
instead of doing emulation, can we do something like the haret?
boot the phone from storage card and run win xp tablet on it?
what's going on? does it work? will u provide any screenshot?
ruffruff said:
instead of doing emulation, can we do something like the haret?
boot the phone from storage card and run win xp tablet on it?
Click to expand...
Click to collapse
No, because PC versions of Windows are made to run on PC x86 processors, not on the ARM ones used in mobile devices. So, emulation is necessary.
Some screenshots...
nice, but what actual use is this, better to get ubuntu up and running and we can really have a play then.
None apart from fun... but ubuntu or linux in general wouldn't be any better if it's an x86 build. Emulation just makes everything way too slow for comfortable use.
Windows 95 runs also nice and perfect...
only thing is- i got no mouse xD
touchscreen is not working =/
edit: ah okay im still useing bochs, thats why ...
can anyone upload this files in the forum or on a hoster like rapidshare/uploadet ?
because i dont want in reg. me on this russian forum
yeah i second that but a compiled version!!!!
I created simple compilation with the latest QEMU WM port I could find.
All the credit for this goes to mamaich (excellent work!), I am merely sharing these files.
Links:
[dead]
Instructions:
1. Extract QEMU_WM.7z to the root folder on your SD card.
2. Extract additional packages (Win95 or Homm2) to 'emul' directory in QEMU folder.
3. Use qemu_launcher from QEMU folder to start selected VM.
Note: QEMU must be placed in '\Storage Card\QEMU\' directory, otherwise you have to edit 'cmdline.txt' etc files accordingly.
Generally, everything works well and pretty fast (as for emulation). Homm2 is completely playable (with sound!). On Win95 mouse cursor is a bit dodgy - it looks like button clicks are not detected correctly.
Please note that this software (Homm2, Win95) although very old, is still copyrighted, so don't download it if you haven't got license for it. If these links violate forum rules, please remove them.
Hi just a few quick questions:
Does the internet work on windows 95, e.g. can i go on internet explorer and actually go on websites?
Is it possible to run windows 98 on HTC HD2?
I've seen youtube videos with a HTC HD2 running windows xp, vista or 7 on them through remote desktop, is this possible or just a fake?
http://www.youtube.com/watch?v=QFiDZ_wBAtM
Can you please post some screens of your HTC HD2 running windows 95 with internet explorer on the screen, thanks alot!
sagam12 said:
I've seen youtube videos with a HTC HD2 running windows xp, vista or 7 on them through remote desktop, is this possible or just a fake?
Click to expand...
Click to collapse
Well as you said it's through remote desktop. So it's not fake, but the HD2 is not "running" them either, just displaying on its screen what another computer is running, and interacting with it.
aszu said:
On Win95 mouse cursor is a bit dodgy - it looks like button clicks are not detected correctly.
Click to expand...
Click to collapse
They are, but it needs playing with one of the bottom buttons. See attached picture, the button pointed by the arrow is the key. When it's grey (default), a tap on the screen will do a left click. So a tap&drag will do a left click and drag, i.e selection, moving stuff, etc, which is why it looks weird to you. Tap the button, it turns to black, and now a tap&drag on the screen moves the cursor without clicking, like a laptop touchpad. The button on the left marked "rb" does the same as grey but with right mouse button.
So you need to turn the thing black, move the cursor where you want, tap it to grey, tap or double tap to single/double click, tap it to black, move to some other place, etc, toggling the button each time between movements and clicks. Not very convenient, but works.
I'd gladly try the net etc, but I just tested on my Win98 image, and it has IE and all network drivers stripped out, so no way. Plus, I still haven't found how to get an onscreen keyboard. And W98 is very slow.
Will have a look under W95 tomorrow, it seems that one was complete.

Mupen64plus Android edition [port] [new n64 emulator]

Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant​
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated

[Q] Best ROM for "Ubuntu for Android"?

First things first, I'm NOT talking abot canonical's project "Ubuntu for Android"which dual-boots your phone.
I'm talking about this: http://sourceforge.net/projects/linuxonandroid/?source=navbar
Also, this project requires that the device supports a loop device (configured in the kernel). I know that there are some ROMs that support it, but I want a ROM that is really light (so no graphics tweaks or TouchWiz UI) and that I can use to run that.
Also I have a bit experience to build my own ROMs (although I've never shared them), so tips to build one myself are appreciated as well.
I hope that is enough to answer my question,
thanks in advance
shivam89 said:
First things first, I'm NOT talking abot canonical's project "Ubuntu for Android"which dual-boots your phone.
I'm talking about this: http://sourceforge.net/projects/linuxonandroid/?source=navbar
Also, this project requires that the device supports a loop device (configured in the kernel). I know that there are some ROMs that support it, but I want a ROM that is really light (so no graphics tweaks or TouchWiz UI) and that I can use to run that.
Also I have a bit experience to build my own ROMs (although I've never shared them), so tips to build one myself are appreciated as well.
I hope that is enough to answer my question,
thanks in advance
Click to expand...
Click to collapse
Assuming you have a 5.0 player...
That method of running linux on android is known as the "chroot" method which allows you to run linux alongside android, and use vnc to use the gui.
I believe that loop device support has been enabled since the initial development of the 3.0 kernel for the 5.0 and I sure that it's enabled on all the ROMs that I've built. This line in the defconfig confirms it:
https://github.com/Meticulus/nutell...rm/configs/cyanogenmod_venturi_defconfig#L975
I personally have done this before but it was on the stock ROM (long time ago). It should work on any ROM. There are even apps in the play store that will help automate the process for you...
https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid
For me, it was novel. I had alot of fun doing it but it wasn't practical to use as a daily driver. Keyboard usage in vnc apps is a bit of a pain and because of the small screen, it was difficult to use the mouse to hit buttons. Minimize, maximize and close; on windows was especially difficult to use..
Anyways... Good luck...

Would it be feasible too...

Would it be possible to emulate android on an android phone? As in, you could supply an app with an android version (or have the app build it for you) an emulate or run it. Any time it asks for something device specific, it would simply run the request back to the stock OS. Said app would kill all but the essential android processes to improve performance. And to return, it could add a shortcut to the app drawer that would close everything and return to the stock. Using this, could we create universal, or at least wider, distributions of android?
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Darkcon said:
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Click to expand...
Click to collapse
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
The Original Leppa said:
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
Click to expand...
Click to collapse
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Darkcon said:
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Click to expand...
Click to collapse
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
The Original Leppa said:
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
Click to expand...
Click to collapse
Hmm you've got a point there, this could be used to root a phone thats unrootable effectively, like the android emulated inside an Iphone that some people did in the Iphone 4 days
all depends on implimentation, you'd have to set up the emulator to trigger normal events, like power saving cpu states etc in response to the emulated android os's requirements
I've been thinking.
Let's say you decide to emulate AOSP Nougat. You then installed the official Pixel Launcher. While emulating, it would act as it should, as it would be entirely identical to if you were running Nougat.
Then you close the emulation. You then try to open Pixel Launcher; it's already installed. Would it crash?
Ok then...
Would I just look for adb? Or does adb simply ask something else to emulate?

Windows 11 (Ghost spectre ultralite edition prebuilt iso) usable performance 2023

Hi guys,
I recently dug up this ancient piece of hardware wondering if i could get it back into a usable state again, as expected the normal windows 11 edition was almost unusable. So i created an ISO based on https://tech-latest.com/ghost-spectre-windows-11/. Its completely stripped down version of Windows 11 and has an intuitive command line tool to install your needs.
NOTE: As with all custom windows builds be careful about putting in personal data, i don't know the sources, I just added the drivers.
Bugs:
All drivers are already installed, only thing not working is Camera... but let's be honest... that thing never worked please SHARE if you found a solution
Instalation instructions:
Download iso here: https://mega.nz/file/5YwHyRaR#kgjrw2iQI23EvW2V6ReqlUu1-Rs9GT60zzhPXSNU-CA
Download Rufus here: https://rufus.ie/
1. Use Rufus to create a bootable USB
2. Dont use any of the Rufus options to customize your install
3. After creating the USB connect it to the tablet through a USB OTG adapter
4. Press F2 while booting up, select to boot from USB
5. Wait till in the windows install screen (this can take up to 15 mins).
6. Go through windows installation (can take up to 1 hour)
7. your pc will automatically reboot
8. set up admin password
9. connect to wifi
10. open GHOST TOOLBOX on the homescreen.
11. you'll see a menu with numbers, type in the number of the feature you'd like installed and it will guide you through the installation.
Tip: start downloading a browser first
yeah I know, the install time is insane. But at least you will have a semi-usable tablet.
MAKE A BACKUP OF THE ISO( IT'LL BE ACCIDENTALLY DELETED IN THE FAR FUTURE).
THIS ISO WILL ONLY WORK FOR THE FIRST EDITION YOGA BOOK WITH WINDOWS 8. DONT SEND ME A DM QUESTIONING ME IF IT'LL WORK ON [INSERT GENERIC CHINESE BRAND]
Good luck and may the odds be ever in your favor
“I installed Ghost Spectre Compact without DEF and I would like to add it. Can I upgrade without reinstalling?” Thanx
You saved my life! Your ISO was very helpful, and the solution you provided was both light and stable. My yoga book was broken and wouldn't boot, but now it's working very well. Thank you!
kakalotfreedom said:
You saved my life! Your ISO was very helpful, and the solution you provided was both light and stable. My yoga book was broken and wouldn't boot, but now it's working very well. Thank you!
Click to expand...
Click to collapse
Thanks, it's good knowing I didn't do it for nothing. I mostly created it for myself but was so surprised with the usability that I decided to share.
Tbh I'm not really sure if this ISO is compliant with the MS Terms of Service. So I would recommend to download a backup
At least this ISO makes the tab usable and I'm happy I could share this goodness
Btw, I discovered that the camera's are not working with this iso. Please let me know if you found a solution
just working with superlite and its not good for audio production like Pro Tools my CPU not working with all cores even if i want to change to make my CPU work with full core from
System Configuration in windows >boot>Advanced option
is grayed how can i fix this?
and if i want to go with compact is any way to ypgrtade without losing setup plugins and configuartion installed before to make the system
the flying dutchman said:
Thanks, it's good knowing I didn't do it for nothing. I mostly created it for myself but was so surprised with the usability that I decided to share.
Tbh I'm not really sure if this ISO is compliant with the MS Terms of Service. So I would recommend to download a backup
At least this ISO makes the tab usable and I'm happy I could share this goodness
Click to expand...
Click to collapse
I attempted to install Android and Windows Lite on my slow Yogabook, but it resulted in it not starting up properly and being unresponsive to touch. However, with the help of your software, my old sluggish Yogabook now looks great and runs smoothly - almost like a brand-new device. Thank you very much for your assistance.
about the camera, check on setting, camera VO2740 is working well for me. You can try to update the drivers (instead of the battery driver)
Minanapil13 said:
just working with superlite and its not good for audio production like Pro Tools my CPU not working with all cores even if i want to change to make my CPU work with full core from
System Configuration in windows >boot>Advanced option
is grayed how can i fix this?
and if i want to go with compact is any way to ypgrtade without losing setup plugins and configuartion installed before to make the system
Click to expand...
Click to collapse
This is weird. Tbh I never looked into that and the perceived speed of the device is faster. Maybe there are some changes in this build that affect the multi core performance? Maybe the lack of TPM and windows 11? Is hyperthreading and or virtualization enabled? And have you tried it on the normal version of windows 11 and was it different? It could also have something to do with the limited CPU. I'm busy with my graduation internship, so don't really have time to delve into it myself

Categories

Resources