Related
I bought this 32 GB HTC One T-Mobile phone which is unlocked, and will be here in a few days. It IS an M7, right? It has rooted stock firmware (not sure if Sense or AOSP) but will probably flash a custom ROM. I read up on the Google Edition bootloader/recovery, and read Vomer's guide as well. I'm not sure if I need to do the whole GE process before I flash a GE ROM, or which GE/AOSP ROM I should go with. It seems like most of them are Sense, so which ones are AOSP?
The one original android development forum is the asop Roms .
There are GE versions that will work with your current setup. The only reason to "convert to the GE version is for official ota updates.
Sent from my HTC One using xda premium
ihavoc said:
The one original android development forum is the asop Roms .
There are GE versions that will work with your current setup. The only reason to "convert to the GE version is for official ota updates.
Click to expand...
Click to collapse
The what? Oh, you mean the ORIGINAL One forums has AOSP ROMs? How do you tell the difference between the original One and the 2013 model?
How often are there OTA updates? Those are usually compiled into current custom ROMs, right?
In the case of the HTC One, would Sense be better over AOSP (not just because of the camera)? It would seem there are more Sense-based ROMs than AOKP/AOSP ones. I also see a few Sense/GE ROMs. What exactly does that mean? Is it just Sense with the additional AOSP settings and options? If I wanted the best camera, should I just stick with Sense?
UndeadSquirrel said:
The what? Oh, you mean the ORIGINAL One forums has AOSP ROMs? How do you tell the difference between the original One and the 2013 model?
How often are there OTA updates? Those are usually compiled into current custom ROMs, right?
Click to expand...
Click to collapse
There is a android dev and there is an original dev. Read up on the stickies and you'll get an explanation, after you read ask questions with direction so users won't have to type up 2-3 paragraphs explaining everything out .
Sent from my SGH-T999 using xda premium
UndeadSquirrel said:
The what? Oh, you mean the ORIGINAL One forums has AOSP ROMs? How do you tell the difference between the original One and the 2013 model?
How often are there OTA updates? Those are usually compiled into current custom ROMs, right?
In the case of the HTC One, would Sense be better over AOSP (not just because of the camera)? It would seem there are more Sense-based ROMs than AOKP/AOSP ones. I also see a few Sense/GE ROMs. What exactly does that mean? Is it just Sense with the additional AOSP settings and options? If I wanted the best camera, should I just stick with Sense?
Click to expand...
Click to collapse
Stock Sense 5 is very good. You can try AOSP ROMs and see if you don't miss the Sense features. The camera app has been ported to AOSP if I remember well so you don't loose Zoe/Highlights.
I'm stock and haven't planned on going o AOSP or other custom ROMs because I'm more than happy with Sense 5, except some things here and there, but the same can be said about any other ROM. the one thing I change was the launcher. It's good, but not as flexible as Nova, specially for adding more columns/rows to home screens.
I thought this was the sub forum for stock/ stock-modded roms and 'original development' was for all other roms. What gives? Page one has at least 2 AOSP roms and an app mod for xposed. I'm only asking because it's been this way for weeks and it's not making much sense.
I was wondering the same
phantomzer0 said:
I thought this was the sub forum for stock/ stock-modded roms and 'original development' was for all other roms. What gives? Page one has at least 2 AOSP roms and an app mod for xposed. I'm only asking because it's been this way for weeks and it's not making much sense.
Click to expand...
Click to collapse
Original Android development is supposed to be for roms built from source code and android development is for roms not built from original source.
It has nothing to do with AOSP or Sense really, but still there's a lot of roms that aren't in exactly the right category and some of that is because we are taking items with lots of grey components and forcing them to be black or white so to speak. But that's the idea behind the concept when it was formed.
And due to it being sense, which is closed source proprietary, kernel excluded, it means that it's a lot harder to make the argument that a sense rom should be in original development, whereas with AOSP roms they will be in both. There have been device sections though where sense roms have been in original development, usually it was one or two major roms with a lot of custom source or a bunch of custom java and tweaks added, and then in android development it was just roms with minor changes and tweaks that were borrowed.
???
No disrespect but who cares as long as development is happening, some devices have no development at all, so just enjoy having variety my friend.
Why is there a question in the Dev section? Lol, you've got your answer. Now who is gonna answer my question. ?
Sent from my HTC One using XDA Premium 4 mobile app
Because ROMs in this section are either sense based or OEM from HTC or Google meaning the bugs and other issues you get from AOSP roms shouldn't be found in roms you install from this sub forum. It can get confusing quickly if there are two different sub forums with essentially the same material. I wasn't asking out of malice, I was more trying to understand what was going on lately so I can browse appropriately. I got my answer. /thread. Thanks Charles!
Moderator update,
Thread moved to Q&A as we do not allow question threads in the development forums.
Now to answer your question, which is a good question. There are certain OSAP Roms in the AD forum for the following reasons.
Original development is just that. It is what makes the rom original. This applies to both sense and OSAP Roms. For an example of a sense rom that could be in original development is the venom rom. They have so much code in the rom that is original it makes it different from the rom it was built from.
In terms of OSAP Roms simply building it from source does not make it original. It needs extra code to make it original. Eg official CM Roms are original because of this, an unofficial build is not original so does not belong in OG so goes into AD.
So to sum up. Simply building a rom or kernel does not qualify for OD. It is the amount of original code that the developer has added to the base rom that determines which section the rom goes in.
Sorry for the long post hope it clears things up. Let me know if you need any more info.
Ghost
***NOTE TO MODERATORS:
I hope you can see what I'm trying to do with this thread. If some kind Dev takes the time to answer soon, then this could be a very informative resource. If no one answers, then the thread is pointless and I will totally understand if you decide to delete it. Thanks ***
Hi to all you amazing Custom ROM chefs.
I'm sure loads of us are waiting for the roll out of M7-based Android 5.0 ROMs, especially as we know the GPE version is imminent, but maybe like me they don't understand the full process. So would someone kindly let me know the following, and by posting it here I'm sure many other people will be able to understand.
Once the GPE image is released, how long do you expect it to take before the image is edited to run on non-GPE phones? And who actually does this? Do all you devs wait for the CM12 nightlies to be released and then base your own ROMs on that? Or is the port very easy once HTC release the GPE ROM, which allows you to build your ROMs from scratch? I read enough on xda to understand that there are some 'big' players out there, like ARHD, Paranoid Android, SlimRom, ASAP, etc. Do other devs wait for these and then do their own mods? And (potential 'grey area') where do the images actually come from? Do HTC happily give their images to the main devs, knowing that there's a whole User Base who will stick with their HTC handsets if they can customise them with 'unofficial' ROMs? After all, if we stick with our M7s and M8s, then we're not buying Samsung or Nexus and the market share tilts ever-so-slightly in favour of HTC.
I hope someone will take the time to explain the Custom ROM process, and I also hope this will stop other users from posting "when, when, when?" threads (irony appreciated).
Thanks in advance,
miles_muso
Since anyone hasn't answered this yet, I'll throw in what I know...
There are three types of ROMs: Google Play Edition, Sense, and AOSP.
GPE roms are stock, Nexus-like roms that have underlying frameworks similar to that of Sense (which I'll get into in a sec) however they are aesthetically virtually the same as the Nexus devices. They receive updates much quicker than their Sense counterparts due to HTC not having as big a role in modifying the interface, etc. They also have apps that are very similar (if not the same) as AOSP apps. SinlessRom GPE and Android Revolution (GPE) are examples of this.
Sense roms are HTC roms. HTC takes the updates Google releases and then proceeds to change it drastically, both under-the-hood and aesthetically. Their interfaces are heavily modified and they often have different apps from AOSP and GPE. These take the longest to release new versions of Android for. Android Revolution HD (Sense) is an example of this.
AOSP comes straight from Google. ROMs such as CyanogenMod are a modified AOSP. AOSP Lollipop is already available to build and it has been built for our M7. AOSP roms are (nearly always) aftermarket roms and can work on all S-On m7 devices. ParanoidAndroid and CyanogenMod are examples of this.
If a user has a phone that ships with HTC Sense, they will typically have to achieve S-Off before flashing a GPE rom. I'm not sure if the same is true for the vice versa, however I can imagine it is.
Now, to answer your question, you can build roms from scratch already (and there are some that have been released). You can't build Sense or GPE from source and you must modify official versions, leaks, or ports. You can build AOSP from source, and since we have somewhat-proper kernel source for Lollipop, it's not as difficult as it is for less-popular devices that don't have that source.
I personally feel like the release of GPE will be most helpful for AOSP in the aspect of kernel sources (as it will be the first OFFICIAL and hopefully BUG-FREE Lollipop for the m7 devices).
I'll add to this post if I can think of anything else.
Hi nuuits,
Thanks for your reply, this is EXACTLY the kind of info I wanted here. Hopefully this will help a lot of people understand the Custom ROM development phases. And, may I ask, when do YOU think we'll start seeing the first batch of ROMs based on Android 5 (apart from CM12, which, as you state, is currently available)?
miles_muso said:
Hi nuuits,
Thanks for your reply, this is EXACTLY the kind of info I wanted here. Hopefully this will help a lot of people understand the Custom ROM development phases. And, may I ask, when do YOU think we'll start seeing the first batch of ROMs based on Android 5 (apart from CM12, which, as you state, is currently available)?
Click to expand...
Click to collapse
Apart from AOSP, you can expect GPE and Sense ROMs when they're either leaked, ported, or released officially.
Leaks are "early builds" (not always intended for the general public's use) that are, well, leaked to sites such as XDA. Ports occur when you take a ROM for one phone (let's say the M8 ) and port it over to ours. Official releases are just that- ROMs pushed by HTC and/or Google.
You can expect custom GPE ROMs when one of the above occurs. I'm putting my finger on "official release", which is projected for the coming week(s), however I can never really know!!
Sense ROMs will come much later than GPE (but still within HTC's 90 day limit- if they keep their end of the bargain). There's an even toss between the above three methods imo- as the m8 will get the Sense update before the m7, we might see a port. Leaks are somewhat likely and the official release will come when it comes (which is hopefully before and probably around the 90 day mark- so January at latest).
After the initial stock ROMs are leaked, ported, or released, there are bound to be updates to your favourite custom ROMs, but of course that depends on the developer in question.
I am looking for a stock based ROM, which there doesnt seem to be many of, that has the ability to change around the nav buttons. I really want to swap that recents and back button and I know we have been able to do it on AOSP based ROMs for a while now. However, AOSP based ROMs get significantly worse battery life from idle drain than the stock based ROMs on my phone at least so I would really like to find one with a stock base. Does such a ROM exist and I am just missing it?
EniGmA1987 said:
I am looking for a stock based ROM, which there doesnt seem to be many of, that has the ability to change around the nav buttons. I really want to swap that recents and back button and I know we have been able to do it on AOSP based ROMs for a while now. However, AOSP based ROMs get significantly worse battery life from idle drain than the stock based ROMs on my phone at least so I would really like to find one with a stock base. Does such a ROM exist and I am just missing it?
Click to expand...
Click to collapse
well, if you wamt a real rom with the additions, then you have aosp as an option. real developers dont put up a stock rom because no source is provided. no source equals no building roms. some people learning how might use stock, but they dont build it, they just add add-ons to it. something like what you are looking for requires framework changes, so the rom has to be built from scratch. amyways, have you looked if xposed provides an option for you?
simms22 said:
well, if you wamt a real rom with the additions, then you have aosp as an option. real developers dont put up a stock rom because no source is provided. no source equals no building roms. some people learning how might use stock, but they dont build it, they just add add-ons to it. something like what you are looking for requires framework changes, so the rom has to be built from scratch. amyways, have you looked if xposed provides an option for you?
Click to expand...
Click to collapse
Oh really? I thought Google had all the source for builds for the Nexus devices. Hmm. That must be why I cant find what Im looking for then. lol.
So Xposed works now on Lollipop? Ill give it a look. Thank you.
EniGmA1987 said:
Oh really? I thought Google had all the source for builds for the Nexus devices. Hmm. That must be why I cant find what Im looking for then. lol.
So Xposed works now on Lollipop? Ill give it a look. Thank you.
Click to expand...
Click to collapse
yea, xposed now works on lollipop. and yea, stock is only build by google. but its easy enough to add some things to it. and aosp is where all the code is provided for us to build our own roms. google dors have all the source, tbey just dump it into aosp for us.
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
MrBrady said:
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
Click to expand...
Click to collapse
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
simms22 said:
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
Click to expand...
Click to collapse
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
MrBrady said:
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
Click to expand...
Click to collapse
well, first off, aosp and stock are two completely different roms. stock roms also have closed source code included, where aosp roms dont have that code included, so they WILL run differently, as two different roms should.
---------- Post added at 03:20 PM ---------- Previous post was at 02:58 PM ----------
anyways, the answer to your question is really simple.. better is whatever is better for you,personally. to you, image based roms are better. for me, aosp is better.
as a real answer of which is better doesnt exist, its all which is better for you(or me).
Had you followed the rules you would know threads like this don't stay open long.
There is no best. Or better. There is only what works for you.
Most people that get a nexus device do it for the active development. Which does mean some bugs here and there, but that is the fun. In learning, finding and killing bugs. If you got a nexus for any other reason you really are not doing yourself any favors.