[help]aosp rom development - Galaxy Ace S5830 General

Hi Developer's,
It's really great to see a lot of great roms for Samsung Galaxy Ace releasing day by day.....Why don't you guys work together and bring up an AOSP rom for SGA....Please try concentrating on developing an AOSP rom...
THANKS

Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.

consegregate said:
Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.
Click to expand...
Click to collapse
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App

EmoBoiix3 said:
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!

consegregate said:
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!
Click to expand...
Click to collapse
Wow that's a small package
That's the only advantage ?

EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
with AOSP, we'll have a pure google phone no touchwiz

EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
Small, but also extremely lightweight so I presume it'll be fast. With that as base custom roms should be better and faster.
If sod is really a firmware bug both AOSP and Cyanogenmod should stomp it off...

AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.

skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Wow.....THAT IS AWESOME !
Unfortunately I know nothing about code , otherwise I would've worked on it . LOL

skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.

I have Ubuntu....but I'm a fail at programming XD HAHAHAHA
Anyone wanna make an AOSP ROM with me ?

consegregate said:
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.
Click to expand...
Click to collapse
Of course both cyanogenmod and aosp have to be built from scratch. Cyanogenmod,pure AOSP and MIUI are all based on Original AOSP source code and so have the maximum speed and utilize the hardware to its fullest. This is unlike samsung stock which has incorporated some closed source code with the open source one which limits its development.

...and all AOSP ROM should have no SOD issue

I set to work on it....but I didn't go far . FML
Sent from my Ultima Weapon using XDA App

For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832

adiles said:
For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832
Click to expand...
Click to collapse
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App

EmoBoiix3 said:
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.

edit.. wrong forum

skynet28 said:
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.
Click to expand...
Click to collapse
Thanks a bunch
It's hard t do such things on a VM , you know ><
Sent from my Ultima Weapon using XDA App

Related

[UNOFFICIAL] [ROM] CodeAuroraICS (Android 4.0.4 - .35 kernel - CAF-based)

