Develop Bugs

Question...Noob stuff

Alright, I'm new to the whole Android thing.
Am I right in assuming, that without a front end GUI like Sense, Android is just another command line OS? Does it have an interface?
If it has an interface, why doesn't Google just release an end user install-able version of it so the user can do whatever they want with it? didn't the legality of unlocking and hacking your own personal device just get settled in congress? With that being said, I would like to be able to just simply download ICS and install it unmolested on my EVO. Hell, I would have liked to do that with Gingerbread too. I know there are different phones, different hardware platforms, but that's all driver related anyway. I thought it was all Open source?
Just an interesting thought I had, no real issues or nothing going on.

Sense is a skin put on top of standard Android GUI. There are some subtle differences. Just install a non sense Rom like cm 7, it seems to be very popular, I like the sense tweaks, calendar, messaging, contacts.
You should be able to dl ics and install it if u know how to port a Rom.
Sent from my Synergized Evo with aggressive Freedom using the XDA app

Just be sure and make a nandroid backup before you switch in case you want to go back to what you had and store a copy of it on your desktop hard drive or in some location other than your phone.

CM7 is what sparked this question. I installed it, and it broke my WiFi and my GPS. If Gingerbead was an out of the box solution, there would be drivers and portability. I don't understand why there has to be ports of roms and things from other phones to make the OS work. Thats where i think Google is dropping the ball. Why is there not some sort of driver repository where one could get all the hardware drivers for their device and simply load them into the OS and install it? That would make the most sense to me. It puts the ownage of hardware support back o nteh manufacturer to ensure its updated.
I don't know, something to rant about I guess.

I'm running decks rom rite now and never had any issues at all. Try that instead. Its in dev
Sent From My Pocket

There are ROMs out there that are just pure android with no UI overlay or anything, you might just have to look back a bit in the forums and settle for 2.3.3 or earlier. At one point there was a ROM called PureGB or something along those lines that was just as it sounds, pure GB - built right from the SDK. You have to understand that the EVO is manufactured by HTC and Sense is their baby so they are never going to give us a stripped down ROM... Google puts the SDK out there and devs create ROMs for individual devices so it's all about what the devs want to make.
The popularity of Sense 3.0+ and AOSP custom ROMs has steered devs away (for the moment) from creating super basic ROMs but it can be done.
There is a stock android 2.3 launcher, notification bar, messaging app and so on, it's just that the alternatives are entirely to lucrative to pass up for most people.
I hope that at least makes some sense (get it!?! Sense!?!... So lame...) and I'll try to find that Pure GB ROM and link it so you can dig it.

[Q] AOKP or CM9 kang?

Is there a difference and if so, what is the difference?

each has changelogs afaik , im using aokp and love it. cant speak for cm yet and unless im mistaken arent they all kangs right now ?

Flash them both, and have a look. It takes all of 5 minutes to flash a ROM. I used the CM9 builds on my Desire, not much of the CM9 extras are working, I'm not sure if that's the same for the Prime.
AOKP has extensive working tweaks, that much I do know.

aokp
difference is its features. cm9 is still in the works so a lot of the options you find in CM7 devices arent present yet.

On zephiK's recommendation I installed AOKP and don't see myself changing. It's a solid ROM.

hondaboi20002 said:
Is there a difference and if so, what is the difference?
Click to expand...
Click to collapse
There will be. There will be.
But for starters, AOPK is like Cyanogenmod, in the sense that both are based in AOSP. Neither are finished, at their current stages.

Im going from CM9 Kang to AOKP right now. CM9 was getting a little laggy for me (when moving around homescreens). And im sold by the AOKP tweaks

Reading the op of both rom threads can answer this
Sent from my Galaxy Nexus

Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?

azn android said:
Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?
Click to expand...
Click to collapse
AOSP is Android Open Source Project, Android before manufacturers get their hands on it and install Sense or Touch Wiz. Essentially the Nexus Primes OS. AOKP is Android Open Kang Project a modified AOSP ROM made by Team Kang, with more bells and whistles than the stock Nexus ROM. Hope this helps.

azn android said:
Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?
Click to expand...
Click to collapse
Fresh blood
AOSP - Android Open Source Project. Simply put, this is Android straight from Google, with no modifications. This is what you have on your phone. All of the ROMs here are built on AOSP - most, like AOKP, add modifications, while some don't.
AOKP - Android Open Kang Project. A ROM by Romanbb and his friends, built on AOSP, that adds many modifications and tweaks that aim to improve the end-user experience.

