Related
[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 ask this because we are now in December. I have recently fired up an old Z1 and want to breathe new life into it. So I have been looking around for a while now. A few things I gathered.
: Sony supports custom roms and supplies everything needed for a rom.
: fxp.co makes roms but they have been inactive since October, does this mean their latest rom is stable?
: Sony have released some camera stuff yesterday but nobody has come forward and said they will take it and build with it.
Everything seems dead and as if no one wants to build further. I don't know how to build otherwise I would of done it my self by now and shared it.
Is this device dead? Is there someone who knows what they are doing going to release a build? I'm still on stock waiting for my first AOSP build to flash.
Coming from a motorola (Moto G 2014) that has a million roms build a day. This is weird for me to not have a rom to flash and use as a DD.
I'm coming off as a snotty kid here I know. I just want to flash some AOSP's... So thats the question... Are there any AOSP's that can be flashed and used as DD?
Thanks for at least trying to read this... Pece
Yeah it is a little dead around here unfortunately hahaha. I've tried all the CM/AOSP ROMs and from my experience almost all of them are good as daily drivers with no issues with the exception of the Marshmallow one currently being worked on.
tomascus said:
Yeah it is a little dead around here unfortunately hahaha. I've tried all the CM/AOSP ROMs and from my experience almost all of them are good as daily drivers with no issues with the exception of the Marshmallow one currently being worked on.
Click to expand...
Click to collapse
So whick ROM do you suggest then?
On FXP they have this one : AOSP_L_MR1_151203_honami... I guess that is the latest one with the camera thingy that was published. 151203 means 3rd of Dec 2015. Right???
I guess I should just download and flash and answer my own questions
Thanks
ljoao77 said:
So whick ROM do you suggest then?
On FXP they have this one : AOSP_L_MR1_151203_honami... I guess that is the latest one with the camera thingy that was published. 151203 means 3rd of Dec 2015. Right???
I guess I should just download and flash and answer my own questions
Thanks
Click to expand...
Click to collapse
Yea it does.
Up to you man, I personally just grab CM12.1 off the nightlies website http://www.cmxlog.com/12.1/honami/ and maybe also flash M5 kernel on there, which you can find in the development section.
I just want to say... I've been at it for about 4hours now... This is harder than I expected. I finally have a AOSP rom. FXP latest build... Finally have TWRP recovery... About to flash open g apps stock package... I hope it all goes well... This is way harder than the hundreds of other android phones I've done this with.
Edit : It seems that cyanogenmod is the only stable ROM I could get past setup with. After I installed Gapps. I installed Aroma Gapps and selected the apps I use. The Gapps run perfectly and Google camera seems to be pretty good and taking full 20mp shots. I'm impressed with CM12.1. It runs good. After doing an antutu benchmark to see if the performance is close to stock I see that it ,"Benched", Way more that stock. 43288 is my score on Antutu. I know bechmarks tell half a story but it seems to tell an interesting one... It seems CM12.1 is really great and with the Gapps I'm getting my ,"stock android", feels anyhow.
This was the toughest device for me to get a working custom ROM with. There should be a new thread detailing how, late 2015. To get a custom ROM working.
AOSP with FXP in no good for actual use. CM12.1 is really good.
I answered my own questions I wanted details too. I'll be using this CM12.1 Xperia Z1 as my DD and see if it works.
ljoao77 said:
I ask this because we are now in December. I have recently fired up an old Z1 and want to breathe new life into it. So I have been looking around for a while now. A few things I gathered.
: Sony supports custom roms and supplies everything needed for a rom.
: fxp.co makes roms but they have been inactive since October, does this mean their latest rom is stable?
: Sony have released some camera stuff yesterday but nobody has come forward and said they will take it and build with it.
Everything seems dead and as if no one wants to build further. I don't know how to build otherwise I would of done it my self by now and shared it.
Is this device dead? Is there someone who knows what they are doing going to release a build? I'm still on stock waiting for my first AOSP build to flash.
Coming from a motorola (Moto G 2014) that has a million roms build a day. This is weird for me to not have a rom to flash and use as a DD.
I'm coming off as a snotty kid here I know. I just want to flash some AOSP's... So thats the question... Are there any AOSP's that can be flashed and used as DD?
Thanks for at least trying to read this... Pece
Click to expand...
Click to collapse
The first thing to do to stop projecting the image of a snotty kid is to read original development thread. You may surprise yourself finding plenty of custom roms including CM, Paranoid, Slimrom, DU and others. You can find kitkat and both versions of lollipop and every time custom roms were several months ahead of stock.
So, don't be shy and read.
optimumpro said:
The first thing to do to stop projecting the image of a snotty kid
Click to expand...
Click to collapse
I think this is a little harsh, flashing a new device can be quite overwhelming, especially if the forums are as inactive as they are here in the Z1 section.
But OP, there is a super long thread pinned about flashing and rooting for newcomers, you should check that out.
http://forum.xda-developers.com/showthread.php?t=2440565
D33KK said:
I think this is a little harsh, flashing a new device can be quite overwhelming, especially if the forums are as inactive as they are here in the Z1 section.
But OP, there is a super long thread pinned about flashing and rooting for newcomers, you should check that out.
http://forum.xda-developers.com/showthread.php?t=2440565
Click to expand...
Click to collapse
Little harsh? I don't think so. I don't appreciate it when freeloaders complain, especially when they don't know what they are talking about. The guy wasn't asking questions on how to flash, he basically came in and proclaimed that there are no custom roms for Z1, everything is dead and he is waiting for the first custom rom to flash. He clearly didn't bother to read and discover a multitude of custom roms for Z1. And by making that ridiculous statement, he has insulted everybody who contributes to Z1 development..
And by the way, what does "dead" mean? Inability to have updates twice a day? Lollipop has just recently became stable and marshmallows won't get there for at least a year. Plus, I am not sure that M is worth the effort: not much changed as compared to LP.
optimumpro said:
And by the way, what does "dead" mean? Inability to have updates twice a day? Lollipop has just recently became stable and marshmallows won't get there for at least a year. Plus, I am not sure that M is worth the effort: not much changed as compared to LP.
Click to expand...
Click to collapse
Yeah I agree with you, Lolipop is really good on the Z1, even if we do eventually get M I'm not sure it'll be worth the upgrade.
optimumpro said:
Little harsh? I don't think so. I don't appreciate it when freeloaders complain, especially when they don't know what they are talking about. The guy wasn't asking questions on how to flash, he basically came in and proclaimed that there are no custom roms for Z1, everything is dead and he is waiting for the first custom rom to flash. He clearly didn't bother to read and discover a multitude of custom roms for Z1. And by making that ridiculous statement, he has insulted everybody who contributes to Z1 development..
And by the way, what does "dead" mean? Inability to have updates twice a day? Lollipop has just recently became stable and marshmallows won't get there for at least a year. Plus, I am not sure that M is worth the effort: not much changed as compared to LP.
Click to expand...
Click to collapse
You miss understand. Let me explain. I went through all the custom roms threads. And I read the comments. The comments all speak of incomplete roms that have a major flaws in it. Camera not working is the main problem. I also did search the forum to figure out how to flash the Sony. The forum helped but it was scattered everywhere. Some solutions were not even in the Z1 page but in another Sony Xperia page. (The drivers not being accepted by newer windows) This thread : http://forum.xda-developers.com/showthread.php?t=2440565 would definitely come in handy, I must of over looked it.
I am sorry if you think I'm clueless to this. But I have had about 5 phones that I've flashed custom roms on. Motorola, HTC and samsung. All those phones were easy. The Sony is very complicated because I couldn't get into the recovery, after following instructions from Sony and on this forum. Using EMMA to flash the recovery, Pressing the right buttons. I could not get it to work... But with fastboot I kept trying and somehow got it to flash TWRP recovery. Allowing me to install CM12.1
Flashing the FXP AOSP roms was easy. But that rom didn't work. Neither did the Recovery that came with it.
I Just wanted to know how to get this AOSP that Sony bragged about. But in essence it doesn't exist. Not in a functional form for users.
And I think that was my biggest problem. Understanding that the AOSP thing is not for me. Or others that want it as a DD.
*Edit After reading the replies and felt the need to refreshen my story. I understand there are lots of Custom ROMS. The whole idea here was that I was looking for AOSP that all the articles talk about. Sony releasing AOSP build for their phones. But it isn't exactly the full story. I was just looking for these Sony AOSP Roms... But I did end up with CM12.1... I was thinking about trying this Jaguar one that is so active as well. I'm not trying to rip on the custom roms the community was working on. I was justy trying to find Sony's AOSP. I'm sure the Custom roms are great. And I will eventually find the perfect one for me.
hey guys just bought this m7 device now i need your help to choce the right rom for me. im looking for performences over futers, stock on the lates android ( 6 i think )
What model are you running, AT&T, Sprint, Verizon or T-Mobile?
fireball0093 said:
What model are you running, AT&T, Sprint, Verizon or T-Mobile?
Click to expand...
Click to collapse
european
Burllz said:
european
Click to expand...
Click to collapse
Ok, so the international model. So if you want stock Android 6.x, my personal recommendations are Android Ice Cold Project (AICP), it's very feature rich while being as close to stock as possible and it has nightly updates. It also has really great performance and battery life, I haven't had any lag and get at least a day out of my battery. There's also Cyanogenmod 13 although it hasn't been updated for a month or so to my knowledge. And lastly another good one is crDroid. I personally recommend AICP because of the almost daily updates, and features, I have it installed on both my M7 and Nexus 4. I haven't had any issues and if there is an issue it's normally fixed the following update.
fireball0093 said:
Ok, so the international model. So if you want stock Android 6.x, my personal recommendations are Android Ice Cold Project (AICP), it's very feature rich while being as close to stock as possible and it has nightly updates. It also has really great performance and battery life, I haven't had any lag and get at least a day out of my battery. There's also Cyanogenmod 13 although it hasn't been updated for a month or so to my knowledge. And lastly another good one is crDroid. I personally recommend AICP because of the almost daily updates, and features, I have it installed on both my M7 and Nexus 4. I haven't had any issues and if there is an issue it's normally fixed the following update.
Click to expand...
Click to collapse
ok thanks. what about android 5 ? are these google play editions any better then other custum roms?
Burllz said:
ok thanks. what about android 5 ? are these google play editions any better then other custum roms?
Click to expand...
Click to collapse
Android Lollipop with the Google Play Editions are pretty much what you'd get on the stock Nexus experience. A lot of Google apps, and pure stock Lollipop without any modifications. Some do have some modifications to them, and some don't.
fireball0093 said:
Android Lollipop with the Google Play Editions are pretty much what you'd get on the stock Nexus experience. A lot of Google apps, and pure stock Lollipop without any modifications. Some do have some modifications to them, and some don't.
Click to expand...
Click to collapse
seems like marshmewllow is too bugy so ill try the lollipop roms, any sugestions?
Burllz said:
seems like marshmewllow is too bugy so ill try the lollipop roms, any sugestions?
Click to expand...
Click to collapse
Cyanogenmod 12.1 is really the only Lollipop ROM that I have used other than the Sense 7 roms, they have almost nightly updates for their Lollipop builds. Google Play Edition+ is another great one for 5.x, you can pick between stock Play Edition and the developer's custom build packed with features.
fireball0093 said:
Cyanogenmod 12.1 is really the only Lollipop ROM that I have used other than the Sense 7 roms, they have almost nightly updates for their Lollipop builds. Google Play Edition+ is another great one for 5.x, you can pick between stock Play Edition and the developer's custom build packed with features.
Click to expand...
Click to collapse
okay, i found a rom that suits my needs. now i want to dual boot some kitkat rom and karbon as main rom with multy rom. the problem is that multry rom gives me this error "kernel doesnt have kexec-hardboot patch". seems like i need diferent kenal but i cant find any costum kernel for 5.1.1 ? or can i patch the kernal ?
Burllz said:
okay, i found a rom that suits my needs. now i want to dual boot some kitkat rom and karbon as main rom with multy rom. the problem is that multry rom gives me this error "kernel doesnt have kexec-hardboot patch". seems like i need diferent kenal but i cant find any costum kernel for 5.1.1 ? or can i patch the kernal ?
Click to expand...
Click to collapse
If your primary rom is Sense-based then simply download this kernel, ElementalX, and flash it to your main rom. It has some pretty good features too that you can pick from during the installation. There also is a GPE build for Play Edition roms as well. Reboot into the rom just to make sure everything flashed smoothly, and then reboot and you can then boot into your different roms in multi boot. Just make sure that if you change your main rom in Multiboot that it has to have this kernel, I haven't found any other one that supports it. There also aren't any Marshmallow kernels just yet either, sadly.
fireball0093 said:
If your primary rom is Sense-based then simply download this kernel, ElementalX, and flash it to your main rom. It has some pretty good features too that you can pick from during the installation. There also is a GPE build for Play Edition roms as well. Reboot into the rom just to make sure everything flashed smoothly, and then reboot and you can then boot into your different roms in multi boot. Just make sure that if you change your main rom in Multiboot that it has to have this kernel, I haven't found any other one that supports it. There also aren't any Marshmallow kernels just yet either, sadly.
Click to expand...
Click to collapse
its cm based, i dont think this kernel will work
http://forum.xda-developers.com/htc-one/development/rom-t3066364
Burllz said:
its cm based, i dont think this kernel will work
http://forum.xda-developers.com/htc-one/development/rom-t3066364
Click to expand...
Click to collapse
Hmm. I'm currently busy until around 10-11pm EST, whenever I get done and back home I will take a look around to see if there might be anything. If it's Marshmallow based though there isn't any custom kernels yet. Wouldn't hurt to make like a GPE or Sense rom your primary one and simply leave it there, I do that. I use MIUI 7 as my daily driver but I have InsertCoin Sense 7 installed for my main rom so I can have 2-3 other roms installed. Just some advice if that helps
fireball0093 said:
Hmm. I'm currently busy until around 10-11pm EST, whenever I get done and back home I will take a look around to see if there might be anything. If it's Marshmallow based though there isn't any custom kernels yet. Wouldn't hurt to make like a GPE or Sense rom your primary one and simply leave it there, I do that. I use MIUI 7 as my daily driver but I have InsertCoin Sense 7 installed for my main rom so I can have 2-3 other roms installed. Just some advice if that helps
Click to expand...
Click to collapse
okay, im on carbon rom , cm based, 5.1.1 . thanks mate!
Burllz said:
okay, im on carbon rom , cm based, 5.1.1 . thanks mate!
Click to expand...
Click to collapse
I think, what would work best for you since you prefer stock-based roms, is download the Google Play Edition+ I linked earlier in the thread, install it as a secondary rom and also flash the ElementalX kernel under Flash Zip. Afterwards go under Advanced, Multirom, Swap Rom, and leave it as Swap primary and pick the GPE+ and let it run it's course. Might take 5-10 minutes so I'd leave it plugged in and charging if you are below 50-60% battery. Then just boot into GPE+, do a quick setup and leave it as a basic installation. That way you can keep your Carbon Rom installation with all of the data and apps, and just pick that every time you boot your phone. Plus it's easier than messing around with different kernels on Carbon trying to find one to make it work and you have a fallback stock rom in case an update or something messes up Carbon. That's exactly what I did with MIUI and InsertCoin.
fireball0093 said:
I think, what would work best for you since you prefer stock-based roms, is download the Google Play Edition+ I linked earlier in the thread, install it as a secondary rom and also flash the ElementalX kernel under Flash Zip. Afterwards go under Advanced, Multirom, Swap Rom, and leave it as Swap primary and pick the GPE+ and let it run it's course. Might take 5-10 minutes so I'd leave it plugged in and charging if you are below 50-60% battery. Then just boot into GPE+, do a quick setup and leave it as a basic installation. That way you can keep your Carbon Rom installation with all of the data and apps, and just pick that every time you boot your phone. Plus it's easier than messing around with different kernels on Carbon trying to find one to make it work and you have a fallback stock rom in case an update or something messes up Carbon. That's exactly what I did with MIUI and InsertCoin.
Click to expand...
Click to collapse
okay thats what im going to do. i have one last question - is it normal for the cpu to run at 35-40C at all times when i use the phone? also the back cover is always warm sometimes gets hot without any havy tasks?
Burllz said:
okay thats what im going to do. i have one last question - is it normal for the cpu to run at 35-40C at all times when i use the phone? also the back cover is always warm sometimes gets hot without any havy tasks?
Click to expand...
Click to collapse
Yeah, that happens sometimes with mine. Not all the time though, mainly when I'm streaming music in Spotify or Pandora, or if I've been on it for 10-15 minutes on Twitter, email, etc. Sometimes when installing a rom and first booting it, it gets upwards of 50C but cools down after I let it sit for a little while. Also, just throwing it out there because I love the app, if you have $7 you're willing to spend MyBackup Pro is fantastic for backing up everything if you change the rom you use the most. Like data, apps with the app data (not every app backs up the data though) and just like everything else. There's also a free one if you don't care about app data which I'd actually recommend trying that out first. Spares a hell of a lot of time for downloading apps every time. I promise I am no way affiliated with them, like I really feel bad "advertising" them even though I'm not. It's just my favorite backup app xD. Titanium backup is another good one but I haven't used it's backup stuff. Mods you can feel free to edit this if you don't see it fit.
Hi,
I got the 1+3 since 3 days, and I must say that from the ROM point of view I quite happy with it ;
It is ...
1. Stable
2. Quick
3. Battery friendly
4. Enough customisation
5. Not Bloatware
Of course there is room for improvement in each points, I know, but ....
Usually I root for point 4. & 5. and I put Custom ROM for point 1. 2. & 3.
But this time, I´m not so hurry
Same here. I have rooted to solve memory management issue but dont really fancy putting a CM rom on it. Will wait until there is a stable oxygen rom I think
I will wait also. Hopefully more CM13 mods will come and improve performance in general.
I got it since 2 days and was very surprised on easy unlocking bootloader and rooting. ROM seems stable and quick enough. I assume that I will wait for an Android N port before I change to a custom ROM. Has someone an idea if there are already devs on the way to cook N-ROMs for different devices?
Same here, only rooted it for the memory fix, OOS have everything I want
I will for sure flash RR and Bliss Flashing Roms is why i bought this device.
andywright1982 said:
Same here. I have rooted to solve memory management issue but dont really fancy putting a CM rom on it. Will wait until there is a stable oxygen rom I think
Click to expand...
Click to collapse
I haven't even rooted - but I am quite happy with Oxygen 3, feel no great urge to customise or get CM etc installed. I really like it.
Does Android Pay still work on your device??
Thought I was the only one.
No intention of rooting at the moment.
Have a few apps for work that need a stock phone, plus banking apps etc.
But yep OOS3 seems to have everything with nova launcher.
Sent from my ONEPLUS A3003 using Tapatalk
Same here, OxygenOS is awesome so far, but I rooted for Xposed.
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Valid points for staying on OOS, it's a good rom that has most all customizations I need and the rest I can get with xposed...
Thing is do you EVER plan on flashing a rom? My answer is of course so I decided to go ahead and decrypt (format data) now as opposed to later after I have all my music, etc loaded on.
Running Grarak's CM13 swimmingly.
brickedvice said:
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Click to expand...
Click to collapse
Well in my case, I've been flashing rom's for 8 years. This is the first device I've not felt the need out of the box.
brickedvice said:
Those that have been flashing roms for 3+ years pretty much get tired of doing it and want all stock. New people get excited about flashing new roms and do it for 3+ years until they end up getting tired too
Click to expand...
Click to collapse
+1 here. I've been rooting phones for 5+ years as soon as I got them. But now, I'm wondering if I even need to bother.
Yeah, this is hard one. Thanks devs for quickly coming up with root, unlock, custom, and tweaks. Not sure if rooting is needed. I think we can all agree, if you want more out of the devices, you quickly root. For some reason, that's not necessary for one+3. I'm pretty sure we will get bored and devs will come out with super awesome Roms in the near future with many added tweaks. But this phone is solid. Might need a month's of stock rom usage and more arising issues before I will jump to rooting. Great device no complaints..
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Yes also for me. Great Rom and the first time that I don't want to change the rom!
Gesendet von meinem SGP511 mit Tapatalk
I agree, I actually like this stock, I got pretty much everything I need, iI will just miss flashing nightlies but I won't miss all the down time and missed text messages
Been flashing ROMs for 6 years now, always running cm, and I have been seriously considering given oos a few days before flashing, but also I'm to used to cm
I'm waiting for Multiboot/Dualboot patch...keeping Stock-Rom on first "partition" and Custom-ROM on second...
My phone went mad and downloaded 6.80gb stuff from online wasting my this month data package so i decided to update newest Chroma (about year old) to 7.1.1 stock rom + TWRP recovery + Franco kernel. As usually that felt like downgrade.
- Battery not shown as percentage
- Camera sound
- No dark/black theme
Many other issues cames too even i have used phone like 30min so i thought no point change settings more than that. I dont understand how hard can it be google to even try. I first time used android when it was something like 2.2.2 and still wondering same issues what i did then. I went from iPhone 2g to android and still miss what apple had by then and what android does not have even now but no can do.
I am not heavy user of my phone. I just want basic things to work. Is there some custom rom which is like chroma. I liked how chroma was like allmost stock rom but with couple of custom settings but its no longer continued so is there any rom which have taken it spot?
Wow, you went from a custom ROM to stock and you are missing features? Who would've guessed that?!?!
Sorry for the sarcasm lol. Flash literally any custom ROM and you should have those features. Most, if not all, N ROMs have Substratum/OMS which will allow for dark themes. Battery percentage should also be included in every ROM. Camera sound should be in most ROMs. As for me I'm still on Resurrection Remix M + xposed framework, which in my opinion has the most customization out of any possible Nexus 6 setup in the world.
I would suggest Pure Nexus to you which in my opinion is the closest to Chroma. But make a Nandroid backup and flash a few until you see what you like. Also checkout this YouTube channel which is amazing. @glockman4519 does awesome ROM overview videos if you want to get a feeler for something before flashing it.
HTC Tytn user 188 said:
- Camera sound
Click to expand...
Click to collapse
Do you refer to the camera shutter sound? If yes, you can't remove the sound on latest stock camera app...
I go with pure Nexus. Thanks for tip. I dont understand most of custom roms which are allways full of bugs. I never understanded either why there is need for over 10 diffrent rom for one device. Developers should work together and there would be only couple of very good roms to choose from but i know its hard people to work together so aint gonna happen
Running Pure Nexus on my wife's Shamu and on my angler. You shouldn't be disappointed. Just as you, i like simple cosmetic tweaks, dark themes, and it does the job. :good:
Resurrection Remix, @Neo style is my current dd. Every customization you could ever want is in there, but there are many great ROMs. PN is one that if you came from Chroma, you'll like. Nitrogen is good, et al. Just read the threads and give them a shot
HTC Tytn user 188 said:
My phone went mad and downloaded 6.80gb stuff from online wasting my this month data package so i decided to update newest Chroma (about year old) to 7.1.1 stock rom + TWRP recovery + Franco kernel. As usually that felt like downgrade.
- Battery not shown as percentage
- Camera sound
- No dark/black theme
Many other issues cames too even i have used phone like 30min so i thought no point change settings more than that. I dont understand how hard can it be google to even try. I first time used android when it was something like 2.2.2 and still wondering same issues what i did then. I went from iPhone 2g to android and still miss what apple had by then and what android does not have even now but no can do.
I am not heavy user of my phone. I just want basic things to work. Is there some custom rom which is like chroma. I liked how chroma was like allmost stock rom but with couple of custom settings but its no longer continued so is there any rom which have taken it spot?
Click to expand...
Click to collapse
Sounds to me that you are going to like Pure Nexus since it has that Stock look and feel you want but with some extra and PN has extras.
The nice thing is you can pick and choose what features you want to run so you are in controle.
The rom does not come rooted because @BeansTown106 has decided that too many users are looking to pass the Safety Net Check for apps like Google Pay and some others that require your device be unaltered from stock. But if you want to run Substratum, you can either flash Chainfire's SuperSu sr3 v2.79 (or any systems suoerSu) or even flash Magisk Systems Root (I think it is up to v10 now) and that will allow for theming with Substratum.
That should get you pretty close, of not better than you g had with Chroma. PN is one of the most stable N roms out for the Nexus devices that I know. Another great rom would be SiX rom... But that is a whole nother story : )
I´ve been using Pure Nexus two days now. It seems usable but i dont know is it the 7.1.1 or the franco kernel or something like that but im having performance issues. Even clash of clans in own city does not work smoothly. Also camera shutter sound cannot be disabled. Otherwise i think all works as supposed to. When i installed rom i did clean install. I formated whole device including internal memory. Then i installed Pure nexus 7.1.1 + Full dynamic gapps + Franco newest kernel + Supersu
Anyone know whats the best kernel or do i just have to wait for updates on both rom and kernel?
EDIT: i will be now on pure nexus thread. Thanks for help.
@HTC Tytn user 188
The camera shutter sound can't be disabled with stock camera on 7.x Roms.
For performance issues, maybe try asking in The Rom/Kernel thread.
A combination you should test:
Crdroid rom, elementalx kernel, crystal tronik dark 12 substratum theme and latest beta nova launcher
gives me a lot of customizations, dark+blue look and good battery/performance
Works solid for me !