Gingerbread source being pushed today! - G2 and Desire Z General

http://groups.google.com/group/android-building/browse_thread/thread/091172a81604c8a0?pli=1
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
I'll give more details once the source code is available. However,
there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some
points in time when the master branch doesn't build. Sorry about that.
If you're working on the master branch, I recommend that you don't
sync until I send an "all clear" when I'm done and things look good.
Other branches are expected to work fine as soon as their manifests
are created.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
If you're not going to immediately work on porting Gingerbread to
devices with the intent of distributing the result to end-users, I'm
kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Thanks for being patient.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
Yay!
Let's bombard Cyanogen's Twitter! J/K``

Hope something good for my incredible comes out of this
Sent from my ADR6300 using XDA App

Can't wait! The quicker the source is released the faster we will have Gingerbread baked into our roms

First one to get an AOSP build of 2.3 running on the G2 will be my new hero.

lol @ the software engineer having two Nexus B's already ;D

silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...

Wowo!!!!! Can't wait! I've been on the virtous for some time now, because I really like the sense shell, but it's strait over to CM again (been there many times allready) when 2.3 comes!!!

Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!

@cyanogen
Prepare for spam!!

I just looked at aosp and I see next to nothing updated yet so I dunno

@cyanogen WILL come through quickly for the G2. I'm sure of it.

Shady Gambino said:
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
Click to expand...
Click to collapse
Why wouldn't you permroot now? Nearly double CPU clock, the ability to disable throttling, superuser access.
In my experience, the first implementation of new code is often quite buggy. While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.

tornado9015 said:
While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
Click to expand...
Click to collapse
That's half the fun

Follow cmrsc on twitter for updates on compiling a blue-berry flavored gingerbread.
Sent from my HTC Vision using XDA App

sino8r said:
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up

silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".

Come on msm7x30 support!

Blades said:
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Click to expand...
Click to collapse
He probably has a stack of cell phones and probably tries to brick some of them on purpose. He probably just gives back the bricks to Samsung.

ctraywick1 said:
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
Click to expand...
Click to collapse
Thanks, I guess... hard to detect sarcasm in writing My point was... bricks happen!
Just flashing the proper way, epecially packed ones with a bootloader, you can brick even when you do everything correctly. I've flashed over 500 phones (may be more) and it will happen. The nice thing is though, when you are a cell tech, just pop out the board and get another one. Manufacter's warranties for carriers are surprisingly lax... so, yeah we did brick some on purpose, lol

Cyanogen via twitter:
My G2 seems to have Gingerbeard on it. How did that happen?
Click to expand...
Click to collapse

Related

Open Source (Kernel and System) Release Date?

