Hey all. I'm making this thread to compliment the other thread found in this subforum. I really didn't want to fragment the discussion, but it does make sense to split the discussions up into relevant threads, as porting AOSP vs TW is a different process. That, and I'm sure I'm not the only one who appreciates a little punctuation in their OPs . Joking aside, lets get down to brass tacks here. Since the LTE variants of the Note 2 all share similar hardware features, it doesn't take much to get ROMs developed for different carriers to work on our handsets. There has been experimentation with this for the last few months, spanning a dozen threads, and a general technique was hewn together based around Scrossler's patch. Most recently a sort of megathread was posted in this subforum detailing how to 'port' roms to our handset using Scott's patch. This method works pretty well in most cases, but definitely isn't perfect for a couple reasons. Firstly, Scott's patch really wasn't designed with this in mind. I haven't talked to the man himself, but he basically made it as a way to get stock international n7105 firmware to work on our domestic handsets, and as such is specifically geared towards Touchwiz compatibility. So for porting TW roms over, the patch works fairly well and we'll leave it at that. However, AOSP is a different beast. Scott's patch contains certain files that are irrelevant on aosp, and even complicate and break certain roms. The other major downside to trying to port with Scott's patch is that it flashes over his build.prop file, which is bad news bears on any rom that isnt stock touchwiz. So I've sought to refine the porting process a little, just for my own learning and fun, and I've been getting pm's about this so I figured I'd share what I've learned along the way. This is by no means a complete step by step tutorial, more or less a framework or stepping stone for you guys to start from. I can't guarantee this will work for every rom in every case, but it hasn't failed for me yet. As always, ymmv. Also I'm not claiming to be a developer or to know any magical secrets, I'm just another xda casual like you who just happened to do a little poking around for curiosity's sake. It's amazing what you can do when you're walking around with the entire collected knowledge of the human race in your pocket Anyways, meandering bull**** is over. I'm more or less pasting this in from my previous explanations, in plain text for humans to understand. Good luck and enjoy!
All you need to do is grab a working aosp rom for our device to use as a donor. Either of sbrissen's cyanogenmod roms will work beautifully, just use the version with the base closest to the rom you're porting. Open both roms as archives and first navigate to /system/app/. There are three apks found in the donor rom that start with vzw*. grab these and put them in your working rom. Next, navigate to /system/etc/ and copy the apns-conf.xml from the donor into your working rom, overwriting the original. Lastly, we need to edit the build.prop found in /system/ to correct all the cdma/lte references so the phone behaves in a way that verizon likes. This is the most involved step and the biggest source of error, but it's fairly straight forward when it's all said and done. Either open both build.props side by side, or better yet use a comparison tool to note the differences. Basically the build.prop can be broken into three sections, which you can figure out by the comments in the file. you can skip the first section just to be safe, but if you're really anal you can change all the hardware references from t0lte to t0ltevzw, and to SGH-I605 when necessary. Again, not something I recommend a beginner worry about and definitely not necessary for getting the port to work. The really crucial information starts after the line "# end build properties " and ends before "# ADDITIONAL BUILD PROPERTIES" Basically, everything that falls in this block is the RIL information that we need to get this stuff working. You can generally just copy the whole block from our donor and overwrite the whole section in our working rom, as most of it will end up being redundant if we leave it in. The best practice would be to go line for line and see what is applicable, basically all the lines referencing SIMs, RIL, radios, cdma, etc. are the lines that we want. After that, there is only one line in the last block of properties that needs changing, at least in the roms I've ported. This may differ depending on your source, but look for the line "ro.telephony.ril_class=". look carefully and compare it to the corresponding line in the donor rom, if your working rom says anything other than "SamsungCDMAQualcommRIL", change it to read as such. After that just save that file and you should be fine to flash, just be sure to flash a modem and have a kernel on hand in case the ported one doesn't play nice. Congratulations, hopefully you don't have a $700 paperweight in your hands, enjoy that goodness.
I might as well add that if you want to use this method to port TW roms in a more efficient manner, all you need in addition is Scott's patch, or a VZW TW rom. Patch over the secMMS.apk and SecPhone.apk to your working rom. Copy the /system/csc/ folder over to your rom. Finally copy CSCVersion and SW_configuration to your /system/ folder. Do all that in addition to my above steps and you should be golden.
First, why themes?
Second, you get any of your ideas from here? If so, better source.
http://forum.xda-developers.com/showthread.php?t=2069850
Sent from my SCH-I605 using Tapatalk 2
Themes, because the other porting thread is located in themes. I'm trying to avoid as much fragmentation as possible, I can't really call this android development in good conscience. I actually hadn't seen that thread, of course PureMotive can put things in way clearer terms than I. Great find, if my steps aren't obvious to anyone definitely check his thread out.
1ManWolfePack said:
First, why themes?
Second, you get any of your ideas from here? If so, better source.
http://forum.xda-developers.com/showthread.php?t=2069850
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I've been trying to port t-mobile, at&t, and sprint tw roms over to vzw. Not having much luck. Those are two very different methods. Im confused??
Jeff Zaugg said:
I've been trying to port t-mobile, at&t, and sprint tw roms over to vzw. Not having much luck. Those are two very different methods. Im confused??
Click to expand...
Click to collapse
Tw roms you could use the other method with scotts patch but it won't always work this method is for AOSP roms
JetBlue said:
Tw roms you could use the other method with scotts patch but it won't always work this method is for AOSP roms
Click to expand...
Click to collapse
Im talking about above in the op were he says at the end to do all he states above as well as the extra things at the bottom if your porting a tw rom vs the link in the second post that says to only change a couple things for a tw rom and your good. see why im confused?
I don't see this guide working very well at all.
Jeff Zaugg said:
Im talking about above in the op were he says at the end to do all he states above as well as the extra things at the bottom if your porting a tw rom vs the link in the second post that says to only change a couple things for a tw rom and your good. see why im confused?
Click to expand...
Click to collapse
If you're looking for a quick dirty fix, there's another thread in this sub forum that is all about porting TW roms I'm sure you've already seen. What specifically is giving you trouble? I'm definitely not claiming this guide as a panacea or anything, but it's worked for me without fail yet.
Actually think I found out the problem. Ive been trying to port a t-mobile rom called Killajoule v0.9. Its based on UVALK8. Apparently that base is not compatible with vzw.
Sent from my SCH-I605 using xda app-developers app
Jeff Zaugg said:
I've been trying to port t-mobile, at&t, and sprint tw roms over to vzw. Not having much luck. Those are two very different methods. Im confused??
Click to expand...
Click to collapse
I didn't post my link as a guide. I posted it as a reference to the OP, as some of his ideas appear to have derived from the link I posted. It could be pure coincidence, honestly. Not saying/implying the OP was being malicious, just wanted to make sure credit was given if credit was due, as PureMotive has done quite a bit for the community.
Sent from my SCH-I605 using Tapatalk 2
adrynalyne said:
I don't see this guide working very well at all.
Click to expand...
Click to collapse
If you can call it a guide. Looks like a giant, incomprehensible cluster of words to me.
Sent from my SCH-I605 using Tapatalk 2
broprah said:
Hey all. I'm making this thread to compliment the other thread found in this subforum. I really didn't want to fragment the discussion, but it does make sense to split the discussions up into relevant threads, as porting AOSP vs TW is a different process. That, and I'm sure I'm not the only one who appreciates a little punctuation in their OPs . Joking aside, lets get down to brass tacks here. Since the LTE variants of the Note 2 all share similar hardware features, it doesn't take much to get ROMs developed for different carriers to work on our handsets. There has been experimentation with this for the last few months, spanning a dozen threads, and a general technique was hewn together based around Scrossler's patch. Most recently a sort of megathread was posted in this subforum detailing how to 'port' roms to our handset using Scott's patch. This method works pretty well in most cases, but definitely isn't perfect for a couple reasons. Firstly, Scott's patch really wasn't designed with this in mind. I haven't talked to the man himself, but he basically made it as a way to get stock international n7105 firmware to work on our domestic handsets, and as such is specifically geared towards Touchwiz compatibility. So for porting TW roms over, the patch works fairly well and we'll leave it at that. However, AOSP is a different beast. Scott's patch contains certain files that are irrelevant on aosp, and even complicate and break certain roms. The other major downside to trying to port with Scott's patch is that it flashes over his build.prop file, which is bad news bears on any rom that isnt stock touchwiz. So I've sought to refine the porting process a little, just for my own learning and fun, and I've been getting pm's about this so I figured I'd share what I've learned along the way. This is by no means a complete step by step tutorial, more or less a framework or stepping stone for you guys to start from. I can't guarantee this will work for every rom in every case, but it hasn't failed for me yet. As always, ymmv. Also I'm not claiming to be a developer or to know any magical secrets, I'm just another xda casual like you who just happened to do a little poking around for curiosity's sake. It's amazing what you can do when you're walking around with the entire collected knowledge of the human race in your pocket Anyways, meandering bull**** is over. I'm more or less pasting this in from my previous explanations, in plain text for humans to understand. Good luck and enjoy!
All you need to do is grab a working aosp rom for our device to use as a donor. Either of sbrissen's cyanogenmod roms will work beautifully, just use the version with the base closest to the rom you're porting. Open both roms as archives and first navigate to /system/app/. There are three apks found in the donor rom that start with vzw*. grab these and put them in your working rom. Next, navigate to /system/etc/ and copy the apns-conf.xml from the donor into your working rom, overwriting the original. Lastly, we need to edit the build.prop found in /system/ to correct all the cdma/lte references so the phone behaves in a way that verizon likes. This is the most involved step and the biggest source of error, but it's fairly straight forward when it's all said and done. Either open both build.props side by side, or better yet use a comparison tool to note the differences. Basically the build.prop can be broken into three sections, which you can figure out by the comments in the file. you can skip the first section just to be safe, but if you're really anal you can change all the hardware references from t0lte to t0ltevzw, and to SGH-I605 when necessary. Again, not something I recommend a beginner worry about and definitely not necessary for getting the port to work. The really crucial information starts after the line "# end build properties " and ends before "# ADDITIONAL BUILD PROPERTIES" Basically, everything that falls in this block is the RIL information that we need to get this stuff working. You can generally just copy the whole block from our donor and overwrite the whole section in our working rom, as most of it will end up being redundant if we leave it in. The best practice would be to go line for line and see what is applicable, basically all the lines referencing SIMs, RIL, radios, cdma, etc. are the lines that we want. After that, there is only one line in the last block of properties that needs changing, at least in the roms I've ported. This may differ depending on your source, but look for the line "ro.telephony.ril_class=". look carefully and compare it to the corresponding line in the donor rom, if your working rom says anything other than "SamsungCDMAQualcommRIL", change it to read as such. After that just save that file and you should be fine to flash, just be sure to flash a modem and have a kernel on hand in case the ported one doesn't play nice. Congratulations, hopefully you don't have a $700 paperweight in your hands, enjoy that goodness.
I might as well add that if you want to use this method to port TW roms in a more efficient manner, all you need in addition is Scott's patch, or a VZW TW rom. Patch over the secMMS.apk and SecPhone.apk to your working rom. Copy the /system/csc/ folder over to your rom. Finally copy CSCVersion and SW_configuration to your /system/ folder. Do all that in addition to my above steps and you should be golden.
Click to expand...
Click to collapse
I do know you were taling about my thread in the beginning but w/e thank you for this it is very informative in helping what im trying to do. If some time in the future you would like to work together to make ports for the community id be happy to have you on board
I can't take it anymore thought I would help out
Hey all. I'm making this thread to compliment the other thread found in this subforum. I really didn't want to fragment the discussion, but it does make sense to split the discussions up into relevant threads, as porting AOSP vs TW is a different process. That, and I'm sure I'm not the only one who appreciates a little punctuation in their OPs .
Joking aside, lets get down to brass tacks here. Since the LTE variants of the Note 2 all share similar hardware features, it doesn't take much to get ROMs developed for different carriers to work on our handsets. There has been experimentation with this for the last few months, spanning a dozen threads, and a general technique was hewn together based around Scrossler's patch.
Most recently a sort of megathread was posted in this subforum detailing how to 'port' roms to our handset using Scott's patch. This method works pretty well in most cases, but definitely isn't perfect for a couple reasons.
Firstly, Scott's patch really wasn't designed with this in mind. I haven't talked to the man himself, but he basically made it as a way to get stock international n7105 firmware to work on our domestic handsets, and as such is specifically geared towards Touchwiz compatibility. So for porting TW roms over, the patch works fairly well and we'll leave it at that.
However, AOSP is a different beast. Scott's patch contains certain files that are irrelevant on aosp, and even complicate and break certain roms. The other major downside to trying to port with Scott's patch is that it flashes over his build.prop file, which is bad news bears on any rom that isnt stock touchwiz.
So I've sought to refine the porting process a little, just for my own learning and fun, and I've been getting pm's about this so I figured I'd share what I've learned along the way.
This is by no means a complete step by step tutorial, more or less a framework or stepping stone for you guys to start from. I can't guarantee this will work for every rom in every case, but it hasn't failed for me yet. As always, ymmv.
Also I'm not claiming to be a developer or to know any magical secrets, I'm just another xda casual like you who just happened to do a little poking around for curiosity's sake. It's amazing what you can do when you're walking around with the entire collected knowledge of the human race in your pocket
Anyways, meandering bull**** is over. I'm more or less pasting this in from my previous explanations, in plain text for humans to understand. Good luck and enjoy!
1. All you need to do is grab a working aosp rom for our device to use as a donor. Either of sbrissen's cyanogenmod roms will work beautifully, just use the version with the base closest to the rom you're porting.
2. Open both roms as archives and first navigate to /system/app/. There are three apks found in the donor rom that start with vzw*. grab these and put them in your working rom.
3. Next, navigate to /system/etc/ and copy the apns-conf.xml from the donor into your working rom, overwriting the original.
4. Lastly, we need to edit the build.prop found in /system/ to correct all the cdma/lte references so the phone behaves in a way that verizon likes. This is the most involved step and the biggest source of error, but it's fairly straight forward when it's all said and done. Either open both build.props side by side, or better yet use a comparison tool to note the differences. Basically the build.prop can be broken into three sections, which you can figure out by the comments in the file. you can skip the first section just to be safe, but if you're really anal you can change all the hardware references from t0lte to t0ltevzw, and to SGH-I605 when necessary.
Again, not something I recommend a beginner worry about and definitely not necessary for getting the port to work. The really crucial information starts after the line "# end build properties " and ends before "# ADDITIONAL BUILD PROPERTIES" Basically, everything that falls in this block is the RIL information that we need to get this stuff working. You can generally just copy the whole block from our donor and overwrite the whole section in our working rom, as most of it will end up being redundant if we leave it in. The best practice would be to go line for line and see what is applicable, basically all the lines referencing SIMs, RIL, radios, cdma, etc. are the lines that we want.
After that, there is only one line in the last block of properties that needs changing, at least in the roms I've ported. This may differ depending on your source, but look for the line "ro.telephony.ril_class=". look carefully and compare it to the corresponding line in the donor rom, if your working rom says anything other than "SamsungCDMAQualcommRIL", change it to read as such.
After that just save that file and you should be fine to flash, just be sure to flash a modem and have a kernel on hand in case the ported one doesn't play nice. Congratulations, hopefully you don't have a $700 paperweight in your hands, enjoy that goodness.
I might as well add that if you want to use this method to port TW roms in a more efficient manner, all you need in addition is Scott's patch, or a VZW TW rom. Patch over the secMMS.apk and SecPhone.apk to your working rom. Copy the /system/csc/ folder over to your rom. Finally copy CSCVersion and SW_configuration to your /system/ folder. Do all that in addition to my above steps and you should be golden.
Sent from my DARK Note 2
Related
So I thought there was a thread on this but I can't find it.
What is the actual behind the scenes difference in the Roms being put out besides theming?
I don't want a "this rom is better" answer, that's not what this is about. I don't want to disrespect anyones work, I am just curious as to what each team/person does different to post so many Roms. From the uneducated eye(mine) one would think you would post one Rom per team and then post the rest in the theme section.
They usually have the details on the first post, a lot of them explain what the variants are all about.
I am not totally up on the roms in the last week or so, But, all the roms will be using KA5,6 or 7 kernel and or KB1 (K=2011, A= Jan 5= 5th day etc.). That said some are structured to be faster removing some of the misc small routines, overclocked, or expanded memory. Some have as internal ram @ 300-310mb, some 335-340mb, some 350-360mb. Now, that may be important if you are gaming with the phone but, for most things not much change will be noticed if any. Some use Supercurio based, some use morfic based, some use Eugene based kernels or some just customized based on a bit of each or their own cooking.
The real crux is do ALL the things that are expected to work ,,,, work. E.G. Phone, WIFI, Bluetooth, Stereo, headphones, mp3-4 player, facebook, battery, twitter, mms, email, syncing, camera, both video and snapshot, GPS....etc. Now if All those are equal, then the theming and some of the other special touches are trademark of a given developer.
Some roms are just better structured and allow more altering than others, those would be the Axura, Einherjar roms and some of the Team Whiskey roms.
The reason why some will say this rom is great and that one I think has more to do with the date it was built. The problem with all the phones is the parts and sub assemblies are subbed out. So, July 2010 might work flawlessly for one rom but not the other and one phone made in Nov 2010 might be vice-versa
So, all the Long Winded diatribe above it comes down to this, it really is personal choice and the phone you have and how the custom rom works on that phone. The only real 2 differences I have seen with all the roms as distinct is the Axura has remarkable battery life and the rom has a great GPS fresh out of a new flash, other than that, I found no differences in anything else.
But remember that is just my studied observation from my 2 Vibrants.
dcontrol said:
They usually have the details on the first post, a lot of them explain what the variants are all about.
Click to expand...
Click to collapse
Yea, I guess i should further explain, this isn't to see which rom I want. I am not new to flashing so I have a general familiarity to all of them. I more just wanted to further my education on the actual behind the scenes aspects of these Roms and what the developers actually DO to make their Rom THEIR Rom besides custom themes.
To further your point though and also back up my question lets look at axuras change log. most of it consists of theme this or that update programs remove this or that. Then a tiny "framework tweak" "build.prop mod" is thrown in.
Specifically I was asking what do the devs do different in that area which I am assuming is the basis of the whole rom correct?
Also, I am not speaking of the miui or cm7 type ports but more of axura, bionix, trigger ect... all that are usually upgraded to the same kernals and modem in their roms anyway.
The purpose of this forum is for XDA members to post any ROMs they make, which are derived from existing Galaxy S II ROMs (within the scope of the rules). We listened to your feedback, in wanting to separate ROMs from derivative ROMs to avoid confusion and to protect the original creators (the chefs) of such ROMs, and to make it easier to find major developments.
This forum is for ROMs that aren't an original creation by you in terms of the underlying software, meaning, they've been either 1. developed with assistance from a kitchen or are 2. a re-skinning/re-themeing/minor adjustment of a particular ROM developed by someone else.
We welcome your derviative ROMs, as they give even more choice to XDA users. When you post in this forum, we ask that you be respectful of the original creator by following rule 12, particularly:
1. Linking back to the source ROM
2. Mention the creator of the ROM upon which your deriviative ROM is based.
Thank you for your cooperation
P.S. This is a bit of an experiment. Should it make sense, we'll roll it out to other forums on XDA.
Well, finally you can seperate the men from the boys... !! Nice thought..!!
Good idea, but how do I get to this ROM from the XDA app?
thanks
DT
d_train said:
Good idea, but how do I get to this ROM from the XDA app?
thanks
DT
Click to expand...
Click to collapse
+1 i not can see in xda premium app
puschkin said:
+1 i not can see in xda premium app
Click to expand...
Click to collapse
Go to the Stickies tab.
Edit: It's in the Topics tab now.
adyscorpius said:
Well, finally you can seperate the men from the boys... !! Nice thought..!!
Click to expand...
Click to collapse
i dont know about that.
Personally I think this Derivative Rom subsection is a bit ridiculous. How does Litening Rom end up in that section. It was one of the first Rom's created for the SGS2 and sure it's a derivative of the original firmware but whose isn't. If that's the case why isn't Pusler_G2 Rom in there as well. With that line of thinking all Rom's should be placed in the derivative section except CM7, oh wait, but his is a derivative of AOSP. I think XDA's arbitrary judgement on what is a derivative or not needs some further consideration. IMO all your going to do is piss off developers with this new sub-section.
jlevy73 said:
Personally I think this Derivative Rom subsection is a bit ridiculous. How does Litening Rom end up in that section. It was one of the first Rom's created for the SGS2 and sure it's a derivative of the original firmware but whose isn't. If that's the case why isn't Pusler_G2 Rom in there as well. With that line of thinking all Rom's should be placed in the derivative section except CM7, oh wait, but his is a derivative of AOSP. I think XDA's arbitrary judgement on what is a derivative or not needs some further consideration. IMO all your going to do is piss off developers with this new sub-section.
Click to expand...
Click to collapse
+1.....
?????
jlevy73 said:
Personally I think this Derivative Rom subsection is a bit ridiculous. How does Litening Rom end up in that section. It was one of the first Rom's created for the SGS2 and sure it's a derivative of the original firmware but whose isn't. If that's the case why isn't Pusler_G2 Rom in there as well. With that line of thinking all Rom's should be placed in the derivative section except CM7, oh wait, but his is a derivative of AOSP. I think XDA's arbitrary judgement on what is a derivative or not needs some further consideration. IMO all your going to do is piss off developers with this new sub-section.
Click to expand...
Click to collapse
+1. Not a good idea. We need to be VERY clear on the rules here.. Right now, they don't seem to be clear, and or are not being applied correctly.
Anyone knows where Litening ROM is based from? Ive read the OP and saw litening is included. Im just curious
I like the idea of tidying up the fourm there alot of threads and alot of ROMS coming out.
I think that you would need to make clear rule on which section a new or current ROM should be in.
The main example which seems to be going on is between VillanROM and LightngPRO. They did appear near the same time, we know that Villian came first but they are each the individuals work are they not?
In creating the seperation you might end up giving the impression that one ROM is better than another.
Could you not make splits like Samsung ROMS/ASOP/Kernels?
Themes already have their own section.
jlevy73 said:
Personally I think this Derivative Rom subsection is a bit ridiculous. How does Litening Rom end up in that section. It was one of the first Rom's created for the SGS2 and sure it's a derivative of the original firmware but whose isn't. If that's the case why isn't Pusler_G2 Rom in there as well. With that line of thinking all Rom's should be placed in the derivative section except CM7, oh wait, but his is a derivative of AOSP. I think XDA's arbitrary judgement on what is a derivative or not needs some further consideration. IMO all your going to do is piss off developers with this new sub-section.
Click to expand...
Click to collapse
Correct!
xda team must reconsider.
These are not serious stuff...
All custom roms are derrivatives of original firmwares.
giokou said:
All custom roms are derrivatives of original firmwares.
Click to expand...
Click to collapse
They are meaning that if it is a derrivative of another members ROM, not if it is made from the stock ROM, it is obvious that they have to be derrived from somewhere. and silly to say that all ROMs should be in here because they come from stock.
from what i can tell the section is trying to protect the work of ROM makers, by highlight the original work and moving works based on a ROM to this section.
Say if i took Villian ROM, adviced people to use Jame Bonds Kernel not CF. Themed it and removed some app. i have made a release but it is not my work the base was villian, so it was derived from that. hence it would go in this section.
EDIT: But i still think the hard part of a section like this is telling what the ROM was derived from. Who is going to do the checking
Crucio_ said:
Could you not make splits like Samsung ROMS/ASOP/Kernels?
Click to expand...
Click to collapse
+1
10 Char...
Crucio_ said:
They are meaning that if it is a derrivative of another members ROM, not if it is made from the stock ROM, it is obvious that they have to be derrived from somewhere. and silly to say that all ROMs should be in here because they come from stock.
from what i can tell the section is trying to protect the work of ROM makers, by highlight the original work and moving works based on a ROM to this section.
Say if i took Villian ROM, adviced people to use Jame Bonds Kernel not CF. Themed it and removed some app. i have made a release but it is not my work the base was villian, so it was derived from that. hence it would go in this section.
EDIT: But i still think the hard part of a section like this is telling what the ROM was derived from. Who is going to do the checking
Click to expand...
Click to collapse
Exactly my point mate!
That's why it is pointless...
I'd like to point out that my rom is not derived at all, i even explained in my OP what was my IDEA and how i was able to get somethings new compared to other custom ROM.
It is the first rom based on XXKG1 release with HW accelerated browser, and it's my own experiment to built an Hybrid ROM (deodexed/odexed). In addition i am using a new kernel developed by angelom in italy!
I did everythings starting from the official (samfirmware) release XXKG1. I didn't use kitchen for theming i have done it by myself, if you don't believe me you can double check it in my Italian Blog that i realized video tutorials on how to theme for LG Dual!
That said, of course each developer use some cool stuff or mod that have been shared here, otherwise what's the point to have a developers community???
Even if there is some mod ready to be included inside a ROM, i always prefer to decompile things do a reverse engineering on smali code and remake mods by me in order to assure that stuff won't break things in my ROM (i.e. FC)
Sorry, but i like to be fair and i wanted to write it down!
LeoMar75 said:
I'd like to point out that my rom is not derived at all, i even explained in my OP what was my IDEA and how i was able to get somethings new compared to other custom ROM.
It is the first rom based on XXKG1 release with HW accelerated browser, and it's my own experiment to built an Hybrid ROM (deodexed/odexed). In addition i am using a new kernel developed by angelom in italy!
I did everythings starting from the official (samfirmware) release XXKG1. I didn't use kitchen for theming i have done it by myself, if you don't believe me you can double check it in my Italian Blog that i realized video tutorials on how to theme for LG Dual!
That said, of course each developer use some cool stuff or mod that have been shared here, otherwise what's the point to have a developers community???
Even if there is some mod ready to be included inside a ROM, i always prefer to decompile things do a reverse engineering on smali code and remake mods by me in order to assure that stuff won't break things in my ROM (i.e. FC)
Sorry, but i like to be fair and i wanted to write it down!
Click to expand...
Click to collapse
You are absolutely right, there are many dev who have done extraordinary things with their roms and put a lot of hours on their rom making. the only thing that has happened now is that you must go to two different places to look up different rom.
Agree. The Development forum is too big and confusing. It better be split in to:-
1) Samsung-StockROM-Mods (Insanity, VillainROM etc)
2) AOSP/Cyanogen-Based (MIUI, CM7 etc..)
3) Kernels
The so called derivatives/themer's ROMs should ideally be pushed to a sub-forum under Themes.
I don't like this idea. Somebody is bumping up his/her ego for nothing.
Mods/admins are creating illusion for first class and second class roms.
Just my two euros.
hacksome said:
Agree. The Development forum is too big and confusing. It better be split in to:-
1) Samsung-StockROM-Mods (Insanity, VillainROM etc)
2) AOSP/Cyanogen-Based (MIUI, CM7 etc..)
3) Kernels
The so called derivatives/themer's ROMs should ideally be pushed to a sub-forum under Themes.
Click to expand...
Click to collapse
i like your idea, just gonna modify to my tastes
1) Roms (subforum)
2) Kernels (subforum)
3) Other Dev stuff (WIP, Guides etc) (this is main forum)
this way there can be no bias towards anything or anyone. It makes it easier to find either the deisred rom and/or kernel
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
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
None of my work counts as development so copypasta porting doesn't count. If it does, then what I did with the deblur/debloat script should count as a universal ROM for moto android devices.
I've heard people complain about copy and paste devs for a long time. Had alot of drama over it when I had the epic. Bottom line is it still takes know how. You have to know what and where to copy. And it still takes a lot of time. And some of the best roms I've used were from so called copy and paste devs. As long as they give credit to where it came from. Most devs learn from looking at what someone else has done anyway. Bottom line the more roms and devs the better. I appreciate your work here, but I see nothing good coming from a thread like this. No affense.My 2 cents.
Sent from my MB855 using Tapatalk 2
now I'm in no way crying but,.....what's the deal bud.....we do alot more than copy paste my friend every rom I do gets smali edits, I have to decompile/recompile several jars in different builds **** in gummy I have to edit the entire framework.jar just to get market working.....is it built from source, no, do I work hard on it without a doubt yes, i can't understand why you needed to open a thread to try to debunk my work..... reason I say my work .... I worked on miui, bill does it now, and does a pretty damn good job of it too..and you think its only copy paste getting miui working.....lol....that one is a beast of its own...takes several several changes to get our to just freaking boot.....I'm working on 4 ics based on the photon and 4 for the atrix.......and for both phones requires several edits ..... i mean seriously all we're doing is allowing more choices more options more roms..... I think you have a very wrong idea of what actually is done on these roms.....**** if it were only as easy as copy paste ....don't ya think we'd have had more of these roms sooner and made by different people, only reason miui got here is yepitsme gave up I picked up slack and took of with it then handed her off to bill.....so again I say whats the deal bud....should be happy our aging phone is seeing so much activity....now I do apologize if I have went out of line here but I couldn't help but feel a, little attacked here directly....and by two of the guys I freaking looked up to on here....all I can say is wow I guess I should just close my threads then since porting doesn't count..... and to say don't cry and tell you it took hours cause there are guides............who made the thread in the first place and the purpose of it is?? I'm in no way crying but not going to be called out like this and not respond, which your a very smart guy so I know that you knew exactly what would happen in opening a thread like this....sometimes it does take hours copy/paste you have no clue.....every new cm9 joker puts out we have to flash each lib one at a time to se e which one isn't playing nice,.but thats just copy pasting isn't it, edits to the build prop, updater script.....smali edits to numerous files, jars,apks....but thats just copy paste too I guess.....or maybe its how at times we flash each rom several times and troubleshoot each issue everyone has not just release and say nothing....but thats just pasting too....you really have no clue maybe should read a couple of those guides you are reffering to cause even in them they tell you this isn't all you have to do...**** some of them even say I can only point to what might work not that this guide works for every phone no matter what...
Sent from my MB855 using xda premium
I see points for either side of the coin but a discussion like this will not be good for the Photon forum. To have developers/contributors against themselves is exactly what has happened in other threads and it never ends up a positive for anyone. I feel there is a place for all kinds of work as long as no work is being stolen and credit is being given. It allows for more options and benefits us all. We could all debate this further but I think we know where this would be heading.
RockoDev said:
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Are you really considered a developer is you forget sh and root in a rom?
remember, we arent taking shots.. just wanna know how it took hours and yet forget stuff like that. dont be willing to start a fire if you cant handle the heat.
bottom line is this as far as im concerned, i could give two craps less about miui, or any of the other cm clones. however i think (most of them) they bring something to the table. and give people choices, if the users really thought it was crap they wouldnt use it..
after working with so many prepaid devices and telling the users that if they want stuff done for roms/kernels then they need to find a dev to get the phone, or one of them needs to step up. so to see more and more people on the photon jump up to help is really nice and reminds me of why i loved this community so much (yes even you willysp ;P ).
if someone isnt making the roms then youd have threads of people complaining cuz they wanted them, so more people are happy in the end because they are made as well as offering choices.
i could go into more but as it is this thread is gunna turn enough into a blood bath so ill try to at least keep my part in it as civil as possible
So I can learn?.... Ok. I really do wanna learn but I think they def need to give credit to the originals. But if they don't like something of one ROM and decide they wanna change it and then let others take it for a spin, whose to stop em?
Sent from my Motorola Electrify using XDA
RockoDev said:
Just a few questions I have for you guys over the last couple months I've seen alot of Miui threads openend and ICS opened?
Are you really considered a developer if you just switch a few files from a rom that a actual developer build from source and made it boot on our phone?
Reason I ask because I've talked to a few developers and they tell me that it sucks how porting a miui, ICS rom has become so easy when it took them hours to build from source?
Just want get your guys insight
Not taking shots at no one so don't start crying about it and tell me it took you hours when there are threads everywhere on how to port these.
Sent from my MB855 using xda premium
Click to expand...
Click to collapse
Let me set the record straight:
FIRST AND FOREMOST: I DO NOT CLAIM TO BE A DEVELOPER.
SECOND: MIUI is NOT just cut and paste. If I had SOURCE for it, I would BUILD it SOURCE. As MIUI has NOT released it, I CANNOT do that. I DO PORT it, and I label it as such. But, to act like all I do is cut and paste, you're way off base.
1) I have to edit the framework files just to get it to fully boot with service/data, and the options that the users of my build have grown accustomed to. I have to test libs each time that Joker releases a new CM9, as not all are compatible.
2) I have to test libs with each MIUI release, as they often build with ARM7b, which is NOT compatible with our beloved Tegra 2 processor.
3) I then make 2 versions (Aroma based and CWM flash).
4) I credit everyone whose work I used to do what I do. That being said, if I port something, you're darn right I should get credit for the work I do.
5) The reson SO MANY (2) MIUI threads have popped up is that Spleef initially started the ports. At a point in late March, I took over doing the ports and he took to other roms. I have been asked recently by MIUI.us to start a separate thread so that I can keep the OP up to date and standardize it to the format that they wanted.
Now, on to my other CONTRIBUTIONS:
1) Fixes thread-yes, may be slightly out of date, but it's helped a LOT of people
2) How-tos thread-sure...I need to add more to it and plan to when I get the time.
3) Anyone here like Kitchen Sink? I ask as Joker and I have spent HOURS working together on that rom getting it to where it is. Not to mention if you use version 2.11, then you're using something I assembled, as it was done while Joker was on away on Vacation.
4) I am usually found on ALL the Photon/Atrix threads helping people with their issues ranging from flashing issues to data issues, etc.
5) Check out how many ROMs I've helped on.
Another thing, I don't have the title Developer...and didn't apply for it. I am a Contributor. I CAREFULLY examined the criteria for each and decided that I would apply for being a Contributor as I DON'T at this time do SOURCE work.
Funny how someone who isn't doing source either would put "dev" in their name when they don't seem to have a single source-built item to their credit, then have a problem with what I do.
Funny that I count there are 3 Rocko-rom variants 2.3.5 posted. See me starting a thread to ask why you have so many Blur based roms?
I would personally LOVE to have the opportunity to talk to ANY of the DEVS you cite as having an issue with the fact that I port MIUI.
moparfreak426 said:
So I can learn?.... Ok. I really do wanna learn but I think they def need to give credit to the originals. But if they don't like something of one ROM and decide they wanna change it and then let others take it for a spin, whose to stop em?
Sent from my Motorola Electrify using XDA
Click to expand...
Click to collapse
your absolutely right anyone can do this it just takes some patience and a little knowledge....we give credit, thanks, and links to every rom we port over..... I'm guilty of forgetting things in roms. I know I am, sometimes things get forgotten or ill use the wrong damn file...lol.....I'm not taking shots or trying to start no crap but I woke up this morning to this thread and couldn't believe what I was reading.... I mean hell rocko rom was jokers originally and look at it now, we all start some where, true I don't do source right now.......but thats not to say I never will I've had joker trying to teach me for a while now but we live our lives so time is short
Sent from my MB855 using xda premium
shabbypenguin said:
Are you really considered a developer is you forget sh and root in a rom?
)
Click to expand...
Click to collapse
Not sure who did that...we had an issue with SU in MIUI on one build due to incompatibility with MIUI and the 0.6.whatever SU xbin
Th3Bill; said:
Funny how someone who isn't doing source either would put "dev" in their name when they don't seem to have a single source-built item to their credit, then have a problem with what I do.
Funny that I count there are 3 Rocko-rom variants 2.3.5 posted. See me starting a thread to ask why you have so many Blur based roms?
Click to expand...
Click to collapse
I'm not trying to pick any sides in this because I like both of your work, but damn he got you.
Sent from my MB855 using XDA
shabbypenguin said:
......reminds me of why i loved this community so much (yes even you willysp ;P )........
Click to expand...
Click to collapse
Why in the world are you taking a shot at me in this thread?
I think, this thread is something, that shouldn't be here. It's all about choices. I don't like the ROMs of all devs here, so I made my own. But I am still glad they are here. And I appreciate their work.
Think I saw in the new evo thread that Rocko is heading there. Maybe triing to stir the pot before he leaves? Personaly I would like to see this thread closed.
Sent from my MB855 using Tapatalk 2
bricky23 said:
Think I saw in the new evo thread that Rocko is heading there. Maybe triing to stir the pot before he leaves? Personaly I would like to see this thread closed.
Sent from my MB855 using Tapatalk 2
Click to expand...
Click to collapse
AMEN!
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Sent from my MB855 using XDA
willysp said:
Why in the world are you taking a shot at me in this thread?
Click to expand...
Click to collapse
lol was just poking fun at ya man hence the
jokersax11 said:
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Sent from my MB855 using XDA
Click to expand...
Click to collapse
Can I get an AMEN
Sent from my CM9 beast
shabbypenguin said:
Are you really considered a developer is you forget sh and root in a rom?
remember, we arent taking shots.. just wanna know how it took hours and yet forget stuff like that. dont be willing to start a fire if you cant handle the heat.
bottom line is this as far as im concerned, i could give two craps less about miui, or any of the other cm clones. however i think (most of them) they bring something to the table. and give people choices, if the users really thought it was crap they wouldnt use it..
after working with so many prepaid devices and telling the users that if they want stuff done for roms/kernels then they need to find a dev to get the phone, or one of them needs to step up. so to see more and more people on the photon jump up to help is really nice and reminds me of why i loved this community so much (yes even you willysp ;P ).
if someone isnt making the roms then youd have threads of people complaining cuz they wanted them, so more people are happy in the end because they are made as well as offering choices.
i could go into more but as it is this thread is gunna turn enough into a blood bath so ill try to at least keep my part in it as civil as possible
Click to expand...
Click to collapse
No!!!!! I am not have never claimed to be.....
Sent from my MB855 using xda premium
To those that may be offended by my position let me clarify. I was on the Evo for the first price drop. A ton of ROMs suddenly appeared that were no more than a font or color change by folks claiming to be devs. To me, simple edits like that are not development or ROMs. I've seen the same with themes, swap a font and call yourself a dev. There are script releases by "devs" that all that was done was change the device name or partition location. To me none of that stuff counts as honest development.
Another example is ROMs from the JoyOS port guides. Copypasta and a couple build.prop edits and look you have JoyOS. That in itself is not development to me. Now if you have to go through and do framework/smali edits to get it to work, that's a whole different story. That requires know how, skill and time.
spleef, Th3Bill and others, I'm sorry if you took my previous post personally. I consider you guys a dev and your work is well beyond anything I have released. Digging around in the code to get things to work is not easy. There are many with contributor titles really should read developer. (again, in thinking about it I really am not one of them). I was also speaking about android as a whole and not specifically the photon forum.
jokersax11 said:
A developer is anyone who developed something for Android. Themes, roms, hacks, root methods, modifications, even scripts. Just because someone doesn't build from source doesn't mean they don't bring something to the community.
Click to expand...
Click to collapse
I can't speak for others but I agree with you on this only to a point. It goes back to the first paragraph in this post. To me, a font change or other very minor changes isn't development. I'm speaking in general however. When it comes to the Photon specifically, there's a lot of actual deving being done and folks that are very deserving of dev status (again, I am not placing myself in that category).
To All,
A lot of crap has happened to me personally over the past couple months. My attitude is lousy at best and I think it time I walk away for awhile. If I have offended I am sorry. Feel free to grab any of my work and run with it. I also have the following unfinished projects up for grabs;
2.3.5 sudo-Blur ROM with root ODEXed and De-ODEXed built straight from the 2.3.5 leak. (USB is intermittent but not sure if its the phone or the ROM)
webtop+ 2.3.5 leak (missing apps)
Copypasta JoyOS port (never connects to service)
Does anyone know if Team Synergy will be making a rom for the Vzw Note 2??
Sent from my most awesome phone EVER!!!!
I loved Synergy on GS3, was my daily driver. Would love to see it here but I doubt it
I wish...
Sent from my rooted, and unlocked Vzw note 2 running Cm10 ! U mad?
lol you guys...how many stock based touchwiz roms do we need? you guys realize all these roms are completely stock that have been themed and modded. with a little intuition, those mods can be done yourself. take a stock odin image, place it in dsixdas kitchen, add your mods, package it up, and you now have the same thing posted in 90% of the sgs3 forum.
What is dsixdas???
Sent from my most awesome phone EVER!!!!
Just Googled it.... Now I want to build Roms..... Gonna have to try this.
Sent from my most awesome phone EVER!!!!
Team Synergy put out some sick tweaks for my old HTC devices (sprint). Haven't used them in over a year but would love to see some more action over here whether its "stock" based tweaks or not. They may even dabble in some AOSP. Not sure.
Sent from my SCH-I605 using xda premium
As droidstyle said, customized stock roms are basically, well - stock based roms with build.prop/init.d tweaks. I like to go back to stock deodexed Verizon rom and debloat/tweak the rom myself because that's where I find the most fun. Custom Touchwiz roms seem to take that fun away from me
Also, search the internet, there's plenty of info on lists of build.prop and init.d tweaks that boost performance and save battery on your phone.
droidstyle said:
lol you guys...how many stock based touchwiz roms do we need? you guys realize all these roms are completely stock that have been themed and modded. with a little intuition, those mods can be done yourself. take a stock odin image, place it in dsixdas kitchen, add your mods, package it up, and you now have the same thing posted in 90% of the sgs3 forum.
Click to expand...
Click to collapse
Oh my. A voice of reason!!!!
DroidOnRoids said:
As droidstyle said, customized stock roms are basically, well - stock based roms with build.prop/init.d tweaks. I like to go back to stock deodexed Verizon rom and debloat/tweak the rom myself because that's where I find the most fun. Custom Touchwiz roms seem to take that fun away from me
Also, search the internet, there's plenty of info on lists of build.prop and init.d tweaks that boost performance and save battery on your phone.
Click to expand...
Click to collapse
Most of which are snake oil, like a lot of performance tweaks devs claim to put in.
I say we open up a donation thread so we can get Team Synergy on board!! Their roms are sooo bad ass!! LOL Just kidding guys! :silly:
droidstyle said:
lol you guys...how many stock based touchwiz roms do we need? you guys realize all these roms are completely stock that have been themed and modded. with a little intuition, those mods can be done yourself. take a stock odin image, place it in dsixdas kitchen, add your mods, package it up, and you now have the same thing posted in 90% of the sgs3 forum.
Click to expand...
Click to collapse
As many as possible, it's called variety. I'm busy and I don't want to do the mods myself.... I like donating to devs to do it for me...that's why most of us are here.
Also one of the great things about Synergy for the GS3 was the nightly builds. Again, I didn't have to do the work myself, received nightly updates/tweaks and simply donated to compensate for their time and work.
Personally, I figure the more devs working on the Verizon Note 2 the better regardless of what they use as a base for their ROM.
You can only do so much with a zip rom. Nightly builds are pretty ridiculous for zip roms. If nightly builds actually did something notable, the rom would be completely rewritten from scratch within a month.
It simply doesn't happen and is misleading.
Here is what I have seen from nightly builds of zip roms:
1. Nothing changes from one build to the next.
2. Things are broken, then fixed, broken, then fixed. However, nothing is actually accomplished.
3. Why are we calling them builds? They aren't building crap except maybe an apk or two.
adrynalyne said:
You can only do so much with a zip rom. Nightly builds are pretty ridiculous for zip roms. If nightly builds actually did something notable, the rom would be completely rewritten from scratch within a month.
It simply doesn't happen and is misleading.
Here is what I have seen from nightly builds of zip roms:
1. Nothing changes from one build to the next.
2. Things are broken, then fixed, broken, then fixed. However, nothing is actually accomplished.
3. Why are we calling them builds? They aren't building crap except maybe an apk or two.
Click to expand...
Click to collapse
I totally agree with you. I had the GS3 and ran pretty much every ROM available for it while I had it. Nothing against Team Synergy, but their ROM always had some type of issue or another. Which I thought was insane for a stock based ROM.
And then the nightlies started happening and like you said, things would break and then be fixed, etc. I finally just gave up and started running CleanROM and Beans. Both were more stable and to be honest, performed better.
I never got the lovefest for the Synergy ROM on the GS3, but that's just me.
Sent from my SCH-I605 using xda premium
I also don't have the time to do this myself either. I work 50 odd hours a week and have two kiddos. I also have no idea what I am doing. I would love to learn more about all of this. If someone can put up a link for a good starting point to learn that would be awesome.
Sent from my most awesome phone EVER!!!!
adrynalyne said:
You can only do so much with a zip rom. Nightly builds are pretty ridiculous for zip roms. If nightly builds actually did something notable, the rom would be completely rewritten from scratch within a month.
It simply doesn't happen and is misleading.
Here is what I have seen from nightly builds of zip roms:
1. Nothing changes from one build to the next.
2. Things are broken, then fixed, broken, then fixed. However, nothing is actually accomplished.
3. Why are we calling them builds? They aren't building crap except maybe an apk or two.
Click to expand...
Click to collapse
Nobody forces you to download nightlies. I do agree that at some point the nightlies can start doing more harm than good but it's up to the end user to know when it's time to get off the train. I've only ever had good experiences with devs who produce nightlies. If I felt like I was getting a service from nightlies, I donated, if not, I didn't. Simple as that.
Whether you feel forced to download them or not is irrelevant. They are quite pointless.
So if these arguments hold up, there should only be two or three roms per device. Touchwiz (or whatever ui is used by the manufacturer), AOSP or AOKP. Everything else is just tweaks and build prop edits. Not understanding the arguments here. Especially from other devs.
*Madmoose* said:
So if these arguments hold up, there should only be two or three roms per device. Touchwiz (or whatever ui is used by the manufacturer), AOSP or AOKP. Everything else is just tweaks and build prop edits. Not understanding the arguments here. Especially from other devs.
Click to expand...
Click to collapse
I haven't looked to see what other devs are saying, but the only thing I said was that nightlies for a zip rom are 100% pointless.
Source built roms are different.
adrynalyne said:
Whether you feel forced to download them or not is irrelevant. They are quite pointless.
Click to expand...
Click to collapse
Maybe to you, but they were far from pointless to myself and many others.