I'm not sure what they are yet as I'm still downloading the zip. Maybe a way to add the framework support into AOSP?
http://www.htcdev.com/devcenter/downloads
Hopefully a way to implement the Sense Camera and Dialer into AOSP. That would be really awesome, if I could use those two in AOSP, I would switch immediately.
wph said:
Hopefully a way to implement the Sense Camera and Dialer into AOSP. That would be really awesome, if I could use those two in AOSP, I would switch immediately.
Click to expand...
Click to collapse
Well, the Sense stuff requires Sense, it's a choice between Sense and AOSP, really. You'd be better off de-Sensing a Sense ROM than hoping for Sense stuff on AOSP.
These have been available for almost week now
bbedward said:
These have been available for almost week now
Click to expand...
Click to collapse
Yes, I heard it was available on day 2 after the kernel code was released. I don't think anyone has looked into using it/implementing it yet though. I knew the kernel source dropped but I did not see this until today and I'm sure there are many people who didn't know it was even posted.
BenPope said:
Well, the Sense stuff requires Sense, it's a choice between Sense and AOSP, really. You'd be better off de-Sensing a Sense ROM than hoping for Sense stuff on AOSP.
Click to expand...
Click to collapse
I fully understand what you're saying, but these apps depend on the Sense framework, so that's why something like this gives hope.
Porting such stuff was always (almost) impossible, meaning you had to choose between the latest Android and Sense. When, on the long run, the One isn't supported anymore, you are stuck, since de-Sensing a ROM that isn't there is impossible. Maybe, and only maybe, with this framework files it is easier to port a couple of apps and include them in the latest AOSP.
For now I see it like this: HTC made these available, so they must have some reason. Might be because the Google Play Edition camera is not as good as the Sense one, which causes bad publicity, like the review on The Verge which gave a 4 for the camera. By providing these files, they maybe want to reach out to the community?
Forgive me for not knowing much on the development side of things, but if we can't find a way to port the Sense camera with this framework, what can we learn? And what would be required to see what the Sense camera requires to run on an AOSP ROM? Does this make it possible to port the Sense camera to at least the GE edition ROM? I know GE is different from AOSP, so I'm curious. The only reason I'm hesitant to stay on a stock android ROM is because of the camera.
Related
Is this possible?
As of right now I think the development are worrying about getting a recovery on our phones and we need the recovery to flash roms unless there's another way...
Not only that but sense is a cpu hog. Such a horrible UI.
CM6 is all I care about getting on here. FB/Twitter integration all exists in 2.1, Sense adds little other than pretty looking widgets.
Isn't cm6 2.2??
Sent from my T-Mobile G1 using XDA App
robavila721 said:
Isn't cm6 2.2??
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
Yes, I was just referring to the fact that we havent needed Sense UI for anything but pretty widgets since Android SDK 2.1
Why would you want Sense over TouchWiz? If you we're looking for pretty there are lots of HTC Sense packing HTC phones on the market. The myTouch Slide is kind of running an ugly version of Sense but it still is Sense.
One more thing to consider, also. You won't find any reputable developer such as Cyanogen putting sense in their roms because of legality issues. So, if you do happen to come across a rom for this phone running sense, chances are its going to be pretty bunk.
Sense has some very appealing factors, such as the hibernate support and of course, the cosmetics of it
In addition, the new version of HTC sense is supposed to have a lot of optimizations meaning it will be faster than before.
At the very least, is it possible for a dev to port the algorithms used for hibernate to the Vibrant?
Use this. its not sense but its a launcher close to it. has 3d drawer and everything.
sombionix said:
One more thing to consider, also. You won't find any reputable developer such as Cyanogen putting sense in their roms because of legality issues. So, if you do happen to come across a rom for this phone running sense, chances are its going to be pretty bunk.
Click to expand...
Click to collapse
but there are many more reputable developers then CM
kingkurry said:
Is this possible?
Click to expand...
Click to collapse
Possible? perhaps...
Desireable? perhaps not...
Likely? Given the legal issues involved? not very...
I am also interested in this.. But to be honest if it where to happen, it won't happen until the developers get the source code for 2.2 and haber time to play with it.
So, if we are lucky and someone does decide to work on this.. knowing the possible legal issues. It would take a few weeks (after official 2.2) to get it done.
But I have no doubt in my mind that it would work in our phones.
Sent from my SGH-T959 using XDA App
KingKlik(sp?) made a lot of sense roms for the MT3G and a lot of people seemed to like them. I just think Sense looks terrible, compared to any UI on any new age smartphone I have seen(except maybe Windows Mobile). I'm mainly talking about the launcher tough, the part that people for some reason like to throw on their phone even if they don't have sense.
Hey, I'm having some trouble finding a full AOSP 2.3 Gingerbread ROM with zero modifications to styling. I obviously want one that has all the necessary drivers for the hardware, but I don't want "extras". I've seemingly tried them all, and the closest to full AOSP I could find was bcnice's ROM, which he hasn't updated in months. The most up to date, closest to AOSP I've found is the Evervolv 1.0.1b4, but I'm getting tired of flashing the stock font pack every time I try a new update, and I don't like that is has its "own launcher".
Are there any fully functional 2.3 ROMs available that are 100% AOSP, or does everyone add their recommended programs and styling? It feels like I'm getting a carrier update lol.
What you are looking for just doesn't exist yet. Closest thing available are the Roms you already tried or this one below, but many things don't work yet like front cam, gps, etc....
http://forum.xda-developers.com/showthread.php?t=877653
Cicatrize said:
Hey, I'm having some trouble finding a full AOSP 2.3 Gingerbread ROM with zero modifications to styling. I obviously want one that has all the necessary drivers for the hardware, but I don't want "extras". I've seemingly tried them all, and the closest to full AOSP I could find was bcnice's ROM, which he hasn't updated in months. The most up to date, closest to AOSP I've found is the Evervolv 1.0.1b4, but I'm getting tired of flashing the stock font pack every time I try a new update, and I don't like that is has its "own launcher".
Are there any fully functional 2.3 ROMs available that are 100% AOSP, or does everyone add their recommended programs and styling? It feels like I'm getting a carrier update lol.
Click to expand...
Click to collapse
evervolv is no where near stock.... lol.
http://forum.xda-developers.com/showthread.php?t=881557
closest thing to stock
aimbdd said:
evervolv is no where near stock.... lol.
http://forum.xda-developers.com/showthread.php?t=881557
closest thing to stock
Click to expand...
Click to collapse
Cool, thanks. Looks like that one's been updated to fix the issues I remember with it before. I'll give it a shot!
Just out of curiosity, why isn't there a 100% AOSP rom? Is it because there is little dev interest? Would it be very difficult to do a straight port? It seems like maybe CM would release a straight port before they started adding their stuff... but I'm a newb and unsure of how the process works really.
thanamesjames said:
Just out of curiosity, why isn't there a 100% AOSP rom? Is it because there is little dev interest? Would it be very difficult to do a straight port? It seems like maybe CM would release a straight port before they started adding their stuff... but I'm a newb and unsure of how the process works really.
Click to expand...
Click to collapse
I'm using the SalvageMod one mentioned earlier now, and it's VERY stock. The only things that are different that I can see are some custom wallpapers (doesn't really count as not-AOSP) and the semi-transparent notification drop down.
kommydroid is completely stock 2.3 with the only mod being the boot animation.
KommyDroid Looks pretty good... when I get my new Evo from Sprint, I'll try flashing it.
To the Vision ROMS Mods,
would you kindly make us a CM7 Sense ROM? A CM7 ROM with or able to take HTC Sense Widgtes?
It is hard, yes, and our mods are hardworking. It is impossible, no, there is no such a thing as impossible when it comes to technology on XDA-Developers.
Hoping and waiting and believing!
This ... would be epic.
It's not impossible, but it's not worth the effort. The Sense widgets require the Sense framework which is closed source. In order to merge the two, you would need to reverse-engineer the Sense framework which is near impossible. So, no, it's not gonna happen.
This has been talked about countless times for years.. if it was possible it would of been achieved by now..
just saying..
on that note, I'd be impressed if I were to log into XDA one and see it a hybred Cm7/Sense ROM
This would be like the yankees and red sox merging to form one entity.
i think every one would love that, it would be great but who knows maybe soon they will, i mean they have sense-ish with vanilla so maybe
If only such a thing was possible... a Sense/CM7 hybrid would be the best ROM ever, hands down
Shame it isn't though, as someone already mentioned, it would involve reverse-engineering Sense since it's closed source, and CM is strictly AOSP
its a extremely difficult task that may not even have a nice reward at the end. Look at how pissed HTC got with the Beautiful widgets looking too much like theirs. My guess is that if a dev did in fact pull this off, it'd be shutdown before most of us could enjoy it...
I actually prefer having to choose between one and the other, since they are so distinct in style. I think some of the "conveniences" of Sense could easily be easily be written into AOSP roms, but in terms of aesthetics and style - I like them being separate.
If a "blend" is what you want, then you should probably give UD a spin, but I'm pretty sure that will fall short of what you seek.
This belongs in the general section. Android has been out since 2008, you don't think someone has already thought about wanting this? And 3 years later it hasn't been accomplished yet? It should already be obvious its not done yet because it's damn near impossible. But hey its not bad to ask for something. Only thing i think would ever be close to this is someone making a stock launcher with beautiful widgets incorperated into it or something hellishly close to
Sense widgets. But besides that, please don't ever, EVER, count on it.
Sent from my HTC Vision using XDA Premium App
do it with Sense 3.0 and ill donate a ton, and run around my neighborhood naked! lol
Makes me wonder, what ever happened to sillian?
I've never been a fan of sense, CM is great how it is.
dilfatx said:
I'd be impressed if I were to log into XDA one and see it a hybred Cm7/Sense ROM
Click to expand...
Click to collapse
actually the senseginger 3.0 rom is almost that, you can disable htc lockscreen in lieu of vanilla lockscreen, it has the nice gingerbread on/off screen animations, I use launcher pro plus with it and everything seems pretty damn snappy... the launcher pro plus widgets are practically direct copies of the htc widgets, and I get to have a 5x5 homescreen... I'm sure once the source drops for the htc gingerbread vision kernel I'll get stellar quadrant scores as I do on virtuous 1.0.2 (2500+ @ 1402Mhz)
no way...if you want sense, use a sense rom.
Sense is teh suck
what exactly is blur? Ive read that its actually android mixed with motorolla's touch (which is called blur) but what exactly is it?
Ive seen pictures of custom rom and cant tell the difference between blur and custom ROM. At first I thought blur was like a theme and just had fancy animations. But reading about it further it seems like blur is the extra apps that are on the phone that is not stock with the android OS, is that right?
For example if a custom ROM doesnt have blur, how does one get the camera running?
Also is AOSP(android open source project) like the opposite of blur? its considered to be a pure android OS right?
Blur, sense, and touchwiz are all proprietary vendor frameworks that (theoretically) augment the base Android experience. They come at the cost of large ROMs and resources but some people really like them.
AOSP is exactly that- if you build android straight off Google's git, you've built AOSP. It's actually pretty good, hence everyone releasing ROMs for dx /d2 claiming to be 'vanilla' or 'pure.'
In between those is CyanogenMod. CM is more like an extension of AOSP than a replacement framework. You get some nice features and tweaks plus a consistent experience across devices.
HTH!
mrkite38 said:
Blur, sense, and touchwiz are all proprietary vendor frameworks that (theoretically) augment the base Android experience. They come at the cost of large ROMs and resources but some people really like them.
AOSP is exactly that- if you build android straight off Google's git, you've built AOSP. It's actually pretty good, hence everyone releasing ROMs for dx /d2 claiming to be 'vanilla' or 'pure.'
In between those is CyanogenMod. CM is more like an extension of AOSP than a replacement framework. You get some nice features and tweaks plus a consistent experience across devices.
HTH!
Click to expand...
Click to collapse
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?
1dtms said:
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?
Click to expand...
Click to collapse
yes, all nexus model phones are AOSP.
1dtms said:
hmm interesting..
So the google phones that one would buy directly from them without service, are they considered to be pure AOSP?
Click to expand...
Click to collapse
Google only offered that once with the Nexus 1. The Nexus S is sold through T-Mobile and Sprint.
EDIT: but yes, AOSP.
I see.. well thank you! this helped clear up a lot.
So im guessing the camera will still work with all its 8MP if used under an AOSP app?
Also is the liberty rom considered to be pure AOSP? If not, what ROM in your opinion is the best AOSP ROM for .340?
1dtms said:
I see.. well thank you! this helped clear up a lot.
So im guessing the camera will still work with all its 8MP if used under an AOSP app?
Also is the liberty rom considered to be pure AOSP? If not, what ROM in your opinion is the best AOSP ROM for .340?
Click to expand...
Click to collapse
Camera support is more about kernel and libraries, I think, but the aosp camera app handles the Dinc camera fine...
Can't help you much with the rom selection, sorry.
With all the news today surrounding the Nexus experience HTC One there was a point i feel was a little lost. While most of the news centered as to if we can port Sense specific features to AOSP roms (we cant), and all the things that the AOSP One (i am calling it the AOSP One because we have not heard otherwise at this point) will be lacking here is what was lost... and to those of us who have been in the community for years its amazing.
We've been recognized by OEM's.... Think years back when Motorola was locking its bootloader down, HTC wasnt far behind and Samsung was not being very helpful. The modding community was pretty much shoved to the side, and while some OEM's started (half-assed until recently) to provide solutions and options to locked down bootloaders, they widely sucked. The dev model of the Motorola Razr series comes with No Warranty whatsoever once you unlock it.
-
+Unlocking your DEVELOPER EDITION's bootloader voids all warranties and may cause serious harm to your device. Make sure you understand what this means.
Click to expand...
Click to collapse
Of note, there is no MAY like the HTC and NEXUS line have while unlocking.
And up until recently HTC still had issues after unlocking your bootloader with flashing the boot partition and/or adjusting the System partition. It was touchy to say the least.
But finally OEM's are willing to recognize the development community and provide devices that enable us to do what we love to do so much. The price is a 50/50 but a $20 premium is not much of a fee to pay over the stock unlocked model for the One.
For those of us who have been fighting the good fight for years we have done it, we have made a change in the way OEM's work, even if it is a side effort they are still recognizing us and building a device for us. I really honestly wish i could trade in my Tmobile One for the AOSP model, just to show my support for HTC but frankly cannot afford it.
Unfortunately, it won't actually mean anything. It does show that these companies are opening up to development, but the AOSP edition phones themselves will lack so many features that make them distinct. Google has to do some serious discussions with HTC to come out with an open-sourced solution to proprietary hardware like ImageSense and possibly Boomsound as well.
ArmedandDangerous said:
Unfortunately, it won't actually mean anything. It does show that these companies are opening up to development, but the AOSP edition phones themselves will lack so many features that make them distinct. Google has to do some serious discussions with HTC to come out with an open-sourced solution to proprietary hardware like ImageSense and possibly Boomsound as well.
Click to expand...
Click to collapse
Why does everyone think Google & HTC are about to ship some horribly unoptimized phone and open themselves up to the media sh*tshow that would ensue? I don't understand.
HTC is handling the One with SUCH pride and it's such an important device for them, I don't think they'd stand for a noticeably crippled device. And what would that say about vanilla Android if everyone attributes the 'suck' of the device to it's operating system?
Both Google & HTC have probably been working on this for a good while and SOMEONE has raised these issues in-house and I'm sure they're both working together to work out all the kinks & provide a solid device ready to put the Nexus experience into more people's hands.
I also think 4.3 is just around the corner and will continue to achieve parity with third party solutions & ideas, especially in imaging, and hopefully someone will figure out this button situation once and for all.
Interesting thought, but I do believe vanilla Android will be just that. No HTC features. HTC gets to sell a phone.
Sent from my HTC One using Tapatalk 2
asif9t9 said:
Interesting thought, but I do believe vanilla Android will be just that. No HTC features. HTC gets to sell a phone.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I agree. The Nexus Experience will be nothing more than plain vanilla Android running on a HTC ONE. Anyone expecting anything else is just fooling themselves.
When has vanilla Android been anything overly exciting? My experience with the Nexus 4 was boring as hell. I basically just had a device that just worked without any features, kind of like Apple OS.
Call me crazy but I've always loved the overlay that Samsung and HTC adds to Android.
Sent from my HTC One using xda premium
What it gives us is longevity and prompt update.
Coming from Galaxy Nexus and Nexus 4, I prefer a lot of features in Sense 5 over vanilla android. Even 4.3 won't be able to tempt me to go back to vanilla.
But since updates on these Nexus experience devices are supposed to be maintained by Google, what this means is that the One will be among the first devices to get a fully functional Key Lime Pie rom this fall. Without this new Nexus One, we would probably have to wait at least half a year before HTC can come up with Sense 6 or something on KLM.
Sent from my HTC One using xda premium
I think what is being missed about a aosp HTC one. No it won't have sense features, if it did, it wouldn't be aosp. What's important is that it will be a pure android experience WITH all of the proprietary hardware drivers. So no it won't have Zoe, but it will have the same quality image capturing as the sense. No, it won't have Beats sound codecs, but the boomsound will have the same awesome sound as sense with beats turned off. All in all it is going to be what we've wanted forever. The bugs in most all aosp builds are from not having proprietary hardware drivers. We will have a base for the devs to build on that is built by the manufacturer. AWESOME
18th.abn said:
I think what is being missed about a aosp HTC one. No it won't have sense features, if it did, it wouldn't be aosp. What's important is that it will be a pure android experience WITH all of the proprietary hardware drivers. So no it won't have Zoe, but it will have the same quality image capturing as the sense. No, it won't have Beats sound codecs, but the boomsound will have the same awesome sound as sense with beats turned off. All in all it is going to be what we've wanted forever. The bugs in most all aosp builds are from not having proprietary hardware drivers. We will have a base for the devs to build on that is built by the manufacturer. AWESOME
Click to expand...
Click to collapse
It's not just Zoe that you won't get. It's ImageSense that you have to worry about, cos that processes the images to be what it is. We can only hope that the new device would come with open-source versions of drivers for these features as they are embedded deeply into the Sense framework.
Nexus usually means quickest Andriod updates, since no dependencies on OEM skins/overlay development and testing. And ongoing platform support... at least until features can't be supported by hardware.
I've been a long time CyanogenMod fan, but the Sense 5 experience is good so far. Snappy interface, clean, good battery life... but I do some 4.2.2 features from my HOXL. If HTC lags too far behind with Sense 5 development, then it may warrant switching to CM or going naked Android. For now Blinkfeed and Zoe are interesting... wish I could increase the density of icons in Sense...
ArmedandDangerous said:
It's not just Zoe that you won't get. It's ImageSense that you have to worry about, cos that processes the images to be what it is. We can only hope that the new device would come with open-source versions of drivers for these features as they are embedded deeply into the Sense framework.
Click to expand...
Click to collapse
Quoted from The Verge:
"Of course, the big question with running stock on the One is how HTC's unique hardware features will work without its software, and it sounds like there's good news: Barra told me Beats Audio will still work — the hardware optimization is active all the time, but it won't put an icon in the menu bar. HTC's UltraPixel camera module is still present, but it's being made to work with the stock Android camera app — Barra said it'll just "do what it does," adding that more details would be forthcoming as Google and HTC work on the software."
That should settle some worries about Beats and ImageSense support. I wouldn't get my hopes up for Zoe, though...
I am sure they will deliver working htc features like beats, zoe, cam, IR remote and stuff. Otherwise they'd do a huge mistake marketing wise.
Sent from my HTC One
BrickL0rd said:
I am sure they will deliver working htc features like beats, zoe, cam, IR remote and stuff. Otherwise they'd do a huge mistake marketing wise.
Sent from my HTC One
Click to expand...
Click to collapse
They have already gone on record that the ir, zoe, camera enhancements etc won't be added as these are sense specific.
BrickL0rd said:
I am sure they will deliver working htc features like beats, zoe, cam, IR remote and stuff. Otherwise they'd do a huge mistake marketing wise.
Sent from my HTC One
Click to expand...
Click to collapse
Being proprietary features, they will not just port the whole thing over to AOSP cos it needs Sense to work. What HTC can do is make new drivers that are open-sourced for AOSP that interface with these hardware
milaxtpe said:
I don't understand.
Click to expand...
Click to collapse
What don't you understand?
ArmedandDangerous said:
Being proprietary features, they will not just port the whole thing over to AOSP cos it needs Sense to work. What HTC can do is make new drivers that are open-sourced for AOSP that interface with these hardware
Click to expand...
Click to collapse
This is sad. I've been running CM10.1-nightlies for about a week and I really like AOSP/Nexus-style, but the camera in original/sense-based roms are better than CM, at least right now. (Can't really compare to alpha-nightlies)
If HTC were to release the camera-app for playstore that'd be awesome, and I would actually not mind paying a dollar or so for it. But if you're right about it being a driver issue as well I'm not quite sure how they'd be able to solve that with just a camera-app, haven't had time to read up on those parts of Android yet since I'm fairly new to this world (as my post count would suggest).
klewwe said:
This is sad. I've been running CM10.1-nightlies for about a week and I really like AOSP/Nexus-style, but the camera in original/sense-based roms are better than CM, at least right now. (Can't really compare to alpha-nightlies)
If HTC were to release the camera-app for playstore that'd be awesome, and I would actually not mind paying a dollar or so for it. But if you're right about it being a driver issue as well I'm not quite sure how they'd be able to solve that with just a camera-app, haven't had time to read up on those parts of Android yet since I'm fairly new to this world (as my post count would suggest).
Click to expand...
Click to collapse
Welcome to Android! An app would be great, but I don't think that would be enough. It's a HTC-only feature that requires the Sense framework to work, so to me the only logical way to proceed is to create a second set of drivers that are open-source and compatible with AOSP.
ArmedandDangerous said:
Welcome to Android! An app would be great, but I don't think that would be enough. It's a HTC-only feature that requires the Sense framework to work, so to me the only logical way to proceed is to create a second set of drivers that are open-source and compatible with AOSP.
Click to expand...
Click to collapse
Would a 3rd party camera app suffice in these sort of circumstances?
daleski75 said:
Would a 3rd party camera app suffice in these sort of circumstances?
Click to expand...
Click to collapse
Nope. ImageSense is a proprietary piece of hardware exclusive to HTC and Sense and is not accessible/fully accessible through 3rd party apps. They'll still have the Ultrapixels to play with though
ArmedandDangerous said:
Nope. ImageSense is a proprietary piece of hardware exclusive to HTC and Sense and is not accessible/fully accessible through 3rd party apps. They'll still have the Ultrapixels to play with though
Click to expand...
Click to collapse
When 4.2.2 is released for the sense edition phones I am sure there will be camera comparisons between both editions and I reckon there won't be that much of a difference between them.
if they dont include these sense based features they cant sell it for the same price - ergo it has to be alot cheaper hence everyone would buy the stockandroid ONE and flash SENSE custom Roms on it.
I'd do it this way