Related
Tried to search for this but couldnt find anything is it possible to get a mango ROM working on an android tablet?
There are loads of 7" Android tablets out there for under £60 not the biggest fan of android but would like a cheap tablet for quick browsing of web and showing photos to friends etc.
Would be cool if could get a mango ROM flashed onto one of those 7" tabs
That's a good question. I'd also be interested if it were possible to drop Mango onto a tablet that started out life as an Android. It'd have to be a 7" screen, and it'd have to have a capacitive screen
jasongw said:
That's a good question. I'd also be interested if it were possible to drop Mango onto a tablet that started out life as an Android. It'd have to be a 7" screen, and it'd have to have a capacitive screen
Click to expand...
Click to collapse
Why does it have to be 7"? Resolution?
mcorrie1121 said:
Why does it have to be 7"? Resolution?
Click to expand...
Click to collapse
I think we're pretty much locked to 800x480 resolution, which I suspect would look horrible on a 10" tablet
Yea but im sure if it possible to port people will figure out a way around that like a regist edit or something. Actully maybe on a bigger screen more tiles would be visible instead of only 8 tiles or 6 it would be like 12 or 14
That is an interesting question. I was wondering the same thing, which is how I found this thread...
First of all, it would have to be a tablet with a WP7-compatible CPU. Unlike most x86 chips used in PCs, different ARM chips may have incompatible kernel-mode interfaces, so the core of every OS must be built for that chip. Linux (and therefore Android) can be built to run on pretty much any ARM chip. In theory, the same is true of Windows CE (the kernel that WP7 is built on), but without kernel sources (and no, the CE6 and CE7 sources available from MS aren't quite the same) we can't build custom kernels like that.
Second, and much harder, would be finding the drivers for the hardware. Every single WP7 device comes with a bunch of OEM code, the "firmware", that interfaces the kernel to the hardware. This is different from device to device (thus why, if you do something like flash a Samsung Omnia 7 ROM to a Samsung Focus, or even a Focus r3 ROM to a Focus r4, the phone won't work correctly afterward). Android has something similar, but again it has two benefits: the kernel is open-source, and there are Linux drivers for almost every piece of computing hardware (although not always very good ones). For WP7, porting to a new device is very hard because of this. The HD2 worked because
A) it originally ran a CE-based OS (an older one, but still CE based)
B) it's very similar in hardware to the HD7 (not enough to run HD7 ROMs, but enough to pull some drivers from HD7 ROMs)
C) an early firmware for the WP7 kernel was developed for it and leaked.
None of those things are going to be true for the typical random Android tablet.
GoodDayToDie said:
First of all, it would have to be a tablet with a WP7-compatible CPU. Unlike most x86 chips used in PCs, different ARM chips may have incompatible kernel-mode interfaces, so the core of every OS must be built for that chip. Linux (and therefore Android) can be built to run on pretty much any ARM chip. In theory, the same is true of Windows CE (the kernel that WP7 is built on), but without kernel sources (and no, the CE6 and CE7 sources available from MS aren't quite the same) we can't build custom kernels like that.
Second, and much harder, would be finding the drivers for the hardware. Every single WP7 device comes with a bunch of OEM code, the "firmware", that interfaces the kernel to the hardware. This is different from device to device (thus why, if you do something like flash a Samsung Omnia 7 ROM to a Samsung Focus, or even a Focus r3 ROM to a Focus r4, the phone won't work correctly afterward). Android has something similar, but again it has two benefits: the kernel is open-source, and there are Linux drivers for almost every piece of computing hardware (although not always very good ones). For WP7, porting to a new device is very hard because of this. The HD2 worked because
A) it originally ran a CE-based OS (an older one, but still CE based)
B) it's very similar in hardware to the HD7 (not enough to run HD7 ROMs, but enough to pull some drivers from HD7 ROMs)
C) an early firmware for the WP7 kernel was developed for it and leaked.
None of those things are going to be true for the typical random Android tablet.
Click to expand...
Click to collapse
So, long story short, probably not gonna happen. Gotcha. At least I know some of the work that is takes, for I am sure that it will take much more work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
yea your not gonna get arm wp7 on an android tablet , however there are many simulations of wp7 in android tablets , so if you want wp7 on an android yes thats the way to do it , but why?
Hey devs, lets start cranking this baby out. Lets do some research, and find out what he need to get W8 on the G Tablet
Please details, or possible obstacles you find, or feel
Sorry Charlie
DJTJ said:
Hey devs, lets start cranking this baby out. Lets do some research, and find out what he need to get W8 on the G Tablet
Please details, or possible obstacles you find, or feel
Click to expand...
Click to collapse
Well, this has been answered before, but just to make you happy...the closest you will ever get to seeing Win 8 on a gTab is if you play a YouTube video of it.
Won't be possible for numerous reasons:
1. Doesn't meet the hardware specs (too little ram, too little storage, missing various pieces of hardware, screen res way too low, etc)
2. Unlike Android (which is open source), Windows is not...MS would be all over anyone butt if they tried to modify it for another device
3. MS has already stated Win8 (RT) will only come pre-installed on OEM devices meaning the OEM's build will be specific to their hardware
4. We can't even get drivers for our current hardware on Android...how do expect to get Windows ones for it??????
5. I could go one, but I hope you get the point
Al
aabbondanza said:
the closest you will ever get to seeing Win 8 on a gTab is if you play a YouTube video of it.
Click to expand...
Click to collapse
Precisely.
How many devices (of any type) can you name which run any form of Windows (or MS-DOS, for that matter) without MS's blessing? (Let's skip pirated copies here.)
rajeevvp said:
Precisely.
How many devices (of any type) can you name which run any form of Windows (or MS-DOS, for that matter) without MS's blessing? (Let's skip pirated copies here.)
Click to expand...
Click to collapse
My thoughts exactly....... Why OH Why would you want Microsoft software on a Android Tablet. UI for Win8 are not that great and perfomance wouldn't be either. Really Metro on Android it's bad enough they have a launcher for it let alone someone wanting a OS. I would rather try putting IOs on this thing then somthing from Microsoft. Just saying.
Even if the UI is fantastic and the performance is great, the idea is a non-starter. Here's why:
Let's say Hannspree makes a deal with MS tomorrow and releases Win 8 (completely unlocked of course!) on their Hannspad next month. Now, since the Hannspad and the gTab are very close tablets, you could conceivably just pull the official files from that tablet and use it on the gTab with minor modifications. And let's also assume that you've got Win 8 working perfectly on the gTab by going in with a hex editor and patching whatever binaries. And finally, when you boot it, Win 8 blows the socks off everything else.
Unfortunately, what you've done now is create a pirated distro of Win 8 -- a warez distribution -- and no reputable BBS (certainly not XDA!) will touch it. You'll have to post your wonderful creation on some 0-day warez upload site for people to use.
The technical problems are actually a tertiary concern here.
I have it on my U30GT Cube, well, not really on it, but with the "Splashtop" app I can use my main PC (Win8) on my tablet touch screen and its great.
So, while you may not be able to fully install Win8 on the Gtab, if your main PC has Win8 (I assume any other Windows OS too), I do not see any reason why Splashtop would not suffice or indeed enhance any tablet.
I am considering buying the Transformer TF700, but I am wondering if it is possible to root the tablet and install Windows 8 on it when W8 is available for purchase?
Regards, Sari
Unlikely, Win 8 requires an encrypted bootloader.
Installing Win8 as a 2nd OS, NO. But running linux as a second OS and Virtual machine windows on it, Yes. Just not sure how stable that would be, or how fluid. You can always wait and see as asus have announced a partnership with Microsoft for a duclboot android windows Pad...maybe, HOPEFULLY, the hardware will be close enough to our infinity for devs to port it over
Its possible. That locked down requirement is for OEMs, I doubt it'd be hardcoded into the OS since that'd be hard to detect or easy to spoof. Asus's WinRT tablets are Tegra 3 based, so depending on which variant they use it might be relatively simple to port.
Very unlikely. I couldn't spout the technicals for you, but it is a very closed down system, and MC certainly doesn't want any modding or porting in any way.
Assuming you mean Windows RT, then...well, I'm sure Microsoft is probably going to do everything they can to ensure that Windows RT doesn't run on anything other than approved devices.
Ah, that's disappointing :l Thanks for your replies!
I used to be very interested in Win 8 but now I am not sure I want it on a Tablet. I know eveybody is saying it is going to be great on tablets, but nobody really knows yet, and I have been an early adopter of other mobile OS products like Win Smartphones, that were big failures. The beauty of Android is it is more open source so its easy to create apps for it, so I am not sure Windows will ever get the kind of app libraries (Free or cheap) Android and IOS have. Looking at Microsoft's history, I am not sure they will excel in this market at this point.
Just my thoughts . .
guitar1969 said:
... Looking at Microsoft's history, I am not sure they will excel in this market at this point.
Just my thoughts . .
Click to expand...
Click to collapse
This ^^ -- given the fact that I've owned several Windows Mobile devices that have hung somewhere in space as far as support and development went and that MS have crashed several of their purportedly groundbreaking devices in the past (the Zune and the Kin spring to mind in particular) doesn't really inspire me with any hope that the Surface and its successors will be anything to drool about, except maybe for 'paper specs'.
For the graphically inclined and those in search for a read, a search for "Microsoft failures" comes up with, amongst others:
http://www.eweek.com/c/a/Enterprise...osofts-Biggest-Failures-and-Successes-500262/
http://www.money.co.uk/misc/microsofts-biggest-flops-and-failures.htm
http://www.complex.com/tech/2009/05/a-history-of-microsofts-biggest-failures
Just for fun, those.
No way.... The largest software development company in the world has had failures? Who would ever have thought that?
almostinsane said:
No way.... The largest software development company in the world has had failures? Who would ever have thought that?
Click to expand...
Click to collapse
It's not that they had failures, smart boy -- it's their touting so much 'groundbreaking' stuff that wouldn't even float by itself if you threw it in a lake of polystyrene packaging chips.
Ugh, Win8 with its crappy touchy-feely interface. I am fully convinced that desktop and laptop systems are here to stay, whether for gaming or productivity, so I do not need an interface optimized for mobile touchscreen devices on my rather immobile main piece of trusted hardware.
Jotokun said:
Its possible. That locked down requirement is for OEMs, I doubt it'd be hardcoded into the OS since that'd be hard to detect or easy to spoof. Asus's WinRT tablets are Tegra 3 based, so depending on which variant they use it might be relatively simple to port.
Click to expand...
Click to collapse
I think we should wait for any publicly available Windows RT firmware for download. It Asus releases Tablet 600 - that would be even better for us.
I recall the first Hackintoshs (based on first Mac OS X 10.4/Tiger for x86) being run on Pentium 4 and AMD platforms. It required VM and very strong BIOS modifications (as Macs had EFI, at that time unavailable for PCs). Then there were some modified kos (kernel objects, i.e. modules) that enabled it running on PCs with stock BIOS. Later a vanilla kernel was compiled that enabled the system work without problems.
Considering Windows RT port, the last step would be most likely impossible as we don't have kernel source (AFAIK the latest Widows source available is that one of Win2000), but nothing prevents us from attempting to run the Windows RT-enabled device firmware on TF700 and trying to debug failures. However, this can take a long time.
I'm more concerned about running any Linux distro in dualboot with Android %)
What about the new ASUS tablet, tegra 3, windows RT. The same hardware, but different system and screen resolution.
LEGOracer69 said:
What about the new ASUS tablet, tegra 3, windows RT. The same hardware, but different system and screen resolution.
Click to expand...
Click to collapse
Is anywhere its firmware?
The main issue would be the bootloader; the resolution in Windows is much easier to fix.
P.S. "I want NATIVE ubuntu on TF700!" - +1. I bought TF700 as a super long-lasting netbook =)
I have the Asus TF600. It has a lower screen Res and twice the ram of the TF700. WIndows RT requires activation just like the desktop version.
LEGOracer69 said:
What about the new ASUS tablet, tegra 3, windows RT. The same hardware, but different system and screen resolution.
Click to expand...
Click to collapse
That's wonderful!
When did you buy it?
Have you found the firmware?
I only found this: http://support.asus.com/download.aspx?SLanguage=en-us&m=asus vivotab rt - there is only a manual.
Windows activation has never been a probem since its appearance in XP =) The bootloader should be more tricky.
tf700t 1gb ram win8 problem
Even if someone manages to port Win8 over to the tf700, do you think they will curb the use of it by shutting it down from the windows market side?? Especially with RT you wind up at the complete mercy of Microsoft when it comes to applying any apps to the device. I'd be interested in seeing if it could be done as long as there is no hang up on the application side of the equation. Won't do me much good to have a working os with no apps to run on it.
Cheers
Hello, I'm really new to Android devices. In fact, this is my first Android-based device ever. But I do have a lot of experience with Linux and Windows, and it's weird how locked down ARM-based hardware actually is. Android isn't as bad as Apple, but it's still a lot less freedom than I'm used to having. I'm getting the impression that installing custom ROM would be almost as much of a pain as installing the Homebrew Channel on a Wii.
Anyway, one thing that I should point out about my device is that it has no touchscreen at all. It has a touchpad and a keyboard in a laptop form factor, but it runs Android. It has SD card slots, USB ports, and an Ethernet port. It's a netbook with smartphone hardware. I'm curious what I can do with it, and I wouldn't be losing much if I bricked it.
If it were possible, I'd be interested in figuring out how to compile a custom version of Linux for it and flash it to ROM. I really think X with a light Window manager would work well on that hardware. If I can't, though, I would be content with a newer version of Android. It's currently running Jelly Bean and I'm wondering what the new versions are like.
The only thing I've been able to find out about the device is that it's based on a WonderMedia Prizm WM8880, has 1GB of RAM, 8GB of storage, and a 1.5GHz Cortex A9 processor. Mali-400 Graphics. In Google Play, the device is listed as No Carrier WonderMedia GA-1311F. I did a search for GA-1311F, and I found no results.
Note that I don't have an actual Manufacturer or model number, everything I can find digging around leads back to the chipset manufacturer, WonderMedia or some company called WMT. It seems like WonderMedia has ties to VIA technologies, and that they definitely don't make the device I'm using. So that means I have no idea who the manufacturer is.
Is any of this information helpful, or is my device unable to be hacked simply because the manufacturer is too obscure?
Sorry to bump my own thread, but I thought I would mention that I've managed to find out about a method called KingRoot that often works on Android 4.2. I managed to install the APK, but the program got to around 60% and then said my device couldn't be rooted.
I'm not crazy about most of the other methods because they require a USB cable that I don't have. Most Android phones or tablets would presumably have a mini-USB port with a small end for the phone and a large end for the computer, like my Windows Phone does. This machine only has regular-sized USB ports, however, and thus I would need to buy a USB male A to USB male A cord that's capable of performing the same function. I hate to waste the money on it not knowing if it will even work, though. I'm also wondering if I need to worry about crossover vs. patch cables like I would with Ethernet, etc. It's starting to seem like more trouble than it's worth.
There was another method I tried called OneClickRoot, but they told me that I needed to have that same dreaded cable hooked up to my PC, AND pay them $20 on top of it. I'm pretty sure that's ridiculous.
I'm probably going to figure this out eventually, but I'm really frustrated that this is tougher than hacking my Wii was. Embedded systems with non-standard hardware are an amazing pain to deal with.
EDIT: Even thoughc it said it failed, all of a sudden BusyBox installed successfully after I restarted the computer. I think I may have done it, although I'm not sure. Apparently I have a Linux kernel on here already somehow... is that the part of Android that's based on Linux?
imgur.com/HiRyqW2
Still, there's not much I'm finding that tells me how to set up anything much better than using a terminal and a VNC viewer within Android to view a Linux system running on top of it. I guess that could be useful if I had a beefier Android device, but with this it's only useful for a command line.
Hi,
Thanks for using XDA Assist.
Try asking your question in the General Q&A forum:
Questions and Answers
Good luck & welcome to Android
Hi everyone.
Every year millions of phones and tablets are produced. Because hardware makers don't worry about updating them, those devices are often dumped. However, lots of them are very capable machines.
As I've read these forums for years, I've seen a lot of work from a lot of people trying to bring those forgotten devices to life again by making unofficial ROMs with tons of customization, new features, and great efforts like LineageOS and PostmarketOS. However, those lack the resources to bring an updated OS for the majority of those binned and obsolete phones.
If I'm not wrong, the biggest issue about replacing the original OS on those devices are the bootloaders and drivers/blobs for the large amount of different hardware configurations. There are multiple workarounds, shims, ports that solve those problems for one or other device.
It might be quite naive, but i'd like to ask a question I've been thinking about lately. AFAIK, if I have the blobs/drivers for a camera, wifi, bluetooth, GPS or other "peripheral" for a devices' original ROM running Android 4.4, I can make it work on AOSP 4.4. I know this might be crazy, but:
As long as I have the blobs for a certain chipset and display/touch, why can't we use a VM running a nano version of AOSP that matches the devices' original ROM that bridges the device IO to the main ROM?
As an example, imagine wifi. I could network bridge AOSP 9 to a VM running AOSP 4, which would then have the drivers so network would work. The same for bluetooth or camera or GPS, maybe? Is this absolutely unfeasible?
Thank you for your time!
wasserprojekt said:
Hi everyone.
Every year millions of phones and tablets are produced. Because hardware makers don't worry about updating them, those devices are often dumped. However, lots of them are very capable machines.
As I've read these forums for years, I've seen a lot of work from a lot of people trying to bring those forgotten devices to life again by making unofficial ROMs with tons of customization, new features, and great efforts like LineageOS and PostmarketOS. However, those lack the resources to bring an updated OS for the majority of those binned and obsolete phones.
If I'm not wrong, the biggest issue about replacing the original OS on those devices are the bootloaders and drivers/blobs for the large amount of different hardware configurations. There are multiple workarounds, shims, ports that solve those problems for one or other device.
It might be quite naive, but i'd like to ask a question I've been thinking about lately. AFAIK, if I have the blobs/drivers for a camera, wifi, bluetooth, GPS or other "peripheral" for a devices' original ROM running Android 4.4, I can make it work on AOSP 4.4. I know this might be crazy, but:
As long as I have the blobs for a certain chipset and display/touch, why can't we use a VM running a nano version of AOSP that matches the devices' original ROM that bridges the device IO to the main ROM?
As an example, imagine wifi. I could network bridge AOSP 9 to a VM running AOSP 4, which would then have the drivers so network would work. The same for bluetooth or camera or GPS, maybe? Is this absolutely unfeasible?
Thank you for your time!
Click to expand...
Click to collapse
That's sort of what project treble is.
Project Treble
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
forum.xda-developers.com
I was reading about it and it seems like treble is not very seccessful. I imagine Google isn't very interested on this, as they want phones to be sold every year. Anyway, I was asking about this specific method of making phones and tablets compatible with today's OS or, who knows, even linux.
wasserprojekt said:
I was reading about it and it seems like treble is not very seccessful. I imagine Google isn't very interested on this, as they want phones to be sold every year. Anyway, I was asking about this specific method of making phones and tablets compatible with today's OS or, who knows, even linux.
Click to expand...
Click to collapse
Yes and the only way it might work is trebel. Because treble handles lot of the problems involved with booting newer androids on older systems.
You can run linux on older Androids or even Windows XP.
How to install a Linux desktop on your Android device
Get even more from your Android device by running a desktop OS! Lots of options including Debian (no root), Ubuntu, and Kali Linux.
www.androidauthority.com
Running Windows XP on Android
No rooting or custom modifications needed, we’re going to do this with stock Android and a few free (but high-quality) apps.
centerorbit.medium.com
Also, it's not that the OS gets deprecated, it's that the applications like Google Play services which become heavier as years go by.
Degoogled-Android on my Android ICS phone worked fine till it's screen got busted. With Google Play services, it was impossible to install any app since its paltry 400MB storage was extended/
Thanks for your answers!
Running other OSes via VNC is just meant to use the devices as mere thin clients, and that was not the objective.
The Project Treble will never be as widespread as it should be, because Google is obviously not interested in making phones last longer (they want more devices to be sold). Of course I was not talking about devices 10 years old, more about 5yrs. They have specs good enough to run contemporary Android and most of non-entertainment apps.
The obstacles to being able to do this are artificial. The problem is there are no drivers and project Treble does not address this in any meaningful way. Manufacturers aren't interested in this too because they want to sell more chips. So the only way it came to my mind it could work was by running a very light VM with an older Android for which the components' drivers were available. Of course main components would still have to be compatible with newer Android, such as the SOC. But things such as wi-fi, camera... could be bridged from a VM, I believe.
Not sure, but I'd guess the low-level interface would have to be outside the VM.
That is, to be able to run the VM you'd have to have some drivers already in place. I'm also not sure everything can be virtualized. For example, desktop VMs couldn't so easily passthru PCIe or USB to VMs, at least in the past.
There's some EU push to make fixing and servicing some non-phone devices easier, and to mandate labeling phones (and other devices) with repairability scores. Maybe eventually they could mandate, under certain conditions, the logical separation of hardware and software?
Well, after a long time, for those who where curious about this thread: the project Halium is exactly what was in my mind. If I'm not wrong, it basically consists in a minimal Android rom running on a Virtual Machine which then interfaces with any Linux distro, effectively giving the phone the ability to run a (more or less) updated version of Linux kernel and, therefore, many Linux distros. https://docs.halium.org/en/latest/project/Scope.html
hkjo said:
Not sure, but I'd guess the low-level interface would have to be outside the VM.
That is, to be able to run the VM you'd have to have some drivers already in place. I'm also not sure everything can be virtualized. For example, desktop VMs couldn't so easily passthru PCIe or USB to VMs, at least in the past.
There's some EU push to make fixing and servicing some non-phone devices easier, and to mandate labeling phones (and other devices) with repairability scores. Maybe eventually they could mandate, under certain conditions, the logical separation of hardware and software?
Click to expand...
Click to collapse
You are right, and I believe Halium just works on phones which are minimally supported by Linux kernel drivers (like basic SoCs). But all those other hardware parts, like GPS, Wi-Fi, Camera... can be brought to life this way, I think.
Thanks for your insight!