Hello there,while working on OMFGB and CM6,I decided to take ICS CAF sources and build them since andy is working at AOSP,arjen is working at CM9 and now I'm working at CAF. I opened this since I can handle various projects at a time,infact I'm developing for other stuff also.
Current status: Fixing build errors
All d best little genius..
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Good luck bro!
OT: Mind I ask u why u changed ur name?
Sent from my LG-P500 using xda premium
andy572 said:
@Bytecode, maybe this small info can be helpful:
you need to change a lot of configs in CAF to build - its like the AOSP configs.
the most pro on this project is, its made for MSM devices, possible you can get more
things to function (if things are fixed by CAF) as in CM9 or AOSP ... good luck
Click to expand...
Click to collapse
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
mentalityx said:
Keep doing your thing Bytecode. Maybe just make one board for everything. Then when all is final release them in individual posts.
Click to expand...
Click to collapse
You're right. But now i've already created them,so for the next time.
Bytecode said:
So developing for AOSP is same configs **** to fix
One thing I always asked myself: There is no msm7227 manifest in every caf build,but there's msm7627a,which is basically the same. Doesnìt matter if i build msm7627a?
Click to expand...
Click to collapse
dont know, the hw specs are the same - at least the same cpu/gpu and memory.
maybe only another camera^^
Building now
sooo... any news here?
Bytecode said:
Building now
Click to expand...
Click to collapse
Ha ha little bytecode is going again
Enjoy your build procedure well be waiting
Sent from my LG-P500 using xda premium
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Bytecode said:
So... libskia is giving me ****:
make: *** No rule to make target "out/target/product/thunderg/obj/STATIC_LIBRARIES/libqc-skia_intermediates/libqc-skia.a", needed for per "out/target/product/thunderg/obj/SHARED_LIBRARIES/libskia_intermediates/LINKED/libskia.so". Stop.
(BTW: Used andy's device and vendor folder as well as his kernel).
Click to expand...
Click to collapse
edit the Android.mk and remove that lib, its proprietary **** only
SWEATTAIMI said:
Seems like it's a missing file our a target file.
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
_Arjen_ said:
I guess he changed things for his Phoenix Android look
Also some fixes needed there for loading old adreno-drivers.
Click to expand...
Click to collapse
I'm getting really,really confused here
Adding vendor and device folder from andy gives me libskia ****,adding all from andy gives me framework ****,I don't know what to do here
Lemme basically explain: What files are needed for building/booting CAF ICS succesfully? Don't post stuff necessary for fixing bugs later
Thank you
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Bytecode said:
I don't have that anymore
Wow,I can already smell CAF optimized code: Frameworks base is different for lots of stuff: Using AOSP andy's framework base was a bad idea: I'll check on his github what he changed on frameworks base.
@andy: Did you change stuff in framework base for making it boot or you did it later?
Click to expand...
Click to collapse
AOSP is not CAF, AOSP is not CM - each framework has its own code, it
has nothing to do with my changes, as you can see in my patches, its nothing
to make it "feel me like a phoenix"
To help you a bit:
some makefile variables cant be used in CAF, CM or AOSP and vice versa,
you have to look in relevant config variables ad what its used for,
than look in the source code if the name has changed or the variable
cant be used (or what ever).
_Arjen_ said:
Just one little question, what branch did you use from framework_base?
You took the master-branch?
Guess you won't need the msm and qcom repo's, but need evereything else.
I can't remember I had problems related to skia during build, I have taken a look if I did change anything there, but I did not...
Don't have CAF-sources synced yet, so can't take a look what is going wrong.
Perhaps Lupohirp has them and can take a look.
Click to expand...
Click to collapse
qcom repos are very needed to compile qcom related changes like audio/media.

[VMWare] Android Developer Environment - (Beginner READY)

I have made a build environment in VMWare. I have added all necessary programs to the Gnome menu. I spent a good 6 hours on making this and compressing this.
Before you use the VMWare image change RAM and CPU to your needings. I suggest at least 2GB RAM and 2 cores assigned for decent performance.
I have also enabled 3D acceleration for OpenGL developers or those who want to try making games.
Requirements
VMWare Player (FREE)
VMWare Workstation (optional, paid)
Features
- Everything is installed:
- Android SDK Tools
- Eclipse
- Android AOSP ready: tested with Jelly Bean
- CyanogenMod ready: tested with CyanogenMod 10 and later
- Developer links in Firefox to CyanogenMod and Android AOSP.
Downloads
One package
http://rapidgator.net/file/49386792/Android_Developer_Environment_1.7z.html
Splitted
http://rapidgator.net/file/49403760/Android_Developer_Environment_1.zip.001.html
http://rapidgator.net/file/49400833/Android_Developer_Environment_1.zip.002.html
FAQ
Can you upload on a mirror?
- No it takes too much time and bandwidth. I don't have the money to buy extra bandwidth.
Passwords?
- All passwords are: 'root'
Looks awesome! I just finished downloading it.. But whats the passwords? For the user anddev and root.
mattmannlt said:
Looks awesome! I just finished downloading it.. But whats the passwords? For the user anddev and root.
Click to expand...
Click to collapse
I would highly recommend each user and ESPECIALLY new users go through the process of setting up and configuring their own development environment. You will gain a lot of understanding on how Linux and thus Android operates by working with it yourself, and this really is important. This is great for a experienced dev who wants to have a backup of his own environment, but I think it's just adding one more crutch that the newbies really won't understand.
Password is 'root'
I thought this was a nice and obvious password to use. Sorry for letting you wait.
djjonastybe said:
Password is 'root'
I thought this was a nice and obvious password to use. Sorry for letting you wait.
Click to expand...
Click to collapse
aa
---------- Post added at 08:07 AM ---------- Previous post was at 08:01 AM ----------
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
orbital_71 said:
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
No. Just about the same. I use virtual box .
Sent from my Galaxy Nexus using xda premium
lithid-cm said:
No. Just about the same. I use virtual box .
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Lithid-cm, i am a beginner as i had install virtualbox with ubuntu 12.04 in it, but with 512m. I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Tks
Sent from my LG-P990
orbital_71 said:
aa
---------- Post added at 08:07 AM ---------- Previous post was at 08:01 AM ----------
Djj, was building cm10 in vmware are more stable then virtualbox? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
djjonastybe said:
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
Click to expand...
Click to collapse
Djj, here another question. i am a beginner if i set to only with 512m for vmware will that be fine as I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Sorry can't download from rapidgator if u upload to mediafire u still have to pay? Tks
djjonastybe said:
It's much more stable using VMWare. Many systems have trouble downloading the source code. Virtual Box gets the 'HTTPS ... not received' errors. Honestly I don't know how to say the error accurately because I simply skipped Virtual Box due to that issue
Click to expand...
Click to collapse
These issues are simple configuration mishaps and can be fixed easily. Nat tends to do this, I use a bridged nic. There are also a few kernel values you modify to fix any "download errors". I have never experienced any issues like you are suggesting using virtual box.
Sent from my Galaxy Nexus using xda premium
orbital_71 said:
Lithid-cm, i am a beginner as i had install virtualbox with ubuntu 12.04 in it, but with 512m. I not rushing for building rom up just for mine knowledge and understand on building enviroment would that be fine? Tks
Sent from my LG-P990
Click to expand...
Click to collapse
I had issues building with less then 3 gig of memory. 512 might be too low. Might need at least 2 gig.
Sent from my Galaxy Nexus using xda premium
Those who want to install Sun Java JDK (Oracle) need to follow this tutorial:
http://forum.xda-developers.com/showthread.php?p=28793435#post28793435
Follow the Java part I made the guide some time ago
Kernel Source
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
goldchang said:
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
Click to expand...
Click to collapse
You get the kernel source from your device manufacturer.
goldchang said:
Hi,
I'm new to android development.
I know that every ROM will have a Linux kernel, but where does this kernel come from?
I googled it, but I still can't figure it out.
I'll just take a wild guess.
Is it from
1. The source that you git from? (Ex: AOSP, CM10, AOKP)
2. The kernel of the Linux OS? (Ex: This VM's Linux kernel)
and by the way, am I able to change the kernel myself? (Ex: 2.6.35 to 3.0.8)
Thanks!
Click to expand...
Click to collapse
lithid-cm said:
You get the kernel source from your device manufacturer.
Click to expand...
Click to collapse
Or port it from a similar device.
Will try this soom to decompile and compile the Settings.apk from Jelly Bean... Anyone any Tips? Please send me a PM.....
Hi,
can somebody else upload one package on a mirror or something ! because splitted ones are taking forever to download !
Thanks !
ShivangDave said:
Hi,
can somebody else upload one package on a mirror or something ! because splitted ones are taking forever to download !
Thanks !
Click to expand...
Click to collapse
Don't have a mirror, but why don't you just download a Linux ISO and set it up for yourself? Should be smaller downloads the whole way, everything will be up to date, and you'll get invaluable learning experience.:
thewadegeek said:
Don't have a mirror, but why don't you just download a Linux ISO and set it up for yourself? Should be smaller downloads the whole way, everything will be up to date, and you'll get invaluable learning experience.:
Click to expand...
Click to collapse
I have tried to setup the environment but many packages are missing...
EDIT: Downloaded splitted ones... corrupted !
hey guys, im good java programmer but i dont have any idea about android
so i was wondering what are the benefits of learning android developments?
, will it be easy since i'm good java programmmer?
if that idea is good then what android books do you guys recommend for me?

[SOURCE]MT6589 Full Source Availabe

Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
It is the full source for the Xperia C. :good:
dev0xteam said:
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
Click to expand...
Click to collapse
I believe the config file is device dependent so will be different for a116......
still if anyone takes up the project of building it for a116 he has to modify the config :fingers-crossed:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Dj_Ignatius said:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Click to expand...
Click to collapse
Is it complete?
dev0xteam said:
Is it complete?
Click to expand...
Click to collapse
i think yes..
Ok. The sony source is not fully complete but.enough to build a kernel. Still there is some problem in config or something else which is not allowing the kernel to compile..
Sent from my A116 using xda app-developers app
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
A general question :- i previously had mmx a75 which of course didn't had the sources but overclocking through mtkcpu from playstore was achieved..!! So why our device can't be overclocked using the same app..??
Sent from my A116 using xda premium
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
axis.meister said:
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
Click to expand...
Click to collapse
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
konnorrigby said:
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP and got my hopes high. Read your post now and ...
lets hope Mediatek actually releases full sources in the future.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
http://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.Ui5G3sanojp
can this be the full source? i am not a dev so idk anything about it there is a link in the link i gave u maybe u can see it and tell us
so any good news about custom kernel?
Is this enough to build a custom kernel atleast?
Sent from my Micromax A116 using Tapatalk

[ROM][PORT][MAKO > HUASHAN]PA 3.99 (currently not booting!)

Hello everyone!
I present to you a paranoid android 3.99 port for our Xperia SP
Changelog:
V2: Device no longer hard reboots on bootanimation
V1: initial release
BUGS:
V2: Device doesn't boot (stuck on bootanimation and ADB offline)
V1: Device doesn't boot (hard reboot after 10 seconds of showing splash screen)
Download: PA_HUASHAN_V2
Now as you can see this ROM port is not booting but at least it doesn't do a hard reboot anymore! Currently I have no ADB access as it is listed as offline when doing: ADB devices of course I can't figure out the problem myself so I'm asking you guys for help. Since there is no logcat I know that it might be nasty to determine the problem and where the phone stops booting. I hope you guys can help me get this ROM to boot so we will finally have a working PA rom
thanks to: @-NickHalden- for his nice guide on how to port ROM's
@FXP for the base rom (cm10.2)
and the paranoid android team for the ROM that was ported (pa 3.99 from nexus 4)
Why don't you simply build from source?
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
I'm trying that as well but i'm having some issues getting these files working
<device>.adds
<device>.removes
pa_<device>.conf
pa_<device>.mk
If I could easily get/make these files a source build would already be here
Do you have a idea on how to create these files? or where I can get them?
for example for the .adds file I need something like this (this comes from nexus 4)
https://github.com/ParanoidAndroid/android_vendor_pa/blob/jb43/manifests/mako.adds
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
kamarush said:
It's pretty simple
Adds and removes are the repos what you need and don't need. About the makefiles. You can simple use the mako files as base, only need to change the values to match for our device.
Click to expand...
Click to collapse
OK this is the .adds file I just made can you take a look at it?
huashan.adds
kamarush said:
Why don't you simply build from source?
Click to expand...
Click to collapse
A long ago, i dont have see you on xda....
now you've back....great master
OK guys PA is currently building from source! now let's prepare to wait a long time xD
noahvt said:
OK this is the .adds file I just made can you take a look at it?
huashan.adds
Click to expand...
Click to collapse
This file will be almost the same as the cm dependencies. So this isn't good.
Levered said:
A long ago, i dont have see you on xda....
now you've back....great master
Click to expand...
Click to collapse
Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung
noahvt said:
OK guys PA is currently building from source! now let's prepare to wait a long time xD
Click to expand...
Click to collapse
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
I'm a huge fan of PA, I hope this one for our SP will progress nicely. Keep up the good work devs. Currently on CM coz stock is too laggy on my one.
Tapatalked from my Xperia P
noahvt said:
@kamarush
damn I ran into some building issues already (hopefully nothing to serious)
Lunching device
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
Device huashan not found. Attempting to retrieve device repository from ParanoidAndroid Github (http://github.com/ParanoidAndroid).
Repository for huashan not found in the ParanoidAndroid Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:231: *** device/sample/products/pa_huashan.mk: PRODUCT_NAME must be defined.. Stop.
** Don't have a product spec for: 'pa_huashan'
** Do you have the right repo manifest?
i'll upload my "pa_huashan.mk" file: https://mega.co.nz/#!gZESjTKQ!ESlhCwWQROoh53SFYJ5vqyA177o5jqZdy9V688BWUNs
EDIT: I modified my huashan.adds file
EDIT2: I really needs some help with this! I'm familiar with the compiling process of cyanogenmod but this is a whole new story
Click to expand...
Click to collapse
Just need to update/add pa_huashan to the pa vendor makefiles.
@kamarush
Remember you in developing the Xperia line 2011. Glad to see it with our Xperia SP. Some project in mind?
[QOUTE]Yeah was long time ago i just bought this device a week ago. I just came back to Sony from Samsung [/QUOTE]
Great, i really want rom by you. i hope you can make it soon..:good:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
noahvt said:
OK guys the build has started again! All my previous problems were caused by syncing the old repo (github.com/paranoidandroid) instead of the new one (github.com/AOSPA-legacy) if you get errors like I did try and use the new source (repo init -u git://github.com/AOSPA-legacy/manifest.git -b kitkat)
Just letting you guys know that this project isn't dead
Click to expand...
Click to collapse
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
MrSteve555 said:
When you port AOSPA to unlocked Bl's, could you make a version for locked BL's?
Click to expand...
Click to collapse
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
noahvt said:
I'm already using the locked bootloader vendor blobs
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
MrSteve555 said:
That's really good. :thumbsup: One last question, why aren't you porting the latest PA(4+)?
Click to expand...
Click to collapse
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
noahvt said:
I am now! I forgot to tell you that the version updated this ROM will now be 4.4.2 kitkat!
@kamarush still getting product name not defined but build started! I'll finish it tomorrow
Sent from my C5303 using XDA Free mobile app
Click to expand...
Click to collapse
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
MrSteve555 said:
It's really good! If you finish the build tomorrow, I'll flash it right away . I loved PA on my N7, and I think it's the one of the best ROM's on xda. Hopefully PA won't have that annoying freeze bug.
Click to expand...
Click to collapse
Unfortunately it probably will have the freeze bug as it's based on the vendor blobs that bagyusz uses
Sent from my C5303 using XDA Free mobile app

[WIP][DEV] Ubuntu Touch for Sony Xperia Z Ultra

Hi folks,
I just started to port UbuntuTouch for the Sony Xperia Z Ultra and I think I should have a *.zip ready for testing in 2 weeks.
Until then, I will use this thread as a scrap book to document all the troubles I run into, all the things that needed my special attention and fixes that are not that obvious. I hope there will be some fellas brave enough to test everything and report back or even to join me with the development.
Best regards,
Kalle
First Update:
I found that the Ubuntu Touch version that ist based on CyanogenMod was not updated to a more recent version. This means that I have to either look into AOSP or backport everything to CM-10.1. I think backporting is kinda stupid because newer we are writing new software to improve things. Sadly I don't have much experiance with AOSP so I will have to find out how everything works and what the differences to CyanogenMod are.
The good news is, that I'm catching up with the mailing list, which means I'll have a place to call for help.
Also I'm in the progress to start a git repo, but I'm unsure what I will need to add, maybe some common stuff from sony does not need to be changed.
So long,
Kalle
Update!
There is a new porting guide! See here
I already freed some space for it and ordered a bit more ram so after my exam next week, I'll pick this up/Start all over.
Hope you are as excited as I am,
Kalle
XDA:DevDB Information
Ubuntu Touch for Sony Xperia Z Ultra, ROM for the Sony Xperia Z Ultra
Contributors
KalleEatingBrain, Kohelet
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Testing
Created 2014-05-14
Last Updated 2015-02-24
freaking awesome!
freaking awesome!
i would like to test. maybe i can help with developing/porting
Thank you for your efforts. I will test if needed.
Sent from my C6806 using XDA Premium 4 mobile app
Great this would be awesome if you can make it happen. I'm here for testing if required.
Sent from my C6833 using XDA Premium 4 mobile app
In also here for testing... Ubuntu Touch has intruiged me, I would love to try it out.
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
iBuzman said:
Thx... (thread bookmarked)
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
+1
Nice.ill be watching out everyday
Sent from my C6833 using XDA Premium 4 mobile app
blueether said:
I keep meaning to reply to this thread... Thanks for putting the effort in to get this working. If you want any hints/tips etc from my experience in getting slim and carbon built for the ZU just ask, I'll be willing to test aswell
Click to expand...
Click to collapse
Cool, thanks can you give me a hint on how to deal with new targets in Aosp? I mean setting up the files in a way "lunch" is able to find the right target.
Sent from my C6833 using XDA Free mobile app
vendersetup.sh file in vender/ might be what you are looking for?
have a gander at this http://www.kandroid.org/online-pdk/guide/build_new_device.html
How are you doing on this? I've just started working on this as well and am curious to know how far along you've gotten/what issues you've run into.
Sent from my Nexus 7 using XDA Free mobile app
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Kohelet said:
So I've gotten the build to start, but I'm running into issues with libhybris:
ubuntu/hybris/compat/media/media_codec_layer.cpp:51:40: fatal error: gui/IGraphicBufferProducer.h: No such file or directory
compilation terminated.
make: *** [out/target/product/togari/obj/SHARED_LIBRARIES/libmedia_compat_layer_intermediates/media_codec_layer.o] Error
I'll post here once I've found a solution.
Click to expand...
Click to collapse
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
KalleEatingBrain said:
Yeah, thats as far as I got, too. :-/ I tried removing all different libs or compiling different parts and leaving others out but I couldn't get any futher. Also I saw your post to the mailing list but it seems like you wont get a helpful reply either. As far a I could track this problem is the incompatibility of togari CM-11 and the ubuntu AOSP source tree. On xda-university there is a guide for porting from CM to AOSP which I will try but maybe you should take a look, too. Anyways: Great to see there is someone else except lazy me working on this.
Best regards,
Kalle
Click to expand...
Click to collapse
I actually got past the libhybris issue. The problem was that the porting guide is out of date. It's based on using cm-10.1 whereas the current source for Ubuntu is based on cm-11.0. So if you use 4.4.2 instead instead of 4.2.2 then it works. But there are so many other issues and the documentation for fixing them is so poor. I've kept a running list of problems I've come across and the solutions for them (it's below).
Also they dropped the whole UCM thing so you should be able to get sound working once you actually get a working build, but I couldn't get it to build. The error that is currently in my way has to do with "No rule to make target signapk.jar needed by com.qualcomm.location" or something or other. And I found nothing on how to solve that online.
At this point I've decided to take a short break from the whole thing because it's so frustrating.
Once I get motivated to work on it again, I'll probably start from scratch.
Issues List (I apologize for not being specific about the errors, I didn't write them down verbatim):
If you get an error about libelf you need to add CyanogenMod/android_external_elfutils to your local_manifests/roomservice.xml and also add external/elfutils under subdirs in build/core/main.mk
Don't forget to also add device/sony and vendor/sony to build/core/main.mk as well.
The build will complain about not having a rule to make android-boot.img. To fix you have to go to device/sony/fusion3-common/custombookimg.mk and change boot.img to android-boot.img. You need to make the same change in device/sony/rhine-common/custombootimg.mk
I got an error about android.hardware.bluetooth_le.xml. If you just restart the build it doesn't complain, but I didn't find a proper solution to that.
If you get the libhybris error you have the wrong version of the Ubuntu source. Make sure you're using 4.4.2 when you phablet-dev-botstrap. It should be phablet-dev-bootstrap --sources aosp --repo-branch phablet-4.4.2_r1 [target_directory]
You might get an error about a product_config.mk and how it's missing a makefile for togari. You have to make sure that in device/sony/togari Android.mk, cm.mk, full_togari.mk, and vendorsetup.sh PRODUCT_NAME is the same. I solved this by changing PRODUCT_NAME to cm_togari in all of them and then renamed full_togari.mk to cm_togari.mk
You might get an error like MODULE.TARGET.SHARED_LIBRARIES.libOmxCore already defined in hardware/qcom/media. You should have CyanogenMod/android_hardware_qcom_media-caf-new in your repo manifest with a path of android/qcom/media-caf-new so you can safely rm -rf the hardware/qcom/media directory to get past this error.
If you get an error about dtbToolCM, add /device/qcom/common/dtbtool to your subdirs in build/core/main.mk
You may get an error about mkbootimg, that's because Sony uses a different version of mkbootimg. The only option I found was to download it from the internet (Thanks DooMLorD!). Once you get that version edit device/sony/rhine-common/custombootimg.mk and replace $(MKBOOTIMG) with the path to your downloaded mkbootimg binary.
You might get an error about no rule to make target something/something/signapk.jar needed by something/something/com.qualcomm.location. I didn't find a solution to this error.
Click to expand...
Click to collapse
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
blueether said:
Thanks for that list, it's sure to help some one. I think I have had most of those errors in trying to get aosp to build.
Can I copy those errors to my [DEV]Random thoughts thread?
Click to expand...
Click to collapse
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Kohelet said:
Sure, feel free. I built CM for all my devices and regretted not keeping such a list when I did that. So now every time I work on a build I keep lists like that. Eventually, when I have a working build, I'll post a guide for how to build following the same steps I took.
Click to expand...
Click to collapse
Yeh carbon and slim were easy to build, and simple fixes. AOSP on the other hand I wish I had kept a build log
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch. I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
KalleEatingBrain said:
Ah nice, when I last checked CM-11.0 was not working with the 4.4.2r2 branch.
Click to expand...
Click to collapse
That could potentially be a major source of my problems. i wasn't aware of that.
I think I know how to fix the problem with the *.apk. Basically you have to remove all java dependencies from all the makefiles. I will look it up, so I can tell you what to grep for. Do you have a git repo we can work on, or should I add you to mine (which is just a fork of the CM-repos)? I will take a look at the sound in the next days. Thanks for you list!
Keep it up,
Kalle
Sent from my C6833 using XDA Free mobile app
Click to expand...
Click to collapse
All I have at the moment is a fork of the CM repos. Feel free to add me to your repo. My username on Github is Kohelet as well. I can start to look into removing java dependencies as well.
As for the sound, the mailing list made it appear as if it was a simple matter of running
Code:
$ sudo apt-add-repository ppa:ci-train-ppa-service/landing-018
$ sudo apt-get update
$ sudo apt-get dist-upgrade
$ sudo apt-get install pulseaudio-module-droid
I could be wrong though.

Categories

Resources