Here goes, I received a micro velocity Cruz t105 tablet from a friend..its a little tacky. Anyway.being its a little older most of the site links and apps that I can find are outdated.
What I'm asking is. I'm pretty new to the android development. I've seen there a custom ROMs for the device.also I've seen that u can use z4root and abd to modify it. Are these apps android specific.like can i use them on any android device.or do I need to find the correct file for the specific device.
sent from my USTMO HD2 android gingerbread
Related
Hey,
I've just recently started Android development and I'm keen to learn as much as I can about the whole system, not just about SDK app development. As such I'm interested in attempting to build my own ROM completely from scratch. I've downloaded the Android Source (and Galaxy S source) and would like to try my luck.
First I've been mucking around creating custom ROMs with the emulator, moving apps from the Galaxy S ROM I dumped from my device onto the stock emulator ROM and testing things out.
Anyway I'm at the point where I'm wondering if it's possible to flash the stock emulator ROM onto a Galaxy S phone? I know the Galaxy S source includes a lot of device specific stuff however I'm not interested in getting the camera, bluetooth or anything hardware specific working just yet.
If I flash a ROM with a stock kernel, drivers etc. onto my phone will it work? Has anyone done this? Will it just brick my phone?
Any help would be appreciated.
Cheers,
Ben
Anyone?
Also, I know people have flashed AOSP ROMs on other phones, does anyone know if they required modifications or whether they are in fact stock ROMs?
nje, can't work. why?
1) different bootloaders
2) different partition layout
3) different (kernel)drivers
4) different vendor setup
etc.
it is possible to flash the emulator image onto a dev device (dream/sapphire) but even then a lot will not work properly!
if you want to learn about the android architecture you should start with building a kernel (there is already a thread about that here) and playing around with stuff like the (file)system and utilities...
Thanks jodue.
Yeah my long term intentions were definitely to build the Galaxy S kernel and any necessary libraries and drivers specifically necessary for the apps I decide to include in a custom ROM.
I was hoping that I'd be able to start out by tweaking a minimalistic/generic ROM (the AOSP default ROM) on my Galaxy S. However, as you've pointed out I'll have to start out with the kernel and all the device specific stuff first.
I've got quite a bit of information on building an Android/linux kernel both from the thread you mentioned and also the official AOSP page. However information on putting together a complete working ROM seems a bit sparse. Does anyone know where I can find some information on the topic?
I'm also curious to learn about the list of things jodue mentioned i.e. Android bootloaders, partition layouts and drivers (generic and Galaxy S specific). I assume detailed information about particular devices and drivers probably isn't available but if anyone even knows where I can learn detailed information about default AOSP ROMs I'd be extremely interested know.
This probably sounds like a stupid question BUT, when developing for Android, should I just use the latest google api/SDK available or should I install them all on eclipse? I'm grabbing them all from 2.0 onwards atm but is there any point?
No. Just get the latest. It will be able to handle the latest kernels and older ones so it would make sense to just get one (the latest one). Good luck in your development.
I have an Alcatel OT 4010x, the Android version of OT Fire (I guess). Firefox OS should be able to run on my phone, right? If yes, can I request for a rom to flash in (and steps, if it's different from flashing an android rom)? Or maybe can someone please point me in the right direction? I have look around Firefox wiki page and XDA's Firefox OS page, but, it seems there's only a guide to port Firefox OS to other phones, can't find an OT Fire's rom anywhere.
Firefox OS needs Android ICS or higher
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.
Ron Shinde said:
As far as I know, Firefox OS requires that you have Android ICS. XDA has some articles on how to install Firefox OS on specific devices such as HTC HD2, Samsung galaxy and Sony Xperia.
Click to expand...
Click to collapse
Isn't that like dual-boot or something? How about something like clean install or anything of sorts? Sorry if it's a noobish question, but, I don't really know about flashing a new OS, I only know about flashing roms of Androids.
Hey guys!!
I am new around here so I apologize for any brake of rules I might be doing around here. You are welcomed to notify my about them
I just got a Geeksphone Peak. On the box it came with Firefox OS, of course. I had it for a few days and then flashed Android in there. I am not sure how, but it looks like Firefox OS is not there anymore, or I can't find it. Any idea how to flash Firefox OS again here so I can have both?
And another question, is there possible to have another version of Android, a lower one? I have Android 4.0.4 Ice Cream Sandwich but probably the system would run faster in an older version of Android.
Thanks in advance!
As far as I know, it is not officially supported to have dualboot. So you have Androd or Firefox OS. You can download the old images here: downloads.geeksphone.com (sorry I cannot post links because I am new user). But Geekpshone has dropped support of Peak so there is no current built. I am trying really hard to build it but so far no success.
As for the Android - where did you downloaded it? You would have to download old built which is not built anywhere - so you would have to build it yourself.
I'm new to the forums and a novice programmer but here's my question:
There's an app I'd like to run on my device for work. Per the play store, the app requires Android 2.3.3 and I'm running 2.2.2. I'm running the most recent version of a custom ROM on an outdated device so can't update my device's build.
I'm wondering if it's possible to tweak the app's source code and repackage it to make it run on my device. I have downloaded the .apk file and tried to install it on my phone and get a parsing error. So with the help of google I have managed to get into the source code using dex2jar and jd-gui. Problem is I don't know much about how apks are written. I found something in the 'accessibilityservice' area that seems to check the android build version, but as far as I can tell that is checking for whether the device is running ICS (if build >= 14) whereas the app is said to be compatible with older builds as well.
Anyway - how complicated would it be to port an app backwards so that I could run it on my phone? You should assume that I'm already in over my head.
Thanks.
petegw42 said:
I'm new to the forums and a novice programmer but here's my question:
There's an app I'd like to run on my device for work. Per the play store, the app requires Android 2.3.3 and I'm running 2.2.2. I'm running the most recent version of a custom ROM on an outdated device so can't update my device's build.
I'm wondering if it's possible to tweak the app's source code and repackage it to make it run on my device. I have downloaded the .apk file and tried to install it on my phone and get a parsing error. So with the help of google I have managed to get into the source code using dex2jar and jd-gui. Problem is I don't know much about how apks are written. I found something in the 'accessibilityservice' area that seems to check the android build version, but as far as I can tell that is checking for whether the device is running ICS (if build >= 14) whereas the app is said to be compatible with older builds as well.
Anyway - how complicated would it be to port an app backwards so that I could run it on my phone? You should assume that I'm already in over my head.
Thanks.
Click to expand...
Click to collapse
A LOT of things changed from pre-2.3 to 2.3 in Android, code-wise. It was a huge upgrade, and a lot of unsupported things were implemented.
It's set to run on 2.3.3 simply because it uses functions that only exist in 2.3.3 and higher.
So to backport it you'd need to get the source code, check what functions require 2.3.3 or higher, edit them to use other functions/write the code yourself. You can't just simply remove the code that checks what version of Android you're running. That won't do a damn thing.
The last part is the near impossible one, because you'd most likely have to write code that goes deep into the Android framework.
If i were you, i'd simply look for another app that can do what you need and doesn't require 2.3.3 or higher. Though there aren't many out there. Most people base their app on 2.3.3 because like 95% or higher use that version (or a higher one).
If you were to dive into this, you'd need extensive knowledge of Android, Java & backporting.
Though i'm not able to help with that, at least the backporting part.
Moonbloom said:
A LOT of things changed from pre-2.3 to 2.3 in Android, code-wise. It was a huge upgrade, and a lot of unsupported things were implemented.
It's set to run on 2.3.3 simply because it uses functions that only exist in 2.3.3 and higher.
So to backport it you'd need to get the source code, check what functions require 2.3.3 or higher, edit them to use other functions/write the code yourself. You can't just simply remove the code that checks what version of Android you're running. That won't do a damn thing.
The last part is the near impossible one, because you'd most likely have to write code that goes deep into the Android framework.
If i were you, i'd simply look for another app that can do what you need and doesn't require 2.3.3 or higher. Though there aren't many out there. Most people base their app on 2.3.3 because like 95% or higher use that version (or a higher one).
If you were to dive into this, you'd need extensive knowledge of Android, Java & backporting.
Though i'm not able to help with that, at least the backporting part.
Click to expand...
Click to collapse
Thanks for the very helpful information. I will definitely not be attempting this.
Most likely will be getting a newer phone in a few months when I'm due for an upgrade so it'll be a moot point. Until then, I'll get by.