Database Info

Why should I install a custom ROM over offical version?

What are the advantages? I have official 4.0.3, and I don't usually use any of the stuff that requires rooting. I didn't even root my Nexus S yet lol.
Why custom ROM? Which one? And what features do I get?

It makes my pr0n load faster.
Sent from my Nexus S 4G using xda premium

Costum Roms allow you to tweaks almost everything, like overclocking, over/under volting, set governators, I/O scheduler and so on, u get better performance and sometimes (depending on Rom+kernel combo) better battery life. Eerything goes cool & smoother. Just see an review about custom roms (cm9, bixie, alfonso, kang, etc) on youtube to get an idea.
If this info helped you somehow hit thanks button please.
cheers

Custom ROMs make the s3x much better with multiple orgazm.. lol..
Really, it's a sin owning a Nexus S and not rooting/installing custom ROMs. Custom ROMs offer many more features, stability, performance than stock ROM, otherwise the devs won't spend countless hours for just building another stock ROM. Once you flash/use a custom ROM, you will not go back to stock, and that's a sure thing.
Here's just a few things custom ROMs and rooting offer
* Speed
* Stability
* Endless custom mods/features
* Firewall
* Adblock
* Eyecandy themes (if the custom ROM supports themes)
* CPU overclocking/underclocking
* Privacy Guard -- prevent apps from getting unnecessary private permissions such as getting your phone number, IMEI, etc...
I know some people relate the term "jailbreaking" with "rooting", and they're afraid to root because it has a bad vibe to it. "Rooting" != "Jailbreaking". If you come from a Linux background, then you have no problem understanding what "rooting" means. If you're a Windows user, think of "rooting" as granting the "Administrator" access (not to be confused with the Android's Administrator which you can grant some apps without rooting). What can you do with Windows Administrator access/rights? Similar things can be done on the Android device if you have root access.

TheJavaJunkie said:
What are the advantages? I have official 4.0.3, and I don't usually use any of the stuff that requires rooting. I didn't even root my Nexus S yet lol.
Why custom ROM? Which one? And what features do I get?
Click to expand...
Click to collapse
Do u ever think music can be better?
Gps faster cold fix?
Gaming low temp. ?
Batt.lasting longer?
Camera quick shot, nice shot?
Function fast accessing , ex. to turn on wifi hotspot, just hit one button and touch.......
Jump between rom to rom within 5 mins.... (like Pc hardisk gosh)
.
.
.
.
Which one is better ? No one can say extracly..... We can only count some good (in hundreds of other good) as CM rom, Criskelo rom, Exynos extreme rom, Miui rom ....for Ginger, and for Ics that is too early to talk.
Sent from my GT-I9100 using Tapatalk

Besides all the features mentioned above, a custom Rom depends on each of the features you need.
One I like (as in MIUI's ROM) is CyberGR v7 the ability to skip tracks with the sound volume when phone is locked.
Also, some non-important, ability to kill activity by holding the back button, 4-way Reboot, some might have the FB sync problem fixed, etc.

TheJavaJunkie said:
What are the advantages? I have official 4.0.3, and I don't usually use any of the stuff that requires rooting. I didn't even root my Nexus S yet lol.
Why custom ROM? Which one? And what features do I get?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If looking at all those settings options get you excited then you definitely should flash a custom ROM (AOKP in this case). If you look at those settings as a chore to have to mess with then you should just stay happy with stock.

Unicorn?
Sent from my Nexus S 4G using xda premium

RushAOZ said:
Unicorn?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes, if you're lucky your custom ROM may even include bad ass rainbow unicorns

Well thanks guys!
Those pics really had me like AWESOME!
Gonna go search Google and xda now to root my Nexus and install a ROM,will decide which one later

TheJavaJunkie said:
Well thanks guys!
Those pics really had me like AWESOME!
Gonna go search Google and xda now to root my Nexus and install a ROM,will decide which one later
Click to expand...
Click to collapse
You can find here on XDA general how to root it and how to flash custom roms and kernels, so you dont need to google it. Btw there is a good and easy step-by-step guide here: http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/ . It takes 15 or less minutes to root your SGS and install a new ROM.
Good luck

I had a Milestone awhile back and it got the last official update OTA and it really slowed down the device. Luckily there were some good rome out there, even gingerbread ones that really increased the speed of the device as well as the battery life.

Honestly stock ICS is great as is.
Sent from my Nexus S using Tapatalk

vetvito said:
Honestly stock ICS is great as is.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
definitively better than stock GB (which i never liked), but I'm using CM9 now after some weeks with stock ICS and I won't go back
honestly using a custom ROM is somenthing you want to try, you can always go back to stock if you want

tweak
vetvito said:
Honestly stock ICS is great as is.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
my thought just like you before i try any custom rom. Tweaks stock rom much better than stock rom

I agree. Once a ROM is past beta/alpha tests, you will most likely get a better experience than stock (even though a ROM is a constant work in progress).

Kexec, and a Proof-of-Concept Source-Built Kernel (Bootloader Workaround)

Team Epic announces a proof-of-concept source-built kernel for the Verizon SGS3, complete with kexec hardboot support. This kernel serves two purposes:
1. To be included in custom recovery images, as it proves the capability of booting-via-kexec custom kernels from recovery.
2. To serve as a proof-of-concept boot kernel, to demonstrate that custom kernels are capable of running on the Verizon SGS3 in its present form.
Please see our blog post, Kexec, and a Proof-of-Concept Source-Built Kernel for the Verizon SGS3, for full details and source links.
CyanogenMod's Team Epic specializes in Sprint's flagship Android phones on Sprint.
If you appreciate our work, please consider supporting us with a tiny contribution. Thanks!

Awesome! Thank you so much for your guys efforts
Sent from my HTC Rezound via Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MyColorScreen

Good luck guys.
☞ sent from my GS3

Just to confirm, the kexec hardboot approach used here is a bit different from the typical kexec. The main difference is that we actually perform a hardware reboot, reinvoking the bootloader just prior to booting the kexec'd kernel.
The advantage to this approach is that it maintains a high-degree of compatibility and minimizes buggy behavior. The disadvantage is that it requires that the bootloader is capable of booting custom recoveries, which the present Verizon SGS3 bootloader is capable of doing.
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
If it eventually arises that booting from a stock kernel/recovery is necessary, then it's likely a bunch of kernel bugs will have to be fixed, and it might still have compatibility issues observed in previous kexec attempts. It's linked in the blog post, but there's a bit more of a technical description of the hardboot approach in this old thread.
Thanks to invisiblek and captjtkirk for testing.

you guys are awesome xda has the best devs ever! I worship you guys!

Wow! Thanks for taking the time to do this even though you guys aren't vzw owners. Great example of how great this community is.
Sent from my DROIDX using xda app-developers app

Unbelievable...you guys are awesome.
Jelly Bean here we come!

mkasick said:
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
Click to expand...
Click to collapse
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!

jh120 said:
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!
Click to expand...
Click to collapse
nope. you have to accept the OTA

Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app

Neverendingxsin said:
nope. you have to accept the OTA
Click to expand...
Click to collapse
Depends. My rezound didn't ask. I would wake up with my phone in recovery. It would fail to install the update because the stock recovery wasn't there but it never gave me a choice to install or refuse
Sent from my ADR6425LVW using Tapatalk 2

Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
And THANKS! You are just missing the raised finger picture to Verizon over this.

densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.

skennelly said:
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
Click to expand...
Click to collapse
According to Noobnl in the IRC channel, the dual core thing isnt an issue since its a hard reboot so it reloads the bootloader; "this is a more advanced form kexec."

Glad to see some love from familiar faces. This is one if those times when i nuts being on sprint. From the galaxy tab, to the og epic, to the touch, sprint has allowed great things to happen on their devices. Now in big red, it's great to see we can use/reuse stuff across networks.
Big thanks!
Sent from my DROID RAZR using Xparent ICS Tapatalk 2

ceo.mtcl said:
Good luck guys.
☞ sent from my GS3
Click to expand...
Click to collapse
+1

densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores.
Click to expand...
Click to collapse
In short, yes.
Longer answer:
Traditionally kexec works by having one instance of the kernel boot a second instance directly, that is, by avoiding the bootloader. For this to work, every kernel driver has to shutdown in such a way that the same driver (in the kexec'd kernel) can revive and restart the hardware it controls.
The problem is that some, maybe many, drivers aren't actually capable of doing that. For the most part, it's a feature only needed by kexec, so unless the device manufactuer is specifically targetting kexec support, usually one or more drivers will put some part of the hardware in a confused state. That's the main source of compatibility bugs with kexec.
Now, what we do in the kexec hardboot approach is use the Linux kexec infrastructure to load and stage a new kernel in memory. Then we perform a hardware-level reboot, reinvoke the bootloader, and then at the very beginning of the recovery kernel code, we check to see if there's a kexec'd kernel out there in memory and if so, jump to that instead.
The advantage with this technique is that once the kexec'd kernel is booted, the environment is the exact same as if it was a kernel flashed to the device--there shouldn't be any hardware compatibility issues.
As it turns out, the one compatibility thing we have seen, which is unusual reboot behavior, isn't actually an artifact of kexec. The same thing would happen if you flashed a "boot kernel" to the recovery partition and booted it directly.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
ErylFlynn said:
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
Click to expand...
Click to collapse
This is a temporary mechanism. To return back to the stock kernel, simply reboot the device.
To remove the custom recovery and fully flash back to stock, yes, you would use Odin.

Great work guys. You guys are awesome.

Amazing news!

So when you say you just reboot to get back to the stock kernel, is it a certain way of rebooting?
As in, if you were running soap and a kexec aosp kernel and rebooted and it forced you to the stock Samsung kernel, the phone wouldn't boot right?
Sent from my ADR6425LVW using xda app-developers app

[Q] Does BlackJelly Rom work on Verizon S3?

http://forum.xda-developers.com/showthread.php?t=1883845
does this rom work with the verizon s3? I could not find it in Verizon thread. The ROM looks great so far.

No. Do not flash ROMs from other carriers on your phone. It WILL result in a brick.
Covered many times...please search next time.
Sent from my SCH-I535 using Tapatalk 2

It actually wouldnt brick your device as the rom doesnt flash any radios. It might not boot, but it wouldnt brick it. The ATT version of the rom (which is based off the tmo leak) works unmodified (kernel and all) with the tmo version. I have a version in both the ATT and TMO forums and the rom is exactly the same except for the model number in the build.prop. However, I'm not sure it will work on the CDMA variant.

tomalrocks said:
http://forum.xda-developers.com/showthread.php?t=1883845
does this rom work with the verizon s3? I could not find it in Verizon thread. The ROM looks great so far.
Click to expand...
Click to collapse
Like what graffixnyc said, the only differences are in the build.prop. Just add the CDMA specific values to the build.prop in BlackJelly (be sure to remove the GSM stuff). Also, take the apns-conf.xml from one of our ROMs like Synergy or CleanROM and replace the one in BlackJelly. That should get you booting.
Marcismo55 said:
No. Do not flash ROMs from other carriers on your phone. It WILL result in a brick.
Covered many times...please search next time.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I'd say just stay away from the ROMs in the i9300 forums. But even those wouldn't give you a hard brick. I know...I've purposely tried to do it by installing Omega and Foxhound.

Thank you for clarifying guys.
Sent from my SPH-L710 using Tapatalk 2

graffixnyc said:
It actually wouldnt brick your device as the rom doesnt flash any radios. It might not boot, but it wouldnt brick it. The ATT version of the rom (which is based off the tmo leak) works unmodified (kernel and all) with the tmo version. I have a version in both the ATT and TMO forums and the rom is exactly the same except for the model number in the build.prop. However, I'm not sure it will work on the CDMA variant.
Click to expand...
Click to collapse
Even so I'd be really careful saying that. Someone may read that and think it's fine to flash stuff from other threads while in fact it is really dangerous. The OP only has a few posts so this may apply to him too (no offense, there are some people who read on here all the time and just don't bother with an account until they need to, I'm just sayin)

Hey guys,
I just ported over the BlackJelly ROM the OP requested and will be posting it here for people to use. Since I am pretty much caught up in other projects, both IRL and on XDA (AOSP), this ROM won't be receiving much support as I'd like to give it so I welcome anyone to take the port and make it better. And please, no smartass comments like this:
tml478 said:
Don't let the haters win. If other people want to complain because you released a better product then them then so be it. Android is open source for a reason and you made something that's amazing and I for one really appreciate it. Maybe the haters should get back in the kitchen and try to release something that even comes close to this. Keep up the good work and thanks a lot.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
"If other people want to complain because you released a better product then them then so be it." Like... seriously? Read the #1 rule of XDA:
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
Click to expand...
Click to collapse
FORUM RULES
________________________________________________
HOWEVER, if you do want me to support it fully by abandoning other XDA projects and provide updates on the original developer's behalf, let me know. Of course, I will only provide full support if graffixnyc is okay with me doing it.
The build WILL most likely have bugs, some major, some minor, but that is for everyone to fix. I think this will be a good learning tool as well. Oh and if you already weren't aware, you can use kernels from the other carriers. AFAIK, the kernels are common among all carriers (not including the international kernels) so flash away!
Before we get to the download link, MAJOR props and thanks to graffixnyc for BlackJelly ROM. It's great!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD
BlackJelly VZW​

PureMotive said:
Like what graffixnyc said, the only differences are in the build.prop. Just add the CDMA specific values to the build.prop in BlackJelly (be sure to remove the GSM stuff). Also, take the apns-conf.xml from one of our ROMs like Synergy or CleanROM and replace the one in BlackJelly. That should get you booting.
I'd say just stay away from the ROMs in the i9300 forums. But even those wouldn't give you a hard brick. I know...I've purposely tried to do it by installing Omega and Foxhound.
Click to expand...
Click to collapse
I imagine you changed the update-script in it then. The partition difference would brick you for sure. I know several of the two and a half bagillion people that hard bricked did it with omega specifically. And why would you try to brick these. Unless you have a jtag setup or something i don't see the point

billard412 said:
I imagine you changed the update-script in it then. The partition difference would brick you for sure. I know several of the two and a half bagillion people that hard bricked did it with omega specifically. And why would you try to brick these. Unless you have a jtag setup or something i don't see the point
Click to expand...
Click to collapse
I didn't change them. I may have been lucky or something, but I kept the ROM as is and installed it and didn't end up with a hard brick. Regardless, moral of the story is to stay away from i9300 ROMs unless someone makes a successful port.
I was trying to brick the phone for testing purposes.

[ROM][QUARK][UNOFFICIAL]Android Open Kang Project[6.0.1][Marshmallow]

AOKP 6.0.1 for All Quark Devices (XT1225 | XT1250 | XT1254)​
This is for all the AOKP fans out there that are using the Motorola Quark, which includes: DROID Turbo, Moto MAXX and Moto Turbo. It's very stable and runs pretty smooth for those who tested it. Let's get started...
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR PHONE!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!!​ (Or ask for help, there's a lot of friendly people around here)​
Screen Shots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
Clean Install:
Do a TWRP Backup
Wipe/Factory Reset
Flash ROM.zip
Flash GApps
Flash Anything Else
Clear Cache/Dalvik
Reboot
Download
Past Releases
Note: 6.0.1 Currently not in further development, we've went to Nougat
Open GApps (I used Pico)
Credits
Development:
@baybutcher27
@MSF Jarvis
ROM Testers:
@ChazzMatt
@hobbit19
@kitcostantino
@Moondroid
@Nitefire77
@RL_Wells
@rohheat
Sources
Source Code: AOKP
Device Tree: Motorola Quark
Kernel: CM13 Motorola Kernel

Additional Info
Custom Kernel
BHB27-Kernel can be used on this rom, get it here, you'll probably want to grab his kernel auditor while you're there...
For optimization, you can also install IntelliProfiles 6.0 from @Debuffer, get it here
Developer Options
By default are disabled, to enable, go to: Settings/About and repeatedly tap on the build number to turn them on. You can then turn on Debugging, Advanced Boot options and anything else.

Reserved #2

great news. Congrats for your work man, more roms are always welcome

Woot! Looking forward to flashing a new ROM. Maybe I can get VoLTE working on this.

NepoRood said:
AOKP 6.0.1 for All Quark Devices (XT1225 | XT1250 | XT1254)
...
Click to expand...
Click to collapse
#SomethingForTheSignature
Edit : A couple of issues I see
1) The file is bloated. Like, actually bloated to about 140% of its usual size. My builds have been ~270mB without Gello browser and ~310mB with Gello + Snap, so I guess there's plenty of bloat apps in there or you have huge vendor trees.
2) Why u mediafire? You can keep them on my server or throw them onto the far superior AndroidFileHost (after you get developer status and FTP access, may take a couple of days) using the command I will obviously share with you over Hangouts if you want.

MSF Jarvis said:
#SomethingForTheSignature
Edit : A couple of issues I see
1) The file is bloated. Like, actually bloated to about 140% of its usual size. My builds have been ~270mB without Gello browser and ~310mB with Gello + Snap, so I guess there's plenty of bloat apps in there or you have huge vendor trees.
2) Why u mediafire? You can keep them on my server or throw them onto the far superior AndroidFileHost (after you get developer status and FTP access, may take a couple of days) using the command I will obviously share with you over Hangouts if you want.
Click to expand...
Click to collapse
1) Yes, it's stock from AOKP, and I didn't remove any apps or anything (but may in the future)
2) Because I haven't signed up for AFH yet, but will. I know people were eager for a new quark rom, and while I really appreciate your server, anyone with the link can prowl around and download stuff that I'm not ready to publicly share :good:

