***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.
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.
[INFO] Android 4.3 JSS15J&JSS15Q vs. JWR66V&JWR66Y, Custom Kernels and Graphic Issues
So, since this issue pops up often in various threads ever since 4.3 was released, I thought I'd make a thread I could point people to instead of repeating the same explanation over and over.
This has been discussed greatly in various Kernel/ROM development threads and I've been even getting PM's about it so I'll try explaining everything here. Most info is taken from discussions made on CyanogenMod-related threads, Franco kernel thread, thracemerin's WiFi-fix thread, and Google-related sources, so thanks also goes to everyone who participated.
On to business...
Background:
When Google released Android 4.3, it came in a few forms. One is the familiar OTA update zip and factory images. This is what people refer to as 'stock'. The build number for that stock release is JWR66V, also known as Android 4.3r1. This was later updated to JWR66Y (Android 4.3r1.1).
As you all know, Android is open source, which leads us to the Android Open Source Project (AOSP). This is where the source for Android located, and one could build the operating system/kernel (with provided drivers) from scratch and make a working flashable operating system. This is also the 'base' for custom ROMs.
AOSP has newer android revisions - Android 4.3r2.1, build number JSS15J, and Android 4.3r2.2, build number JSS15Q. These builds are newer than 'stock' JWR66V/JWR66Y, but they are official, are made by Google, and are available for anyone to build from scratch, just like JWR66V/JWR66Y. The differences are Google Apps, such as Google+, YouTube, Gmail, etc, which will not be included in an AOSP build, but could be downloaded from the store (or available as a flashable zip) anyway. AOSP also has a different browser while 'stock' comes with Google Chrome (which you could manually download if you wanted to). The system itself is still the same Android. If one decides to build Android from the older JWR66V/JWR66Y revisions, they will have the same system as someone else who flashed stock.
Why didn't Google release JSS15J as stock?
A Google employee mistakenly thought that JSS15J only has changes related exclusively to the new Nexus 7 device. He later apologized and acknowledged his mistake. JSS15J has an updated Nexus 4 kernel with dozens of GPU commits/improvements.
Which build is better?
Depending on who you ask. If newer is better, JSS15Q is better. If factory images are better, JWR66Y is better.
Which build should I use?
People who like factory images will stay with factory images. People who like the stock experience but care less about "factory images" could use a clean non-customized JSS15Q build. In a way, JSS15Q could be considered 'stock AOSP' if it's not customized. It's even more minimalistic than what comes with the factory images, because applications such as Google Keep/Earth/Maps and so on are not forced as system apps, and can be optionally installed from the store only if you want them.
Any other differences besides the updated kernel/GPU commits?
Most changes are under-the-hood. There was an updated network setting found in JSS15J/Q that doesn't exist in JWR66V/Y.
I heard something about a Wi-Fi change though?
There is indeed a major difference related to Wi-Fi. I won't get into many details here as there is a dedicated thread with months of discussions, but in short, JWR66V & JWR66Y still have the Wi-Fi notification delay issue that 4.2.2 had. This is because Google turned off ARP offloading for those builds, but later turned it on in JSS15J & JSS15Q. It was also on in JWR66N, the leaked unofficial build that we got prior to the official release.
If Google were to build a new factory images now from JSS15Q, it would have ARP offloading on, and Wi-Fi notification delays fixed. The change is only to an .ini file and the drivers are the same, so while a fix is needed for JWR66V/JWR66Y, it's a simpler fix. If you use JSS15Q you don't have to flash any Wi-Fi fixes at all.
What does this mean for Custom ROMs?
Custom ROMs are usually synced with the latest AOSP revisions and changes. CyanogenMod's Android build is JSS15Q, and the same goes for rasbeanjelly, Carbon, and most custom ROMs. Clean or clean-ish JSS15Q AOSP builds are also available for those who still want both the newest revision and the stock experience, just check the development threads.
HELP! My screen is stuttering and/or has weird green colors and/or doesn't respond properly to touch and/or is yelling at me!
That is mostly why this thread was needed. As mentioned before, JSS15J&JSS15Q have an updated kernel with some GPU fixes. This means that your kernel MUST match your ROM for the issue to go away. There are workarounds, such as disabling hardware overlays, but that is not really a solution. No hardware overlays = reduced performance and possibly other issues.
The basic rule is this:
If you use JWR66V/JWR66Y, either stay with its stock kernel, or MAKE SURE the custom kernel you flash was based on JWR sources.
If you use JSS15J/JSS15Q, either stay with its stock kernel, or MAKE SURE the custom kernel you flash was based on JSS sources.
This is of course a headache for kernel developers, as they need to either drop support for one version, or release two versions each time. Many kernel developers are already offering two version of their kernels - one for JWR-based builds and one for JSS-builds.
This means that if you use the AOSP build or most custom ROMs, you will have the screen issues if you use JWR-based kernels.
So there you have it. Unless some other solution is found, there will have to be 2 kernels - one for each build.
Well done
Wayne Tech Nexus
Anyone have links to a pure AOSP build with literally no alterations?
Sent from my Nexus 4 using Tapatalk 4 Beta
jaju123 said:
Anyone have links to a pure AOSP build with literally no alterations?
Click to expand...
Click to collapse
There are two I know of, they do have some very slight changes you could read about in their threads, I don't know of one with literally zero alterations whatsoever, but again the changes are very minor:
[ROM][JSS15J] aosp 4.3 for Nexus 4
[ROM][28/07/2013] AOSP JSS15J KALO v3.0
Cheers for the clear up, was doing my head in with all the weird builds
Sent from my Nexus 4 using Tapatalk 4 Beta
Is there any way we can (nicely) ask Google to release a factory image from the JSS build? I think that would be the perfect solution, and I don't think it is really too hard for them to push it.
redsmith said:
Is there any way we can (nicely) ask Google to release a factory image from the JSS build? I think that would be the perfect solution, and I don't think it is really too hard for them to push it.
Click to expand...
Click to collapse
They could definitely do it if they wanted to, probably somewhat easily too. The OTA is being pushed slowly for a reason - not just for bandwidth purposes, but so that if some mistake happened, not all devices would be affected. It's probably not a very high priority for them like what happened previously with the December bug, but they could release a JSS15J-from-JDQ39 OTA to devices that haven't been updated yet, and JSS15J-from-JWR6V for those who did update. Posting factory images is easier, and the binaries are already good for both JWR6V and JSS15J. If they chose to release it, we'd forget about this whole thing 1-2 weeks later. But it's hard to say if they'll listen. Might be worth a try as long as it's done in nice/acceptable ways and not by spamming/yelling/threatening and so on.
They won't release new factory images...
Jean-Baptiste Queru said so...
He said both branchs are the same with the only difference in JSS15J being the new stuff for Nexus 7...
The new GPU commits are from the other branch... So that both matchs and don't give tearing effects or other problems...
Enviado do meu Nexus 4
He had some update statements since. Here they are:
In theory, JSS15J should work just as well as JWR66V for the existing devices. In practice, I expect that there could be minor differences (except for the new Nexus 7 where there are big differences), so if you're targeting a single device you might as well use the source code that matches the retail version the most. Personally, I like to live more on the bleeding edge, so when I carry an AOSP device I'm more likely to be running the master branch.
Click to expand...
Click to collapse
Here's an long-ish explanation of what happened:
-For a number of reasons, the kernel is built separately from the Android tree. We submit binaries of the kernel in the Android tree.
-Those binaries are large. In Google's internal tree, there are 1.5GB of Nexus 4 kernel binaries. With the way our tools work, that's 1.5GB of data that needs to be downloaded and stored by each user in each source tree. At the same time, the binaries don't have any significant value, since the value is in the source history, which is stored separately.
-To avoid making every AOSP user download gigabytes of unnecessary kernel binaries, starting with Nexus 4 (and now also in the new Nexus 7), we've been storing kernel binaries in dedicated projects, and I maintain a parallel history for AOSP that only contains the binaries that are necessary. Right now for Nexus 4, that tree is 31MB (to compare to 1.5GB).
-The retail release process of a new version is actually different for existing devices and for the new Nexus 7. To better reflect that, they each got their release branch, with existing devices in the JW branch (jb-mr2-release) and the new Nexus 7 in the JS branch (jb-mr2.0-release). JW entered final stabilization earlier than JS, which means that the jb-mr2-dev branch and the master branch in AOSP are closer to JS than to JW.
-To save space in the AOSP kernel projects, I try to have as few kernel binaries as possible in there, which means that I prepare those branches at the last minute (in this case I did that on Monday). During testing, I don't stage those projects and I manually use kernels directly from the development branches. For Nexus 4, when I did the final staging on Monday, I only included into the AOSP what ships to end users, i.e. from the JW branch, so I explicitly didn't include the kernel from the JS branch and I used the kernel from JW everywhere instead.
-Since the only changes in JS (compared to JW) were supposed to be related to the new devices, I assumed that the N4 kernel would be the same between the two (without actually checking), and I did all my testing of jb-mr2.0-release, jb-mr2-dev and master with the JS kernel (which was easier as it allowed me to use the same process for Nexus 4 and for the new Nexus 7). One of the changes done for the new devices was in the GPU code, in a way that required a new kernel for Nexus 4.
-The fix was to add the JS kernel to the relevant branches in AOSP.
So, there you have it: I mistakenly assumed there there'd be no kernel changes for N4 between JW and JS, and from there I did all my testing with the wrong kernel.
Sorry about that.
JBQ
Click to expand...
Click to collapse
markd0wn said:
He had some update statements since. Here they are:
Click to expand...
Click to collapse
So peolple who are on stock are outdated and still not enjoying all the gpu optizations?
Correct me if im wrong
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
C4SCA said:
So peolple who are on stock are outdated and still not enjoying all the gpu optizations?
Correct me if im wrong
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
Click to expand...
Click to collapse
Technically you are not wrong. It's a fact that JSS15J and its kernel has GPU optimizations/commits that are not included in the JWR66V build.
markd0wn said:
Technically you are not wrong. It's a fact that JSS15J and its kernel has GPU optimizations/commits that are not included in the JWR66V build.
Click to expand...
Click to collapse
So this 4.3 update is a huge fail for nexus 4 owners... And i was thinking that i wasnt going root it again...
Google messed up this time
4.3 is almost all about the gpu opt. and now people dont have it all on stock? ? ?
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
C4SCA said:
So this 4.3 update is a huge fail for nexus 4 owners... And i was thinking that i wasnt going root it again...
Google messed up this time
4.3 is almost all about the gpu opt. and now people dont have it all on stock? ? ?
typed from my NeXuS 4 tasting some revamped Jellybeans (stock 4.3).
Click to expand...
Click to collapse
I don't know how huge those optimizations are. I'm sure someone will do some GPU-specific benchmark comparison between the builds at some point and see. But yes, a mistake did occur. The average person will be updated to JWR66V (at least at this point) only. Others could install JSS15J manually from one of the threads mentioned in the previous page.
Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?
markd0wn said:
They could definitely do it if they wanted to, probably somewhat easily too. The OTA is being pushed slowly for a reason - not just for bandwidth purposes, but so that if some mistake happened, not all devices would be affected. It's probably not a very high priority for them like what happened previously with the December bug, but they could release a JSS15J-from-JDQ39 OTA to devices that haven't been updated yet, and JSS15J-from-JWR6V for those who did update. Posting factory images is easier, and the binaries are already good for both JWR6V and JSS15J. If they chose to release it, we'd forget about this whole thing 1-2 weeks later. But it's hard to say if they'll listen. Might be worth a try as long as it's done in nice/acceptable ways and not by spamming/yelling/threatening and so on.
Click to expand...
Click to collapse
Agreed. Any way we can contact them? Maybe in their support pages? I'm kind of lost here =D
We should definitely give it a try, we've got nothing to lose.
Why I can't boot into recovery?
I flashed factory image JWR few days ago, everything was good until today I just realized that I cannot boot into stock recovery. Everytime I enter bootloader and select recovery I only get dead android image with red exclamation mark.
Anybody experience this too?
Wonderful! I've been looking for somerthing since 25/07!
Thanks!!
simorangkir_dcs said:
I flashed factory image JWR few days ago, everything was good until today I just realized that I cannot boot into stock recovery. Everytime I enter bootloader and select recovery I only get dead android image with red exclamation mark.
Anybody experience this too?
Click to expand...
Click to collapse
Hold volume up + down and press the power button (may have to do it a few times). The stock recovery has its options hidden unless you press that combination once you get to the screen you are seeing.
Sent from my Nexus 4 using Tapatalk 4 Beta
mattkroeder said:
Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?
Click to expand...
Click to collapse
Can someone confirm this?
mattkroeder said:
Thanks for the info. I flashed the factory images last night thinking I would much rather go with official images from now on. This thread tempted me to give the AOSP builds another try.
Honestly though, I don't know important the optimizations are. Maybe it's just me. Maybe it's just my own device...... but I find the stock build smoother than the AOSP builds. I get stutters while scrolling through my mms messages, for instance. And transitions on the stock feel smoother so far.
How does one know if we have delays in our wifi notifications though?
Click to expand...
Click to collapse
Same too ,i feel stock smoother than AOSP .
Sent from my Nexus 4 using Tapatalk 4 Beta
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
The title says it all. Is anybody interested in a Stock GPE Build for the Sprint S4? The purpose of this build would be a Stock GPE ROM with changes only needed to make it function correctly.
Basically, Keeping it as close as possible to stock GPE for the device with the exception of root/supersu and busybox.
The reason for this would be so dirty flashes work better and be somewhat supported and tested.
Danvdh's GPE build is awesome with many features however there is people like me that need a somewhat stable phone and don't feel like re-building and wiping the phone every time for a new flash.
Let me know what you think.
I think it would definitely be a good idea. Everyone has different needs and as you can see from reading the threads, it seems each phone acts differently on each of these Roms. Thank you for taking time to work on it if you do. If you need someone to test to see if your work causes a phone to glow in the dark, let me know!
pclov3r said:
Mods: If this is not the correct place for this please move it.
The title says it all. Is anybody interested in a Stock GPE Build for the Sprint S4? The purpose of this build would be a Stock GPE image with changes only needed to make it function correctly.
Basically, Keeping it as close as possible to stock GPE for the device with the exception of root/supersu and busybox.
The reason for this would be so dirty flashes work better and be somewhat supported and tested.
Danvdh's GPE build is awesome with many features however there is people like me that need a somewhat stable phone and don't feel like re-building and wiping the phone every time for a new flash.
Let me know what you think.
Click to expand...
Click to collapse
Ahhhh was wondering why dirty flash wasn't working. I'm gonna go with Yes! but it's honestly not much of a hassle either way.
As long as I can get voice-mail.
Sent from my Nexus 7 using Tapatalk
Go for it just as long data,voice, sms and mms work and it does say sprint not digital roam or no service or insert sim
As long as everything works and there aren't any crapola CM add-ons, I'm in for a try.
troyboytn said:
As long as everything works and there aren't any crapola CM add-ons, I'm in for a try.
Click to expand...
Click to collapse
Thanks you made me laugh with that comment.
It exists...
http://forum.xda-developers.com/showthread.php?t=2557353&highlight=modem
No, it doesn't. That rom has been modded to hell and back and has nore issues with each release (which usually requires a complete wipe to even function). The OP of this thread is asking if we are interested in a more closely stock, more stable GPE rom without the mods and CM junk.
Would be nice if there was a actual source of the GPE I have a pure stock aosp build for jflte but its kk no mods no CM crap
Hey guys sadly this idea will have to be placed on hold for now. Somewhat busy with life. Sorry
I have one and love it. Do not know if voicemail works though...
Hey guys, I suppose some of you have had a xiaomi in the past and I have two questions for you and maybe someone that has some knowledge about xiaomi.
1) Currently how's Xiomi dealing with privacy? I remember 1 or 2 years ago Xiaomi has hit with strong reports of leaking information to their government (chinese) and everything we did on the phone would be seeded to their servers, even SMS's and other stuff..
2) How's the ROM support usually for Xiaomi? Do they usually get a stock based ROM, which has no bloatware and some nice tweaks?
Thanks everyone!
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
arnabbiswasalsodeep said:
Afaik, being a mi3 user, they had a "data sharing" option on by default in miui which is now changed to be off. Personally i never considered it much as there were already devs who had made custom rom for the device, i think over the last two years i might only have used miui for about 4 to 8 months.
No bloatware, but if u r not a previous user, u might find some apps useless (it has its own clean master replacement app). So yeah, there are a lot of options for tweaks n stuff by default too. Hopefully this answers your questions. (and add a question mark to the title, it looks like u r going to rant about Xiaomi by reading the title, lol)
Click to expand...
Click to collapse
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
SlyUK said:
Do you think there will be much custom rom/kernel support for the Mi 5 (or does this depend on Xiaomi allowing for an unlocked bootloader together with release of kernel sources) ?
Click to expand...
Click to collapse
There will sure be support for custom roms even when the kernel source isn't there, my device had custom roms even before kernel source was released, although there were a bit bugs due to it and only a few (like 5 to 10) custom roms were there, bit with the release of sources, it jumped to 50+. And my device had the bootloader unlocked by default, which even i didn't knew until i rebooted to it. Although the fastboot wasn't able to get the info about the bootloader (like version, etc). IDK if any new devices require to unlock it but i don't think it should be hard as they support it, so that won't be a barrier for development.
TL;DR- less n buggy roms w/o kernel source, floods of roms and custom kernels after source, nothing to concern about bootloader.
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
zelendel said:
There maybe some rom development from a few people that get the device and maybe from cm. But that's about it. Non of the big name team roms will have official versions, just maybe ports.
As for the security and privacy. That is up in the air as it seems even on custom roms they some how have managed to still keep track of the devices. One person on the MI note found that even while not on miui for months that they still had a current backup of all his apps and info.
Website signature
Click to expand...
Click to collapse
With regards to porting an official rom, I suppose these would be regarded as Unofficial versions. If that is the case is there any real disadvantage in having the "Port" as opposed to have the "Official" version ?
Ports normally will have some bugs as this happens due to not having some things for device built into the code.
Data leak & Software development
Yes I also heard that even with a custom ROM on the device they still found a way to make the device connected and synching information with their servers, which I don't find that funny..
I wanted to know if this data leak is still present in the previous flagship, anyone tested it recently?
It's good to know that it has nearly no bloatware from what you are saying me, but if it has something I don't find useful I may just freeze the app.
Also does anyone know if Xiaomi usually takes long times to update the software of their devices (I heard that they were an exception in relation to other Chinese manufacturers) and release the kernel sources for the ROM developing community or are they pretty good on this area?
Thanks!
:good: :good: :good:
No they are terrible about it. Normally when they post the kernel source it is incomplete and broken.
As for updating. Until very recently they based their os on 4.4 and when asked why they said they didn't care about official android versions.
As for bloat that depends on how you look at it. Miui is about as bloated as TW or HTC Sense.
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
SlyUK said:
@zelendel In terms of big name team roms having official versions, would kindly give a few examples ?
Click to expand...
Click to collapse
The biggest are the one or two devices (cant remember their names off the top of my head) that were able to get/fix the kernel source and device trees which CM picked up. So some of the teams that use CM source as a base like AICP also picked up Official versions for the devices.
Then you have the Roms that are based on AOSP instead of CM. As they dont use CM as a base ( Maybe some parts) These roms like Slim or Dirty Unicorns seldom see official versions of the rom. Normally you might get a port here and there. It all depends on if the one of the devs gets the device as most teams don't offer official support for devices they do not own.