Related
I don't know if you read the news, that Notion Ink will release and already have released a beta of their Android 2.3.4 for their Adam device..
I have tested it, since its basically based on the 2.6.32.9 kernel we all got, and not the latest nvidia 2.6.36.3 which it should be
anyways its not worth porting at this stage, its unstable and its basically using all the apps from the adam device which i find less interesting after trying the hc 3.0 launcher and widget use, i am not going back to 2.2 soon.
but so you .. i tested it and there is nothing interesting about it.
DerArtem's cm7 release is probably much,much better..
How do you port?
Jon2555 said:
How do you port?
Click to expand...
Click to collapse
experience is the keyword or "learn by doing"
I know that you can do it, but I ask you to tell what you change when you port(usually things, not specific), what files do you add, delete, change and what you must change to ported system work(Guide, HowTo or shortly explain) ?
Jon2555 said:
I know that you can do it, but I ask you to tell what you change when you port(usually things, not specific), what files do you add, delete, change and what you must change to ported system work(Guide, HowTo or shortly explain) ?
Click to expand...
Click to collapse
thats no task to explain in a thread..
its all about knowledge and understanding the os, how android loads, and works in general and the more you change, the more you learn..
so "learn by doing" is not = you know i can do it, but a saying when you need to learn how to work with something and its DIY mostly.
I want to learn. Do you know good sites, books or how and from what did you learn?
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
This is a dev thread. Do not install this release unless you know what you're doing. Do not post if you have nothing to contribute.
This is very early build, we're behind other qsd8k devices but will eventually catch up
Big thanks to all qsd8k developers working on this (N1, Desire, HD2, X10).
[KERNEL]
- ol' good 2.6.29-SEMC
- fixed touchscreen driver (now backward-compatibile with Gingerbread)
[ROM]
- partially based on drewis release (thanks!) - currently I don't have access to PC that could handle compilation of the whole thing
If someone could compile clean es209ra build and upload it would be awesome.
[WORKING]
- it boots
- radio, calls, txt (sms)
- audio partially working (in-call is fine, playing mp3/ringtones leads to WLOD)
- bluetooth, GPS seem to work
- wifi almost working ("can't find wlan0 device")
- mobile data (it gets IP but disconects afterwards, needs investiagtion)
[NOT WORKING]
- most of the stuff does not work
- quite unstable
[SOURCES]
Will upload all of the useful code/fixes here.
- ICS + GB compatibile touch driver: es209ra_touch_mt.c
- compatibile ramdisk (props FXP): http://www.mediafire.com/?1n51pn1upwv79ur
[DOWNLOAD]
Alpha1 ROM (for CWM5) + corresponding kernel (flashtool) is here:
http://www.mediafire.com/?ht6p6tbpj2988d4
Cheers,
z
Just did a major clean up on this thread mates....no more "thanks" posts please. If thankful... click the thanks button.
Regards,
M_T_M
Finally we get it. aZuZu is working on ASOP ICS 4.0.1. This may help him work easier. So with locked bootloader, can we flash cause' you wrote there CWM5?
VIDEO
here's a video for ics on x10 alpha build 1
http://www.youtube.com/watch?v=bsOFn4YLvZU
@frosty666 please kindly include this on your ics discussion thread.
thankz
hi zdzihu, its great to see you back! is this only temporary or, are you going to be more active, like before?
mmmkay, I'm not dev, but I want to ask if you're compiling this from ground up (like Jerpelea's CM7), or you're like just mashup of current SE and ICS sources. if its a mashup, I can help. but I do very little design from ground up things.
Sent from my X10i using xda premium
if you have fixed audio hw sources i could recompile..
altho i have complete es209ra compile with ics hw, old cm gralloc / copybit sources and generic audio..
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
I help if u want
Hello guys, I'm new to the forum and I hope to see well with you.
I would be willing to help compile the source since EXCLUSIVELY use only Linux operating system and is much easier to work on programming because most of the libraries are already installed by default, I hope I was clear.
greetings
Joseph
zdzihu said:
Hi Azuzu, I am able to compile single libs and binaries (libhw_legacy, supplicant), it's just dex and stuff causing problems (1GB of ram + 1.6GHz). As for libaudio, I will take a look soon
Cheers,
z
Click to expand...
Click to collapse
yaay Z!!!
glad to see back!
now i feel so bad & depressed that i dont have a working x10 with me
hope that service center guy is able to repair it again...
@aZuZu
can u please upload ur work-in-progress sources to git... i know how much fixing u have done... it might help other too
aZuZu said:
So for me doesn't even boot
As i came from night shift i will try later on more...
Here you are libhardware.so, libhardware_legacy.so & wpa_supplicant from my compiled ICS build so if someone can boot z rom maybe it could test this too
p.s.
it is searching ar6000.ko as normal stock one not wifi.ko as sdk port
Click to expand...
Click to collapse
so good
I will try to build ICS this weekend!
I have no time this weekday
Zdzihu, if the wifi still reports the same error (can't find wlan0 device), it probably means that the kernel refers to wlan interface as eth0. Try changing the wifi.interface entry in build.prop to eth0.
little help for folks that compile ICS on weak pc
make: *** [out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/noproguard.classes-with-local.dex] Killed << if processes during compile get killed try this script > Fix Swap
Well to me helped so maybe it helps other ppl.
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
WHAT IS IT WITH SOME OF YOU GUYS, IT IS DEV ONLY THREAD AT THE REQUEST OF THE DEVELOPER, IF YOU CAN'T FOLLOW SIMPLE RULES THEN INFRACTIONS WILL BE HANDED OUT, YOU HAVE NOW BEEN WARNED!
wbbigdave said:
Has anyone pulled this Kernel apart, i'm trying to lock down some of the touch screen info but I can't gunzip the ICS ramdisk...not even sure if i should be able to.
I GPIO the main files out, can't see anything pertinent in there, so I can only assume its in this ramdisk...biggest problem is that if it is a corrupted archive I can't get ubuntu to open a recovery tool cos it's implementation of the Zlib system sucks dice
Click to expand...
Click to collapse
gunzip -c <ramdisk.gz> | cpio -i
Cheers,
z
The next member who disregards a developers request and posts in a non helpful way will be banned for a week.
i encourage any dev or helpful member to pm me or any other mod with the offending post and the user will be dealt with
Please don't reply tp them to tell them they are breaking th rules as you post will then also be rule break worthy
Hugs and kisses
PiLoT
http://review.cyanogenmod.com/#q,status:merged+project:CyanogenMod/android_frameworks_base,n,z
sorry for posting here. but is for development. for ICS, can we used modified 2.6.29, and modify, like what zdzihu did, it so it 100% or do we have to use 3.x (or whatever) becuase I'm starting to do kernel mods and I want to see what I can contribution.
so in all, does the newest kernel have to be ported? or can we continue using good old 2.6.29 and keep Modding it? (hopefully camera will work, drivers have to be rewritten for kernel. and no one likr to write drivers)
Sent from my X10i using xda premium
In case, we can see here how they get the SD Card working
http://forum.xda-developers.com/showthread.php?p=19774268#post19774268
The first thing I want to say is that my English is not really good. I hope you understand my questions.
I have an idea for a new Android rom, but I'm faced with a dilemma. I want to have as much as possible supported devices, so I also can just build a launcher apk which can be installed through Google Play. In this way all mobile devices with the minimal platform version can use it. The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
The next problem is which base rom I would use if I really build a custom rom. It's most likely to use AOSP as base because it's clean. The question is which version of AOSP: Gingerbread, Ice Cream Sandwich, or the newest version Jelly Bean. You would probably say Jelly Bean because this is the newest version. The problem is the phone support. Gingerbread is supported on most phones. If I build ICS or JB the phones which are supported by Cyanogenmod are easy to support, because I can use their device files. The only problem is that my phone, the Samsung Galaxy Gio is not officially supported and the unofficial port is not really stable. I don't think it's a big problem to use this device files and just wait till the developer makes it more stable, but I don't know for sure.
The last thing I want to know is if it's really that simple to support multiple devices. If I read tutorials about porting existing roms to your device they all say you just have to add your device files to the source and compile it. But they never say something about the kernel. Most devices need another kernel because their hardware is different isn't it? Please explain me how this works.
I'm sorry about this hazy story, but please help me before I make wrong choices. Thanks on purpose.
Wietse
WietsedeVries said:
The biggest problem is that I don't only want a replacement for the application launcher but also the notification drawer and everything else. Is it possible to replace them also? I don't think so, so I think I'll work on a custom rom.
Click to expand...
Click to collapse
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
wingie6200 said:
These changes you are talking about can be done. They are system changes so not supported by the android app installer.
Eg: Your notification drawer, status bar are part of SystemUI.apk. The source for this is can be found in the AOSP source code under android/frameworks/base/...
You can make your modifications, compile it into an apk and then make a flashable zip to replace the current one (or push it via a rooted adb console).
or you can compile the entire source code into a flashable zip (eg CM7,9 etc..) and use it a replacement ROM with your modifications.
This is the line between an application under the android runtime and the android runtime itself.
these files, under framework are part of the OS. so to provide a customized version of the operating itself is what people like to call ROMs.
Now ROMs (like any OS) are device dependant. Windows has the code to run in a lot of different hardware configs, but android aims to be small. It should have only the minimum required code to efficiently run itself on a device.
Thats the kernel. The kernel communicates with the hardware and so the rest of the hardware can happily talk to a working kernel and expect the hardware to function as advertised. Kernel is a simple program which goes into the RAM on system start and sits there directing the operation of the phone.
Kernel devs work on making sure the hardware and the android runtime work perfectly together. Now, in this imperfect world, not all sources are open, even though they should be. and therein the issue lies.
If you want to compile android from source and make sure it works on your phone, first you need to make sure you have the kernel with all the changes(patches) to it made by the vendor (chap who made the phone and bullied you into buying it) to get it working on your hardware.
If you dont have that, you have to do it yourself. Or wait for someone else to do it.
once you can compile android and get it working on your phone with all the itty bitty hardware working A-OK.. then you can browse through the source, make changes as per your individual requirements and compile it into a ROM.
see the changes to the OS are separate from the changes to the kernel. The kernel changes are for hardware-software interaction so they are phone SPECIFIC.
but changes to your custom android OS (ROM) can be "cherry-picked" from other ROM/gerrit/AOSP/CM/AOKP sources and put inside your own source tree to get included in your build.
so if you have all the device / kernel stuff from a working android distribution, you can take the source of another android distribution and swap the device stuff into it and see if it works.
hope this helps.
Click to expand...
Click to collapse
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
WietsedeVries said:
Thank you very very much for your explanation! It's a pity it's impossible to hit multiple times "Thanks".
I think I'm going to make a modified SystemUI.apk but you didn't tell the application launcher is also in this file. Did you just forget this or is this stored in another file/folder? And the lock screen? And I want also to replace the boot animation if it's possible.
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
Only way is through exchanging the png files since porting the whole .apk is impossible.
Sent from my Jelly Beaned Ace
Thanks for the answer. And do you also know the answers of the other questions?
Sent from my GT-S5660 using xda app-developers app
WietsedeVries said:
If I take the source files of the SystemUI.apk of AOSP ICS, does this work on every phone running ICS? Included CM, AOKP and other (smaller) custom roms? And my last question: Since SystemUI.apk a apk file is, is it possible to edit these files through Eclipse and build it in Eclipse? Or do I get errors?
//Edit:
Still another question: How much work is it to, as example, port a modified Gingerbread SystemUI.apk to ICS? (Or vice versa)
Click to expand...
Click to collapse
There are two roads you can go now - one is use apktool to *decompile* apk the apk file that you've taken from your phone, it doesnt convert the app to java source code but java bytecode in .smali files (like an assembly version of the source) but you will have access to the resource files (xml, images etc..) so you can replace them and create some new themes.
http://forum.xda-developers.com/showthread.php?t=1814441
http://forum.xda-developers.com/showthread.php?t=1760133
And no - a GB systemUI.apk will *NOT* work on ICS. It is very probable that any changes you make through any of these methods can brick you phone. So make sure you have CWM and a nandroid backup.
If you want to add/edit functionality within the source code of systemUI.apk, you need to learn how to compile Android from Source. i would suggest getting hold of the CyanogenMod source tree for your device and playing around with it.
Ginger bread is CM7 and ICS is CM9.
http://forum.xda-developers.com/showthread.php?t=1552090
once you have the full source tree, you'll find a folder called android/frameworks/base/core/...something../systemui/..
this will contain the javasource code for your application. Here you can edit stuff to your hearts content!
Note that this cannot be compiled standalone by eclipse. The Android build system must be used to compile this (cuz its a system app).
a nice resource i used when i was doing the same thing :laugh:
http://iserveandroid.blogspot.in/2011/01/how-to-implement-your-own-status-bar.html
cheers and have fun.
Hi all,
i want to start with AOSP 4.2 for our SGS3 i9300 - is anybody interested to develop and publish a AOSP based rom with me?
I'm a real application developer (C,C++,JAVA,PHP,MySQL,some Oracle PLSQL) and now its some cold out - i have time to do
some nice things
I think a team of 2 or 3 developers should be enough to develop on this rom, as we can use a lot from AOSP 4.1.2
### EDIT
As long as no one has found to help, here a short description of current progress:
- Code is pure based on AOSP 4.2 but some snippets of CyanogenMod to bring up hardware (camera,graphics,audio)
- Device is bootable (no other boot.img required anymore)
- Bootanimation is working
- Mount of partitions is working
- Deodexing is working
- adb, debuggerd and root access is working
Not working: a lot
- Graphic not working perfect, needs a kernel patch or a working gralloc/hwcomposer/hwconverter to work without laggy PMEM)
- Camera can not be activated due to a missing function call (undefined reference, maybe it can be solved with a newer driver)
- Audio: missing speaker device (Code have to reworked to work with stagefright and tinyalsa libs)
- USB/internal SDCard: cant be mounted (error message sounds like the device is mounted twice, have to find the error in init process)
- RIL not working (Java file from CM10 have to be integrated in frameworks/opt/telephony)
Currently, i'm working on the Graphic problem and USB part to bring up the device to a stable UI
Way to go man. Good luck to you!
Good luck ...!! Im waiting
Sent from my GT-I9300 using xda premium
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
hop3l3ss1990 said:
Good evening,
Well how have you imagined that? Do you have build something like that before or would this be your first attempts to build up a rom from scratch? Do you know what's all necessary to contribute for that?
I would try to help you, but I have clearly to say that I haven't done anything like this before. I'm in the last term of my study of technical computer sciences, working in a company as application programmer for C/C++ and Java(Android). Due to my studies I have also some knowledge about hardware programming, down to read/writing some code in assembler. I would be interested to this if I get introduced to the topic and some help with the necessary tool chain wouldn't hurt too ^^.
greetings
Click to expand...
Click to collapse
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
andy572 said:
I have successfully built a rom in year 2010 for the LG-P500 device, based on CM7 and modified it in a strange way, so i included a lot of nice things
written from scratch - this rom was a unicate ... later, i developed the "Phoenix Launcher" for Gingerbread enabled devices, but its development is currently
frozen because its strange to support every or almost every device with a bugless launcher. In the last months i learned a lot about android and have to re-think about
what i'm able to do, and what i want to do. In the summer of 2011 i bought my SGS3, the first thing i was doing was to remove that samsung crap from my device and
have installed AOKP. So now it's time to do my own thing again - i want to have AOSP as i think for me its the best Android solution for myself and want to publish it
to other users who think "thats ok for me" too
In short, it doesnt matter if its your first rom - its enough if you know about basic things like "how is android doing all that nice things", "how to debug code", "how to fix
some bugs (even strange bugs)" and some experience with git and github. All other you can learn in a very short time - i've learned the most of things with try & error
Click to expand...
Click to collapse
This all sounds interesting for me and yes I like the idea of developing a own clean rom with some cool additional stuff, too. But what would be the first steps to a new rom? Have you begun with all the administration stuff like setting up a new gitrepo, make a to do list etc...?
I think Code debugging and writing some new stuff wouldn't be a problem for me but what are you meaning excactly with "how is android doing all that nice things"? How it build up, deep level architecture? Well, I know how the "normal" Linux system is working, how modules are getting loaded into the kernel... But how this is correctly working on android I have to learn at first and if there is a chance to do that I would do it
Currently on my S3 is SlimBean and till that there is still no update to 4.2 I'm happy with it, but exploring something new would be pretty cool
Do you have an IRC chat room or something like that? I've to go offline now, my girlfriend wants more attention.^^ But If you want, I' m willing to try to contribute to the rom
PS. I'm sorry for my bad English and hope its understandable, but outside from here you can talk to me in German ^^
If you want to help the AOSP experience on our phones the best place to do it is with the CyanogenMod guys. You'll find pretty much everything based on AOSP (including people that port Vanilla AOSP and AOKP) is using a CM kernel.
They're likely working on the merge now in terms of getting CM10.1 out (with Android 4.2) but most of our CM guys are pretty burned out on working with Samsung's subpar reference material to get basic stuff working (mostly HWC). If you think you could help with this, this would be provide a massive boost to the whole community that want to run these phones on an AOSP based ROM and they would be very grateful.
Gotta warn you though it sounds like it'll be an uphill struggle to get the rest of the stuff working right; unless Samsung release some decent sources for HWC.
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
Wish i could help (just started learning JAVA ) ! gl with this awesome project
Nice to see you here, I remember you from the P500 forums.
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
slaphead20 said:
Xda user krarvind should be able to give you some useful hints, you will have to contact him through the RD forum as his pm is locked down, or I could possibly put him in contact with you
Click to expand...
Click to collapse
Thank you, it would be nice if you can contact him
andy572 said:
Thank you, it would be nice if you can contact him
Click to expand...
Click to collapse
Ok, will mention it to him
andy572 said:
Currently i have only downloaded the AOSP sources and started to integrate most of the configs. Currently it cant compile because AOSP is not AOKP/CM10
where i got the device and vendor directories, so i have to make some changes in the basic system. if it's compiling to the end, i open a fresh github account
and upload all my modifications. The compile process stops currently on audio,OMX plugins, graphics and camera - most of that are small pieces of changes
i have to make - i think, tomorrow (its monday in germany here) i can upload all and then we can start to develop on
Click to expand...
Click to collapse
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Good Luck Dude~
I haven't tried AOSP yet.
Hope someday i can give it a go.:silly:
hop3l3ss1990 said:
How it's going forward?
Maybe it could be useful to publish the github link when it's ready and some more information like staus, on first post
In the next days I have some trouble with my exams ( in two weeks I'm completely finished with my studies ^^) but I think if there is something to do I'll find some time to work on.
Click to expand...
Click to collapse
current state:
- patched android/build so we can compile the kernel within the main compile process
- patched android/build main.mk file so we can use OpenJDK or Oracle JDK
- added android/vendor/aokp and android/vendor/samsung tree from AOKP (its the most useful directory structure)
- added android/hardware from AOKP so we have all that Exynos things that are needed, even by AOSP
- modified android/frameworks/native/include so a OMX Plugin header can be found
- modified android/libhardware and patched gralloc module
currently it compiles to the Webkit library, most of all apps, libs and binaries are building without errors - the next problem
to solve is the PRODUCT_COPY_FILES ****: nothing of proprietary files are copied to the android/out directory, seems like
a bug in android/build too.
For only 2 days trying to compile to the end without errors its a very good cut
here we go: it compiles to the end and a flashable "JOP40" zip could be created
tryed to flash, but it gives errors in CWM: have to remove the recovery folder and the recovery.sh file from etc folder in the ota zip file, but it doesnt boot up - got a black screen only.
do we need a new or patched kernel instead the CM10 smdk421x one?
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
b-eock said:
Well does it have all the closed source libraries fron the phone? If not, it wont boot. Dont think i am calling you stupid, you obviously know what you are doing, but maybe you forgot. Idk. Check that. Try running a log cat and debug that.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks for the hint, yes i have all files included - i cant connect to adb, i see only small colored point on the top left side and a sensor
is red blinking (the one to the right of the speaker.
That would be the proximity sensor near the top front speaker. Cant connect, adb binary in /system/bin or xbin?
Sent from my GT-I9300 using xda premium