Yes it does thank you! So basically AOSP and AOKP are categories of the type of ROM a ROM is? Are there any other projects or are these the only two ones? Which one offers more stability and fluidness in the OS?

azn android said:
Yes it does thank you! So basically AOSP and AOKP are categories of the type of ROM a ROM is? Are there any other projects or are these the only two ones? Which one offers more stability and fluidness in the OS?
Click to expand...
Click to collapse
Almost.
AOSP is the version of Android that comes straight from Google. Manufacturers (such as Samsung, HTC, Motorola, etc) usually like to take AOSP ROMs and add their own modifications to it - and that's how we got Samsung's Touchwiz, HTC's Sense, Motorola's MotoBlur, etc.
However, Google partners up each year with a manufacturer to release a Nexus device. These devices are special in that they always come with AOSP, and because of that, they are always the first to receive updates to the Android OS, and are for the most part the devices with the most developer support on forums such as XDA.
AOKP isn't a type of ROM in itself - it is just a name given to a specific ROM. Like AOKP, you have for example CyanogenMod, which is yet a different ROM. Because we have a Nexus device, all of the ROMs you'll see in our development section are all built straight on AOSP. There are many ROMs out there, all unique in their own way, and the best way to find out which one is right for you is simply to try them all out. It may be scary at first, but after your 1st or 2nd flash, you'll become addicted for a few weeks

Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?

azn android said:
Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?
Click to expand...
Click to collapse
It's not, where did you read that? CM9 will be built from the ground up using the AOSP released by Google back in November.
Kang are using the Cyanogen GitHub to compile a CM9 beta ROM, as as far as I know, CM haven't released any betas (do they even release beta ROMs?) As far as I know they just go for a final build which is as stable as stable can be, people can't wait for the final builds and build ROMs using their work so we can try them as they are developed by the CM team.
That's my understanding of it anyways.

Oh my bad. I jumped to conclusions when I read the title to this post haha.

azn android said:
Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?
Click to expand...
Click to collapse
CM is not built off of Kang. Kang is simply a term used to denote a compiled build of a ROM by someone other than that ROM's team or "authorized dealer". For example, User A compiles CM, changed a few lines in the code, and then publishes it here as his own work. That is a kang, and its highly frowned upon.
The reason the CM thread is labeled a "kang" is because there are no official builds of CM9 coming straight from CM yet - they're just experimental builds as of now. The reason why its allowed, is because recognized members of the CM team are releasing them.
I unfortunately don't even have my Nexus yet, but its coming in two days and I'm getting my feet wet. However, from what I've been exposed to, one of the more popular combinations around here seem to be AOKP with Franco's kernel.
I strongly advise you not to flash anything yet, though. You seem motivated to be here, which is good - but you also seem to not know too much about the world of Android yet.
Please, take the time to read through the following links:
Basic Android Terminology
Galaxy Nexus Frequently Asked Questions
Different Guides and Tutorials for the Galaxy Nexus
After you've finished, you'll be a little more familiar with Android and how stuff works. If you have questions, I strongly advise you to search Google and XDA first - I can almost guarantee your question has already been answered before
If you searched, but couldn't find an answer, please post in the Q&A sub-forum - there are many members like myself who love to help new users who are willing to take the time to learn themselves, without expecting others to do their work for them.
Finally, as a general rule, don't post stuff in the development sub-forum that aren't specifically development related. Yes, if you'll go through them, you'll probably see a bunch of posts that aren't tied in directly to development - but two wrongs don't make a right if you have a question about a specific ROM, usually the answer is right in that ROM's thread - if it isn't, most ROMs have IRC chatrooms set up, and if they don't - consider making a thread in the Q&A sub-forum.

AOKP vs Sprint ROMs

In my previous life with my TouchPro2, I used the AOSP roms and they worked well. With my Galaxy S II / D710, I've only used the Sprint based ROMs.. including the latest FC07.
I haven't found any posts comparing the AOKP ROM (which, unless I'm mistaken is based off of AOSP) to these Sprint ROMs..
Are there any major differences or anything that the AOKP ROMs will not do?
I'd be curious to hear opinions from people who have tried both and why they ended up with one over the other.
thx

Just to clarify, they're not "Sprint ROM's", they're called "Touchwiz ROM's". The Touchwiz UI is added on top of Android by Samsung then Sprint adds some apps and there you have it. Now I shall let someone who has experience with AOKP answer better for you since I do not have any experience with AOKP yet.

