New Roms??? - Hero CDMA General

Is it just me or does anybody else feel they are going through withdraws from the lack of updated roms lately... Especially after the kernel was released.
I know all the chefs are cooking up some real magic (like the gumbo kernel, which is awesome) and its going to be fun to see what they come up with next. Thanks again to all the chefs for all you guys do. You are all truly amazing...

a lot of the dev are working on other things flipz for example is is working on getting his kitchen from pre to full realese and a lot of the others are working on porting to .29 so that we can get the 2.1 roms fully functioning.

a few of us are devoting most if not all of our time to porting the kernel htc released into the 2.6.29 kernel so we can hopefully get fully working 1.6, 2.0.1 and/or 2.1 android builds. After that the rom flood will begin again. I've got a half finished rom I was working on but I'm waiting until I can get 2.1 fully functioning without having to hack android into thinking it has the right kernel.
Honestly I've barely scratched the surface with my attempts at porting the kernel to a newer version and my eyes are spinning, my programming experience is more at the beginner level though, hopefully some of the other devs are having better luck than I am.

Related

Best 2.1?

Hi all
Looking to flash a 2.1 ROM for my sister as i recently sold her my Hero as i purchased a N1
Sorry to ask but in your opinion which is the best 2.1 ROM to flash for day to day stability? usually im up to date on these things but having switched to a nexus ive been abit out of touch with what's going on with HERO DEV work
Cheers in advance for any replys
Get CronosDroid. Only installed yesterday but so far without any major issues. Runs as smooth as any 1.5 with few quirks which are normally present on all custom 2.1. Honestly, I've been very impressed and really can't see how HTC can improve much on official version.
I found the SlideVillian 1.1 to be amazing, fast, smooth and with lots of features... yet to have any problems with it...
Jago
Wait until next week. The most up to date kernel has just been made available so a decent 2.1 ROM can be made. We'll have a full, non-buggy 2.1 very soon methinks.
mikeyd85 said:
Wait until next week. The most up to date kernel has just been made available so a decent 2.1 ROM can be made. We'll have a full, non-buggy 2.1 very soon methinks.
Click to expand...
Click to collapse
I agree. Most people are using the Cronos one, and the 3 Villian ROMs I think. Read the threads, see what bugs are present and have a play.
But yeah, I reckon within the next week or so we'll be seeing some real magic.
mikeyd85 said:
Wait until next week. The most up to date kernel has just been made available so a decent 2.1 ROM can be made. We'll have a full, non-buggy 2.1 very soon methinks.
Click to expand...
Click to collapse
To correct you. The kernel that was released/leaked already is working correctly.
All static/module drivers for the hero are being loaded the way they should.
It is not the kernel that is giving these issues on the roms. but the Libraries created against that kernel. It was more then enough to use the goldfish 2.6.29 kernel and do some little coding so it compiles correctly. Using the compiled kernel and building up the roms with those libraries was the fix...

What's up in the world of Android?

Hey guys and girls!
Sorry for the long absence. Divorce is... sticky. Ha.
So, I was coming back considering working on HappyRom again, I've seen a few other roms have taken some pieces of what I've done, which is great - also sad though because they've given themselves some of the same old issues I was working on fixing. On the other hand though, I've seen a lot of good stuff going on, new roms, new work, NEW DEVELOPERS!
So, someone give me the lowdown - whats going on, what's hot and what should I be working on?
Well you already have a request for a 2.2 sense rom above you in this thread. If its even possible right now.
sent from my superfroyo dream
Froyo on G1, that's hot! First AOSP released source code for Froyo, then Cyanogen started to work on it and when CM6 RC1 and nighlies was released, every dev started to release their ROMs based on CM6. In short - CM6 and it's modifications are hot.
If it's about Sense ROMs - nothing interesting, maybe ZXHero and Hero2G1 are still updated, I think everyone gave up on them since they are slow and newer firmware is available.
For me very nice work is what Firerat is doing - scripts! His MTD Partition Hack eliminates need of using Haykuro, since you can freely repartition your /system, /data and /cache partitions on your G1. You can also fake your SPL which is awesome, brick-free method of installing too big for stock layout.
His all-in-one script and a2sd (included in all-one) also rocks, they enable swap, a2ext and few other really handy functions.
Erm, I don't know what else. Maybe a new radio? 2.22.23.02 was released, for some it has better signal reception, for some worse, few reports way better battery life, while others see no difference.
Hope I helped, if you want more intel please ask .