NepoRood said:
...
and while I really appreciate your server, anyone with the link can prowl around and download stuff that I'm not ready to publicly share :good:
Click to expand...
Click to collapse
Try accessing roms.technologistguild.com/manage, you'll see what I intend to do to mitigate that

Can baybutchers kernel be used ? What about kernel auditor?
Sent from my DROID Turbo using Tapatalk

PILLMUZIK3600 said:
Can baybutchers kernel be used ? What about kernel auditor?
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
Yes, to both. I've been meaning to add some more info to the OP, but I got distracted. Will get back to work on it now...

If you are coming from RR, you can make a TWRP backup of your data partition, and after 1st install and boot of aokp, and once you are at the home screen, reboot into twrp and flash your data backup. It should boot with all your apps and settings. This method worked for me and Neporood.
I lost LTE signal when I did it on mine, but clearing modem status fixed it for me. I dunno if it will affect anyone else, might have been an app I had installed.
Enjoy!

Do you have volte?

If VOLTE doesn't work on CM13 or RR what makes you think its gonna work on this?

None of the custom ROMs (aside from CF) even have the files needed for VoLTE (IMS and numerous related frameworks and stuff). With that said, I'm in the process of attempting to insert all the necessary files and get VoLTE working.

Nitefire77 said:
If VOLTE doesn't work on CM13 or RR what makes you think its gonna work on this?
Click to expand...
Click to collapse
It was just a question. Someone is going to be the first one to do it.