To be quite honest, there's nothing that one can do that the other probably cant. AOKP and AOSP tend to have more things built into the ROM itself like overclocking, etc.
But in the end, no, there's nothing I can think of that one can do that the other can't. There may be something out there, but I've not come across it yet. I've used both, and I prefer somethings about each.

clamknuckle said:
To be quite honest, there's nothing that one can do that the other probably cant. AOKP and AOSP tend to have more things built into the ROM itself like overclocking, etc.
But in the end, no, there's nothing I can think of that one can do that the other can't. There may be something out there, but I've not come across it yet. I've used both, and I prefer somethings about each.
Click to expand...
Click to collapse
There are some things like cm7 you could use Wii mote with the Bluetooth stack and could not on touch wuz....aokp is cm 9 on steroids..... Lots more customizable
Sent from my SPH-D710 using xda premium

I haven't tried an AOKP rom but I'm assuming it's very similar to an AOSP rom. I personally think an AOSP rom as a lot less bloat, and right out of the box it's very customizable, but I switched back to a touchwiz rom because I think the samsung camera app is one of the best camera apps out there, plus I think touchwiz runs a lot better on our phones.

Aside from a few "bugs" here and there with the FCxx roms that they are basing the AOKP roms off of, there are only a few faults. One I keep on running into is the Netflix problem. Hell, aside from getting sick of trolling this place for over a year combined with my Streak 7 and my E4GT, I had to try and get in on the action with FC and FB "leaks", CM9, AOKP, and other 2.3 based rom fun.
But seriously, the only problem I have keeping me from making AOKP a daily driver is the Netflix problems. I need my netflix for work.

Kevin_Q said:
Aside from a few "bugs" here and there with the FCxx roms that they are basing the AOKP roms off of, there are only a few faults. One I keep on running into is the Netflix problem. Hell, aside from getting sick of trolling this place for over a year combined with my Streak 7 and my E4GT, I had to try and get in on the action with FC and FB "leaks", CM9, AOKP, and other 2.3 based rom fun.
But seriously, the only problem I have keeping me from making AOKP a daily driver is the Netflix problems. I need my netflix for work.
Click to expand...
Click to collapse
aokp is being ported right now but it is just like cm9 it's built from aosp source code ... And not being based off any of the fc or fb leaks .... They are using kernels from them with changes because there is no kernel source to build a aosp kernel with right now
Sent from my SPH-D710 using xda premium

Epix4G said:
aokp is being ported right now but it is just like cm9 it's built from aosp source code ... And not being based off any of the fc or fb leaks .... They are using kernels from them with changes because there is no kernel source to build a aosp kernel with right now
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
And I learn something new every day.
As a side note: I like AOKP because of pink unicorns.

R800X CDMA FXP CM9 questions

Can someone list a couple of apps that don't work?
I can't get Google Goggles to even snapshot a picture of a QR code
I like that fact that FXP has done what they have but
CM9 dev team hasn't done much of keeping this phone what it was
No PSExperia support, No Video Play Back, Most google functions don't work, Forced dim lighting
FXP keep on rocking and hopefully you guys will get this rom upto full function

Cm9 is still in alpha, it's expected to be buggy

ICS still have issues with apps, I suggest you Google ICS compatibility, which is why its not being released sooner for many devices. As of this date, I don't even see CM9 for the Play (GSM) at the official Cyanogen website, and the CDMA version is not supported, so I don't see where you can blame the CM9 dev. Just have to wait till Sony release ICS for it.

FPlusPS3 said:
Can someone list a couple of apps that don't work?
I can't get Google Goggles to even snapshot a picture of a QR code
I like that fact that FXP has done what they have but
CM9 dev team hasn't done much of keeping this phone what it was
No PSExperia support, No Video Play Back, Most google functions don't work, Forced dim lighting
FXP keep on rocking and hopefully you guys will get this rom up to full function
Click to expand...
Click to collapse
CM9 is like the bleeding edge of technology. It's to be understood that, since it is in development, not everything is going to work like Stock.
The rule for using Custom ROMs is if everything has to work like stock, stick with ROMs based on Stock. If you want to help test the latest Mod and are willing to sacrifice some useability to do so, then go with the ROMs that are in development.
If you do decide to go bleeding edge, you are expected to keep up to date with the development thread for that ROM and to post your observations, pro and con, in that thread. That's the only way the devs and other testers know what the issues are.
A good stock ROM is the one by KeiranFTW called DarkForest 3.X (3.0.5 for CDMA, 3.1.0 for GSM). It's a nice balance between customization and stock, and pretty much everything works like you would expect. [ROM] Darkforest ROM 3.0.5 UPDATE | GSM 2.3.4/.62 | CDMA 2.3.3/.145 [WIP]

