Related
Would it not be easier to get together and create a single ROM? If JF releases a version now, there will be what? 3? 4?
So now all themers need to create 3 or 4 ports. Also, I have noticed that a lot of these different ROMs come pre-themed. Isn't this a bit redundant?
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style. Once we get past the "beta" mode of these roms and they are more official, the cookers will be able to theme and do that stuff on their own. You would then pick roms based on features/themes/addons that you like instead of just going with the newest one that is out like we are now.
Agreed! (This text is just to pass 10 char limit)
Darkrift said:
Not really. if you are familiar with how rom cooking went with teh other htc phones, each has their own style.
Click to expand...
Click to collapse
Agreed. That was half the reason I loved recooking my old Apache every week.
but arnt all these builds just different attempts at getting a working 1.5 build?
Freedomcaller said:
but arnt all these builds just different attempts at getting a working 1.5 build?
Click to expand...
Click to collapse
Not any longer. The official 1.5 has been released and therefore should just simply be giving people root and adding other options.
well no, the official hasnt been released till tmo sends it as an OTA. they will add their own "style" (junk apps, and some good stuff if we are lucky) to it and then we will have official builds. Once that happens, there will just need to be root/themes/modifications. each cook will add his own ideas into his roms and will have his own followers. There will continue to be branches off of each style as we have seen with JF > lucidrem, haykuro > TheDude etc.
I remember when JF made his first rom and I started hoping this would happen. It did not seem like it would based on what was required, but we are fast approaching a rom kitchen like environment in Android where any custom build you can dream will be available. Lets see the iphone do that!
Good point DarkRift....
I went ahead and tested out Haykuro's version and while it's pretty stable, hate the fact that half of my apps no longer work. For this reason, I'm probably going back to JF1.43 until the devs have time to get the software working on 1.5.
momentarylapseofreason said:
Personally I would like a plain-jane ROM without anything added (with the exception of root). Then you can add the options you like as we have in the past rather than have them spoon fed to us whether we like them or not.
Click to expand...
Click to collapse
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
harry_m said:
100% agree ...
We developers have to support 3, 4 or more different roms (different app2sd-mods not included) - that generates an unbelievable workload!
So, why not having one single base (a plain-jane rom) and all firmware-"modders" could publish one single "update.zip" (which can be applied to this basic rom) to make (specified) changes (like I've done with my kernel-update for ADP1.5 - http://forum.xda-developers.com/showpost.php?p=3699701&postcount=157)
Click to expand...
Click to collapse
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
The growth of new Dev's are pretty exciting for me. I love to see that we have options, everyday I have something to look forward to with all these new builds, and I hope more Dev's jump on in with new and fresh ideas. Hey you never know some one can jump in XDA with a genius mind and make our UI look like the Ophone. Now wouldn't that excite you knowing you can jump to that rom instead of being stuck on 1?
Darkrift said:
well no, the official hasnt been released till tmo sends it as an OTA.
Click to expand...
Click to collapse
Incorrect. HTC has released 1.5 as an update for ADP (Dev) phones. So it *is* officially out there for Dev phones, just not an "official" TMo release for TMo branded G1s, which personally I don't particularly care about anyway (
) as I'd always take a manufacturer rom over a carrier one. I'd expect a TMo 1.5 to be practically the same as the HTC one, with additional bloatware!
Regards,
Dave
I love having all of these roms to choose from. I'm just having trouble deciding whether to give up the pdf reader, HTC VK and camera, for the ADP1.5H with multitouch. I'm thinking that sooner or later, I will be able to have all of those things in one rom though.
I am still on Haykuro's HTC build, and my phone is waaaay more exciting than the fruit phone!
The only thing that I can see wrong with this phone now, is that HTC didn't include more internal memory from the beginning. Even with the apps to sd fixes, there are still problems which crop up with those.
Azlum said:
100% Disagree ....
In my past experience with a few htc wm phones, I've seen that competition between the rom "cooks" is exactly what drives them to create the next greatest rom! If they all teamed up then there wouldn't be any roms to compete against and they might lose their desire to keep improving.
And as to the extra workload for devs.... unless you are themeing, there is no extra work required? I am developing for android and the only extra workload I have is making sure my stuff works with both 1.1 and 1.5... the specific rom makes no difference. Edit: I see you are the dev of wifi tether... in which case I'm obviously completely wrong, and I agree it must be a pain in the ass(in your scenario) to make your stuff work in every rom.
This whole conversation is moot anyways, because it will never happen. Even if the current "cooks" all teamed up and worked on one rom, new people would come along who want to make their OWN rom that's different, and the cycle would continue.
Click to expand...
Click to collapse
Quality over Quantity. If they all hooked up together and made on EPIC 1.5 ROM that was plain jane but 110% stable, i would love them for it. But in the end, im waiting for JF's build. Im sure thats what he is doing.
As has been stated by people such as "Big in Japan" though....
Big In Japan said:
Android 1.5 presents more than a few problems for developers. According to Alexander Muse, applications currently running on Android won’t necessarily be compatible with Cupcake 1.5; that means a mad rush to download the new firmware and rebuild their software. Compounding the problem is the fact that the Android Market won’t allow more than one version of an app, which means developers aren’t able to simply create a new, 1.5-friendly update and leave the existing version in place for those without Cupcake. Instead, Big in Japan face creating a new build that’s also backward compatible with earlier versions of Android, something they conservatively estimate should normally take around two to three weeks of development.
Click to expand...
Click to collapse
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Just something to keep in mind.
momentarylapseofreason said:
So basically, if there are ROMs that affect the software, devs will need to "choose" which ROM to use their software on. Although this is a little extreme and MOST of the time this won't be an issue, what if ROM cooking goes that far? Will you be willing to deal without applications that you use to have something else?
Click to expand...
Click to collapse
If the developers were using private APIs during the development of their application, then the fact they are broken on Cupcake is likely to be their own fault for using an API which is not necessarily static and therefore liable to change. If they only used public APIs, then it is Googles fault for changing those APIs, or the behaviour of those APIs.
This is one of the "problems" with Android being open source - you can't realistically hide the private APIs from developers since they can see them being used in the source code, and thus may be tempted to use them when in reality they should be restricting themselves to just the public APIs to ensure forwards and backwards compatibility.
Regards,
Dave
I have to agree with everyone who wants to keep things in one.
This does NOT mean that different people can't add particular modifications to what is available, it just means distributing these things as smaller components.
Start with the stock ADP1.5 image. If you want multitouch, apply the update.zip that provides multitouch (and nothing else). If you want tethering, apply the update.zip that provides the kernel with netfilter. If you want a skin (or whatever you want to call it), apply the update.zip that provides it. There is no point in bundling everything together in full system images since all this does is it makes the downloads huge and creates incompatibilities.
For example, I have always used the stock ADP firmware. I have looked at JF's full go and found that while nice, it adds things that I don't want and leaves out things that I do want, which means that it would end up being equal work to adjust those builds into something that I want as it would end up being to modify the stock image. The deciding factor is that I know exactly how my changes work against the stock image and I don't necessarily know what changes JF has made to his.
Actually since most builds are only file-based (i.e. changing some files in /system), could we make a program that (with root, of course) download the difference and apply them? Like an android market for firmware builds or say an apt for android.
Then user get the freedom to choose what they want and can go back to previous versions easily when things go wrong.
To be safe, it could just use symbolic links to apply updates, so restoring will be easier and gives the internal flash a longer life.
So, since HTC is now almost 3 months past due releasing the kernel sources, I've been trying to adapt the GSM kernel to compile and work with our devices, by disassembling the stock kernel and going through line-by-line of the source to see what needs changing.
I started by copying all the '*hero*' files to be '*heroc*', and renamed all the symbols to be heroc as well. Then pulled /proc/config.gz to use as a base config. Also had to fix up the Kconfig's and Makefile's, as needed, to be able to support HEROC-specific stuff. That more or less gets it to a point where you can compile the kernel successfully, although it's still just a GSM kernel with the name and mtype of heroc.
Then I imported the stock kernel (extracted from boot.img, then decompressed) into IDA as a ROM, setup the CONST segment of string data, imported the symbols from /proc/kallsyms using an ida .idc script, and analyzed the remaining areas of the ROM. At that point, I had a virtually fully analyzed binary ROM in ida, complete with symbols. Then went through and renamed the important symbols from the board-heroc* segments as needed to match what is in the source. I also set up some of the more complicated structures/arrays to make them easier to identify.
I found several differences between the stock heroc ROM, and the make-shift hero-turned-heroc source code, and fixed most of what I came across, or just left notes for things to investigate later. What I have now is a hybrid GSM/CDMA kernel that will likely not boot on either device But I figure since I've put as much time into as I have, and I'm sure there are people more familiar with IDA and ARM than I am, I'm putting my IDA file out there for people to start from. If you're not familiar with ARM assembly, this is absolutely useless to you, so you probably shouldn't bother.
I've spent 2 sleepless nights on it already, and still can't get anything to boot. I also tried to get htc_fb_console working so that I could at least see where and why it was dying, but that hasn't worked out well either.
So, by all means, have fun: http://madcoder.binti.ehpg.net/~madcoder/stock_kernel_heroc.i64
It was created using IDA 5.2, 64-bit, but I don't know how well other versions are with compatibility. Oh yeah, it's 35MB
And if you make some breakthroughs, please post about it here. When I get some time, I'll make a patch set to go from the released GSM kernel, to what I have now, and put that up here too.
Thank you, sad but true
I just wanted to say thank you for this work and express how sad it makes me to see the necessity of reverse-engineering in an OPEN SOURCE kernel. I never thought I would see the day.
I would be very curious to hear from you about the specific differences your disassembling unearthed. Can you say with certainty that the Linux kernel code has indeed been changed to work on the CDMA Hero? I mean it's not simply a matter of some missing driver code or other userspace stuff? If so, this would be pretty damning for HTC.
Thanks again, it's amazing to watch the XDA developers' progress in spite of the barriers put in front of their work.
The majority of differences I found were in things like heroc_fixup() where it doesn't check for engineerid/skuid/etc; different camera driver (s5k3e2fx, vs cy8c); fewer checks for multiple pieces of hardware (which is weird considering the stock phone's kernel supports 4 devices) based on system_rev; wrong vreg_get() strings; etc.
The source that HTC released *does* appear to have all the support we need. With modifications to Kconfig and Makefile, and ignoring the missing board files, you *can* compile the kernel directly, using the stock /proc/config.gz, which means all the necessary drivers are already in the GSM source. It's quite obvious that they had a working kernel tree that supported the GSM phone, plus our 4 CDMA phones, and they simply yanked out the CDMA board files and Kconfig changes, before releasing the source code.
What worries me is that I can't get a console, so it's incredibly difficult to find out where it's dying at. If I could get even a serial console to work, it would make this task so much easier. I think my next step is going to be to load up my hacked kernel into ida, and see how different the two are -- that might be easier than translating asm into C and comparing that way. If I can just compare the assembly for the two, it'd probably be easier.
maejrep said:
plus our 4 CDMA phones
Click to expand...
Click to collapse
Not to derail this too much, but which 4 phones do you mean? does it name them in some way?
markachee said:
Not to derail this too much, but which 4 phones do you mean? does it name them in some way?
Click to expand...
Click to collapse
MACH_HEROC (sprint hero)
MACH_DESIREC (vzw droid eris)
MACH_HEROCT (not entirely sure, maybe bell south hero?)
MACH_NEONC (neon is supposed to be the touch dual, which afaik has never been planned as an android phone, so I'm not sure what's up with this name either)
You can see those in the /proc/config.gz on the phone (ungzip or zcat it first ), and just search for "CONFIG_MACH_".
Also in the htc_wifi.c source, you can see references to espresso, and many others.
Would it be possible to port the moment kernel over and use that since its the same processor type and then fill in the things we need?
Mr. Biggz said:
Would it be possible to port the moment kernel over and use that since its the same processor type and then fill in the things we need?
Click to expand...
Click to collapse
I was talking to zefie not too long ago and he was saying the hero kernel is so much more stable than the moments kernel... just my 2 cents.
Keep up the amazing work mad man.
travo1 said:
I was talking to zefie not too long ago and he was saying the hero kernel is so much more stable than the moments kernel... just my 2 cents.
Click to expand...
Click to collapse
Yeah, my fiance went through 2 moments, and they were so buggy she switched to the Hero. No problems since.
flipzmode said:
Keep up the amazing work mad man.
Click to expand...
Click to collapse
+1 for keeping up the good work!
:beer: (Does that emote work on this forum? I hope so...)
bumping this so it doesnt get buried 3 pages again
toastcfh said:
bumping this so it doesnt get buried 3 pages again
Click to expand...
Click to collapse
I thought you said you were going to bed
gu1dry said:
I thought you said you were going to bed
Click to expand...
Click to collapse
i was till i had to refresh again
Yeah, I basically put this on hold, due to work priorities (happens a lot unfortunately :/)
But with the news that HTC may be releasing the source soon, this is probably not worth continuing anyway
maejrep said:
Yeah, I basically put this on hold, due to work priorities (happens a lot unfortunately :/)
But with the news that HTC may be releasing the source soon, this is probably not worth continuing anyway
Click to expand...
Click to collapse
Honestly, I would continue it. Nobody's sure that HTC will release the source code (HTC said they would release the source for the "Gero"...we're hoping that was a mistype).
I have a feeling they won't release it anytime soon and you'll probably solve the entire issue with the cameras and more before that source is released.
bump.... its on the second page
Yea def keep the good work up HTC said over the weekends tht came and went so now all we got is you my good man
man we gotta get this thread stickied!!!!
toastcfh said:
man we gotta get this thread stickied!!!!
Click to expand...
Click to collapse
agreed... lol
anyhow i think this will work out before the htc hope does. bumped to the top
So, with some inspiration from NetRipper, I started trying to find a way that I could see how far it gets in the kernel booting before it stops, since I still don't have a console. Unfortunately, his suggests were LED-related (particularly gpio-enabled), and we don't have any of those. Did find one reaction that is very hard to miss, and luckily very easy to trigger: reboot via gpio
So now I'm stepping through the code, trying to find at what point in execution it stops rebooting and just hangs. So far I'm in init level 4 (of 6). I'm really hoping this leads me to something that will at least tell me "well THERE'S your problem!", and I can reverse the stock kernel asm to figure out what is different.
Link: http://conclave.notionink.com/showthread.php?767-Honeycomb (I assume this is OK, as you don't need to register to get the ROM. I haven't registered).
This will boot off a 1.2-based GTAB, I used 4349 stock as my baseline. Requires a data wipe, post install. Gsensor and camera are broken with this ROM, FYI. I haven't tried a 1.1-based GTAB but I'm fairly certain it would soft-brick - there's a boot.img in the ROM.
Initial thoughts: Seems similar to the Tabletroms HC16 / Beast kernel already in existence. Haven't gotten to Flash video yet, but high-def video playback is broken for me, so far. Google Market is missing, for reasons unknown (legal reasons? Not sure).
Just a heads up that they did release this.
Damn. It doesn't sound any different from the ports we already have.
I haven't found anything of major importance yet. Mostly HC16 with some tweaks to make it more "Adam" branded.
Still, it's refreshing to see a company making the attempt. Viewsonic, you watching? Where's that new 1.2 ROM?
i thought the biggest thing would be drivers.... guess not. looks like if you have to install gapps after installing the rom the second post had the gapps dl
roebeet said:
I haven't found anything of major importance yet. Mostly HC16 with some tweaks to make it more "Adam" branded.
Still, it's refreshing to see a company making the attempt. Viewsonic, you watching? Where's that new 1.2 ROM?
Click to expand...
Click to collapse
roebeet,
You know I'm a big fan, but isn't what NI did, essentially releasing the work of the Tabletrom guys, the same as if Viewsonic took one of your roms, made a new bootscreen, and released it?
I'm just sayin...
MC
I think you're not far off the mark - I haven't done a diff yet, but it does seem very similar.
Granted, I can't really say anything since my BoS mod is essentially the same thing. But I actually give those devs a nod not only in my update.zip, but also in my boot up screen. In NI's defense however, they've mentioned Tabletroms several times in their recent blog posts.
My bigger concern is whether or not Google will stand up and take notice of this NI ROM (and I don't mean in a good way, I mean in a "cease and desist" kind of way).
Roebeet, I know you are very busy. Didn't a big shot at Viewsonic like a VP of marketing used to read this site. Has something changed. When I called Viewsonic recently the phone messaging system seemed like it was a fifth party support for a fourth party support of a third party support company. I hope you get my meaning. I have not heard or seen anything from Viewsonic in a long time. The news release on their web site makes a big deal out of releasing 3588. Which was actually a recall of the 1.2 bootloader. Have they stopped all support for the G tablet?
roebeet said:
My bigger concern is whether or not Google will stand up and take notice of this NI ROM (and I don't mean in a good way, I mean in a "cease and desist" kind of way).
Click to expand...
Click to collapse
I wouldn't be surprised if you're right there.
I think where we've all been failed, and I've been a long time droid owner, now a droid thunderbolt, is Google's release cycle. The original droid came out with 2.0 on it and it was ok, but within a month of any official release of the OS, the code was released on AOSP, and so you could count on the devs to release good ROMS way before the handset manufacturers and carriers did. In the period between release on any one handset, and AOSP you would get the "kang'd" roms. Those are roms cobbled together with bits and bobs from releases for other phones, or betas, etc., and they were pretty good, certainly good enough to hold you over until AOSP became the latest Cyanogenmod and other assorted roms.
So I bought my GTab based on the assumption (mine, and incorrect), that shortly after the XOOM came out there would be kang'd roms that worked pretty well, followed by an AOSP release that the devs turned in to something better than what the XOOM had on it.
I never really cared what Viewsonic did from the standpoint of support because I assumed the minute I bought the GTab that it would be rooted and run better ROMS than they would ever put out, and that was true for Froyo, and is almost there for Gingerbread. HC, we'll see...
Everything that's happened, Google not releasing HC to AOSP, NVidia not getting drivers to devs, has lead to a much more disappointing experience than I expected on this particular device.
Eh, the more I write the more frustrated I sound. I'll stop for now.
MC
guitar geek said:
Roebeet, I know you are very busy. Didn't a big shot at Viewsonic like a VP of marketing used to read this site. Has something changed. When I called Viewsonic recently the phone messaging system seemed like it was a fifth party support for a fourth party support of a third party support company. I hope you get my meaning. I have not heard or seen anything from Viewsonic in a long time. The news release on their web site makes a big deal out of releasing 3588. Which was actually a recall of the 1.2 bootloader. Have they stopped all support for the G tablet?
Click to expand...
Click to collapse
The Viewsonic from December 2010 is not the same Viewsonic post-April 2011. Yes, they used to read this forum and their customer service area did too. When we were grumbling about things like Angry Birds support and Flash back then, they (or whoever was developing for them) delivered and right before Christmas, I might add. I had hopes that they would give us continued support. You don't even want to know what I think now -- I've actually been retrained here and in Slatedroid, believe it or not. If I wrote how I really feel, the moderators would have to delete the post due to language.
As for Notion Ink, I have mixed feelings. I am certainly disappointed with both the GB and HC efforts so far, but at least they've had recent Froyo updates. At least they have a vendor blog and a forum. That's more than what we have with our vendor. I know that Google's stance on HC is partly to blame for all this, but Viewsonic's silence isn't helping.
Well that sucks. Way to over hype a release Notion Ink! Pee on you!
roebeet said:
My bigger concern is whether or not Google will stand up and take notice of this NI ROM (and I don't mean in a good way, I mean in a "cease and desist" kind of way).
Click to expand...
Click to collapse
Yeah, I've been wondering that too. When I first heard NI was officially releasing a Honeycomb ROM, I assumed they got the source code, because how can you have an official release of it without getting google's permission (from a legal standpoint)? But when I read their blog post earlier today and realized they were essentially using the tabletrom effort, I thought "uh oh, this won't last very long". I hope google doesn't step in to stop continued progress, because I'm still wishing for a fully functional version of Honeycomb for the gtab (or at least mostly functional with flash; that's the only thing that's prevented me from switching already).
I apologize if this has been discussed already, but why can't notion ink get honeycomb source? I mean jeez, asus, acer, toshiba, viewsonic etc... are all releasing honeycomb tablets. Seems like if you are a legit company, ask and you shall receive.
Seems to me either
1. Google refused them source. Or..
2. Already focusing on adam 2, they are content with just lazily releasing a community mod as their own.
I'd be ticked if I was an adam owner. Gtab owners knew going in that the community was going to be their sole support. But if I put up with that circus that was the notion ink adam, I expected at least official honeycomb support.
Sent from my T-mobile G2
It's not the vendor, I think it's the hardware. Elocity, Gtablet, Olipad, Hannspad, Folio, VEGA and yes the Adam - all Harmony devices. Google has seemingly ignored that platform, as well as Nvidia. I almost wonder if Notion Ink wants to get caught with their hands in the Honeycomb jar - would at least make Google stand up and finally take notice to a Harmony vendor.
I know that us GTAB'ers didn't expect much of a future, but we know Honeycomb can work given enough resources. This whole situation has totally soured me in regards to Android tablets, and Nvidia devices in particular.
I didn't expect much when I got my GTab just wanted a cool tab to read and play a few games. I personally am probably gonna get an hp touchpad and give my mom my GTab so she can play games and video chat with her BF when he is in Iraq
Notion Ink Blog
Read the June 25th entry:
http://notionink.wordpress.com/
roebeet said:
My bigger concern is whether or not Google will stand up and take notice of this NI ROM (and I don't mean in a good way, I mean in a "cease and desist" kind of way).
Click to expand...
Click to collapse
What would their motivations be? To make us buy more tablets?
That doesn't seem inline with their "do-no-evil" philosophy, though I wouldn't be surprised if it were to happen, for this reason ;;
But would it be Google that would issue such a request, or the companies that took the Honeycomb platform and developed firmware specifically for their products? I would guess the latter, since it's probably with them that we entered a "thou shalt not reverse compile thine firmware, for it is holy" agreement, not with Google.
scyld said:
What would their motivations be? To make us buy more tablets?
That doesn't seem inline with their "do-no-evil" philosophy, though I wouldn't be surprised if it were to happen, for this reason ;;
But would it be Google that would issue such a request, or the companies that took the Honeycomb platform and developed firmware specifically for their products? I would guess the latter, since it's probably with them that we entered a "thou shalt not reverse compile thine firmware, for it is holy" agreement, not with Google.
Click to expand...
Click to collapse
I think you're saying, if someone takes a ROM and modifies it to run on the Notion Adam, and then the folks at Notion stick that ROM on their website, Notion might get served a request to take that ROM down. I dunno, it's open source so other parties have every right to take the code, modify it, and distribute it.
Hello I have the gtab the stock rom, if I make the root with SuperOneClick I can then apply honeycomb update.zip?
StereoD said:
Hello I have the gtab the stock rom, if I make the root with SuperOneClick I can then apply honeycomb update.zip?
Click to expand...
Click to collapse
You don't have to root the device before running one of these ROM updates - the GTAB's stock recovery is not locked down and can accept custom ROM's.
As always, read the modder's directions as they might require things as a pre-requisite. For example, cyanagenmod usually requires clockworkmod as a pre-req. Again, best to ask the modder if it's not stated in their post.
roebeet said:
You don't have to root the device before running one of these ROM updates - the GTAB's stock recovery is not locked down and can accept custom ROM's.
As always, read the modder's directions as they might require things as a pre-requisite. For example, cyanagenmod usually requires clockworkmod as a pre-req. Again, best to ask the modder if it's not stated in their post.
Click to expand...
Click to collapse
Means that it is possible to apply the update.zip in the stock rom on gtab? I can download the file and then apply it in recovery mode?
as the title, on ics rom. what is the different between kernel 2.6 and 3.0?
who can tell me?
its the kernel of linux in general lol
they stopped at 2.6.something now they are on 3.0
see http://www.phoronix.com/scan.php?page=news_item&px=OTUwMg
Yay! Let the bikeshed painting discussions about version numbering begin (or at least re-start).
I decided to just bite the bullet, and call the next version 3.0. It will get released close enough to the 20-year mark, which is excuse enough for me, although honestly, the real reason is just that I can no longer comfortably count as high as 40.
The whole renumbering was discussed at last years Kernel Summit, and there was a plan to take it up this year too. But let's face it - what's the point of being in charge if you can't pick the bike shed color without holding a referendum on it? So I'm just going all alpha-male, and just renumbering it. You'll like it.
Now, my alpha-maleness sadly does not actually extend to all the scripts and Makefile rules, so the kernel is fighting back, and is calling itself 3.0.0-rc1. We'll have the usual 6-7 weeks to wrestle it into submission, and get scripts etc cleaned up, and the final release should be just "3.0". The -stable team can use the third number for their versioning.
So what are the big changes?
NOTHING. Absolutely nothing. Sure, we have the usual two thirds driver changes, and a lot of random fixes, but the point is that 3.0 is *just* about renumbering, we are very much *not* doing a KDE-4 or a Gnome-3 here. No breakage, no special scary new features, nothing at all like that. We've been doing time-based releases for many years now, this is in no way about features. If you want an excuse for the renumbering, you really should look at the time-based one ("20 years") instead.
So no ABI changes, no API changes, no magical new features - just steady plodding progress. In addition to the driver changes (and the bulk really is driver updates), we've had some nice VFS cleanups, various VM fixes, some nice initial ARM consolidation (yay!) and in general this is supposed to be a fairly normal release cycle. The merge window was a few days shorter than usual, but if that ends up meaning a smaller release and a nice stable 3.0 release, that is all
good. There's absolutely no reason to aim for the traditional ".0" problems that so many projects have.
In fact, I think that in addition to the shorter merge window, I'm also considering make this one of my "Linus is being a difficult ^&^hole" releases, where I really want to be pretty strict about what I pull during the stabilization window. Part of that is that I'm going to be travelling next week with a slow atom laptop, so you had better convince me I *really* want to pull from you, because that thing really is not the most impressive piece of hardware ever built. It does the "git" workflow quite well, but let's just say that compiling the kernel is not quite the user experience I've gotten used to.
So be nice to me, and send me only really important fixes. And let's make sure we really make the next release not just an all new shiny number, but a good kernel too.
Ok?
Go forth and test,
Linus
Click to expand...
Click to collapse
just for commemoration
same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?
Singnal said:
same question.why brainmaster's ics version's kernal is also 2.6x as Gingersnap,but official ics is 3.0.
how about future's OTA for NS?
Click to expand...
Click to collapse
Because its probably a moded rom to look like its ics.
if i'm not mistaken, ics is based on the latest linux kernal - which is 3.0 (or 3.2 by now not sure )
the biggest differents are?
Have you read anything that I just posted yet? >_<
Read what i posted earlier.. and if you want follow the link.
Read under:
So what are the big changes? in my previous post!
Brainmaster's ROM isn't pretend ICS, it's the real thing. The new kernel 3.whatever won't be available until the sources are released, and there's not a huge gulf between those kernel versions anyway, it's more cosmetic
Sent from my SNES
I'll keep this post upto date with the last on the status of the build.
I've updated the manifest and it's inline with cm10. https://github.com/TeamICS/manifest_ics_cm/tree/jellybean
Builds are located here.
Nightlies are here or here
If you are not using firerats or don't know what that is make sure you use one of the "_shrunk" nightlies.
Currently the room boots. Lots of things work, here is what doesn't:
Bluetooth (pairing)
HW Acceleration (not likely)
Anything missing from CM10
Known issues are:
Headphone + speaker plays when headphones are in
<--previous-->
IT LIVES!
The build doesn't flash, but it successfully built. You need to use firerats as the system partition is over 173mb by itself. Not sure of optimal settings as it doesn't flash but we're getting closer.
Complete repo diff and repo status is here:
https://gist.github.com/3095432
Things disabled at build:
audioinwrapper from srec
libaac/libFDK
compiler-rt
maybe others.
Please note I haven't cleaned anything so it's quite messy and some stuff isn't pushed up to the repos yet. However it builds and that's a big step. It's off to bed and work tomorrow so I won't get a chance to work on it until the evening/friday.
Very close to a build, libaac is the only blocker, I've reached out to cyanogenmod guys to see if they have any ideas to fix aac, without completely rewritting the asm code. The problem is armv6j doesn't support smmul, clz and others in thumb mode, but armv7 (and the few devices with thumb2 on armv6t2) do. I don't have enough experience with arm asm to figure out how to rework the code to convert from 32 bit operations to 16bit operations. Also valgrind is not supported in armv6 (and can't be) so its disabled.
problems building aac, due to asm code, currently disabled a blocker
problems building srec due to audio issue, disabled
haven't ported camera
So far there is only two show stoppers, first is the audio because its changed again slightly. Shouldn't be too hard to work around. Second is cm team is still porting over all armv6 patches. Building on armv5 get stuck at audio, but armv6 get stuck on some asm code in bionic.[/sstrike] aac. AAC is being a really PITA!
<--Original Post-->
So I'm sure some of you guys are watching the I/O live. For those that aren't it's offical Jellybean will be 4.1. It's got loads of new and nice features. A lot of performance upgrades and the most important thing is the annoucement of the platform development kit. It's got all the low level details and apis need to port hardware to android.
Source code will be released in mid july, which is when the real development starts.
The hardwork everyone did on ICS, jaybob, matt, evervolv team and everyone from the G1, hero and eris forums laid the foundation. The main issue that has always held the heroc back has been the drivers. We have a great .35 kernel but with ICS a lot of the framework, that is hardware <-> software interactions changed. Thats what our audio issue was at first, and the camera. Audio was fixed by porting gingerbread patches and legacy audio support. The camera was tougher but eventually fell to the power of the community! The only two major things left are camcorder and full gpu acceleration.
The PDK will hopefully provide the last little bit we need to get acceleration working fully. It's no magic but from the keynote sounds like it might provide the information we need. Or it might not. Won't know until it lands on the web.
Overall jellybean is a step further from our old heroc's but there is still almost 20k devices officially running cm7! We obviously still have a community here who has yet to upgrade so the new goal is jellybean or bust!
As more information and sources are released I'll update the thread. I plan to port our TeamICS github account to Jellybean as soon as it's released. With luck everything will compile and be in the same boat as ics but only time will tell.
Thank you so much for posting this thread! I would have never knew about this. I'm willing to contribute to Jellybean although I'm with the Evo Shift now. I can make AOSP whenever the first jellybean Rom is released hopefully fixing some things!
count me in, i still have a few months on my heroc left until i upgrade
most of the fixes that happened from eligorom should be able to be applied to jellybean, as its basically the same rom as ics (from early reports)
I really need to add it to a signature when here in the HeroC forums, but:
My HeroC has been inactive on a carrier for the last year +, that being said, I still use the crap out of the device when I can, for a clock/alarm, music, GVoice and GrooveIP phone calls when home...
Basically, I would LOVE to see this thing continue to get updates, I still run CM7 over CM9 or ICS because for me, I see the most performance with CM7. Your talk of the PDK has me excited that I might see equal or better performance out of Jelly Bean on my HeroC!
TYVM, keep us updated
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Thanks for sharing! Hard!
Not to sure if it can get 4.1. I'm having troubles getting it on the Evo Shift right now...
whoshotjr2006 said:
im pretty sure jellybean is going to run equal with ics for us, since hardware acceleration is still not available to us
i've been scouring the web for a solution, but no dice so far. we can turn off hwa, but i see no performance increase from doing so
from what i read, its going to take a module and some tweaks, so its going to take a dev with alot of time and knowledge on their hands to get us up to par with the adreno 200, which may never happen (although i hope it does, the heroc is awesome)
Click to expand...
Click to collapse
So will Project Butter have no effect on the Hero? I would think that it would at least have some effect in adding smoothness.
Sent from my SPH-D710 using xda app-developers app
I have to say I'm really exited about this. I ran ICS a few times on my hero with no problems, but I'm still using it as a daily even though I'm sure it would run fine. Ive been thinking about upgrading, but i don't see why. I really don't like any new phones. Their too big, no track ball, and i just simply don't like any of the new phones out right now. So all that being said... JELLYBEAN !!!!!
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Shelnutt2 said:
Source is out!
https://groups.google.com/forum/#!topic/android-building/XBYeD-bhk1o
edit: Not quite yet.
I'll update the TeamICS github with a new manifest for it as soon as it's out. Good news is that I happen to have tomorrow off so looks like I'll get a nice full day of playing around and trying to get it building. As with ICS I suspect most things will be broken, audio, dalvik, etc. So we'll have to port the ICS patches to jb. Once cm updates it's sources to jb, then we can switch back to them as they will have most of the patches in place already.
Click to expand...
Click to collapse
I change my mind, i do think the hero can run jb BUT im not to sure about 5.0 or whatever they call it.. i upgraded to the evo shift and love it!! Just letting y'all know because this might be the last upgrade sadly said :/
Sent from my BNTV250 using xda premium
awesome, cant wait to see the first source build
ill help in whatever way i can, i just cant dl source because of my crappy internet connection (but if i can find someone to borrow faster internet from for a few hours ill most definitely dl source and try to contribute back that way)
Lol may take me a while before I can start porting for the hero again..
My current projects for the evo shift:
Motoblur
Porting Sense
4.1
3.0
Thats pretty much it =)
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Shelnutt2 said:
Well the cyanogenmod guys are making quick work of jellybean. Every hour more and more patches are ported over. Good news is we are very close to a build. Here are the current issue and workarounds.
Audio doesn't build, working on porting it over
problems with v6 in dalvik, changed to arm mode and ported ics *.S files
problems building aac, due to asm code, currently disabled
problems building srec due to audio issue, working on porting audio
haven't ported camera
Currently hungry and looking for lunch :fingers-crossed:
Click to expand...
Click to collapse
So excited. My Hero has a sweet tooth.
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
megaghostgamer said:
Ha yeah to be honest the hero is getting more development on ics then my evo shift because y'all have aokp.. I need help with someone getting it to work on my evo shift.. We just had a ICS Kernel released so that better get some devs working .. Even though we lost A LOT to the evo 4g lte sadly said..
Click to expand...
Click to collapse
I dont know about AOKP. Sure it was ported, but what work has there been done on it since? Honestly ICS ran super smooth for me on my Hero, especially coupled with V6SuperCharger. I was using LauncherPro on ICS to add to the smoothness, but the V6SuperCharger allows for smooth use of Apex.
yeah, it wasnt aokp that accelerated our cause, aokp has only been around for a few weeks for us so far. it was jaybob's ics aosp rom that really kicked things into gear. that and stritfajt with the camera fix, and the guys over at hero gsm for all the different tweaks and fixes, and mongoosehelix over at eris that kicked butt with evervolv for us. im sure im missing some people, but it doesnt make them any less important to the cause.
and last but not least all the testers and rom flashers that gave excellent feedback
i look forward to seeing jb run like ics
So the reason it's unflashable was because it's over the 170mb limit of the phone. Even though I'm using firerats there still seems to be a hard limit of the recovery and fastboot. The solution is to use a newer recovery, anything cwm 3.x or higher works. The dev phone I'm using had 2.5 cwm and that was the issue. Now it flashes fine. Only problem is for some reason sh didn't build, so now I'm looking to see why it didn't build.
we can cut out some cruft, like live wallpapers, and ringtones/notification sounds. live wallpapers dont work well on heroc anyway.
the sh error is boggling me too, supposedly its mksh symlinked as sh, which should have worked as thats how it is in ics roms.
im on the job lol
edit: yeah something is definitely rotton with those permissions, i checked them against an ics rom and everything checks out, but we still get the permissions error. i'm wondering if its the update binary possibly? ill do some checking and let you know one way or the other