i do not have much knowledge on android phones and from looking on the internet there is a lot of tutorials and information but they seem to be specific for a certain phone, like the HTC's for example.
the phone i currently have was purchased from chinavasion.com and it is a phone they have built themselves and have done so very well, i believe it contains hardware from different existing mobile phones and it runs on android v1.6.
i am really wanting to update my phone now and my biggest problem is that there is little internal memory on the phone and i am wanting to be able to save applications onto the SD card which i believe you can on android v2.2, i have heard about rooting but i am very unsure how to do it and whether it would be worth it.
any information on how to update this phone or rooting this would be very much appreciated,
thankyou.
this is the information given by the manufactured/wholesaler
* Qualcomm 7227 CPU is the same chip found in the Motorola Devour Android Phone.
* Though hacking the firmware voids the warranty, Qualcomm 7227 CPU supports all leading mobile operating systems including Android, Symbian S60, and Windows Mobile.
Note: The Android OS version on this cell phone cannot be upgraded or flashed and any attempts to modify the default OS will void the warranty. As a wholesaler, Chinavasion provides no software support, advice, or training regarding the Android operating system and software.
I would also like to have such update!
This phone is also knows under name "TWM T1" (Taiwan mobile), but that version also have donut ROM
There are nice treads in mobile01.com forum about Rooting and APP2SD
Using their instructions, I rooted, managed to install APP2SD and Google Apps on phone, so it's now much more useful than before.
Related
I am not a developer so I don't understand why it is so hard to receive updates on some android devices.
Today, particularly I am concerned with the ICS update . Why is it that even though TF meets all the hardware requirements it still can't receive ICS?
To a n average user like me this is like saying "we both have similar computers but Windows 7 won't work on yours and it's nothing do do with hardware".......
it is not the same at all. For windows computers all of the components are supported by their respective manufactures and all of those manufactures write the drivers for the operating system. By doing this you can install windows (or linux) on most platforms because of the cumulative support. In android there are many more steps. Most drivers have to be written by a single manufacturer which may get hardware from other manufactures but they do not provide software support for that hardware. writing those drivers takes some time and implementing them into each release of android as it changes the parameters it accepts ect. then each device has to be tested rather than just testing one part to make sure everything is in order then it goes through google who do even more checks to make sure that it is near perfect before it is released to the general public
Hi guys, is there a clean generic windows phone 7 os? just like desktops were we get a retail os, is there one for phones? and is it flash-able with all phone?
No
No.
It would certainly be interesting to get hold of the OS as Microsoft delivers it to OEMs to begin the process of adapting it to a certain phone model, writing or modifying device drivers, etc., but it seems nothing like that was ever leaked.
WP is closed, as is iOS; for the reasonably open Android there is of course something like a "generic" version; you could even compile and produce one yourself.
There isn't really any such thing as a "clean generic" phone OS, anyhow. Unlike desktop OSes, phone OSes don't ship with support for the massive array of hardware configurations that are found in the wild. Instead, phone OSes rely on a Board Support Package, commonly simply called the firmware, which has the various drivers needed to interface with that specific model's hardware. This is why, for example, even though the source code is available for the Android Open Source Project upon which CyanogenMod is based, it still takes a long time to get fully functional CM ports to each individual device. On things like WP7, where the source code isn't available (except for the kernel and some core libraries), it's even harder.
However, if what you really mean is you want a "clean" ROM that has no carrier customizations in it, there are "open market" ROMs available for many WP7 devices. These ROMs are still specific to the device whose BSP they contain, but are not specific to any mobile operator and usually not to any region.
thanks for the info guys, but it looks like there are no open market roms for the omnia w yet, well, not yet anyway, will keep an eye out now that i know what to look for,
thanks again guys
Answer is yes and no. No oem device created by Microsoft, but there is Nokia. As you know Nokia is part of Microsoft Windows Phone hardware partner. More options etc has Nokia.
Sent from my Lumia 900 using Board Express
Hello,
First off, apologies if I have posted this in the incorrect forum.
The company I work for is looking to update one of it's product lines and has been toying with the idea of using Android as a development platform. Up until now the philosophy has always been to develop simple, bespoke embedded software that provides only the functionality that is needed at the time. The device itself will be a medical device, and as such will have no telephony requirements (and associated things like contacts, calander and the large majority of the pre-installed Android apps).
I have read, and understand it is possible to re-compile Android from source and remove all of these non-required functionality. My question is really if that is worth doing? i.e. stripping out all un-needed applications that get build into a stock ROM. Or would it be a more efficient to use some form of OTS embedded Linux platform?
Something in Android 4.0 that does seem to be useful is the support for Bluetooth HDP.
Kind Regards,
Simon
Well there are other devices that aren't phones that use Android. Take the motoactv for example. It's a fitness watch that runs a stripped version of Android, but it's still Android and applications can still be programmed and installed to it.
Hello World ! I have identified a need for a smaller tablet and have begun the process to request information about how to have the hardware designed and manufactured. But as we all know, hardware is only half of the equation - the other half is the software. So I have a question for you:
What would the ideal software configuration for an Android-based LTE-enabled TABLET (with SIM card), suitable for ROM developers ?
I have (a little) previous experience (as an end-user) with replacing the manufacturer/carrier ROM for my HTC Desire with the CyanogenMod ROM. That, coupled with my years of experience as a developer (pre-Internet) allow me to at least be aware that there are layers of software from bootup, to device drivers, to OS, etc.
I would like this community to help define (or point me at some documentation) what those specific layers are, which package(s) should be used at each level, up to the point of being able to get into the Google Play Store.
I am not interested in which apps should be discussed - that's the end-user's problem.
Thanks,
Steven.
Dream software config for Android Tablet ROM developers ?
Hey all, hoping to get some visibility & feedback here ...
Steven.
StevenCShearer said:
Hello World ! I have identified a need for a smaller tablet and have begun the process to request information about how to have the hardware designed and manufactured. But as we all know, hardware is only half of the equation - the other half is the software. So I have a question for you:
What would the ideal software configuration for an Android-based LTE-enabled TABLET (with SIM card), suitable for ROM developers ?
I have (a little) previous experience (as an end-user) with replacing the manufacturer/carrier ROM for my HTC Desire with the CyanogenMod ROM. That, coupled with my years of experience as a developer (pre-Internet) allow me to at least be aware that there are layers of software from bootup, to device drivers, to OS, etc.
I would like this community to help define (or point me at some documentation) what those specific layers are, which package(s) should be used at each level, up to the point of being able to get into the Google Play Store.
I am not interested in which apps should be discussed - that's the end-user's problem.
Thanks,
Steven.
Click to expand...
Click to collapse
Original Post : linkedin.com/pulse/google-android-guys-here-idea-you-prashantha-mundkod
Today, I have some business ideas for Google Android guys..
Idea
A tool (a desktop tool and/or android app tool ) for creating ROM and installing stock android.
This tool basically does 3 major tasks.
1. Reads hardware information of an Android device through the desktop/android tool and creates a stock android ROM for that device.
2. Creates a super user , roots the device , installs the ROM created in step 1.
3. Provides an option to keep/remove the super user after the installation based on user sophistication.
(Alternatively, tool will install a generic stock android and then look for appropriate drivers for the device after the installation)
Why do we need a tool ?
Here is what I found while playing around with stock android.
1. Majority of handset manufacturers simply don't bother provide updates . Even if they do, its ridiculously delayed.
2. The UI created by most manufacturers is not innovative or user friendly. They are loaded with ridiculous amount of bloatware. Since they don't bother to provide timely updates either, end user is stuck with an older version of Android regardless of device's capability to support newer versions of android.
3. For an average user, there is no simple way to install a stock android . Users are in mercy of tech forums and developers who volunteer to create custom ROM. Expecting a ROM from volunteers for all devices out there is unrealistic . Trusting those ROMs is another biggest concern as well. Despite the volunteer efforts , installing a stock android ROM still needs some level of IT knowledge , not the cup of tea of an average android user.
4. There is no generic stock android ROM. Reason perhaps is that, creating a package with drivers for thousands of manufacturers would be practically not feasible as the package size would be enormous.
User Experience
An end user who wants a stock android doesn't need to be an IT guy and the tool should be simple to user. Example : Click a button that would read hardware and create the package, next user interaction is a prompt asking the user to install the stock android ROM. All other user interactions such as retaining super user etc is an an option for advanced users.
Manufacturers
Any custom UI or App package a manufacturer wants to push for their device should be updated as App package from manufacturer over a pure android . (Example : Once user install the stock android, manufacturers like Samsung, can push their app like Galaxy gifts etc as a package. )
This would shorten the development cycle for manufacturers as well. Thus updating Android for their device becomes purely a app package for an android version , rather than individual device.
Advantages
For users, clearly the benefit is the ability to have most updated software and experience of pure android and freedom from abandonment of device from manufacturers.
For Google (and Android as a platform ), one of the biggest competitive disadvantage is , its fragmentation. One of the reason for fragmentation is that, for a large number of devices, simply there is no easy way to update the software. The tool could help solve fragmentation issues.
The tool may be included as part of Google's attempt for Android One initiative. Certainly , no explanation is necessary on how it benefits Google from having one single version of android in all (or at-least as many devices as possible) android devices.
For now, that's it . When i am free, I will post the details on how exactly they should do it .
Experts... What do you think ?
Disclaimer : Views expressed are my own.