SGSII ICS leak = Port for the brave - Samsung Galaxy Tab Plus

http://www.engadget.com/2011/12/15/touchwizzed-ice-cream-sandwich-leaks-for-samsung-galaxy-s-ii/
any brave devs?

I think we should wait our rom officially release...there not much talented dev on this tab forum.. We should wait bit more
Sent from my GT-P6200 using xda premium

Since there is no Development per say, Im moving this to General.
Thread moved.

At least Sammy is working on this which is good, but the ROM is in very alpha stage...

Is there development of ICS on the 8.9 or 10.1 forums? You would need an ICS kernel of some type to even begin porting, if the other tabs have one that may work for the 7 too with some tweaking. Not sure if a kernel for a phone will even work on a tablet. ROMs I have some experience building, kernels I do not.

kzoodroid said:
Is there development of ICS on the 8.9 or 10.1 forums? You would need an ICS kernel of some type to even begin porting, if the other tabs have one that may work for the 7 too with some tweaking. Not sure if a kernel for a phone will even work on a tablet. ROMs I have some experience building, kernels I do not.
Click to expand...
Click to collapse
I'm pretty sure our tabs run off an entirely different chipset as well.
Sent from my PC36100 using xda premium

true, would be a pain I'm sure. ICS will be released soon enough.. I hope...

abowlby said:
I'm pretty sure our tabs run off an entirely different chipset as well.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
I think you'd have to find a ICS kernel for the exynos processor in the 7 not sure if the current Honeycomb kernel would even work. Porting itself is basically taking the system and boot images off of your current device and replacing the ones in the ROM you want to port with them. The easiest ports are from devices with similar hardware. For the more difficult ports getting things like the sdcard to mount and wifi and bluetooth working can be a ***** and takes some expertise. Way beyond what I could do. I know enough to make ROMs using the kitchen and how to insert premade mods into them and also a little about decompiling and modding apks. All the info is pretty much on this site scattered about in different forums. I've been hesitant to even try anything with my Tab as you can easily brick it playing around I'm not familar enough with it to get it back if I even soft bricked it. My phone has an unlocked bootloader and I can recover it from pretty much any disaster. This thing I'm not even sure how it all works yet, samsung devices are totally new to me.

Related

[Q] Port ICS from Samsung Galaxy S II I9100

is there a way to port this build Here to our phone?
Sure if you want a paper weight
Sent from my SAMSUNG-SGH-I727 using XDA App
lol ^
Sent from my SAMSUNG-SGH-I727 using xda premium
No each rom is specialized to a specific phone unless otherwise stated. The best ics rom I have used to so far which looks almost identical to that rom is [ROM] Sky Ice Cream Sandwich (2.3.5 <<WHAT DOES THIS SAY?) Multiple Flavors 1/24/12
Many kudos to seanscreams. Good documentation, quick, and average battery life, by my testing.
Cheers
If the T-Mobile version gets it, then we may see it sooner than the official release. the OG GSGII has very different hardware.
Converter
There is a way to put S2 roms on skyrockets but I'm not very familiar with it and I've never tried it out etc.
i can't remember where it is but its in the Dev section i believe and its a converter so u install the rom then convert it from recovery menu and stuff
idk don't hold my word to it because i haven't tried it yet
but just an idea
Won't work, different hardware, different hardware identifiers, different...differences.
It's all speculation at this point.
Besides, there's already a build out there floating around, but key features aren't working.
BootyWurk said:
There is a way to put S2 roms on skyrockets but I'm not very familiar with it and I've never tried it out etc.
i can't remember where it is but its in the Dev section i believe and its a converter so u install the rom then convert it from recovery menu and stuff
idk don't hold my word to it because i haven't tried it yet
but just an idea
Click to expand...
Click to collapse
Let me get this right...
You don't know where you got this info from, don't remember where this mythical tool is, and you haven't tried yet, but you are confident it is doable?
Let us all know when you remember where we can get this imaginary tool. I am not holding my breath meanwhile.
enigma00 said:
Let me get this right...
You don't know where you got this info from, don't remember where this mythical tool is, and you haven't tried yet, but you are confident it is doable?
Let us all know when you remember where we can get this imaginary tool. I am not holding my breath meanwhile.
Click to expand...
Click to collapse
I'm sure he's thinking of the method of getting T-Mobile Hercules roms over to our Skyrocket... That's not too big of a deal, because again, the hardware is the same, just different modems need to be used.
But like stated before, this won't happen. May be the same OS, but without the same hardware, it's useless to us. We're not going to get ICS until they release it/it leaks for either the Skyrocket or Hercules.

[Q] Merging firmwares?

