Is it possible to use mhl with cm or aokp??
Sent from my HTC One S using xda app
Killadude said:
Is it possible to use mhl with cm or aokp??
Sent from my HTC One S using xda app
Click to expand...
Click to collapse
No, at the moment there's no AOSP ROM that can do HDMI/MHL out. It's the #1 reason I continue to use Sense based ROMs on the One S (or any other HTC Android phone). When I was using the HTC Sensation it was the same thing, developers couldn't get it working most likely because the functionality relied on some proprietary software locked down by HTC.
MHL is a feature that I would personally donate money to developers for, but it seems the majority of users simply don't see MHL as an important feature. This is why most AOSP ROM change logs don't even bother mentioning that MHL doesn't work. For those more knowledgeable, please feel free to correct me if I've said anything wrong, my apologies in advance.
I've been hoping for this very thing myself. Vanilla is so much cleaner than any of the stupid skinning HTC has done... so far, i've settled with Viper OneS to keep the HW functionality with as much sense removed as possible. still have it for the titlebar/drawer, settings, phone/messaging and lock screen which kinda sucks, but at least I can use it with my appradio2.
cabasse84 said:
I've been hoping for this very thing myself. Vanilla is so much cleaner than any of the stupid skinning HTC has done... so far, i've settled with Viper OneS to keep the HW functionality with as much sense removed as possible. still have it for the titlebar/drawer, settings, phone/messaging and lock screen which kinda sucks, but at least I can use it with my appradio2.
Click to expand...
Click to collapse
I just switched a couple days ago to the ViperOneS ROM, and I've been impressed with how smooth it runs given the Sense 4 UI (props to the ViperOneS team). Yes, AOSP would likely result in more free RAM overall (thus more multitasking ability), however I like how the ViperOneS has several AOSP tweaks like the apps dialog and lockscreen. Of course, the MHL / HDMI out is working great as well.
Interestingly, the only modern smartphone I could find that has MHL / HDMI fully working on AOSP is the Sony Xperia T/TX (and similar variations). The FreeXperia project somehow managed to get it working, though I guess it's because of the generous source code sharing from Sony. For users who absolutely require an AOSP ROM with MHL, recent Sony smartphones with FreeXperia based ROMs are the only option.
Related
I started this thread with hopes of learning and educating the talented Rom cookers and bakers XDA has to offer. There are alot of varying points of view, both in completely different camps as to which UI has more to offer/ meets a user's needs or desires. Vanilla, custom, Sense. I am trying to figure out WHAT users want in there roms.
For example:
I keep using Sense based Roms because I love the camera & enjoy the fact that it employs face detection. I also enjoy the fact that the SMS application automatically applies my picture from Facebook or twitter as my avatar when sending messages, to me that makes it feel cleaner.
I dislike the fact that sense keeps a rolling list of my most recent applications above the notifications bar, I also dislike how taxing on the system sense is.
Alas, this thread isn't only about what I like and I want... its about what we all would like to see.
P.S.
If we have a team of skinners/themers and bakers out there willing to undertake an on-demand ROM like this... 1. We would forever love you 2. If you haven't done so already, I will set up a PayPal account for donations in your honor because I'll love you like that.
Personally I like HTC Sense but there's something about AOSP that I can't help but have a huge attraction to so I'd have to go with that. I agree though about the status bar showing your recent apps and I did notice that Sense slows down my phone more and kinda kills battery
What does AOSP have to offer? AOSP vs Sense.
I'm familiar with a lot of terms, but what is "vanilla" ?
Sent from my PG06100 using XDA App
Enraged21 said:
What does AOSP have to offer? AOSP vs Sense.
I'm familiar with a lot of terms, but what is "vanilla" ?
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
From what I have gleaned, it's basically the most simple/basic/no frills form of the ROM. Then, the bakers out all nice goodies and stuff in it to make it what it is.
Demented71 said:
From what I have gleaned, it's basically the most simple/basic/no frills form of the ROM. Then, the bakers out all nice goodies and stuff in it to make it what it is.
Click to expand...
Click to collapse
AOSP stands for Android Open Source Project and is like you said, stock android. It's what android is meant to look like but then companies add HTC Sense and Motorola Blur and other frames over it. If you check out the Ginger beast rom for the Inspire, which is what I run, then you'll see what it looks like and such
Canio Wolf said:
AOSP stands for Android Open Source Project and is like you said, stock android. It's what android is meant to look like but then companies add HTC Sense and Motorola Blur and other frames over it. If you check out the Ginger beast rom for the Inspire, which is what I run, then you'll see what it looks like and such
Click to expand...
Click to collapse
So is Gingerbeast a very trim version of an AOSP ROM? I played with MIUI a bit, but then went to CoreDroid and am pretty much loving it. Though I do have that itch to flash again...lol
Sense roms are made from what either HTC leaks us or stock firmwares modified or whatever that particular dev wants to do to that build(theme, deodex, zipalign, add whatever tweaks). You can remove some sense apks, but sense framework is still there and there is still some hints of it throughout that just can't really be removed.
Unmodified aosp roms are pretty much what you would see on a nexus s. Absolutley no bloat, no sense at all, fast and nothing to hog resources. But aosp wasn't specifically built for this phone and its a lot harder to get everything working right (thank the cm team for not only getting everything working, but it works insanely well).
Gingerbeast uses some cm core parts, but removes some cm specific stuff, adds in aosp parts from both source trees and is then compiled. Same for the kernel- cm aosp kernel, with some extra speed/efficiency tweaks)
Some sense roms are almost 300mb, gingerbeast is around 85 I believe.
di11igaf said:
Sense roms are made from what either HTC leaks us or stock firmwares modified or whatever that particular dev wants to do to that build(theme, deodex, zipalign, add whatever tweaks). You can remove some sense apks, but sense framework is still there and there is still some hints of it throughout that just can't really be removed.
Unmodified aosp roms are pretty much what you would see on a nexus s. Absolutley no bloat, no sense at all, fast and nothing to hog resources. But aosp wasn't specifically built for this phone and its a lot harder to get everything working right (thank the cm team for not only getting everything working, but it works insanely well).
Gingerbeast uses some cm core parts, but removes some cm specific stuff, adds in aosp parts from both source trees and is then compiled. Same for the kernel- cm aosp kernel, with some extra speed/efficiency tweaks)
Some sense roms are almost 300mb, gingerbeast is around 85 I believe.
Click to expand...
Click to collapse
So what you are saying is, without htc sense frame work we can't have things like the sense camera and weather app with your kernel and an adamholden rom?
Sent from my Inspire 4G using XDA App
I want what Android Revolution has to offer, sense with a no sense script. Best of both worlds, no sense but still have a good camera and all the htc apps, but no sense! Makes sense!
I have to say that I think I prefer some of the things in sense. I've been from leedroid to miui to gingerbeast. Miui. Was slow and taxing, while very pretty... not what I want... I prefer a phone that can fly through pages as fast as I can navigate them.
Gingerbeast is very, very quick which is awesome, but like said before the HTC camera and SMS, as well as clock Widgets and ringtones, are better with sense.
I think ill try out android revolution next
Sent from my Inspire 4G using XDA App
It would be cool of someone made a kernel with calibrated color, I think the captivate had some roms with that. I've noticed the black levels on the inspire seem more dark grey then true black. Wishful thinking maybe?
Sent from my Inspire 4G using XDA App
I love sense, It's better than the others (touchwiz etc)
I use GingerBeast, which I like because it is small and light and fast. I do miss the sense camera, though the miui camera is decent enough for my purposes.
Sent from my Inspire 4G using XDA App
I don't mind sense at all. I'm Still running stock but I'm thinking hard about flashing RCMix kingdom Rom cause I want to check out sense 3.0
hahiss said:
I use GingerBeast, which I like because it is small and light and fast. I do miss the sense camera, though the miui camera is decent enough for my purposes.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Seems like the sense camera is one of the things people without sense miss the most
Sent from my Inspire 4G using XDA App
All,
I've always had google (nexus devices) and decided to give the HTC One S a go. Honestly, this sense is a bad joke/torture device. Between the linkifyapp, multi-tasking, sense specific apps(calendar, dialer, sms etc) which are just abominations, i've had ENOUGH. These mods are done with absolutely no thought to usability or seamlessness.
Time to try AOSP build, or then return this phone and unfortunately get a plasticy SGSIII with easily available AOSP.
/rant
A few questions:
1) Which AOSP rom would you recommend I run (which one is closest to nexus builds)
a) CM9
b)evervolv
c)AOKP
d)other
2) What are major issues to consider when going to an AOSP rom on this phone?
a) Is there a way to get wifi calling on these roms
b) Does the crap VOIP pop go away on these roms?
3) Are there any issues in getting back to stock incase I need to return?
4) How is the camera compared to the stock cam app (only awesome appon this phone)?
Let me know, i'm going to do this today
Best,
I have a lot of the same questions for this phone. I really think the only option worth using will be CM9 if and when there is an official build for the HOS. Totally agree with the camera app. The thing that makes me nervous with CM9 is losing the excellent camera functionality. Its for that reason that I'm still stock and waiting. The VOIP popping sound is annoying, although I'm glad I'm not the only one with the issue. I just want to go back to a clean AOSP based ROM, but from what I've seen there really isnt a good option unless you want to try an Alpha of CM9.
i love the stock HTC one S its brill.
DownloaderZ said:
All,
A few questions:
1) Which AOSP rom would you recommend I run (which one is closest to nexus builds)
a) CM9
b)evervolv
c)AOKP
d)other
2) What are major issues to consider when going to an AOSP rom on this phone?
a) Is there a way to get wifi calling on these roms
b) Does the crap VOIP pop go away on these roms?
3) Are there any issues in getting back to stock incase I need to return?
4) How is the camera compared to the stock cam app (only awesome appon this phone)?
Click to expand...
Click to collapse
1) I would not recommend any of them until there are stable releases available. If I were going to install any of them, I'd choose CM9.
2) List of non-working features are listed in the OP of the CM9 thread. Not sure if the popping sound has been fixed in AOSP.
3) Pretty sure you would use the same method as any other ROM... RUU, relock bottloader, etc.
4) No idea, but would I would be surprised if the stock camera app could not be loaded onto AOSP.
WCCobra said:
4) No idea, but would I would be surprised if the stock camera app could not be loaded onto AOSP.
Click to expand...
Click to collapse
I've read so many times that extracting the stock Sense camera app is going to be a nightmare since it's so deeply rooted into the whole of Sense. So most likely, it's going to be a trade-off situation.
The Ville has official AOKP so that would be your best bet.
I agree with you. I have always disliked Sense since HTC first released it.
1) All are pretty close to stock ICS. CM9 is probably the closest. I prefer AOKP as it has more tweaks, IMO.
2) Wifi calling as of right now is a no-go. I don't know if someone is working on it, and I don't care as I do not use it. One gripe of switching to AOSP is the camera, more info below.
3) In a custom recovery, make a backup of your stock ROM (sense). If you **** anything up you can always go back to exactly what you had when you made the backup.
4) AOSP camera is **** compared to Sense. No burst shot, shutter has lag, video barely works, and no panorama. There is no HDR mode as well, which I really like on the stock. The camera is the BIGGEST turn down when switching to Sense. It is why I am still on Sense.
CSP, what Aokp rom are you talking about? Pm me a link or something. Want to look into it.
Sent from my HTC One S using xda premium
Please stop with the bull****!
CM9 is very stable on the One S. Great battery life and smooth. Camera and camcorder working great and even takes pics while filming.(idk wtf guy above is saying about camera)
AOKP is basically CM9 but with more tweaks and at the moment not as stable as CM due to a few bugs but overall good enough for daily driver.
Every AOSP custom rom is basically CM9 so if you want stock like the OP says about his Nexus S...CM9 only way to go!
Sent from my HTC One S using Xparent ICS Tapatalk 2
A lot of people buy HTC phones with sense but don't like sense that makes no sense
Samsung has touchwiz or get a nexus with aosp as post above suggests.
Sent from my HTC VLE_U using Tapatalk 2
glacierguy said:
A lot of people buy HTC phones with sense but don't like sense that makes no sense
Samsung has touchwiz or get a nexus with aosp as post above suggests.
Sent from my HTC VLE_U using Tapatalk 2
Click to expand...
Click to collapse
I think most of us bought the phone because of the great specs. There are a lot of people who get Samsung phones but dislike touchwiz. It's all personal preference...
WCCobra said:
I think most of us bought the phone because of the great specs. There are a lot of people who get Samsung phones but dislike touchwiz. It's all personal preference...
Click to expand...
Click to collapse
+1. Im on T-Mobile, loved the specs on the HOS even over the SGSIII. Disliked Sense but disliked touchwiz even more. Decided to go with the best house in a bad neighborhood in terms of bloated android overlays. I honestly do not see why manufacturers feel the need to "improve" upon Android. Its perfect in its unadulterated state. One man's opinion of course. The HOS would absolutely fly on 4.1 with no extra BS on top of it.
My Experience
I have owned Htc devices since the G1 I got the 1S for my girl when the upgrade was available I had to send the 1S back for replacement due to data issues (T-mobile) They sent me another one with an older baseband hell I rooted it put a stock sense Rom on it and told the girl here you go it works great and is fast camera is awesome I replaced my Sensation with the play store Gnex all I can say is HOLY **** what a piece this is IMHO it blows away any of the devices I have previosly owned including the 1S my girl has now plus I don't need to wait on HTC or T-mobile to provide an outdated update for the device I currently am running JB V.1 pre release and its badd azz I run aokp aosp both and they just fly I think the camera is fine and getting updates from google is much better than going thru the carriers at 349.95 right now thats a deal ----so long sense/Htc I had all the fun I could stand
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
basically a rom is never really finished.
theres always something to be ironed out or a bug that needs to be squashed. or sometimes its just enhancements,
but yea like you said until htc releases the source then stuff wont be 100%
Even when they do release the sources, there's still lots of things that potentially might not work.
Like take for example CM9 (ICS based) - although there are kernel sources out already for HTC's ICS, a bunch of things are not yet working. You can blame that on closed-source drivers, like wifi or camera, etc.
So it might take a while for everything to work properly, but as long as we have dedicated developers like xkonni, intervigil, etc, there's nothing to be worried about.
Sent from my HTC One S using xda premium
Nice thanks guys that makes sense. I just assumed that things like drivers could be poached and reused but I guess a lit of that is part of the sense framework.
I look forward to seeing what happens
Sent from my HTC One S using xda app-developers app
dillinga said:
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
Click to expand...
Click to collapse
No worries man this was a very legit question.
Has anyone had any luck tracking down a decent ROM (much preferably one as close to vanilla android as possible) that actually still has working MHL? I've done a good bit of searching through most of the individual ROM threads and it seems like this is something that is hardly ever mentioned. I realize that it's missing in CM, much to my sadness as that has been my best experience with a custom ROM thus far. need something that works with my appradio 2!
I'm on $droyd$'s jellybean nonsense build 6 right now and it's not bad, but still too HTC-y for my tastes (plus i'm on hboot 1.14.0004 right now so no wifi for me )
cabasse84 said:
Has anyone had any luck tracking down a decent ROM (much preferably one as close to vanilla android as possible) that actually still has working MHL? I've done a good bit of searching through most of the individual ROM threads and it seems like this is something that is hardly ever mentioned. I realize that it's missing in CM, much to my sadness as that has been my best experience with a custom ROM thus far. need something that works with my appradio 2!
I'm on $droyd$'s jellybean nonsense build 6 right now and it's not bad, but still too HTC-y for my tastes (plus i'm on hboot 1.14.0004 right now so no wifi for me )
Click to expand...
Click to collapse
Dark jelly s edition supports OTG im using bubba kernel along with this... Will check the MHL availability and will post back...
Cheers
This interests me too. In my test of different ROMs I found that trick droid and viper work but make the phone freeze after the mhl cord is removed. Black bean, avatar, jellybam and codename lungo don't work with mhl. None of the awesome cm based ones are supposed to work with hdmi
I keep going back to nonsense which has since been closed. I only have version 4 and version 6 seems to be unavailable for download. Now after almost 5 months as my daily driver I started having Bluetooth issues and I have to load music via USB from the recovery since that must have been removed from it.
Sent from my HTC One S using Tapatalk 2
I got the same results
jillora said:
This interests me too. In my test of different ROMs I found that trick droid and viper work but make the phone freeze after the mhl cord is removed. Black bean, avatar, jellybam and codename lungo don't work with mhl. None of the awesome cm based ones are supposed to work with hdmi
I keep going back to nonsense which has since been closed. I only have version 4 and version 6 seems to be unavailable for download. Now after almost 5 months as my daily driver I started having Bluetooth issues and I have to load music via USB from the recovery since that must have been removed from it.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
I have the same problems, freezing when disconecting mhl cord y trick droid and viper. And with trickdroid 10.x.x there is no output.
I also have opened thead in Q&A, to see if Torxx can help us with trickdroid 10.x.x
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
sandys1 said:
Hi guys,
I am curious to know if the kernel used in Sense ROMs (stock, ElementalX, BeastMode) be made to work in the CM/AOKP roms?
Here's my problem - I personally like the look and feel of CM. However, one big problem is the fact that there is a lot of lost functionality in these roms as compared to sense roms.
Now, I dont mean things like transparent status bars, etc - but core features like HDMI out, headset buttons, usb tethering, battery life, etc.
The focus of the developers is also around cool new features and not around fixing hardware issues. For example someone posted yesterday that wired headset buttons have been broken all the wsy from kernel 3.0 to 3.4.
Im wondering if one can leverage the fully working Sense kernels to run CM.
Sent from my One X using Tapatalk 4
Click to expand...
Click to collapse
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
ImagioX1 said:
Sense kernels cannot run be used to run cm10 or later based roms. IF you like the look and feel of stock android but still want all the working features why don't you download one of the sense roms and desense it? I know viperxl offers desense option in the aroma installer.
Click to expand...
Click to collapse
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
sandys1 said:
Yes - I thought about it, but I like the CM roms for all the added functionality (remote wipes, themes, etc.). Also, in the longer term Kitkat is only going to be possible on our phones via the AOSP/CM route.
I wonder if there is any possibility to fund a bounty to fix hardware compatibility for all the AOSP/CM based roms.
Click to expand...
Click to collapse
What hardware compatibility do you mean? I don't know whether a bounty is going to work, the devs we have working on these ROMs are already doing their absolute best to bring us the best software possible. Also, some of these issues are caused at an upstream level and are completely out of their control.
Sent from my Evita