Database Info

[Q] Where's Source?

Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.

Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix

Kid_Cudi said:
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Click to expand...
Click to collapse
I like Kid Cudi as well first of all.
What I mean is and I'm probably not going to use the right term here but the RIL or perhaps SDK.. Bear with me here I'm good at trouble shooting stuff but not programming.
I was googling it didn't help me get the right term lol. Chime in who ever knows what the hell I'm talking about here lol.

The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.

ProTekk said:
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
Click to expand...
Click to collapse
Yeah I think it's RIL. It's what the Cookers keep stating they're waiting for to finish their ROMs like CM7 for instance. The developer for it states that he's waiting for RIL to be able to officially finish his work. We really need to get this released from HTC so we can fix some of the issues people are having with CM7 and the leak for GB. I went back to Froyo because of the issues the leaks having with charging etc..

thewebsiteisdown said:
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Click to expand...
Click to collapse
HTC and google do not have to release any of the android source if they don't want to because the source (NOT THE KERNEL) uses the apache license, which is very permissive like the BSD/MIT licenses. It lets you use any code additions you make to the source for commercial projects without having to give it back unless you choose to http://en.wikipedia.org/wiki/Apache_license. This is why google doesnt have to release the Honeycomb source as long as they didn't make any additions/modifications to the kernel itself.
Google went through lots of effort as well to make sure they would not be bound by the GPL by writing their own clibs based off of code from various BSD ports. See here for an interesting article on some of the low level features of android (it's a bit old, but most of it is still relevant). http://codingrelic.geekhold.com/2008/11/six-million-dollar-libc.html
The kernel (like all linux kernels) is GPL and must be released.

RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.

miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I think there is a misunderstanding here. The RIL from Slayher is not the same as the RIL from HTC/Qualcomm.
Slayher will merge his "source" into the public CyanogenMod repo once he deems it's ready.
On the other hand, the "source" from HTC/Qualcomm is a whole different subject. We won't be getting a drop of it from them. Not now, not ever.

miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.

thewebsiteisdown said:
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
Click to expand...
Click to collapse
No the RIL source and Sense source run under the apache license which states that the software developer can use the open source code but does NOT have to repost anything he or she produces.
So it is up to our dev's to do that and make it readily available.

Android 2.3

I realise that the alpha/beta of ICS has been released but why is it there is no development on 2.3 roms at the moment. Sure people want to have the best ICS rom but seriously I am sick of the constant crashes and "this application isnt supported by your device" on the Android market.
Hopefully the developers focus on the actual stable roms and not silly pre-releases.

daftdrew said:
I realise that the alpha/beta of ICS has been released but why is it there is no development on 2.3 roms at the moment. Sure people want to have the best ICS rom but seriously I am sick of the constant crashes and "this application isnt supported by your device" on the Android market.
Hopefully the developers focus on the actual stable roms and not silly pre-releases.
Click to expand...
Click to collapse
To each his own! I completely disagree, I don't understand what you're asking for, 2.3 roms seem good to go and stable as it is. What else do you want done? Also, I for one don't consider it "silly" pre-releases. Even though ICS has yet to be complete it's far better than what GB has been for me. ICS is also the one that needs some work on, hence the crashes and stuff (I don't experience any at all). If GB is working without crashes and is STABLE, what updates are you looking for? If it's working great, then you don't need to update! Although there are some apps which are yet compatible, it doesn't affect users such as myself.

daftdrew said:
I realise that the alpha/beta of ICS has been released but why is it there is no development on 2.3 roms at the moment. Sure people want to have the best ICS rom but seriously I am sick of the constant crashes and "this application isnt supported by your device" on the Android market.
Hopefully the developers focus on the actual stable roms and not silly pre-releases.
Click to expand...
Click to collapse
Considering I haven't experienced a single crash on Baad's InsertCoin ICS ROM, I have no idea what you are talking about. I suppose one could also question why the Windows Mobile and Palm ROM development forums haven't seen much action...what more is there to do to working stable ROMs? Or better yet, why bother

KAwAtA said:
To each his own! I completely disagree, I don't understand what you're asking for, 2.3 roms seem good to go and stable as it is. What else do you want done?
Click to expand...
Click to collapse
Speaking for myself, I'd like a stable (i.e. not alpha) release of CM7 for my new Sensation. I agree with the OP, if the CM devs are blocked waiting for HTC to release ICS, why not polish off a stable CM7 release? I'm in the process of pulling down source to see if I can help. I'm an embedded Linux developer during the day, but being new to android development and only having one phone (and a wife and kids), I'm not expecting anything but getting my feet wet by the time ICS comes out on this phone. I'm grateful that CM exists, just wish there was a non-alpha mod for my new phone.

elceedub said:
Speaking for myself, I'd like a stable (i.e. not alpha) release of CM7 for my new Sensation. I agree with the OP, if the CM devs are blocked waiting for HTC to release ICS, why not polish off a stable CM7 release?
Click to expand...
Click to collapse
Well I guess they did not want to waste time polishing CM7, where in 1-2 months time, everyone will be expecting them to release CM9 for sensation. Let's say they release a super stable CM7 by the end of Feb, people will be using it for only a month before switching to CM9. Might as well wait for ICS.

forzanetti said:
Well I guess they did not want to waste time polishing CM7, where in 1-2 months time, everyone will be expecting them to release CM9 for sensation. Let's say they release a super stable CM7 by the end of Feb, people will be using it for only a month before switching to CM9. Might as well wait for ICS.
Click to expand...
Click to collapse
Speaking for myself again, I'd prefer to use a solid CM7 until CM9 is just as stable. It was more than 1-2 months before CM7 stable enough to put on my MT4G. But I understand it is the culture here to regularly flash new stuff, even if there's no good reason to, and I'm not knocking that, I've done it too. Which is why I'm either returning this phone for a SGS2, or getting to work on my own (wow, 4.5 hours to sync the CM GB repo!).

elceedub said:
Which is why I'm either returning this phone for a SGS2, or getting to work on my own (wow, 4.5 hours to sync the CM GB repo!).
Click to expand...
Click to collapse
While waiting for the CM code to sync, I went over to htcdev.com and clicked their comments link to "Tell HTCdev what YOU want". I explained that I would like full source code for my HTC phone like LG and Samsung provide for their phones (at least the diffs from the open source code). I didn't really expect to get it, and was not surprised when the reply was no - they only release the Linux kernel source because they're bound to by license. But it made me realize that I had purchased the wrong phone. So I returned it. I was pleasantly surprised to find that the SGS2 is quite functional and performant out of the box, and the source easily available from Samsung. So long HTC...

[4.1] JellyBean Dev thread

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

When Motorola gets around to releasing ICS for the Atrix 2...

my question thus becomes:
Once we get ICS officially from Motorola (and I'm guessing it'll be Android 4.0.4 and not 4.0.3 or whatever), and Jelly Bean is already floating around, will it be possible to then have some ROMs made or built for JB that will work automagically on the Atrix 2, or will the updated kernel in JB become a big hassle/issue that prevents us from using it at all, barring that nobody will most likely crack that bootloader anytime soon...?
tl;dr version: Once ICS is official for the Atrix 2, can JB ROMs be built and usable or, will the updated kernel and whatever just be yet another wall on this fortress?
I just picked up an Atrix 2 and I find it to be extremely fast and so far pretty much rock solid stable. I rooted it, installed CWM, did a Nandroid backup of the 2.3.6 stock installation for safe keeping and then installed Remus 2.0 and it's just insanely responsive and everything works as expected.
But I just watched the Google I/O keynote to see what all the fuss about JB is about and I can see it's pretty amazing considering it's an incremental upgrade for ICS more than anything else, but the performance improvements are crazy so, I'd hate to think that Motorola would work on JB for us and yet not get around to releasing it till well into 2013 which is just a bit insane.
For such a company, Motorola is so behind the curve it hurts. I do love this device, however, it's utterly fantastic for me and I plan to keep it for some time, but obviously it's more than capable of running ICS/JB from the gitgo - now it's just "ok, when?"
Thanks...

br0adband said:
my question thus becomes:
"ok, when?"
Thanks...
Click to expand...
Click to collapse
As per official information - update for ICS - Q3 of 2012 (which actually already started), more precision date - unknown

I don't think you read my post very comprehensively - I didn't nor was I asking if ICS is coming and when it'll be out as we already know that based on Motorola's schedule announcement.
I know ICS is coming, I know it's between July (like, right now) and September (which means between right now and the end of the year given Motorola's somewhat inefficient release schedules of past years.
What I'm asking again is:
When ICS is out, and when I've got it installed on this Atrix 2, is there a possibility that Jelly Bean will be ported over to this Atrix 2 considering they're very similar OSes that most likely will use the same bootloader, or ... ?
In other words, after ICS is available, are we looking at a 2013 release of Jelly Bean for the Atrix 2, if it even happens, or will it be up to talented folk in the developer community to make the best of ICS as given by Motorola?
Hope that's more clear... I don't know how else to ask the question, honestly.

I'm no dev... but I did sleep in a holley day inn last night...
The locked bootloader means that the bootloader can only load the official Moto released kernel. JB will have a new kernel so the only way to get JB is when/if Moto releases it.

That's all I wanted to hear, at least from one other person as a confirmation. Nothing surprising, but somewhat of a disappointment I suppose.
/me kicks Motorola in da shinz, hard... then does it again...

I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.

cogeary said:
I wouldn't be so sure that it's never going to happen. People have accomplished CM9 and AOKP (both ICS ROMs) on the Razr, Droid 3, and Droid Bionic (all of which atm are still on GB) that uses the GB kernel (and just about all of those ROMs are flashable on the A2, just without a working radio). So there's a good chance that the same thing will happen with ICS to JB, and since it's an incremental upgrade then I think it would be easier to do.
Click to expand...
Click to collapse
Yes, this is true. What most seem to not realize or maybe even know, is that the jump from GB to ICS was huge in the kernel space because honeycomb was completely jumped over and skipped in the phone space. What this means is that all of the upgrades from HC were merged into the ICS kernel, so the jump from Gingerbread to ICS was a huge one. The jump from ICS to JB will be much smaller, and it will have a lot more performance tweaks and increases from ICS. So this should be more doable. The real issue is that we need the ICS kernel first to start looking into JB.

Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.

apinkel said:
Yeah I intentionally qualified my reply since I'm not familiar with the enhancements that went into the GB, ICS and the JB kernels...
I would have expected that the project butter enhancements in JB would have required significant kernel level changes. I take it that the kernel level work to support project butter happened with the ICS release... and now the UI layer in JB is more or less just leveraging that foundation.
Click to expand...
Click to collapse
No You may have misunderstood, just a little.
The jump to JB from ICS will be smaller.... Than the jump from GB to ICS. Yes there are a going to be some hefty changes for project butter, but only in in the performance and virtual space areas of the kernel, since every thing in the android app space is handled by the jvm, so there are a lot of enhancements to how the virtual space is handled, that is really what project butter does, as well as the changes in kernel to do that. Now Project butter also changes the vsync timings in the OS as well, and I am pretty sure we can port or figure out some of the changes and make some of that up in ICS as well.
We will most likely be able to run JB "ROMS" without ALL the project butter enhancements once we are on ICS, but that will be more than likely not until closer to the end of the year that we will begin to see some ported ROMS for JB that are capable of running on this phone.

It would be nice to see that... I like Moto hardware but the locked bootloader can be a bit of an annoyance.

Stable ICS/JB ROMs?

Hey.
I've been on jb roms since they came out for desire s and have been using ics before that. However... ics roms have been in beta stage since ever and have not really advanced in terms of having stable or even working main functions. Well this is because of the fact that our devs did not have kernel sources. There have been words that kernel source release would solve all our major issues like front cam and others. But kernel source has been released and I'm seeing a decline in our forum's traffic and in development. I know i's partly due to many original members leaving. But I also hear that devs are facing difficulty in making the kernel. So I want to ask, will we ever have fully stable ics or jb roms or is this not a possibility?
Sent from my Desire S using xda app-developers app

Sorry for the tone, but this is a pretty pointless thread (IMO) there are already several others in a similar vein that exist and as we don't have a time machine and can't see into the future....although speculation appears to what the majority of threads contains these days....
This is now unfortunately an old device and as you rightly pointed out lots of the forums previous users have moved on to bigger and better new devices so the forum traffic was always bound to fall. We still have several devs that are developing for this device so don't do them a dis-service by suggesting that no progress has been made. Just look at the CM, AKOP and JB source build threads for examples.....
Since the release of the kernel source - progress has certainly been made, just look at the tweaked kernel we can now use, in which we are now able to UV & OC not to mention that the wifi tether issues are now resolved... everything takes time, so be patient....or learn to code yourself and help out!

ben_pyett said:
Sorry for the tone, but this is a pretty pointless thread (IMO) there are already several others in a similar vein that exist and as we don't have a time machine and can't see into the future....although speculation appears to what the majority of threads contains these days....
This is now unfortunately an old device and as you rightly pointed out lots of the forums previous users have moved on to bigger and better new devices so the forum traffic was always bound to fall. We still have several devs that are developing for this device so don't do them a dis-service by suggesting that no progress has been made. Just look at the CM and AKOP threads for examples.....
Since the release of the kernel source - progress has certainly been made, just look at the tweaked kernel we can now use, in which we are now able to UV & OC not to mention that the wifi tether issues are now resolved... everything takes time, so be patient....or learn to code yourself and help out!
Click to expand...
Click to collapse
I fully understand the devs' hard work and their dedications. That's not what this thread is asking. It seems to many devs that they are still having a hard time adjusting ics and jb to our device even upon kernel source release. Despite the prior speculation that things would be much easier with kernel source. So I was bringing the problem forth to see if it is possible for us to have stable ics or jb roms. No need to be all defensive. Just want an objective discussion
Sent from my Desire S using xda app-developers app

custom roms are rearly FULLY stable. there is always a little bug here and there. but since the release of the official ICS and the latest kernel source ICS roms are getting mature at last. and if you're still not satisfied, wait a month more. or flash the official ICS and have a really stable rom now.
JB is another story. there is no native kernel source for it and i doubt there will ever be.

I totally see where you are both coming from. The kernel source was released over a fortnight ago.
I agree with Ben, in respect we should appreciate what the current devs have given us etc etc,
But I also agree with skim, I am quite surprised that with the kernel source released, AOSP still hasn't got a functional kernel based on our Saga build. (Andromadus is using a kernel port)
I was hoping for at least ICS AOSP to be working by now, but I guess that is not the case
The forums have certainly gone a lot quieter now, and I suspect by the end of the year, even more of us will leave
But back to the original point, I wish that things could pick up like they were this time last year, but sadly that will never happen.
I have no intentions of insulting any devs, I truly appreciate the work they have provided us, and I haven't contributed anything particularly useful, so I am in no position to do so, but this is just how I feel.
When I look through forums like the S2, I envy the development... even after a year, ROMs are still on full scale, with so many choices to choose from...
Sent from my GT-P1000 using Tapatalk 2

Unfortunately Oly I don't think that you can compare the DS to the SGS2. We unfortunately were never a main stream device (like the SGS2), we sadly missed the boat, with the Sensation coming out shortly after our release, I reckon that the focus went from DHD to Sensation and the limelight never really shone on us long enough to get a main stream following.
The Samsung onslaught appears to unbeatable currently sadly even the One series hasn't really made a dent.

We must all accept the inevitable that our device (Desire S) is by fact outdated with the phase of how fast mobile technology comes. That said, sooner or later, our thread will surely die.
It is with great appreciation that our devs are prolonging the inevitable. Most will surely be having new devices comes these coming months. I too will be leaving the scene as a new device is surely coming at hand in two months time.
Everything in our life changes. One must be oblige to flow with it. If not, one will be left alone and at lost.
P.S.
For an answer for the OP. THERE WILL BE a stable JB/ICS ROM as long as a dev will be willing to still work on it. If not, then THERE WILL BE NOT.
Long answer short: we will never know unless there will be one.
Moral of this post: learn to accept the truth that you have to move on to a new device if you really want to have a stable up-to-date ROM, even past JB.
Sent from my HTC Desire S using xda app-developers app

Well, that was philosophical!
Sent from my HTC Desire S using xda app-developers app

Skanob said:
We must all accept the inevitable that our device (Desire S) is by fact outdated with the phase of how fast mobile technology comes. That said, sooner or later, our thread will surely die.
It is with great appreciation that our devs are prolonging the inevitable. Most will surely be having new devices comes these coming months. I too will be leaving the scene as a new device is surely coming at hand in two months time.
Everything in our life changes. One must be oblige to flow with it. If not, one will be left alone and at lost.
P.S.
For an answer for the OP. THERE WILL BE a stable JB/ICS ROM as long as a dev will be willing to still work on it. If not, then THERE WILL BE NOT.
Long answer short: we will never know unless there will be one.
Moral of this post: learn to accept the truth that you have to move on to a new device if you really want to have a stable up-to-date ROM, even past JB.
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
Haha I don't know about you man... but I'm a student and learning to move on to a new device is not as easy as it sounds. I'm stuck with a contract until next April. So ill be sticking around here till then xD
Sent from my Desire S using xda app-developers app

I think custom roms have advantages, but it's not easy for the devs to make them perfect.
If i compare the stock ROM of x10mini/pro with custom cm6/7 ROM, the stock ROM sucks...

SteveO_ said:
I think custom roms have advantages, but it's not easy for the devs to make them perfect.
If i compare the stock ROM of x10mini/pro with custom cm6/7 ROM, the stock ROM sucks...
Click to expand...
Click to collapse
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.

anazhd said:
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.
Click to expand...
Click to collapse
At the moment i'm using stock rom (sense) too, cause my prefered custom rom has still a problem with battery drain...
As soon this is fixed, i'll go to ICS DS again...
But at all, the ICS stock rom is working very nice...

Fallout v4.4.0 is pretty stable to me, been using since a while now.

Tonight i'll try Fallout 5.0, let's see how it is... :highfive:

MIUI 2.8.x or 2.9.x
I recently flashed MIUI 2.8.17 and its been a joyful ride! It is very very stable. I had to reboot only once so far and that is an intermittent bug. BT/WiFi/Tethering/Camera etc. etc. everything works! (hard to find that in an ICS ROM)! Its my daily ROM now.. :good:

Fallout 5.0
I got myself S-off and rooted 2 days ago.
The first custom rom Ive tried is Fallout 5.0. Only one day into my test and it's very stable and fast compared to stock gingerbread.
I'm very pleased with it so far :good:

anazhd said:
htc stock rom ( sense ) , indeed, the best stock of all android. I've been using samsung, motorola and sony, but nothing is better than sense.
Click to expand...
Click to collapse
My Gingerbread stock rom experience made me root my phone. I kept getting the white screen with the green HTC logo and no matter what I did it always came back. I have now tried out about 5 or 6 custom roms and this issue no longer appears. Of course there are other issues, some of which are serious. But there are ROMs which are in general more than good enough for day to day usage. I currently use ICE-DSv5 but for example Fallout v4.4 is stable (v5 is not stable for me but it is for a lot of people).
If you are interested you can look at my other thread here called "My First Rooted Phone" for an overview of my experiences so far.

Blindbean and Codename are great JB roms, not fully stable, but good to work with.

Yes. I flash every recent roms so I know how they are. I started this thread to get an idea of if it is possible to have a stable rom. The devs have been struggling with major bugs since early this year and we're still stuck with the same bugs we had prior to the release of the kernel sources. I do know it is a difficult process. But wanted an answer from a dev. Is it possible for us to have working front cam, proper video playback, etc. ? This isn't complaining btw just wanted an answer other than "be patient. Be thankful. It's good enough"
Sent from my Desire S using xda app-developers app

if you want stable flash rooted stock. it has everything you mentioned. combine it with tweaked kernel and you have even more...