What would be the best way to get communication between the radios (CDMA) and the operating system?
I ask this since after all the Ubuntu Touch operating system is based upon Android.
Or is it mostly because the RIL's (Radio Interface Link) are proprietary to Android?
This is mostly just a question why it hasn't been integrated yet amongst the community for *any* device regardless of what radio (CDMA or GSM) a device has.
It'd be nice to try something new but I still have to have my phone as a phone lol.
Sent from my DROID RAZR HD using Tapatalk
Deleted
Related
Alright, I know this will sound weird but I have my reasons for asking:
Is it possible a flyer rom would run on the Evo View? I know it seems unlikely but the only difference -should- be the CDMA radio and a few kernel files missing for the CDMA / Wimax radio but aside from that there should be no difference. So is it possible to run a Flyer rom on my evo view 4G? I know some devices with similar architecture can run the same roms (My friend had a device that was able to run Desire roms) just need to know if I can run one of the honeycomb flyer roms.
When I first got the view I thought they would run the same Rome but apparently not. I used to have a xoom and both the wifi and the lte version both used the same Rome so I don't know why that's not the situation here
Thanks for the info.
Sent by breaking the sound barrier
Hi all. I have a random question. Why is android criticized for its fragmentation but not windows.
Doesnt windows pc come with so much more different hardware Configurations?
How do developers do it for windows then?
Sent from my HTC Desire using XDA
lol...
IMHO The main problem is that despite the numerous configurations of PCs the OS is always the same. Unique to all/everybody no matter the hardware.
The differences are solved using custom Drivers for the HW (usually from the manufacturer) but that does not change the OS.
But with Android, there is not a "unique/universal" version that works on every hardware. It is modded by every hardware manufacturer/implementer.
Starting from the "root version (official android release)" Drivers are usually integrated to the OS. Also many Mods by each developer. So, in the end you get a "customized" version of the original. And so the so called "fragmentation"
This is one of the main advantages/deficiencies of open source. You are not tied/limited by a closed source OS, but in the other end, you have lots of variation of the same software.
Just a few random thoughts ...
Have fun
Dip
I don't know about the rest of you guys, but I moved on to another phone a while ago. But I have always loved my Atrix... Has anyone ever thought about seeing what kind of linux unit our phones could be? I mean, minimal phone code & use both processors for Ubuntu or whatever popular arm linux is available.
My main deal here is that the phone w/ the lapdock has always been an awesome wifi terminal. I just feel like half of it's processor is wasted running the phone UI. Anyone have any plans for a full linux Atrix project?
& yes, I already have ubuntop on my Atrix & have had it since it came out.
& yes, I know Canonical has already stated they are working on Ubuntu for phones, but the stench of their Vaporware is hurting.
It all comes down to the kernel. With the limited support we have for our device, it's hard enough trying to run android on the thing (ICS); an operating system which is "native" for phones, it'll be that much harder to port desktop Linux. Standard Linux kernel is starting to come with android stuff, but it's still going to need device specific patches.
Now if ubuntu comes out with a universal arm/tegra kernel, that would be kind of amazing.
Sent from my MB860 using xda app-developers app
http://www.ubuntu.com/devices/phone
Ubuntu for phones uses Android as its base, so does that mean features that are broken in ICS and JB builds would still be broken in UFP?
Not really. I've spent a lot of time with these as I hope to bring it to the Atrix. But it's not based off those builds, In the video he describes that it is ment to be compatible with any devices that run android. It is actually built off their operating system simmilar to windows 8 and windows 8 RT. It will be released for the samsung galaxy nexus. It will function similar to how their OS runs on computers, where it comes with one OS, but it will be compatible with another. Ubuntu Phone will hopefully be able to run on devices that run android. meaning that as long as you don't have an iphone, or windows phone, you should be able to run it. Which to me is really exciting as I see a lot of promise with this OS, especially along side our lapdocks
That would be amazing if we could get a full supported ubuntu for the atrix. Im looking to reutilize mine (despite its broken digitizer)
Sent from my SAMSUNG-SGH-I747 using xda premium
Unfortunately, almost nothing stated in here is accurate.
The only Android dependency is the Android Kernel. So any issues we have, would still exist in Ubuntu for Phones.
I do hope the Ubunutu OS will be able to run on my atrix 4g. But yes, all android issues will exist if we have to stick with the atrix 4g kernal.
IF ported Galaxy R 3.x.x kernel gonna fully working before late Q4 2013, I assume, ubuntu for android will working flawlessly on our atrix
Hi there,
I'm currently studying Software Development and Engineering in college. I'm planning on building something with android OS. I'm just wondering how Android handles hardware.
Does it detect the available hardware on a device it's installed on? or does it need to be set up for a specific configuration of hardware. Say I install android on a tablet with no phone capibilities or GPS for example, does Android handle the fact that these features aren't there and just get on with it's job? Or does it need to be tweaked for the device in question?
It needs to be built from source for the device, with all hardware drivers and binaries. Unlike Linux and Windows, you can't just install Android on a phone and have it work with most hardware. Computer OSes have years and years of driver support and backing from manufacturers. On smartphones, with the exception of a few manufacturers, a lot of them are very stingy and secretive with their proprietary drivers and other essential files, and they're not really supportive of third party development. This sucks, but it should change in future and smartphones could be just as open as PCs (I hope).
Android has a HAL (Hardware Abstraction Layer) for handling the hardware. Technically it's capable of detecting and enabling the device hardware in a modular way. But since the Android phone's hardware doesn't change typically throughout the life of the phone, the manufacturers tend to tweak it for each device so that you get the optimized version which can run only on that device. While PC like functionality is certainly possible with Android OS itself, it's not needed on a phone since there is not much scope for hardware addition / removal / upgrade.