Froyo on the G1 and other devices - Android Software/Hacking General [Developers Only]

First off, allow me to introduce myself: I'm an 18 year old cook from new orleans and I'm fairly tech savvy. I have an ipod touch and enjoyed hacking the **** out of it, and now I have a G1 and look forward to hacking the hell out of it as well, espcially since android is much more hack friendly and so far I absolutely love it compared to the iphone os.
Ok, so I just downloaded sign-passion-frf50-from-ere27.1e519a24.zip
From what I understand this is Froyo (2.2), which cannot(?) run on the G1.
Can I get this to run on the G1? If not, can I get 2.1 to run on the G1?
If it is possible, but very difficult, please let me know anyway so at least I know what I'm up against.
On this note, what is the process of manually updating the android os anyway?
P.S. I did search before posting this, and nothing seemed to spefically match this post

mattj7 said:
First off, allow me to introduce myself: I'm an 18 year old cook from new orleans and I'm fairly tech savvy. I have an ipod touch and enjoyed hacking the **** out of it, and now I have a G1 and look forward to hacking the hell out of it as well, espcially since android is much more hack friendly and so far I absolutely love it compared to the iphone os.
Ok, so I just downloaded sign-passion-frf50-from-ere27.1e519a24.zip
From what I understand this is Froyo (2.2), which cannot(?) run on the G1.
Can I get this to run on the G1? If not, can I get 2.1 to run on the G1?
If it is possible, but very difficult, please let me know anyway so at least I know what I'm up against.
On this note, what is the process of manually updating the android os anyway?
P.S. I did search before posting this, and nothing seemed to spefically match this post
Click to expand...
Click to collapse
Even if all Android systems have the same roots, they differs on various devices. This is caused by different hardware specs: CPU architecture, drivers, customizations; and there are some custom add-ons as well: Google apps, Sense UI, etc. This is why it isn't possible to run OS designated for other devices, even if both of them are running "the same" system.
Porting is a process of mixing up bits from both systems to get some features from one device to another. And adding some missing parts. We have to wait for someone to manage to build workable version of Froyo system for G1 devices.
Ahh and there is no problem with 2.1 on G1 - there are plenty of 2.1 roms for this device, I personally recommend CM5.0.7 .

I see. So do you think that froyo will be ported to the g1? Where can I download the roms for the g1? and how do I install them? Is there a way to get sense ui on the g1 after I install CM5.0.7? Thanks for all the help

Well first you will need to root your phone. There is tons of information on that. I'm sure you'll find a guide no problem. Is you want cm5, which I highly recommend as well, go to cyanogenmod.com and look in the forums under experimental. You cannot, however, simply add sense to a rom. It's a lot more complicated than that. There are lots of sense roms though. Check the g1 forum here on xda. As for froyo, time will be popping up soon enough but we're all going to have to wait until the source is released sometime in the next week or two.
Hope that helps,
Samuel Maskell
-------------------------------------
Sent via the XDA Tapatalk App

Related

Developers of ROMs

Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.
Agreed! (This text is just to pass 10 char limit)
Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.
but arnt all these builds just different attempts at getting a working 1.5 build?
Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.
well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!
Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.
momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?
Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave
I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.
Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.
As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.
momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave
I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.
Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.

What's involved in porting a GSM Hero rom to CDMA Hero?

