Related
Basically, how quick could we expect a straight AOSP port of 2.1 and how functional will it be? I know that the 2.2 build is missing camera, 4G, and MMS, but will we have those same limitations since the source code of 2.1 is already out?
-------------------------------------
Sent via the XDA Tapatalk App
Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.
Shidell said:
Nah--we've got the libraries for 2.1 from the original ROM; all we need is access to flash what we desire, and we can put together an AOSP 2.1r2 build in short order (24 hours or less) that's fully-functional.
Click to expand...
Click to collapse
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.
Roman G said:
When you say the libraries I assume you mean because we already have 2.1 on the evo.
I know with the hero it was a ***** to get the camera, cause HTC has not release the .29 kernel source, so we were stuck with the .27 until toast finally built his own .29 kernel. He is such a stud. By the way it was prolly less than a month ago they got the camera in a 2.1 full aosp rom.
I would think it would not be anything like this though.
Click to expand...
Click to collapse
I think we have a lot more support coming over to the Evo than we had with the Hero. Shouldn't be that long, but its just a matter of getting that kernel source. Your right though, with Toast on our side I dont think anything is impossible. The good thing about Android is you can flash another image in no time at all, so if you wanna see what its all about (Without Camera, MMS, and whatever it was) then you can flip back and fourth just to see the difference. Apps2SDK will be a big plus since we wont be needing to go to the market everytime to get all of our widgets and things back. My mouth is watering as im less than 43 hours from getting her juiced and ready to go!
Thank you for asking this question! (I was going to but was too lazy.) Unfortunately I'm going to wait to get the Evo until there is a way to get AOSP 2.1 (or fully functional 2.2) on it. I hate Sense with a passion. So, good luck everyone and may you quickly make our dreams come true!
Stunna4life888 said:
Shouldn't be that long, but its just a matter of getting that kernel source.
Click to expand...
Click to collapse
We already have kernel source
We tried the 2.1 camera libs in 2.2 (hint came from the fact that Toast saw that the froyo N1 ROM does not replace the camera library as part of its update from 2.1 to 2.2, indicating that the library itself works unmodified between 2.1 and 2.2), but it failed due to a prelink map mismatch: the N1's froyo build expects the camera lib to load itself at location "XYZ" (in memory), as it was built that way for performance reasons, and works that way on the N1. However, the HTC library (different camera) does not load itself at the same location the N1 expects it (call it "ABC"), and was not stripped with the apriori prelink utility. So the framework refuses to load the library because it can't load it where it expects it should be loaded from.
I didn't try an AOSP 2.1 ROM yet, so it feasible that it may load it properly... However, due to the fact that the EVO has hardware that is not supported in Android 2.1 (FFC, 720p video, wimax, HDMI out, etc), HTC has rolled their own framework modfiications. If the camera lib requires any of those modifications (99% guaranteed, it *does*), the library won't be able to find those modified APIs, and will still fail.
Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App
TheBiles said:
Are any devs working on this?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.
TheBiles said:
I appreciate it! However, it sounds like the same things will be broken in that build as the Froyo build. Kind of disappointing, since I at least want the rear camera working. I don't care about MMS/4G/front cam.
Click to expand...
Click to collapse
Well we will just have to see. That's the thing. The cam theoretically should work however we don't know yet. With the front cam and the HD recording you never know what they did to the libraries. I've been thinking and I don't see why it won't work. I guarantee you 4g won't work off the bat. We might be able to hack that in though.
chuckhriczko said:
Yessir. At work now but as soon as I get home I am going to recompile my AOSP build for the Evo and pray that it works. As Maejrep said I don't expect the camera to work (either front or back). I know 4g won't work. But I'm hoping I can get a basic build working and then go from there.
Click to expand...
Click to collapse
If you need any help testing, feel free to contact me. I am very interested in an AOSP ROM, and I'd be more than happy to help out.
Any update on this, guys?
I just installed the Newest Xoom Zone Rom with functioning Camera and HDMI, and I love it. I was going to post this in the Dev forum for the Rom, but because I'm a noob it won't let me. Is there any way to port the Face Lock from the Nexus to a Xoom. I tried the simple, copy .apk to the system install of the zip before I flashed it, and it crashes when I go to set it up. Face Lock appears under the security heading, but it doesn't function. I like this feature on my Nexus, and I think it would work great on a tablet. Is there a way to make this function on the Xoom, or will we have to hope Google releases a way to build it?
marnett2005 said:
I just installed the Newest Xoom Zone Rom with functioning Camera and HDMI, and I love it. I was going to post this in the Dev forum for the Rom, but because I'm a noob it won't let me. Is there any way to port the Face Lock from the Nexus to a Xoom. I tried the simple, copy .apk to the system install of the zip before I flashed it, and it crashes when I go to set it up. Face Lock appears under the security heading, but it doesn't function. I like this feature on my Nexus, and I think it would work great on a tablet. Is there a way to make this function on the Xoom, or will we have to hope Google releases a way to build it?
Click to expand...
Click to collapse
It would be great to have it in deed! But if i were you i should post it into antother section.
Functionality like this will come in time.. We have really only had ics for 30 or so days and alot of devs are working hard on core functions and ensuring it is stable, we only got cam and hdmi in the last few days... Also other devs not associated with the builds may be able to come up with a solution but it may require libs or other files as u have seen just an apk drop wont cut it.. Or the apk itself may need porting for tablets or the xoom specifically, personally i dont know i wish i did. i do think though face unlock will come soon as alot of people are like yourself and want it... i would like it myself
Sent from my mind control device
joshndroid said:
Functionality like this will come in time.. We have really only had ics for 30 or so days and alot of devs are working hard on core functions and ensuring it is stable, we only got cam and hdmi in the last few days... Also other devs not associated with the builds may be able to come up with a solution but it may require libs or other files as u have seen just an apk drop wont cut it.. Or the apk itself may need porting for tablets or the xoom specifically, personally i dont know i wish i did. i do think though face unlock will come soon as alot of people are like yourself and want it... i would like it myself
Sent from my mind control device
Click to expand...
Click to collapse
I wasn't trying to *****, believe me I'm so impressed with the Dev support of this thing. I don't really know a lot about programming or any of that stuffs, and I wasn't sure if anyone had any insight to offer in getting this to work. It seems like the only way that is happening is by testing apart the APK and there is NO way I'm smart enough to do that. I was surprised when I saw the camera support already. Im just really hoping there is a way for this to work eventually, it seems like this is more suited to a tablet than a phone, and hopefully we get this working eventually.
youtube fix attached until i can bake it into the rom and reupload, expect a few more changes once the reupload happens
hey guys
updated with usb mass storage quickfix
back again with a new rom port. this is cyanogenmod 9 for the heroC.
please do not expect cm9 to be a magic cure all for all the problems we still face on our older devices. this runs equally as well as eligorom (evervolv) and will most likely stay at the same pace as evervolv
i take no responsibility for your phone crashing and burning in an epic fashion, or the naked zombie from miami starts a worldwide zombie outbreak. or war, or famine, or disease, or anything of the sort. try at your own risk, dont bother me if your phone blows up
dont give me any credit, give the following people mad props and donate to them if you wish to:
erwinp for youtube fix
stritfajt for getting the camera working
mongoosehelix and all the crew over at the eris forums
1ceb0x for the kernel minfree tweaks and the crew over at the hero gsm forums
dsixda and his kitchen
matt, jaybob, dastin and the heroc crew
zeppelinrox and his v6 supercharger script
tvall and the crew at the g1 forums for the rom
all the people who test this rom and give me feedback
im sure i forgot people, im sorry if i did and if i forgot you please yell at me and ill make sure to thank you
what works:
touchscreen
sdcard
radio (data and calls)
adb
camera preview and taking pics
fixed keyboard
wifi
sound
buttons
audio
root
vibration
bluetooth
zeppelinrox's supercharger script
minfrees are set at boot, no need to change them
video playing from sdcard (software encoding)
displays correct carrier, and hopefully mms should be fixed
usb mass storage (had to use an app, not ideal, but working)
youtube (non hd)
what im working on:
need someone to test mms with stock app
what doesnt work
hardware acceleration
youtube hd (almost unrealistic, at least it works)
probably others
works with problems:
camcorder (displays preview but will not record)
long press home displays large previews, not sure why just yet
other stuff im sure
when you flash this, remember i did not sign it, so if your using clockworkmod recovery toggle signature verification
i reccomend downloading Script Manager from the market and running V6 supercharger. the reason behind this is while minfrees are set already, trebuchet could use being bulletproofed.
this is the gapps i use from evervolv eris: http://www.mediafire.com/?qbpc1zthauh4c1h but feel free to use whatever ones you want
and now for the link:
CM9HEROC v1-1
http://www.mediafire.com/?zutjrhbizhuhhqu
md5sum: 2d9fb865dae038a9c87e4e13db2b5a4c
happy flashing!
Thank you
will pull my Hero out of the draw and give this a shot!
Does camera autofocus work or do we still have to set focus to infinity?
i havnt tested it out yet, but seeing how there is little to no difference at all between evervolv, aosp, and cyanogenmod ics, if we run into camera problems in one ics rom, we will have it on all ics roms
im going to take the safe road and say no autofocus doesnt work, still gonna have to choose infinity. we're amazingly lucky to have camera on ics, and stritfajt did his best to give us what we have.
I was getting nothing but fc's when I flashed this :/ I have firerats at 170 50, and nothing is different from flashing other ics roms. I was able to get through the gapps setup, and settings worked fine. The fc's I remember seeing were browser, email, trebuchet, and the gapps process.
Sent from my HeroC using XDA
hey shakes,
yeah fc's are an unfortunate part of our ics experience right now. if you flash just cm9heroc, you dont get half the fc's as flashing gapps also.
gapps are slowing down our ics roms pretty noticeably bad. im not 100% sure what to do about it at the moment, but im investigating.
when you get those fc's, just hit wait, and then wait a minute or 2 for everything to chill out on your phone, and you shouldnt have many (or hopefully any) force closes after that.
(this is my assumption that you had just flashed the rom and gapps and got all the fc's immediately)
can anyone test if mms is working through the stock app? much appreciated
oh hey and im going to be uploading another build with a way of fixing usb mass storage, not my ideal way, but it works. plus a few build.prop tweaks.
Which sources/manifest are you using? I've been off and on working on cm9 with our TeamICS repos on github. It compiles and boots fine but every app force closes and then the phone starts melting. I haven't had enough time to figure it out but seems you got it all working! Look forward to testing this out.
I'll try just flashing cm9, but wouldn't trebuchet (the launcher) still fc? And these aren't fc's where you're given the option to wait, it's just the dialogue that basically says such and such app stopped working, just letting you know, hit okay to dismiss. Haha. I'll take another look later today and see what's going on, right now I need my phone so I'm running your everevolv rom.
Sent from my HeroC using XDA
Shelnutt2 said:
Which sources/manifest are you using? I've been off and on working on cm9 with our TeamICS repos on github. It compiles and boots fine but every app force closes and then the phone starts melting. I haven't had enough time to figure it out but seems you got it all working! Look forward to testing this out.
Click to expand...
Click to collapse
+1
Same too on the GSM hero side
hey kayant and shellnutt
i ported this from g1. i dont have the internet speed to download the repos or else i would be working on a true cm9 port built from source. sorry for the inconvenience.
shakes,
the only time ive gotten trebuchet to force close on me is when i first boot the phone and unlock the screen too fast. if you can, try to get a logcat and let me know if you find anything out of place.
I'm not sure if I can, I'll definitely look into it though. Any chance of an update for this?
always a chance for an update to this, i just have to have something to update from since i cant build from source.
if anyone knows how to build from source, has the internet speed to dl and the processor and memory to build, PLEASE build cm9 from source. then we can pull in all the fixes that are going to make it into future versions of cm9.
if anyone manages this, please upload your work.
whoshotjr2006 said:
always a chance for an update to this, i just have to have something to update from since i cant build from source.
if anyone knows how to build from source, has the internet speed to dl and the processor and memory to build, PLEASE build cm9 from source. then we can pull in all the fixes that are going to make it into future versions of cm9.
if anyone manages this, please upload your work.
Click to expand...
Click to collapse
This is why we were merged with evervolv, so that any changes they make for devices like ours get to us.
Sent from my HERO200 using XDA
there has to be a way to pull those changes from evervolv over to cm9 though, they are basically sitting on the same base. really its just frameworks that are different, and not different by too far.
i respect everything that the evervolv team is doing and i appreciate the hell out of them for keeping us in mind even with how old our phone is, but many of us are used to the cyanogenmod feel after using it forever on many different phones.
as long as some device like ours has a cm9 built from source though, ill continue to port it on over to heroc and hopefully keep everything evervolv has working consistent through changes.
Hey ya'll, I was just snooping around here in the hero forum since I just flashed a rom on my wife's sprint hero. I see ya'll have a cm9 port over here as do we Evo'ers too. I am using CM9 from Team D.I.R.T over there in evo land. It is great and I thought it would be worth mentioning that "videocam illusions" works great with CM9 on the Evo 4g. We use it to replace the native camcorder. It is free in the Google Playstore. You can give it a try, nothing to lose. Maybe you will get lucky.
thanks cityneversleepz ill have to give it a try, been super busy havnt had time to mess with my phone in a while
Quick question, I don't know if anyone here would be able to answer, or if this is a dumb question, but with official ICS on our phone, what is breaking the camcorder on many of the ICS roms? Is it a kernal issue, or something more in depth?
When "vanilla" AOSP (CM9) or AOKP ROMs are ported over, there are no drivers to make the hardware work with the ROMs. I think the drivers are hacked. So often some hardware does not work. Hacking drivers to make them work is a time consuming process. If/when HTC released the kernel source code, it may help (I'm not sure).
That's my non-developer understanding of the issue.
In the CM9 thread theres a link to "Camcorder.zip" that you can flash after installing Alpha 4 that enables your camcorder. It "sometimes" corrupts the video, but 8 times out of 10 it will work, and records in 720p and SD modes.
Not a perfect fix, but it's something. Probably works with AOKP too but haven't tried it yet.
Thanks for the feedback guys, it reminded me that HTC is pretty bad about releasing source... I've been using samsung products for so long that I had forgotten it was still an issue but unfortunately my infuse broke recently so I bought a one x from someone in the mp. Hopefully I'll get my infuse replaced and have a backup!
so essentially the kernal is still closed source, which is understandable now why there are still some hardware issues.
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