iiWoodstocK said:
None of the custom ROMs (aside from CF) even have the files needed for VoLTE (IMS and numerous related frameworks and stuff). With that said, I'm in the process of attempting to insert all the necessary files and get VoLTE working.
Click to expand...
Click to collapse
I would consider CF to be modified stock ROM running a stock kernel. CF is a modified Verizon XT1254 debloated stock ROM, is it not?
For instance, all the custom ROMs have to run CM-based kernel, correct? Even AOSP Mokee and the now-discontinued AOSP Nexus Experience -- which are not based on CM -- still use CM kernel. Even BHB27 kernel is based on CM kernel code. Whereas CF is using stock kernel, does it not?

ChazzMatt said:
I would consider CF to be modified stock ROM running a stock kernel. CF is a modified Verizon XT1254 debloated stock ROM, is it not?
For instance, all the custom ROMs have to run CM-based kernel, correct? Even AOSP Mokee and the now-discontinued AOSP Nexus Experience -- which are not based on CM -- still use CM kernel. Even BHB27 kernel is based on CM kernel code. Whereas CF is using stock kernel, does it not?
Click to expand...
Click to collapse
Correct. That's exactly why I excluded CF's ROM. While it is a "custom" ROM in the sense that it's not stock, it's built on stock as an optimized/modified stock ROM. It's the only "custom" ROM to have VoLTE for Verizon, and technically the only ROM to have VoLTE on any Quark, since all the other custom ROMs don't have any IMS files.