Title pretty much explains it. There are (not many) but more Hero roms on the GSM side of things than the Hero. But obviously, MoDaCo took his rom and switched it over to CDMA for us. So if anyone could help that would be great.
I also have been trying to port Malign's Hero rom for the Dream over to Hero but I'm getting stuck on boot. Loads up but Rosie doesnt seem to want to load. I am trying to do this so I can learn how to port over the good roms since it doesnt seem like many devs are interested in CDMA Hero, which is understandable considering it's price and carrier.
chuckhriczko said:
Title pretty much explains it. There are (not many) but more Hero roms on the GSM side of things than the Hero. But obviously, MoDaCo took his rom and switched it over to CDMA for us. So if anyone could help that would be great.
I also have been trying to port Malign's Hero rom for the Dream over to Hero but I'm getting stuck on boot. Loads up but Rosie doesnt seem to want to load. I am trying to do this so I can learn how to port over the good roms since it doesnt seem like many devs are interested in CDMA Hero, which is understandable considering it's price and carrier.
Click to expand...
Click to collapse
If you need any help with this task, I can help to, I am interested in this also
What's involved? The hand of God.
I'm kidding. Well, not really. I don't really know.
goku14238 said:
If you need any help with this task, I can help to, I am interested in this also
Click to expand...
Click to collapse
Are you saying you know a bit of how to do this or you just want to learn as well?
I don't know the ins and outs of the apks in that ROM, but I do know step 1 - a kernel recompile.
Thankfully, HTC released their kernel changes shortly after the CMDA Hero arrived, which you can download here:
http://developer.htc.com/
You'll need the android SDK and sources for whichever version you want to build - 1.5 should be fully compatible with this kernel, not sure about 1.6, but probably not 2.0.
Unforunately HTC probably won't release their changes for 2.0 until after they dunk Eclair onto the Hero. 2.0 support may work out of the box, may require just a few quick changes, or may be broken entirely, who knows!
[edit] Thinking on this further, a kernel rebuild might not be necessary, but it wouldn't be a bad idea. You may just be able to replace the kernel/boot image in the ROM with the kernel on your Hero (or yanked out of MoDaCo's ROM). No way to know execept to do a thang.
chuckhriczko said:
Are you saying you know a bit of how to do this or you just want to learn as well?
Click to expand...
Click to collapse
I would love to learn as well. can put android hacking, and rom making on my hacking/modding resume

Any Android roms for Wizard?

I have an old Wizard I wanna bring back to life and I wanna know if Android development got far enough for a daily functional Android OS for Wizard?
Wing Linux
Find Wing Linux on sourceforge. It is clearly a work in progress, with slow development. I wouldn't expect anything usable. I mean, most of it works, except voice, which is pretty critical for a phone. But it's an old version of Android, and runs very slowly.
If you want your old Wizard to be a very nice phone, use one of the newer roms in this forum. They are so good that, even though I want a new phone, I am having a hard time justifying it. The wizard with a new rom is fast and powerful. It doesn't have 3G, GPS, or motion sensor, but I've never had a phone with those features so I don't know what I'm missing.
...
Why is there any need to replace TouchFlo with a droid system?
This is totally dull!
Thanks n2rjt. Guess I'll put a WM 6.5 on it instead. I love Android on my Kaiser so much that I was hoping to get it on my Wizard. Oh well.
Does this work?
Follow the link: http://www.androidonhtc.com/wiki/Installing_Android
Dukenukemx said:
Thanks n2rjt. Guess I'll put a WM 6.5 on it instead. I love Android on my Kaiser so much that I was hoping to get it on my Wizard. Oh well.
Click to expand...
Click to collapse
I fully agree! I've been trying to build wing-linux, and I've built dzo's fabulous Froyo that runs on Kaiser, and am trying to gain understanding of how the various sources are laid out, how they are interrelated, how to build them, etc. There is a lot to learn. I think that, unless the key people lose interest in Wizard-era technology, Android can run acceptably well on a Wizard. The Cupcake in wing-linux seems fairly responsive, and I did get my APN to work for EDGE connectivity. But, currently wifi and voice are broken. Apparently they have fixes for these but the main developer has other things of greater interest.
It is, after all, only a hobby.
I might eventually learn enough to build on what they've done, but it is only a hobby for me too, and like you I have a sweet Kaiser (AT&T Tilt) that runs both WM 6.5 and Android 2.2 very well. So Android on WIzard is like a wish but not a big priority. In the meantime, I follow Ham3r and use his ROMs, so that the Wizard remains a very fast and reliable backup phone for me.
Dukenukemx said:
I have an old Wizard I wanna bring back to life and I wanna know if Android development got far enough for a daily functional Android OS for Wizard?
Click to expand...
Click to collapse
Yes, you can do it for Wizard
****:**al.robotfuzz.com*content*android-htc-wizard
Replace **** ---> h t t p & * ----> /

