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
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.
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
If anyone has questions or concerns regarding the CyanogenMod 10 please ask here and stay away from the development section for these posts, as it has over 3000 posts.
To start off please read the CM10 faq on the first Page of the CM10 thread before asking any questions here or in the official thread. Thanks
Sent from my HTC One X(L/AT&T)
So, does (or will) the camera app in CM10 have the same burst mode that the Sense camera has? Can you take AS MANY photos AS QUICKLY? Will those photos be similar quality? Will we be able to pull stills from previously recorded video? Or take Hi Res stills while shooting HD video?
I read the last 15 pages of the development thread and didn't see any of this being discussed.
Thanks a bunch!
Billy
Sent from my Nexus 7 using Tapatalk 2
Burst mode is a sense cam feature only, because there is no sense in cm those features will not be there. Your best bet is if you want sense cam but asop feel go with clean rom or tn rom, they can desense the launcher but keep the apps but you will be on ics. But i will say the cm cam is alot faster then it used to be and is still a good camera.
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
PaKMaN787 said:
To start off if you want the video camera and/or audio fixes, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
yungskeeme said:
by audio fixes do you mean caller volume? Im on the 8/22 build. I heard the 8/19 has good caller voice but it kills my battery.
Click to expand...
Click to collapse
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
PaKMaN787 said:
To start off if you want the video camera and/or. music workarounds, please download the experimental build instead of the new nightlies. They will soon be merged.
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
PaKMaN787 said:
Sorry I meant music by audio. Honestly they aren't even fixes for music it just doesn't seem to work sometimes for nightlies... and in call is always a hit or miss
Sent from my HTC One X(L/AT&T)
Click to expand...
Click to collapse
Definetly hit or miss. Heard it was fixed in the 8/28 but no music so I guess I'll stay on 8/22 and deal with it. Heard someone say they flashed AOKP ICS rom and reflashed CM10 and it was fixed.
bstephens2u said:
Any idea how we can get native emoji working? It gives the option to download the add on in keyboards settings. Installs. Then refreshes and shows ready to download again. Also, any plans for Google wallet? This ROM is amazing and ridiculously fast!! Thanks for your hard work and help!!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I'll do a little poking around and see if I can get this working (I probably won't) and I'll let you know if I do!
tropazr said:
**PLEASE READ IN REGARDS TO CAMERA ISSUES WITH CM10**
The rapid fire camera mode is named Zero Shutter Lag or ZSL and there are plans to implement this in the near future. You will also soon be able to take still pictures while recording video. H8 & the CM10 team are working on getting every feature of the camera to 100% and they say they are nearly there.
However, as of right now the camera, video camera, & panorama mode is still relatively broken. The camera's bare bones features are working but only in the build's that are labeled as EXPERIMENTAL. The regular CM10 nightlies do not contain the WORKAROUND that H8 has come up with because this workaround has not been merged with the offical CM10 nightlies that the One XL is now getting.
Word on the street is the camera will be 100% working very, very soon so please be patient.
If you use and rely on the camera on a daily basis...please only flash the EXPERIMENTAL builds until further notice!!!
Click to expand...
Click to collapse
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Is wake locks an issue with cm10 so far or just a few users isolated type instance? I was getting massive wake lock for alarmmanager that I do not get on CleanRom.
anyone else getting bad battery life with this ROM? currently running the 8/29 nightly.
Right now im at 33% battery with 11h on the battery but only 1h45min screen time. I also have GPS on and brightness around 1/2..which could possibly be the problem.
JeepFreak said:
This is such great news! I'd like to publicly commit to donating $30 to the team that makes this happen!
Anxiously waiting,
Billy
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
toptalent said:
I have a couple of general questions.
1. Will the official release of HTC JB drastically and rapidly improve the project? Will lots of things need to be redone/reoptimized? Or it's simply some missing links being filled? What kind of time frame can we expect for a fully working CM10 (equal or close to the quality of CM on the other officially supported devices) following the HTC JB release?
2. Exactly how was the team able to develop this rom so far without official support? And how much farther can this realistically go if we do not get the official JB in the near future (hopefully this doesn't happen). From what I read, I'm under the impression that this rom is already in a much better shape compared to the development phase CM builds on many other non-officially supported devices (for example ICS/JB builds on older devices that received EOL after GB). Is the kernel of the phone somewhat "easier" to crack compared to those devices or is that we have some super talented developers behind this project? And the developer seems confident that even without official HTC JB, this rom can pretty much become a *fully working* one?
Thanks for the awsome work!
Click to expand...
Click to collapse
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
h8rift said:
Well, its done and it should be in the next nightly (20120901)...assuming nightlies are fixed (today's nightly 404's).
Click to expand...
Click to collapse
Wooooooooooot!! And would it just be TeamDouche in general that deserves the donation? Or was somebody specific working on this?
Thanks H8!
Billy
Sent from my Nexus 7 using Tapatalk 2
1. Nope, didn't help us at all. Didnt need it. As far as I'm concerned, after tonight's nightly (technically...tomorrow morning's nightly) everything is pretty much 100%. a few bugs here or there...but I think the Nexus devices are the only ones ahead of us regarding "working" status.
2. We're magical. *snicker* just kidding. We've pretty much completely beat HTC to Jellybean with CM10. The great part of the kernel work intervigil has provided is that we use the same kernel for ICS and JB. Meaning we can backport all JB stuff to ICS with minimal differences. We are very confident that this will be a fully working one. The last piece we needed was the Camera HAL which we *just* received.
Thank you for the thanks! Enjoy!
Click to expand...
Click to collapse
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
toptalent said:
That sir, is very impressive. "Beating HTC to jellybean" sounds so satisfying in an ambitious way, and completely changes the way these games used to be played. Hats off to all the "magicians" who made this happen!
One more question: what about LTE? I'm currently on the 4.0.4 based CleanRom 4.5, which is my first custom rom flashed on the phone (only bought it a week ago). Do I have to flash back to a 4.0.3 based ROM (which I have trouble finding) before flashing to CM 10? If the answer is still yes, is a solution being worked out to troubleshoot and solve the problem?
Click to expand...
Click to collapse
I'm not entirely sure if something is being worked on but I think you should flash CR4.0 as it is definitely working and is 4.0.3 base which is what h8rift said to flash.
Sent from my HTC One X(L/AT&T)
May I ask what is the right procedure to flash CM10? In the zip there is a boot.img. Do we need to manually extract and flash it with fastboot?
I ask this because some people (including me) can't make LTE to work in CM9/10. Some say by flashing CleanROM 4.0, full reset then flash CM10, LTE will be the default. This trick does not work for me. What is the mechanism of this trick? What stays after full reset? All I can think is the boot image. But even manually flashing CleanROM's boot.img then flash CM10 does not work for me. Changing build.prop (ro.ril.def.preferred.network and ro.telephony.default_network as suggested at code.google.com/p/cyanogenmod/issues/detail?id=1623 , sorry can't link external) of course does not work either.
I know #*#*info*#*# can change the preferred network type, but it does not stick after reboot, which renders this approach useless.
Thanks.
What goes into a fully functional ROM for an android phone like our beloved TB's? ICS for us has been an evolution of sorts. From what I understand, first we had woefully buggy ICS because we were missing something that only the manufacturer can provide (the RIL, whatever that is?). Sounded to me like the OS would work, more or less, but it was the calling and data that was missing.
Then we got our leak. The leak provided some critical component, but we still have imperfect ROMs. What did we get, and what do we still need?
I know our devs are leaner and meaner coders than the guys at HTC, and that there have been ROMs which are much improved over the initial BAMF one. But, have we gotten ICS to a sweet spot that can't be improved by an official HTC update? Or can we still benefit from it whenever the hell it comes out?
Duely blundered from my thunderdolt.
If I have to guess, you're seeing them hang back until something a little more refined than that leak comes out. The kernel source will be very helpful in getting some kinks ironed out related to the battery life problem of the leak. Also, I believe there are camera and camcorder issues that are kernel related. Kernel source never gets released until after the official update goes public.
Some of the devs may also be preparing Jelly Bean ROMs and not even paying attention to ICS anymore. I'm hoping for this, as we're still going to be one revision behind when HTC releases Ice Cream Sandwich for Thunderbolt. I've seen at least one dev state that ICS to JB is a snap, relatively speaking, so we should get some sweet 4.1 action fairly quickly one the OTA drops.
The ril was one component we were lacking but jester stumbled across something in his build that gave us 1x data and liquid figured out some of the rest. The main thing we are missing now is official ics kernel. The leak we got was a crappy test build and I think that was among their first test builds but that is just my opinion. Once we get kernel source for ics things will be much better. We also need a kernel dev too because imoseyon has moved on to other devices and won't have time for the thunderbolt.
Sent from my Thunderbolt using Tapatalk 2
Yes, I am currently being a coward. Normally I could live without a camera and camcorder, but I just had a kid. Don't want to miss those moments because daddy hacks his phone.
So we got the RIL and need the kernel. After the real release comes out (probably by the time yet another version of Android will be out), we wait a few months, and bam we have the new htc stock ICS kernel. Is the only way to get it is from them intentionally releasing it? There's no way to reverse engineer it eh?
Guess we wont see another "lean kernel" then if Imo's out of the equation. Hopefully he's not the only show in town.
Duely blundered from my thunderdolt
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Sent from my Thunderbolt using Tapatalk 2
Liquid's current ICS ROM is pretty damn good, if only with a few hiccups that can be fixed without the new kernel. I can't even imagine how good it could be with a new official ICS kernel.
Kernels can be hacked and changed to your liking but I think you can get into trouble if you publish it.
Click to expand...
Click to collapse
Wouldn't imoseyon have gotten in trouble for all the great kernels he's released if that were true?
The Linux kernel is free for anyone to modify. If you improve it, you're expected to share your work. That's the beauty of open-source software.
If HTC doesn't release their source for the kernel but you hack it is what I mean.
Sent from my Thunderbolt using Tapatalk 2
If HTC doesn't release kernel source, they will be in violation of the GPL. The only source they can legally withhold is their own software, like Sense, or proprietary driver files. They don't own the kernel, so they must release the source after they release an official ICS build, and they can't go after anyone for hacking it and publishing the source. Of course, if they never release ICS, the wouldn't have to release the kernel source, and some brave dev would have to figure it out. I hope that doesn't happen.
I suspect we're splitting hairs on this one.
Technically, HTC isnt allowed to withhold the kernel source at all. But they do. So reverse engineering / decompiling the kernel is completely legal.
I'm super excited for ICS/JB/BBQ/whatever. I'm running liquid's rom on my bolt right now. It isn't perfect, but I love the overall user experience. It's a shame these things take so long to move through the pipe, but I'm very appreciative of the efforts folks are putting in to make this happen. :good:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
There will be peace in the middle east first. :banghead:
Sent from my SM-N900V using XDA Premium 4 mobile app
Just because they say it could run on lower end phones doesn't mean it will run w/o lag and so on. I heard the chez won't be getting kit Kat so what does that tell you about the older phones.
Sent from my HTC6500LVW using Tapatalk
The only thing that will run on lower end devices is the new launcher and Google apps. The new ui is supposed to be included in the new launcher and make lower end devices feel and look more like newer ones.
Sent from my ADR6425LVW using Tapatalk
lazarus0000 said:
Sssooo.... According to what I read last night, KitKat is supposed to be able to be usable on pretty much all Android phones, all the way down to those with 512mb of RAM.
Any thoughts as to whether the Charge is gonna get some love with this (certainly, I know, NOT from Big Red)?
"I've got a revolution behind my eyes..."
--Battle Flag
Click to expand...
Click to collapse
The problem with an upgrade to any newer OS on the Charge is the radios. I don't see KitKat and an exception.:crying::crying:
Interesting how they had it where you could use Hangouts as your default SMS App with all the Emoji smileys on phones with Gingerbread including the Charge on the leaked version from the Nexus 5. It was fully working and I tried it. However, now that it's released to everybody through the Play Store, the SMS option is for Android 4.0 Only.
just got kitkat on my razr.... wish I knew how to port, b/c then I would attempt to port this great ROM over to the old Charge....
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2284985
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
pyroman512 said:
I'm interested in doing a CM11 build for the Charge or atleast a CM 10.2 build. I have a Galaxy S4 now but I would love to get some use out of the charge. I just want to turn it into a kickass media player since the RIL situation is never going to get solved. If anyone knows what is involved to make this happen it would help me greatly. I've never built CM before. I've read the CM developer wiki. A lot is over my head. I am trying to learn though
Click to expand...
Click to collapse
I think you're on the right track, though I think I'd stick with CM11 rather than CM10.2.
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
pyroman512 said:
Well I am really interested in learning how to build. So I think I will run a few builds for the Fascinate and then see what I can do for the Charge. My programming experience is intermediate. I feel confident I can learn the process and at least get a semi functional kitkat build up and running and then maybe others could help work out the bugs
Click to expand...
Click to collapse
good luck brother... i'd be glad to test for ya.
some tips that you may/may not already know:
my understanding is that OS 4+ require EXT4 rather than RFS, so it might help to start with a kernel that allows this conversion. there are a few floating around that work.
someone (JT) has successfully (and I guess relatively easily) ported ICS and JB to the charge, the key aspects not working though were mobile data and camera.
I'm told the key road block is the RIL for the kernel in order to get those aspects functioning properly.
as for me, I'd be happy with just a working camera, as the Charge is used by my son as a WiFi-only media player/gaming device. he likes to take pictures/videos, so this is the only thing preventing me from converting it the latest JB port.
again, good luck, and let us know how the progress goes!
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
pyroman512 said:
Well I just started a new job and am settling into that so time will be scarce for a bit. I wouldn't even know how to start with the RIL. I would definitely want to get the camera working provided I can even successfully build CM11. I want to make it clear that I am new to this so it is a big undertaking for me and I have a lot to learn. Once I get a build enviroment set up I will see if I can make some fascinate builds for practice since it is very similar to the charge. Then i will reach out to sbrissen or jt1134 and see if they can give me any pointers. I forked their code on github already.
Click to expand...
Click to collapse
As a previous owner of a droid charge, I honestly hope I can squeeze some use out of it as a media device.