Hello... sorry for the trivial question but...
This ROM is based on CyanogenMod or AOSP pure? Thank y

pickmod said:
Hello... sorry for the trivial question but...
This ROM is based on CyanogenMod or AOSP pure? Thank y
Click to expand...
Click to collapse
AOKP is primarily based on Cyanogen

Nitefire77 said:
If you are coming from RR, you can make a TWRP backup of your data partition, and after 1st install and boot of aokp, and once you are at the home screen, reboot into twrp and flash your data backup. It should boot with all your apps and settings. This method worked for me and Neporood.
I lost LTE signal when I did it on mine, but clearing modem status fixed it for me. I dunno if it will affect anyone else, might have been an app I had installed.
Enjoy!
Click to expand...
Click to collapse
Do I have to make a data backup? I usually just download new apps because I usually have issues with using backups.

[ROM][NOUGAT][QUARK][AOKP 7.?]DROID Turbo/Moto MAXX

AOKP (Android Open Kang Project)
7.? Nougat for All Motorola "Quark" Devices (XT1225 | XT1250 | XT1254)
With Substratum/OMS Themes​
KNO'DIS: I, OR ANYONE ELSE AT XDA, WILL NOT BE HELD RESPONSIBLE FOR "BRICKING" YOUR PHONE!! IF YOU MANAGE TO MAKE A BRICK, DUE TO YOUR "FUN-DA-MENTAL" INABILITY TO READ, GO BUILD A BBQ PIT WITH IT!!​ (Or ask for help, there's a lot of friendly people around here)​
This is for the AOKP fans out there that are using the Motorola Quark, which includes: DROID Turbo, Moto MAXX and Turbo Maxx. It's stable, I use it daily, however it's still under development, see post #2 ("Extra Info") for additional information.
Screen Shots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation
Clean Install Recommend:
Use TWRP for a Full Backup
Wipe/Factory Reset
Flash ROM.zip + GApps
Clear Cache/Dalvik
Reboot
Upgrading
Use TWRP to Backup Data Only
Wipe/Factory Reset
Flash ROM.zip + GApps
Clear Cache/Dalvik
Reboot
Setup Phone
Reboot Recovery
Restore Data Backup
Download
Current Release
Open GApps 7.? (I used Pico)
Credits
Development:
@bhb27
ROM Testers:
@eddiemc12
@hpbrasil
@kitcostantino
@Nitefire77
@Shiftydogit
And, I've recently added more (PM me if you want your name here)
Sources
Source Code: AOKP
Device Tree: Motorola Quark
Kernel: BHB27 Stock Kernel

