Related
Has anyone got Android 2.0 working on the hero? Seems "Steve Kondik" has got it running on his G1.
http://source.android.com/
the community there did it, among others also cyanogen ;-) and they ported it to g1.
You MIGHT have read about it, but:
1: The code ported to AOSP isn't complete yet, and there are a few things which still don't work, like calendar.
2: ROMs running on the G1 were either ported from droid/sholes or partly, from the SDK.
Than again, the G1 has a 2.6.29 kernel, which the Hero doesn't.
A.
and HTC has announced that there will be an 2.0 update for the HERO, but when it will be released only they know...
> darn connection; dbl post <
no1 is currently working on 2.6.29 for hero. isnt it? tht means we will have to wait for the official release.
dying4004 said:
no1 is currently working on 2.6.29 for hero. isnt it? tht means we will have to wait for the official release.
Click to expand...
Click to collapse
Im learning about this stuff as fast as I can but HTC will probably release it before I learn enough to port it. That said, I'm trying to become an uberdev
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
So it's officially out.
Would it be too optimistic to wait to see a port of ics for archos gen 8? Apparently cyanogen team is waiting to get their hands on the source code and presumably they will build new cyanogenmod version very soon after that. Well, sooner or later but I'm sure they will make it.
Is it possible that the system requirements would be too rough for archos gen8? Now that we already have some kind of cyanogen ported would it be easier to make it again with cyanogenmod based on ics?
Not sure if my questions make any sense because I'm not very familiar with developing stuff. I just like to follow instructions and hack everything I own!
I think we will have ICS on our Gen8 devices, but i will be a experimental port, just like the cyanogen port (2.3.3) now...
I hope this community wont die!
Greets,
Lenn
These are the requirements for Salsa Rom:
Android 4.0+ or Android 2.3.3+
LeeDroid Tweaks
SuperSU
Root Wifi Tether App
Wifi Key Recovery
AWD.Launcher in Android 2.3.3+ Build
Apex Launcher in Android 4.0+ Build
All Google Inc Apps (Except Chrome For Android 2.3.3+ Build)
Development Sites:
GitHub Repo
Rom Website
Development Forum Thread
Remember this is a development thread not a coming soon thread like I made last time (Sorry Mods won't happen again ) this means that this rom is not coming out anytime soon. But rather is a place for the developers to talk.
Nathan, check your pm please.
Save the Drama for your Mama with Tapatalk 2
Moved to general until there's a rom base, from which to develop. Until then it's not development, it's hoping to develop.
Why I Created This Thread and belive that it is considered a development thread!
I created it so that developers can ask other developers if they aprove of certain changes. So would anyone like to help?
Just wanted to say that,
I added to branchs to the Git Server one for the ICS Build and one for the GingerBread Build
nathansuchy said:
I added to branchs to the Git Server one for the ICS Build and one for the GingerBread Build
Click to expand...
Click to collapse
For GSM as well?
Yep it will
pransh said:
For GSM as well?
Click to expand...
Click to collapse
It will work on every phone through a common kernel that is changed by the setup script for the Rom and changes to a kernel optimized for the device it sets up carrier, kernel, device type, network type, etc as well as standard setup. But I will only be developing the script and the kernel for HTC EVO 3D CDMA VM the rest will have to be designed by developers who have the phone but I'm am still doing my research on how to do this. The project is on GitHub!
So what devs are a part of this "project"? Because honestly all I see is you and nothing posted in github. So what exactly are you trying to do?
Just curious
Get people to develop it but stoped becaused found something i know how ti do. I started my own forums android-developers.forumatic.com and please mods this is just me saying that im too busy with other project not an advert
Sent from my HTCEVOV4G using Tapatalk 2
Any developers out there having HTC desire v and interested in building roms for our device, post here.. I have been helping in development of galaxy mini, and a member of team jellaxy as well..
I am currently not having free time so cannot build one! If anyone else interested post in this thread, I will try out when I have free time in a couple of weeks
Sent from my HTC Desire V using xda app-developers app
i create this thread http://forum.xda-developers.com/showthread.php?t=2007243 this is my first ROM, but i wont to build for our Desire V CM10 or AOSP
AKA_noodle said:
i create this thread http://forum.xda-developers.com/showthread.php?t=2007243 this is my first ROM, but i wont to build for our Desire V CM10 or AOSP
Click to expand...
Click to collapse
That's great @AKA_Noodle. I used to own the Galaxy i9003 and have experience in testing ROMs, customizing, boat ware removal etc. for 10 months. I have just bought a Desire V yesterday and this is my first HTC. I am getting to know the difference.
I have followed your post and am going to ROOT the phone in a couple of days. I am giving my stock 7 days for the just in case hardware issues with my handset. Post that I will unlock the bootloader and free my device. I am ready for testing and development.
And by the way,
Congratulations to all. We finally have a dedicated thread for our phone.
Thanks @AKA_Noodle, i use the European Rom, great
Guys,
I don't own this device, but I'm interested in developing for it.
I believe I could try to port a ROM or two from the desire X to this device, if anyone would test it.
The only thing I need to know is: do you guys have android 4.0.4 or 4.0.3?
Sent from my awesome fridge
4.0.3
Rew64 said:
4.0.3
Click to expand...
Click to collapse
Thanks. I hope that little difference doesn't affect the ROM.
I don't have time in this week, but I'll try to get you guys a ROM next week.
Sent from my awesome fridge
I'm interested with HTC Desire V Rom Development. And I will first make CM10, then MIUI, etc. I'm following the tutorials at XDA.
Finally i have device tree ready for HTC DESIRE V The next task is to download sources for CM9 ( takes a hell lot of time :/ ) and start working on it, hopefully with community's help, it will be completed
i will be uploading the device tree soon, so anyone can help me building it..
I'm waiting for that CM9, because all other ROMs I tried are disappointing. I posted here earlier a version for Baidu ROM but turns out that was also buggish.
So, please someone make a Cyanogenmod for this phone.
yeah... please develop a CM9/10 version for this dual sim phone ///
Until today, i still can't find an easy way to root my device. LOL!
carliv said:
I'm waiting for that CM9, because all other ROMs I tried are disappointing. I posted here earlier a version for Baidu ROM but turns out that was also buggish.
So, please someone make a Cyanogenmod for this phone.
Click to expand...
Click to collapse
I did some snooping - it turns out that it's buggish because we are using the nightly builds version of the Baidu . The official version is V4:
http://translate.google.com/transla...m.php?mod=viewthread&tid=62590&extra=page%3D1
charmainelooi said:
I did some snooping - it turns out that it's buggish because we are using the nightly builds version of the Baidu . The official version is V4:
Click to expand...
Click to collapse
I know, but my version was from that stable one, which is based on version 27. Still it had some "things" because for Baidu stable not means final, it's a project in developement. I guess, if no one develop a CM for our device we'll have to wait for some final Baidu.
One other thing is that they develop Baidu to integrate with their service (let's not forget that Baidu is Google for China), and it will be more suitable to users from China .
Too bad that HTC couldn't release a ROM without bugs. Baidu, even in beta, didn't restart my phone randomly like HTC rom did (stock version too), and I have a friend with Wildfire stock, unrooted, untouched which do the same. Maybe it is something with HTC rom platform, I don't know.
I don't think it is hardware, because if it was, Baidu would restart too.
For developement
I just finished to try every single open source of android to make a new build for this phone and my conclusion is not good.
HTC announced that this phone will not get JellyBean - understandable 1 single core processor, 512 MB Ram, not enough.
That will be a huge obstacle in order to get Paranoid, PAC or Slimbean to this phone - they mentain those sources now only for jellybean. Or for jellybean, we need a new kernel to support that. And even so, we can not know if it will work - poor phone specs.
Cyanogenmod doesn't support DualSim, and I bought this phone for that function only.
MIUI doesn't support DualSim either - I know there are a lot of dualsim phones with MIUI, but these are ported not compiled from source - and MIUI source isn't public (what they have on github is a patch tool, wich doesn't work very well, especially with HTC phones which are more difficult).
LewaOS has a source open on github, but is only for Gingerbread - if they upgrade this it will be our best alternative, because LewaOS is a very stable, fast and reliable ROM, and works well even in low specs phones. Baidu ROM seems to be at the begining some port of LewaOS (I still found some mediatek references in baidu, and mediatek is the main processor for Lewa).
So, we're stuck with Sense...
Desire V Rom Development
rohan007 said:
Finally i have device tree ready for HTC DESIRE V The next task is to download sources for CM9 ( takes a hell lot of time :/ ) and start working on it, hopefully with community's help, it will be completed
i will be uploading the device tree soon, so anyone can help me building it..
Click to expand...
Click to collapse
Hi Rohan,
I am interested In developing Android Rom for HTC desire V, so i required few things, can you suggest where i get the device identity (Device Tree, Vendor) details.
carliv said:
Too bad that HTC couldn't release a ROM without bugs. Baidu, even in beta, didn't restart my phone randomly like HTC rom did (stock version too), and I have a friend with Wildfire stock, unrooted, untouched which do the same. Maybe it is something with HTC rom platform, I don't know.
I don't think it is hardware, because if it was, Baidu would restart too.
Click to expand...
Click to collapse
I have the same problem with my htc desire V, can you please link the rom that solved your problem?
ManthanRB said:
I have the same problem with my htc desire V, can you please link the rom that solved your problem?
Click to expand...
Click to collapse
None, it's a hardware issue. I took it to a service shop and then I sold it and never bought a HTC again.