AOSP equals future support?

So, let me start off by saying that I have searched, read and spent time trying to understand this... but still don't. Which answers why I'm posting this question.
First, what exactly is the reason that an AOSP rom is being developed and a Vanilla Froyo ROM is being developed?
Is the AOSP rom the important one here? Does the working AOSP rom with working kernel mean that we would have 2.2, 2.3.... and so on supported regardless of Samsung?
I understand that Samsung has not supported tremendously up to this point, I understand 2.2 has not been released for the CDMA version yet, and I understand the code they have released is "crappy." When I hear everyone talk about the great work the devs are doing, are they referring to mainly working on the AOSP? If this rom is built, will we be able to just keep developing it for the new versions of Android?
Sorta like in Back to the future when they break off the real timeline and go into the alternate 1985?
Samsungs Android - 2.1, 2.2.... EOL
Dev's Android - 2.1, AOSP, 2.2, 2.3?
Is this how it works? Basically just trying to understand what needs to happen for the Fascinate to get to at least 2.3... not WHEN or even IF it'll get to 2.3.
Thanks
AOSP means Android Open Source Platform.
It's a version of Android built entirely from sources provided by Google. It's completely Vanilla and comes with zero customer or manufacturer customizations. It's easily root-able, and able to be customized completely by the user if desired.
AOSP ROMs are desirable because they tend to be a bit faster and lighter due to their lack of crapification.
AOSP builds are only distributed in their complete and compiled form by Google for their developer handsets (Currently the Nexus One and Nexus S), and not by any carrier or manufacturer.
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Bwangster12 said:
Okay, I appreciate that definition... I think I've gotten what AOSP is exactly... but I guess my question is does AOSP have any involvement in a future for this phone if Samsung decides to close its doors. Is a working AOSP, radio, kernel... whatever basically devs developing a future of this phone parallel to whatever Samsung does for it?
Like, I see from other threads that the ROM for Froyo and Gingerbread isn't necessarily the problem, its the radio and the RIL? If that is the case, what needs to happen for everything to figured out and for us to have a bright future for the Fascinate? Samsung has to release code for the RIL and radio? Are we SOL without Samsung helping here or will the devs definitely figure something out to get 2.2, 2.3... and so on for the Fascinate?
Click to expand...
Click to collapse
It's kinda like building an office park, or strip mall or something. You toss up the basic vanilla buildings, and when it's finally done, companies move in and tweak it how they deem fit.
With a working ASOP build, it'll remove some of the shackles of Samsungs bs code.
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
I don't know where to start with your confusion.
Samsung has not given 2.2 to us. This means that we do not have froyo...
The RIL is an interface layer between the os and the radio. I'm not too sure about it, but anyways...
The developers are working around the fact that samsung has not given further tools that they need to get froyo ported over. Currently they are working on a 1.6 RIL to get froyo working. On another note, vanilla aosp is a good thing because it gives developers more freedom to customize the roms. It also allows for them to be able to port over other roms.
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Bwangster12 said:
So... the AOSP build IS THE KEY here? I understand it isn't working yet, but if the devs get AOSP working, does that mean we will get a 2.2, 2.3 and so on regardless of what is released by Samsung?
I'm just trying to figure out what is happening to keep the G1, Droid, Droid 2... supported by ROMs like Cyanogenmod and others, that hasn't happened yet for the Samsung Fascinate.
I'd like to get the Fascinate, but am sorta waiting because I don't wanna be stuck with a phone for the next 2 years that will max out at MAYBE 2.2 if we are lucky.
Click to expand...
Click to collapse
Basically, that's the hope at least. If there are changes in say, 2.4 that require something that couldn't be hacked around with ASOP, we'll be stuck waiting for Samsung. But with a working ASOP, the groundwork is laid for updates to be ported over a bit more quickly by the devs.
Regardless of the future of this device, the Fascinate is one of the better Android handsets on the market. The screen is brilliant, it's the perfect size, and it's damn fast. The only thing that drags it down is the factory setup (although I personally think it's idiotic to ding the phone because of the inclusion of Bing like some people/reviewers have.)
I'm trying to understand what is going on instead of being one of the millions to ask about updates for this phone. I see phones like the droid series and read that they basically are being supported forever and then I see the Samsung Fascinate, and while I understand that the code is crappy/not released to community... I'm trying to figure out what needs to happen for it to be a supported device like the droids have been.
Bottom line, nothing at all is going to happen unless Samsung releases more than just a 2.2 update? If I see 2.2 drop like tomorrow, does that mean anything for a future, or is it just 2.2 update and we will just get devs releasing their versions of 2.2 roms?
RacerXFD said:
I really don't understand your confusion. If you want a better explanation , I recommend getting on irc.
Click to expand...
Click to collapse
I read his questions as:
"Will a working ASOP build mean better developer support/faster developer released updates?"
I did skim them though.
RacerXFD said:
If I were you, I'd wait. Next gen phones are coming from vzw in the next few months which will essentially blow the existing tech soon.
Click to expand...
Click to collapse
This is a good point. There's an LTE Samsung handset coming out soon, so it might be worth holding out for a little.
Although the Fascinate is no slouch.
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs (like HTC seemingly has done), but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Bwangster12 said:
Pretty much what I am asking. Like of everything that could possibly happen, Samsung releasing 2.2, AOSP being finished, blah blah what is the key that a consumer should look for to say...
"Well, now the Fascinate has no negatives to it and I have no fear that in a year, we won't still be stuck on 2.1 or 2.2 because Samsung screwed us."
Doesn't necessarily seem like Samsung needs to do MUCH to future this phones life and turn over the keys to the devs, but I'm trying to understand what that thing is they need to do. Release a newer kernel, RIL, 2.2 ROM, some code that magically allows devs to port over future roms eternally...
I don't think I care if the phone has LTE capability. I won't get LTE and a regular 3G phone is beyond enough for me. LTE is zero impact for me.
Click to expand...
Click to collapse
What does SAMSUNG need to do? Release their source code, and not just incomplete parts of it.
Will that happen? I doubt it, but it might. Clearly the companies ears are perking up with all the yelling by the consumers.
What can we do in the meantime? Support the devs and wait for them to crank out a working ASOP build and Froyo.
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Basically... AOSP will only be updated to whatever version Samsung has released?
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
No. Android Open Source Project means "Android" in general. It can be 2.1, 1.6, 2.3, whatever. The devs elected to start with 2.1.
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
If you've followed anything in the dev folders, clearly not. JT's "Vanilla" Froyo looks like an AOSP build.
Basically... AOSP will only be updated to whatever version Samsung has released?
Click to expand...
Click to collapse
No. At least not our version.
Bwangster12 said:
Yes, would be nice to have a fully working AOSP build, and then Froyo... but they are seperate from each other right?
Click to expand...
Click to collapse
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
Bwangster12 said:
AOSP build is being done for 2.1? It can't just be magically updated to 2.2 can it? Does Froyo have to be officially released for them to update it to AOSP 2.2?
Click to expand...
Click to collapse
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
ChrisDDD said:
It's hard to answer your question because AOSP and Froyo refer to two completely different things, which can be the same or separate.
AOSP is basically Android, built from clean, unmodified source code directly from Google, without any changes by carriers or manufacturer.
Froyo is simply the 2.2 version of Android.
So, you can have Froyo that's modified by a carrier and/or manufacturer. This wouldn't be AOSP. And you can have Froyo, built directly from Google code. This would be AOSP. You can also have Eclair (Android 2.1), or any other version of Android that's AOSP or not AOSP depending on whether it was built directly from Google code, or modified by a carrier or manufacturer.
AOSP doesn't refer to a single, particular version of Android, but the state of the code that was used to compile whatever version you want to talk about.
A lot of the issue surrounds the kernel. When Google releases a new version of Android, it runs on a particular version of the kernel, which supports it's particular features. Manufacturers have to modify the kernel to support their particular hardware. So, since Samsung has only released source code for the kernel for Android 2.1, we're stuck on 2.1.
The versions of 2.2 from Kaos and JT are running on the Android 2.1 kernel that's been hacked to enable 2.2 to boot and run correctly. It works, but it's far, far from ideal. It doubles (if not more) the amount of work necessary to get 2.2 running, which is the reason for the rather slow pace of development.
So for your question, once Samsung releases 2.2 (the system and kernel), it'll be much easier to get an AOSP build of Android running, since the devs will only need to worry about the system instead of hacking together a kernel and RIL (radio interface layer) as well.
At least this is my understanding of the situation. I'm sure people with more knowledge and experience can correct me where I'm wrong, but I think this is the basic gist of it.
Click to expand...
Click to collapse
Okay, thank you for this answer... this makes sense to me.
So, have HTC and Motorola released newer kernels for the devs of roms like Cyanogemod to update their ROMs, despite HTC and Motorola not actually releasing newer versions? I mean, how is the G1 updated as far as it has. Did HTC release a 2.2 kernel to allow devs to put 2.2 on it?
That's were I'm start confused as well.
I understand that Samsung has some proprietary kernel level code and drivers.
But, I'm curious what is the difference between Linux kernel versions used for different versions of Android. It doesn't sound like major version change and hence should not change anything dramatically. It should be mostly bug fixes. That's why jt was able to get kernel work.
As in relation to ASOP for SF, I see it like attempt to adapt Samsung code to current android interfaces. Once again, these interfaces should not change dramatically between versions, because these are evolutionary. So, I assume when done it is pretty much paved road up to 3.0 at least. That said some new features might not work at all, because we do not have working initial binaries from Samsung.
By the way mrbirdman has GB in progress.
Alright... so this may sound like I'm oversimplifying it, but I don't mean to.
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on? You say that they are working to hack the 2.1 kernel Samsung has released so it allows 2.2 to run on the Fascinate... but why can't they just make a 2.2 kernel? Is that sorta what Cyanogenmod is doing to get a 2.2 Froyo build to work on a G1?
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Bwangster12 said:
Why can't the dev community just create a "custom" kernel to work with their versions of 2.2, 2.3 and so on?
Click to expand...
Click to collapse
Theoretically they could, it would just be a lot of work. Hardware drivers might not be compatible with the kernel version designed for 2.2 or 2.3. I don't think manufacturers are required to release the code for their drivers, so if a driver wouldn't work, one would need to be written from scratch, and without the detailed knowledge of the hardware itself, that is very difficult.
Hardware support is very integral to the kernel, so a kernel for one phone wouldn't run at all on another. So in addition to the difficulty of putting together a totally independent kernel, it would need to be done separately for each and every phone out there, and how many versions of the Galaxy S alone are there? How many HTC phones, how many Motorola and LG and Sony and so on.
It's just not realistic for people doing this, essentially, in their spare time.
So, what the devs generally do is wait until a carrier releases a version of Android (System, kernel, radio, etc.), and with all the hardware support in place and working, they can focus on building custom or AOSP versions of the system.
It's not that they couldn't build their own kernel, it's just a matter of practicality, audience and the shelf live of the particular phone. As it is, a new generation of phones are already either coming out or on the near horizon... and our phone is what, 4 to 5 months old?
Bwangster12 said:
Based on the amazing things I've seen the dev community do, building ROMs from scratch, I guess I don't understand how the kernel can't be built specifically for each new version... forgetting about what Samsung releases.
Click to expand...
Click to collapse
The misunderstanding is in the complexity of compiling a custom system, and developing a custom kernel. They are hugely different in terms of complexity.
Think of a ROM as taking Windows 3.1 and simply tweaking the components that are installed by default - what accessories are installed, what wallpaper is selected, the color scheme of the windows. Not terribly complicated.
Think of the kernel as having to compile DOS, complete with custom drivers for all the hardware - CPU, graphics, memory, storage, multitouch, sound, radio, modem, WiFi, networking, power management, USB support, file system support, etc. all by hand.

will development continue with gingerbread looming?

So sony it going to release GB for our x10 by sept. do you think the devs will stop with the ports and such? becuase why work so hard to port it when in less than 5 months the full build will come? comments concerns?>
i think that dev. will start to focus on kernels and maybe a sense port with it?
i don't think it will stop util gb is released, then gb will be used as a base for future builds.
Or we can use the elements in the SE gb build to theme up our CM7 rom =D
it would really kick ass
The work will not stop. Wolf is joining J now on his work on CM7. It doesn't matter that official GB will come up. The custom GBs will be much faster and smoother without the SE crap in it. And ofcourse custom kernels should fully work until then
GB update is scheduled for end of June, not September. The devs better keep working, if they want to beat SE to the punch.
The official 2.3.3 update will be based on vanilla GB, so it will be very similar to what the devs are cooking up. Basically, we will only really need root to get close to pure vanilla. We won't need a bunch of roms that are just GB vanilla with bloatware removed and a theme added. Most of us can do this ourselves at this point.
However, the bypass will be helpful for lifting any fps limits, speaker volume, undervolting, and overclocking. But it looks like 16mil colors is going to be a bit more difficult, as there is a second layer of security surrounding that (i am not a developer).
I have a feeling SE is going to surprise us with the performance of the GB update. Outside of what I mentioned above, I don't think the average member will find much need for custom ROMs when we are running current OS, unless the devs can get Honeycomb working. That will be the next thing we are looking for.
No disrespect intended to the devs. They are amazing, and if it wasn't for them and xda I would be stuck with 1.6. Just saying that SE is giving us what our devs have so diligently been working on.

[Q] Is there any project about Honeycomb on HD2?

Is there any project about Honeycomb on HD2? Do you know somebody tries to port it?
there was a thread in the dev section with honeycomb but i think most efforts now are getting gingerbread working propelrly and with sense 3 coming out honeycomb has taken a backburner to it all
Lack of interest from devs I guess, and community. Seeing as everyone loves sense and gingerbread. And I don't think most are keen on the idea of a tablet ui on a phone.
If you go to the SD builds, there's a regularly updated build that emulates Gingerbread. I used it last night and quite liked it, and I may try it again when I have the time
EDIT: Sorry, Honeycomb
smeddy said:
If you go to the SD builds, there's a regularly updated build that emulates Gingerbread. I used it last night and quite liked it, and I may try it again when I have the time
Click to expand...
Click to collapse
honeycomb or gingerbread? they are different os's
it is bootable now, let push imilka more
http://forum.xda-developers.com/showthread.php?t=978939
its not stable i'll wait for something more stable
sarp_pasha said:
its not stable i'll wait for something more stable
Click to expand...
Click to collapse
No more work can be done on Honeycomb until Google release all the source code needed, getting everything working on Gingerbread sense appears to be the main focus for most now but still issues like camcorder and glitches,etc to sort out alongside some other small issues.
and they aren't planning to release the source 'till ice cream thingy is released, sometime around.after the end of teh year, they dont want people putting it on phones, cos they used trickery to make it work on tablets(is their official stance) ((all part of their slow gentle move towards controlling their own phone OS, in an iOS/WP7-like way, in my uneducated, wildguessworklike opinion, , ))

Categories

Resources