Just have owned i7500, first remarks:
- android without internet is useless
- android without touch screen is useless
So porting this system to Vox is rather meaningless.
m32
Related
OK, so is there any means to dual boot android/android? iphone can do it, why not android? I would like to chose between cyanogen/htc stock on the fly for emulation purposes. is this possible without having to set up all my nonsense?
unlikely =\
windows mobile and the iphone can not technically dualboot android, they use a program to clear all of the memory in order to boot android ontop of windows mobile/Iphone OS (haret), therefore the original operating system is no longer running and resources are devoted to the new virtual one running
android doesn't currently have a function similar to haret I far as I know (I'm rather new to android)
Its not impossible but as far as I can tell, it hasn't been done yet...
Hi Guys,
I'm looking for some guidance from experienced Android devs - I have an O2 Joggler device which the original OS (am i'm being kind) is appauling.
Work has been underway to get Android x86 working on this device and currently we have a working image of 1.6 on the joggler - the only problem is the graphics are very slow, this is because there is the worlds most hated GPU in the Joggler (GMA500).
However - recently the official Android x86 guys have been working with a GMA500 device (Intel's S5 Viliv) which closely shares it's inners with the O2 Joggler and they have posted up a Froyo image with GMA500 support.
I've tried myself (not really knowing what I'm doing) and a few other guys have also, and the image doesn't boot off the bat on the joggler (just sits at the jogglers EFI screen not displaying anything but the O2 logo)
So, I'm looking for help from you guys as to what / if there is anything we can tweak to get this running like 1.6 (but hopefully with smooth graphics thanks to the new GMA500 support)
I don't have much experience in Android dev'ing but I have a strong IT background and some linux experience - I'm willing to do whatever you guys can suggest to see if we can get this working.
So, first question I guess is, what do you need to know to get the ball rolling?
Here is some info on the joggler's hardware; http://jogglerwiki.info/index.php?title=Hardware
The 1.6 Android Image (that works fine apart from slow graphics) ; http://jogglerwiki.info/index.php?title=An..._Prebuild_Image
How that image was made; http://jogglerwiki.info/index.php?title=Build_Android_Image
Android x86 Image for Viliv S5 (Has the GMA500 support we want!); http://android-x86.googlecode.com/files/s5_froyo_101008.img
Viliv S5 Specs; http://www.umpcportal.com/products/Viliv/S5/
Any help you guys can offer would be madly appreciated by the joggler community, as Android is the perfect OS for the little device!
Thanks
I should probably add, I have tried to replace the system.img from the working 1.6 release with the one from the Viliv 2.2 release, but the 2.2 file is system.sfs not .img so I guess the kernel won't find it..
Presume the kernel would also need to be changed too anyway??
Hello
I have a Nokia E61i, and want to install Android on it. After Googling for a long time, I only found the non free M1 project which reveals to be in fact a USER INTERFACE, a skin.
At the moment, the phone has Symbian S60 (probably v3, not sure - can't find the ver in device), and sim-UNlocked. I don't have any data/USB cable (probably can buy on Ebay/Dx).
Any Android would be better than Symbian for me, including 1.0
Thanks.
I have a lot of old smartphones.
While trying to use those phones, I suddenly thought about it.
Is Android the least possible like a DOS operating system?
For example, if you want to use my phone as a MAME game Emulator
Without loading apps with various functions during Android booting
1. Turn on the SmartPhone
2. Enter Android's Boot Loader
3. Boot the least Android OS (Excluding phone function, text function, GPS function, NFC function, and many other functions....) So that only the MAME app can be launched.
Regardless of the model, only the minimum Android OS is provided. (Like MS-DOS)
4. Launch MAME Emulator
Is that possible?
If that is possible, I think I can use it with the remaining old smartphones.
MAME emulator runs on Android 4.1+ what can be considered to be a minimal Android OS compared to latest Android versions.
The new RootMyTV exploit brings a lot of ideas to my mind one of them being , replacing the inbuilt system apps with rebuilt versions that have much more control and maybe a better UI.(But still a similar UI otherwise it will become super hard for people to use it.)
The new Inbuilt app (Settings app in this case) can have (Not limited to):
Finer control over the options
Always upto date UI (Web OS 5.0 UI on older devices , Web OS 6.0 seems to be a fully non-multitasking OS)
Adding newer features from the newer devices as soon as possible.(Game optimizer comes to mind)
But there is a problem , the OS seems to be using Verified Boot so is this possible? Will we have to create some kind of Magisk but for Web OS?(Web Os is based on Linux)
If you do have any ideas please do share.
We probably will not be testing them immediately on the TV's (No one wants a 2000+ dollar paperweight) and instead using the emulator.
Since I have been changing the system a lot myself for quite a while now, I can say that at least the UI of the apps should be relatively easy to replace (most of them are based on web technologies). The easiest way to modify / replace webOS / default palm apps should be via overlayfs.
But I'm also always a little 'confused' (in a lack of a better friendly description) about the countless strange questions from several users, whether you can e.g. install webOS 6 on a device with webOS 4, if you can enable feature X of a newer generation on your TV or how you can use the root access to defeat copy protection mechanisms for obviously illegal purposes.
There's obviously a lack of a basic understanding how an operation system in general and especially on a TV works. The different generations have different hardware that require the corresponding proprietary drivers, kernel modules and system services written by LG (which are of course closed source).
Obviously, this means that it is virtually impossible for most features of newer devices to be made available on older devices.
For example, you can rebuild the UI of the Game Optimizer, but the functionalities of it are not easily backward portable. If a TV does not support VRR, for example, there is nothing you can activate in this regard.
There are a very few exceptions, like OLED Motion Pro, which can be enabled on 2019 models - but only because this feature is already supported by the TVs and was disabled at the last minute before release. OLED Motion Pro will never activate on a 2018 (or earlier) model!
I hope this helps a little better to understand what is possible and what is not. UI / UX yes, functionalities and features not or only to a very limited extent.
I do know about the feature enabling limitations etc.
By adding newer features I meant the UI/GUI of the newer features , we cant really do anything other than that.