Extra Info
Most "bugs" have been fixed. IF you find one, feel free to share on this thread :good:
PLEASE, PLEASE:
Do a "clean install" before reporting issues, you may also want to clean your modem first using this:
Download Zip
(Flash using TWRP)

Kang 2

Great.
Is it using bhb27 kernel or you modified something in it?

Very nice, thanks @NepoRood

Debuffer said:
Great.
Is it using bhb27 kernel or you modified something in it?
Click to expand...
Click to collapse
Using bhb's stock CM14 kernel, it's running great. I'll be adding more information to the first 3 posts as time goes on :good:

NepoRood said:
Using bhb's stock CM14 kernel, it's running great. I'll be adding more information to the first 3 posts as time goes on :good:
Click to expand...
Click to collapse
But is it using Bhb kernel 1.0?
Or you changed something and it's your 1.0 version?

ROM was running great. Been running it a couple days without hassle

Nitefire77 said:
ROM was running great. Been running it a couple days without hassle
Click to expand...
Click to collapse
same here ,smooth and fast with no reboots.

For those who has problems installing because of com.android.phone has stopped
First fresh install
Reboot
It'll problem
Reboot in recovery
Dirty install the rom again (without any configuration done in the first boot)
Reboot
Worked for me.
@NepoRood can you please add caffeine tile in next update? And maybe zzmoove gov? I know its just the first build, but this additions would be really loved. Thank you for such a good job.

Link to kernel not working. Could you please confirm

janine13 said:
Link to kernel not working. Could you please confirm
Click to expand...
Click to collapse
It's a typo, my bad. You know that is the source code, right?

@Debuffer, personally, I have no use for all the "extra" functionality of a custom kernel. After the holidays, I'll look into providing a custom kernel along with the stock one (like bhb does with RR). Just out of curiosity, did you install the Kernel Auditor app?

NepoRood said:
@Debuffer, personally, I have no use for all the "extra" functionality of a custom kernel. After the holidays, I'll look into providing a custom kernel along with the stock one (like bhb does with RR). Just out of curiosity, did you install the Kernel Auditor app?
Click to expand...
Click to collapse
Yeah. I use Bhb kernel since 5.1.
Thank you for this.

NepoRood said:
It's a typo, my bad. You know that is the source code, right?
Click to expand...
Click to collapse
Yeah, I got that part after I went to the site. I was looking for the kernel in a bid to try using it with the ROM. I have been using the ROM for the past 3 hours now and all seems smooth and stable so far. I will keep running it and see, if it stays this way I just may have a new daily driver

Great rom, it runs very well. Only issue with it, is that the torch using gestures is very inconsistent. Similar to what happened when 6.0 roms first came out. It either takes 30 seconds to activate, or never works at all.
Also, the setting to control media volume by default doesn't work. This is the same on cm14.1, so imagine it's not something you can easily change in the rom.

