Database Info

[Source code][GINGERBREAD]Android 2.3 just dropped

http://developer.android.com/sdk/android-2.3.html
Sent from my SPH-D700 using Tapatalk

Oh my. +99
Sent from the future.

I await all ROMs with gingerbready Greatness!!
And to be honest, I thought we'd be a little ways into Jan before we seen the source code. Glad it took just 1 day after the Nexus S release. Now, the many-months wait for OEMs to get Official updates out to the devices =\

if that was sent from the future, that comment must mean that you are afraid for us because something is WRONG with gingerbread because you would have KNOWN about this already! LOL so HOW IS IT?!?!?

Yay!
Sent from my Epic 4G

Yet still no official 2.2 for us.... awesome.

Is this different from what was dropped last week?
Sent from my SPH-D700 using XDA App

How did GB source C drop before FroYo????????

If you are referring to what I posted, it was source code
For the Nexus S kernel Android version 2.3
And yes, pretty cute we have available source code for a new
OS before we seen a piece from any Android 2.2 source code for our Epic
jaaka78 said:
Is this different from what was dropped last week?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Sent from my SPH-D700 using Tapatalk

Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?

sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
Slow down, Sprice. Gotta get 2.2 first.

sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
I think the million dollar question is what are the predictions for an official 2.2
rom for our Epics? jk but I think after samsung and sprint gets ahold of it first.
Otherwise it would be another AOSP like cyanogen.

I've got a related (and hopefully not stupid) question regarding the process.
So, I know we're waiting for the 2.2 kernel source for our epics, obviously.
Generally, what's the process in between Google dropping a version's source, and it being released (by samsung) to us? This is not a complaint-- I'm really just curious how it works.

decalex said:
I've got a related (and hopefully not stupid) question regarding the process.
So, I know we're waiting for the 2.2 kernel source for our epics, obviously.
Generally, what's the process in between Google dropping a version's source, and it being released (by samsung) to us? This is not a complaint-- I'm really just curious how it works.
Click to expand...
Click to collapse
I know someone can explain better than I can.
Google drops the stock rom. This wont run on our phones without drivers, and support for specific hardware for our device. Then you have Sprint carrier modifications like VVM, ota updates, 4G and other configured apps. After all the work is done, developers can go back and modify things to their liking.
Otherwise you would have a from the ground up like CM,
where its a lot of trial and error, getting the ROM to support hardware/software.

sprice5 said:
Now for the million dollar question. What are you predictions for a working 2.3 rom for our Epics?
Click to expand...
Click to collapse
I'm no developer or expert, but i'd give it a week or two before we see a slew of ROMs, maybe less. Its great that Cyanogen has 4G working on the Evo, so cant wait for 4G-enabled CM6/7 for our Epics. As for an official 2.3 update from Samsung.... March is my earliest guess
hayabusa1300cc said:
I think the million dollar question is what are the predictions for an official 2.2
rom for our Epics? jk but I think after samsung and sprint gets ahold of it first.
Otherwise it would be another AOSP like cyanogen.
Click to expand...
Click to collapse
I'd say we get official 2.2 updates in a few weeks. The leak is out, so they are probably just cleaning it up for release. The plain-jane (no custom ROM) leak works flawlessly on my phone tho.

At this point Noobnl is going to deliver faster than Samsung is on the Froyo. He's got CM pretty much done it seems. Whenever Cyanogen's done with gingerbread source for CM7(im presuming) noobnl will hopefully start on that as well.

I bet that the hardware drivers for 2.2 will work with 2.3, sounds like 2.2 to 2.3 is a lot less of a change than 2.1 to 2.2, but I could be wrong.
sent from my nexus s with a keyboard