Stock Jellybean > Custom rom: silly?

So I basically just flashed my yakjuxw build to yakju, to get my hands on Jellybean. The experience is more than awesome, buttery smooth and fast! Now, I wonder, what will (for example) AOKP bring to the table to make it 'even more' buttery and fast, etc? I'm not much of a tweaker, I just really wonder if there will be any SIGNIFICANT advantages over stock rom. It all seems a bit silly to me.

Every other Android phone I have had I've flashed all the ROMs available purely to try and have the stock experience or get to a new version of Android. I purchased the Galaxy Nexus so I would get all the updates when released and to enjoy the stock experience, I have no intention of installing custom ROMs on this device.
Cheers
Jason

aokp brings few options to try with not the speed. It's the user experience that get enhanced with custom roms.
Similarly cm10 aosp and stock custom Roms do the same but not as much as cm10 and aokp do natively.

atifsh said:
aokp brings few options to try with not the speed. It's the user experience that get enhanced with custom roms.
Similarly cm10 aosp and stock custom Roms do the same but not as much as cm10 and aokp do natively.
Click to expand...
Click to collapse
So what you're saying is that it's mostly visual differences? I mean what are the key elements that AOKP/ CM10 provide?

gideonMorrison said:
So what you're saying is that it's mostly visual differences? I mean what are the key elements that AOKP/ CM10 provide?
Click to expand...
Click to collapse
Watch a video or something. Aokp brings a lot of new features, such as customizable navbar, options to move your clock and change your battery icon and what not, weather and calendar on your lock screen. That's the type of things you'll see on a custom ROM.
Sent from my Galaxy Nexus using xda app-developers app

Custom ROMs are more about extra features. At least when it comes to builds like Jelly Bean. I don't see Jelly Bean needing much in performance enhancements.
Sent from my AOSP Android 4.1.1 Galaxy Nexus

Aokp or cyan brings TONS of useful real world features. Its not just visual stuff or fluff. If you are asking then you aren't aware what these roms offer.
The problem is their JB versions don't have much added yet. So you'd have to flash their ICS version to see a fully loaded rom.

RogerPodacter said:
Aokp or cyan brings TONS of useful real world features. Its not just visual stuff or fluff. If you are asking then you aren't aware what these roms offer.
The problem is their JB versions don't have much added yet. So you'd have to flash their ICS version to see a fully loaded rom.
Click to expand...
Click to collapse
Noted. It sounds interesting. It's just that it makes my head spin sometimes, all the possibilities I guess we have to wait until a good JB rom shows up. However, isn't it slightly annoying you have to reflash the whole time to get the newest builds etc? I just don't see myself doing that the whole time

I am getting a nexus Monday. Right now I have a note. I have been reading the last coupledays to try and catch up but maybe I have missed something. Isn't there already good jellybean roms out already? Like Paranoid Android?

gideonMorrison said:
Noted. It sounds interesting. It's just that it makes my head spin sometimes, all the possibilities I guess we have to wait until a good JB rom shows up. However, isn't it slightly annoying you have to reflash the whole time to get the newest builds etc? I just don't see myself doing that the whole time
Click to expand...
Click to collapse
Alot of roms use Rom Manager or Goo Manager to host or link to their roms, with goo manager you can update most roms like an ota update when ever the dev updates the rom on Goo.im , same holds true with Rom Manager though i dont recall which website is used.
As far as both CyanogenMod and AOKP you can use these applications so that you dont have to search for the latest and greatest, just hit a button telling the application to check for updates and if there is one it applies it for you and phone updates nice and easy, of course you have to let the phone reboot to recovery and what not but the entire process becomes automated.

gideonMorrison said:
Noted. It sounds interesting. It's just that it makes my head spin sometimes, all the possibilities I guess we have to wait until a good JB rom shows up. However, isn't it slightly annoying you have to reflash the whole time to get the newest builds etc? I just don't see myself doing that the whole time
Click to expand...
Click to collapse
No not at all. Before jelly bean, I just flashed a loaded aokp and ran it for months and months. No need to upgrade. Currently JB roms need to be merged but once they are finished just flash one and go live life using the extra functions. If you are looking for a hobby then yes flash each week.
And as mentioned, most of the time you can just flash the rom update just like an OTA and you don't lose anything. Its just like an official ota update.