Haven't posted much here and read through the threads under the Evo board. Im not familiar with how HTC handles Android releases. My only Android and open source experience has been with Samsung and the moment.
Any rough ideas how long HTC has historically taken to release the open source for an android phone after its public launch? 2-3 weeks? 2-3 months?
Does anybody know if they will release kernel source (2.6.29) and Android 2.1 source or just their modified kernel source?
Hope these questions aren't too far off...
I think you may have to wait a while for that.
david279 said:
I think you may have to wait a while for that.
Click to expand...
Click to collapse
i'm curious if anybody has any information which i wasn't able to find regarding this. the answer would either be based on previous information, inside information, or speculation. as i inquired previously and to combine your answer, is "a while" 2-3 weeks or 2-3 months? if nobody has any idea, that wouldnt surprise me either...
joeykrim said:
i'm curious if anybody has any information which i wasn't able to find regarding this. the answer would either be based on previous information, inside information, or speculation. as i inquired previously and to combine your answer, is "a while" 2-3 weeks or 2-3 months? if nobody has any idea, that wouldnt surprise me either...
Click to expand...
Click to collapse
Well it took what, 5-6 months for the release of the kernel for the hero, so a while could be a long time.
the htc increadable source is already out, I don't think it will take that long at all
The problem with the Hero was due to GSM and CDMA variants.
-------------------------------------
Sent via the XDA Tapatalk App
kyleblakepeters said:
The problem with the Hero was due to GSM and CDMA variants.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Not really. HTC had the Kernel source, they just sat on it. Most of the Android devices HTC has released has taken about 6 months to get the kernel source. I would expect no different with this device. However, considering the Incredible source is indeed already released maybe they are changing that. Regardless, is the kernel version actually still 2.6.29 or do the newer devices have a newer kernel? I thought the N1 used 2.6.31.
chuckhriczko said:
Not really. HTC had the Kernel source, they just sat on it. Most of the Android devices HTC has released has taken about 6 months to get the kernel source. I would expect no different with this device. However, considering the Incredible source is indeed already released maybe they are changing that. Regardless, is the kernel version actually still 2.6.29 or do the newer devices have a newer kernel? I thought the N1 used 2.6.31.
Click to expand...
Click to collapse
android 2.1 released for the samsung moment is on 2.6.29. idk how accurate of a gauge this is for the EVO.
thats unfortunate it took them so long to release the source code. i thought there was a time constraint on the GNU open license giving them a short time period between public release and deadline to release the open source. i could be wrong though...
HTC just released the Incredible's and Eris's source codes 5 minutes, ago via Twitter, so I don't think we will wait long.
htc
Because we know how much you developers love source code...Legend, Incredible, Desire, and Eris(2.1) kernels are online. http://ht.ly/1MODf
Click to expand...
Click to collapse
TheBiles said:
HTC just released the Incredible's and Eris's source codes 5 minutes, ago via Twitter, so I don't think we will wait long.
Click to expand...
Click to collapse
It's been up on their developer site for a couple weeks at least
chuckhriczko said:
It's been up on their developer site for a couple weeks at least
Click to expand...
Click to collapse
Eh, well it was news to me.

No Custom ROMs for Honeycomb

