Related
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.
Hi,
I was thinking about this because, almost every 4.2 rom for the Atrix HD as a lot of problems (camera, battery drain, etc), it's worth?
Flashed AOSPizza and its incredible and can't find anything that I miss from 4.2 so that's my focus: why don't put effort on 4.1 which is running great since (to me) there aren't so many differences with 4.2?
A 4.1 version of Paranoid Android would be awesome for example. Just putting the debate on the table
Right now the benefit is broken camcorder...:silly:
http://socialcompare.com/en/comparison/android-versions-comparison
Lockscreen widgets
360 degree images with Photo Sphere
Gesture Typing, for faster typing
Wireless display with Miracast
Daydream to display information when idle or docked
Hefty amout of project butter additions
Eruditass said:
http://socialcompare.com/en/comparison/android-versions-comparison
Lockscreen widgets
360 degree images with Photo Sphere
Gesture Typing, for faster typing
Wireless display with Miracast
Daydream to display information when idle or docked
Hefty amout of project butter additions
Click to expand...
Click to collapse
Even if in the words appears to be a lot, I don't know if actually those are "killers" updates.
neondunker said:
Even if in the words appears to be a lot, I don't know if actually those are "killers" updates.
Click to expand...
Click to collapse
I agree, but supporting new development is always good for a device issues fixed may help porting over more major updates.
Here's a video showing the differences:
http://www.youtube.com/watch_popup?v=mo1DmO9JH3Y
Eruditass said:
http://socialcompare.com/en/comparison/android-versions-comparison
Lockscreen widgets
360 degree images with Photo Sphere
Gesture Typing, for faster typing
Wireless display with Miracast
Daydream to display information when idle or docked
Hefty amout of project butter additions
Click to expand...
Click to collapse
Photosphere does not work on AtrixHD, no gyroscope
neondunker said:
Hi,
I was thinking about this because, almost every 4.2 rom for the Atrix HD as a lot of problems (camera, battery drain, etc), it's worth?
Flashed AOSPizza and its incredible and can't find anything that I miss from 4.2 so that's my focus: why don't put effort on 4.1 which is running great since (to me) there aren't so many differences with 4.2?
A 4.1 version of Paranoid Android would be awesome for example. Just putting the debate on the table
Click to expand...
Click to collapse
I totally agree with Neo. In fact, most dev threads run developments from 4.2 down to even Froyo!
Many devs prefer to dev on top of a proven daily rom because it's pretty much documented.
I would suggest working on a 4.1 with everything working. GPS, camcorder, data, lagless,etc
This would be a dev job on 4.1 with the purpose of tweaking a proven working rom.
Even I feel the same, why dont we make a fork of the cm 10 when we have working cam and gps everything?
Why people are goin after cm 10.1 or 4.2.
swapnil0545 said:
Even I feel the same, why dont we make a fork of the cm 10 when we have working cam and gps everything?
Why people are goin after cm 10.1 or 4.2.
Click to expand...
Click to collapse
Because its newer, simple as that. And a lot of custom roms don't do CM10 based anymore -- all CM10.1. I mean, if PAC, Slim, AOKP, PA or whatever were still doing 10 it would be worth doing.
I mean, I could probably\maybe do a 10 based rom, but first release would pretty much be it. Our devs don't really do CM10 anymore, nor do the major projects.
Android 4.2.3 and a 3.4 kernel is where we're gonna be in the future. We just need to be patient enough for Hashcode and the rest of the gang to get 3.4 working. Lots of progress has been made, but its not all the way ready. Personally, while inconvenient, I can live without gps and camcorder because I know that I'd rather have them working on a better 3.4 kernel for us than trying to fix our current out of date kernel.
I'll look into doing a 4.1 based PAC, but that's as much as I care to do for CM10 other than help someone else start their own CM10 based project.
EDIT
Gonna try and make PAC Jellybean 4.1 based on XT926 CM10 unlocked bootloader sources and kernel. Wish me luck
skeevydude said:
Because its newer, simple as that. And a lot of custom roms don't do CM10 based anymore -- all CM10.1. I mean, if PAC, Slim, AOKP, PA or whatever were still doing 10 it would be worth doing.
I mean, I could probably\maybe do a 10 based rom, but first release would pretty much be it. Our devs don't really do CM10 anymore, nor do the major projects.
Android 4.2.3 and a 3.4 kernel is where we're gonna be in the future. We just need to be patient enough for Hashcode and the rest of the gang to get 3.4 working. Lots of progress has been made, but its not all the way ready. Personally, while inconvenient, I can live without gps and camcorder because I know that I'd rather have them working on a better 3.4 kernel for us than trying to fix our current out of date kernel.
I'll look into doing a 4.1 based PAC, but that's as much as I care to do for CM10 other than help someone else start their own CM10 based project.
EDIT
Gonna try and make PAC Jellybean 4.1 based on XT926 CM10 unlocked bootloader sources and kernel. Wish me luck
Click to expand...
Click to collapse
GO FOR IT!!! a lot a people will be thankful!!
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.
Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice
kewkie said:
Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice
Click to expand...
Click to collapse
You've to try the roms for choose which is better.
Howeve the GE have some features like beats audio and some thing from sense, and the update are from htc with the latest release of android.
The CM rom have some features like the editing of status bar and so on, and are built from developers
Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms
kewkie said:
Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms
Click to expand...
Click to collapse
The problem is that mod don't like thread as: which rom is better for you?
This rom have a better battery then this?
And questions like this
Yeah i know, but it actually isnt a thread like this
I just wanna hear some experience
Google play edition roms are built on HTC's framework, or they were when it released. AOSP roms are actually built from AOSP framework using the libs and drivers and device trees that have been custom built for the one.
So the foundation of the Google Play edition, the part the user never sees, is a lot closer to stock sense from HTC minus the interface and launcher, while CM and other AOSP roms are built from AOSP style source code (CM from their source, others from their own custom source code some of which is truly custom and some of which is modified from CM source)
There's a lot of advantages to running AOSP source code based romms if you're going for an AOSP rom, but theres also a lot of users that can't use adb or fastboot and don't want to learn how and don't care to read into a rom thread, and the google play edition stuff is nice for people who want a phone with a stock google launcher, that doesn't have the sense interface heft, and just want things to work with an out of the box type experience. You know the type, they don't do a clean install for six months and wonder why the headlights in their car blink and settings force closes when they press the volume rocker.
There are certain apps that will work with the GPE and others that will only work with AOSP source, so on and so fourth. Half the people are better suited for GPE rom's and stockish foundations and then the other chunk of the people only buy their phone so they wipe it till its raw getting HTC stuff off and get custom AOSP source based roms on instead. It all depends on the user and what's better fitted for their experience.
In your case if you're not running sense roms at all and you like to follow development from what I've seen because I've seen you on here a good bit, I'd get into some real AOSP for a bit and see how you like it. The good thing about AOSP is that it's infinitely customizable and any user that wants too could be theming in a week and compiling/merging source in a month and cooking roms for their personal use. Most people way less than that. That doesn't mean that the devs publishing roms don't have a lot of time in them, it's just much easier to compile and work with the source than the HTC source is and the senseish framework.
Thanks @CharliesTheMan Thats a pretty good answer
Well i liked CM/AOSP rom's on my other phones and never used stock-ish ones.
Well, mainly i use my phone for phoning around (no sh*t! lol), social networking, taking photos and derping around a bit.
I never used the sense-features (blink feed, zoe, beats-audio etc. - i like the gallery, but honestly.. i like quickpic much more, i like it minimalism), neither like the look of sense.
I'm just a bit scared of using an AOSP rom, i dont really now why.. maybe scared of phone-signal-breaks, quality breaks or something like this.
But to be honest, i have to test it by myself i know, like the performance, stability and battery - its stuff i have to test and figure out by myself, because everyone is using the phone not in the same way and everyone got other recommendation from a rom and i got the point you wanted to say with your post
Hey all! I'm building a ROM and was wondering what your thoughts were on speed and stability on CM vs AOSP. From my experience, CM is faster but not as stable, and AOSP isn't as fast but is stable.
Please vote and/or comment on your thoughts!
CM tends to have worse battery, in my experience
Sent from my Nexus 4 using XDA Free mobile app
Tanmaynarang said:
Hey all! I'm building a ROM and was wondering what your thoughts were on speed and stability on CM vs AOSP. From my experience, CM is faster but not as stable, and AOSP isn't as fast but is stable.
Please vote and/or comment on your thoughts!
Click to expand...
Click to collapse
Here are my beliefs (anyone feel free to correct me):
AOSP is rock solid (usually). It's not the fastest, but that can be fixed. It lacks features.
CM on the other hand isn't the most solid base, but they're very good about fixing bugs. They've got (arguably) one of the largest developer teams working on an aftermarket firmware. They do have more features as well.
What you need to answer is this: How clean of a base do you want to start off with? Do you want to go for AOSP and market it as simple and close to stock with hand-picked features and optimizations? Or do you want to start off with a CM base, having features that are now nearly ubiquitously considered "necessary"?
Connor Baker
THEBANDIT420 said:
CM tends to have worse battery, in my experience
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I've never experienced this, but I can see it happening because of the smaller range of kernels (since it's CAF).
Connor Baker said:
Here are my beliefs (anyone feel free to correct me):
AOSP is rock solid (usually). It's not the fastest, but that can be fixed. It lacks features.
CM on the other hand isn't the most solid base, but they're very good about fixing bugs. They've got (arguably) one of the largest developer teams working on an aftermarket firmware. They do have more features as well.
What you need to answer is this: How clean of a base do you want to start off with? Do you want to go for AOSP and market it as simple and close to stock with hand-picked features and optimizations? Or do you want to start off with a CM base, having features that are now nearly ubiquitously considered "necessary"?
Connor Baker
Click to expand...
Click to collapse
Valid points, I see CyanogenMod being geared as much more developer friendly and extensible, they even have better documentation for AOSP's tools than AOSP does
I want the ROM to be stable and fast, but also ready for customization, where I see AOSP not being very extensible.
So speed and stability is democracy now?
Actually if you are building a ROM from source, you are better off starting with aosp and merging the caf patches then go from there. You can look at patch commits/gerrit to see how to add in the features that you want since the code is normally available to see and will give you what line and all. In the process, you have something to call your own and learn the coding structure and source which is invaluable
Sent from my C6916 using XDA Free mobile app
cm, fast? lmao..
simms22 said:
cm, fast? lmao..
Click to expand...
Click to collapse
Keep Preaching brotha! Lol
He is Right about CM
tommypacker said:
Keep Preaching brotha! Lol
Click to expand...
Click to collapse
The fact is that CM is starting to be real SLOW.
Go for AOSP based roms! Build with linaro? That's even faster.
v3ng3anc32002 said:
The fact is that CM is starting to be real SLOW.
Go for AOSP based roms! Build with linaro? That's even faster.
Click to expand...
Click to collapse
cm was fast until about mid 2012. then they just started piling on as much as possible into the rom and it has been slower since. when steve(cyanogen) used to spend much time working on cm kernel, thats when cm was known for speed, back in the beginning and a little after cm started. back then, they werent about feature, more about minimalism. now its all about feature.
AOSP>CM
Always.
At any aspect.
CM has become so low and weak ROM since 2013. In the past it was the fastest and the most non-bull**** custom firmware but now as it's available for so many devices it's become sluggish, slow and the quality doesn't even exist. Another thing against CM is that they decided to use CAF code on Nexus devices. I can't understand it as well as other devs working in Nexus sections. I remember CM7 on my legendary HTC G2. It was so fast and damn feature-filled as for those times. Now it's gone. Formerly, my first thought on custom ROMs was CM, now it's quite different... I am so disappointed with CM nowadays.
Just my opinion tho ?
Sent from my Nexus 5 using Tapatalk
The hell are people knocking caf code for??? It is aosp code with fixes for specific hardware by the people who actually make the hardware, wtf would you not use it for????
As far as cm fast, bwhahahahahaha, it hasn't been fast since about cm4 back on the g1/mytouch when dwang came into the picture. Cm's goal evolved to bleeding edge features and getting on as many devices as possible while dwang was straight aosp Roms with speed and stability as the goal
Sent from my C6916 using XDA Free mobile app
If you own a nexus CyanogenMod is just as stable if not more so. Latest nightly is flawless.
I actually installed 30/6/2014 Nightly and seems faster to me in some areas, such as animation smoothness.
I was on PA 4.4 Final previously and hadn't touched CM11 for 3+ months.
Both were tested with latest Adreno drivers(June), same kernel, same kernel settings and the same Gapps; only the ROM changed.
Konstantinos said:
I actually installed 30/6/2014 Nightly and seems faster to me in some areas, such as animation smoothness.
I was on PA 4.4 Final previously and hadn't touched CM11 for 3+ months.
Both were tested with latest Adreno drivers(June), same kernel, same kernel settings and the same Gapps; only the ROM changed.
Click to expand...
Click to collapse
faster than velocity?
pincher65 said:
faster than velocity?
Click to expand...
Click to collapse
Isn't Velocity the ROM that has ART by default? And lots of commits to ART. Still, ART is experimental in KitKat, so in the L release there will be lots of changes. I'd rather use something which doesn't have commits to something experimental(such as ART).
Also, I must note that Velocity has changed the animation to 0,75. This results as being "faster" (because of transition) but it's not. Try testing both @ 1.0 animation speed and see for yourself.
Konstantinos said:
Isn't Velocity the ROM that has ART by default? And lots of commits to ART. Still, ART is experimental in KitKat, so in the L release there will be lots of changes. I'd rather use something which doesn't have commits to something experimental(such as ART).
Also, I must note that Velocity has changed the animation to 0,75. This results as being "faster" (because of transition) but it's not. Try testing both @ 1.0 animation speed and see for yourself.
Click to expand...
Click to collapse
A real test would be turning animations completely off and seeing what's faster. That's where real speed and optimisation can be noticed. 1.0 is just too damn slow.
Konstantinos said:
I actually installed 30/6/2014 Nightly and seems faster to me in some areas, such as animation smoothness.
I was on PA 4.4 Final previously and hadn't touched CM11 for 3+ months.
Click to expand...
Click to collapse
Try stock AOSP, way faster than PA.
I've got 2 nexus 4s so I can do nexus 4 vs nexus 4. Nothing beats stock jellybean.
Sent from my Nexus 4 using XDA Free mobile app
calyxim said:
Try stock AOSP, way faster than PA.
I've got 2 nexus 4s so I can do nexus 4 vs nexus 4. Nothing beats stock jellybean.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
stock jellybean??? kitkat??
I'm stock unrooted on my n5 so far, running art and no animations. Feels blazingly fast to me. I miss custom Roms for the themes and a couple features they usually include but other than that stock has been almost 100% stable even with art.
I reboot it once every week or two and saw one soft reboot the other day in the couple months I've had it, not sure what caused it.
Still trying to decide if its worth rooting and what ROM to run. I like art which rules out stock with xposed.
I've been a chronic ROM flasher on every phone I've had until this one. It just works so good I'm afraid to mess with it. Especially when I've got warranty.
Sent from my Nexus 5 using XDA Free mobile app