Related
So in case you did did know, Cyanogen has said that they are not dropping D/S support but rather Cyanogen himself was stopping the managing of the D/S branch (he was previously the one in charge of D/S). This is why we are seeing these "unofficial nightlies"
Cwirl has come out and said that the team is looking for someone to manage the D/S branch. They want someone who uses the D/S as their daily.
Has anyone taken this position?
I am hoping Firerat or Ezterry will be the white knight for D/S
Come on some one please.... take charge for D/S
I dont want to make my "Dream" a paper weight which is not wrecked actually ;-)
I believe that Ezterry or Firerat would do that.
A lot of you are familiar (and have asked) why we don't just have/ask Ezterry and Firerat to take over maintainership. While I like this idea, it would be up to them to decide if they wanted to do so, and, personally, I wouldn't want to feel like CM squashed their creativity and personal efforts. They are doing their own thing right now, and deserve all the props to them for it. If they want to take part in CM, then awesome, we'd welcome it. But thats gotta be a choice they make. Their work can be found on XDA, and is currently your best chance of a 100% Gingerbread install for the DS line.
via:ciwrl at CM
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Not to mention I like their stuff way better than anything CM.
konnspiracy said:
Why does etzerry or firerat have to belong to CM?
they are developing there own rom right now. How would belonging to CM officially help them in any way?
Click to expand...
Click to collapse
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Also, joining forces in a such scenario like it is now would work better for D/S users.
I hope that they commit their progress to CM also because it looks like that ezterry work is working better than current CM D/S development. It would be better for everyone since there are a lot of CM-users that freakly test every CM-nightly. More people = more fun
However, I do understand ezterry and firehat position. I believe that working apart from CM allows faster development and to get away from cyanogen and cyanogenMOD project shadow...
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
luminoso said:
Personally, I would love to see etzerry/firehat to work with CM. So far I've observed all they have to do is maintain an overlay and the rest almost happens by magic and by itself (such as AOSP bugfixes, cm-features, etc)
Personally, now ezterry/firehat development away from CM looks to work great, but in the feature I think I trust more in a big, constantly maintained project like CM
Click to expand...
Click to collapse
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Kinda mixed feelings. i think there's a lot to be gained from joining forces, in terms of faster access to bug reports and bug fixes. More eyes on the code can only be a good thing, particularly at the kernel level. At the user level, with the various customizations, not sure if there's much to be gained.
But I gotta admit, I really like the notification bar power widget, and miss it when I'm on a plain Froyo build. (Which right now is only on my TP2. And if I could get a decent/stable CM6.1 for my TP2, I'd run it happily.)
shadowch31 said:
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
+1 !
shadowch31 said:
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
Click to expand...
Click to collapse
They are all based on CM because CM provides what developers need to do whatever they want. An actively maintained source. That's even one more reason that, independently of Terry/Firehat developing is own ROM or not is always a plus to merge their achievements on CM.
Note that I am not against/favor whatever should Terry/Firehat in particular do. They do whatever they want! I am just using as an example to discuss general android/xda/etc development philosophy
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Ohsaka said:
Theres no reason they need to merge. Its not like either team doesn't openly share their source code. New code and bug fixes flow both ways. And in the long run, its always better to have more choices.
Click to expand...
Click to collapse
+1 I'm scared if they join CM we will never get their insightful answers to our questions. How many times has Terry or Firerat been the one to shed light on your problem? Most everyone here has benefited or been enlightened by these two devs. I can't speak for everybody but Cyanogen has never wasted his time on my problems. I hope they do whatever they want to do. It's time to buy new phones and I want the phone that these two devs move to next.
I took up Tmobile on their offer for a free G2.....i feel kind of like a traitor.....but i love the phone
hopefully they do keep updating the phone along with cm...im keeping my old one and will continue updating and playing with it.....
and i highly recommend the g2
I agree with shadow... I think the days of CM for the G1 should come to an end. It has been a wonderful run, but yes...it is time for something else for these phones...
Here is what I posted in this thread: http://forum.xda-developers.com/showthread.php?t=916770
"Who cares? I mean really.. I'm not trying to be a douche by any means. But think of this... We have TONS upon TONS of stuff for the G1 already... Metamorphs to make it "look" like Gingerbread, ton of apps, etc...
Why not let the newer phones have their chance too??
I say we take the software that has been bestowed upon us and improve it. Make it fast, more stable, etc. I mean really... Do we honestly need 45 ringtones, 27 notifications, news and weather, and all that extra "bloatware" in these ROMS right out the gate?
I think maybe we should focus on making a ROM or ROMS smaller, faster, nicer, etc. I know I for one don't "need" all that extra stuff in the ROM... And if I did, I could install it my SD card, keeping the ROM lightweight, fast and stable.
Now, I am not developer, but I damn sure am NOT afraid to try new stuff on my phone. Look at my sig... The ROM I'm running is stupid fast and stupid stable, and I still stripped out over 10MB of "extra" stuff, and still have all the functionality that it was meant to have."
**Just an example of some of the "extra" things we could do to these phones... Think of the PSP field... People, including myself, have modded these to the extreme! Lighted triggers, etc... Check out my sig and click on the last link...
Awesome discussion going on here. I really like the ezterry and firerat's work for gingerbread on D/S. These two developers are really superior developers in the android community. They both work at the source level producing totally authentic roms. Also Looking at cm they are also still at the nighlies and we are at alpha. It does take time to port something new and at the speed we are going is really amazing we had basically nothing working at the beginning. Now almost everything works on the ezterry's gingerbread for D/S. What we need now is just some speed enhancement and some bugfixes. I believe over no time we will have a really good gingerbread rom that can be a daily driver. Also there are people working on the CM7 for dream sapphire as well. I am sure we will definately see CM7 stable on our devices as well even if it takes some more time.
shadowch31 said:
I have never been a fan of CM and done all I can to stay away from his roms and bases but that is just personal choice and the base for my next bit.
I hope Terry and Firerat stay away from the CM group and keep as they are which is independent coders that work well together as this offers users an alternative to CM. It appears if the G1 community lost these two fine individuals then what choice would we have on anything? CM bases roms are all over the forums in some incarnation or other but for those of us that prefer a different flavour in ASOP builds or builds not built around CM then we would loose that one thing that makes this phone so great and as they say variety is the spice of life.
@Terry & Firerat - Simply, thank you.
Click to expand...
Click to collapse
I take a whole different approach. Cyanogen really has been here for us for a very long time. He was not the first, nor he will not be the last great modder. But you cannot say that the impact CM made is not significant. May I ask, one year before now, what mod did you run on your phone? Cyanogen? Dwangs? Enoms? Bens? WG-build? Kings? Hero? I'm willing to say that you probably tried all of them. They all had their ups and downs, but do you know which one of them is still on my nandroid? CM4.2.15.1. For me, that was the most stable build.
Many phones came out since then and devs came and went. Some were skilled wonders like cyanogen and some just copied and pasted bits and pieces. I particularly remember Eclair. It was basically kick ass when we had the first builds out even though everything was broken. I used to use king's 1.9 as it was the fastest. Slowly, everything started falling into place. Live wallpapers were taken apart and optimized, features were added, NCommander helped to reverse engineer the camera, 3D drivers came in (which F*cked up the Live Wallpapers, a problem we still have to this day lol, just try to run the nexus LWP on OE and tell me how crazy smooth it is). The only problem left was the camcorder. By then OpenEclair led by Wes Garner was the best. Finally 1.3 came out and it was amazing. Wes opened a new thread on the very promising OE2.0, but that quickly faded. From that point, I can't remember how much time has passed. People were over the thrill of eclair and going back to donut. Then out of nowhere CM comes out with the test builds of CM5.0.7. EVERYTHING WORKED! Noone else was able to do this. He wrote drivers from scratch. Just ask Jubeh, he was never able to make the camcorder work on his AOSP build. The kernel was a much newer 2.6.32, performance was amazing. It really breathed new life into my phone.
By the time of Google IO when Froyo dropped by, CM was at 5.0.8 and he decided to expand his team from just the Nexus, Droid, and G1 to 7 more devices like the desire and the hero. That is probably when our phones started to suffer a little. Instead of being more tailored to our specific device, it became more tailored to the higher end phones. CM6 finally rolled out and everyone was super exited again. The system required more resources than Cyan's hacked together drivers could deliver. People started complaining, and this is when the complaints about Cyanogenmod really started coming in. When the MT3G OTA rolled out a few months later people in the G1 section had a little bit of a sour taste from CM. People complained and moaned, and hell, some guy even cursed him out on twitter for an issue with MMS (who remembers "FIX THE ****ING GODDAMN SMS"). I think that was the last straw for Cyan, he put the G1 more as a backburner than a daily driver, I mean, Who would you invest time with, a community that cares for your work (Nexus) or one that complains and curses him out (G1)? If we were a little more patient and more supportive I'm sure most of you guys complaining now really wouldn't be.
Since then I've got a G2. I love the phone, and I love CM. Gingerbread is awsome, neocore tops at 58 FPS, quadrant easily reaches 3000, the works. I've really been removed from the G1 section since then, so I can't really comment on ezterry's roms (Somehow my G1 has an exploded battery lol, and I haven't used it in weeks).
I really did not mean to write a story, and thanks for those who took the time to read it, and sorry if anything is out of chronological order. I guess the moral of this whole long story, is that you should treat your devs with respect. You guys are sitting with 3 year old hardware, and just because someone isn't here anymore to defend his work doesn't mean you **** on his work.
Lol, I'm too melancholic, so I 'm just gonna list the things I remember most about this section.
-my first time flashing a radio. My phone rebooted and I was going totally crazy
-use the search! Don't post in development! Your mom is ugly! posts
-"bricking my phone" I spazzed out when I accidentally did a fastboot wipe and my phone wouldn't turn on LOL
-first time I saw the droid red eye boot up on my phone and using LWP's
-the whole incident with Kingklick when he used his winzip skills to copy jubeh's rom, and ended up with all his threads closed. Poor guy (where we got "kanged from")
-Using CM6 for the first time with all the extra options under CM parts!
-Before Firerat the genius came up with custom MTD, we had to run hero roms with system apps in both system and data, and everything else on sdcard!
I better stop now, its getting late lol. I guess my sig sums it up best:
"Thanks to all the devs that make me love my phone!"
This is a noon question and I appolagize but I figured I would ask anyways. If I were to build the ics myself and flash it would I have any issues getting back to 3.2.2 if I so wished to? I ask because I know the bootloader it picky for the images released for 3.2.2 and have never actually built it myself before. If its not obvious already I own a xoom 4g.
Sent from my ADR6400L using xda premium
Where do you plan to get all the code for all of the hardware drivers? Those are NOT included in the source code.
While we appreciate your enthusiasm for ICS and the developer community. We ask that you do many hours of research before diving into anything near the task you seek to accomplish. To start, you might want to try by flashing between roms, looking at different rom sourcecode, and different driver codes for hardware.
Thanks for the info, like I said I have never done anything like it before. I am kinda embarassed that I didnt even think about the hardware drivers that would be required as well. After doing a little reading on the aosp source site I come to find out an additional bit of information. As of ICS there is more needed than just the source code, there will also be some additional information for the graphics hardware acceleration to work , and the Xoom wasnt mentioned (only the Official Google Devices). Guess I will just sit tight and be happy with flashing ROMs for now. Thanks again.
So at the moment I am currently working on developing a "bare bones" stock rom and modifying it as much as possible with scripts and such.
But what I would like to know from you all is what would you all like to see in the next rom?
Cyanogenmod?
More themes?
Faster?
Battery life?
Cool features?
I think it'd be good to hear you all thoughts & input.
Sent from my SK4G on XDA Premium
Cm6 or 7 and cooler apps to use and batter theams
Sent from my SGH-T839 using xda premium
CM6 an CM7 have both been asked for in the past sadly i think the only way to get it is to mail one of the cyanogen developers a SK4g since it seams none of them have one to even begin making it avail on our phones by making the drivers an kernals from complete scratch like they have with devices like the nook. CM6 i don't know understand fully why we can't get because it is froyo based so the thing would be making a kernal (with out drivers in it from how much i understand building a android kernal). Then when creating the rom an figuring how to make it function more correctly with our odd frame work build. Honestly with themes if you got CM7 working that problem would be more or less taken out with the gingerbread theme engine they use in their roms which makes it a hell of alot easier to change how your phone looks.
Now to the people saying we need a kernal for gingerbread i understand that but then i do look at my nook color an I've tesed a ICS alpha build an have to say "um...... if a kernal is so godly important then how did they make one to run ics on a device that should never be able to run it that has bluetooth drives that were hand made because B&N never intended the device to have bluetooth an they had to hand make alot of other drivers just for the nook color. Anyways I'm getting a spare android phone in the next 10 days (xperia x10 mini) which is even capable of running gingerbread..... and has a alpha ics build.... am i missing something here?..
the kernel is what provides all of the drivers for the phone's hardware. The reason that it is difficult to build an updated kernel for the sidekick is because it uses hardware that isn't found in any other phones, and the drivers are only designed for the 2.6.32 kernel, rather than the 2.6.35 kernel required for GB/ICS.
The reason that ICS alpha builds are being released for the nook color and the xperia are because the CM devs put in the work to get the CM kernel working correctly. The CM kernel is designed in such a way that it can be updated quite easily with little breaking of drivers, but typically requires a large amount of rewriting drivers.
Basically, the reason that it came so fast to the nook color and the xperia is that the CM devs actually wanted those devices, so they bought them, and ported CM to them.
The fact is that the CM devs don't want anything to do with the Sidekick, and won't do anything with it short of someone handing them a free phone to work on.
sduvick said:
The fact is that the CM devs don't want anything to do with the Sidekick, and won't do anything with it short of someone handing them a free phone to work on.
Click to expand...
Click to collapse
is there any particular reason they don't want anything to do with the sidekick?
also, i assume we haven't tried collecting a glob of money to buy an sk4g off ebay or something... have we? seems like it'd be worth it...
I'm not 100% sure why, as I'm not one of them, but I'm guessing that it's because the sidekick is perceived as a teen/feature phone. Typically the support for Samsung phones is limited, and the amount of customization from Samsung on this phone compared to previous phones would require even more work out of them.
Basically in order to get CM7/CM6 it would require the CM dev team 2 things:
1: Interest/Willing-ness to work on the phone
2: A Free SK4G to work on lol
I like the idea of the community all pitching in on buying the CM dev team the SK4G just so that they can begin to work on CM for our phone. CM would open up so many doors for new roms and ports
If it wasn't for the some slight disconfort in giving away my SK4g I'd mail it to a CM dev for them to go crazy with it.... after sending it to someone that can make the sidekick unbreakable modded >.> I'm getting the xperia X10 mini pro cause I can find them for cheap (got mine for 125 after shipping) an it has a hardware keyboard. I'll gladly pitch in money for one of the CM devs to get a sidekick though if they are interested.
it'd be nice to get a feel for the likelihood of the cm devs porting cm to sk4g if they had a phone. that way we can get more concrete on whether we should raise funds for a phone to send to them. i tweeted cyanogen to ask, but got no response. maybe someone else can get to him or other cm devs?
i did posted in the cm forums someone in the xda forums made a bounty request?
and did any dev respond?
stock GB or ICS(cm7/9 would be fine too), better battery life (the current crop of roms are terrible), stripped down lite version would be nice too( no preinstalled apps just bare min)
No one replied
Sent from my SGH-T839 using XDA App
wuziq said:
is there any particular reason they don't want anything to do with the sidekick?
also, i assume we haven't tried collecting a glob of money to buy an sk4g off ebay or something... have we? seems like it'd be worth it...
Click to expand...
Click to collapse
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
insanedrunk said:
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
Click to expand...
Click to collapse
so pretty much we got swcred because of cm dislikement of the phone and his groupies don't want to get kicked out of their team so they don't do anything about it? WOW talk about tyrany
xtrem88 said:
so pretty much we got swcred because of cm dislikement of the phone and his groupies don't want to get kicked out of their team so they don't do anything about it? WOW talk about tyrany
Click to expand...
Click to collapse
Yuup, even if it sounds rediculous, seems that way.
insanedrunk said:
I think that none of the cm team want anything to do with the sk4g is that cyanogen himself didn't like the sk4g. So in result his cm team of followers didn't want anything to do with it. They would be embarrased to be caught with one. For some one that has worked on many diffrent phones like them, it shouldn't be hard to rewrite a kernel.
Think about it, they get cm on almost any new phone that comes out? Don't you think that every phone that comes out have diffrent drivers? Someone has to backwards engineer a driver to get a kernel out that's compatible with cm "roms". Its just a matter of having a member that knows how to code, cm isn't the only person in the world that know how to.
But then again this is just my opinion...
Click to expand...
Click to collapse
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
wuziq said:
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
Click to expand...
Click to collapse
i know that they dont like EVERY phone that CM is on but they still "port" CM to as many phones as possible because that is their goal
i think that it could either be due to lack of interest or lack of not having the SK4G
wuziq said:
did cyanogen actually say somewhere that he didn't like the sk4g?
even if he did, why would he poopoo on another dev that ported cm to it? he'd want cm to be on as many phones as possible. "how dare someone do work that i didn't really want to do?" no. he's not some evil overlord with a bunch of peon devs who back off whenever he gives a stern look.. because.. OSS projects don't work like that?
also, someone correct me if i'm wrong, but they're not rewriting kernels. they'd have to update sk4g drivers for the cm kernel.
Click to expand...
Click to collapse
I don't have the exact quotes, but they (the usual cm members) were reviewing the sk4g cm said he didn't like the fact that samsung made it, from there evry one weighed in on it..... source: it was on twitter. @koush @cyanogen and others, plus the retweet crap..
insanedrunk said:
I don't have the exact quotes, but they (the usual cm members) were reviewing the sk4g cm said he didn't like the fact that samsung made it, from there evry one weighed in on it..... source: it was on twitter. @koush @cyanogen and others, plus the retweet crap..
Click to expand...
Click to collapse
so b/c samsung made the sk4g and other galaxy s phones they won't port CM to the phones?
i think if we get enough community support by having a lot of us post on cyanogen's twitter and on their forums about it we could get possibly get them to port it
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
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.