Related
I have actually windows XP and Windows VISTA installed in my PC. I never had problems upgrading Roms using windows xp. However, today, the upgrade utility failled in windows VISTA. When the upg utlity goes for upgrading (after checking and sowed the rom instaled in the device), WIN VISTA close the app. So that, the wizard is left in BL mode and nothin more happens.
Does anyone get successfully upgrade the wizard using VISTA?
Thank you
No, its not working.
Confirmed, not working.
Flashing ROM's + Vista = NOPE!
Hi folks,
I can also confirm that flashing ROM's with Windows Vista does not work.
I tried different compatability settings but no chance.
I am working with the final version of Windows© Vista Ultimate RTM...had the same problems with the Vista betas.
dual boot or vm w/ xp
yes not supported yet by htc
i remember emailing htc about this issue and they said they currently have no plans to make the rom utillities compatible in running windows vista!
So, If they have no plans to make upg utilities Vista compatibles. I would say HTC needs a upgrade. for now any similar company are working hard to make their softs vista compatible.
Yeah, this really sucks for me since I have been running Vista exclusively since the RTM came out.
d'oh...that sucks...I just upgraded to Vista last week.
I think the reason that htc is not supporting vista rom upgrade compatablity is because crossbow will conduct upgrades from the platform/unit itself. I think i've read it somewhere.
hiimcliff said:
I think the reason that htc is not supporting vista rom upgrade compatablity is because crossbow will conduct upgrades from the platform/unit itself. I think i've read it somewhere.
Click to expand...
Click to collapse
Can see if you can find that article. I am curious on how that is going to work.
that's funny because they promised that for the original release of WM5 also.
Microsoft... they make me giggle with their blown deadlines and empty promises.
-Mc
its the photon version he is talking about bink article
Scratch VMWARE
Downloaded and installed VMWARE v6 build 36983 on my windows Vista machine. Running Vista Ultimate build 6.0.6000 (MS Technet Direct download).
Installed Windows XP SP2 into VMWARE and got all updates, patches, etc...
Installed ActiveSync 4.2 on the virtual XP 'puter...
Attached HTC Wizard (Cingular 8125) via USB and activesync picked up device. Wow! this is gonna work (so I thought)
Went to flash rom and it started out well enough... Phone went to load the rom screen, and then I get the "VMWARE workstation unrecoverable error" message... Rom didn't even start to load (thankfully) and I just pulled battery and turned phone back on... No prob...
Haven't had time to look at the dump yet to see what went wrong, but as of now, VMWARE doesn't appear to be an option either....
Anyone else tried VMWARE??
Come on ppl, someone out there smarter than me has had to try the VMWARE thing besides me and gotten it to work
Maybe once Vista is finally "released" to the masses, not just us "technet" or "MSDN" subscribers, support will magically appear...
As an aside, (for those thinking about getting Vista and Office 2K7) you can get Technet Direct Plus for about $290-$300 if you shop around... Sure, you have to download and make your own media, but you save about $100-$150 bucks for your trouble...
You get Vista and Office 2K7 Ultimate and can activate on up to 10 different machines... Also get XP, XP MCE, Office 2003, Exchange, etc....
In a german forum they are talking about flashing and that it is possible.
They did simunlock and flash WM& with vista.
http://www.ppc-welt.info/community/showthread.php?t=109541&highlight=vista
vista ruu works...
did you guys follow these steps? ultimate works fine for me;
http://forum.xda-developers.com/showthread.php?t=291723
here's a wiki;
http://wiki.xda-developers.com/index.php?pagename=Trinity_WindowsVista
dcoelho said:
So, If they have no plans to make upg utilities Vista compatibles. I would say HTC needs a upgrade. for now any similar company are working hard to make their softs vista compatible.
Click to expand...
Click to collapse
No plans for vista from my company either. Ever. Not until MS fixes their anti-competitive problems like driver signing, and stops imposing DRM crap on system functions. Just because a company releases some new platform does not mean it will have software support. If you want a functional platform look into Linux or XP. Both of witch have massive software support.
Most of the Apps I write run on OS X & Linux which have strong cross platform compatibility. XP is just a side OS, and buggy at that, with no cross platform compatibility. Vista more so. I would never recoup costs by developing for Vista so there is no point in it. It would be a tax write off and a waste of time and resources. Until Microsoft releases a platform that does what it is supposed to, and that is function as a platform, and not an advertising bus load of crap, then it will gain more support by independent software companies.
The purpose of a platform is to run software. If it cannot do that, then it is worthless. The function of a computer is to increase productivity, and make life easier. If Vista cannot do that, then ditch it, and get a platform that works. Stop expecting the world to evolve around a single company. If M$ was bombed with nukes tomorrow, the world would have to learn how to use a computer instead of playing with one. I would laugh, then run down the street naked shouting rejoice.
[/RANT]
OryHara said:
No plans for vista from my company either. Ever. Not until MS fixes their anti-competitive problems like driver signing, and stops imposing DRM crap on system functions. Just because a company releases some new platform does not mean it will have software support. If you want a functional platform look into Linux or XP. Both of witch have massive software support.
Most of the Apps I write run on OS X & Linux which have strong cross platform compatibility. XP is just a side OS, and buggy at that, with no cross platform compatibility. Vista more so. I would never recoup costs by developing for Vista so there is no point in it. It would be a tax write off and a waste of time and resources. Until Microsoft releases a platform that does what it is supposed to, and that is function as a platform, and not an advertising bus load of crap, then it will gain more support by independent software companies.
The purpose of a platform is to run software. If it cannot do that, then it is worthless. The function of a computer is to increase productivity, and make life easier. If Vista cannot do that, then ditch it, and get a platform that works. Stop expecting the world to evolve around a single company. If M$ was bombed with nukes tomorrow, the world would have to learn how to use a computer instead of playing with one. I would laugh, then run down the street naked shouting rejoice.
[/RANT]
Click to expand...
Click to collapse
Yes, cause I'm certain that syncing our phones and flashing the roms works much better in Linux or OS X than it does in Vista or XP.
I can say that I have been running Vista since before it was released, XP likewise. I have had very little trouble with either of them not running software. The ROM update program for our phones is one of the few pieces of software (outside of security and some utility type apps) that I've seen be a problem with Vista. Most of the problems that do arise are from the new security features preventing software from running in ways that it probably shouldn't have been programmed to in the first place (like trying to run as session 0 or mucking with the kernel).
Avatar28 said:
Yes, cause I'm certain that syncing our phones and flashing the roms works much better in Linux or OS X than it does in Vista or XP.
Click to expand...
Click to collapse
Under Linux, yes, it would be much easier, and the research would be easier as well. My staff flashes close to 20 routers a day with Linux boxen. Very easy to do.
Avatar28 said:
I can say that I have been running Vista since before it was released, XP likewise. I have had very little trouble with either of them not running software. The ROM update program for our phones is one of the few pieces of software (outside of security and some utility type apps) that I've seen be a problem with Vista. Most of the problems that do arise are from the new security features preventing software from running in ways that it probably shouldn't have been programmed to in the first place (like trying to run as session 0 or mucking with the kernel).
Click to expand...
Click to collapse
From your reply it seems like you are a end user, and not a developer, and probably have no idea what driver signing is, what it involves, and how DRM crippled Vista really is, especially if you are using < Ultimate edition.
When it comes to flashing phones, this is why the carriers are NOT going to support Vista for a while, if not ever. You could quite easily brick a phone because of some subvertive driver function that M$ has no public documentation on. Thats why my company doesn't support vista with our routers.
Hello Everyone,
I recently got my HTC Shift with Windows Vista Pre Loaded and it always seems to me a bit slow while running many stuffs together such as messenger with Internet explorer together. I don't tried loading any other windows yet. Can someone please confirm which is suferfast on HTC Shift? i.e; XP, Vista or Win7?
Thank you for your help....
In me experience XP is fastest, follwed by W7, and miles behind Vista. Currently I'm running Vista though...I tend to change every 6 weeks or so...I find once Vista has loaded ( a long time!) it isn't too bad for normal surfing or word processing. W7 started much quicker but I had some issues with it always trying to find the snapvue modem and not allowing me to access WiFi...a bizarre issue.
May go back to XP but I really like the resolution changer in Vista/W7.
FOOFTR said:
May go back to XP but I really like the resolution changer in Vista/W7.
Click to expand...
Click to collapse
Do you mean we are not able to change the display resolution in windows XP like in vista...?
mustking said:
Do you mean we are not able to change the display resolution in windows XP like in vista...?
Click to expand...
Click to collapse
To me, W7 is the best compromise. You have all the functions, including touch screen writing, and better speed.
mustking said:
Do you mean we are not able to change the display resolution in windows XP like in vista...?
Click to expand...
Click to collapse
Some of us had issues getting a resolution fix to work with our devices...so in Xp there is no standard way to change resolution. I agree with thaihugo that W7 is the best compromise and will buy a proper upgrade when it comes out (retail).
There is one thing you should know about windows 7 before loading it on your shift. It's terribly unstable for games, especially older ones.
I was able to get world of warcraft running on it, but every other classic game I've tried so far, crashes windows 7.
For everything that isn't gaming related, Windows 7 is great. But Windows Vista is the only operating system which will actually use the hardware of your shift in the right way.
Caid.
444
Win 7 new build
Are there still problems using Windows 7 newer builds on HTC Shift ?
On RC1 I had the following problems: Using or not using AERO, it crashes when accessing Windows Media Center [BSOD], also when runing AERO and button-switch resolutions.
Please if any post, say what build are you using and the problems you have.
I really really want to get along with Win7 on my HTC Shift but as much as I worked to fix those problems it still doesn't work properly.
PS: I will install Win7 in aprox 2weeks when the RTM release is on, and I want Ubuntu 9.04 too with dual boot.
I do NOT game with my HTC Shift, I use Windows for programming and stuff, and Ubuntu for browsing and some ssh. I really hope that Microsoft fix these problems and Windows 7 will run with no problems on HTC Shift
I absolutley LOVE W7 RC1 7100 on Shift, (and my PC's and my tablets, and my laptops for that matter). Any XP or Vista lovers, take note of W7 and start to migrate there
WinMedCetner works IF you dont maximize to full screen, but you can stretch the window to almost full screen. (I know, sucky, but hey, its an answer right?)
Also, I can get the bubbles screen saver to work on shift, but you are all right, AERO does crash it....Not the worst of things to have to give up in my opinion, becuase I still get the Hover Thumbnail Preview for running Applications.
As for games, I'm not your man...I strictly stick to business programs, but have not had any problems with anythign I use, and there is a long list I ahve installed.
My vote is Go for W7! The absolute BEST thing you can do to your Shift!
Bradaland said:
I absolutley LOVE W7 RC1 7100 on Shift, (and my PC's and my tablets, and my laptops for that matter). Any XP or Vista lovers, take note of W7 and start to migrate there
.........................QUOTE
Thnx mate i am installing win7 now to my shift i am installing RC and let me see the magic
I will later also try to install win XP. actually my main concern is the most available ram to run my softwares... I run Yahoo, MSN, Internet Security and bunch of other programs....
Click to expand...
Click to collapse
well...
Here's the thing about windows 7. It seems that almost all of the issues that people have, are somehow related to the way win7 handles the shift's video drivers. What this means is, there's a strong chance that anything which requires graphical resources may end up blue screening the shift. This doesn't happen with vista. I'm not sure about XP, but it's a glaring problem for windows 7.
I know windows 7 wasn't designed for the shift, however, it's a shame to have the added efficiency of windows 7 on the shift, with such a disabling exception. Frankly, all of these issues are most certainly related to how windows 7 tries to use the shift's video accelerator.
My logic is, if Vista can do it, Windows 7 should technically be able to as well, the only problem is, Microsoft isn't in charge of driver research for the shift, HTC is. And to HTC, this is of no urgency, for more than one reason.
The shift isn't meant to run Win7, is the first reason, secondly, all development into the Shift and it's drivers has been abandoned. Basically, I don't think enough people bought a shift, which caused HTC to take the "good enough" attitude towards it. They're not going to put anymore effort into improving a device that *while cool and all* is far inferior to most netbooks out today.
Sure, the Shift is a pretty cool device after you come to XDA and enable the phone options and such, but frankly, it's half as powerful as a comparitively priced netbook, and out of the box, not as versatile on account of it's poor processing power. It's been labelled as a tablet PC, and only to it's user base is it known as so much more than that.
The possibilities of the shift are very great, but the effort needed to reach those possibilities is more than what is available today.
Personally, I'd like to see the shift have a second chance, and it would be cool if HTC felt the same. But from what I've seen on behalf of HTC, this is a cold case file for them. I guess I'll have to see what I can get done on my own from China, tonnes of talented programmers here who should be able to churn out results. I'm even prepared to begin hiring a couple programmers who've been affected by the financial crisis, and see about solving some issues which could most certainly be worked out.
This driver issue, is one that by all means of reason, should be solvable, so long as there is no severe OS function which is fundamentally flawed between Vista and Win7, as far as the Shift is concerned.
I suppose the next question would be, if I did try to get a project like this going, what other ideas of improvements could be thought of to improve the shift experience? I know people would like to see BT, Wifi and SD cards on the winmo side, that unfortunately would be an ongoing effort whereas I'm more concerned with working on finishable projects during the resolution of greater issues like winmo's BTWiFiSD problem.
Any ideas, or support would be greatly appreciated.
My next step, and possibly the most difficult, will be convincing my wife that buying another shift (for the programmers to work on) is actually a worthwhile thing. She's not into tech, and doesn't much like my addiction
Caid.
444.
I like your enthusiasm with the Shift Caid. Truth be told its only Shift fans who know its goodness. Its like owning a Jeep. Nobody else can understand and when people ask questions they are simply told "IT'S A JEEP THING". So I guess ours too "IS A SHIFT THING". We still cherish our underpowered gadget even knowing its limitations. But honestly can I buy another Shift? I dont know. Even if my current shift was to somehow explode and burn into ashes I dont think I would replace it with another shift. Or maybe I would! But as long as I have it I will love it and continue to improve it.....
The biggest advantage with the Shift is when you plug a car charger into the cigarete lighter. There aren't many full fledged comps that you can charge with a 12V DC socket, you know.... I know there are DC-AC converters but thats a story for another day!
Now if only we can get a solution for BT-SD-Wifi winmo side........
Can I install Windows Vista Ultimate on the Shift. Love it.
Thanks
Hmm, I installes all of them, the most native. (Vista as an Upgrade to SP2 and Office 2007 SP2) And: It is the slowest what I known.
Windows 7 is nice, but with the newest RC we must rebuild the HowTo for installing Windows 7, some of the old original HTC Vista Homepage drivers not needed anymore.
best practice for all members here is, to make a Windows XP Slipstream to SP3, the modify the slipstreamed TabletPC Edition source with the programm nlite (and remove many not neccersary drivers and thems and so on, and build a bootable USB Stick Version with the small tool winsetupfromusb.
If work all together and have a look to the "last session" File of nlite, all people can have a really nice and "the fastest" and most compatible Windows XP Tablet edition multilanguage of all time.
Ans the builders of this perfect solution don´t need share their own TabletPC Edition product key, lets only have a look to the *.ini file of Nlite building, and many Ideas come together ;-)
Hey guys,
So I just got this laptop for a decent price (HP pavilion g7-2275dx). It has the AMD A8-4500M 1.9GHz processor (4gbRAM). I got Win8 pro on it, and got visual studio setup on it. Got the Hyper-V to kick...yada yada.
So my issue is, when I go to start the Windows 8 emulator, it just sits there...the Emulator window comes up saying "Starting Windows Phone Emulator..." like it should...but just sits there. It never loads...and eventually Visual Studio times out and says that the deploy failed.
Now, I'm able to launch on my Lumia 920 just fine (hooked to the computer and all).
Is RAM the problem? It's not tacking out the machine or anything (processor just plays around 0-3% utilized).
Also (don't know if this is related or not) but I installed the latest Android Studio (they announced yesterday at Google I/O!!!) but it won't even launch!
What am I missing? I"m ready to sell the thing and get an i5 or i7 intel. Would I just be better off overall getting an intel?
Thanks.
I'm assuming the A8 supports SLAT, or you couldn't use Hyper-V at all. Same goes for having virtualization enabled in the BIOS. Beyond that, I'm not really sure what the likely problem is... but I use an AMD 8350 CPU in my dev/gaming machine, and it's a beast (I also have 32GB of RAM, but that's honestly overkill).
With that said, I never saw much point in using the emulator. Deploying to the phone is faster, and you get a much more realistic experience of how the app works. What's the point of the emulator again, unless for some reason you're writing apps for a device you don't own?
Yup, enabled Hardware Virtualization in the bios and then upgraded to Win8 Pro for the Hyper-V.
I could live with not having the emulator because I do have the 920...would be nice to see it on other resolutions though just to be sure the app looks good.
I'm more concerned about the Android Studio though...
Found out the issue with the new Android Studio (though this really isn't the forum for this info). Anyhoo, turns out I needed the Java 7 jdk setup. So used to Java 6 that it didn't cross my mind to try 7.
Is there a possibility to wipe out the Android and install Windows on a MTK6589 device? Thanks
Read the FAQ.
NO!
Impossible. Windows Phone 8 doesn't have the drivers to run on other devices, unless you're willing to program them yourself. Furthermore, I believe it's hardware locked because of Secure Boot. All devices have secure boot (unlike Windows 8, where only some computers have secure boot) and it is (I believe) a requirement, hence the inability to boot Windows Phone 8 on an Android device. Unless you're willing to emulate secure boot somewhat as well, then go for your life.
Want Windows Phone 8 on an Android device? Buy a Nokia Lumia and sticky tape it on top of your current Android device. Voila! Results are instant.
Honestly, if you want a certain OS on your phone, buy the phone that has the OS. It's like buying a tomato and then saying "fudge, wish this tasted like a cucumber".
The idea comes straight from the world of PCs : there you can if you want to wipe the system clean and install almost anything you like. From MS-DOS to Windows 2, Windows NT, OS/2, dozens brands and copies of Linux, Unix mutations the list is almost endless.
The onboard ROM on a "PC" will happily run whatever's on the disk or CD or DVD or other boot device. This is a 1970'as design which has not changed.
If you are missing device drivers for a certain device on PC then it (a) defaults to basic functionality (b) this device does not work at all but it is not always a stopping block.
I did not know what the obstacles are on smartphones. I was hoping to find and understand more details.
The MTK65XX chip set is an Arm CPU for which Windows have a new system. Some Chinese tablets now sell with Android or Windows.
Thanks for the explanations.
Yeah, you might have saved yourself some time if you'd done even a little research. Not only do ARM devices require a Board Support Package (firmware image, basically) that generally won't be available for an arbitrary device/OS combination (it's not just a matter of having basic drivers like on x86), but there isn't actually any installer (at least, not publicly available) for Windows Phone. There's only full device images available, which are specific to their intended devices. Custom ROMs, even for variants of the same OS that the device shipped with, are hacked together and often don't have full hardware support, especially when switching between OSes. You would need to build one nearly from scratch for a device like yours, given that the manufacturer of it doesn't (so far as I know) sell *any* Windows Phone devices so you couldn't even crib drivers from another phone. Additionally, nearly all ARM devices ship with locked bootloaders that will not boot a different operating system, or even allow the OS to be tampered with (although these days, consumer Android device bootloaders can usually be unlocked).
Zilliman said:
The idea comes straight from the world of PCs : there you can if you want to wipe the system clean and install almost anything you like. From MS-DOS to Windows 2, Windows NT, OS/2, dozens brands and copies of Linux, Unix mutations the list is almost endless.
The onboard ROM on a "PC" will happily run whatever's on the disk or CD or DVD or other boot device. This is a 1970'as design which has not changed.
If you are missing device drivers for a certain device on PC then it (a) defaults to basic functionality (b) this device does not work at all but it is not always a stopping block.
I did not know what the obstacles are on smartphones. I was hoping to find and understand more details.
The MTK65XX chip set is an Arm CPU for which Windows have a new system. Some Chinese tablets now sell with Android or Windows.
Thanks for the explanations.
Click to expand...
Click to collapse
Well then think of it this way, Install XP on a computer. Take the hard drive out and try to boot on another one. It won't work unless you have all the drivers or extremely similar hardware.
I don't have a complete understanding of ARM, but I assume these Qualcomm SoCs have the TPM built in. Its almost the bottleneck with using WP8, but we'll have to wait for HTC to release a potential dual boot Android Windows Phone. Things will align sometime.
Sent from my Lumia 928 (RM-860) using Tapatalk
thals1992 said:
Well then think of it this way, Install XP on a computer. Take the hard drive out and try to boot on another one. It won't work unless you have all the drivers or extremely similar hardware.
I don't have a complete understanding of ARM, but I assume these Qualcomm SoCs have the TPM built in. Its almost the bottleneck with using WP8, but we'll have to wait for HTC to release a potential dual boot Android Windows Phone. Things will align sometime.
Sent from my Lumia 928 (RM-860) using Tapatalk
Click to expand...
Click to collapse
OK Here is how PC/Windows works:
When Windows boots it uses a thing called "HAL" (hardware abstraction layer) - and whilst booting it tries its best to cope with a number of chipsets, disc drive controllers, and other core hardware components. This is done on the fly because there are only so many chipsets out there and the drivers aren't that large. If you boot Windows in debug mode you will see it loading one million drivers for hardware which you definitely not have - and when you actually install it it does the same - it does not ask you " what CPU / north bridge / south bridge / other DMA/ chipset / and everything else you have?". It just tries it all and loads what fits. The only things left out are whatever you can load later, eg specific sound card drivers, wifi, video card etc.
So this is a marriage between the PC's BIOS ROMs and the OS - so that with one single CD you can install pretty much anywhere. And this idea and technology has been around since the 70s.
For Linux/Unix/OS/2 and anything else on the PC the idea is pretty much the same: the BIOS has " started " the machine for you, and you simply run your "application" which in most cases is a complete OS!
For example I once wrote a memory tester that booted straight off the drive, without any other OS being present, it is that simple once you have the BIOS in place.
In my complete ignorance of how smartphones are made, I assumed that the hardware manufacturer of each phone provides a BIOS which can provide basic services like on the PC. Is that what we call the "bootloader" ? Looking at the "scatter files" it appears there is a whole lot of binary images before the "android" image.
Are these images the "hardware layer / BIOS" then? And can we consider the "android" image to be the actual OS?
Zilliman said:
OK Here is how PC/Windows works:
When Windows boots it uses a thing called "HAL" (hardware abstraction layer) - and whilst booting it tries its best to cope with a number of chipsets, disc drive controllers, and other core hardware components. This is done on the fly because there are only so many chipsets out there and the drivers aren't that large. If you boot Windows in debug mode you will see it loading one million drivers for hardware which you definitely not have - and when you actually install it it does the same - it does not ask you " what CPU / north bridge / south bridge / other DMA/ chipset / and everything else you have?". It just tries it all and loads what fits. The only things left out are whatever you can load later, eg specific sound card drivers, wifi, video card etc.
So this is a marriage between the PC's BIOS ROMs and the OS - so that with one single CD you can install pretty much anywhere. And this idea and technology has been around since the 70s.
For Linux/Unix/OS/2 and anything else on the PC the idea is pretty much the same: the BIOS has " started " the machine for you, and you simply run your "application" which in most cases is a complete OS!
For example I once wrote a memory tester that booted straight off the drive, without any other OS being present, it is that simple once you have the BIOS in place.
In my complete ignorance of how smartphones are made, I assumed that the hardware manufacturer of each phone provides a BIOS which can provide basic services like on the PC. Is that what we call the "bootloader" ? Looking at the "scatter files" it appears there is a whole lot of binary images before the "android" image.
Are these images the "hardware layer / BIOS" then? And can we consider the "android" image to be the actual OS?
Click to expand...
Click to collapse
You don't understand the basic problem.
Windows (desktop) is an entirely different OS which has very powerful hardware at its disposal and it is supposed to run on various hardware configurations. It was designed to be this way from the ground up.
Windows Phone is just not like that. It is designed to work with one configuration, and one configuration alone. You can;t even flash the WP8 image from one device model to another without risking brick.
If you try to flash the lumia 1520 ROM on a lumia 820, chances are the lumia 820 will brick.
In other words, WP8 does not load "millions" of drivers in hope of matching the single one the system matches. There are various technical and marketing reasons why this does not happen.
And it is like this for android as well. Getting past the bootloader is easy (for android devices). Getting to actually boot something is an entirely different story.
Just a FYI, I did have a old mtk device once that has dual boot Android 2.x and Windows 6.1... I know that is old. But that was cool.
I can pop a Windows installation disk into just about any computer and install it with no problems whatsoever. Why do Android ROMs need to be so tailored to each device?
enginuity2 said:
I can pop a Windows installation disk into just about any computer and install it with no problems whatsoever. Why do Android ROMs need to be so tailored to each device?
Click to expand...
Click to collapse
Each device is unique and may involves various components that are not necessarily present in other devices. Also things like the kernel cannot be uniformly coded for every device or else you'd start having some serious problems. Also technology changes from phone to phone. Some manufacturers also layer Android with "skins" to make their product more unique and add different features. If all devices were the same then there would be little incentive to buy from one manufacturer vs another.
enginuity2 said:
I can pop a Windows installation disk into just about any computer and install it with no problems whatsoever. Why do Android ROMs need to be so tailored to each device?
Click to expand...
Click to collapse
Just popped a Windows 10 disc on my Mac, and suprisingly its a no go. What happened?
enginuity2 said:
I can pop a Windows installation disk into just about any computer and install it with no problems whatsoever. Why do Android ROMs need to be so tailored to each device?
Click to expand...
Click to collapse
I have an old PCAT 80386, and my Windows 10 just won't install.
I'm sorry, but this is a bad comparison. Windows comes with the most common drivers, but if you have a rare hardware device then it won't work when you install it. It will appear as a red x in Devices, until you download your driver from the manufacturer's homepage. I mean if it's still compatible. If it only has Windows XP drivers, then you're boned. If it has Vista, well you r chances have increased.
Unless you have a Broadcomm ethernet adapter that windows does not support. Download those drivers if you can.
Now imagine if the device which is not working your touchscreen. Or, the screen itself.
Linux would be a better example, since all divers are in the kernel itself, or at least a simplified legacy version, that's not hardware accelerated until you install proprietary closed binary drivers. Like the nVidia cards on Linux. I wouldn't want to have my phone in 640x480 in 256 colors until I can obtain the latest driver.
mikeprius said:
.... If all devices were the same then there would be little incentive to buy from one manufacturer vs another.
Click to expand...
Click to collapse
It's true for manufacturers, but pesky for consumers. I have had HTC sense....no more HTC !
I think the point that @enginuity2 is trying to make is that one can buy a PC from almost any manufacturer, with a varied range of components from various manufacturers (or buy components and build one), and Windows will almost certainly run on it. I think this boils down to the fact that Windows has drivers for almost all devices/components, or they can use generic drivers, that are built into the OS itself.
From what I hear, communication components (like modem) have proprietary drivers that cannot follow this model for some reason. In theory, should it be possible for the OS to have access to a repository of drivers for most (if not all) components? Yes - if Microsoft can do that with their desktop OS for years, it "should" be doable here as well. I don't know why it can't be done. I'm sure there is a reason why.
enginuity2 said:
I can pop a Windows installation disk into just about any computer and install it with no problems whatsoever. Why do Android ROMs need to be so tailored to each device?
Click to expand...
Click to collapse
Its because of the way the ARM CPU and bootup processes work -- all different. x86 platform standardized this, which is why you can drop a "generic" OS onto them without much in the way of customization.
doitright said:
Its because of the way the ARM CPU and bootup processes work -- all different. x86 platform standardized this, which is why you can drop a "generic" OS onto them without much in the way of customization.
Click to expand...
Click to collapse
That's why I was dumbfounded when Asus succeeded in making their Atom based Zenfones equally convoluted to unlock, flash, boot, etc.
(Though you can run Windows under KVM )
istperson said:
That's why I was dumbfounded when Asus succeeded in making their Atom based Zenfones equally convoluted to unlock, flash, boot, etc.
(Though you can run Windows under KVM )
Click to expand...
Click to collapse
Just because the infrastructure to do it correctly exists, does not mean that everybody has to do it correctly.