Users with GPS problem only make the flash of this file that will be solved.
https://www.androidfilehost.com/?fid=24531035584725320
Please add publication. @NepoRood

Very good rom.stable and smoot.but there is little laggy for camera conect in many apk.more of it happens for front camera
Sent from my DROID Turbo using Tapatalk

great rom, liked it alot, clean installed it without any phone stop errors, bhb27's auditor n govtuner works perfectly aswell
only one issue i have was when i take photos im not able to share them online for some reason (example via watsapp or facebook) it always shows "sharing failed please try again" msg. dont know what happened there i tried re-installing watsapp and also a different camera app but still get the same error.
reverted back to 6.1 for now as i really need photo share as my work is depended on it, although i did notice the pictures i took on 7.1 now in the gallery were corrupt n un-viewable aswell ? was there something i did wrong? should i try flashing again?

Pakman300 said:
great rom, liked it alot, clean installed it without any phone stop errors, bhb27's auditor n govtuner works perfectly aswell
only one issue i have was when i take photos im not able to share them online for some reason (example via watsapp or facebook) it always shows "sharing failed please try again" msg. dont know what happened there i tried re-installing watsapp and also a different camera app but still get the same error.
reverted back to 6.1 for now as i really need photo share as my work is depended on it, although i did notice the pictures i took on 7.1 now in the gallery were corrupt n un-viewable aswell ? was there something i did wrong? should i try flashing again?
Click to expand...
Click to collapse
There are 2 folders where pictures are stored: DCIM and Pictures
Using the built in file explorer (or a PC), rename each of these. I did DCIM2 and Pictures2, then use your phone to take a picture. Both folders will be recreated. Then, drag and drop everything from the #2 folder into the corresponding "New" folder.
Hassle? Just a bit, but we did just change branches on our android phones :laugh: