Related
The shipping ROM of the HTC EVO 4G has now been leaked. The RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe file is the official ROM present on the devices that will go on sale on June 4th (and probably originates from one the handsets offered yesterday during Google I/O). You can grab the file here. I guess that the next logical step will be an attempt to port this ROM to the HTC HD2.
http://www.mobiletechworld.com/2010/05/21/official-shipping-htc-evo-4g-rom-available-for-download/
I wonder how long it will take......Hopefully not longer than June4th
SPENONE said:
I wonder how long it will take......Hopefully not longer than June4th
Click to expand...
Click to collapse
My prayers are with your post
plzlordplzlordplzlordplzlord.....
Im sure the awesome modders here in the greatest mobile phone fourm in the UNIVERSE can work their magic
hd2 is watching u!
reorx24 said:
plzlordplzlordplzlordplzlord.....
Im sure the awesome modders here in the greatest mobile phone forum in the UNIVERSE can work their magic
Click to expand...
Click to collapse
+1 lol. can't wait to see android on this hd2.
I think it is better to wait for froyo if this rom can be installed on the HD2.
this i would love to see
Could someone who knows about the difficulties associated with porting ROMs quickly describe how feasible getting a work of port of android from the EVO 4G over to the HD2 would be?
I imagine the fact that the camera is different would cause problems?
laserviking said:
Could someone who knows about the difficulties associated with porting ROMs quickly describe how feasible getting a work of port of android from the EVO 4G over to the HD2 would be?
I imagine the fact that the camera is different would cause problems?
Click to expand...
Click to collapse
Lawl, you guys must be smoking some pretty good pot. This will take months. You are assuming that every single internal part save for the camera is identical. I'm pretty certain it won't be. It'll be a long time before any port of Android is working on the HD2. Until then, it's best you not get your hopes too high because you'd surely be disappointed if you think a working port is feasible in 4 ~ 8 weeks.
this topic has been beaten to death over and over guys. i'm not trying to come off as a ****, but please search and read before making posts, because it upsets the devs. A LOT of parts are different between the HD2 and EVO, they don't even use the same touchscreen. This is going to take some time. Be patient.
a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.
PoisonWolf said:
Lawl, you guys must be smoking some pretty good pot. This will take months. You are assuming that every single internal part save for the camera is identical. I'm pretty certain it won't be. It'll be a long time before any port of Android is working on the HD2. Until then, it's best you not get your hopes too high because you'd surely be disappointed if you think a working port is feasible in 4 ~ 8 weeks.
Click to expand...
Click to collapse
I've got no such expectations, for one I pointed out at least the camera is different and I assume a whole lot of other stuff is too.
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.
laserviking said:
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.
Click to expand...
Click to collapse
The knowledge that a hefty paycheck is arriving at the end of every two weeks and that if they don't perform, they'll get replaced with another person who is qualified and willing to deliver on said schedule. Things change when you do it as a hobby and when you're struggling to make a better life for yourself and/or spouse and kids.
Even a somewhat working version of Android on the Blackstone came out what, 12 months after its release? Making Android work on a Windows Mobile device is not some plug and play magic or drag and drop process as a lot of you are making it out to be (not directly at you, in general). While I'm only a beginner in programming, I know the difficulty that goes into making a good single working software, let alone making an entire OS work on a completely different set of hardware.
laserviking said:
I've got no such expectations, for one I pointed out at least the camera is different and I assume a whole lot of other stuff is too.
Anyway, here's a question I've never seen addressed in any topic but is interesting for layman plebs:
What information do official HTC devs have access to which XDA devs don't, which makes churning out working drivers, etc. for phones doable for the former and nigh-on impossible for the latter? Please don't misinterpret this post as accusing XDA devs of being lazy or anything, I'm just curious as to why it's so difficult.
Click to expand...
Click to collapse
The official developers get the hardware datasheets from the manufacturers and software apis because they are licensed to work on these devices. If xda devs got those things, it would be much easier.
CraigBirnie said:
a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.
Click to expand...
Click to collapse
Android has not been ported yet. I don't know where you saw that, but its probably fake. There have been videos of WinPhone 7, but it hasn't been established whether its fake or not.
CraigBirnie said:
a quick Google search will reveal picture and video evidence of this already working, along with Windows Phone 7 succesfully ported on the HD2. problems arise with the assignment of the hard buttons more than anything else.
Click to expand...
Click to collapse
Oh hey, thanks for the link.
Kids on here are incredibly stupid.
zarathustrax said:
The official developers get the hardware datasheets from the manufacturers and software apis because they are licensed to work on these devices. If xda devs got those things, it would be much easier.
Click to expand...
Click to collapse
Thanks! I knew there had to be a missing link somewhere.
I do not want to upset anybody, just trying to get some understanding of the entire upgrade to a new OS version.
I'm a programmer myself, but on Windows platform and mostly do middle tier business server side apps. Do not know a thing about Linux and android. But had some java experience in the past.
I wonder why we cannot get Froyo so long? Ain't the sources open? Even if we do not have some drivers, these parts cannot change dramatically from version to version. Published API must be stable...
Is this about Dalvik JVM? But, I guess this must be in released ROMs for other phones in the line.
What's the deal? Will appreciate some explanation here.
Android is open source, but that is only the operating system and the kernel, but the drivers and RIL that make the device actually functional are the issue as far as I'm aware. From what I've read here and in IRC, Samsung gave us a hack-job RIL, which is causing many of the issues with getting an AOSP ROM fully compiled and working. I think there may be some driver issues as well to be worked out yet, but I feel those are less important than getting things like phone/data/messaging working. I'm guessing there are more technical reasons why they can't just get 2.1 or 2.2 built from source, but those are probably the big issues.
Honestly, it boils down to Samsung.
Put simply, they're crappy coders (as HTC once was many moons ago), or they're just hella lazy (I strongly believe its the former, given RFS and this RIL mess). Most companies are pretty crappy coders, but most of the time, it doesn't interfere with major things, like OS upgrades.
That, plus the lack of effort or support on Samsung's part, has me never wanting to buy another Samsung phone again, or ever recommending an Android phone from Samsung....
I'm gonna do my best to find in my next phone another quick processor with a nice super AMOLED screen and be done with Samsung, I've had enough, and I'm a very patient person....
What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)
CNemo7539 said:
What is RIL? Is this Radio Interface Library?
Is it linked into kernel or other module? Not extractable at all?
As I imagine it to myself, if it is some sort of dll or package, it shouldn't matter if we do not have source, because it's interface have to be already strictly defined. It doesn't matter if it is buggy. It should work with any android version.
Please correct me if I'm wrong.
P.S. I have Dell Axim v50x and people already created ROM from scratch! However it doesn't have RIL. ;-)
Click to expand...
Click to collapse
if it could have been done, birdman would have done it already
Well I think it's a valid question. Some might think it tedious or obnoxious, but absolutely valid. This is a development forum after all. The reason we don't have 2.2 isn't a hardware limitation, so it must be a practical one -- or yes it would be here.
But I'll just speak from speculation in the hopes that someone will correct me. For god sakes this is a development forum! We've got releases, we have fixes, we have patches, we have complaints, we have gossip. I'd love to see all the _development_ discussion I can get.
From a wider puzzle-piece perspective, I would like to know what is missing. We have working drivers. We have working hardware. We have full source from Google for the operating system. There are several other android phones on Verizon, a few even have Froyo. Sprint currently offers a CDMA Galaxy S phone (Epic) with android 2.2, and that phone possibly shares some hardware (though the WIMAX radio is totally irrelevant to us).
I'm not up to speed on exactly what the RIL is, or how it gets plugged into the android kernel. The RIL (Radio Interface Layer) is a software layer between android itself and the drivers controlling the phone hardware. Google provides some samples for a carrier to create one to govern communication on their network. I'd expect one issue of randomly hacking something like this, is if you are taking over your radio hardware's communications, then you have the capability of putting unwanted data on the network, which might even be criminal. Am I being extreme? So, perhaps we can't touch the RIL and need to wait for it to be spoonfed to us by those that bought the radio band from the FCC. Perhaps this code is inexorably married to particular hardware, unavailable for reading, or even encrypted. Maybe the primary limitation is the royal pain in the apricots that it is to inspect, decompile, and reverse engineer binary code.
But what if we could do something?
My understanding is the RIL is only a carrier-specific interface to the underlying hardware. Shouldn't it be similar between phones, even with wildly different hardware? Shouldn't its interface also be similar between close versions of android? The Droid 2 is a verizon phone with a RIL that does indeed work with Froyo. What I'd like to know is A) can another phone's RIL be extracted within the same carrier, and B) Being the abstract entity that it is, what prevents it from being married to the Fascinate's hardware base?
To be honest, I ardently believe a frank discussion (sans opinions, complains, problems, just productive discussion w/ a smattering of facts) BELONGS in the Development forum.
I'll stop here, in case this thread dies, as so many of mine do.
Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App
I don't know anything about how the RIL works, but I would assume that it could only be easily ported from one device to another if they were using the same chipset in the underlying hardware for the phone. I doubt you'd be able to take the Droid 2/X RIL, and take it to the Droid 2 Global or Droid Pro. Given that, I'm guessing that you can't really take a RIL from one phone and put it on another without extensive work, since most OEMs tend to use different hardware in their devices. From what I've heard, there is a semi-working AOSP build floating around, so the devs are trying, but Samsung's crappy source to work from is not making things easy for them.
There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App
ksizzle9 said:
There are actually some semi-working builds of aosp floating arpunfld but the last time I checked one out it was missing one thing that I consider to be kind of a biggie. It couldn't quite make calls. I'm sure they have it to make calls now but there is a reason its not out to the forums yet. I agree withstand nuts up there. Thanks you Samsung.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
i believe there was still no radio at all in aosp, and the hope is that 2.2 can fill in the gaps
Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?
CNemo7539 said:
Wow, wow, wow!
Why do we need another phone RIL? Current one from SF at hand should do perfectly. Did Google changed something in android API related to a RIL? I don't know for sure, but never heard or read anything making me think they did it. Android should call RIL and that is set in stone. ALL calls signatures must to be known. Something new may be added, but it is not show stopper.
So, I still do not understand - is it not extractable or what?
Even if not and it is somewhere in protected memory, encoded or whatever, Froyo slapped on top must work, IMHO. And sources available. So, why we stuck waiting for Samsung?
I know, one may say - do it yourself if you are so smart... Once again, I just want to understand root of the problem. I probably can do something, because I have degree and experience. But, it will take me forever. From what I've tried and seen learning curve is very steep.
On the other hand, skilled developer might simply need fresh look at the problem... May be guys just hitting wrong wall?
Click to expand...
Click to collapse
is it possible? perhaps...but the 5 or so guys who really develop for this phone havent been able to get it to work....nor is aosp working 100% on any galaxy s phone
Response from developers?
Anyone?
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
Agree get your ass moving so we can have teh honeycombzzzz. Quit being such a lazy stingy jerk and get us our AOSP!
ksizzle9 said:
Jt1134, adrynalyne, and fallingup(angel12) are all very capable as well. This is solely the fault of none other Samsung.
Edit: to answer your question, i think that.the answer about RIL is no, although i dont have a good qualified answer about why the RIL from D2 cant be ported im sure that if it could have, it would have. Sorry thats not a better answer.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
yes i was just pulling one dev name out for the heck of it
but i subscribe to the "if it could have been done, it would have been done"
adrynalyne said:
Yes, you know so much, we are waiting for you to fix it.
Hurry the hell up.
Click to expand...
Click to collapse
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
that may be a problem for those who just stay here as virtually everything is irc only these days...or the majority of it anyway
CNemo7539 said:
I don't care what you did for community! But you behave like f****g jerk.
No real explanation for the rest of us? Stay on irc, we will survive without your comments here.
Click to expand...
Click to collapse
How many different ways do people need to say that "it's being worked on"? The devs are doing a lot of work on our device, but also working with other stuff, all in their free time. Follow the stuff they do on Twitter and github, or join in on IRC.
Attitudes such as your's are precisely why the devs have stopped posting stuff here. You act as though it's a simple process to do things, when it isn't, especially when Samsung gives you a crappy base to start from. The devs have to first get Samsung's source fixed and cleaned up, then start on whatever it is they want to work on, all while finding more bugs and issues that need fixed, primarily all stemming from the crappy source. If you want to be angry at someone, make it Samsung, not the few devs that are working on our device.
Sent from my StupidFast Voodoo Fascinate
As I said - I will survive. I'm OK even with not rooted stock.
Was it so difficult to answer what the real problem is? I don't know what is the problem with this generation? Do I need to be on FB, irc or whatever to get the answer? Why do not answer in place? Ain't it this forum purpose?
No, seems like I need to kiss somebody ass to get meaningful response these days... That way he can maintain his "super god" status.
I do believe I've been pretty polite stating my question, even though English is not my native language. What generated so much sarcasm?
Now, I appreciate everything that these devs have had to offer. I've tried different Custom Roms (With Core Cell 3 being the most stable I've experienced, outside of the annoying Opera Mamory bug)...Android builds...and all that great efforts you guys Put forth.
I look at all these threads and Roms and see the same thing over and over...bugs...bugs....and more bugs...
The most stable Windows Rom I've truly experience is the stock one...lol...not being a smart a$$ at all. Everything just works. Take a registry editor to it and it's provided the most stable platform with Core Cell 3 a hair away from it.
Now, with Android, I see constant bug reports. I mean, people seem to have a great appreciation for the builds and love them, but it always follows up with a major bug...or even worse...lots of little bugs.
What I don't understand is why don't all you devs get together and build the "XDA" Custom Rom or "XDA" Android build that gets undiveded attention and all resources so to make it truly BUG free? Once that has been accomplished...then we can go ahead and try these test builds and play with them...
Now, I say this with a great deal of respect, having worked with developers before I know how fragile the ego's can be
It's also my experience with those same developers that taught me complete focus of resources surfaced the best result.
I mean, an effort like that is something I would pay...eeerrrrr....donate too.
Android seems to be the future for the HD2, at least I think so...some may have a different opinion...that's cool. But as much as I actually like WinMo 6.5...and WinMO 7 showing signs of being a demo at best on the HD2, Android has a future.
I think it would be a great idea for you guys to focus on one thing at a time until it's at a state you can consider it marketable...not that I'm saying that's what you should do...sell things and all.
I would even think it would be cool to take WinMo 6.5 and change it into something completely different and better than what Microsoft settled for...I always promote making Big Brother look silly with a superior view of their own product.
My point is...no matter what platform or approach...get together on it...I bet the result would be far more productive.
I fear though that this idea...no matter how much sense it makes...will not come to fruition...WHAT THE DEUCE!
Looking forward to your thoughts.
well i came up with this idea http://forum.xda-developers.com/showthread.php?t=902534 and would need a thew devs to work on it,about having our own unoficiall Android Rom,Something wich we can say is our own HD2 rom not direct ports if you know were im coming from and pretty much bug free and stable and fast.i know a thew devs came together to create nand so why not do it to create a rom
Thew?
Sent from my HD2 using XDA App
Hah, bug free... That's an interesting idea. The last bug free thing I saw was my Nokia 3210. Since then even my microwave ovens get bugs.
The devs do work together for the most part... different problems get solved by different devs, and they credit each other. I think its amazing what they've accomplished. You should be more than happy with how well we have a port working. I never thought it would get as good as it has, especially as quick as it has. Just look at the Raphael or blackstone... they've been working on ports for those devices for years and are nowhere close to where we are, and might never be.
The devs are doing what they can. This is their hobby... they're gonna work on what interests them. You can't expect them to all work on what you want them to... they would lose interest and we wouldn't have so much innovation. Plus a little competition can bring the best out of a person.
Sent from my HTC HD2 using XDA App
Well most of the bugs in Android are at the kernel level, and there is already a group of developers working on that same piece of software together.
You also have to keep in mind, as other users in this thread have already said, that no software will be without bugs.
I guess...I just know with absolute confidence this idea will work best. Nonetheless, I understand. Also, it's not what I want?...its about completing a task these forums have already put in motion...just at a more effective manor.
i want sense build base on desire hd or z
its will be lite enuf to run from RAM and boot fast
the Data.img will be backed up in the nand but will work from SD card for better performance
that's what i think is perfect to me
RAM gives boot time and less battery drain
data.img on nand and sd card is for better iops and for backuping ur info fast with CWM
u can remove anything u dont use cos it wont be in the RAM
all most important things like email / messages / people browser will run from RAM to get the speed-est performance
As has been stated, aren't most the bugs pretty common to all builds in one way or another therefore indicating that the problem is at the programming level rather than the rom developer level.
IMHO find one you're happy with and take the bugs with a pinch of salt - the HD2 is still one of the most exciting handsets about and to have the ability to experiment with all this thanks to the ROM guys and the tools developers on here is just blooming fantastic!
Stop moaning and appreciate what we have here!
Personally, I think this is a bad idea.
I'm very happy to have multiple developers all working on different projects and supplying us with different ROMs. For example, I hate HTC Sense and prefer stock Android, but lots of people disagree with that and think Sense builds are superior.
If all the devs worked on only 1 ROM then that's all we'd have. 1 ROM. My phone would be the same as yours, and yours would be the same as every other person on the forum. That would be pretty darn boring! If you ask me, more choice is better.
"If everybody looked the same, we'd get tired of looking at each other."
I never said stop working on different flavors of Roms. Just focus on an XDA Rom. Once refined, let the flavors flow...right?
You know, I approach this topic from a respective and open discussion approach with an expressed curiosity at most and the best you can do is confuse it for moaning?
It's guys like you that start all the flaming, when you have people who are simply exchanging ideas.
There's always a few out of the bunch that can't resist being abrasive aka a$$holes while others are just chatting.
AGxM said:
As has been stated, aren't most the bugs pretty common to all builds in one way or another therefore indicating that the problem is at the programming level rather than the rom developer level.
IMHO find one you're happy with and take the bugs with a pinch of salt - the HD2 is still one of the most exciting handsets about and to have the ability to experiment with all this thanks to the ROM guys and the tools developers on here is just blooming fantastic!
Stop moaning and appreciate what we have here!
Click to expand...
Click to collapse
http://www.androidcentral.com/android-30-sdk-preview-2d-3d-graphics-and-dual-core-support-honeycomb
Any one insane enough to try a quick and dirty port?
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
StephanV said:
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
Click to expand...
Click to collapse
They did it with the SDK of Gingerbread, and this one will earn the devs some serious props (and mentions from virtually every tech site, I presume).
That might just be me, though. I'd certainly like to see it happen, no matter how unstable or unusable it might be.
I think the port would be more a case of. LOOK WHAT I CAN DO, then any thing else.
(Have a peek at www.twitter.com/blackal1ce , I'm posting up screenshots from the REALLY slow SDK)
M-en-M said:
They did it with the SDK of Gingerbread, and this one will earn the devs some serious props (and mentions from virtually every tech site, I presume).
That might just be me, though. I'd certainly like to see it happen, no matter how unstable or unusable it might be.
Click to expand...
Click to collapse
They started porting it - as they did with every release before - and got fed up after a while because it's too much effort for something that Google's gonna release a couple of weeks later anyway.
Although the GB SDK port was still majorly flawed, it was at least meant to run on phones with this kind of hardware. Have you seen the previews of Honeycomb? Even if someone did a pretty decent SDK port (which on itself is already quite impossible) it still wouldn't be any good because even our big-ass 4.3" screen is still nothing compared to a tablet. The UI just wouldn't be useable.
And yes I know there's gonna be people willing to give it a shot anyway, and of course that's fine by me, best of luck. Just trying to keep it real here: don't get your hopes up for a somewhat useable port because I don't see that happening before Google decides to put it in AOSP.
StephanV said:
An SDK port of an unreleased tablet-only OS sounds like a major waste of time to me.
Click to expand...
Click to collapse
While I agree you couldn't just compile and run this thing on a HD2, it's not just for tablets. It's optimised to be used on higher resolutions and bigger screens, but will still run fine on phones.
I reckon we'll be seeing ports of this in the near future
No, as of now it really is officially tablet-only, and I'm not talking just about the technical stuff. A tablet OS isn't quite useable on a phone, not because you can't run it, but because it's really hard to use its UI.
I did hear originally that is was tablet only, but I've since heard reports that it's viable for phones as well. You know what t'internet's like. I guess we'll only know when it's actually out proper!
Very good news, waiting to see who's the first want to put their hands dirty
Committed to the developer community, we're launching http://www.HTCdev.com and opening Sense to devs via OpenSense SDK #uplinq #HTC
We know that, by supporting your ideas, the benefits customers get from our technology can increase exponentially. HTCdev is designed to give you the inspiration to explore the possibilities within the HTC platform, the support you need to develop your ideas, the platform you need to promote your applications and the forum to connect with other developers and with HTC. Through tools, tutorials, blogs and events, HTCdev is dedicated to helping you get the most from your talent and potential. And we can’t wait to get started.
http://www.htcdev.com/about/
Looks like my next phone may be HTC afterall.
Habbit said:
Looks like my next phone may be HTC afterall.
Click to expand...
Click to collapse
ya i could agree my first batch of phones were htc then i moved off but i could say i will be getting the sensation afterall the bootloader business etc.
this is great news! glad HTC has decided to embrace the open dev community instead of creating barriers all the time.
Wow! I have been waiting for this for a long time. I hope they will release it in the summer.
so we can expext to have HTCSense on almost every Android Device? ^^
Was speaking to CM_arcee on twitter (developer for CM): "They're opening APIs to use Sense on devices that have it, they're not giving away Sense itself."
So that means Sense won't be coming to out non-HTC phone
n-zocker said:
so we can expext to have HTCSense on almost every Android Device? ^^
Click to expand...
Click to collapse
No, this is an API of sorts into the current sense environment. Developers will be able to write apps that use sense features to give the same look-and-feel as stock sense apps on sense based devices.
Why would developers limit themselves to HTC devices only in stead of the whole Android ecosystem?
it will help the development of apps for the flyer
let's hope
WOW, incredible news.....from locking their boot loaders to almost total openness, what a turn of events. Just shows what a nice strong community can accomplish. If there wasnt XDA nothing like this could have happened.
If the new HTC dual core doesn't take much longer to release, I ll be getting that definitely. I love HTC and after HD2, I still believe that the brand can reinvent themselves and lead the new smartphone industry, as they have done before.
This is a very clever move from HTC, and one which will certainly see them gain much love from the dev community.
I'm not sure it will be total access to HTC Sense, but certainly a way to make apps/widgets etc integrate with Sense a lot better. That can only be a good thing. HTC have obviously realised that the dev community came to originally, and wants to stay with them, and they are making it worth our while.
If it will run only on HTC devices, this is the right way!
Makes sense as not to open it up to other devices Sense is what makes it stand out from other devices.HTC sense is why im married to the brand so to speak.
Worst idea ever... HTC will give you access to propriatery HTC APIs and you will be able to code apps for their phones only... worst "open" idea ever.
I sincerely hope that devs ignore this HTC ploy to better their own UI.
This is going in the same direction as the Nvidia, Qualcomm, Samsung optimised games that only work on one of the CPU. WTF.. games on android should be optimised for all CPUs or should I say CPUs should be compatible with some standard... like OpenGL that they are using dooohhhhh... Stupid SoC makers.
mkrmec said:
Worst idea ever... HTC will give you access to propriatery HTC APIs and you will be able to code apps for their phones only... worst "open" idea ever.
Click to expand...
Click to collapse
It gives devss the option to integrate with the Sense UI if they want to. It's up to the devs themselves whether they want to code exclusively for it. They can still code for all Android (as they could before) and then on top of that make it work nicely with Sense as well. This can only be a positive thing in my opinion.
As long as they doesn't release the entire sense source code it's not open. Period.
the first thing that came to my mind was Cookie's Home Tab from winmo. Can't wait!
Good for sense cuz they get developers but those apps made for sense will only work with sense and then more android fragmentation... the last thing we need
Sent from my SGH-T959 using XDA App
Great news!
I am sorry I don't wish to be rude, but it is absolutely ridiculous that some people are trying to make this look like a bad thing. How some people can turn a news about Sense becoming MORE open, into an almost doomsday prophecy for Android is beyond me.
This is only making life easier for the devs working on Sense, which in terms means better and faster development of said UI... How can that be bad? It's not like it means that all deving for other devices is getting worse as a result..