I found this at Galaxy SII Forum
LINK
Don't know where should I post this because this is not a app/theme nor a question though.
The files are from Galaxy Note but are working on Galaxy SII. I tried on S5830XWKT3 2.3.6 but have no success. Galaxy SL user also can't make this work.
Maybe this need a little bit mod ?
wait for instruction.. offcourse they will not work as sgs2 and note share same core so libs of note can work on SGS2...
they are libs so changes should be made according to sources to ace libs
madman_amit said:
wait for instruction.. offcourse they will not work as sgs2 and note share same core so libs of note can work on SGS2...
they are libs so changes should be made according to sources to ace libs
Click to expand...
Click to collapse
no instruction available yet , maybe some devs decompile it and see whether can compile to ace lib or not ?
i hav no knowledge to decompile and compile .so lib file
imbawind said:
no instruction available yet , maybe some devs decompile it and see whether can compile to ace lib or not ?
i hav no knowledge to decompile and compile .so lib file
Click to expand...
Click to collapse
.so files are compiled from compilers (such as AOSP)
To decompile them is near impossibility (unless you are good at reverse engineering)
Related
Hello All,
I am looking to PORT over the Cyanogen 6 Camera to the MIUI ROM at least on Rodriguez Style's version. I am aware that Rodi has included the working Libs in his ROM however this is where I am stuck. I would like to first get a list of all the libs that are needed to support the Cyanogen 6 Camera and then possibly complie this into a flashable zip.I have checked on CyanogenMod github under the androidpackage_apps_camera and have found very little info expcept the RAW java.
Lets make this a community effort.
Moderators please dont move this thread as it is Android Development Related.
U cant do that until u have the framework sources of miui, most cyanogen cam changes are in framework and not in camera app.So no need to even try without framework source for miui
charnsingh_online said:
U cant do that until u have the framework sources of miui, most cyanogen cam changes are in framework and not in camera app.So no need to even try without framework source for miui
Click to expand...
Click to collapse
what if we installed the cyanogen framework as an addition to the MIUI framework? Would it work? Like framework2 or something like that?
Hello all,
So I remember not too long ago a lot of people were asking for touchwiz 4.
Now it's out and I haven't really seen any steps in porting it to other devices (like ours).
BUT, some people over at the Galaxy S I9000 already ported it to their devices.
So, since we can also run android 2.3.4 now, I was wondering if there was a porter around here interested in porting this.
Here's a Link To the original post at the Galaxy S forum.
I don't have much experience porting other apps (unless I can get the whole source I.E. All the Java files and XML files in original format), otherwise I would have tried it.
Dympy
I think Gaby02 try port this.
Hello
I did not try this one yet, but maybe it works:
http://forum.xda-developers.com/showthread.php?t=1061883
I linked to that post in the OP.
Already tried and didn't work :/
Dympy.
Whoops, sorry did not saw that
Try running it through Chainfire? Or am I talking **** now?
Well graphics aren't the problem.
First of all, it just won't install (Maybe because I'm on Froyo (The manifest file requires a minimum SDK version of 8, so if I'm right Froyo is capable of using it)).
If that problem can be overcome, I think the rest of the porting Would be quite easy.
Dympy.
Try pushing it to /system/app and reboot? Maybe it works then?
the current port of Touchwiz 4 on froyo is for arm v7 devices only....... so i suggest wait till marcellusbe port's cm7 and releases gingerbread AOSP.... cause then only the pngs will have to be converted... i guess......
Installed on cm7 but when I select tw it just gives a black screen with the notification bar :/
Touchwiz 4 is for ARMv7 so for the moment I think it's impossible to use it :S
i have tried all on froyo and on cm7 but no one would start i cant install it and only blackscreen
Probably, this would take an another marcellusbe to port the lib files
can anyone help me to learn a bit more than android!
I heared about compile form source and biuld form source...And I can't understand what diferences between compile from source and port! can U explain easily?
for example should I want to bring superOxygen Rom in my x10 , should I port it with cm as base or compile form source?!
thx
for short:
porting means you are making rom to your device from another device, you will be just moving libs, editing ramdisk, etc.
compiling from source means you make a complete rom from scratch including programming own drivers, libs in some situations.
If source is avaiable fot superOxygen then you can try compiling it yourself, but editing, or adding your drivers is necessary, and anyway its harder than porting, but gives better result in fact because you can program everything to make it work and you aren't dependant on binary files like in porting.
When porting, hardware should be close to one you have in your X10, because most things will not work when processor differs, wifi modules, gsm etc. You take files from any X10 rom and replace ones that are with same name in another rom (oxygen here).
Thanks very much man!
I took your advices...it was good advices but what is your idea about this:
If I port Superoxygen from Nexus1 for my x10 and (use stable AOSP as base) , then can I say I make a superOxygen Rom?
compiling from source is how much difficult?! I'm 17...! , I have a link that teach compile from source... Is it need some Knowledges that is impossible for me?!
heh, im 17 too and I don't have much knowledge, but looking on pcfighter(a gt540 developer) im impressed, hes 17 too and does a great job, so it depends on time spent and interests
when you port oxygen, you can just say that you ported and not made it. credits go to the maker and you for just making it work on x10
I'm looking now how to compile for gt540 but can't find any idea how to make it strict for gt540 compiling from source tutorials are mostly for nexus s and nexus 4g because most of are just remade of what you can find on official android developer page and its easier. For unsupported device its even harder, you have to work with what you already have and add it first to sources then ... more things to do. I'm beginner with that too, just pulled sources yesterday and looking how to make it work :] so don't expect so much help in this way :]. Just telling you overall how this looks
For compiling you need to know Java and C programing language.
Sent from my Xoom using Tapatalk
@mesaj! do you know c and gava programing languge?! ofcourse I worked c++ a little...
Thanks now I also know what the difference is.
In easy terminology. Compiling a ROM is building a ROM from the source code so it means you are building a ROM from the ground up. Porting a ROM to your phones means to take a ROM built for another phone and to get it working on yours. That's the simplest way to think of it. I have in my signature a guide for compiling a ROM. Oh and I'm newly 18
私のEVO 3Dから送信される。
Thanks for this thread
Thanks now I also know what the difference is.
Click to expand...
Click to collapse
Thanks for this thread
Click to expand...
Click to collapse
just press the thanks button if you like this thread
Hi guys.
While surfing the Internet I found the open source page Samsung (do not know if you already knew about it.). In it, is the official source code for Stock ROM of all editions of the GT-S5830 (L / I / M ...)
And there is something curious, there is a source code for of a S5830V ROM. I do not know that phone is, but this is not code for Android 2.3 is for Android 4.0. To know where I'm going.
Useful?. I hope so. :fingers-crossed:
If the code is to be useful, it will be possible to develop Custom ROM more stable and fully functional. :victory: Just need a good developer invest some of your time to take a look at, something that would be greatly appreciated and if I can with a good donation.
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=S5830
There's also many other models like the SIII / II / I, Y, S5550, etc, etc, etc
PS: Excuse my English, Google Translate I speak Spanish
Yeah, but most of Galaxy Ace here are the pure GT-S5830
I think he means that since the hardware is about the same we may able able to use some of the source code and code from the drivers to make a fully working CM9 for the GTS5830
Sent from my GT-S5830 using xda app-developers app
Yes. in fact, I think the only difference between an edition and another is just the modem, the bands used for mobile network.
Not sure, but seriously believe that these sources will serve to create fully functional CM9.
Please share
Ok, I don't know if this is important, but I found it on the README_Kernel file:
$ cd kernel/common/
$ make ARCH=arm bcm21553_cooperve_defconfig
$ make ARCH=arm CROSS_COMPILE=../../prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- modules zImage -j`grep processor /proc/cpuinfo | wc -l`
Click to expand...
Click to collapse
BCM21553_Cooperve is the chipset of those C, M and I models, a.k.a Cooperve
I have this phone i bought it in australia lockd to vodafone network i manged to unlock it through them i posted here http://forum.xda-developers.com/showthread.php?t=1902313
I spoke to the samsung customer service rep who put me on hold to speak to the tech department he got back to me and said the V has the same chipset as the 5830i different only in the band
Im trying to flash the 5830i stock firmware throught odin and havnt done it yet
Definitely looks promising!
Downloading the code, i'll try to inspect it. ForceF said it had kernel version 140, afaik 5830is only have kernel 126
I downloaded it time ago,the kernel is for Gingerbread 2.6.35.7
The config is CooperVe for Galaxy Ace V
The config for Galaxy Ace I is totoro (Galaxy Y)
Why would they call it ICS if it's a GB build, wtf samsung :\
ZakooZ said:
Why would they call it ICS if it's a GB build, wtf samsung :\
Click to expand...
Click to collapse
Could have been a mistake...
POTATO!!!!
Just like the Xpera P & Sola I've also considered to make a Thread....for the Port Jelly Bean to Galaxy Ace 2 from Galaxy SIII Mini :fingers-crossed:
It's know that our Galaxy Ace 2 is a device with Novathor u8500 SoC chipset
and right now, i'm pretty sure that Samsung will provide Jelly Bean for our device next year. But, we also know that there out is a device with our same chipset and Jelly Bean at launch. Yes, i'm talking about Samsung Galaxy SIII Mini. I have been talking with some users on their forum and i think some information can help us to port jelly bean to our Galaxy Ace 2
So, here are some files which can help us to make a working Jelly Bean Rom on our device:
1. I want to thanks nixonik member to provide a full system dump of SGSIIIMini in here System dump.
https://docs.google.com/file/d/0B-S6...d6cDVsb00/edit
2. Jelly Bean open source code for this rom, provided by Samsung.
in HERE http://d-h.st/c1n
Now that would be really great if some devs step up to initiate this.
You might get some More Info/Help at the Guys at Xperia U,Sola,P,Go threads
Xperia U thread - http://forum.xda-developers.com/showthread.php?t=2055883
Xperia P thread - http://forum.xda-developers.com/showthread.php?t=2057087
Xperia Sola - http://forum.xda-developers.com/showthread.php?t=2047945
Xperia Go - http://forum.xda-developers.com/showthread.php?t=2058766
Awesome awesome AWESOME...now this is some great news..let's show the galaxy w users what ace 2 is worth
EDIT: And be4 ppl start wondering and sayin stuff I said that cuz I had read some complaints on galaxy w forums about w deserving jb more than ace2
Thread cleaned.
Kindly do not flame the OP for opening collaboration projects which benefit the community.
Thanks,
Jonny
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Dr01nE said:
I think Ace 2 and SIII Mini's SoC are not EXACTLY alike but many of us expected to use the SIII Mini for the ongoing project of porting AOSP Jelly Bean to Ace 2 but we've had no luck since many believed that SIII Mini won't help that much with the port so the project has been stalled and we've been waiting for at least an update to the S Advance (or at least a leak we could port) or an official Ace 2 update. I don't really know where this is going but I don't really have my hopes up for Jelly Bean on Ace 2, well at least not until next year.
Click to expand...
Click to collapse
We just need someone to modify the ram disk.
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Sorry if i spam, but when JB is a problem for now, what abou ICS port?
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Since jelly bean can't be ported...how is ics supposed to?(I guess)
mojito0 said:
Since jelly bean can't be ported...how is ics supposed to?(I guess)
Click to expand...
Click to collapse
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
forbidden8 said:
Bcoz other device's, like xperia u and other xperia phones. They have same hardware like Ace2.If the S3 mini is not... dont know; just thinking.
Sent from my GT-I8160 using Tapatalk 2
Click to expand...
Click to collapse
Ahh yeah sorry you're right, xperia u only has ics and not jb, my bad
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Thanks for this little explanation yowanvista and yes it is gonna be hard and what about galaxy advance ? is this devise really different from ace 2 ?
yowanvista said:
That wouldn't work, their kernels are different, their libs, drivers, RIL interface and wrappers are also different. They don't even use the same chipset model and have a totally different board configuration with different components. Their specifications may appear to be similar on paper but it's a different story when it comes to internals.
And Jelly Bean requires Kernel 3.x, it's something that we don't have for the Ace 2 yet and porting a whole kernel from another device running the same chipset is almost impossible. Without kernel 3.x a whole load of things won't work, that obviously includes Vsync (which is totally incompatible with the current Kernel 2.6). We don't even have the device-specific JB sources for the Ace 2 so a lot of things won't work even if someone gets JB booting. Basically what needs to be done:
(1) Get it to boot with a custom 2.6 kernel/experimental 3.0.x (if built)
(2) Fix primary/critical hardware-specific code for the novathor chipset (display, audio)
(3) Fix RIL
(4) Fix secondary hardware (sensors, bluetooth, wifi)
(5) Fix camera HAL
Gonna be hard without the device sources.
Click to expand...
Click to collapse
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
espaciosalter20 said:
oh my god! .... Jelly bean was working on motorola defy with 2.6 kernel and TOTALLY LOCKED bootloader....
Click to expand...
Click to collapse
Sure it can, even my i9001 works with CM10 but Vysnc is broken (and will always be unless a proper Kernel 3.0.x is used). However it seems pointless to use a dated kernel with a whole load of compatibility patches and reverse wrappers here and there just to fill the gaps. It would be better to use a fully fledged Kernel 3.X with everything already set in place, proper drivers and libs without having to look elsewhere trying to port & adapt specific code for the Ace 2. We'll have the official JB sources next year so it's useless to hit your head against a wall trying to figure out how to make a half-baked kernel without the required pieces of code. With the new sources development will be easier, porting CM10.1 will easier too, it's better to wait imho.
JB for Galaxy S Advance is now available
i think this might help. Galaxy S Advance is now receiving JB update. DOWNLOAD LINK
Here's the news: LINK
Only **** ! nice !!!
we still don't have kernel sources to work on it;
mkel91 said:
we still don't have kernel sources to work on it;
Click to expand...
Click to collapse
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
hafidzduddin said:
samsung release source i9070 in opensource samsung web
Sent from my GT-I8160 using xda premium
Click to expand...
Click to collapse
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
strofo said:
I found only gb sources on the opensource.samsung website. Where you saw jb sources?
Click to expand...
Click to collapse
i9070 is s advance not our devices. but we can use it
cocafe tell me he got i9070 source kernel jb
Sent from my GT-I8160 using xda premium
soo what exactly is this new kernel? I can't find changelogs anywhere, just the file to download o: