641 replies to this topic

[Obsidian]

Just wanted everyone to know that Super Dallas just posted a rag3 v3 that is SS flash able

EDIT: Never mind v3 = #fail once again

Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

[Thepatriotvirus]

Just wanted everyone to know that Super Dallas just posted a rag3 v3 that is SS flash able

EDIT: Never mind v3 = #fail once again

Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2

Aw man!

[Int_Rnd_Pooka]

New question (sorry, you have gotten me curious now MrRedPants):

What's the main difference between AOKP and CM? also, in hash's download location he has it divided between the CM10, CM9, AOKP and AOSP. but I thought that AOSP was what Cyanogen and AOKP were based on, so I don't understand how you can have an AOSP rom.

This is really just for instruction's sake, since when I went to download this new rom which I'm trying out, I saw these designations and was mildly confused.

Thanks for everything.

CM is AOSP with a lot of source modifications built in before compiling to make a final ROM.

Okay, this implies that AOKP modifies the ROM after it's compiled. This is completely untrue and is very misleading.

AOSP = Android Open Source Project. This is "vanilla" android, direct from google, and has no "extra" features.
CM = Cyanogenmod. This is a fairly heavily modded AOSP source code tree that compiles to give you additional features as part of the ROM
AOKP = Android Open Kang Project. This is ALSO a heavily modded AOSP source code tree. It also compiles to give you a slew of features that aren't available in AOSP

Both CM and AOKP are source built. They each have several additions. To be perfectly honest, from an end user standpoint, I've found them to be nearly identical as far as functionality and added features are concerned. They have a hugely similar feature set, it's really just where the options are located in the settings menu. And AOKP comes with unicorn all over it, if you like that sort of thing. As far as from a back end code standpoint, they're still both based on the same google code for Android, so they're going to perform similarly as well. It comes down to whichever you like the feel of, for the most part.

In regards to the numbers following CM, CM9 is Ice Cream Sandwich, based on Android 4.0.x, while CM10 is a JellyBean build, based on Android 4.1.x.

[johnlgalt]

Okay, this implies that AOKP modifies the ROM after it's compiled. This is completely untrue and is very misleading.

AOSP = Android Open Source Project. This is "vanilla" android, direct from google, and has no "extra" features.
CM = Cyanogenmod. This is a fairly heavily modded AOSP source code tree that compiles to give you additional features as part of the ROM
AOKP = Android Open Kang Project. This is ALSO a heavily modded AOSP source code tree. It also compiles to give you a slew of features that aren't available in AOSP

Both CM and AOKP are source built. They each have several additions. To be perfectly honest, from an end user standpoint, I've found them to be nearly identical as far as functionality and added features are concerned. They have a hugely similar feature set, it's really just where the options are located in the settings menu. And AOKP comes with unicorn all over it, if you like that sort of thing. As far as from a back end code standpoint, they're still both based on the same google code for Android, so they're going to perform similarly as well. It comes down to whichever you like the feel of, for the most part.

In regards to the numbers following CM, CM9 is Ice Cream Sandwich, based on Android 4.0.x, while CM10 is a JellyBean build, based on Android 4.1.x.

You're right, but only if they misread what I wrote because I misread what they wrote.

I thought the post I replied to said AOSP not AOKP. Hence my reply.

I went back and edited my reply showing this. and linking to your post for the real answer

[Aldroid33]

Obsidian, I am using a touch Bootstrap which works beautifully. However, does anyone have a versions which boots up to recovery each time? Also, to make it boot to recovery in BP Tools? Or, anyone know how to modify the touch bootstrap that I have to do so?

[Obsidian]

Obsidian, I am using a touch Bootstrap which works beautifully. However, does anyone have a versions which boots up to recovery each time? Also, to make it boot to recovery in BP Tools? Or, anyone know how to modify the touch bootstrap that I have to do so?

Yeah I use that on my 7. You could ask the guy that ported the BPtools mod to the Bionics BS if he could help with that

I believe the thread belonging to this guy is the one you want to talk to

Please Login or Register to see this Hidden Content

I personally am going to just wait for Hash to finish Safestrap v3. It will be touch, have the ability to flash any rom and boot everytime like it does now

Sent from my DROID BIONIC using Xparent SkyBlue Tapatalk 2

[mrredpants]

Okay, this implies that AOKP modifies the ROM after it's compiled. This is completely untrue and is very misleading.

AOSP = Android Open Source Project. This is "vanilla" android, direct from google, and has no "extra" features.
CM = Cyanogenmod. This is a fairly heavily modded AOSP source code tree that compiles to give you additional features as part of the ROM
AOKP = Android Open Kang Project. This is ALSO a heavily modded AOSP source code tree. It also compiles to give you a slew of features that aren't available in AOSP

Both CM and AOKP are source built. They each have several additions. To be perfectly honest, from an end user standpoint, I've found them to be nearly identical as far as functionality and added features are concerned. They have a hugely similar feature set, it's really just where the options are located in the settings menu. And AOKP comes with unicorn all over it, if you like that sort of thing. As far as from a back end code standpoint, they're still both based on the same google code for Android, so they're going to perform similarly as well. It comes down to whichever you like the feel of, for the most part.

In regards to the numbers following CM, CM9 is Ice Cream Sandwich, based on Android 4.0.x, while CM10 is a JellyBean build, based on Android 4.1.x.

Sorry I'm late into this.

I presume any stock Google device has what would be considered ASOP, ie pure Android.... Eg gnex and nexus 7

This true Jon?

I was just giving a general overview of ROM choices from a practical standpoint in my earlier post.

I THINK hash has AOSP section because he and d hacker are trying to get all hardware issues fixed on stock first before moving ON (IE Data issues) . Or to give it as a base for others to Kang. This is my assumption. Sent from my DROID BIONIC using Tapatalk 2

[johnlgalt]

It's become confusing. Back in 2009, AOSP was the Android Open Source project and referred to only the Android OS that anyone could freely download, modify, and install on a device.

Now that Google is into making / marketing what we then called vanilla devices (such as the OG Motorola DROID) AOSP could be said to be referring to those devices as well. However, I stick with AOSP meaning the OS itself and AOSP-devicemeaning any device that was designed to run an AOSP-derived ROM with minimal modification - Nexus series, DROID, etc.

So, yes, those devices as you noted are vanilla devices, and are able to run AOSP-derived ROMs (both stock and 3rd party compiled, like CM / AOKP) with minimal fuss.

As for Hash and DHacker - It's probably so others can use their developments as a base for other ROMs.

[mhous33]

Obsidian, I am using a touch Bootstrap which works beautifully. However, does anyone have a versions which boots up to recovery each time? Also, to make it boot to recovery in BP Tools? Or, anyone know how to modify the touch bootstrap that I have to do so?

here's my thread on the standard bootstrap with bptools mod:

Please Login or Register to see this Hidden Content

you can extract the hijack binary from it (in the /assets directory) and drop it into your touch recovery using 7-zip. i haven't used the touch recovery, so not sure if it will work, but if it's based on koush's bootstrap it should.

i agree with Obsidian though, can't wait for safestrap 3!

[Aldroid33]

Yeah I use that on my 7. You could ask the guy that ported the BPtools mod to the Bionics BS if he could help with that

I believe the thread belonging to this guy is the one you want to talk to

Please Login or Register to see this Hidden Content

I personally am going to just wait for Hash to finish Safestrap v3. It will be touch, have the ability to flash any rom and boot everytime like it does now

Sent from my DROID BIONIC using Xparent SkyBlue Tapatalk 2

thanks, looks like he already responded. Safestrap 3 sounds great! The only problem I have with safestrap is not being to flash directly over 247 and keeping my data. Correct me if I'm wrong? That was the difficulty I had with flashing RAg3 and Liquid 1.2 on Safestrap. You get a blank slate on the safe side, and you can't flash over 247 on the unsafe side.

[Aldroid33]

here's my thread on the standard bootstrap with bptools mod:

Please Login or Register to see this Hidden Content

you can extract the hijack binary from it (in the /assets directory) and drop it into your touch recovery using 7-zip. i haven't used the touch recovery, so not sure if it will work, but if it's based on koush's bootstrap it should.

i agree with Obsidian though, can't wait for safestrap 3!

Thanks id like to give it a try. I haven't used 7-zip. Can I use Root explorer for this?

[mhous33]

Thanks id like to give it a try. I haven't used 7-zip. Can I use Root explorer for this?

if you want to send me a link to the touch recovery i'll edit it with the bptools hijack binary. i haven't seen it posted anywhere for awhile.

[Aldroid33]

if you want to send me a link to the touch recovery i'll edit it with the bptools hijack binary. i haven't seen it posted anywhere for awhile.

pm sent

[docluv01]

Hey guys....I have a silly question (please no reeming).

I have been using SParky's Axiomcs rebirth as my daily driver, coming from liquid, this was a perfect replacement!

No knocking of the author, but I found a few glitches when it came to wifi and battery power. (also have issues when in dead area...)

I'm thinking of moving to one of teh JB builds by team haters. I see they have a few black ones, but not sure if these woudl be equivalents...

What would be the known issues with the JB builds? are the AOKP builds based off the latest AOKP or are they usually a version or 2 behind?

Any help or guidance would be appreciated, as im looking for another daily driver...thanks!

[mrredpants]

Hey guys....I have a silly question (please no reeming).

I have been using SParky's Axiomcs rebirth as my daily driver, coming from liquid, this was a perfect replacement!

No knocking of the author, but I found a few glitches when it came to wifi and battery power. (also have issues when in dead area...)

I'm thinking of moving to one of teh JB builds by team haters. I see they have a few black ones, but not sure if these woudl be equivalents...

What would be the known issues with the JB builds? are the AOKP builds based off the latest AOKP or are they usually a version or 2 behind?

Any help or guidance would be appreciated, as im looking for another daily driver...thanks!

The only issues I'm aware of are camera... Need to use camera 360 from market and bluetooth does not work correctly.

I'm pretty sure they are fully functional. All JB roms are based off same source.. Aokp and CM10 by Hashcode and d hacker. Don't know version

Sent from my ICS'd Blackholed BIONIC

[Obsidian]

Hey everyone I just got a copy of Safestrap v3.01 from Hashcode so I'll be testing it out here in a minute and will report back... Hopefully it'll be released soon :-)

Nexus 7 [Rom] C&C (PA+CNA) [Kernel] Franco's r17

[Rootuser94]

Hey everyone I just got a copy of Safestrap v3.01 from Hashcode so I'll be testing it out here in a minute and will report back... Hopefully it'll be released soon :-)

Nexus 7 [Rom] C&C (PA+CNA) [Kernel] Franco's r17

Super Epic win!!!!!!!!!!! let us know how awesome it is

[Obsidian]

Just wanted to let everyone know that i added two new roms and that I added their build dates. I will continue to do this and when a rom is updated i will move it to the top of the list

I added "9–10 CM9 unofficial aosp" . Compiled by Pooka using DH and Hash's code...

So those of you that want an updated cm9 build thank Pooka for compiling it... You can check what your current rom is built from your phones info

I also added "Speedlite AOKP v2.0 by JP1044" ... He just released this on the 5th

Nexus 7 [Rom] C&C (PA+CNA) [Kernel] Franco's r21

[Obsidian]

Hey guys....I have a silly question (please no reeming).

I have been using SParky's Axiomcs rebirth as my daily driver, coming from liquid, this was a perfect replacement!

No knocking of the author, but I found a few glitches when it came to wifi and battery power. (also have issues when in dead area...)

I'm thinking of moving to one of teh JB builds by team haters. I see they have a few black ones, but not sure if these woudl be equivalents...

What would be the known issues with the JB builds? are the AOKP builds based off the latest AOKP or are they usually a version or 2 behind?

Any help or guidance would be appreciated, as im looking for another daily driver...thanks!

The only issues I'm aware of are camera... Need to use camera 360 from market and bluetooth does not work correctly.

I'm pretty sure they are fully functional. All JB roms are based off same source.. Aokp and CM10 by Hashcode and d hacker. Don't know version

Sent from my ICS'd Blackholed BIONIC

Like Mr said all of our builds will be built from Dhacker's and Hashcode0f's base. cm9, cm10 & ics and jb AOKP.

To answer your question though there is a couple variables. DH and Hash build their builds from the newest cm and aokp code. So no their builds aren't a version or two behind. But that doesn't mean that the rom you are running is built from the newest code. It is the Dev's choice on which base they use to build their rom from.

Dh and Hash were putting out nightly builds of cm9 and aokp until 7-25-12 when their Rombot server got hacked. So as far as I know all ICS AOKP builds are built on top of that last build. Other people tried to compile new builds but couldn't get it to work. Luckily Pooka has been able to compile working updated cm9 builds but you will have to check the roms info to find out how recent of a cm9 build they used. The other lucky thing is that Hash and Dh started putting out builds again but they are all jb builds either AOKP or cm10.

So if you want to stay on an updated jb build goto the The targa folder link and dl the most recent build. If you don't care about that that much check out other peoples jb builds. Thats not to say there isn't a dev out their building from updated source but most aren't.

Mr also gave you a decent idea of what is wrong with JB builds but he left out one big point. JB builds still don't have the strongest 4g/3g data connections so I personally am not running one as my daily driver.

I personally use a blur rom as my Daily Driver because I like having a fully functioning phone. I haven't found a mod yet that has made me want "it" over a phone that functions like it is supposed to. I hate the rotation issue and I actually like the blur apps. Like the dialer and camera...

Nexus 7 [Rom] C&C (PA+CNA) [Kernel] Franco's r21

[Int_Rnd_Pooka]

I know that TeamHaters has current CM9 and CM10 compiles, and I want to say JB-AOKP too, so they're going to be current as well (provided they're updating those ROMs, I haven't checked for a bit)