For Samsung it's more rational for them to use their dev's time to spend on making new working firmware for new devices that are debuting at CES and to ready the firmware for those devices.
Samsung's strategy has changed over the years and is now executing the mantra "first out the door with new technology." While this is great for those of us who like new toys, it's a set back when we want long term support for our new toys. If their R&D resources are tied up working out new firmware for the next gen, they lose focus on their current customers.
If you've kept up on the latest engadget, gizmodo, boy genius, etc etc news - you'll know there's a dual core super duper galaxy whatever chip coming out soon. That's where the resources are now. For a company that has been lagging behind in innovation for the last few years in the mobile area, this is their new direction... Innovate quickly and be the first to market. Support resources are but a second thought; overhead.
http://www.bloomberg.com/news/2010-...uct-crisis-as-choi-tries-to-triple-sales.html might give you a better perspective of the company.

So if I am reading this right....
Once we have CM6 running on our epics it will be a lot easier for us to get Gingerbread installed; for that matter any new verisions?

Does this really need to be in the Epic section?

[Dev] AOSP Gingerbread

Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...

Here's my 2.6.36 kernel zImage file and .config build if anyone is curious.

My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board. With the Nexus S source out, some things shouldn't be TOO hard, but I think porting the CDMA stuff is probably a huge challenge.

plapczyn said:
My suggestion...change your title to [Dev] AOSP Gingerbread. Start a github or similar repository and get cracking. I'm sure there are plenty of people that would consider jumping on board.
Click to expand...
Click to collapse
id jump on board if i knew what i was doing

Glad your focusing on this! I don't think we have to finish froyo to start gingerbread. Not sure how much I can help but hit me up if you need anything done.
Sent from my SPH-D700 using Tapatalk

I glad too see that someone is taking initiative here. My thinking all along is the drivers for froyo will most likely work in someway for gingerbread but without kernel source for froyo yet, I would think you would have to start from ground up. But good luck to you regardless.
Sent from my SPH-D700 using XDA App

This is delicious. Now it only needs sauce.
Everyone can learn from the OP's example. Less posturing more action.

msponsler said:
Yeah, I know...let's get a stable Froyo first.
But...
I pulled the 2.3.1 (gingerbread) source, and it's currently building. I hit a couple of snags, but I'm off and running so far.
I've also compiled the latest 2.6.36 kernel -- compiled, not tested! Don't get excited just yet.
I'm not going to lie, I'm green to android. But I've worked with Linux professionally for 15+ years. I've been compiling kernels since Linus released 2.0 oh so long ago. Building Linux x86 from scratch (go gentoo linux!) is nothing new to me. But android and arm...ehh...bear with me.
So is anyone else trying to do this? I'd like to collaborate and hear about your progress and any problems you've had. No need to try to reinvent wheels or anything.
Step 1 is getting it to boot...
Click to expand...
Click to collapse
About time!

Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App