I've been thinking about the possibility of extracting the firmware from a Galaxy Tab 2 (ICS) and merging it with the kernel and build.prop from the 7 Plus (Honeycomb).
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Would it be a futile effort? Maybe if Samsung releases ICS for the Plus, but who knows when that will be.
I don't have any experience on these two Android device other than in an end user capacity (though I have been reading) and very little on a few other Android devices so I dunno if it's feasible, but I thought I'd mention the idea.
Anyone with deeper experience on these things think it might be viable?
I know the devices have different hardware specs so I don't know if it would meld...
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
/QUOTE]
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
leodfs said:
fewt said:
Technically I can't think of a reason that it wouldn't work, I'd think that the challenge would be getting the kludged FW back onto a 7 plus.
Click to expand...
Click to collapse
technically: different hardwares, the ics may need some changes on kernell itself to work, so you may not be able to use hc one.
besides the differences of one device to other is not just encapsulated on kernel, the dalvik virtual machine needs to be ported to every machine depending on aspects.
Enviado do meu MB525 usando o Tapatalk
Click to expand...
Click to collapse
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
fewt said:
Technically, it shouldn't as kernel interfaces don't change that much between releases. Since both processors are ARM, I wouldn't expect a problem with the Dalvik VM either but I guess I could be wrong there.
Would be interesting to see, but I can tell there isn't any interest in it. I've been trying to find a good reference on where to get started with this stuff, but it just seems like a hodgepodge of information sprawled all over the place.
Anyone have a solid guide to getting started building custom firmware that isn't the great google?
Click to expand...
Click to collapse
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
I would think if it were as easy as combining the two, who would need XDA?
kzoodroid said:
I suggest you read the CyanogenMod 9 thread in development as you will experience the same problems porting this over without a working ICS kernel.
Here are some threads I've found useful on porting and building from source:
http://www.iphoneandroidtips.org/miui/how-to-port-miui-v4-to-android-phones/
http://forum.xda-developers.com/showthread.php?t=1153233
http://forum.xda-developers.com/showthread.php?t=1499411
http://forum.xda-developers.com/showthread.php?t=1169570
http://forums.androidcentral.com/ht...how-build-your-own-kernel-package-source.html
http://source.android.com/source/index.html
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
These threads are for all different models of phones and the methods may or may not work for our tablets but the principles are pretty much the same. In the instance of porting over MIUI 4 you have to start with a working CM9 ROM as it requires a working AOSP ICS kernel, which we don't have yet. Our devs are working their butts off trying to port one over from another device but its slow going without the proper source code that Samsung won't release.
Click to expand...
Click to collapse
This is awesome, I really appreciate you taking the time to write it up.
I hope you have success, either way you will learn, that's why we bought our android for.
I think there's a lot of interest, but this thing is dangerous, lots of devs have their devices bricked trying port or improve,.
My advice is not of an android developer, but of someone that has some experience of customizing or compiling the Linux Kernel. any little thing you forget render you with a system that will not boot. And even if they use the same kernel, ics may need some things activated that hc may not
Sent from my GT-P6210 using Tapatalk 2 Beta-5

Anyone trying to port the ICS for us yet? :)

Sent from my SGH-T769 using xda premium
I wish lol. Likely not anytime soon. At least we're getting the official update if nothing. Funny enough, I bought this phone thinking we would get lots of ported ROMs, being so close related to the S2 series, but boy was I wrong
Sent from my SGH-T769 using xda premium
Bulletblitz27 said:
I wish lol. Likely not anytime soon. At least we're getting the official update if nothing. Funny enough, I bought this phone thinking we would get lots of ported ROMs, being so close related to the S2 series, but boy was I wrong
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
like in the other ics thread u started I said i would but sorta/extremely difficult without the device lol
I have been making efforts, but trying to keep them generally quiet. I am trying to build us an ICS kernel based on the kernel sources from the T989 release. It has most all of the bits that we need for our variant (our LCD panel code, earjack, etc), but it's obvious from attempting to build the thing that Samsung wasn't finished yet. At least, they weren't finished with the T769 code when they packaged up the T989 sources. I've already fixed a number of simple errors in the kernel code, but bigger ones are now holding me back.
I am not a programmer (and I keep saying this) but I am confident that with my other bits of experience, I'll be able to get a working kernel. Based on that, I am hoping that the architecture of CM9 and it's more official samsung_msm8660 base (thank you, T989 team and contributors) will make it easier to put together a build once we have a working kernel.
This phone is not without love. In as much as no one hears about it, I probably spend 50-60% of my free time trying to get something together for this phone, hitting dead ends or massive missing pieces down each road I take. An ICS kernel, which is what I am trying to build now, would be a massive bridge to get me much closer to point B from point A.

Is it possible...

Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
You'd be better off asking the Infuse devs, I doubt any NS dev is going to be able to do anything to help you since they don't have the device to work on. The hardware is pretty similar so it could be doable but you're definitely going about it the wrong way.
DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
it is probably possible but you are likely to run into numerous errors, that is if you even get it to boot !
we just recently got jelly bean a few days ago and it is still improving so using that as base would likely result in a very unstable port.. but you are welcome to give it a try and see how it goes. the worst that can happen is having to go back to stock
if you happen to have a capable PC, you might want to try building your own rom from source! it should be a great learning experience and is much more likely to work compared to a port
DefinitiveX said:
Would it be possible to port a JB rom for the nexus s to the Samsung Infuse 4G? I'm new to all the development stuff, all though I have been flashing roms and such to many devices for a while. I understand most of the simple development stuff, but I know hardly, if anything, about porting roms to other devices. I don't think it would be possible, seeing as they are two completely different devices, but anything is possible. Just doesn't mean its very probable. So go easy on me.
Sent from my A500
Click to expand...
Click to collapse
not sure about porting but there is a working JB rom on the Dev section
galaxy s line
i believe you'd actually be closer by using the CM10 for the fascinate that just landed yesterday, but i digress. the JB CM10 in the dev section is working better than CM9 for me.
I would definitely like to learn how to build a rom from source. But isn't there a lot of coding involved in that process? If there is, I would have to learn all that as I go. And I'm also going to check the development section right now, as soon as I post this reply. Seeing as I have a Nexus S and not an Infuse(my girlfriend does), I don't check this forum that often. Thank you all for the replies.
There are a few guides around that tell you how to set up the building environment on your PC, and how to sync repos and build for your device.
The complicated part might be fixing errors in your build , but thats how we all learn
Sent from my sweet and buttery Infuse

AOSP on Galaxy Tab 3 10.1

So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
ush
AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud
Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app
Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2
Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device

Categories

Resources