Well via to an article over at Android Central, and Bloomberg: Business Week, its been said by Google that they wont be releasing the source code for Honeycomb. The reasoning behind it apparently is to keep your small time, crap companies, from trying to put 3.0.x onto a device and giving android a bad rep. So I dont think we will be seeing any ROMs until Ice cream.
Source: http://www.businessweek.com/technology/content/mar2011/tc20110324_269784.htm
http://www.androidcentral.com/google-not-open-sourcing-honeycomb-says-bloomberg
Google Holds Honeycomb Tight
It will delay distribution of new Android tablet source code to outside programmers
We'll get it eventually..
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
jmc2543 said:
Eventually we may but they are saying they dont want craplet devices coming out that aren't intended to run HC. Yea I can see them releasing the source code, after they get a version of this new style android that runs on phones and tables, AKA ice cream. They also say that it wont be release in the foreseeable future, I take this as dont loose sleep waiting for it.
Click to expand...
Click to collapse
+1
running Tiamat .1.1.6 for the OCing & USB
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
When it comes to preventing carriers from putting money sucking spamware on your phone googles "that would jepordize the very definition of open source". But when it comes to releasing the source code for developers to smooth out and patch their half baked OS so each consumer (who paid an unwarranted premium for their device in the first place) can have the free choice of how they would like their "open source" OS to function googles.
Say it aint so.
MOD EDIT: Language
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
orionshock said:
I Saw somewhere that they are only holding the source code back from the masses to ****up. you can still request & sign for the source code if you ask google directly.
IANAL, but if the owner of the source code decides not to publish, isn't that their right? regardless what "Licence" they publish it under?
Click to expand...
Click to collapse
Not if they have already distributed product using it. AKA Xoom.
colbyb25 said:
I think people need to relax on this issue. Google will release it when they are ready. Either way I can almost guarantee that it will be leaked. The Dev community always gets what I needs. To be honest it is a little annoying that the android community freaks out over everything. Everyone just relax. I am going to go back to enjoying my Xoom.
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
I believe this is not just a simple issue.. leaked <> AOSP
one thing for sure, if we don't have HC AOSP, never expect custom rom..
this android open source is going into nightmare .. Google please remember this "Don't be Evil" ..
this is ur second Evil move after c&d letter to cyanogen..
peace all..
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
So if I type assassinate and then.....Google, do u think they will send a team of nerds and lawyers to get me. Be a martyr...start a revolution..Viva la Zoom
...j/k. Not serious
Sent from my ADR6300 using XDA App
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
whitedragon33 said:
+1
running Tiamat .1.1.6 for the OCing & USB
Click to expand...
Click to collapse
Ftw
Kcarpenter said:
Curious why there haven't been any Zip Aligned or Deodexed roms put out, even if that is as far as we can go other than Kernel Tweaks.
I'm not complaining, just curious.
I guess well have stuff in due time.
Click to expand...
Click to collapse
Bauxite said:
You don't need the source code to make a quality rom.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Here's the deal guys. The legend JesusFreke has stated that he needs source to update his programs smali / baksmali. The are the base tools for decompiling framework and apk.
we cannot deodex rom without those tools. Thus we cannot modify smali and XML. So we are stuck with a stock rom. But we have kernel source which is far more important.
So, its all good for now
Is it still possible to theme the Stock ROM without deodexing? I thought I read somewhere that you could but it was not as easy.
Samsung probably pissed them off for putting their craptastic TouchWiz on the new Galaxy Tabs.
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
th0r615 said:
I bet you we'll see the Honeycomb source around the I/O in May. I bet we'll also get the deal on 2.4 and some hints for the next version which will unify the tablet and phone forks back into one.
Click to expand...
Click to collapse
3 weeks after io..I think that's how long it took for froyo source.
Sent from my Samsung-SPH-D700 using XDA App
My guess is Google is probably more worried about all the bagnasty China tabs that have flooded the market all running earlier versions of Android.. Imagine the cheap China crap that would hit the streets if they released the HC Source.. No way the masses would pay the big bucks for the Google sanctioned Tablets when they could pick up a China tab for pennies on the dollar..
While I don't think Google is doing themselves any favors by taking this approach, I would point out that folks would probably make more headway spending time porting Ubuntu or one of the other Linux distributions to the Xoom than trying to prevail on Google to change their ways.
Let's Take A Deep Breath Folks
I'm going to keep this short because I'm not a developer yet, so I'm only qualified to speak as a user and as a grateful member of this forum. As I understand it, in order to be "open" the code has to eventually be released (kind of like non-packaged Linux, i.e. CentOS, Ubuntu, etc.).
From what I've experienced, the only people that DON'T want code coming to us are the carriers. When you folks develop way better ROMs than the crap with bloatware that they try to pass off to us, it hurts their wallets - BFD!!
I'm honored and proud of you guys and I KNOW that the Google probably held it for legitimate problems that they're going to fix for us. Once that's done, they KNOW that once you get a hold of it, more people are going to be exposed to it which only makes more people want future versions. that's how I got snagged by you folks, first with Windows Mobile and then with Android.
I have faith in parts of the system. I have faith in Google to deliver their end, it's the carriers and their greedy practices that I don't trust. Keep the faith folks, take a deep breath and relax. XOOM has been here for only a minute, but we KNOW that it's unlocked, it's rooted and as soon as the 4G hardware and the SD card issues are resolved, we're going to be hip-deep in better versions of the ROMs. I believe that with all my heart because you folks have shown it to me time and again.
It's gonna be great - just wait and see.

some thought about the delay on gingerbread release for Epic 4G

The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
meh, not buying it. more to gain by keeping on course. lots of phones doing it right now so bricks and problems are so expected that they can write it off.
I take this as a bad news!
Nice to see you back noobnl.
Since most phones are not on gingerbread yet, I'm not surprised if it is delayed.
Sent from my SPH-D700 using XDA App
He is saying we will have the gingerbread update on the 20th then another even more optimised update after that. So there's no delay. We will be on gingerbread it will just get better ppl so be happy
silver03wrx said:
He is saying we will have the gingerbread update on the 20th then another even more optimised update after that. So there's no delay. We will be on gingerbread it will just get better ppl so be happy
Click to expand...
Click to collapse
Exactly what I was reading. Sorry, for wandering off course, read it too fast.
Sent from my SPH-D700 using XDA App
I sorta agree with noobnl, if anything it makes it look like they are trying hard to keep it updated by having more updates...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
ecooce said:
I sorta agree with noobnl, if anything it makes it look like they are trying hard to keep it updated by having more updates...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Click to expand...
Click to collapse
really, this isn't too bad. I wouldn't call it "... look like they are trying hard..."
I'd call it here's a 'fairly' stable build. play with it while we watch XDA for the bugs, we'll tweak the bugs, then do a maintenance release to fix the bugs
If anything this is a good thing for their PR.. they've had a bad rap over the years regarding updates.. this (so far) has been a welcomed change of pace IMO
I agree.
I accept any updates with open arms.
Sent from my perfect epic
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
Of course they'll probably release bug fixes. You made a "prediction" out of something that's more or less a truism.
However, I disagree. Aside from the camera and keyboard, the Epic is very much like the Nexus S 4g. They already have complete source for that. Aside from integrating Sprint Spyware and Touchwiz, very little has to be done from the existing Nexus S 4g. Major stability issues would exist here.
Now, the Nexus S 4G does have known bugs, which is where the truism part comes in. The Epic will be subject to any bugs the Nexus has, otherwise they would have fixed it there first. It's well known that the Nexus S 4g gets sub-par data speeds. Whether or not this will be transferred to the Epic is to be determined.
You also set your margins of error pretty wide, first saying they'll be deploying ril, modem, and kernel fixes, then in your second stanza saying they'll be rolling out "optimizations". Employing fixes in the base layers critical to stability of the platform are hardly optimizations. Further, you cite 2 weeks for this prediction, and then expand it to 2 months. This is a pretty large window.
At what point in this blathering of a post did you actually make a prediction?
Again, that's just his predictions/presumptions. Don't flamed the poor guy. Just like everyone else, all are just predictions and presumptions. When updates hit your phone, then it will. Stop flaming the dude before he goes into extinction for another few months! LOL
jnadke said:
Of course they'll probably release bug fixes. You made a "prediction" out of something that's more or less a truism.
However, I disagree. Aside from the camera and keyboard, the Epic is very much like the Nexus S 4g. They already have complete source for that. Aside from integrating Sprint Spyware and Touchwiz, very little has to be done from the existing Nexus S 4g. Major stability issues would exist here.
Now, the Nexus S 4G does have known bugs, which is where the truism part comes in. The Epic will be subject to any bugs the Nexus has, otherwise they would have fixed it there first. It's well known that the Nexus S 4g gets sub-par data speeds. Whether or not this will be transferred to the Epic is to be determined.
You also set your margins of error pretty wide, first saying they'll be deploying ril, modem, and kernel fixes, then in your second stanza saying they'll be rolling out "optimizations". Employing fixes in the base layers critical to stability of the platform are hardly optimizations. Further, you cite 2 weeks for this prediction, and then expand it to 2 months. This is a pretty large window.
At what point in this blathering of a post did you actually make a prediction?
Click to expand...
Click to collapse
As soon as you have something usefull to say, post it. Until then, just read.
Sent from my perfect epic
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Sent from my perfect epic
Click to expand...
Click to collapse
What he said.
I see a lot of facts not in evidence here, and a lot of wishful thinking. My feeling is that you're sadly mistaken if Samsung worries about the appearance of "keeping up" or that not releasing updates in a timely manor is "bad PR". I would hazard a guess that less than 5% of the Epic 4G user base hangs out here, or even spends much time thinking about what OS they run. They don't care unless it's broken, and the current version isn't.
It's easy to wish for it, and even try to project your reality onto the situation, but here's the fact - Samsung is a HUGE company and the Epic 4G accounts for probably .002% of their biz. They aren't losing sleep over what the Epic user base is thinking about. Heck, a few months ago we didn't even think that GB was in the cards for the Epic.
So I guess my opinion is that it will happen when it happens. To try and read between the lines is no better than a wild guess at this point.
ccnd8 said:
Again, that's just his predictions/presumptions. Don't flamed the poor guy. Just like everyone else, all are just predictions and presumptions. When updates hit your phone, then it will. Stop flaming the dude before he goes into extinction for another few months! LOL
Click to expand...
Click to collapse
Before people flame me, I was partially being facetious. Hence the
Not hatin', noobnl.
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Click to expand...
Click to collapse
I did post my counter-thoughts. Beyond mirroring Nexus S 4g, any future patches should be mainly stability improvements in the TouchWiz/Android integration. Gingerbread, despite being a minor update in looks, was a huge update in API. A lot of stuff is likely broken that will slip QA.
There will always be follow-up patches in any software release cycle. The Epic had 2/3(?) patches for Eclair, 2 patches for FroYo, and probably no less than 2 for GB, since it'll be the last update for a while, if ever.
I apologize for posting my counter-thoughts in his thread. Next time I will make a new one.
I also apologize for coming off as attacking noobnl. I wasn't aware he had a beer flavored schlong.
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
Well if there is anyone's 2 cents around here I would put money on its noobnl. If there is anyone who knows what goes into developing the OS and what goes into making it all work it would be noobnl or Dameon87. Two of the most recognized and respected names in Epic 4g hacking history in my own opinion. Many of the newer users in the past few months have no clue who these two people are or what they have done but if it wasn't for these guys we wouldn't have squat for the Epic 4g. Before anyone doubts what these two and others have to say they should do their studying and read up on who's names are all over OneClickRoot, CWM and many other things we use constantly in rooting and hacking with the Epic 4g.
Just my 2 cents...
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Click to expand...
Click to collapse
LOL, coming from you.
Paul627g said:
Well if there is anyone's 2 cents around here I would put money on its noobnl. If there is anyone who knows what goes into developing the OS and what goes into making it all work it would be noobnl or Dameon87. Two of the most recognized and respected names in Epic 4g hacking history in my own opinion. Many of the newer users in the past few months have no clue who these two people are or what they have done but if it wasn't for these guys we wouldn't have squat for the Epic 4g. Before anyone doubts what these two and others have to say they should do their studying and read up on who's names are all over OneClickRoot, CWM and many other things we use constantly in rooting and hacking with the Epic 4g.
Just my 2 cents...
Click to expand...
Click to collapse
Oh, I agree, Noobnl, Dameon87, and k0nane are the **** around here. This community would be largely lost without them.
They're not the best though, that title is reserved for dzo, the guy who got Android working from largely scratch on the HTC Touch (Windows phone), my old community.
I'm aware of the integration aspects of Android. I've compiled my own AOSP for the HTC Touch, built a GPS driver for the HTC Touch, and done some RIL hacking / development. Further, I was employed for 3 years as a linux developer for small platforms just like these phones. Alas, I do not have the time commitment nor the strive anymore unlike those three above.
I give my hat to them, but I am more than capable of making my own highly experienced opinion.
bigray327 said:
LOL, coming from you.
Click to expand...
Click to collapse
Wait, what is that supposed to mean? I'm very helpful lol

