People, is there any Windows App that can allow us to run Cooked and other ROMs on a Computer, just for testing or for seeing that particular ROM's interface ?
If yes, can you provide its link along with instructions ?
anyone have any idea bout this ?
Erm hello ?
A ROM is more than just an interface, there are also drivers which make up the ROM, which are targetted towards a specific set of hardware. In order for an emulator to be able to run any cooked ROM out there, it would need to be able to emulate the full range of hardware on the market. This is obviously not feasible to do. The emulator provided by Microsoft in the development SDK emulates a specific set of hardware, and the image that comes with it is targetted at that hardware.
There is one thing you could do, dump the emulator image, and rebuild it using the cooked ROMs parts, but keeping the emulators drivers, kernel, etc. However, you won't be able to bring in any device-specific software (like stuff that talks to the GPS, or G-sensor, etc)
At that point you will have gone through quite the effort just to see a ROMs interface But it might be useful for testing.
Also, moved thread to Questions and Answers.
Related
Hello the community
I would like to know how to perform a soft reset (reboot) from a WM user interface. Of course there is a lot of external programs and utilities providing such the functionality also, but I guess there should be a mechanism built in WM.
I am sure there should be a DLL responsible for that, so probably there is also a way to execute this DLL?! Something like Windows’ rundll.exe?
My device is HTC p3600/Trinity with WM5, but I think it doesn’t make sense.
Your advice would be much appreciated,
Br, Alexey
dll mean dynamic linked libary
which pretty much mean it's a lib full of functions that
other apps call you cant normaly just call it's functions from
the GUI
yes, I know what DLL actually mean
And that’s why I made a guess about a possible way to run DLL similar to rundll.exe
I would prefer using something like reboot.exe, but if such a program isn’t provided along with standard WM, I don’t mind using workarounds like running DLL, if possible.
Anyway, my question was not about real nature of DLL but the way how to perform a reboot using standard functions of WM.
Check out the SDK documentation, MS might have made a direct api to achieve this through a direct rundll type action, but the easiest way is just to code a tiny app and launch it, eg
http://www.pocketpcdn.com/qa/softreset.html
VJEschaton will reset in a variety of fashions.
V
Thanks
Is there a way to compile such a tiny application without installing any huge C++ IDE? Something like command line compiler downloadable thru a simple ZIP file?
shkaff said:
Thanks
Is there a way to compile such a tiny application without installing any huge C++ IDE? Something like command line compiler downloadable thru a simple ZIP file?
Click to expand...
Click to collapse
The C# compiler is free and can produce WM executables. The only problem is that you must instruct it to use the .NET Compact Framework libraries instead of the normal ones. I readied a guide when the last OS was WM2003. I don't know if it is still working, but actually I have no reason to think it won't. Just choose the right subset of files.
Here is the link:
http://www.jargoncode.it/tips/netcfcompile-eng.htm
If you want a C++ compiler... I don't know.
I'm a professional programmer, and I'm baffled. It seems that there is a whole "smartphone scene" and it's intimidating. I'm a Java expert and am comfortable with the Android SDK in Eclipse. However I'm completely baffled by the prospect of getting tethering to work on my Nexus One.
One thing that baffles me, for example, is the concept of a "ROM". Is there a ROM on the N1? I thought that ROMs haven't been used for 10 years. I was under the impression that the N1 is basically a little PC running Linux, which means that it should only have a bare minimum of a BIOS and everything else would be on "disk", or flash.
Another thing that baffles me is the concept of "rooting" the N1. It's running Android, which is an open-source mobile operating system. And, as far as I know, I have the permission to change all bits of the phone. Heck, that's part of the appeal! To say that you have to "root" your N1 is like saying that you have to "root" your Ubuntu box - it just doesn't make sense.
Complicating matters is the release of Froyo. I simply don't know enough to judge whether the actions required to upgrade the N1 to Froyo are compatible with the actions required to install a tethering app.
And that's the thing: I'm not just interested in installing tethering. I want to understand what I'm doing and why. I'd like to understand the options choose intelligently between them. There are so many resources online which are trying so hard to be helpful, but which don't really answer these simple questions.
I really appreciate your help.
-Ablation
search the correct forum for your phones model here on xda. some roms provide tethering preinstalled
check this thread for more info
http://forum.xda-developers.com/showthread.php?t=668090
while that targeted at g1, its the same concept. again search xda for the n1 section
Thanks for the link. However, I think I need a more conceptual introduction to the scene. The essential question is: what are the bits? On a PC you have:
1. BIOS
2. Disk
3. Peripheral firmware.
The disk is further broken down:
1. Bootloader
2. Operating system
3. Drivers
4. Applications
When you say ROM I assume you mean some combination of BIOS and Peripheral Firmware?
Ok, I know much of what I'm about to ask has generally been answered or discussed in other posts, but I could really use some more direct/specific answers to my own questions.
My first question is about hardware drivers. To my understanding, a great many, if not most, of the more common wifi drivers are incorporated into the latest linux kernels. If this is the case, will more or less any Android system run on a device so long as the appropriate kernel is provided?
To be a little more clear on that, I'm actually trying to learn Android development (both for apps and building roms) on a cheap Chinese tablet that I picked up. Naturally it already has a version of Android 2.2 pre-installed. However, I have not been able to extract the contents of the boot.img or the system.img, I keep getting an error, whereas I can unpack the SDK img's no problem. So I was hoping that I can get away without compiling a custom kernel, use the already existing one, and go ahead with tweaking the system.img from either the AOSP or SDK sources. Getting the source code from the manufacturer may be impossible since I can't even seem to find out who the manufacturer is or get their contact info.
I'm actually looking to port CM7 to my wife's LG Shine Plus eventually, but I don't want to pull a Tim Allen on her phone so I want to get some experience and feel for working with Android's internals on my tablet.
So my next question is still about drivers, but what I want to know is how are things like the LCD, touchscreen input, audio output, wifi and the cell radio handled on a typical Android device? Is it mostly handled by the hardware itself with the Android framework or kernel just passing universal APIs or do the drivers for each individual piece of hardware need to be compiled into the kernel? As in the gkisystem for radios, is this handled by the kernel or the framework? Which kinda brings me back to my first question, if it is built into the kernel itself, can I not use, for example, the already existing kernel on the LG Shine Plus (it's running 2.1) to port CM7?
Any and ALL help is honestly and truly appreciated. I've been looking for detailed answers for these questions EVERYWHERE.
** just bumping this post so that it can get seen**
any help or advice at all?
Hi there, this is my first post on xda so forgive me if this is put in the wrong forum.
I am new to android and wish to play around with the emulator.
What I want to do is to create my own piece of virtual hardware that can collect OpenGL commands and produce OpenGL graphics.
I have been told that in order to do this I will need to write a linux kernal driver to enable communication with the hardware. Additionally, I will need to write an Android user space library to call the kernal driver.
To start with I plan on making a very simple piece of hardware that only does, say 1 or 2, commands.
Has anyone here done something like this? If so, do you have any tips or possible links to extra information?
Any feedback would be appreciated.
Regards
Has anyone done this?
Bump Bump
Im surprised this is left unanswered.
Yes, you can do this. There are several ways to do so, but I will explain 2 good options for you.
One: Use AndroidSDK. It's configured for android and simple to set up.
Two: Use virtualbox. If you have the android ISO, you can install it as a bootable image in this software. This gives more functionality than AndroidSDK, but it is not as simplistic. There are settings you will need to adjust to get it running. For a working Android ISO with limited functionality, you can download this: http://www.android-x86.org/download
Hi there, not sure if I'm on the right forum, but this seemed like the safest place to ask.
I have this project in my head that I would like to try, but I have no idea if it is even possible.
I'm currently doing a bachelors in computer science and as a way to learn, I would like to take on a big project.
As will soon become clear, I am a linux noob and know nothing about android development, but that's what I'm trying to change here.
Some time ago I bought a Chinese ereader (rebranded BOOX C67ML - using a rockchip rk3026 SoC, don't know how important that is -) and it's decent but it also kind of sucks. It runs android which overkill for a device like this if you ask me. When I look at the kindle or kobo ereaders, they have their proprietary os that is also Linux based, but much more streamlined without unnecessary features. This device doesn't even have wifi, so what am I going to do with full android on an e-ink screen? It only drains my battery more than it has to.
My question is, how feasible is it to create my own 'OS' for this device that is also Linux based and lightweight? I know that android devices can run gnu/linux in a sort of vm on top, but is it also possible to install this directly on the device? Wipe android and install a custom linux distro as you would a custom ROM.
Is this possible? Where do I begin? Any information on how the linux kernel underneath android functions and differs from a standard linux kernel would be great. I'm not asking for an easy solution served on a platter, I just want to know if it is possible and why or why not? Where do I go to learn about how to do this, point me in the right direction?
In searching around I came across postmarketOS, from what I understand they are trying to do something similar, only completely open source. No proprietary drivers for anything. For this project that is not a goal for me. If I can reuse parts of the android rom that it is running right now, I have no problem with that. Updating and keeping it up to date are not really a priority, I just need this to run a single application that works. Could also be that I completely don't understand what they are trying to do and I'm way off, but if so, please tell me what I don't understand and where I go to learn.
TLDR: Lightweight 'desktop' linux instead of android on an ereader, is it possible? Where do I start? Point me in the right direction please.
PS: If there is a better solution for this problem entirely, please do explain.
For anyone interested or with a similar idea, I'll just post what extra information I find here.
I stumbled upon Halium and Libhybris today. From what I understand, libhybris provides a compatibility layer between the android kernel and posix compatible applications. Halium uses libhybris and tries to create a common base that can be used to develop a non-android os for an android device. Please correct me if I'm wrong.