This might be asking a bit much from the dev's, but is there any way to including compatibility for the DIAM500 (Sprint Touch Diamond) and RAPH800 (Sprint Touch Diamond Pro)? I would think the Vogue would provide a good base starting point for the Diamond since it's the same chipset, but in addition it would need Wi-Fi, g-sensor, and higher resolution. Still what has been done so far here would be a good base platform to build from.
I have been contributing to the Diamond thread and would be working closely with the devs here to ensure there isn't anymore repeat work being done between the ports. I own a DIAM500 so I can test any ROM and kernel updates closely with you guys.
The CDMA Diamond has been lagging behind the GSM greatly. Help me bring it at least up to Vogue levels! Where we currently stand on CDMA builds is located at Connect-UTB.
I have a cdma diamond as well, and as much as I wish there was a magic fix, I don't think the vogue port is our answer to getting android working on the diam500. The hardware isn't the same, and much work has been done already in porting to the diam100 etc, so I think we just need some good developers to iron out the kinks and get the diam500 working with that port as well.
I don't know if this thread is going to get moved back into the diamond subforum, but regardless, a thread like this might serve as a good starting off point for diam500 users/developers, since we are such a small subset of the diamond user base.
Zenulator, who i believe is/was a dev for the vogue made an offer to help with the diam500 port if he could get his hands on a diam500, so that may be one lead we have.
MrPippy made progress before. He got the cdma radio initialized (voice + text messaging), and fixed the colour issues we have by using mtype 2040. Whether using this mtype is the correct method in the long run, I don't know. But he has gotten farther than most of us.
Using semi-recent builds with their included (not specially compiled for diam500) kernels, I have been able to get android to run on my diam500, albeit without any radio support and with incorrect colours. However, 3d acceleration was working, which never worked in previous builds. I don't think we are really that far off; we just need to fix a few somewhat major problems to get us a lot closer to where the gsm guys are.
I have a spare laptop I've set up with ubuntu and the tools necessary to compile the linux kernel, so I would be happy to help with testing or anything else that would help this project.
1.) please don't post Diamond stuff in the Vogue forum, remember this is more than just a vogue android forum, there's regular vogue users here as well.
2.) Hit me up privately and I'll see if I can help.
I have one thing to say about connect-utb and diamond and raphael. I was offered a cdma diamond but turned it down. Most of those packages up at connect-utb are my xrom/donut builds and the basefiles from vogue-android with exception of the diamond/raphael specific kernels and startup.txt. So I'm not going to do any work on thats side. Frankly it's irritating when you go to a site and see "New donut package by ......" and I look inside and it's one of my donut builds. Same build.prop and everything. Still set for qvga. With no credit to me or the hard work at vogue-android. I talked to one of the guys that put out a diamond/raphael package and he gave credit afterwards but the next thing I see is another package with a different name and a different donut build of mine. So if thats how they deal with the work of others then they are on their own. I try to give credit each and every chance I have. Even if it's an edit of one line in a file. I've repeatedly pm'd Edvard about this and I get no response. I don't think I'm being unreasonable I just want credit to go to the right people and not to some guy that zips together a bundle of other peoples work.
So true and sooo frustrating when that happens,
zenulator said:
I have one thing to say about connect-utb and diamond and raphael. I was offered a cdma diamond but turned it down. Most of those packages up at connect-utb are my xrom/donut builds and the basefiles from vogue-android with exception of the diamond/raphael specific kernels and startup.txt. So I'm not going to do any work on thats side. Frankly it's irritating when you go to a site and see "New donut package by ......" and I look inside and it's one of my donut builds. Same build.prop and everything. Still set for qvga. With no credit to me or the hard work at vogue-android. I talked to one of the guys that put out a diamond/raphael package and he gave credit afterwards but the next thing I see is another package with a different name and a different donut build of mine. So if thats how they deal with the work of others then they are on their own. I try to give credit each and every chance I have. Even if it's an edit of one line in a file.
Click to expand...
Click to collapse
I've even seen Zen turn down donations and tells people to send them off to the ones that started before him and gives them credit time and time again. I think he downplays a lot of his own work.
Yeah zen is definitely not your typical dev. I'm sorry he feels this way, but it is warranted. I was hoping to mainly strike up a conversation on if it was possible to use a Vogue build as a basis to build a Diamond. But it sounds more feasible to get a good dev on board to help us iron out the remaining issues.
Gleng did a very good job laying out where we currently stand. I sent both him and mssmison a PM. We'll see where it goes from here!
Related
Hey!
As i've previously mentioned here once (I think), i started a small forum where I tried to gather all the setups for running Android on various HTC models. Now that the HTC G1 (Dream) is soon released, we will will get some very interesting challenges while trying to build Android ROM's, etc..
This forum is great, but its also very big. Thought that it might be a good idea to have our android resources on a separate forum?
Anyways, thought i could register a domain and such, but for now the forum is at http://www.connect-utb.com/htcandroid
Some of you are there already! Hopefully, with the experienced user base we have here, we can get Android ROMS and whatnot for our HTC models, as the HTC Dream looks rather poor. (Although better devices will surely come in the future).
you must be joking. Android is a total OS unlike apps that we see all over which are portable among HTC devices. It takes months alone just to get Android as it is today for the kaiser. Mostly everything for WM can be ported among other devices which some exceptions to nontouch devices. It'll be a long time until you see Android ported over to more devices than now. My suggestion would be to use a device that's got android projects already in progress or at your nearest convenience to buy a device with android on it.
Think we misunderstand each other, but you dont believe that if we can extract the android ROM from the HTC Dream, and modify and install it on lets say, the Kaiser?
You can always try before saying that it isn't going to work.
I will track this post because i'm very curious by the Android OS.
I get it...and completely understand what this is about...it's HTC...which means theoretically we should be able to at least somewhat get it working...I've started a wizard thread on your new forum in hopes that any information or progress getting it ported over gets posted all in one location for easy access....kudo's for thinking ahead as I dont think android is going anywhere soon and while this forum is very useful it's mostly for winmo devices....nothing wrong with speading the wings a lil bit and branching out...
looking forward to the press conference!!
I would say we should be able to get Android to run on the OS level of our devices, but it will probably need a bit of modifying. However, since it's open source I'm hoping the modifying will be a lot easier because of this.
Hey,
I was just on HTC homepage ( htc.com ), where the G1 is shown.
They printed the specs, which are very similar to the diamond
Same chipset, same rom size, same ram size,...
SO I think, it would be ( maybe easily?) possible to port android to the diamond
greets doena
WatskeBart said:
I will track this post because i'm very curious by the Android OS.
Click to expand...
Click to collapse
Same here!
If my memory does not fail, I remember that one of the first peaks at Android was being run in a Blue Angel. So, I guess there is a big chance that we might in fact be able to see Android running on more than one device (of course, you will have more or less features depending on the device's capabilities and hardware limitations, namely apps that work with an accelerometer, etc).
Maybe, the development should be worth following because as much as I don't want to believe it, my device (Blue Angel) will only trick death for so long (by death I mean not being able to move to newer versions of WM) and we will need a way to pass the time .
HTC Touch Vogue in progress of being ported
Hey don't forget about the senior member "DZO" that started ANDROID porting to HTC Vogue and it is Successful
This is his direct link to the files : http://cs-alb-pc3.massey.ac.nz/vogue
And here is the link to the posting: http://forum.xda-developers.com/showthread.php?t=382265
I think he did a GREAT job porting Android. I am running Android 0.9 with most of the featuress except installing programs but only because he is the only one that does that. So, he needs help! I am sure... Plus, on this site people are cheeping in for HTC Diamond so he can work on that too...
Here is the link: http://www.myhtcphone.com
So, if you want something done we should start by contributing either money, or programming support! I wish I knew how to program this
ahhhh I wish I would have fully functional Android on my HTC
Thanks for the support! The forums are slightly active now!
Hopefully, we will be able to get Android running more or less flawless soon! As pointed out, its possible!
he he nice link, it seems that there are allready htc devices running with android.
just wondering, is it possible to have dual boot in one device ?
hmmm, seems to have no desktop syncing.. this may be a huge set back for anyone trying to get androig running on another HTC device.
crescentsaber said:
just wondering, is it possible to have dual boot in one device ?
Click to expand...
Click to collapse
well currently (or in the case of the vogue) android is being booted via haret (a linux bootloaded) running on top of windows mobile.. so i guess its already kind of dual boot
For now, Android has to be run from within Windows Mobile, so no true dual boot yet
Already started
Hey you guys might want to check out the following links. Over at PPC Geeks they already have a thread going:
http://forum.ppcgeeks.com/showthread.php?t=23244
Also if you want to download the current Android cab for HTC go to:
http://www.myhtcphone.com/
doena said:
Hey,
I was just on HTC homepage ( htc.com ), where the G1 is shown.
They printed the specs, which are very similar to the diamond
Same chipset, same rom size, same ram size,...
SO I think, it would be ( maybe easily?) possible to port android to the diamond
greets doena
Click to expand...
Click to collapse
Diamond doesnt have QWERTY keyboard, so i think it could be on Touch Pro instead
Someone ported Android for BlueAngel?
Please can someone tell me if Android is already running in BlueAngel? If there is a way show me how. Thanks Man!!!
Maybe I'm mistaken, but wasn't Android made so that it can run on a wide range of devices. I, for one, can't wait till its ported to samsung omnia. Damn, that would be good!
@Coldheat,
What does the cab file do? Its an OS, so cab file??
Hello all, after toying arround a little bit with themes and everything definatly have become really confident in modification of the G1 file system. I am currently in school for Computer Science with East Stroudsburg Universty figured that I would lend my hand into rom development. Have been reading alot on android development toolkits and stuff and have recomplied some other ones to support ext3 and you guys are right much more reliable. Seems like there is already great 1.5 roms that are complete and great i don't know how that I would be able to improve on them other then putting on some of the HTC programs. The Ion is a great build trying to copy some things from Hero to Ion and not playing well going to try and tweak Hero maybe but need some help like where to find more information about possibly getting Bluetooth working I think it may just be as simple as changing a device ID. Did make Hero a little bit but there is the watermark thing to worry about so that i won't make available yet and especially is still glitchy and no bluetooth. Just looking for direction on what can be done further. Trying to take place of haykuro and see if can lend a helping hend although I know I won't be able to fill his shoes and all. But I also wanted to take a crack on Hero build if anyone might be able to give me a lending hand and point the right direction I want to try and get that running with the Rosie UI and Bluetooth but need some files and help. Anything would be greatly appreciated can pm me anytime. Looking forward to being a biger contributer here. So just any points towards rom development would be appreciated again. Sorry though if this is the wrong section.
The thing i like most about hero beta 4 is the exchange support. i'd love to see the exchange support on the ion rom with all its speed goodness.
I don't think any of us would be able to help you with files for Hero, and the Rosie UI. If you manage to get a Hero build with the Rosie UI somehow and then make it usable without any traceable files then that should be a start for making a name for yourself, but as you can see getting a Hero rom with the Rosie UI would be quite difficult.
This great if you take a look at the "He didnt do it! I did!" thread you can see the people who helped haykuro. I would say to try to get in contact with these people.
I support you all the way.
haykuro
Why dont you try contacting haykuro himself. Though I would be surprized if he was whilling to give up that info its worth a shot.
Yeh The traceable data in Hero is a big problem and I don't think that there is one currently without it yet. I understand how it is I am just unsure of how to get arround it. I don't have the Rosie data and that would be a future thing anyway. Looking over code from google there is alot to understand and I have a basic concept of most of it just need to know how that they interact with each other a little better. As far as exchange support that uses alot of HTCs stuff so on a Ion build would be hard since you would need to have the HTC binaries instead which is a little difficult.
Hi all, I'm new to the Shift scene. After having read the whole 'Shift>Shift' subforum I can see that activity has petered off somewhat since this time last year. One page of threads used to last about half a month, now one page of threads gets us well over a month (I hope you can understand what I' trying to explain there). I plan on bringing together all the ROMs, Radios, Guides, etc into one thread that can hopefully be stickied like in the Xperia X1 forum (http://forum.xda-developers.com/showthread.php?t=477801), because at the moment there doesnt seem to be anything like that here.
1)So out of the original members of the Shift project+others (names below):
a) Who still has their shift.
b) Who is still actively looking in to ways to improve it. I.E. at least once a week.
Looking on http://forum.xda-developers.com/showthread.php?t=375898 at post #18, it looks like the core members were:
ltxda
Olipro
Cmonex
PK
And some good contributors:
Thaihugo
Pawel062
Saiweb
2)Who were actually the official members of the Shift project?
3)Who else was involved in the Shift project?
4)What were the original goals and how many of the goals have been 'scored'? See below
5)Whats are the outstanding goals, i.e. full screen and SD Card in WM ?
6)With regards to 'full screen and SD Card in WM' how far did you get, and what ultimately stumped you?
7)How many Shifts did you buy with the donated money and whose got them now?
If there is anybody with a Shift purchased with the donation money who is not using it anymore, perhaps you could donate it too me so I can continue to try and unlock any more secrets this device holds.
I am now going to start reading the whole 'Shift>Shift upgrading etc.' sub forum starting at page 15 and working to today.
If anyone wants to help me correlate all the ROMs, Radios, Guides etc, any links would be helpful.
8)Does anybody know how many different ROMs and radios there are for the Shift?
Like I say im going to read up now but if someone already knows that would be helpful.
Coming back to question 4, I will give what I think were the goals. Please feel free to add or subtract goals :
a) Get SD card working in WM - Not done
b) Get WM fullscreen - Not done (Limit of MSM7200 is VGA)
c) Get the device HardSPL'd - Done
d) Create custom ROMs - Done
d) Get GPS working in WM side - Done
e) Get GPS working in Vista side - Done
f) See if HDD is upgradable - Done (it is)
g) See if RAM is upgradable - Done (it isnt upgradable)
h) Get mic working on WM - Done
i) Get wifi working in WM - not done
j) Get bluetooth working in WM - not done
The 'Shift Project' ground to a halt when newer, shinier toys came along.
I can't wait to see this project being active again. Right, there are hundreds of devices out there but Shift is still the only one which combines
windows (7/vista/xp) + wm + phone.
Honestly, I would try to answer something not too bitter. Let's put it mildly: The shift project is (has?) probably not working (ed?) anymore (way?) for the shift. They sure got the money, but never delivered. On the other side, any legitimate group trying to help was dead on arrival because of this. Every cluster of developer failed because the shift project was magicaly reapiring to promess a new development.
I would consider this "projects" as a request for a hardspl adaptation for a device. Anything else would have need some other efforts. I think we can be happy with the current possibilities, and move along with it.
Ahhh I see, well lets wait to see what Itxda and comnex have to say, maybe we can get this ol' baby fired up again!
It would just be nice to know where they got with thee SD card and fullscreen WM issue.
Dont give up , keep on trying to solve the sd card , bluetooth and the rest that is not done yet . U can do it . Just try n try again , u know u can do it , concentrate ...
thaihugo said:
Honestly, I would try to answer something not too bitter. Let's put it mildly: The shift project is (has?) probably not working (ed?) anymore (way?) for the shift. They sure got the money, but never delivered. On the other side, any legitimate group trying to help was dead on arrival because of this. Every cluster of developer failed because the shift project was magicaly reapiring to promess a new development.
I would consider this "projects" as a request for a hardspl adaptation for a device. Anything else would have need some other efforts. I think we can be happy with the current possibilities, and move along with it.
Click to expand...
Click to collapse
1. money was spent on getting device, so it's not like we used it for our living or whatever
2. I don't understand some words, maybe typos? "reapiring", "promess"? please can you rephrase? thanks a lot.
2b. as for not delivering, I would disagree. we got a lot done, even if some of it was leaked by certain members before our group's release also, I can't vouch for what others said, but I never promised that BT or wifi even has a good chance for working.
3. anything else than the hardspl/radio/phone stuff is more work for sure. for example the WVGA mode enabling in ARM part works only half so far.
vinokirk said:
1)So out of the original members of the Shift project+others (names below):
a) Who still has their shift.
b) Who is still actively looking in to ways to improve it. I.E. at least once a week.
Looking on http://forum.xda-developers.com/showthread.php?t=375898 at post #18, it looks like the core members were:
ltxda
Olipro
Cmonex
PK
And some good contributors:
Thaihugo
Pawel062
Saiweb
2)Who were actually the official members of the Shift project?
3)Who else was involved in the Shift project?
4)What were the original goals and how many of the goals have been 'scored'? See below
5)Whats are the outstanding goals, i.e. full screen and SD Card in WM ?
6)With regards to 'full screen and SD Card in WM' how far did you get, and what ultimately stumped you?
7)How many Shifts did you buy with the donated money and whose got them now?
If there is anybody with a Shift purchased with the donation money who is not using it anymore, perhaps you could donate it too me so I can continue to try and unlock any more secrets this device holds.
I am now going to start reading the whole 'Shift>Shift upgrading etc.' sub forum starting at page 15 and working to today.
If anyone wants to help me correlate all the ROMs, Radios, Guides etc, any links would be helpful.
8)Does anybody know how many different ROMs and radios there are for the Shift?
Like I say im going to read up now but if someone already knows that would be helpful.
Coming back to question 4, I will give what I think were the goals. Please feel free to add or subtract goals :
a) Get SD card working in WM - Not done
b) Get WM fullscreen - Not done (Limit of MSM7200 is VGA)
c) Get the device HardSPL'd - Done
d) Create custom ROMs - Done
d) Get GPS working in WM side - Done
e) Get GPS working in Vista side - Done
f) See if HDD is upgradable - Done (it is)
g) See if RAM is upgradable - Done (it isnt upgradable)
h) Get mic working on WM - Done
i) Get wifi working in WM - not done
j) Get bluetooth working in WM - not done
Click to expand...
Click to collapse
I got your PM so I'm replying here now
1)
a) I have mine. love it! as for the others, see below
b) well, not once a week currently... :S
c) PK is pawel062. but he left windows mobile scene for iphone :cries: (he never got a shift, tho)
2) you got the "official" members right other than that
3) you got that right too
4) see project thread, but a quick sumup, HardSPL, radio unlocking, phone funct. unlocking, GPS, cooked ROMs, and the low level/hw hacks (WVGA, SD... the others only if possible). I guess other than hw hacks that's been done for the most part
5) yes, those two
6) WVGA half works, I can enable it, picture no good yet. I found SD was disabled in the bootloader where I saw evidence for use of it, no further news right now
7) Shifts: I have one from the project, Olipro too, ltxda got one, which he wanted to send to PK to cook for it but he left the project. I do not know what happened to that shift, as ltxda got distracted by the death of a family member. I'll ask him what's up with that. there is no other money left in the Shift account.
7b) as for sending it to you (ltxda's device), I'd like to know what sort of experience you got, what sort of goals you'd like to try and achieve
by experience I mean: coding experience (and what languages), low level driver experience, reverse engineering experience, etc... but then, I'd like to first know what goals you have in mind as well
8) I have a few radios, ROMs, if you mean stock ones, then not terribly many.
cmonex said:
I got your PM so I'm replying here now
6) WVGA half works, I can enable it, picture no good yet. I found SD was disabled in the bootloader where I saw evidence for use of it, no further news right now
Click to expand...
Click to collapse
cmonex
what about BT and WiFi? I was able to check the virtual COM ports for them and tried to enable them and noticed something was blocking it. Were they too disabled at the bootloader?
Thanks
--Ram--
Vinokirk sweet thnx for stirring up this part of the community.
Our Shift is a 1 off. Keep it, caress it, nurish it.
After the Chinese debacle (Someone having a too large ego and hoaxing about SD) nothing much happened above the surface.
My idea would be that everyone start sharing his findings for making SD , headset mike, and BT work (in respective order)
Like CMonex staed that the WM bootloader disables SD it seems. This seems new info and might spur others to action.
Shift project has delivered beyond expectation in the early days.
cmonex said:
I got your PM so I'm replying here now
Click to expand...
Click to collapse
cmonex! Many many thanks for your reply; your information is very valuable to me!
Yes I was devastated reading about Itxdas story, it was truly a tragedy and my heart goes out to him.
Personally my goals (in order) are:
1) SD card
2)'Personal calling' over BT or wired headset.
3) WVGA screen in WinMo
4) Cooking everything into a ROM
But I am very much a community person. If anyone has an idea they would like to see developed, I would try my darndest to make their wish come true!
I have some basic grounding in C++, Pascal (he he he), and Java. I have a friend and brother-in-law who are AMAZING programmers in many languages, so they will be my 'goto guys'.
I have in the past re-written a couple of drivers in windows, but that was a while ago and they weren't low level drivers.
I haven't officially reverse engineered something before, but I have taken loads of things apart to fix, so in a way I have been taking say a phone apart to find out what the problem is.
I have A-levels in Maths and Electronics (they are the UKs 16-18 yr old exams), but nothing at degree level.
I do however have experience with cooking. I have made a couple of my own ROMs for my Xperia X1.
But the main thing is, I have a passion for things like this, as you can see im asking a lot of questions, and posting in a few threads!! So with your guidance I'm sure I could deliver at least something! This would be a great first step into your world and I am really looking forward to getting the opportunity to do so
cmonex said:
2b. as for not delivering, I would disagree. we got a lot done, even if some of it was leaked by certain members before our group's release
Click to expand...
Click to collapse
As far as I know, olipro and you weren't part of the shift project first, and they called you to the rescue. So again, I thing the shift project AFAIK, never released a think. They "rebranded" you as shift project because they didn't have a think to provide.
Also, I don't see the leaks you're talking about. Was the group about to release something? Do you mean your radio? Has it anything modified from a 1.27 radio? because otherwse, I think we are all doing the same job here, taking existing roms, modifyng files and releasing them. The trick is to find the right files, and I don't see where any work here is stealing or below somebody elses work. I don't think anybody took a rom from the shift project, modified it and claimed it as it's own.
lucid said:
Vinokirk sweet thnx for stirring up this part of the community.
Our Shift is a 1 off. Keep it, caress it, nurish it.
After the Chinese debacle (Someone having a too large ego and hoaxing about SD) nothing much happened above the surface.
My idea would be that everyone start sharing his findings for making SD , headset mike, and BT work (in respective order)
Like CMonex staed that the WM bootloader disables SD it seems. This seems new info and might spur others to action.
Shift project has delivered beyond expectation in the early days.
Click to expand...
Click to collapse
1) uh yeah I'm afraid it is going to be a one-off from HTC :'( and where is Thoth?? (Athena2) gee HTC really needs to get back on track for making the best usable devices
2) wish those chinese guys had shown more. this way it does seem a hoax.
vinokirk said:
cmonex! Many many thanks for your reply; your information is very valuable to me!
Yes I was devastated reading about Itxdas story, it was truly a tragedy and my heart goes out to him.
Personally my goals (in order) are:
1) SD card
2)'Personal calling' over BT or wired headset.
3) WVGA screen in WinMo
4) Cooking everything into a ROM
But I am very much a community person. If anyone has an idea they would like to see developed, I would try my darndest to make their wish come true!
I have some basic grounding in C++, Pascal (he he he), and Java. I have a friend and brother-in-law who are AMAZING programmers in many languages, so they will be my 'goto guys'.
I have in the past re-written a couple of drivers in windows, but that was a while ago and they weren't low level drivers.
I haven't officially reverse engineered something before, but I have taken loads of things apart to fix, so in a way I have been taking say a phone apart to find out what the problem is.
I have A-levels in Maths and Electronics (they are the UKs 16-18 yr old exams), but nothing at degree level.
I do however have experience with cooking. I have made a couple of my own ROMs for my Xperia X1.
But the main thing is, I have a passion for things like this, as you can see im asking a lot of questions, and posting in a few threads!! So with your guidance I'm sure I could deliver at least something! This would be a great first step into your world and I am really looking forward to getting the opportunity to do so
Click to expand...
Click to collapse
I replied to your PM again the public part of that is, I've talked to ltxda about sending the Shift to you. he'll get back to me on that soon.
saiweb said:
cmonex
what about BT and WiFi? I was able to check the virtual COM ports for them and tried to enable them and noticed something was blocking it. Were they too disabled at the bootloader?
Thanks
--Ram--
Click to expand...
Click to collapse
it needs more than virtual COM ports.
thaihugo said:
As far as I know, olipro and you weren't part of the shift project first, and they called you to the rescue. So again, I thing the shift project AFAIK, never released a think. They "rebranded" you as shift project because they didn't have a think to provide.
Also, I don't see the leaks you're talking about. Was the group about to release something? Do you mean your radio? Has it anything modified from a 1.27 radio? because otherwse, I think we are all doing the same job here, taking existing roms, modifyng files and releasing them. The trick is to find the right files, and I don't see where any work here is stealing or below somebody elses work. I don't think anybody took a rom from the shift project, modified it and claimed it as it's own.
Click to expand...
Click to collapse
nono, of course I didn't mean anything like claiming a rom
Any progress / news ?
Not yet, I'm waiting to hear from ltxda. As soon as I get his Shift project Shift ill be able to start cooking a new ROM. And with the hep of cmonex and others, hopefully crack someof the other issues.
vinokirk said:
Not yet, I'm waiting to hear from ltxda. As soon as I get his Shift project Shift ill be able to start cooking a new ROM. And with the hep of cmonex and others, hopefully crack someof the other issues.
Click to expand...
Click to collapse
cant wait
some news???
I'm new to Android but not new to Linux and wondering what is necessary to get these ROMs (and others) working on the CDMA Hero. What are the major differences, proprietary drivers? Kernel modules?
New Cyanogen ROM, just released
http://forum.xda-developers.com/showthread.php?t=567610
In other words, what's stopping us from running these ROM's right along with G1/Dream users?
I'm curious also... would love to try his roms...
Since Android 1.6 was supposed to add CDMA support I would think they should work as well as 2.0 unless the developers have taken the cdma support out of the code in their roms to shrink the size to fit on the G1's.
If I had a Hero I would be giving it a try most likely. I might try picking one up this week since Best Buy has them down to $99. I just wish it had a keyboard.
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
herzzreh said:
I'll try when I get home from work.
On a side note, even if this rom doesn't work, I should be able to boot into the recovery rom no matter what... riiiiiiight?
Click to expand...
Click to collapse
Correct! The recovery image isn't touched by normal ROMS typically.
I'm tempted. Can this be applied right over the MoDaCo ROM?
I have tried a couple things with these. I tried flashing it outright. Wouldnt get past the initial htc boot screen. So I replaced the kernel in the boot.img of Cyans rom with ours, that still didnt work. Then I tried replacing the entire boot.img and still no boot working. I think Donut uses the 2.6.29 kernel or whatever it is. Ours is .27 so I think we would need to recompile the .29 kernel and pray our drivers work with it. Please, someone else try it too and see if they can get it working. I would love you forever if you could. If not, we will just have to wait until HTC gets us Eclair.
Thanks
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
5tr4t4 said:
Thanks for trying this, chuckhriczko and others.
I'm mainly coming at this from the pure Linux point of view: shouldn't these ROM's run anywhere (barring proprietary bits)? Shouldn't we be able to "share and share alike" between platforms, Hero/Dream/G1/whatever? If there is a chip architecture difference, fine then we need a recompiled kernel. Obviously there is also the question of firmware, but that's a given on all phones.
Otherwise, shouldn't these ROM's be fairly universal? Or if they are not, I'd like to know what makes ROM building such a unique endeavor for each phone.
Click to expand...
Click to collapse
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
thecodemonk said:
I believe it's mostly the proprietary drivers for some of the hardware as well as needing a kernel recompile...once HTC releases the CDMA kernel, I'm sure we'll see a lot more (that or some genius will reverse engineer it...either way!)
The other thing to consider is that most of these ROMs are based on something...they take what's existing and tweak the heck out of it (I'm willing to bet that the vast majority of ROMs can trace their roots back to an official vendor image at some point).
I'm actually trying to setup a build environment and poke around but I'm starting from ground zero on the mobile platform side of things so I wouldn't hold out for me (and finding a Java 1.5 runtime is surprisingly hard these days ).
I'm noticing that we're seeing more and more ROM's pop up (primarily gutted ROMs focussed on eeking more speed as opposed to MoDaCo who went for more features).
Click to expand...
Click to collapse
What OS are you using? If your using a Debian based linux then you can get it from the Debian Lenny repositories. One word about this though, it killed my existing Java 1.6 so I had to reinstall it when I needed it. Otherwise that works.
And yeah, we are primarily doing gutted roms because that is all we know up to this point. It is very difficult to find help from those who know all about recompiling a kernel and things like that. Like I said, I couldnt get Cyanogen to even boot on my phone but obviously, it should at the very least do that. But only one dev on these forums ever helped me with my CDMA roms and that was Mlign from the Dream forums. Everyone else (understandably busy) ignored me. Im not saying anything bad about them but it's just harder for people to learn. Patience will give us what we desire though.
vendor tree for cyanogen heroc
im a noob and dont know how to build it but its here:
http://github.com/darchstar/vendor_cyanogen_heroc
Thread gravedigging much?
yes haha i want cyanogen on my hero lol
ok so we are all aware of all the various android builds out there for different phones. some with sense, some stock. all the chefs have their own basic formula for the perfect rom when they try to cook them for us. now most builds we apply to our phones are mod's of builds for other phones. After working with so many builds and liking certain features of each, but only available to each, i found myself asking the following question.
Companies like htc, etc. are assigned to build a certain phone with a certain android build with certain features activated/deactivated (ex. some builds have tethering, but tmobile said to cut tethering option out of g2. or some builds have a 2g/3g on off option where as others don't) this must mean that there is a general android build they start with that has all features and they just decide to keep/omit things they want or things carriers don't want. (or add some version of sense ui to it or touchwiz). My question is, is there a general ultimate android build that is available that has every feature there? i'm not a developer so i've never cooked a rom, but it would be awesome to have one build with everything and a simple way for users to decide which options they want or to omit. i know it sounds simple in theory and will never be that easy. but it would be awesome to have one general build with all options and can choose which ones i want to use or not to use vs. a developer selecting them for me.
this is a major problem with many winmo builds i've worked with compared to android builds, but its still something that bugs me when i try a rom and say damn i wish there was a 2g/3g on off in the network options vs having to dig for gsm/wcdma options. like i said in theory it sound easy and i'm sure its not, thats why i give all the chefs credit. but just throwing it out there in case something were to exist like that. thanks
I think I understand what you mean.
I've played with the Android SDK and the BASE 2.2 (what we know as Froyo) has all you mention (tethering etc), but looks kinda bland, this may be that I'm now so used to Sense and it's niceties that anything less than Sense to me just looks wrong.
If you want to see Android as Google intended for us all to use just download the SDK and start a 2.2 session with no modifications and you'll see the differences that carriers and the cooks here do, it's amazing work.
Also, almost all cooks here in XDA will try and give you access to everything the phone itself can do, that's part of the fun of running a rooted OS.
thanks for the tip about trying out the sdk Reno, i'm gonna check it out this weekend. Don't get me wrong, i love all the fun of flashing and its an addiction since 2007 on my HTC 8525/G1/HD2 lol. and i give mad props to all the chefs, god knows if i started messing with code, my phone would be a brick an hour later lol. Android chefs are really good and don't tweak much like winmo chefs do at times which i like. so many builds for winmo you'll find are scraped down to bare minimum because the chefs wanted a bare rom that gave u the "most space and fastest speed" which all went to hell once u install crap you want on it anyway, but half of the features and options have been deleted! thank God android chefs are good with keeping things there.
woohoo sdk fun friday night! will i become a chef? do chefs need to wear the silly hat?
I'll be perfectly blunt you'll need more than just the SDK to get a build made. I only downloaded it out of pure curiosity. You'll hopefully see in the attachments exactly what default Froyo looks like and realise even more what a godsend these guys here are.
I would honestly love to make my own build (more for my own fun and use than for general consumption) but I realise after many hours of reading and research that it's ridiculously hard work and these guys deserve every penny we can afford to donate for their toil.
Going back to the original point though: I think to create one overarching build that upon install you could pick: stock/sense/launcherpro or whatever other flavour there is available out there would actually be impossible. The look of the build is so deeply embedded in the build itself and requires so many different parts of the operating system itself to be changed you would need several copies of each file with the different variations for each look/style you'd end up with HUGE download sizes and it would be more difficult to keep up with when there is an update.
As things stand now, I know I could never drop my Sense builds, I love hastarins kernel tree, and I have my favourite small group of cooks that I follow, and that helps me limit what builds I download and test. Having a couple of small spare memory cards helps and only cost me £20 or so to give me that choice.
Reno i feel that you are correct. i couldn't resist and went to download the SDK after replying to your post. its still downloading a bunch of things and as i read the android developer page i'm enticed to hit the cancel button! I think i'll just go back to picturing the chefs as the magicians and let them entertain, instead of being the guy who tries to figure out all the tricks lol.