Related
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
You should do it so that we get AOSP rom
jim93 said:
You should do it so that we get AOSP rom
Click to expand...
Click to collapse
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It is cool. And yes i would love to do it. With my experience with linux this would be no biggie, but android i have no idea. I think that if it was possible surely someone would have made a flawless 98% AOSP rom with 2% samsung parts....... right?
Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA
lilz4life said:
Csb are u done tryna be a mod? Cause reading back to your comment you didn't really contribute anything useful to his question either.
Now as for the question also apks cannot simply be installed on a touchwiz room the framework for both of these is pretty different you have to actually change code and port it over can't simply uninstall =(
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
You did not answer my question at all.
Then I don't u derstand ur question.
Sent from my SGH-T989 using XDA
Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*
jahrule said:
Can some one tell me why we can't compile AOSP for the t989 and just use Samsung kernel so everything works? Basically why can't we kang together a t989 ROM that is how much ever is needed of Samsung device modules etc and the rest AOSP?
Click to expand...
Click to collapse
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::
thederekjay said:
Apparently you have never worked with source and/or compiled from... there are plenty of reasons why that can't happen. Main reason there is no device tree with proper source.
:: DARKSIDE ::
Click to expand...
Click to collapse
I only use linux for the past 5 years i sure the hell have compiled and worked with source. I just never had to compile for anything other than x86(_64) cpu before aka no toolchaining.
Towle said:
That wasn't his question. Just don't respond if you have nothing useful to say. This is exactly where all the flame wars start.
Sent from my SGH-T989 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
It has been suggested before so clearly if someone knew how to do it they would have done it. The best thing at this stage is to try it.
alphadog32 said:
Okay, it is very difficult to make an AOSP ROM with no device tree. That's why we have barely any 100% working. Remember, if you take kernel apart, you will find yourself with many, many files. You need to look through them all and link all the files. If those linked files don't work, then maybe you have to add some. If it still doesn't work, you will need to rework the drivers/firmwares. It is a difficult process. You also need to link all kernel/ROM together. *APK's HAS NOTHING TO DO WITH THIS PORTING PROCESS*
Click to expand...
Click to collapse
Yea.. I was not implying that we grab APKs from some random AOSP build and copy on top of some working stock ROM. My question more is that I see on samsungs opensource site they give us kernel source for the t989 (have not looked at it yet) and then they gave us some build files to copy over and overwrite the build environment for AOSP which I did and built (currently trying to figure out how to use the *.img files), but shouldn't that give us a ~90% AOSP build? That or I am completely not understanding the README file from samsung.
jim93 said:
This is among the useful response for the original question. I was just encouraging him to go try it that is the best way form him to figure out why its not that simple.
This question has been asked before and I have seen how people have responded with different answers of this question. Whenever this question has been responded with technical reasons then it just ends up being followed by a question of why cant you do "A" even though "A" is based on not knowing another technical reason. The problem is the real satisfactory answer involves knowing alot of the basics which would have precluded you from asking the question in the first place.
Asking this question is like ends up like the following
"A: Why cant you fish with potato bits as bait?"
"B: well fishes dont like to eat potatoes"
"A: potato is food though,Why dont they like food"
Click to expand...
Click to collapse
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.
jahrule said:
I think he was trying to say if you don't want to spend the time explaining the details because you make some asumptions about people and their posts whom you have never met... then it is best you remain silent rather than giving some smart remark as an answer.
Click to expand...
Click to collapse
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.
jim93 said:
I wasnt giving you a smart remarks just pointing out that at this point it is best to just try it because nobody knows all the exact steps because nobody has done it for this device.
You are left seeking genera android kernel advice which ->
If you run into trouble with technical details go here http://forum.xda-developers.com/forumdisplay.php?f=565 since it is a better place to ask questions about using img files than in the same forum where people ask "how do I install custom rom" even the themer section is a better place.
Click to expand...
Click to collapse
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?
jahrule said:
I was not saying you were being a smart %^& just saying what I think dude was saying. In fact because of your comment I went got the source from samsung and repo synced AOSP and compiled it and have been playing around since just a little stuck now. My question was for more a technical reason. I understand now that we don't have a device tree for the t989 that works flawlessly... at least thats what i get from alpha and darkside. Now my question more is what the heck is the use of the source from samsung then?
Click to expand...
Click to collapse
You can actually modify the Kernel it just takes work. For example if for some reason either the t989 or skyrockets ICS kernel was open sourced there would be a rotation fix so quick for the one with broken rotation.
Samsung just throws the source they finished out there but doesnt really provide or I think care to provide any work towards AOSP builds.
Check out this thread.
rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Hes asking about compiling Kernel from source I think
jim93 said:
Hes asking about compiling Kernel from source I think
Click to expand...
Click to collapse
No i am talking about the userland
Sent from my SGH-T989 using XDA
rynstphn said:
Check out this thread.
Click to expand...
Click to collapse
Yea thats cool and all but i am more intetested in GB. There is sone source that samsung gives us which i thought is the device tree for this phone... So in essence what i am asking is: what is the source that samsung provides and what use is it? I am aware of the kernel source already i am refering to the other package.
Sent from my SGH-T989 using XDA
Hello.
I have a kernel based on CAF's jb_2.5 branch booting on d2spr.
Source is here.
Status currently is: userland comes up (working panel) and seems to be functioning properly, with the caveat that pretty much all peripherals are broken. USB also works - so this project really is a developer's dream: plethora of mini problems to work on and a wealth of debugging information readily available.
Up until this point, I could focus on specific problems with the boot process and tackle them one by one. However now, there are dozens of directions one could go in, so I am posting this with the hopes of soliciting some help from like-minded individuals with experience in kernel porting. Work is also picking up for me, and I really need to offload some of this kernel work. Plus, I am burning a hole through my boot partition flashing/re-flashing, and it really is no fun doing this alone.
A bit of background: I used CAF's jb_2.5 branch because it is closest to being compatible with the userland HAL (display-caf in particular) currently used in cm10.1. I also have CAF's msm-3.4 branch booting, but the panel headers in userland are too far apart.
I tried to be surgical with the alterations: rather than mass merges, I tried to insert drivers individually (with the exception of media/video where samsung seems to have done an amazing job of crapping all over qcom's already non-upstreamed v4l2/camera/media code). The upshot of this is, we get rid of all the extraneous samsung crap. The downside is things are harder to fix.
The priorities as I see them:
1. Get d2vzw, d2tmo, d2att (etc) off the ground. Currently I only have board files for d2spr since this is the device I own, but someone with the right device and skill set should be able to invest couple of hours to follow my commits and get their version up.
2. Sound.
3. WiFi/Bluetooth. (invisiblek)
4. Camera
So let's get this going.
I wish we could put an effort to make this happen on Midas...
But really this is the wrong forum, the Qualcomm devices are truly on a completely different platform, there is little to no shared code here. Anyway good luck with it...
This honestly belongs in one of three places.
I am very interested in this work though.
http://forum.xda-developers.com/forumdisplay.php?f=1672
http://forum.xda-developers.com/forumdisplay.php?f=1692
http://forum.xda-developers.com/forumdisplay.php?f=1712
It's not really in the wrong section (currently): the US variants of the SGS3 share this "development discussion" section with the exynos versions. If a different dev discussion is created for the qualcomm devices, this thread will probably be moved there.
Take care
Gary
Audio is up and going.
You know you want in on this.
moving along well
wifi and bluetooth now too (bluetooth is just as ****ty as it was before)
as far as i can tell, the two big things left are:
-shutdown/reboot sequence is borked
-data
EDIT: oh, camera too
Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary
garyd9 said:
Can you please discuss development, as opposed to just give status updates on a project? (Otherwise, I'll have to delete the thread.)
Some suggestions: Discuss HOW you got audio, bluetooth, wifi, etc working - perhaps with some code snippets or actual examples.
Thank you
Gary
Click to expand...
Click to collapse
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
If someone wants to spur discussion on a particular part of any code that's been committed then I am game, but rehashing past efforts for the sake of generating content is wasting everyone's time.
You have the last word so do what you gotta do.
In the meantime we have all sensors going (prox/light/g-sensor), gps also works, device reboots properly, and now actually enters power collapse in suspend. Thanks to invisiblek, our wifi and BT drivers have been ported over from 3.0, + he's got d2_vzw up to speed.
Other than some (minor and not so minor) tweaks here and there, the major project that needs a champion is camera.
detule said:
Gary, I appreciate what you are trying to do here, but the commit log is readily available. It's not like folks are asking specific questions and they are left unanswered.
Click to expand...
Click to collapse
The issue is that this section is for development discussion. Currently, this thread is using it as a "status updates for a specific product" thread (and not discussing the process whatsoever.)
Perhaps "Sprint samsung galaxy S III -> General" would be a better place for this thread?
Take care
Gary
How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2
Oh wait, never mind I'll just check the progress on github.
Sent from my SGH-T999 using Tapatalk 2
Moved to sprint sgs3 general.
Take care
Gary
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
klin1344 said:
How's the progress on the camera coming along? Its pretty impressive that you got the 3.4 kernel this far already.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I had an aosp rom with 3.4 kernel and the camera working, plus audio, wifi, and bluetooth. This was almost 3 weeks ago. Sorry to burst the bubble. Thanks
Yes I approve bigwillyg
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Get out of here dude! Hahah jk.
Sent from my SPH-L710 using Tapatalk 2
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
Isn't his beta ROM 3.4. I've ran that since he dropped it. Best aosp ROM out there.
Sent from my SPH-L710 using Xparent Blue Tapatalk 2
bigwillyg said:
Just an fyi, I saw Chad Goodman post a pure Google aosp jb Rom with a 3.4 kernel a couple of weeks ago where everything including camera worked, even html5
Obviously it wasn't here.
Click to expand...
Click to collapse
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.
detule said:
You should know better than to post things like the above without offering a source tree.
Mod please close this thread, it obviously does not belong here.
As a side note: Pretty disappointed with XDA here - this thread gets bounced from development (into general nonetheless), in favour of threads "how to compile CM10.1"? Close it, posts like the ones above are exactly what I was trying to avoid.
Click to expand...
Click to collapse
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2
daniel4653 said:
Why are you getting upset ? Because someone else has already accomplished what the OP is trying to do. I've ran the Rom before so I can say that it ran great.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 I ran it also wish I still had it
Sent from my SPH-L710 using Tapatalk 2
---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------
klin1344 said:
Then where's the kernel source?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Since kernel is not on XDA there's no need to show the kernel source.
Sent from my SPH-L710 using Tapatalk 2
So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.
I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2
jasvncnt1 said:
I don't run that ROM so no idea if it would help but have you tried another kernel? Or tried changing governor's or scheduler
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I have tried other kernels and same thing happens sadly. I will give the performance schedule a try though.
Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2
LGIQEXPO said:
So, normally help is plentiful on the Nexus S forums and I thought that here would be even better due to the devices popularity.
So far no matter where what or who the post is for or at, I have gotten no help from this community in any threads, for any issues I have encountered: I am not saying anything here to be a sarcastic idiot, but I am just hoping that I don't get 2 million people saying "WRONG THREAD IDIOT" and then not helping me or telling me where it should be...
None the less, if there is a good soul willing to help I am currently (and always) on the latest CM10 nightly build. My problem is that regardless of which version, or whatever I do, after about 4~ hours of the phone being on (used or not) it becomes very very.... low frame-y. Normally when the phone first re-boots it is smooth as butter and excellent, much like my old Nexus S yet unlike my Nexus S, it then begins to get worse as each hour passes.
It does NOT get slow.... apps take the same amount of time to load, and the phone feels as quick, yet the problem is it looks as if it is running at 5 frames a second. (This happens no matter the build and regardless of what is flashed with the ROM, but often times all I flash on top is just the GAPPS) This problem never existed on my older phones, and I really wish I could get some help for it.
Thanks guys, Eric.
Click to expand...
Click to collapse
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.
jasvncnt1 said:
Damn. Sorry. You have these issues even after a full wipe?
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Yes I do, I also tried the stable releases of CM and the same problem persists sadly.
zelendel said:
This is why nightlies are Alpha builds. Random bugs and things happen.
As for the lack of help. You got to remember this is a development forum. Not a support forum. I see no mention of a logcat, things you have done to troubleshoot the issue. These things need to be done before opening a new thread
Click to expand...
Click to collapse
Nice to see you here Zel!
LGIQEXPO said:
Nightlies are Alpha builds, yes. But how come my single core 1ghz Nexus S handles them nicer then my brand new dual core S3.
Also, This section on the forums is the "Q&A, Help & Troubleshooting" section is it not? In the equal forum over for the Nexus S, I got help from people as busy as the ROM makers them self. Here, barely even random people come on unless it is to say that I posted in the wrong section. As for a log cat, most every issue I have ever had ever with software has been resolved by something very simply, and only twice in my life was a log cat needed. Of those two times a log cat did not help in fixing the problem I had.
Man, I don't mean to sound mad here this is just my honest experience so far. I am very used to coming to XDA with a problem and leaving with the solution I guess. That and well I am a tad mad my phone is doing this. So please, don't take offense.
Click to expand...
Click to collapse
The Nexus S will work better in SOME situations because those that build CM for it have ALL the needed drivers and such since it is a NATIVE ASOP firmware. The problems with any other device (specifically Samsung decices) is that Samsung doesn't share MANY of the hardware drivers and such for important things. So those that build for Samsung devices have to try and tweak things differently to make them work. That is why CM has nightly builds, sometimes with minor advancements in their tweaking and other times major advances. It takes the devs longer to work it out things.
Sent from my SAMSUNG-SGH-I747 using xda premium
As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III
zelendel said:
As stated above. The nexus hardware was made to work with the open source files and drivers of AOSP. As OEM branded devices have their own closed sourced drivers. With the open source ones work? Yes but not as well.
Wayne Tech S-III
Click to expand...
Click to collapse
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?
LGIQEXPO said:
I see. That makes more sense. So these drivers can't be brought over to other stock builds I guess?
Click to expand...
Click to collapse
No because the driver rely on other files that only work with files of the same type. So OEM drivers and files or OEM files and drivers.
Wayne Tech S-III
Okay, so we have all of course seen that Synergy ROM and GalaxyMod have gotten multi-window/multi-view (is there seriously an official name for it??) working on the Galaxy S3, and on 4.1.1 no less.
This is really bugging the crap out of me (and probably a few other frustrated people). See, I want to make my own ROM from stock with all the features I want, without having to even deal with ROMs like Synergy that just don't quite fit with what I want and what works.
So I shall ask the question many may be dying to answer themselves, and why not sit down and actually discuss it rather than say "oh go here and get 'x' rom lol".
How does one get the Galaxy Note 2's Multi-window feature working on a Galaxy S3 touchwiz (or perhaps even AOSP) ROM?
Simple as that.
We all know it is possible, since it has already been done. And even on a version beneath 4.1.2!
If anyone has any clue whatsoever, please contribute to the discussion. I hope that soon this can be useful to all who would like this feature.
If anyone has any arguments to me asking the question, I haven't ever found an answer, and I've searched almost anywhere I possibly could (even here). So please don't.
Thank you.
Ascyndaeon said:
Okay, so we have all of course seen that Synergy ROM and GalaxyMod have gotten multi-window/multi-view (is there seriously an official name for it??) working on the Galaxy S3, and on 4.1.1 no less.
This is really bugging the crap out of me (and probably a few other frustrated people). See, I want to make my own ROM from stock with all the features I want, without having to even deal with ROMs like Synergy that just don't quite fit with what I want and what works.
So I shall ask the question many may be dying to answer themselves, and why not sit down and actually discuss it rather than say "oh go here and get 'x' rom lol".
How does one get the Galaxy Note 2's Multi-window feature working on a Galaxy S3 touchwiz (or perhaps even AOSP) ROM?
Simple as that.
We all know it is possible, since it has already been done. And even on a version beneath 4.1.2!
If anyone has any clue whatsoever, please contribute to the discussion. I hope that soon this can be useful to all who would like this feature.
If anyone has any arguments to me asking the question, I haven't ever found an answer, and I've searched almost anywhere I possibly could (even here). So please don't.
Thank you.
Click to expand...
Click to collapse
You have to code it into the rom your using. Which means ripping your rom apart down to the base code and redoing alot of the coding from scratch.
AOSP is not an option. If you dont know why then you might want to rethink doing it your self.
You will need to know Java and C++ to start with.
zelendel said:
You have to code it into the rom your using. Which means ripping your rom apart down to the base code and redoing alot of the coding from scratch.
AOSP is not an option. If you dont know why then you might want to rethink doing it your self.
You will need to know Java and C++ to start with.
Click to expand...
Click to collapse
So basically what you're saying is that I should download the source code from Samsung and code it into the ROM? (can't think of any other way to get to the base code simply from my little ROM itself, so that's why I ask this) Never worked with actual source code yet, so I might need a few pointers. It has always seemed as though source codes for different sorts of software are handled differently. And that's true. The thing is, finding how to handle each person's/company's source, and I still have much to learn in that regard.
Call me a noob if you'd like, because I pretty much am. But even so I would like to learn. Just saying. (and before you say "oh, well then go look at the other parts of the forum if you're so helpless", I'm just throwing it out there)
Okay. I thought I saw multi-window on an AOSP ROM but I could be mistaken. Besides, I don't have to do it myself. I could probably team up with my friend who is a hardcore android phone modder like myself.
Yeah, I figured I'd need to know Java and C++ to legitimately code android itself. I'll probably be able to get it down completely one of these days. For now, I'm still learning it.
There is a mod on the sprint gs3 forums that has multiwindow. It's a flashable mod for sprint 4.1.2 rims only though. It's a lotmore work than just that though. Port Sprint ROM then add the mod. And more behind Tue scenes stuff.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ascyndaeon said:
How does one get the Galaxy Note 2's Multi-window feature working on a Galaxy S3 touchwiz
Click to expand...
Click to collapse
You NEED to also know that the APKs themselves also need to be multi-view compatible. This means decompiling and re-compiling each APK for your device (with the change in coding).
I'm not sure if you'd need to change the build prop to match the Note2 as well, but I think your CSC can remain the same.
hednik said:
There is a mod on the sprint gs3 forums that has multiwindow. It's a flashable mod for sprint 4.1.2 rims only though. It's a lotmore work than just that though. Port Sprint ROM then add the mod. And more behind Tue scenes stuff.
Click to expand...
Click to collapse
Thank you. I figured this might be moreso the case, as Team Synergy apparently made their ROM by using dsixda's android kitchen. Porting methods definitely must be learnt to get this kind of thing going.
Anonymously_Unknown said:
You NEED to also know that the APKs themselves also need to be multi-view compatible. This means decompiling and re-compiling each APK for your device (with the change in coding).
I'm not sure if you'd need to change the build prop to match the Note2 as well, but I think your CSC can remain the same.
Click to expand...
Click to collapse
So I'm assuming you mean we should use something like apktool. The question then is what parts of each code do we change/add to make it work. Alternatively, I have seen mods that make it so just about any app will work as well.
I'm supposing I should get the stock Note 2 ROM to obtain the build.prop? I dunno, I haven't done much with build.prop's.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ascyndaeon said:
So I'm assuming you mean we should use something like apktoo
Click to expand...
Click to collapse
This is correct. I don't have the correct answer to any of your other queries as we are actually in the same boat.
Anonymously_Unknown said:
This is correct. I don't have the correct answer to any of your other queries as we are actually in the same boat.
Click to expand...
Click to collapse
Okay. Well hopefully soon we will have the answer.
If anyone else has any info, please share it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Bump?
You are better off learning to use Dsixda's Kitchen or wait on someone else to create a custom ROM for this.
Anonymously_Unknown said:
You are better off learning to use Dsixda's Kitchen or wait on someone else to create a custom ROM for this.
Click to expand...
Click to collapse
Well...I actually already know how to use the Kitchen. It's really simple to use. You just need to know how to install individual mods after you do what needs to be done in the kitchen itself. The only thing I don't fully know is how to port. He doesn't give any pointers because he doesn't actually know how to port either.
And I really don't want to wait for someone else to make a ROM with it included. We already have two, and both are still pretty buggy. Synergy is notably slow (despite CPU tweaks) and there are quite a few apps that don't even work on it (for example, the regular e-mail app). I'm determined to figure out and know how top create my own ROM, but if I can't get the info I need to progress then it'll be pretty tough.
Like I said though. I'm determined to gain the knowledge to do what I want.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ascyndaeon said:
Well...I actually already know how to use the Kitchen. It's really simple to use. You just need to know how to install individual mods after you do what needs to be done in the kitchen itself. The only thing I don't fully know is how to port. He doesn't give any pointers because he doesn't actually know how to port either.
And I really don't want to wait for someone else to make a ROM with it included. We already have two, and both are still pretty buggy. Synergy is notably slow (despite CPU tweaks) and there are quite a few apps that don't even work on it (for example, the regular e-mail app). I'm determined to figure out and know how top create my own ROM, but if I can't get the info I need to progress then it'll be pretty tough.
Like I said though. I'm determined to gain the knowledge to do what I want.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
There are porting guides all over XDA and one in our very own development section. You could run a few things by the guy who made the CSROM BMB rom...and its not buggy as you said others are. It's has a Sprint base and works well with the multiview feature.
hednik said:
There are porting guides all over XDA and one in our very own development section. You could run a few things by the guy who made the CSROM BMB rom...and its not buggy as you said others are. It's has a Sprint base and works well with the multiview feature.
Click to expand...
Click to collapse
hednik, you are in love with upndwn4par. thats all there is to it
xBeerdroiDx said:
hednik, you are in love with upndwn4par. thats all there is to it
Click to expand...
Click to collapse
What's not to love?
Sent from my SAMSUNG-SGH-I747
xBeerdroiDx said:
hednik, you are in love with upndwn4par. thats all there is to it
Click to expand...
Click to collapse
No offense to all the bother devs here but he like loser makes the most solid ROMs and his work goes unnoticed. Guys a boss
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
No offense to all the bother devs here but he like loser makes the most solid ROMs and his work goes unnoticed. Guys a boss
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
agreed. no offense to any devs as well but their are several trending ROMs/devs that everyone seems to run to...without even looking at the great (and often more stable) material that already exists. not to mention, guys like upndwn4par have their hands in a dozen other small mods/patches and really, really useful bits of software that have made S3 life for many of us so much easier.
hednik said:
There are porting guides all over XDA and one in our very own development section. You could run a few things by the guy who made the CSROM BMB rom...and its not buggy as you said others are. It's has a Sprint base and works well with the multiview feature.
Click to expand...
Click to collapse
Yeah I know. I've bookmarked a couple so I can go through them when I have time. :3
Oh, wow! I just went and looked at that ROM and it looks pretty bada$$!!
Also wondering if Gruesomewolf's multi-window mod will work on any ROM. Not real sure what "MB1" is though...
That's so awesome though. I'm a bit surprised people like Max Lee haven't featured that yet.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Mb1 is the sprint 4.1.2 leak. The gruesomwolf mod gas the have a sprint 4.1.2 base... Maybe Verizon will work but at&t and T-Mobile haven't gotten it yet.
Sent from my SAMSUNG-SGH-I747 using xda premium
Ascyndaeon said:
So basically what you're saying is that I should download the source code from Samsung and code it into the ROM? (can't think of any other way to get to the base code simply from my little ROM itself, so that's why I ask this) Never worked with actual source code yet, so I might need a few pointers. It has always seemed as though source codes for different sorts of software are handled differently. And that's true. The thing is, finding how to handle each person's/company's source, and I still have much to learn in that regard.
Call me a noob if you'd like, because I pretty much am. But even so I would like to learn. Just saying. (and before you say "oh, well then go look at the other parts of the forum if you're so helpless", I'm just throwing it out there)
Click to expand...
Click to collapse
So if you want to create a Rom with multi Window you will need framework from gs3 4.1.1 4.1.2 and note 2 4.1.2. You do not need the source from Samsung necessarily as you can pull framework-res.apk with adb, but you need a thorough knowledge of java and c++. You don't normally start off doing major reconstructive editing to roms. If you have adk set up build an app first. There are tons of tutorials in xda and all over google. Then move on to theming and whatnot.
Remeber to hit Thanks if I've been helpful.
Our community seems small. How many developers do we have?
I'm getting ready to release my first ROM for this phone.
Sent from my HTC6500LVW using Tapatalk
Reefer Madness said:
Our community seems small. How many developers do we have?
Click to expand...
Click to collapse
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
More than enough. Not really small. We just don't have 30 copies of the same ROM like most lol.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
This^ Previous phone was the GNex and it was unbelievable how many variants and kangs there were for CM10, AOKP, etc. I ran a lot of them but in the end there wasn't all that much that was different from the original rom. In a lot of cases, the variant ran worse.
Sent from my HTC6500LVW using Tapatalk
Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees
I agree with what has been said already. Quality is better than quantity... My old S2 had about 194873 ^6 worth of different roms. Touchwiz this and AOSP that and don't forget the AOKP, with CM and a side of Sense ports. In the end I dropped myself on a really good rom called The Blu Kuban which was headed up by rujelus22 over in the Epic 4g Touch development forum. I ran that rom for about 18 months before I nix'd my device and went over to the red side here at Verizon. I heard he went forth to the S4 and has kept that rom's traditions alive. He was one dev who was helped by the many and made a rom that many made their daily drivers just like I did.
I know we have a good community over here as well as even before beaups dropped rumrunner on us we had a few devs tinkering with their roms.
Now remember! A community is only as good as the people around it. Support your devs any way you can if it's simple donations or a click of the thanks buttons. But most of all, be part of the community. List the bugs you find in the roms, mods, and tweaks. Help the devs make the best they can and we all prosper.
I'd still like to see old Sense on this phone. Like Sense 3 or 4.
I'd also like to see a CM variant built off Sense base. Like the old style ROMs that had all full Sense apk compatibility but no Sense launcher. Not sure if this is doable with Sense 5 though.
And last but not least, hopefully a dev will pick up Ubuntu Touch.
Just a daydreamin' wishlist.. lol
Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
tylerlawhon said:
Can't port old sense to new hardware. Plus the old stuff was lower resolution.
Sent from my HTC6500LVWBLU using Tapatalk 4
If I've helped, please hit the thanks button
Click to expand...
Click to collapse
you could port sense4+ to this phone (someone did it on the intl one) as the kernel base is the same (3.4.x)
dont know why you would really want to, but its possible
nitsuj17 said:
Quality is always better than quantity
Like was mentioned above, some phones have 200 Rom threads, but really what's the difference between the Rom? They (aosp variants) are 90% cm based with varying mods pulled from aokp source with pa stuff as well
Really, no disrespect intended those 3 aosp roms are all that matter as everything else is just mashed up and derivative of them
As for sense, you only really need a few roms as well; something stock for those who only want root and a few basic mods, some kind of aroma Rom with user configurable options, and or a rom with a lot if built in mods (well you don't need them lol)
Really imo if you have 5 or 6 roms that meet the above criteria you are set
Unless you have a need to flash a different rom every day that has 1 more bs script or 1 different mod in it
The end user doesn't always see the forest from the trees
Click to expand...
Click to collapse
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.
Reefer Madness said:
Consumer choice is always a win. I'd kill for a thread with five million views and fifty three thousand replies. Developers in different sections have had months to build their own form of paradise. Android Revolution HD has fullSnapdragon 600 (GPU) rendering. I want to try that.
Click to expand...
Click to collapse
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own
nitsuj17 said:
thats a bs mod that requires the deleting of a lib (and does nothing)
the end user might enjoy that, real developers know the work done in roms and can sort out the differences between fancy features in a changelog and real code changes and development
views and posts have nothing to do with the work that go into a rom....you can have a thread that explodes because it has a leaked version of sense, a large user base of a rom that drives discussion and hypes upcoming releases, massive bug issues that require help and dicussion, new hboots or firmware needed to run new updates and so on
thread views and # of posts, as well as individual member post count and thanks count is really deceptive and a TERRIBLE barometer of worth in the development community
the best and most important kernel, rom, root exploit, recovery and so on developers that exist in the android world often have a relatively low post and thanks count, whereas guys who release stock deodexed roms made with a rom kitchen in cygwin have tens of thousands of posts and thanks which leads new users and even more experienced ones to inflate their value and skillsets
developers can generally sort out whos who amongst themselves, but its unfortunate that the end user often cant; usually through no fault of their own
Click to expand...
Click to collapse
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4
Reefer Madness said:
Perhaps you should stick to answering the questions you were asked. In any case, it would be smarter to back a winning horse.
Click to expand...
Click to collapse
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app
cstrife999 said:
He did .. You must have not read it...
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
Here I was thinking it was truly reefer madness...lol
Sent from my Nexus 7 using Tapatalk 4
dottat said:
Not to start a war, but I'm going to give you benefit of doubt you probably don't know him. What he said is true.. And you probably just proved his point too.
His work on other devices is proof of that. Give it time, we will see more options now that the crowd is turning more s-off.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I know what he said is true and I don't care. CPU vs GPU. That interests me.