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
Related
I made it for fun and it is NOT usable and will not be before we get official source
http://saraev.ca/signed_120810_223045.zip
working:
- data/radio (no incall microphone)
- wifi
not working: everything else
please do not report bugs. I know whats not working but can fix NOTHING for now
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Woot Woot, Hopefully once we get the source this can become stable. The magic lives on. Not many froyo builds I tried for the 32a werent that easy on battery life. Hopefully this turns out good. Hope the devs will work together to create a stable rom, instead of having their own builds with pros and cons.
If 2.3 ever starts working on 32A + NR, I am jumping ship asap! I miss vanilla android
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
There is no beginning no end. We are never be alone
HTC planning any updates in the future for "oldest" device? :/
eyegor said:
Good job. IMO these ports will be unusable for the next few months until cyanogen comes up with a release.
It was like that with eclair and later froyo. History tends to repeat itself.
Click to expand...
Click to collapse
I would have to agree with you except for I think I read on Cyanogen's twitter page that they will NOT be supporting first gen devices after CM6.1 which I assume meant NO ported 2.3 for us.
Hopefully I am wrong.
where is that quote? can't see it
good job!!!!!!!! hahahahaha
Did anyone1 tried on OR and cm Bcrook kernel???
i want to make a team for dev this rom to work full on magic..contact me..
nice hopefully it will fully work
Download does not work?
Really impressive work Hope to see this fully working.
what changes are needed for this to boot on 32b?
This is all well and good and I'll try it if I get my repaired phone back and can once again have a spare to play with.
However is it reasonable to expect this to ever be usable? We don't seem to be able to get a fully working 2.2 under the new radio so why would 2.3 ever get enough attention or drivers? I used 2.2 for a long time on the old radio but I really needed to use the new radio and have since gone back to 2.1 since it is now my daily driver again.
This will be great fun once I can put the Magic back to dev use.
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
studjuice said:
I tested this on my g1, with a pershoots kernel over top so that it boots. And I was wondering how you got wifi to work? I tried replacing many things, but still get an error starting wifi supplicant daemon on logcat.
Just curious, not like I expect anything to ever become usable haha
Click to expand...
Click to collapse
hm did you replace wlan.ko ? you should
also take a look at init.sapphire.rc:
Ive changed wpa_supplicant service a little because wlan_loader is not used as in eclair/froyo roms. my *wpa_supplicant.exec* loads the firmware and then starts *real* wpa_supplicant.
I realy dont have an idea whether firmware & tiwlan.ini are different for trout/sapphire. if they are you can edit wpa_supplicant.exec to load propper firmware files..
EDIT: this will not be usable untill we get gingerbrad sources published by google. then maybe cyanogen will do a build for us. I heard he will not support sapphire/trout anmore and if and *only if* it is true I will try to make a working one. I hope it isn't true and cyanogen will still suport our devices because he can do it better than me for sure
saibot64 said:
where is that quote? can't see it
Click to expand...
Click to collapse
twitter.com/cyanogen/statuses/8805829046177792
twitter.com/cyanogen/statuses/10393734621433856
*bump* any news, updates, anything?
found this
http://phandroid.com/2010/12/15/gingerbread-source-headed-to-aosp-soon-now-the-real-fun-begins/
Hopefully we can get a working build, dont wanna let the magic die.
Porting
Anyone done any work porting this? I'm currently working to compile this for my fender. Hopefully with the new radio. Which I've read doesn't work, so... anyone found a working one? I'm running eclipse to compile but if you'd like to help, let me know what you use and I'll send you what I've got.
Hey XDA, this is my first rom its just a basic compile of AOSP, very slow and buggy at this stage i'm afraid, but figured you guys would want to see it in the flesh and hopefully i will be making it run alot quicker in the near future.
To install:
1) Wipe / Data / Cache
2) flash Pryon_Gingerbread.zip
3) flash 2708 kernel found here: http://droidbasement.com/g1/kernels/ram/2635/18/boot-cm_2635.9_ds_32b-oc-uv-xtra-ram-fp-121510.zip
4) Boot Gingerbread.
v.03 COMING SOON
12/21/2010 v.02
LINK :: http://www.4shared.com/file/HCuuugqE/pryon_gingerbread_v02.html
12/19/2010 (first release) v.01
:: Change log:: v.02
Added Gapps that doesn't crash rom
Added Busybox and Toolbox
Google Sync should be working now
Added Facebook
Slightly faster but still very buggy and not a daily rom.
WiFi Fixed also should work with mytouch now.
firsstt....to reserve for future commenting lol
well... if wifi and gapps were working..it mite b good for many to atleast download n try n bug reporting
I thought AOSP was suppose to be fast?
Working on WiFi now, bug reports would be good, although there's to many to count
2.2 AOSP seemed a whole lot faster then 2.3 but this is just a start and also this is the first time i have cooked a rom worth releasing so be patient please speed takes time + I'm new to all this
Can you please post some screen shots? and btw, have you fixed wi-fi in this build or are you planning on a ver .2 ? And yes, can I please have a list of what's actually working? I know its all too much to ask for but I guess these questions will help understand this AOSP for G1 more.
Thanks in advance
Compiling a new build now with jit and a few extras, also hopefully WiFi should be up and running, anyways will be a update tomorrow.
Dominating said:
Compiling a new build now with jit and a few extras, also hopefully WiFi should be up and running, anyways will be a update tomorrow.
Click to expand...
Click to collapse
You may be interested in:
http://forum.xda-developers.com/showpost.php?p=9930562&postcount=23
camera works .. (still a long list of other glaring issues thus why I have no binary)
oh cheers ezterry, syncing now i think i'm pretty close to camera built on my compile but I've always had trouble with the camera stub := false cammands.
Looking forward to future updates
........................10 char
Photos and benchmarks would be nice. I'm a flash-o-holic as it is, but I wanna start using my phone. Seems like every week I'm switching to another rom. So I'm sticking to what I got.
Dukenukemx said:
Photos and benchmarks would be nice. I'm a flash-o-holic as it is, but I wanna start using my phone. Seems like every week I'm switching to another rom. So I'm sticking to what I got.
Click to expand...
Click to collapse
Um dunno if you read the whole post, but bro said this ain't fast and is buggy, and to top it off he said he's new to this. Soo it can't really be a daily driver. I'm using that CM6 gingerbread mock up, which I like and its been fine for days on end, don't do much on it but I have the new radio w/ 15 or 14 ram hack, firerats aio-script, and new market, don't use data but use wifi, and I almost have half battery by the end of the day and that's about a good ten hours for me. Dunno what's good for you, but I recommend. But really use common sense and read the op. You can keep up on the progress or support the cause and help out and give a bug report
Sent from my HTC Dream
Today 0.2?
cctv35 said:
Today 0.2?
Click to expand...
Click to collapse
Hopefully
Although right now i'm not using the ROM i'm eager to see some progress
Does it work on Magic 32B too ?
I'm interested in this!
Btw how is the 3d working on your build ?
Sorry guys had a real busy day yesterday didn't get much done but before i head out christmas shopping i'll try and get the next release fixed wifi and hopefully some gapps will be included.
does this have the gingerbread screen off animation?
I AM IN NO WAY RESPONSIBLE FOR ANY DIRECTIONS YOU FOLLOW HERE NOR AM I RESPONSIBLE FOR THE PROBLEMS ANYTHING I HAVE CREATED MAY CAUSE YOU. YOU ASSUME ALL RESPONSIBILITY AND DISCLAIM THE RIGHTS TO SUE ME.
NEW RELEASE 3/28/2011
OK, time for a simultaneous release of AOSP Showcase and Mesmerize, with AOSP voodoo kernels and a set of GAPPS that jt1134 has built for us.
First of all lets give thanks to those that helped me out and made this happen. Phidelt82, thanks for testing and hosting the downloads. Elijahblake, thanks for testing and sticking to it even through your phone troubles that the inbetween releases and original (yet buggy) release called. Thanks dfgas for testing as well, and getting me important Mesmerize files. Baked_Tator, thanks for testing it, you provided great help. MrHanMan, thanks for testing, you provided great help as well. Thanks to all other testers who I can not remember their names at this moment (PM me and you'll get put in this list). Thanks jt1134 for all the work you put in on the fascinate rom lately, you've had me playing catch up, because though I strive, I can't be as fast as you. Thanks to lmartin92, for dedicating time, energy, and learning through the entire experience and making these builds happen (that's me)
Now to the order of business, announcing this release. You showcase users who have endured previous releases are now ready for a stable release and here it is. Yes some things are not working, but these are the things most folk can get along without.
What's working?
Bluetooth (though headsets, and keyboards may not work), file sending has been tested by many and is claimed to be working.
SMS is now working fully.
3g is working.
GPS is working.
Wifi is working.
Google contacts/gmail syncing is working (may require reboot or a bit of patience on your part).
In call sound volume setting is working thanks to jt1134.
It shows the proper company as to who is providing you services now.
Much more is probably working, but I can't identify them all nor make claims as of yet.
What isn't working?
Bluetooth headset.
MMS.
Video Camera.
Camera does not work at 5mp and it uses black and white previews.
Probably some other things, if you find them, let me know and I'll get to work fixing them.
Where can I get this?
The Showcase AOSP V0.9 rom release is here
mirror
and a torrent magnet link is magnet:?xt=urn:btih:7f1f77e7e9e9cd29cdf19b8eff9daa0ddaf8f9cf&dn=showcase-aosp-latest.zip&tr=http%3A%2F%2Fopenbittorent.com%2Fannounce.
The EC10 AOSP voodoo kernel is here.
The AOSP Gapps are here.
Use CWM Red to flash these in this order, kernel, rom, gapps. Anytime you flash the rom reflash gapps because the rom breaks gapps after reinstallation. Be sure to wipe data and cache before you reboot.
What happened to the kernel being inside of the rom? I've decided to seperate them out, if someone wants a non-voodoo kernel, they can make one and use it. It does have to be customized for AOSP. I just don't know yet how to do this, but it shouldn't be too hard.
In other words, I'm allowing folk to use different kernels than mine own if they care to put the work into it to make it happen.
WHATEVER YOU DO DO NOT *228 unless you wish to possibly lose your phone!
I would like to donate to the cause.
Glad to help you do that. I'm specifically looking to beef up my dev machine to a six core 16 GB ram beast. Of course, if anyone wants to participate in building, I'll actually donate some of my machine torwards a build server. These are the parts I would like to have, and I'm probably upgrading from 8GB 3core machine to a 12GB 3core machine next month (just modifying this sucker here).
I need 2 sets of this memory to make my dream happen. It's a Mushkin 2x4 GB ddr3 1333 (10666) MHZ). The cpu I would like to see is a six core AMD Phenom II x6 1100T. No I don't expect anyone to provide me with this, but this is what I'm going to upgrade to eventually and try to donate back to the community with a Samsung galaxy s i500 build server. By the way, when making donations I'm not the only one to consider. All those fine folk listed above deserve it just as much or more so than me. Now enough with my dreams.
Enjoy AOSP.
Changes in 0.9.1
Streaming issues kind of fixed (no hd youtube, but the rest seems to work).
New GAPPS.
New Kernel (EC10 from jt1134 which is a generic (works on all i500 devices to date) kernel)
GMAIL/contacts sync is fixed
For any questions, comments please join the IRC on #samsung-mesmerize on irc.freenode.net.
Fix for MY PROBLEM please READ FULLY!!!!
New Version is working GREAT!!!!! Thanks again Lmartin92 Thanks to JT1134 and thanks to everyone involved
Awwwwwwwwwww yeah!!!... Thanks to everyone involved!!!
Go go gadget Batesville. Thanks again for the goodies!
Now for some help on getting fixes
all i need fixed is sms and 3g.. I can work with that
Excellent job! I'm looking forward to seeing how this progresses.
Good work man, would you be so kind as to keep the title of this like the rest and add [ROM] and EB11?
I'm also interested in seeing some screenshots .
No problem, changed. That's good info right there, makes this as easily searchable as the rest. Thanks.
lmartin92 said:
No problem, changed. That's good info right there, makes this as easily searchable as the rest. Thanks.
Click to expand...
Click to collapse
No prob, plus this should save you from answering some dumb questions . Glad to see the showcase getting some Dev love!
I'll add some sms debug to the framework tonight. Shouldn't be hard to fix.
Sent from my SCH-I800 using XDA App
Actually, if someone could send me a deodexed framework.jar from a stock build, I can decompile it find a fix that way instead of wasting time on debugging
Sent from my SCH-I800 using XDA App
jt1134 said:
Actually, if someone could send me a deodexed framework.jar from a stock build, I can decompile it find a fix that way instead of wasting time on debugging
Sent from my SCH-I800 using XDA App
Click to expand...
Click to collapse
i can definitely do that for ya...
This is from the picknpack 3 for the showcase
http://www.megaupload.com/?d=93OJ5MTE
THANKS!!!!!!!!!!!!!!!
This is from phidelt82's Pick-and-Pack .3, which is based on Stock Froyo, I think.
EDIT: *shakes fist at elijah*
Updated Post#2 with how i fixed MY *228 and possibly other NONO debacle...
Be sure you read my exact problems before attempting my fix though please!!!!
Yeah the problem may be the fact there's no Cellular South info even in the apns-conf file haha. And some of the build.prop information is for Verizon, and there's values in there for GSM ? Er?
I flashed the one for the fascinate on my mez. My baseband still read eb16 I had 3g data idk will flash back at lunch and see if texting works but calls and data do. I was in a roaming area I work in a uscc home area that will tell it lol. Are those quadrant scores real? I mean I know that on the vibrant the test was high because of h.264 not working correctly.
Sent from my SCH-I500 using XDA App
stephenj37826 said:
I flashed the one for the fascinate on my mez. My baseband still read eb16 I had 3g data idk will flash back at lunch and see if texting works but calls and data do. I was in a roaming area I work in a uscc home area that will tell it lol. Are those quadrant scores real? I mean I know that on the vibrant the test was high because of h.264 not working correctly.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Are you asking if the scores in my pics on post #2 are real? lol, YES THEY're REAL!!!
I got the same scores lol I'm just saying that the test itself could be flawed kinda like oclf scores arent accurate
Sent from my SCH-I500 using XDA App
Also it still linpacks the same
Sent from my SCH-I500 using XDA App
stephenj37826 said:
Also it still linpacks the same
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
well, it definitely doesn't feel the same, no lagging and stuttering when skimming through contacts.. Even the market is smoother for me..
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
Um I'll update all this later as im doing it mobile lol
Bugs:
GPS still being douchy meaning it still not working
WiFi stays on searching for networks
Install: must be on at least ICS rom
Wipe data
Flash Rom + 4.2.x gapps
Reboot
Wait 5 mins enjoy.
Source:
Proton kernel source is still same kernel source which is why WiFi doesn't work :/
LUKE I AM YOUR SOURCE LOL
Downloads:
v5:
recording both ffc n rear fixed 100%
fix camera
fixed playback 100% (because i can )
battery isn't draining (fixed deep sleep)
fixed wifi enough to turn on for temp fix
smaller size of rom
misc changes
link :
v5 is beast
v4 *beastflood*
changelog:
video playback fixed.
camcorder fixed *ffc doesn't record right*
updated to tonights changes
deep sleep issue fixed.
bluetooth issue fixed.
wifi still not working.
etc...lol
link:
I am number 4
V3:
Changelog :
TBD
Link:
http://d-h.st/HaA
v2: it's called beastmode edition but idk why lol jk
changelog :
to make this quicker on myself it has the same bugs fixed as 4.1.2
but the wifi doesn't work on this lol
everything else works and you will need 4.2.1 gapps
fixes battery issues. ( put this here just because that was the biggy)
link:
Yankee doodle went to town and brought back an updated lol
v1:
Because I could lol
Link:
http://codedgraphx.info/tka/sgs4g/jellybean/cm10.1/cm-10.1-20130116-UNOFFICIAL-galaxys4gmtd.zip
sent from my batcave in space! lol
My views on Q's in Dev thread lol
I guess screenies too lol
BTW you guys should thank hechoen without him pushing me last night I wouldn't of tried again and fixed the phone.apk issue lol
@hechoen there it is released!
Lol we now have 4.2.1 before s2 lol
sent from my batcave in space! lol
Edit: Didn't read OP correctly lol
The ROM is working fine so far other than WiFi... I also problem with device settings, but you know that already.
Erik, I wanted to say thanks (already hit the button lol). You never gave up on this phone and now we are on par (in terms of updates) with many popular phones out there. Sure its great to develop on a popular device like the S3, but it is even greater to develop on a phone that is so old and archaic now. I really think that we need more devs like you, people who don't give up on the forgotten. You did what nobody thought could. Not only did you give us a daily driver for Jelly Bean, but now you give us Android 4.2.1... You are the best!
There are other links? low speed download
webxs said:
There are other links? low speed download
Click to expand...
Click to collapse
Do you see other download links in the posts? If there was mirrors, they would listed. This is hosted by one of our members on his own webserver for free just to help out and this was just released, so everyone is downloading at the same time. Don't be so impatient to run a alpha ROM where half the stuff doesn't work and you can't use as a daily phone ROM.
eeeit... Erickmm congratulations you always forward takes this device, why not buy a smsung s2 hercules are in offers, you will be well received...lol
webxs said:
There are other links? low speed download
Click to expand...
Click to collapse
I will say this once and once only. It seems that since Erik is doing roms for other devices as well and is "VERY" popular, this I know cause I looked at the stats on my site which all his files are hosted on, the download speeds are getting bogged down. Unfortunately, there is nothing I can do to fix this. I have made a suggestion to Erik to host on other sites as well, mainly goo and mediafire, and use my site as a mirror. Maybe if there are more mirrors, then it won't get bogged down as much. So, I'll just leave it at that and for now, you'll just have to deal with the slow speeds until Erik decides what to do. Just to give you an idea of what's going on here, I'm gonna show you the stats just for this month alone.
Code:
Jan 2013 HTTP usage codedgraphx.info 179.36 Gig
Day All Traffic (Megabytes) HTTP Traffic
1 11038.48 11038.48
2 13269.43 13269.43
3 11693.21 11693.21
4 10452.60 10452.60
5 11378.55 11378.55
6 13586.09 13586.09
7 11872.08 11872.08
8 14547.27 14547.27
9 11609.46 11609.46
10 13572.19 13572.19
11 11127.03 11127.03
12 10059.93 10059.93
13 15044.09 15044.09
14 11383.62 11383.62
15 9385.89 9385.89
16 3644.03 3644.03
About 95-99% of that is Erik's stuff. So, I'll leave it up to Erik on what he wants to do. He is more than welcome to continue using my site to host his files. With all that said, I'm sorry, but it just seems my site's host just can't handle Erik's popularity.
I'm a nub. What exactly does bln borked mean?
If only wifi, gps, and call worked... I would love this phone again. I'm hating this phone so badly lol
sungersoo said:
I'm a nub. What exactly does bln borked mean?
If only wifi, gps, and call worked... I would love this phone again. I'm hating this phone so badly lol
Click to expand...
Click to collapse
BLN means Backlight Notification. It turns your capacitive buttons into LED notifications. You need an app to control these features.
Seems like 4.2 is really a monster for battery (not a placbo but the truth) on this phone, just 30 minutes and 20% gone (on my second charge)
Sent from my SGH-T959V using xda premium
daothanhduy1996 said:
Seems like 4.2 is really a monster for battery (not a placbo but the truth) on this phone, just 30 minutes and 20% gone (on my second charge)
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Idk man, I used it for a day and found it hard to notice any difference.
I flashed it yesterday and tested a few things (maybe half an hours worth). My battery was fully charged. Fell asleep. When I woke up the battery was dead. I don't know how long it lasted, but with no use it shouldn't have died that quickly.
Sent from a hole in the time/space continuum.
Maybe you have some mediaserver action running?
Got any corrupt music files?
I think this is big problem about battery.
WiFi stays on searching for networks
You can test after turn off WIFI.
What do you think?
Re: [4.2.1]CyanogenMod 10.1 v1[UNOFFICIAL][BETA]
Second time this is a Dev thread I regret opening tbh this rom isn't a DD yet plus its a beta build only released so you guy can play with it that's it .
Its not ready to be used daily and without logs it'll never get there.
sent from my batcave in space! lol
Re: [4.2.1]CyanogenMod 10.1 v1[UNOFFICIAL][BETA]
Erickmmm... PM
Enviado...:thumbup:
OK people. I'm posting this with Erik's permission. Since I've already played with CM 10.1 on my tab, I know a little of what's to be expected and how some of the things work. With that said, here's something to keep in mind...
READ ME:
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal. For us SGS4G users, since we don't have nightlies yet, the updater is totally useless. Do not even attempt to try and use it.
# You do not need to wipe when updating to 10.1 if coming from an earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating from 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0. Credit to post from CyanogenMOD team (G+ https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5)
Now with that said, the only way we will get this to be a daily driver is to HELP the devs by providing logs of what's going wrong. Without logs, the devs can't fix things. Once we get things ironed out and get the major things working properly, then maybe we can submit to the CM Team for our device for nightlies. Until then, if you want to help get this moving, then quit complaining and provide logs. Otherwise, Erik won't support this project at all and may request this thread to be closed or worse, deleted. So, come on guys, let's try to get this project rolling. I for one would love to see our device get some 4.2.1 love.
GFX.myst. said:
Now with that said, the only way we will get this to be a daily driver is to HELP the devs by providing logs of what's going wrong. Without logs, the devs can't fix things. Once we get things ironed out and get the major things working properly, then maybe we can submit to the CM Team for our device for nightlies. Until then, if you want to help get this moving, then quit complaining and provide logs. Otherwise, Erik won't support this project at all and may request this thread to be closed or worse, deleted. So, come on guys, let's try to get this project rolling. I for one would love to see our device get some 4.2.1 love.
Click to expand...
Click to collapse
Now hating to derail thread, but is there a good primer out there or forum post on the best way to get logs or a suggestion on what to submit, what to filter out, how to filter, etc. There a zillion "log" apps. Is one better than the other? I don't mind testing, but I admit, I get lost sometimes in the "post a log" thing and sometimes the log is so long, I'd hate for a dev to have to sift through tons of crap just to find the 1 line that is the key, so anything that can be suggested on what to submit, etc, would be helpful, for me at least and maybe some others.
erikmm said:
Its not ready to be used daily and without logs it'll never get there.
l
Click to expand...
Click to collapse
I am not sure how to get logs... I went to the terminal emulator or what ever and typed in "logcat" then copied this. I am not sure if this is what you need or not. Please help me help you? Also when you get a text, the quick actions bellow the message preview are cut off.