How to?

My daughter has HTC Hero from Sprint running the latest 2.1 version and I wanted to upgrade her phone to 2.2 with all of sprint features like TV etc.
I started to read the forums, looks like there are too many way methods to do things.
Can someone just create a sticky, step by step to newbes on what to do in order to bring the Sprint Hero from 2.1 to 2.2.
which distribution is recommended?
will the upgrade causes a problem with the service?
Get the AOSP Rom, push the sprint apk's using adb.
Its easy..
Sent from my HERO200 using XDA App
First off you have to root your phone (http://forum.xda-developers.com/showthread.php?t=804296), then install a custom recovery (http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1), then flash the ROM .zip in the recovery (http://forum.xda-developers.com/showthread.php?t=782320), then flash a kernal in recovery (http://forum.xda-developers.com/showthread.php?t=756774). This is no easy task since froyo was never released for the hero. good luck and if you have any questions...ask. Once you get that working then you can worry about sprint apps
First you want to do this
http://forum.xda-developers.com/showthread.php?t=694572
That is called rooting your phone, it's a process which sort of "breaks" the security on the phone, which allows you to do alot more things than usual to your phone. The one thing you want the root to do is allow you to flash a custom ROM (Which is basically a new Operating System for your phone).
If you want a nice, fast, and unthemed 2.2 operating system, than you want to flash this rom on your phone.
http://forum.xda-developers.com/showthread.php?t=782320
This is pretty much the OS you want.
Unfortunately you can't do this without a rooted phone. Sprint has left us CDMA users in the dark providing us with no good updates (with the exception of a few bug fixes once in a while), so the Dev's at xda-deelopers have blessed us by creating there own ROM's (Operating Systems) so that we can enjoy the benefits of newer Android Operating Systems.
And if you need a guide to flash a new ROM to your phone, its right here.
http://theunlockr.com/2009/08/27/how-to-load-a-custom-rom-on-your-htc-hero/
Good luck man, it looks overwhelming at first, but it becomes very easy once you get it down.
EDIT ** To answer your question, no it doesn't mess up your Sprint service. In fact, theres a thread somewhere that has a new radio that gives somewhat better signal.
Next time lets learn to read, im not trying to be a **** or nothing but this section is for ANDROID DEVELOPMENT ONLY, i see no dev'ing going on here. Theres seperate sub-forum called "Questions and Answers" just for things like this. Also if you would have search theres tons of stickys for "Noobs". But reason it bothers us the most is theres a sticky up there that says STOP posting non-development crap here and people come do it anyways. Im bothered by it because were all adults here....well most of us....and we have trouble reading.

[Q] Custom ROM for a netbook?

Hey all,
Today I bought an Acer Aspire One D255E netbook which has dual boot Android.
The thing is though that I'm pretty sure its running 1.5 or 1.6 from the looks of the UI (I don't quite know seeing as my HTC phone has HTC Sense) and there is also no Android Market. Is it possible to install a custom ROM based on Honeycomb?
If so would you please be able to give me a step by step walkthrough as I am completely new to rooting/ custom ROMs etc
Thanks
I'm not 100% but I can't imagine it being 1.5 or 1.6, its probably just vanilla android (no proprietary ui). You don't get to see android all by itself very often. As for a custom rom,i don't see why not. You would just need to find a developer with interest in it. Most net books aren't far above this generation of phones, and also would think the file system would be similar if not identical.
I might even go as far as to say start poking around the file system if you can, being a computer it may have root access already (sort of like a dev phone). Hey if you're feeling brave you could try one of the one click root apps like z4 root, see if it works.
i'd also like to say that I'm not telling you to do this, there are risks involved in doing anything unknown and try this only if you are prepared for those possibilities. Do it at your own risk, I'm not responsible if you mess something up while experimenting.
Just some thoughts ;-)
Samsung Fascinate
Frankenclean 2.9.2
Voodoo Frankenkernel
Jumba's Neon BT 6Lock(beta) theme
Sent from XDA Premium App

Categories

Resources