i'm new into this, so i was wondering if anyone knows if there is any way i can port android on a samsung preston. it's native ui is awful and there's little to no customization.
if no-one is planning on doing an android port for this phone, can anyone point me in the direction of a good guide to doing it myself?
My daughter has this phone it it could really do with a decent OS
Yeah...I would really like to have android on my samsung GT-S5600...I HATE the samsung OS...I like the phone's design,but I'm thinking of buying a new one,just because of the crappy OS...If someone could make android for it,I would be grateful...
dexter9374 said:
Yeah...I would really like to have android on my samsung GT-S5600...I HATE the samsung OS...I like the phone's design,but I'm thinking of buying a new one,just because of the crappy OS...If someone could make android for it,I would be grateful...
Click to expand...
Click to collapse
I have the same "problem" if anyone find the solution will be very apriciated.
Thanks
Bissius
Well, I think our only way out would be getting a dev interested... Or we could always buy another phone
I don't see this as being very likely. There are a number of problems that will need to be overcome. First and foremost is the processor type. We have no idea what the speed is. Let alone the architecture. Android requires an ARM based architecture to run with a minimum of 200MHz or so which pretty much guarantees global system lag. You'll probably have smoother performance on the proprietary OS. Not that I've used the device or anything but that's what would be expected. After all, the prop. OS's have been slimmed down to the extent that only the incorporated functions run and nothing else. Next is ram. We again are told nothing on how much memory this thing has. Barebones 'droid requires 128mb minimum to run. Storage… Here's a list of 'droid's requirements.
http://www.netmite.com/android/mydroid/development/pdk/docs/system_requirements.html
Recommended is 256MB of minimum internal storage. It says it will run on less but its not recommended. Let's push the boundaries a little. Lets say that the preston has 96mb of internal memory, which realistically should be about right. Maybe 128mb TOPS. Thats 37.5-50% of the original requirement. Even if you did get it running, where are your personal files going to be stored if you can't get the sd card slot working? In addition to that, more lag will be faced as it is a proven fact that all machines slow down if more than half the internal storage has been used.
Assuming that we got passed all of this (it'll be a miracle if we did), there are other matters that are sure to lay down a roadblock. First of all, drivers. The internal hardware of the device will need drivers written for it. That means everything like radio, bluetooth, camera, keypad, touchscreen, audio, display etc. etc. All current devices that run Android can run it because the hardware in the device already exists in an equivalent Android device. If none of the hardware in the 5600 exists in any other droid phone, drivers will need to be reverse engineered. The kernel is essential for the system to boot. It is the underlying structure on which the OS is built. If the CPU in the device is not ARM based, there is a fat chance that a working kernel will ever be built for it. And the final and probably most important reason why this will probably never work is the boot loader. Even Windows Mobile devices which currently run Android won't work without a third party loader. Hence the reason it must boot into WinMo first to load droid. The reason being is that all phone manufacturers lock the phone's boot loader to prevent it from running anything but the shipped OS. Lets say we got past this by creating a loader similar to haret that ran inside the prop. OS. You would be able to TECHNICALLY bypass the problems we would have with the stock boot loader and internal storage (that is, considering that we have established a way to enter the linux kernel). But you would still be faced with CPU compatibility issues, driver support and sufficient ram to barely run an OS as packed as Android. I will gladly give a medal and bow down to the gentleman/woman who manages the task but as I previously said, it does not seem possible.
ayilm1 said:
I don't see this as being very likely. There are a number of problems that will need to be overcome. First and foremost is the processor type. We have no idea what the speed is. Let alone the architecture. Android requires an ARM based architecture to run with a minimum of 200MHz or so which pretty much guarantees global system lag. You'll probably have smoother performance on the proprietary OS. Not that I've used the device or anything but that's what would be expected. After all, the prop. OS's have been slimmed down to the extent that only the incorporated functions run and nothing else. Next is ram. We again are told nothing on how much memory this thing has. Barebones 'droid requires 128mb minimum to run. Storage… Here's a list of 'droid's requirements.
http://www.netmite.com/android/mydroid/development/pdk/docs/system_requirements.html
Recommended is 256MB of minimum internal storage. It says it will run on less but its not recommended. Let's push the boundaries a little. Lets say that the preston has 96mb of internal memory, which realistically should be about right. Maybe 128mb TOPS. Thats 37.5-50% of the original requirement. Even if you did get it running, where are your personal files going to be stored if you can't get the sd card slot working? In addition to that, more lag will be faced as it is a proven fact that all machines slow down if more than half the internal storage has been used.
Assuming that we got passed all of this (it'll be a miracle if we did), there are other matters that are sure to lay down a roadblock. First of all, drivers. The internal hardware of the device will need drivers written for it. That means everything like radio, bluetooth, camera, keypad, touchscreen, audio, display etc. etc. All current devices that run Android can run it because the hardware in the device already exists in an equivalent Android device. If none of the hardware in the 5600 exists in any other droid phone, drivers will need to be reverse engineered. The kernel is essential for the system to boot. It is the underlying structure on which the OS is built. If the CPU in the device is not ARM based, there is a fat chance that a working kernel will ever be built for it. And the final and probably most important reason why this will probably never work is the boot loader. Even Windows Mobile devices which currently run Android won't work without a third party loader. Hence the reason it must boot into WinMo first to load droid. The reason being is that all phone manufacturers lock the phone's boot loader to prevent it from running anything but the shipped OS. Lets say we got past this by creating a loader similar to haret that ran inside the prop. OS. You would be able to TECHNICALLY bypass the problems we would have with the stock boot loader and internal storage (that is, considering that we have established a way to enter the linux kernel). But you would still be faced with CPU compatibility issues, driver support and sufficient ram to barely run an OS as packed as Android. I will gladly give a medal and bow down to the gentleman/woman who manages the task but as I previously said, it does not seem possible.
Click to expand...
Click to collapse
thanks for the info, looks quite feasible what you're telling; it makes me a little sad though
Related
Just wondering if it's possible?
Why would you want to do that?
cause it's a better, more robust OS
Not gonna happen.
The PPC version of the OS relies heavily on touch screen so even if someone somehow managed to cook a ROM (which is nearly impossible unless you work for Motorola or Samsung) you'd still wouldn't be able to do much with it.
pretty sure that no smartphones use arm compatible cpu's
and as roms are binarys for one surden cpu series
it would require as much recompiling from buttom as getting windows xp running on it
I'm sure there's some thread somewhere about this, but I haven't found one after searching quite a while.
What ROMs are people using for Windows Mobile before loading XDAndroid? Searching Android Rom doesn't seem to work very well and I've tried several other options.
I'm looking for a lighter rom, but I'd like to have 6.5.3 so when I can't use XDAndroid (like when I need speakerphone or camera) then I'll still have a system I like.
If there's already a thread somewhere for this sorry, please point me at it.
There's been some debate about whether or not the ROM effects Android at all. I'm of the belief that the particular ROM you're running has NO bearing on Android whatsoever. There are others who say differently... But I've run the "lightest" ROM possible - basically boots WinMo enough to immeidately kick off Haret...and I found no difference in performance.
This was on my original TP, but the concept should be the same.
So, I just run EnergyROM. But, try it out - let us know what you think. Install a light ROM and see if there's a difference... I don't think there is, and the placebo effect plays very greatly into this without some hard numbers on performance differences. Since WinMo is booted out of memory, I honestly don't think the ROM effects Android at all.
I was thinking more along the lines of space still left in storage, but depending on how the roms are done and how much you install I guess the rom isn't a huge difference.
zharptitza said:
I was thinking more along the lines of space still left in storage, but depending on how the roms are done and how much you install I guess the rom isn't a huge difference.
Click to expand...
Click to collapse
Hrm... Either I'm misundertsanding you, or you're misunderstood
Android runs entirely off of the SD card presently. So whatever space is leftover from flashing the ROM, it won't really matter... because currently Android doesn't touch the space that a WinMo ROM takes up. Make sense?
Using Energy Rom here and the reefer BLAZIN build runs great parallel to it. Although I also believe The winMo rom you are running makes no difference.
arrrghhh said:
Hrm... Either I'm misundertsanding you, or you're misunderstood
Android runs entirely off of the SD card presently. So whatever space is leftover from flashing the ROM, it won't really matter... because currently Android doesn't touch the space that a WinMo ROM takes up. Make sense?
Click to expand...
Click to collapse
This is not entirely true that it has no effect. On the HD2 it really matters what kind of winmo rom you use. Don't ask me why, but with some winmo roms you hear a robot voice when calling.
So it could be possible that it also has some effect on our tp2, but I don't think that is the case for us because I never heard anyone about it.
Lennyz1988 said:
This is not entirely true that it has no effect. On the HD2 it really matters what kind of winmo rom you use. Don't ask me why, but with some winmo roms you hear a robot voice when calling.
So it could be possible that it also has some effect on our tp2, but I don't think that is the case for us because I never heard anyone about it.
Click to expand...
Click to collapse
Are you talking about the NAND bootloader for the HD2 or the SD card haret method...?
Besides, I've never experienced anything like this, and I tried A TON of ROMs on my TP1 to figure out if there was any difference. My conclusion was there was no difference. Granted WinMo initializes some things for Android, so it is still necessary, and some settings within WinMo will affect Android... but I don't think the ROM itself whether it's light or heavy will affect the performance of Android. I assume that's what we're talking about...
Slight OT but i just need to ask.....if i do finally get Android to run on my TP2 and it boots up fine. Assuming i install 10 applications from market. After i do a reboot, would the apps and it's setting stay? Or will i get a fresh android OS again?
Scann69 said:
Slight OT but i just need to ask.....if i do finally get Android to run on my TP2 and it boots up fine. Assuming i install 10 applications from market. After i do a reboot, would the apps and it's setting stay? Or will i get a fresh android OS again?
Click to expand...
Click to collapse
You'll only get a "fresh" Android OS if you delete your data.img file. So yes, the apps will stay
I've ran Stock Verizon ROM and Mighty ROM. No difference when Android is booted since HARET unloads the memory space WinMo is using.
coolsilver said:
I've ran Stock Verizon ROM and Mighty ROM. No difference when Android is booted since HARET unloads the memory space WinMo is using.
Click to expand...
Click to collapse
try energy titanium. really you wont notice much difference tho. but homeboys right, placebo effect could help ya out
In the current lineup of Windows Phone 7s, some phones have 512MB ROM while others have 1GB ROM. In Blackberries, Androids and Pres, this would mean the 1GB phones have double the storage space for apps because apps can only be installed on ROM memory (though Android now allows Apps2SD).
But in Windows Phone 7, I thought the OS created a single volume of the ROM + other memory (Flash or SD), meaning the apps can be installed anywhere. If the ROM only stores the OS and at max 60MB of pre-installed apps, what's the advantage of having 1GB ROM?
Haven't heard of any max. So no worries.
My guess is that if any updates require a good bit more space, only those phones will get it, like how the G1 was left out for not having enough ROM.
ckacey said:
My guess is that if any updates require a good bit more space, only those phones will get it, like how the G1 was left out for not having enough ROM.
Click to expand...
Click to collapse
Though with that said I don't think Microsoft will be looking to make that mistake anytime soon.
The G1's issue was compounded by the fact that Android < 2.2 does not support installing applications to SD card. Windows Mobile devices didn't have all that much trouble getting upgrades from 5.0 to 6/6 to 6.1/6.1 to 6.5 with small ROMs because users could just install their applications to the SD Card (and Sync their media there as well).
Android didn't, so even if the OS could barely fit into the ROM, it would make the phone borderline unusable since unless it was an upgrade to 2.2 the applications and data/cache files woulnd't have anywhere to fit.
The HD2 came with a 1GB ROM/576 MB RAM for the US Market.
I personally hope that when Samsung releases the Vibrant FroYo, that it allows installing apps to the INTERNAL SD card, because I do not like installing apps to removeable media - personally.
I'm kinda sad to see the HD7 has half the ROM of the HD2, but sense and the tmobile crapware were probably taking loads of space there
Unless 512MB is all Microsoft needs for future updates + OS..
SO unless their plan is to release attractive phones to get people into buying them and getting used to the OS while only releasing Updates with Needed Features and Several Bug fixes so in the end the ROM is filled with Updates then they use the excuse that it won't support the next Step up since theres not enough space...
Just like Android in Some Cases...
It sounded better in my head
hakuchi18v said:
Unless 512MB is all Microsoft needs for future updates + OS..
SO unless their plan is to release attractive phones to get people into buying them and getting used to the OS while only releasing Updates with Needed Features and Several Bug fixes so in the end the ROM is filled with Updates then they use the excuse that it won't support the next Step up since theres not enough space...
Just like Android in Some Cases...
It sounded better in my head
Click to expand...
Click to collapse
hmm That way you'd have to get a new phone for WP8. I've read that it is in the plan phase already
I don't think the phone OS will get any ware near that and so I don't think 1gb would be needed.
By the time WP8 is ready we'll all be ready for new phones anyway, unless it is ready before 2 years is up. But if they do it like Vista and W7 and leave a bit of breathing room, we'll be fine. If they pull an iPhone and WP8 is out next year, it'd best work on WP7 launch devices too, and be pushed through Zune. A $5 fee wouldn't be offensive if this time next year WP8 is ready.
I think that there seem to be some confusion about the term "ROM".
ROM stands for Read Only Memory, if it's a read only memory you have to erase the whole memory if you want to add something to it (i.e. flashing the device). If it's real ROM, you can't use it for apps, no matter what platform you're using.
Now I've heard somewhere that WP7 can mirror data on a smaller, but faster internal storage for fast access. If that is the case, and the 1GB isn't really a ROM, it could be used to mirror things of the Storage for fast access.
Sir. Haxalot said:
I think that there seem to be some confusion about the term "ROM".
ROM stands for Read Only Memory, if it's a read only memory you have to erase the whole memory if you want to add something to it (i.e. flashing the device). If it's real ROM, you can't use it for apps, no matter what platform you're using.
Now I've heard somewhere that WP7 can mirror data on a smaller, but faster internal storage for fast access. If that is the case, and the 1GB isn't really a ROM, it could be used to mirror things of the Storage for fast access.
Click to expand...
Click to collapse
ROM is a misnomer but it's what OEMs refer to when talking about application memory. You do not need to erase the whole memory to add something new. The ROM space is meant to be changed infrequently.
I see two reasons why some WP7s have 1GB ROMs: (1) WP7 does install apps to the ROM for speed reasons; this means WP7 will be very limited in app size and some app developers will not create large, quality apps for WP7. (2) The phones with 1GB will also be Android phones, which by default install to ROM.
I still have not found an answer as to what's the advantage of having 1 GB of ROM on WP7.
I'm still guessing that like Android's Apps2SD, WP7 is writing only the apps' necessary files to the ROM and storing the rest of the app on the internal/SD memory.
I'm fairly sure that I'm right in saying that WP7 doesn't see a difference between the internal ROM and the Expanded storage (be it Nand or SD Card) as it stripes the two in a Raid type array. So it sees it all as one contiguous drive. I would imagine that the original OS image will be stored on part of the ROM, and when it's initially set up, or hard reset etc... then it will deploy the image onto the striped array?
So I don't think the size of the ROM will make any difference in terms of updates, applications etc... I'd be shocked if MS had set it up so that they wouldn't be able to deploy updates etc... due to storage constraints - that said, stranger things have happened!
"...writing only the apps' necessary files to the ROM..."
Am I the only one spotting the mistake here?
ROM stands for Read Only Memory. You cannot write to ROM.
There are types of ROM that can be rewritten via special processes, such as EEPROM (Electrically Erasable Programmable ROM).
But apps cannot write to ROM.
Jim Coleman said:
"...writing only the apps' necessary files to the ROM..."
Am I the only one spotting the mistake here?
ROM stands for Read Only Memory. You cannot write to ROM.
There are types of ROM that can be rewritten via special processes, such as EEPROM (Electrically Erasable Programmable ROM).
But apps cannot write to ROM.
Click to expand...
Click to collapse
You are wrong; please refer to my post near the top of this page.
Take the HTC Droid Incredible for instance: it has 512MB ROM, 8GB internal Flash and up to 32GB SD. The OS and all applications are installed to the ROM. The OS takes up a lot of that space and you're left with very little room for apps. You can install and delete apps from the ROM as many times as you want.
Here's an interesting fact that makes the question even more intriguing: The HTC HD7 (512MB ROM) with 16GB memory and the Samsung Focus (1GB ROM) with 16GB memory (8GB embedded + 8GB SD) have the same amount of total storage--14.5 to 14.6GB. The few MB difference is likely from different pre installed apps (limit of 60MB pre installed).
This likely means that WP7 does not count ROM as part of the phone's storage. So why would Samsung put more ROM than needed on the Focus?
Pete2s said:
This likely means that WP7 does not count ROM as part of the phone's storage. So why would Samsung put more ROM than needed on the Focus?
Click to expand...
Click to collapse
And that is the question that baffles here...
Still haven't figured it out.
Jim Coleman said:
"...writing only the apps' necessary files to the ROM..."
Am I the only one spotting the mistake here?
ROM stands for Read Only Memory. You cannot write to ROM.
There are types of ROM that can be rewritten via special processes, such as EEPROM (Electrically Erasable Programmable ROM).
But apps cannot write to ROM.
Click to expand...
Click to collapse
That's not necessarily a typo. ROM chips are updated with software all the time and lots of people just say ROM because it's shorter, more convenient, adn it's what they're used to.
Lots of people said RAM even when there were SDRAM, RAMBUS, EEC-RAM, DRAM, etc. floating out there. It's just habit, and it doesn't necessarily destroy the accuracy or technical merits of the text.
With the release date of the Ubuntu phone Images announced, are any developers preparing to port it the the arc? I hope the spec can handle it as I would love Ubuntu to see my beloved Arc out!
http://www.ubuntu.com/devices/phone/operators-and-oems
minimal specs are :512 mb -1 gb ram+
4-8GB eMMC + SD - we dont have enoth storge we have only 1 gb....
1ghz procesor +
Will ubuntu pwned android?
Hmmm short term answer will be NO
But long term, we wont know
what is eMMC?
thelast3lack said:
what is eMMC?
Click to expand...
Click to collapse
It's internal storage
What if we use a mod like data2sd adatped for Ubuntu OS? Like the users of Asus Transformer, that used fast class 10 sd cards to dump all the system related files there? Will that be a possible solution?
Sent from my Xperia Arc S using xda app-developers app
Porting Ubuntu Phone to Xperia Arc (S)
Jet70355 said:
What if we use a mod like data2sd adatped for Ubuntu OS? Like the users of Asus Transformer, that used fast class 10 sd cards to dump all the system related files there? Will that be a possible solution?
Click to expand...
Click to collapse
It depends. You don't need to port stuff like data2sd, the best solution would be to mount some directories at the sdcard which aren't immediatly needed at boot. I want it as well, but I'm still rather unexperienced with porting os'es to ARM devices. I do know something about linux.
For example: In my (basically unused) Ubuntu installation (I run Arch Linux as main OS) 75% of the total 2.5 GiB is used by the dir '/usr'. If we could mount that on the sdcard, 1 GB is plenty for the rest. Putting '/usr' on another partition/disk is not that uncommon in linux, so it should work. Also, if you download applications, most of it goes in /usr. (other directories we have to put on the sdcard are /opt (some kind of /usr) and /home ofcourse)
Space is no problem. One of the problems is that the Xperia Arc runs on an ARMv7 processor, and the Galaxy Nexus (which will receive Ubuntu Phone on 22 feb) is ARMv9.
evertheylen said:
It depends. You don't need to port stuff like data2sd, the best solution would be to mount some directories at the sdcard which aren't immediatly needed at boot. I want it as well, but I'm still rather unexperienced with porting os'es to ARM devices. I do know something about linux.
For example: In my (basically unused) Ubuntu installation (I run Arch Linux as main OS) 75% of the total 2.5 GiB is used by the dir '/usr'. If we could mount that on the sdcard, 1 GB is plenty for the rest. Putting '/usr' on another partition/disk is not that uncommon in linux, so it should work. Also, if you download applications, most of it goes in /usr. (other directories we have to put on the sdcard are /opt (some kind of /usr) and /home ofcourse)
Space is no problem. One of the problems is that the Xperia Arc runs on an ARMv7 processor, and the Galaxy Nexus (which will receive Ubuntu Phone on 22 feb) is ARMv9.
Click to expand...
Click to collapse
I heard that the processor isn't a big problem, as it should run on wide range of devices. Something about kernels or something...
Processor
replicant101 said:
I heard that the processor isn't a big problem, as it should run on wide range of devices. Something about kernels or something...
Click to expand...
Click to collapse
'Big' is relative of course. We will need to compile everything for ARMv7, because I assume Canonical won't have repositories for every architecture possible from the start. If Canonical releases ARMv7 stuff from the start, the main problem would be to get the different components to work, just like an Android ROM. Ubuntu Phone will use Android drivers they said, so hopefully it'll work.
If there's anyone that wants this on their Xperia Arc S and wants to help as well, please contact me or post something in this forum.
I will try my best to get this up and running on the Arc, but I can't promise anything. I'm not an experienced developer.
evertheylen said:
'Big' is relative of course. We will need to compile everything for ARMv7, because I assume Canonical won't have repositories for every architecture possible from the start. If Canonical releases ARMv7 stuff from the start, the main problem would be to get the different components to work, just like an Android ROM. Ubuntu Phone will use Android drivers they said, so hopefully it'll work.
If there's anyone that wants this on their Xperia Arc S and wants to help as well, please contact me or post something in this forum.
I will try my best to get this up and running on the Arc, but I can't promise anything. I'm not an experienced developer.
Click to expand...
Click to collapse
i am ready to help, although i dont have any experience with these kinds of developement.
i have an lt18i.
I think we are waiting on ubuntu to publish the wiki page about how to port it to other devices, once its up then we can have a crack at it
It is published. unfortunately i cant sync those HUGE sources because of low diskspace left (for compiling which has been taken up by other projects). hopefully as i clean up, you may expect a build soon. I said may, not will.
disc space isn't an issue over this end, how big is it?
Edit: 15GB, thats a big download.. D:
Around 15 gigs I think. With more needed for binary compiling. It says so in the guide
Im on a 40gb download limit a month, and I've already used most of it up :/
i would love to have a port of this
but unfortunatly, i am not able to help, as i do not know how to succesfully port
Sent from my sending thing..
Stupid computer y u no fast
I'm ready to help, I'm not s dev but would be willing to test though.
Roland
Sent from my Nexus 7 using Tapatalk HD
Volunteers needed
Hello everyone, I want, just like you, Ubuntu Touch on my Xperia Arc (S). I'm willing to spend a lot of time on it, although I'm not an experienced developer, I think I might be able to do it. For the moment, I have no immediate plans to port it, I'm first trying to understand it better. I've already encountered a lot of possible problems, but thank Canonical that they have made Ubuntu Touch so easy to port. (based on CM 10.1, using the same display driver, ...)
I would like to have a list of people that want to help or test. I'm not a real fan of doing everything in a forum, so perhaps we could make a google project or so. What do you think?
As someone's who's just switched from a dual boot of linux mint / Windows 7. To Just Ubuntu, I would be interested if it were to come to our architecture, but I thought ubuntu needed dual core processors? And obviously HDMI won't be available.
Google Apps isn't native to ubuntu right? So what kind of ecosystem would we be moving to? Also there is no lockscreen which is a little concerning, but the device itself works like BlackBerrys new OS, which is nice.
Sent from my LT18i using xda app-developers app
I would test it, as I'm no developer I can't do anything else
Hi!
I have great respect for the people that give us our great ROMs, and i KNOW that that is hard - but my question is: why exactly is it that hard?
This is just a question out of curiosity, because I would really like to understand the unerlying problems that cause all the other issues.
I was under the impression that the Android stack runs on top of the Linux kernel.
Usually, the Linux kernel is the Hardware Abstraction Layer, and apps and ROM, in theory, should be kind of hardware agnostic?
e.g. the Bluetooth Issue on our Captivate Glides: I would guess that Android communicates, through some API, with the kernel's BT stack/driver. There must be some (open or closed source) driver available (worst case: some .so module ripped out of an official ROM, maybe?). So why does the headset profile not work? Did the APIs change? Are custom ROMs forced to use another version of the driver?
It also happens to this 50$ chinese tablet i have here: some ROM screw up the touchscreen, some break audio, and so forth. Why can't there be some way of installing a generic ROM, and then side-loading the OEM's drivers?
Thank you again to all ROM developers! This is NO WAY a complaint. Just pure curiosity!
I may be out of my league when trying to describe this, but the processor in our phones is somewhat different to the processor in the bulk of other phones. This is where majority of the issues came from in porting ICS to the glide before ATT released it. Even after the first official ICS update, the modders here were the ones who fixed the keyboard lights... I changed up to JB because the GPS wasn't locking quick enough and PACROM had all the quick toggles and the speed/gps lock I needed.
Sure the kernel is the underlying part that pulls it all together, even still there is all the drivers that need to work with it. If there isn't a bluetooth/wifi/HW Video driver for the version of the kernel, then it gets really tricky and now its coding for a piece of software to speak with the hardware ..... We have things that partially work, but not fully ...as with everything computers, in theory things that "should" work, don't always... I'm an IT tech.. I run into weird **** all the time that "should" work ... takes time, but with persistence and the right skillset, majority of the time a resolution can always be found.