Related
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.
Hi
Since I'm a new user I can't post in the development forum, so imma ask here.
I have been following this thread for a long time:
http://forum.xda-developers.com/showthread.php?t=1293751
And I'm having a hard time finding a list of known issues for each ROM. I've been looking everywhere but still can't find if BT, HDMI output and 30fps video (just to name a few) are working with the ROMs that are listed in the thread.
I'm more interested in the Compiled CM7 for Infuse and MIUI for Infuse, but they only redirect to the CyanogenMod website and/or give half-answers.
Can anybody help?
Nope none of it works on CM7 or MIUI.
Bt and Hdmi will work when the source codes for gb come out for our phone. Hopefully soon since the last leak came out like last month and was pretty solid.
Not all that sure with the fps issue.
Sent from my SGH-I997
Thanks for clearing that one out for me.
Do you know if we'll be able to port CM9 to the Infuse once the source codes do leak? Or is this not compatible/irrelevant?
Bluetooth isn't waiting on source code, cyanogen mod uses a different Bluetooth stack than Samsung roms, the only thing that will fix Bluetooth is to find a competent developer who had the time, skill, and motivation to get the call audio working over Bluetooth.
So far we have all three, but not all in one developer
the current cm7 compile is otherwise working really well. as kies mini just hit for the infuse you gotta think the full release is right behind it.
Crossing our fingers for source code soon, HDMI and getting our video support back would be nice on custom kernels. Stock kernel is killing my inner child
"the current cm7 compile is otherwise working really well" - so, no HDMI output and no Bluetooth? Otherwise, no problems? I might give it a shot then.
What about CM9? Anybody has a clue?
DenisGuy said:
Hi
Since I'm a new user I can't post in the development forum, so imma ask here.
I have been following this thread for a long time:
http://forum.xda-developers.com/showthread.php?t=1293751
And I'm having a hard time finding a list of known issues for each ROM. I've been looking everywhere but still can't find if BT, HDMI output and 30fps video (just to name a few) are working with the ROMs that are listed in the thread.
I'm more interested in the Compiled CM7 for Infuse and MIUI for Infuse, but they only redirect to the CyanogenMod website and/or give half-answers.
Can anybody help?
Click to expand...
Click to collapse
Kinda shocked that nobody mentioned this.. but this should not have been asked in the development thread to begin with... thanks for choosing the right thread........
As for finding their issues.. just read the threads.. I'd recommend checking out the one with Zeus in the title.. my resources tell me it's a pretty good one...
Sent from my A500 using Tapatalk
DenisGuy said:
"the current cm7 compile is otherwise working really well" - so, no HDMI output and no Bluetooth? Otherwise, no problems? I might give it a shot then.
What about CM9? Anybody has a clue?
Click to expand...
Click to collapse
no cm9....10 chars
Just wondering. Waiting to really do some fun stuff with this fun if/when we gain that capability. Does anyone know if any of our roms have it?
Bulletproof doesn't yet but I was around and very closely following that develop from nothing to something on the Nook Color and have at least some of the project files from playing along way back when.
It's on the short list when I get the chance to start working on the ROM again, because I plan to use that as a band-aid for the PS3 controller while working on fixing the BT issue around that in Sense.
It would also be nice to be able to plug in and use my handful of flash drives while out and about using the compact package the doubleshot is instead of having to rely on something as large as the tablet as the best I got.
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Thanks Blue "The Reason I Still Have My Doubleshot" 6IX. I am looking forward to the day this arrives. Been in the NC forum salivating over USB host stuff. It's more than a bit for my skill level at this point but fascinating! I'm going to mainly be utilizing DSLR Controller.
Sent from my myTouch 4G Slide using Tapatalk
Blue6IX said:
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Click to expand...
Click to collapse
Well I'm so glad you have a plan
Just a side question for you Blue: IF we do get a OTA update from T-Mobile or HTC and it is ICS...would you rebase to that and start developing for ICS?
Because I see you are trying hard to make the stock ROM all that it can be; but if we get a OTA ICS would you switch your attention to making that 'all that it can be?'
Typed by ---- oh wait! I'm schizophrenic!
Blue6IX said:
Bulletproof doesn't yet but I was around and very closely following that develop from nothing to something on the Nook Color and have at least some of the project files from playing along way back when.
It's on the short list when I get the chance to start working on the ROM again, because I plan to use that as a band-aid for the PS3 controller while working on fixing the BT issue around that in Sense.
It would also be nice to be able to plug in and use my handful of flash drives while out and about using the compact package the doubleshot is instead of having to rely on something as large as the tablet as the best I got.
Right now there are other issues to work out on the device first as far as my dev time is allocated, and I can't speak for any other dev's work, but I am curious as well to know if anyone else is spending time on this.
Sent from a digital distance.
Click to expand...
Click to collapse
whaddya mean ps3 controller? is my doubleshot going to finally work on a ps3? O.O and what is usb host support exactly anyways and what can it be used to do ?
Appreciate the kind words _atlien_
@CoNsPiRiSiZe :
If HTC releases an official ICS ROM with corresponding kernel source, i'd jump on that pretty exclusively in an instant without a backward thought.
The only kernel source we have is 2.6.35.10 which corresponds to the 1.28.531.9 / .10 software version. This is really the limiter on my decision for what to work with.
Being as this is my first Android phone, I don't really know enough yet about how it works to be comfortable writing my own source for a kernel (basically) from scratch like tbalden and others are doing, so starting with a working and official source is necessary at this point in my education so I can make progress instead of a mess.
I imagine by the time I eventually move on to another device I'll know enough to just do what I want. Not having prior experience with this stuff is a bit frustrating sometimes because I do really want to play with ICS and the latest and greatest Google is providing us. Intentionally ignoring it sucks, but i'd rather make progress and not problems, hence this is my pennance for not getting a smart phone before this device launched.
I'd rather get a solid education then a whole lot of scattered knowledge if possible, my aim is for being involved with Android for a long time to come so having the patience and restraint to build a solid base of knowledge on how it works will serve me well in the future, even if it forces me to work with yesterday's software now.
Think of it like learning to drive a stickshift on a $200 beater P.O.S. instead of in a lamborghini - you could do it either way but one method makes more sense then the other.
The other thing, though, is the balance of trying to do what would most benefit the whole doubleshot user base the most instead of just the people on my ROM or whatever, so something like working on and posting details about progress on S-OFF trumps it all because that is the single most important issue I can help with I think. Even if I don't get it, maybe my notes and discoveries will help someone else solve it who has a better understanding or more experience with that kind of stuff.
Both of my devices were S-OFF and I had to go out of my way to learn how to put one S-ON again to work on the problem, I could have just ignored it because it didn't affect me but i'd rather try to help everyone, at any cost, then just serve my own selfish desires.
/end thread derailment
----
The question still remains, though, is anyone else working on USB host / OTG cable support?
Sent from a digital distance.
Some_dude36 said:
whaddya mean ps3 controller? is my doubleshot going to finally work on a ps3? O.O and what is usb host support exactly anyways and what can it be used to do ?
Click to expand...
Click to collapse
PS3 controllers cannot connect to and be used by HTC Sense devices, the bluetooth software HTC went with prevents it. If you flash an AOSP ROM you can use one, though, so it's not that it doesn't work but that HTC doesn't want to let us. (Technically broadcomm, but their name isn't printed on the device)
USB host support means that if you get a micro-usb to female USB cable or an adapter you could plug in flash drives, portable hard drives or even other devices to this phone directly.
Since I can get usb cables and adapters at the dollar store now, they aren't hard to come by.
Being able to plug in a flash drive, or install linux on the doubleshot and use it to run the android sdk and program other phones or android devices by plugging it in to this one would be nice - I can install linux on my nook color and then plug this phone into it directly and run fastboot commands while I'm sitting on the bus or something without a bulky laptop - pretty sweet, huh?
No reason we can't do it with this nice, tiny, portable android powehouse other then someone hasn't sat down to take the time and make it happen.
Sent from a digital distance.
I thought the cable used for the ps3 was for charging only and still sends signal via bluetooth. I knoww that's how the xbox works with it's plug and play kit.
Sent from my HTC myTouch_4G_Slide using xda premium
ps3 controllers
PS3 controllers communicate with either USB or bluetooth. He was refering to using the bluetooth part with our phones and "sixaxis controller" app to pair them together.
Any new word on this?
I know tbalden an kornyone have put together a customized kernel for the CM9 alpha releases in http://forum.xda-developers.com/showthread.php?t=1644084
I haven't seen any mention of USB host mode, but I don't have enough posts on xda to ask if that's even a consideration.
my aokp rom has customizable usb host support. idk if cm does
Man, I'd love to see OTG in Miktouch or one of the Sense ICS ROMs.
scverhagen said:
UPDATED 10-27-2012 (r7b)
ROM
This is the stable version of CyanogenMod 9.1 with some modifications:
- Battery drain bug fixed
- Remote Wipe hack/exploit patched (see here)
- Includes modified kernel (see next section)
Stable Kernel
- Linux Kernel 3.0.48
- Kernel debugging disabled to improve performance]
- USB Fast Charge - credit to yank555-lu and xmc-wildchild22
- Undervolting tweaks - credit to xmc-wildchild22
- Overclocked GPU - credit to xmc-wildchild22
- Snapdragon optimizations - credit to xmc-wildchild22
- Inverted front facing camera mirroring issue [r3] (CyanogenMod)
- bluetooth deep sleep issue fixed (lpm -- credit to Agrabren) - modified in [r5] to (hopefully) reduce wifi drain issues
- ondemandx governor (existz [email protected])
- lulzactive, lulzactiveq, and hotplug governors (thanks to SilverL for the pull request)
- IO Schedulers: noopp, deadline, cfq, sio, vr
- USB OTG support (SebastianFM)
- Camera flash enabled down to 5% battery [r7]
- zsmalloc from kernel 3.5 (godmachine81) [r7]
Click to expand...
Click to collapse
quoted from cm9.1
mattlowry said:
quoted from cm9.1
Click to expand...
Click to collapse
Too bad it isn't a Sense ROM. Hopefully, someone will be able to incorporate it into one soon. I just don't like CM or AOKP at all.
How come it's so hard for devs to get the camera to work along with the HDMI? I mean (keep in mind I have no idea how to do this and am just beginning to learn how to program with Python) couldn't they just copy the set of code from a seperate ROM and put it into their ICS ROM to get it working?
(Just for the record, I'm talking about the Motorola Triumph.)
Whatever, if anybody could just explain why (if you could keep it simple, that'd be a plus too) that would be great. Thanks in advance!
The main problem is due to kernel source which controls the hardware. Without this it can be very hard to get things to work. The same for the HTC inspire. The camera is done with dirty hacks and not completely as the camcorder really doesn't work well and won't until we get the kernel source for the ICS update. This is the main reason I am getting a nexus and not dealing with it anymore
sent from my cell in Arkham
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