Why is it difficult to get CM7 on SGS phones if Samsung doesn't lock bootloader ?
Was going to post in QA, but I think this question might be better suited in dev section. Feel free to move if needed.
StDevious said:
Why is it difficult to get CM7 on SGS phones if Samsung doesn't lock bootloader ?
Was going to post in QA, but I think this question might be better suited in dev section. Feel free to move if needed.
Click to expand...
Click to collapse
I think its cuz the drivers are proprietery but I know for sure its cuz Samsung jumbles up the source code so it makes it harder to combine the cm7 code with the Samsung code
Sent from my SCH-I500 using XDA App
I've wondered the same thing.. perhaps has something to do with the framework? Still no 'official' leak of the Gingerbread source for the Samsung Fascinate.. maybe someone can fill us in?
It has nothing to do with the bootloader. All an unlocked bootloader does is allows you to install custom ROMs and kernels without having to use elaborate workarounds like they use for the Droid X (and even then, there's no way to install custom kernels). The problem, as stated before, is with the proprietary code Samsung uses for its device drivers.
Incidentally, all questions belong in the Q&A section, even those having to do with development. The Development section is for posting ROMs, kernels, and mods, along with the occasional step-by-step guide.
Another Fascinating post by my XDA app...
jbarcus81 said:
I've wondered the same thing.. perhaps has something to do with the framework? Still no 'official' leak of the Gingerbread source for the Samsung Fascinate.. maybe someone can fill us in?
Click to expand...
Click to collapse
Well, considering that cm7 is gingerbread and that means .35 kernels (GB kernels). And our current functioning cm7's are using hacked. 32 kernels (froyo kernels), I'm amazed any of it functions. Jt and kaos have done an amazing job combining something that wasn't supposed to be together.
Sent from my SCH-I500 using Tapatalk
jmcintire said:
It has nothing to do with the bootloader. All an unlocked bootloader does is allows you to install custom ROMs and kernels without having to use elaborate workarounds like they use for the Droid X (and even then, there's no way to install custom kernels). The problem, as stated before, is with the proprietary code Samsung uses for its device drivers.
Incidentally, all questions belong in the Q&A section, even those having to do with development. The Development section is for posting ROMs, kernels, and mods, along with the occasional step-by-step guide.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
As others have said, it's Samsung's proprietary code and stuff. But I have a question for you? Is that the case with the Galaxy S2 as well? I know they didn't use their proprietary RFS file system, is it the same with everything else?
GoogleAndroid said:
As others have said, it's Samsung's proprietary code and stuff. But I have a question for you? Is that the case with the Galaxy S2 as well? I know they didn't use their proprietary RFS file system, is it the same with everything else?
Click to expand...
Click to collapse
If you jump on over to the Galaxy S II Android Development forum and scroll down far enough, you'll find a thread for an AOSP ROM. In the OP you'll find a very familiar list of things that don't work. That tells me that Samsung has still not repented of its wayward ways and is still using proprietary code for its device drivers.
Another Fascinating post by my XDA app...
jmcintire said:
If you jump on over to the Galaxy S II Android Development forum and scroll down far enough, you'll find a thread for an AOSP ROM. In the OP you'll find a very familiar list of things that don't work. That tells me that Samsung has still not repented of its wayward ways and is still using proprietary code for its device drivers.
Another Fascinating post by my XDA app...
Click to expand...
Click to collapse
All OEM manufacturers use proprietary code, even HTC does. What really matters is how much did they change from the stock AOSP code, and how easy is it to reverse engineer the stuff that they did change that is needed. Samsung made a lot of stupid changes in our AOSP code that are unique to the Fascinate (like padding data) which makes trying to get AOSP working that much harder.
Related
I'd really like to get the Galaxy S2, but not without Cyanogen Mod support. What do you think are the chances that the Galaxy S2 will get CM? The Galaxy S still has no stable CM Rom.
Does a bear **** in the woods?
Sent from my HTC Desire using XDA Premium App
Polar bears don't.
But why doesn't the Galaxy S have a stable CM ROM then?
Stock Media Codecs > CM
if they find a way to keep all the goodies from Samsung then I'm all for it
Frankly, I don't care about the Samsung programmes. If it can be turned off, then ok, but I'd rather have the whole CM experience.
This hardly seems like the right forum for this thread...
So what's the right forum, if not the Galaxy S II Android Development Forum?
Android Development should only contain threads based on actual projects/ROMs/kernels/etc being developed. Discussions about what may or may not be coming to the device should go in general. Best rule of thumb in my book: if you're not actually developing something yourself, a thread shouldn't be started here.
Sorry if I came off like a prick - I just know that this ends up becoming more work for the mods who have to comb through and move threads around.
Also I apologize for theoretically hijacking your thread - Just trying to help keep people in the know
hopefully it will get CM
i really cant stand touchwiz
slyydrr said:
Android Development should only contain threads based on actual projects/ROMs/kernels/etc being developed. Discussions about what may or may not be coming to the device should go in general. Best rule of thumb in my book: if you're not actually developing something yourself, a thread shouldn't be started here.
Sorry if I came off like a prick - I just know that this ends up becoming more work for the mods who have to comb through and move threads around.
Also I apologize for theoretically hijacking your thread - Just trying to help keep people in the know
Click to expand...
Click to collapse
No problem, I didn't know that.
Maybe a moderator can move the thread into the appropriate forum.
What I really like to know is why the Galaxy S still hasn't got a stable release. Is this also to be expected with the S2?
slyydrr said:
Android Development should only contain threads based on actual projects/ROMs/kernels/etc being developed. Discussions about what may or may not be coming to the device should go in general. Best rule of thumb in my book: if you're not actually developing something yourself, a thread shouldn't be started here.
Sorry if I came off like a prick - I just know that this ends up becoming more work for the mods who have to comb through and move threads around.
Also I apologize for theoretically hijacking your thread - Just trying to help keep people in the know
Click to expand...
Click to collapse
I agree. Good post, and yes, this should have been in General. Just keep that in mind for the next time We are all excited for this phone, and i personally think that Samsung stock ROM is also quite good. However, to each his own, and I am sure that CM will be out for this phone too
Cheers!
ro-mann said:
No problem, I didn't know that.
Maybe a moderator can move the thread into the appropriate forum.
What I really like to know is why the Galaxy S still hasn't got a stable release. Is this also to be expected with the S2?
Click to expand...
Click to collapse
Moved to general
The SGS2 is similar to the SGS in many ways, therefore CM will be difficult to port over.
Especially that there is no Nexus S 2 (a lot of CM7 is from the Nexus S)
Don't expect CM7+ to be running on the SGS2 anytime soon, although it probably eventually will. That's unless anything else happen (a/a genius comes along b/samsung open source more stuff c/Nexus S 2 is released d/sgs2 shares even more with the sgs than I though and current work can be ported over more easily)
This phone is fast enough without CM7. A clean up of the stock ROM, a new launcher and its sweet enough!
Sent from my GT-I9100 using XDA App
risq said:
This phone is fast enough without CM7. A clean up of the stock ROM, a new launcher and its sweet enough!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
It will still miss the CM Tweaks.
A shame that Cyanogen has chosen the G2x as his next phone. The Galaxy S2 is way better than the G2x.
bilboa1 said:
The SGS2 is similar to the SGS in many ways, therefore CM will be difficult to port over.
Especially that there is no Nexus S 2 (a lot of CM7 is from the Nexus S)
Don't expect CM7+ to be running on the SGS2 anytime soon, although it probably eventually will. That's unless anything else happen (a/a genius comes along b/samsung open source more stuff c/Nexus S 2 is released d/sgs2 shares even more with the sgs than I though and current work can be ported over more easily)
Click to expand...
Click to collapse
i'm not aware of the history, why exactly was it difficult to bring cyanogen to the original galaxy s, and hence this SGS2 as well? wasnt it like any other phone, the source was released, and cm team built from that?
RogerPodacter said:
i'm not aware of the history, why exactly was it difficult to bring cyanogen to the original galaxy s, and hence this SGS2 as well? wasnt it like any other phone, the source was released, and cm team built from that?
Click to expand...
Click to collapse
Open-source drivers are hard to find. The system is open source but the drivers are not.
amtrakcn said:
Open-source drivers are hard to find. The system is open source but the drivers are not.
Click to expand...
Click to collapse
Isn't this the case with any other phone?
But why doesn't the Galaxy S have a stable CM ROM then?
Buy the devs a SGS 2 and they can work on it . Bit hard to work on a phone you dont have .
jje
Well, apparently they have a Galaxy S, otherwise there wouldn't be Release Candidates.
I am considering buying the SGS2 very soon. I am going to root it but here is my question. If I wait to get pushed the ATT update to 4.0 ICS do I have to flash back to stock just to root it? I want to wait for the stock push of 4.0 and just wipe off the bloatware and not have to worry about custom ROMs etc. Thanks for the help.
Currently running captivate with cognition 4.5.3 froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
Re: Root sgs2 after ATT update to ICS
Sent from my SAMSUNG-SGH-I897 using XDA App
You should be able to root after the update. But we don't know yet for sure.
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Just wait for a Rom to be made , im sure one will be as soon as the sources are avail... I stopped doing the Ota upgrades when i realized its easier to just change the Rom.... So root... imo
Entropy512 said:
Way too early to tell. You aren't going to see an official AT&T ICS OTA update for many months - if the Captivate is any indicator, not for at least a year.
Click to expand...
Click to collapse
I'm hoping ATT/Samsung push it sooner because it's still one of ATT's highest end phones.
Of course, this is just wishful thinking.
Sent from my A500 using xda premium
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
votinh said:
Reading this thread, suddenly triggering me asking this question, I don't know why I haven't asked before: is there any ongoing development for ICS ROM?
I assume most of the custom ROMs surface in here are Gingerbread based OS.
Click to expand...
Click to collapse
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
There is development
Sent from my SGH-I777 using XDA App
eep2378 said:
No source for ics yet so there is no development. Look in general forum there is a sticky talking about it. There is also Cm9 but it's not fully working yet on our device.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
votinh said:
Google did release ICS source codes about a month ago, I'm sure you know that.
Alright, so only CM dev. team currently working on this then.
Thanks
Click to expand...
Click to collapse
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Entropy512 said:
That's base platform source for Nexus devices with not a single bit of source for anything specific to the I9100 or I777.
Click to expand...
Click to collapse
Did i ever mention about Nexus devices which running ICS, ehhh?
You really need to educate yourself on what source has and has not been released, and what that source means and is used for, before posting crap like this.
Click to expand...
Click to collapse
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Basically, I could spend a few hundred hours trying to port the 2.6.35.x drivers for Samsung-specific items to a vanilla Linux 3.0 kernel - only to have a halfassed buggy release ready after Samsung releases official ICS with kernel source for the I9100, which can be ported to the I777 in a matter of a few hours of work.
Click to expand...
Click to collapse
Are you the one who create Entropy512 DD kernel? If yes, every minute you spent is well appreciated, left alone a few hundred of hours.
If so, yes, you seem to be very smart in Android field but in life, learn to grow up and act nicely, politely to others. Get some love, kiddo.
The CM dev team is not working on ICS for the I777 either - to get anything even working on the I9100 they had to resort to something they almost NEVER do, which is an initramfs repack of a binary kernel. Getting an I9100 binary kernel to work properly on an I777 is simply not possible - you can repack the initramfs all you want, the audio routing code will be different and so will the touchkey mapping code.
Click to expand...
Click to collapse
Again, I don't know who is working on what so I asked. One of the poster mentioned about CM, so I just repeat it.
If they currently do it, great.
If they currently do not do it, it's ok.
I am just asking, 'cuz in B&N NOOKcolor forum, a lot of XDA dev. is WORKING on ICS ROM from ICS source code that released a while a go.
I thought XDA dev. in this room will also do the same.
The only ICS development that will occur on the I777 prior to I9100 kernel source getting released (or an I777-specific leak showing up) is some basic reverse engineering efforts (mainly focused in audio routing), since the library swap Hellraiser uses can't be done with ICS (depends on audio blobs extracted from an I777 device.)
Click to expand...
Click to collapse
Good too know.
I've learnt something.
Thanks
votinh said:
Did i ever mention about Nexus devices which running ICS, ehhh?
Wowww!!!
Just posted once sentence and being tagged with "crap like this"? LOL
By reading my English, do you understand that I just said Google has released ICS source codes? Did you see I am saying Google has released ICS source codes for I9100 or this specific i777, huh? Did you read and understand or just premature assumption?
Or you are telling me that you never know Google has release ICS source code?
Click to expand...
Click to collapse
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Entropy512 said:
Another poster said we were waiting for source.
You replied to him saying Google posted source over a month ago. Thus implying that you thought that Nexus platform source would actually be sufficient on its own to get our device running ICS - it isn't, it's nowhere close.
I'm sick and tired of repeated "WHERE'S ICS? GOOGLE POSTED SOURCE OVER A MONTH AGO!" posts.
Click to expand...
Click to collapse
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
votinh said:
"Another poster" I assume you meant "eep2378, one that posted right above my "crappy post"?
Firstly, if eep not getting itchy, why you?
Secondly, I don't know what he meant about ICS for Nexus, and even if he meant that, he didn't spell out so I thought he meant the general ICS source code. In his next sentence, he actually mentioned about CM team working on it, even not fully function, w/o waiting for this specific phone ICS source code, so I thought he meant they, CM team are using the general source code, just like XDA dev. in B&N NOOKcolor room.
Thirdly, and if eep irritated about my post, I apologize him.
Now back to you, let's square and clear up all confuse, hardness.
You're a talented kid, good, keep it up. If you know something, teach us, I'm sure a lot of others will learn from you and quietly appreciate.
Be socialize with people around you, in real life or in cyber.
To the ICS related questions, if you don't want to answer, DO NOT answer, there's no one forces you to do so. There is no point to irritate about it.
Click to expand...
Click to collapse
Ok let me try to clear up some confusion:
1) Nexus source code has nothing to do with I9100 or I777
2) I didn't mention anything about ICS for Nexus because(see #1) and this is the I777 forum NOT Nexus(another reason why I didn't mention it)
3)I mentioned CM9 because(RIGHT NOW) its the only thing that even approaches getting ICS on I9100 forget the I777. And Even Codeworkx(OP for CM9 aka Dev) is WAITING for ICS SOURCE to drop FOR THE I9100.
Only then, as Entropy said, are we able to get it working on the I777
4)I'm not "itchy" or irritated in the least and there is no need for an apology. Having said that I am fairly tired of reading posts about ICS source code being dropped/when are we getting ICS?/ Can ICS run on my I777?, etc.
Finally, ICS source code dropped FOR THE GALAXY NEXUS!! What does that mean for us?? SEE #1!!
@Entropy, I responded to you in another thread(in Q&A) Porting Bezke ICS KP8(yeah I know another one lol) regarding comments you made on Captivate and I9000 kernels being similar but I9100 and I777 not sharing the same similarities.
I'm sure you never went back to that thread, but didn't want bother you via pm
---------- Post added at 04:01 PM ---------- Previous post was at 03:44 PM ----------
Nick281051 said:
There is development
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
For the I777? Where?
I don't want to sound ignorant, but Samsung always releases the kernel source along with the ROM?
I've read on the sammobile twitter page that there is a new Kernel for the S2. Developers are pretty happy and exstatic, I actually never thought about it,
But wat is a Kernel and what does it do?
You will likely get massively flamed for asking, but you learn by asking. The kernel is essentially the bridge between hardware and software, if you want the hardware to do something (light up the touch buttons at the bottom of the phone for example), Android must run the request through the kernel, which duly lights up the buttons.
Now, devs are so excited because a lot of the code to manipulate SGS2 hardware is proprietary, I.e. written specifically for this phone by Samsung, so its been difficult to do things with the hardware. Now Samsung have released the sources, it makes it possible for devs to use the hardware properly, so a fully working custom ROM with all the hardware working can now be made.
Sent from my GT-I9100 using XDA
TheReverend210 said:
You will likely get massively flamed for asking, but you learn by asking. The kernel is essentially the bridge between hardware and software, if you want the hardware to do something (light up the touch buttons at the bottom of the phone for example), Android must run the request through the kernel, which duly lights up the buttons.
Now, devs are so excited because a lot of the code to manipulate SGS2 hardware is proprietary, I.e. written specifically for this phone by Samsung, so its been difficult to do things with the hardware. Now Samsung have released the sources, it makes it possible for devs to use the hardware properly, so a fully working custom ROM with all the hardware working can now be made.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Alright! Thank you for answering my question, I finally know what it means and the Q&A section in XDA for me is a good source for answers.
Thnx!
L A X said:
Alright! Thank you for answering my question, I finally know what it means and the Q&A section in XDA for me is a good source for answers.
Click to expand...
Click to collapse
So are FAQs and stickies.
Hello I'm a newb!
I'm sorry, but this is the unfortunate state I find myself in.
When I first found this site, what I was expecting to find was a ICS for my phone. I could not have guessed what I would learn here. I had no idea I had a counter in my phone to worry about when installing open sourced roms? Next after much more reading I am to learn the source code Google releases is not complete, and uses binary drivers? Now I am to learn about CIQ, and my phone is spying on me? Wow!
Before I say anything else I want to express my thanks to this community. This has been such a resource I had no idea that it would be when I started. Thank you!
Now on to my question that after learning about all of that I don't seem to have a clear answer to. What I wanted when I first considered getting an Android phone, was to build from source, and run my own rom. I still want this, even more so since I learned about CIQ.
1. Due to the counter on my phone
2. I am to understand multiple images that make the phone work (boot, firmware, system)
3. The binary drivers.
Is this at all a reasonable goal?
Are there more flash images that I haven't read about yet?
Would having a direct from Google rom even be desirable?
I own a stock SGH-I777, I have done nothing to it yet.
Lastly about this site:
Is there anything you think I should read about on the forums?
Any language I should know, as in what does hellraiser imply/mean?
Any Android experience you think might benefit a could be developer?
Counter can be reset and avoided all together.
Sorry I don't know much about AOSP building, but your better off starting with compiling CM and learn from there unless you are really experienced in coding.
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source. Ty for reminding me.
NEME5I5 said:
Speaking of, the image used to not increment the counter does, or does not still contain CIQ? I suspect it does? I would like a phone at some point w/o CIQ, and fully open source.
Click to expand...
Click to collapse
AT&T Galaxy S2 SGH-I777 has never had CIQ.
LiLChris06 said:
AT&T Galaxy S2 SGH-I777 has never had CIQ.
Click to expand...
Click to collapse
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
NEME5I5 said:
I'm shocked AT&T choose not to bug their customers? I assumed since I saw mention of it being on Samsung, that it was on all their phones?
Click to expand...
Click to collapse
No it was just some phones, I think the skyrocket had it at some point.
Sent from my SGH-I777 using Tapatalk 2 Beta-5
Ok, so I rooted my first cell phone. It would seem heimdall latest has a bug that will brick your phone. (I'm on Mac OS Lion) I used the 1.3.1 instead, and it worked fine.
I saw many more sites, and this was quite easy. The way they showed it was very complex. Since I'm new at this should I wait to try out a ICS rom till after Samsung releases their source code, and the devs have had a chance to get it stable? How complete is the open source version of ICS? There was a note on the fsf.org page that linked me over here that some of the parts were still binary. Is it still true?
I think long term I want to get away from the official releases.
Well, you came this far, might as well flash an ICS rom now. If the leaks are any indication of status, the Samsung release will be pretty stable but the included kernel is problematic because it can cause hardbricking. Besides, you want to get away from stock, and all of the big roms released thus far are pretty darn stable; I don't know anything about binary parts or any of the coding, but plenty of people have no problem running CM or AOKP. Even the Samsung-based roms all look AOSP-like nowadays because they use Apex or Nova (not many devs like Touchwiz anymore). So take your pick, they're all good roms and most look like AOSP to some extent, with a few (mainly CM and AOKP) striving for pure AOSP.
Make sure to read and follow this guide carefully for flashing stuff, and have fun!
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
NEME5I5 said:
Ok here is where I have a problem. I have no idea about half of what you said? I know AOSP means "Android open source project" by inference of another reply. I even think CWM means "clockwork mod." (don't even know what this is yet) Saw a youtube video that mentioned it.
What is hard bricking, and what should I read to prevent it? I came here for a ICS rom, and it sounds like the two trying to be most open source are my preference.
Click to expand...
Click to collapse
Prother, by no mean to offense you, but seriously, if you don't know those fundamental technical terms, I strongly suggest you to hold off what you about to do and spend more time reading.
Let me go off and do a search the post for you, where you can get used to those terms.
Hang tight, prother.
Pirateghost said:
Read, read, and read some more. If you don't understand the post above then there is no way you would be able to compile a rom for this phone, which is what I gathered from your op
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
So I will. To be honest I don't see the connection between the new jargon, and development I learn in school. There is definately much to learn here. I was expecting this to be like Zaurus development from back when I was active, it's very clear to me that this is a very different beast.
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
votinh said:
Here is one, I'm sure there is other thread.
http://forum.xda-developers.com/showthread.php?t=1466228&highlight=abbreviation
Click to expand...
Click to collapse
Thank you friend. I may not have my own rom at the end of summer, but I should be on my way to understanding what would be needed for one.
Well the terms I wanted are not present on that list, most of that I was familiar with. To be honest, some of it I have not seen before as well. What is hellraiser, and some of the other xda developed jargon? I do have a tab open to that part of the forums, I just hadn't made it over there yet. I started on the forums for my device, then Android OS, and lastly general. Is there any other place I should pay special attention to that would help me?
Phalanx7621 said:
Yeh. Just give me the new thing! I want that shiny biscuit! Zomg! "Check MY device out. Its got AOKP on it. BAM.". "Oh cool how does that work?". "Pfft who cares. Its shiny!!!"
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Ok? I'm not sure I understand, is there something you don't like about the aokp rom that doesn't work very well?
I want off of the carrier provided images based on personal conviction. Google's development practices smack of cathedral, as do all of the 3rd party companies. In a sense they are abusing the spirit of free software by using a signed kernel to impede (if not actually prevent) our right to modify hardware we own. Any normal user of the software provided by the community (bazaar) can only help the cause.
I plan to share what I personally learn with close friends who live in my area. The more people we liberate, the better for everyone else. I simply applaud the work done here.
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
karate104 said:
You can safely ignore Phalanx's post, he's just mocking you and other new users for not reading carefully and being stupid. You're at least trying to read and understand stuff, so I don't see any reason you should be put down the way he's doing so.
Here are a couple other links I think you'll find useful (please click my thanks button if you agree!):
ROM vs Kernel
Odex vs Deodex
Make sure to read all of the links posted in the sticky at the top of this forum, too. But note that by no means is this everything you need to read.
Mind you, all this reading is meant mostly for end-users, so that we learn how to safely and smartly modify our phones. Actual original developing beyond using what's already provided by the devs is a whole different story, and I'm sure there's even more to read up on that.
Good luck, happy flashing, and if you plan to develop later down the line, good luck with that too!
Click to expand...
Click to collapse
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
From a relative noob:
Follow the directions in the " [GUIDE] How to Flash Custom Binaries Without Ever Incrementing the Flash Counter!! " thread. Then pick a rom you want to try and follow the CWM directions ... after that , find a ROM you like. If you don't want to void your warranty, wait for your carrier to provide the closest thing to what you want ... but, I'm happy with my flashed ICS ROM.
NEME5I5 said:
Ty for all your help. I'm glad you're all so thorough, it was like peeling an onion. The more I was looking at rooting my phone, the more there was to learn. All of you have done an amazing job making this approachable to a brand new user.
Ah I don't assume anymore about what people are trying to say, not everyone is a native english speaker. So I try to be understanding.
Yup I'll be at this for a while, I'm happy to have made some introductions, and maybe some time down the road I can even hope to contribute in some small way.
Click to expand...
Click to collapse
Just like everyone else has said. Read read read. Search for answers for your questions before you ask on forums. U will be fine as long as u can read and follow simple directions. Good luck to u. If u haven't flashed a rom yet I would recommend aokp. Awesome rom.
Sent from my SGH-I777 using XDA
Hi guys
I'm aware of CyanogenMod, but is it possible to have a completely stock JB ROM with no mods (other than busybox, deodexing, etc..) or custom apps installed? I can't seem to find one
Cheers
The community will correct me if I'm wrong, but I believe you'd have to build from source (AOSP) if you wanted something that is super-vanilla and hasn't been touched by a manufacturer outside of CM, AOKP, etc.
That said I also believe this particular question should be posted in the General or Q&A sections, for future reference.
djmatt604 said:
The community will correct me if I'm wrong, but I believe you'd have to build from source (AOSP) if you wanted something that is super-vanilla and hasn't been touched by a manufacturer outside of CM, AOKP, etc.
That said I also believe this particular question should be posted in the General or Q&A sections, for future reference.
Click to expand...
Click to collapse
Thanks for the reply
I mean Android was made to work on all devices right, but does CM do something like adding "drivers" (or the equivelent)? Is that what developers do when they "port" something like a new ROM that has been released on a similar device?
If multiple devices have a stock Android JB ROM, and they're also using a Tegra 2 CPU (and I'm guessing they all use the same type of RAM) etc.. is it quite easy to port? Do you have any idea how difficult it would be to compile it from source/getting it to run on a device?
I'm into technology, but without some serious research, I wouldn't have a clue where to start unfortunately
P.S. Yeah I realised after, already reported it to be moved
I've never ported between devices, but I've read enough to say confidently that things can be tough if you are porting between devices that are too different. At the very least you should stick between manufacturers...like it would be easier to port from Galaxy S2 Hercules to S2 Skyrocket for example than it would be from S2 to HTC xxx. There are quite a few good guides that explain how to port safely as long as the board configs and other important stuff are the same. If you aren't sure, don't do it.
For compiling from source, do a search on XDA here for shenye's guide "Compile JB on Ubuntu" - it was also featured on XDA TV. It's very helpful. Compiling isn't all that hard, but takes time and patience especially if you are working on a non-flagship device. It will likely take much research to find the right repositories for your device and vendor config, plus time to fix any errors the compiler reports.
Good luck!!