In the custom sense roms like viper or d3rp do the HTC proprietary things like the image sense chip work? Or what if I'm using a custom kernel?
How about on aosp roms?
Shifted from the ONE
In the sense roms all the sense stuff works, but in aosp it does not.
Sent from my EVO using xda premium
Depends on whether they release that part of the source/kernel
Kernals can be built from source code as he said above. Aosp roms also. Sense based roms are never built from source, same as touchwiz as manufacturers would never release proprietary code. Even if code was leaked, manufacturers would chase tirelessly any developer who integrated any string of the proprietary code in any of their roms. It's happened before and most developers are very aware of it.
Related
I searched the forums and couldn't find a clear answer on this.
Is there a way to push the HTC Smart Dialer to any ROM(Specifically thedudes Cupcake 1.3RC2)? I know the source code is closed source, but it seems that its a matter of morals rather than support that the dialer isn't being included on most ROM's.
I've been using a Rogers based ROM for awhile and I'm kinda spoiled by the dialer. I know its included in most Hero builds, but I'm not a fan of the speed of the Hero builds on the G1 so far.
Not easily. My understanding is that the dialer needs the closed source htc android core, which would need to be ported as well for that dialer to work on other roms. This essentially defeats the purpose of porting it, because you'd basically end up with the rom you ported the dialer from, as a result of porting the whole android system.
qrohlf said:
Not easily. My understanding is that the dialer needs the closed source htc android core, which would need to be ported as well for that dialer to work on other roms. This essentially defeats the purpose of porting it, because you'd basically end up with the rom you ported the dialer from, as a result of porting the whole android system.
Click to expand...
Click to collapse
not entirely true. Look in the dream applications & games section. I'm working on an easy port with minimal movements of frameworks. I'm halting the porting until I can get a working classes.dex file from a a WWE Hero build.
when the nexus s was released i was a god send for galaxy s devs because they had all they stuff they need (source) to have a very good implementation of cm7
when the galaxy s2 was released it was hell for devs they ended up signing a petition with +10000 signatures just to get the kernel source and that took them over 6 months or so (as far as i can remember )
now with the HTC one almost as the same as the nexus 4's hardware , no ?
are there big architectural changes?
could they use stuff from the nexus 4 to make cm10.1 work flawlessly ?
The hardware of the n4 and the one are very very very different , so it won't benefit from the n4.
Sent from my iPhone 5 using Tapatalk
Why did you think a HTC built phone would benefit from a LG built phone.
The soc isnt even in the same Series Never mind all the camera changes. There nothing alike
Sent from my HTC Desire using xda app-developers app
An open SoC from QC is a step in the right direction, however sense kernels are quite different from those needed for CM/AOSP roms, so it's unlikely it will be perfect. The HOX still has niggles with CM today because some of the blobs just don't play along with non-sense roms.
These days if you want decent CM, I think you just need to buy a Nexus. If only the N4 were better I'd buy one...
Currently tossing up between this phone and the Xperia Z, if I get this it'll be under the mindset that i'll probably be running sense on it forever (annoyingly).
M.
what is the difference between sense based roms vs aosp based roms? i've seen some sense based ones that have the same UI as CM10 etc.
CursiveQ said:
what is the difference between sense based roms vs aosp based roms? i've seen some sense based ones that have the same UI as CM10 etc.
Click to expand...
Click to collapse
It's personal preference. CM10 roms are typically alot smaller and tend to use less ram so can aid device performance. Some people also just like running a rom like they would get on a nexus. Of course this all depends on CM10/10.1 being decent on the phone.. if it doesn't work well because of sense kernels, then it's not really worth it.
If you want to run excellent CM roms, I would suggest waiting until kernel sources are out and see what devs can do, or just buy a nexus (though there's no nexus as good as the One).
i'm currently running aokp on my One X. the only real reason i flash roms is so i can have the status bar, settings, dialer, phonebook etc look like stock android.
is it possible to have a sense based rom that will be skinned to look like stock android? with the status bar, settings, dialer and all that jazz?
CursiveQ said:
i'm currently running aokp on my One X. the only real reason i flash roms is so i can have the status bar, settings, dialer, phonebook etc look like stock android.
is it possible to have a sense based rom that will be skinned to look like stock android? with the status bar, settings, dialer and all that jazz?
Click to expand...
Click to collapse
Not completely skinned, no. Dialler is the hardest part IMO as there's no custom dialler that looks like the stock one does. It's actually the thing I miss most when running sense.
M.
mattman83 said:
Not completely skinned, no. Dialler is the hardest part IMO as there's no custom dialler that looks like the stock one does. It's actually the thing I miss most when running sense.
M.
Click to expand...
Click to collapse
ah.. bummer. i really hated the sense dialer
mattman83 said:
Not completely skinned, no. Dialler is the hardest part IMO as there's no custom dialler that looks like the stock one does. It's actually the thing I miss most when running sense.
M.
Click to expand...
Click to collapse
I would disagree with that to a point. I've used sense ROMs where, when you push AOSP contacts.apk to /system/app, you get get AOSP dialer and contacts. Same with mail is possible, if I remember correctly. I've even seen the AOSP settings used in sense (though, it may have been just themed that way) in jellybomb domination ROM. I forget exactly, it's been a while. I run just AOKP or PACman on my Evo lte. I buy HTC for the hardware, not the software. But, sense 5 is intriguing and seems to resemble AOSP more than in the past, but with the blink feed and Zoe (which is what I do find intriguing).
From my Evo LTE, yup.
CursiveQ said:
what is the difference between sense based roms vs aosp based roms? i've seen some sense based ones that have the same UI as CM10 etc.
Click to expand...
Click to collapse
in cm your're guaranteed to miss out on some key features. For instance, with the HTC EVO 4g LTE (and the one x and all its variants as far as i know), CM cannot incorporate the sense based cameras into the rom, so your're really getting something like 70% of the image quality because nobody's been able to figure out how to use the separate, Sense-designated optics hardware with an aosp rom. You're obviously missing out on hmdi/mhl out so forget about connecting to your tv. There are issues with using mass storage from sdcard (probably not going to be a problem here though), amongst others.
CM is on the other hand, generally more customizable and smoother to run than sense based roms, but there are some sense roms (like VIPER 4G 3.X) that are imo right on par with CMX when it comes to great custom experience yet do not omit important hardware features.
I really love the new Google Edition roms since they provide the all the pluses of AOSP without all the lag of the AOSP based roms like CM and PA. Only problem is they just dont provide that same level of customizability that the custom AOSP based roms do.
Any chance well see roms like CM, PA, and AOKP show up soon based on the Google Edition source? Is something like this even possible?
Just patience.
Remember hardly no one has the phone yet to do full on developer stuff.
-Sent from Marino's One-
thekalby said:
I really love the new Google Edition roms since they provide the all the pluses of AOSP without all the lag of the AOSP based roms like CM and PA. Only problem is they just dont provide that same level of customizability that the custom AOSP based roms do.
Any chance well see roms like CM, PA, and AOKP show up soon based on the Google Edition source? Is something like this even possible?
Click to expand...
Click to collapse
we prob will pretty soon i would give it a week or 2!
HRodMusic said:
we prob will pretty soon i would give it a week or 2!
Click to expand...
Click to collapse
So it is possible? For devs to add the CM 10 or AOKP customizations to the GE rom?
Probably not too soon. From what I gather the sources released aren't very helpful to AOSP ROMs and since the GE ROMs aren't built from source it is harder to add things to them that are.
Sent from my HTC One using Tapatalk 2
Hey guys. With the new GE releases coming out, I was curious what the major differences are between GE and CM10.1. I'm on cm now and it's awesome. What's the difference tho?
Sent from my HTC One using Tapatalk 4 Beta
Well firstly CM10.1 was built from AOSP source, while the GE build was created from the software on the GE edition HTC One, which is actually built on sense framework.
As far as functionality wise, there is just much more customization and functionality on CM 10.1 that isnt present in stock aosp android, I cant even start to list the additions, but there are a lot. There site HERE lists some of them. Ultimately though CM is just nightlies for the time being, meaning its not 100% stable right now. The GE rom is much smoother obviously because it was built by the guys over at HTC.
I appreciate the solid answer.
Sent from my HTC One using Tapatalk 4 Beta
thekalby said:
Well firstly CM10.1 was built from AOSP source, while the GE build was created from the software on the GE edition HTC One, which is actually built on sense framework.
As far as functionality wise, there is just much more customization and functionality on CM 10.1 that isnt present in stock aosp android, I cant even start to list the additions, but there are a lot. There site HERE lists some of them. Ultimately though CM is just nightlies for the time being, meaning its not 100% stable right now. The GE rom is much smoother obviously because it was built by the guys over at HTC.
Click to expand...
Click to collapse
Actually the GE ROM does not rely on the Sense framework, that's why the IR blaster, Zoe and Internet Pass-through don't work. The ROMs are provided by Google, but HTC provides the kernel. CM10 on the other hand uses the base Android code provided by Google and makes it to whatever they want. They've got a pretty solid team
ArmedandDangerous said:
Actually the GE ROM does not rely on the Sense framework, that's why the IR blaster, Zoe and Internet Pass-through don't work. The ROMs are provided by Google, but HTC provides the kernel. CM10 on the other hand uses the base Android code provided by Google and makes it to whatever they want. They've got a pretty solid team
Click to expand...
Click to collapse
That makes sense, I knew HTC provided something in the rom, sorry for the mix up.
Hello, on XDA there are lots of custom ROMs, some are based on HTC One GE system, some on AOSP. I though that it's the same, but i see kernels are not compatible so i'd like to ask what are the differences. Thanks
Cero92 said:
Hello, on XDA there are lots of custom ROMs, some are based on HTC One GE system, some on AOSP. I though that it's the same, but i see kernels are not compatible so i'd like to ask what are the differences. Thanks
Click to expand...
Click to collapse
This AOSP = Cyanogenmod. GEL = Include Beats audio, STOCK ROM FROM GOOGLE.
Sent from my HTC One using Tapatalk
MixaDJ said:
This AOSP = Cyanogenmod. GEL = Include Beats audio, STOCK ROM FROM GOOGLE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm asking because I noticed a huge battery drain with CyanogenMod, that I don't have on Sense ROMs. It's probably caused by kernel, right? Any advice?
Thanks for the informations, so GE is a real Nexus-like system white AOSP pure Android, in fact that's different
Thread title seems like an invitation to a religious war.
But I'll plunge in anyway.
Two things:
1)Battery drain can be due to so many things, I wouldn't assume kernel. More likely an app or a setting. Install a good battery stats app and learn how to interpret the results.
Sometimes reinstalling the entire ROM won't even help. Flash back to a Sense ROM and see if you still have bad battery life. If so it could be firmware/radios etc.
2)
Google, for better or for worse, controls every aspect of a Nexus or GPE ROM. They have vast resources. They have talent, discipline, and access to low level hardware drivers etc. These ROMs come loaded with the whole arsenal of Google apps and are intended to showcase an optimized Google "experience"
AOSP ROMs , even Cyanogen, are produced by amateurs that do not have the same resources. They do amazing work, but necessarily they are going to take much longer to get up to speed after major changes to Android. Also, Google apps are not even included, technically. And cyanogen in particular has created their own control panels, apps, over-the-air update schemesand other proprietary systems that have nothing to do with Google.
If you are looking for purity, the question is "pure what"? Pure Google? Go with GPE.
Pure Freedom from Google? A pure, non-corporate, best-effort attempt at compiling a functioning ROM using the AOSP programming environment? Go with CM.
Google controls AOSP, admittedly, but they have no control over what projects others produce using it.
Your call.
Sent from my HTC One using xda app-developers app
NxNW said:
Thread title seems like an invitation to a religious war.
But I'll plunge in anyway.
Two things:
1)Battery drain can be due to so many things, I wouldn't assume kernel. More likely an app or a setting. Install a good battery stats app and learn how to interpret the results.
Sometimes reinstalling the entire ROM won't even help. Flash back to a Sense ROM and see if you still have bad battery life. If so it could be firmware/radios etc.
2)
Google, for better or for worse, controls every aspect of a Nexus or GPE ROM. They have vast resources. They have talent, discipline, and access to low level hardware drivers etc. These ROMs come loaded with the whole arsenal of Google apps and are intended to showcase an optimized Google "experience"
AOSP ROMs , even Cyanogen, are produced by amateurs that do not have the same resources. They do amazing work, but necessarily they are going to take much longer to get up to speed after major changes to Android. Also, Google apps are not even included, technically. And cyanogen in particular has created their own control panels, apps, over-the-air update schemesand other proprietary systems that have nothing to do with Google.
If you are looking for purity, the question is "pure what"? Pure Google? Go with GPE.
Pure Freedom from Google? A pure, non-corporate, best-effort attempt at compiling a functioning ROM using the AOSP programming environment? Go with CM.
Google controls AOSP, admittedly, but they have no control over what projects others produce using it.
Your call.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
It's not, maybe I chose the wrong words :\
However, thanks a lot for the clarification!