I have it just about booting(;
Sent from my SPH-D700 using XDA App

somedude0608 said:
Thank you for working on this. I never really understood the source argument. I just put gingerbread on my old hero and everything works except for camera and screen rotation. It sure as hell doesn't have an official/leaked release or even froyo source. Anyways just ranting about the things I hear. I know I dont have the skills to work on this stuff, so thanks for the effort.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I agree, I had froyo on my hero long before I even thought about switching to the epic.... and they've made so much progress on gingerbread... I often wonder whether I made the right choice or not going with the epic. Although the evo doesn't have a keyboard and is really square, it gets a lot of attention and has had many official updates. I wish samsung would get off of their asses and just release the source.

I'd love to help out any way I can. I'm not a programmer, but I hve a great understanding on what the issue is. I had a hero before the epic, and they have fully functional froyo despite never having kernel source. One would have to be built, cause I don't think samsung is going to really support us that much longer (if at all) and give us any hope for gingerbread source. The trickiest part is the cdma/wimax radios (wimax still not supported in cyanogenmod for evo).
Sent from my SPH-D700 using XDA App

bubby323 said:
I have it just about booting(;
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Did you build gingerbread from source?
What kernel are you using?
I built a 2.6.36 last night...but the more I thought about it, the more I realized it doesn't do me any good as it is right now.
I've downloaded samsung's kernel source for 2.6.29 and I'm trying to get the modules for the video, radio, etc... to compile with 2.6.36.
The nexus s is using 2.6.35, which is fine when it comes to the video drivers, wifi, and such....but it doesn't do us any good when it comes to 3G because tmobile doesn't use CDMA, so it wouldn't have the same radio kernel modules.
I'm currently running noobnl's cyanogenmod (froyo) on my epic, and that has a 2.6.32.9 kernel. I'll have to take a closer look at how you built that kernel.

Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App

nerdtaco said:
Thank you for your initiative OP! I appreciate it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Seconded! I know nothing about developing software but I'm a pretty good test dummy =)

This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.

furysama said:
This is pretty kickass. Is there anything in particular you could use for help? I have some limited experience with both linux and android specific kernels.
Click to expand...
Click to collapse
At this point I don't necessarily need any assistance. But thanks for all the offers!
If I have any questions / requests I'll sure to let everyone know!
Thanks!

The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?

furysama said:
The only other question i have is this: how difficult is it to integrate Samsung's 4g drivers into an AOSP mod? Now, I know if we wanted to keep it 100% AOSP it would be... difficult. But is it possible to run a 90% AOSP mod, and just keep the drivers for 4G in the AOSP kernel?
Click to expand...
Click to collapse
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel

daryelv said:
Very very difficult considering it took a team of developers a few months on the EVO to get 4G working with a AOSP kernel. I guess it will depend on how Samsung releases the code, they'll probably not release the 4g code because it doesn't fall under the GPL. If they were to release the drivers as modules that could be included in a kernel, that would be great, but I doubt they'd do that either.
In other words... don't hold your breath...
-Daryel
Click to expand...
Click to collapse
The reason it took the CM team so long is because they developed their own drivers from the ground up. I'm willing to bet that it's much easier to rip the drivers out of the kernel we already have than to replicate the work that the CM team did.
The GPL licensing is *why* the CM team developed their own drivers; not because its impossible to get Samsung's code, but because doing so would have violated the licensing terms of Samsung's code and of Cyanogenmod.

[Q] Where's Source?

Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.

Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix

Kid_Cudi said:
Gingerbread? Or Froyo? Cuz Froyo been out...
Thunderbolt «» das BAMF Remix
Click to expand...
Click to collapse
I like Kid Cudi as well first of all.
What I mean is and I'm probably not going to use the right term here but the RIL or perhaps SDK.. Bear with me here I'm good at trouble shooting stuff but not programming.
I was googling it didn't help me get the right term lol. Chime in who ever knows what the hell I'm talking about here lol.

The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.

ProTekk said:
The kernel source itself has been out for quite some time. We will never see the "source" for the RIL (Radio Interface Layer) because it is proprietary on both HTC and Qualcomm's side. That's about as simple as it gets.
Click to expand...
Click to collapse
Yeah I think it's RIL. It's what the Cookers keep stating they're waiting for to finish their ROMs like CM7 for instance. The developer for it states that he's waiting for RIL to be able to officially finish his work. We really need to get this released from HTC so we can fix some of the issues people are having with CM7 and the leak for GB. I went back to Froyo because of the issues the leaks having with charging etc..

thewebsiteisdown said:
Any word from any one on when the devlopers will get the source code for this phone? I realize that this will help everyone developer wise get a better handle on kernels and greatly help the community.
I went back to GB for a second there but the charging issues have gotten out of control with the kernels which is why I'm starting to wonder when the sourrce will be released. We obviously need it to make further advancement with the community ROMs at this point.
I also seen where HTC said that they will unlock their bootloaders here soon.
Thanks for any one who contributes to this conversation.
Click to expand...
Click to collapse
HTC and google do not have to release any of the android source if they don't want to because the source (NOT THE KERNEL) uses the apache license, which is very permissive like the BSD/MIT licenses. It lets you use any code additions you make to the source for commercial projects without having to give it back unless you choose to http://en.wikipedia.org/wiki/Apache_license. This is why google doesnt have to release the Honeycomb source as long as they didn't make any additions/modifications to the kernel itself.
Google went through lots of effort as well to make sure they would not be bound by the GPL by writing their own clibs based off of code from various BSD ports. See here for an interesting article on some of the low level features of android (it's a bit old, but most of it is still relevant). http://codingrelic.geekhold.com/2008/11/six-million-dollar-libc.html
The kernel (like all linux kernels) is GPL and must be released.

RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.

miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I think there is a misunderstanding here. The RIL from Slayher is not the same as the RIL from HTC/Qualcomm.
Slayher will merge his "source" into the public CyanogenMod repo once he deems it's ready.
On the other hand, the "source" from HTC/Qualcomm is a whole different subject. We won't be getting a drop of it from them. Not now, not ever.

miketoasty said:
RIL will be released when it is finished. Slayher is working hard as hell on it. Not saying anyone is under appreciating just give the man some time and soon we will all have MIUI and CM7 running flawlessly on our devices.
Click to expand...
Click to collapse
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.

thewebsiteisdown said:
I deffinately appreciate all the hard work. I just thought that HTC had to release this info. I didn't know that Slayher or any other coder could just reverse engineer it.
Click to expand...
Click to collapse
No the RIL source and Sense source run under the apache license which states that the software developer can use the open source code but does NOT have to repost anything he or she produces.
So it is up to our dev's to do that and make it readily available.

Ics kernel

As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA

anoymonos said:
As far as kernels for ICS if Samsung releases source code for kernel does it have to be solely for our device or can it be (ported so to speak) from another device as long as it's a samsung
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!

Well I just read that samsung has released source for ICS kernel for the new Note just wondering if this can be used for our device. Also I read this from engagement.com source was from Open Source Market
Sent from my SGH-T959V using XDA

Ok I am personally going to start a new trend of not talking about ICS, CM9, or heck even Jelly Bean. If I can see that the Devs are starting to get annoyed with the constant onslaught of ICS, CM9, and CM7 questions and soon next month if it is released Jelly Bean. I guess if you can't help Develop, then you really have absolutely no place to complain about how long things are taking this is not a "customer Service" situation. Devs are here because they want to improve their own phones, or this is their hobby. They are not here to develop you a product. That's what Samsung is for in our case. If you are honestly angry about how long it is taking for us to get ICS then write T-mobile and Samsung not the Devs here that are spending their free time in order to eventually bring these awesome ROMS to our phones. Since I joined a year ago I watched Devs and entire teams leave (when is the last time you saw a Team Whiskey ROM?)So I for one am going to Back off on all the ICS business and let the Devs do their thing Without Having to stop constantly and answer the same questions over and over again. We have limited Devs that can at any sell off their SGS4g's and say "screw this" and move on to another phone. Guys seriously instead of constantly asking the Devs lets try something new ( or old to some of us) and ask Google, Yahoo, Ask.com, and or any other search engine you so choose and let the Devs concentrate on Developing.

One day people will learn how to ignore annoying posts. One day..........

i say "TEAM WHISKEY ROM" haha. lol

airfluip1 said:
i say "TEAM WHISKEY ROM" haha. lol
Click to expand...
Click to collapse
LOL thanx I didn't even see the typo, fixed it

thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Sent from my BAMF SGH-T959V!
Click to expand...
Click to collapse
Lol thanks thomas

thomas.raines said:
Team kick ass is working on it (mostly Erik)... Be patient...
Click to expand...
Click to collapse
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol

hechoen said:
I go away for a few days and now we're working on an ICS kernel. I should go away more often. lol
Click to expand...
Click to collapse
now that's comedy! !

My question had still not been answered a
Sent from my SGH-T959V using XDA

The answer( as I have come to understand, but I maybe wrong) is well parts can but for the most part the linux kernel is the part of the OS that houses all the device, and processor specific drivers. To make matters worse is some of those drivers are also OS specific. meaning Froyo versions won't work with a Ginger bread distro and so on. To port an Android distro you have one of two choices to make it work. Recompile some or all of the libs to work with the older kernel. Or create a kernel from scratch by finding other devices the have the same hardware that have been upgraded to ICS. Often many devices have pieces of the same hardware as your phone. Sometimes it takes scouring different phones to find phones that share pieces of your hardware.
Sent from my SGH-T959V

@ bot42
You are precisely correct. We at Team Kick Ass have found a way to do just that. Unfortunately, it is a very time consuming process as we have to pull many of the information, files, and things from source. I said this once and I will say it agian. Everything is in the process of being worked on. Please be patient.

Thanks sorry if I sounded rude but all the comments that were posted were way off topic that's all I'm in no hurry for ics just seen that Samsung released source for it was trying to be helpful
Sent from my SGH-T959V using XDA

it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.

airfluip1 said:
it's taking me forever to properly port voodoo sound into CM7. Precisely as thomas and bot said. If it takes so long to properly port a little thing, think about how long it's gonna take to port a whole kernel.
Click to expand...
Click to collapse
Yep to port a feature from one device to the next is hard a kernel/whole rom requires a lot of time and that is where my free time is being spent between reading and trying a lot of stuff

So, there are two efforts going on.
The first is what TeamKickAss is working on. I haven't seen what they are doing or any plans posted.
The second is what I'm working on over in the aosp port thread.
This port is a little more ambitious to port to three different versions.
first port sgs4g specific parts to android-samsung-2.6.35-gingerbread
then port that set of changes to android-samsung-3.0-ics branch (both branches originate from the upstream aosp samsung kernel)
the last port I will do will be to Linus's tree at whatever version it is when I get to this step.
So in the end, we'll have:
a stock kj6 kernel
the various kernels that forked from my bml and mtd kernels
aosp gb port
a couple ics kernel ports (one by teamacid, and one by teamkickass)
3.6 kernel port(or maybe 3.7)?
So, there is a peek in the crystal ball I have.
The future's so bright, gotta wear shades

Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium

i bet kickass can port it within a few days of an ICS kernel, but ports aren't always the most reliable/stable/fast. It'd be easier just to build from source. That way, we'd have a stable rom, and easier bug fixing.

itzik2sh said:
Hi Bryan
Wassup?
I have a friend with SGS i9000, (which didn't get official ICS) nevertheless he installed an ICS 4.04 AOSP ROM on it, working flawlessly.
So my question is, once kernel port will reach its purpose, will we be able to successfully port such ROM ? (PS. I downloaded that ROM and saw some MTD_over_BML stuff inside)
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Yea, with so many developers on teamhacksung... they can WORK TOGETHER and port their Aries kernel to any Aries phone. Our phone is kinda funky and we have very few developers.
Sent from my SAMSUNG-SGH-I717 using xda premium

AO[S|K]P ROM development life cycle question

Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks

basically a rom is never really finished.
theres always something to be ironed out or a bug that needs to be squashed. or sometimes its just enhancements,
but yea like you said until htc releases the source then stuff wont be 100%

Even when they do release the sources, there's still lots of things that potentially might not work.
Like take for example CM9 (ICS based) - although there are kernel sources out already for HTC's ICS, a bunch of things are not yet working. You can blame that on closed-source drivers, like wifi or camera, etc.
So it might take a while for everything to work properly, but as long as we have dedicated developers like xkonni, intervigil, etc, there's nothing to be worried about.
Sent from my HTC One S using xda premium

Nice thanks guys that makes sense. I just assumed that things like drivers could be poached and reused but I guess a lit of that is part of the sense framework.
I look forward to seeing what happens
Sent from my HTC One S using xda app-developers app

dillinga said:
Hi Guys,
I'm very new to this scene and have already started experimenting with ROMS (running Leedroid at the moment). I've just had a quick play with Coldblooded CM10 and love it but I'm intrigued about the current 'broken list'.
Is this just the way it goes with ROM Development on a new device that it goes through multiple iterations until the dev engineers a fix to all the issues? Does it make any difference when HTC for example eventually release the kernel source (which I assume they will once the official JB release comes out). I'm guessing stuff like the headphone issue/in-call echo will be 'fixed' in the official release from HTC so could be implemented in existing ROMs?
Hope that makes sense and I haven't just broken a load of noob xda rules....
Thanks
Click to expand...
Click to collapse
No worries man this was a very legit question.