Time to troll HTC again?

http://www.gottabemobile.com/2011/1...ist-which-phones-will-get-ice-cream-sandwich/
So where's ICS for the Shift, HTC?
We might as well start getting on them now since they held out forever on the kernel source. The shift is so under rated still.
I don't really see us "officially" getting ICS. Like Sparksco said, the Shift is severely underappreciated.
I do know we have a couple devs working on it though...
I think its a very possible we will see one because
At first I would have said no way we would get it when HTC released Sense 3.0 which only supported Dual-Core devices. That would make you think any later version after 3.0 would also be a definite no and we will never see ICS (officially for the shift) and we know HTC will have to update Sense UI to a later version for ICS
But then again now HTC released Sense 3.5 on devices which is optimized to run on Single Core phones so now if they do update Sense it leaves room to think maybe their next iteration of sense will be compatible with lower end phones to (don't take that to context to much the shift IS very powerful)
We might also see an update like the EVO got when it recieved gingerbread. It got the firmware upgrade to gingerbread but HTC still kept it at 1.0
So their is always the possibility it could be our turn for that.
and now with the Handset alliance thing which HTC is apart of I believe, part of the ruling is you have to support a device for 18 months with latest updates as long as hardware allows.
If anything we know we will be waiting longer than most devices out there anyway if we do end up getting it. The phone is underappreciated a lot, just like the article says (to be honest I was suprised they even mentioned it)
But yea its basically time to start bugging HTC as much as we possibly can for some kind of update. I know I will start
crump84 said:
I don't really see us "officially" getting ICS. Like Sparksco said, the Shift is severely underappreciated.
I do know we have a couple devs working on it though...
Click to expand...
Click to collapse
I love you crumpy but that wasn't the question!
VICODAN said:
I love you crumpy but that wasn't the question!
Click to expand...
Click to collapse
Haha.. well to answer your question.. Trololol away..
*puts on troll hat*
VICODAN said:
*puts on troll hat*
Click to expand...
Click to collapse
Let us know what they say and I'll also ask htcdev about it on twitter
Sent from my PG06100 using xda premium
sparksco said:
Let us know what they say and I'll also ask htcdev about it on twitter
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
https://www.facebook.com/htcusa/posts/231659726902311
Official response from HTC USA on Facebook:
Hey guys. If you haven't seen our latest note on ICS, you can catch it here. http://on.fb.me/vSPMMr We will be announcing more phones later so just because it hasn't been announced yet doesn't mean that it won't be in the future.
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
HTCotta said:
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
Click to expand...
Click to collapse
Either way we're still waiting. The G1 and other older phones have a more working funtional rom or ICS then we do.
Sent from my PG06100 using xda premium
HTCotta said:
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
Click to expand...
Click to collapse
Useless? We got GB kernel source code fairly quickly once we started trolling them. It is important we get an official update from HTC more than you know.
GB source code was always coming, we were quite literally entitled to it (GPL). This is not the case with an ICS update. I know that getting an official update helps immensely, but we're certainly not gonna get one by trolling HTC. It's Sprint's decision.
VICODAN said:
Useless? We got GB kernel source code fairly quickly once we started trolling them. It is important we get an official update from HTC more than you know.
Click to expand...
Click to collapse
Yes your right it is important that we get a official update. A new kernel could really help a lot even if it was a sense kernel.
Sent from my PG06100 using xda premium
HTCotta said:
GB source code was always coming, we were quite literally entitled to it (GPL). This is not the case with an ICS update. I know that getting an official update helps immensely, but we're certainly not gonna get one by trolling HTC. It's Sprint's decision.
Click to expand...
Click to collapse
It's not just sprints choice. It's a partnership between sprint and htc. We just need to express that we do want a official update to htc because htc will listen to us, and might come up with something with sprint. Sprint will not listen to us about a official update because all the do is tell htc which phones are more popular and which ones they think should get the updates first, and then htc goes on it's happy way to make a update. Meanwhile they throw in some of sprints apps (big deal). Htc does most of the work. They do all the kernels, and most of the rom development.
Sent from my PG06100 using xda premium

Share the news CM10 is out!!!

Hi all,
Wanted to share this exciting news and hope that our devs will start working on this.
http://androidcommunity.com/cyanogenmod-10-will-bring-jelly-bean-to-many-20120705/
Jelly Bean source is expected to be released by the end of the month.
Anyone hungry for more desert?
Sent from my MotoA953
that is really an exciting news
can't wait the release of jb!
Sent from my MotoA953 using xda app-developers app
yes!:laugh: cant wait!
And the code is out. Cranck up your machines and let the fun begin....
http://www.xda-developers.com/android/android-4-1-jelly-bean-source-code-released-to-aosp/
I read elsewhere the differences between JB and ICS weren't really large, so it should be "easy" (as easy as something as complex can be ) to port ICS working devices to JB.
I would love that, the longer my phone last, the happyer i am.
Looks like CM already started working on JB
http://androidcommunity.com/cyanogenmod-updates-their-status-on-cm10-jelly-bean-20120710/
which is a good new, I hope, one of our devs will take an interest on porting one to MS2, although it's a little premature for that.
Megalith27 said:
Looks like CM already started working on JB
http://androidcommunity.com/cyanogenmod-updates-their-status-on-cm10-jelly-bean-20120710/
which is a good new, I hope, one of our devs will take an interest on porting one to MS2, although it's a little premature for that.
Click to expand...
Click to collapse
Yeah it's a bit "premature", but we will probably get it in time.
If i'm not mistaken, we had ICS on our phones before the official version was available for MS4.... it speaks a lot of the "proficiency" and understanding of products of Motorola devs...
Ashareth said:
Yeah it's a bit "premature", but we will probably get it in time.
If i'm not mistaken, we had ICS on our phones before the official version was available for MS4.... it speaks a lot of the "proficiency" and understanding of products of Motorola devs...
Click to expand...
Click to collapse
Moto now should do, as they promised. Unlock boot loaders fro mobiles, which they won't support ....
Sent from my MotoA953 using xda app-developers app
_panter said:
Moto now should do, as they promised. Unlock boot loaders fro mobiles, which they won't support ....
Sent from my MotoA953 using xda app-developers app
Click to expand...
Click to collapse
Well, according to this:http://androidcommunity.com/motorola-promises-unlocked-bootloaders-coming-soon-20120711/
Moto just promised to "try" to unlock BL what they were doing for the last couple of years but time will show, i guess...
Megalith27 said:
Well, according to this:http://androidcommunity.com/motorola-promises-unlocked-bootloaders-coming-soon-20120711/
Moto just promised to "try" to unlock BL what they were doing for the last couple of years but time will show, i guess...
Click to expand...
Click to collapse
I'm always "reassured" by people BUILDING/CREATING AND SELLING PRODUCTS when they explain to you they can "try" to do something that is super easy, and haven't made the slightest progress in 1 year and a half on it.
It makes you want to believe they are able to do more complex things on their products without botching it... not.
Megalith27 said:
Well, according to this:http://androidcommunity.com/motorola-promises-unlocked-bootloaders-coming-soon-20120711/
Moto just promised to "try" to unlock BL what they were doing for the last couple of years but time will show, i guess...
Click to expand...
Click to collapse
We can understand why we won’t be holding our breathes...
Looks like the ball had already started rolling on Defy front
Which is a good sign for Moto community and especially for us. Time to hold your breath.
Megalith27 said:
Looks like the ball had already started rolling on Defy front
Which is a good sign for Moto community and especially for us. Time to hold your breath.
Click to expand...
Click to collapse
Or not.
It's not like we don't have our hands full finding new bugs on the CM9 port already... (yeah i know, there is not much, and most of them are known already ).
And there is still quite some functionality of CM9 to be merged too, like themes support and so on.
But yeah, it's a good thing people already started working on JB/CM/10 port (makes you wonder what the overpaid devs working for constructors/operators are doing in their days, since having access to far more than us, and not having to work with the locked bootloader restrictions, they still haven't ported most of their december 2011 devices to ICS... ).
Hell at that rythm, MS2 will have JB before the official ICS hits the MS4...
Ashareth said:
Or not.
It's not like we don't have our hands full finding new bugs on the CM9 port already... (yeah i know, there is not much, and most of them are known already ).
And there is still quite some functionality of CM9 to be merged too, like themes support and so on.
But yeah, it's a good thing people already started working on JB/CM/10 port (makes you wonder what the overpaid devs working for constructors/operators are doing in their days, since having access to far more than us, and not having to work with the locked bootloader restrictions, they still haven't ported most of their december 2011 devices to ICS... ).
Hell at that rythm, MS2 will have JB before the official ICS hits the MS4...
Click to expand...
Click to collapse
Gotta love your optimism, buddy
But I think, Alex is doing an amazing job of taking ownership of CM9 and tiding things up. I read on his tweet that he has resloved the flash conflict issue, so we may be getting an update this weekend. (hopefully)
Regarding HW keypad, read your post on CM9 thread, I'll have a look into that when I'll be home and have all my tools. I use qwerty, so I fixed the file for my own convenience to be able to have caps lock on double press of shift button.
But, you're most certainly right, it's not like we will have JB working from day one and it's gonna take a lot of effort by our devs to make MS2 stand tall in front of the big boys lol afterall this is probably the best hw keypad device in the market.
And for now we just can watch closely how thing are developing for Defy
Megalith27 said:
Gotta love your optimism, buddy
But I think, Alex is doing an amazing job of taking ownership of CM9 and tiding things up. I read on his tweet that he has resloved the flash conflict issue, so we may be getting an update this weekend. (hopefully)
Regarding HW keypad, read your post on CM9 thread, I'll have a look into that when I'll be home and have all my tools. I use qwerty, so I fixed the file for my own convenience to be able to have caps lock on double press of shift button.
But, you're most certainly right, it's not like we will have JB working from day one and it's gonna take a lot of effort by our devs to make MS2 stand tall in front of the big boys lol afterall this is probably the best hw keypad device in the market.
And for now we just can watch closely how thing are developing for Defy
Click to expand...
Click to collapse
Being optimistic is nice sometimes, and it's quite easy when people like Alex works so fast AND pretty much everything unlock around the same time (in a short time we had the camera, the 720p decoding (and encoding i think) and hwa unlocked for our phones ), but yeah, i know it'll take time, but i'm not in a hurry anyway, my phone is more than usable on a daily basis for what i do, everything else is "added benefits".
For the keyboard, if you can find how to change that, and explain to me how to do it, i would be glad.
do you think there will be ever some release for ms2?
mondkrater said:
do you think there will be ever some release for ms2?
Click to expand...
Click to collapse
The code is very similar to ICS so the cyanogen team think any phone that can run CM9 will probably be able to run CM10, which is promising
Sent from my MotoA953 using xda app-developers app
Quarx on Defy front is on fire!!! He managed to make audio work with some help from other devs and also video recording.
I am saying by Friday he will have complete pre-alpha version of CM10 for Defy.
Hard to explain but I am kinda excited, although I get an impression that Defy sees more love from devs than our MS2 and can't find a reason why
Megalith27 said:
Quarx on Defy front is on fire!!! He managed to make audio work with some help from other devs and also video recording.
I am saying by Friday he will have complete pre-alpha version of CM10 for Defy.
Hard to explain but I am kinda excited, although I get an impression that Defy sees more love from devs than our MS2 and can't find a reason why
Click to expand...
Click to collapse
That's good news.
Quite some reasons actually for the far more active Defy :
- there is far less versions of it (he don't have like 3/4 versions just for the countries outside the US ), and from what i've read, the Defy is roughly the same everywhere, unlike the Droid2/Droid 2 Global/MS2
- there wasn't the "oops, you can't downgrade anymore" update on it i think
- it's a more "mainstream" phone than the Droid lines (strangely, the phones with hardware keyboards are "niche" phones, wonder why when they are similar in price, size and perfs to non hw ones )
But hey, good thing the MS lines of phones share so much hardware and similarities with other more active phones like Defy/Atrix, makes it easier for us having something working.

Categories

Resources