I'd like to know what the absolute minimum system requirements for using activesync are. (The official MS site isn't very helpful regarding this question)
I am a mac user so I cannot install most programs on my device through my desktop. I was advised to set up my Blue Angel through a PC and then backup using Spritebackup, so that I can always restore in the event of a hard reset, but the restored files just have too many errors to be useful.
As I paid enough for my device I figured that I would get the cheapest, crappiest PC I could solely for the purpose of initial syncronization.
Anyone know what that system might be?
Thnx
my guess is 100% the same spcs which is required to run windows itself
Hi,
I use pda from the Qtek 9090 with wm2003. After I have purchased one Qtek 9100 and finally one Universal Qtek 9000 with the hope ... I have expended a lot of money for these pda. These PDA, better, windows mobile, have donate to me bugs, freeze, lost call, lost sms, random reset, ecc ...nervous and austerity.The list is very long!
In all these years I have never seen one, only one windows mobile rom stable and fast, not super-fast, only fast, usable. The same is for windows on desktp or server arch. Random reset, freeze, blue screen, bugs, ecc ...
Now my question is simple: I have read here which you develop new roms for passion. Then, it is not for profit. Then, why all developers not develop with another o.s? Today exist Linux, Symbian, Android, Open moko, and a lot of other probably.
I not understand why use windows. If all Senior present here abdicate windows for linux, per example, probably after less than one year, all of you will develop a very stable, fast and usable operating system!
Really I not understand why ...
Best Regards and many thankS for your attention and your work
If you search around the Forums for threads on "Android" you will find out where they are in the Linux process.
Generally Getting Linux to work on a handheld device is not as simple as installing it on a PC.
Windows Mobile comes from the Manufacturer with everything working, there for it is easier to tweak Windows then to write a whole new base code, like Linux.
Hi,
first, thanks for the answer.
Yes, I know which linux and android are work in progress. But are work in progress from long time, maybe because there are few developer which work on it?
However, usually open source software which control the hardware, drivers, is based on reverse engineering. Because some Manufacturer not provides the datasheet of the hardware. Cause of this, you have reason. But probably if a great number of capable developer want, with the current relase of linux for pda, is possible to make easier this too.
Unfortunately I have some trouble to speak or write English like my native language. However, I hope have wrote aprox correctly.
Best Regards
If we port symbian to out devices, there is a chance that this site could get shut down. You see, each windows mobile device is sold with a license to use windows mobile, similar to how you have to use a serial number to register certain applications.
Because we already have the license to windows mobile, there is not any specific legal problem to creating custom roms.
However, because we have no license for symbian, we are not legally and contractually allowed to port it to our devices, because the makers of symbian recieve no licensing fees from us, which is essentially piracy.
Moved To General Discussion.
I can say that when cooking ROM's, I'm fixing all the pieces of the OS that bug me and add parts that are missing. Through trial and error, I get my greatest OS!
I have no doubt on your work. But if the o.s. born bad, remain bad! Independently from your hard work!
About other o.s. and license: today exists a lot of possibility instead of microsoft products what are know to be bad and expensive ...
However, I hope which one day I can use my pda as use my N95.
Regards
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?
Hi all,
I hope I'm doing this in the right forum. I have an ambitious project I want to do.
I want to be able to read the entire contents of a smart phone.
Currently I plug, say a generic Windows Mobile phone into my PC, and using Active Sync, it shows the files on my device. I want to go beyond that and essentially see everything, the unused storage etc. Similar to how programs can see each sector on a computer hard drive, not just the files visible to the operating system.
There may be an easy way to do this, but I've done some searching and can't seem to find it.
I guess the first place for me to start is getting to know the architecture of the generic smartphone. I'm making an assumption that most smartphones which can run Windows Mobile, Android, Linux, etc have the same architecture (I won't be looking into Blackberry/RIM, Palm, or iPhone).
I understand that the processor for these smartphones are mostly by ARM, and use the ARM instruction set. From what I can make out also these phones store the OS/ROM in the memory (which I'm assuming is flash), and the applications and files are also stored in the same place.
Does anyone know where I can find info on how the architecture of these phones? Or know of a good place to start looking? Or have any advice for me?
Thanks ahead
Hello, guys.
Let me tell you a little bit about myself: I'm a software and hardware enthusiast. I have lots of experience slimming down operating systems, including iOS, BlackBerry OS, and Windows itself (I'm pretty proud of my knowledge to tell you the truth). However, I don't know squat about programming. I have very little experience with Python, but nothing else.
Not until recently was that I first had an Android smartphone under my property (3 days ago to be accurate), and I've been playing around with it this whole weekend. So far, I've managed to unlock the bootloader and root the phone (a Moto G, by the way) without installing any other ROM. Not bad for my first time, is it? Anyway, now that I know stuff as "simple" as that (took me a whole day to accomplish them), I want to take the next step: installing a ROM.
I downloaded the Android SDK, and I realized it contained a system.img file. I know that image is generic, and you're supposed to custom it according to your needs, but my questions are: if I install the untouched system.img file to my device, is my device going to work? What are the risks of doing that? Would I need to integrate my device's drivers in order for the image to work, or many more things than just integrating drivers? And, most importantly, is that file what you guys call a "pure Android (or AOSP)"?
Thank you very much.