Because it seems to be a often requested topic I wanted to give back my experince with compiling the in topic mentioned source code and how really value it is for anything.
I started this because I got the code for review for a intrested customer but my experince with arm and gcc is rather low. So i started reading up on the cross compiler and came accros serveral dificults with the build enviorment.
First the code seemed to be aimed to a rather old version of gcc, newer cross compiler toolchains won't compile it.
So I obtained a 2004 linux (redhat 8) which fitted best in the time mentioned in the headers source was last edited. On this system I was able to build the cross-arm toolchain like mentioned in the readmes without any problem.
With the builded toolchain I was also able to compile celp_fxp and with the make file. i mentioned that in the makefile there is a (intentionally) added error. After the last source file there was fxlp.c added which is not a file present in the tree. After removing this the .o files builded fine.
I imported the .o files produced back to windows Embended Visual C++, opened the project and started a compile like further explainedin the readme docs. Sadly I now face this error:
acb_parm.o : fatal error LNK1190: invalid fixup found, type 0x0010
It is possible this error occures from a wrong compiled gmp libary for which no build isntructions were given. If anybody has any value information on this I would greatly appriciate this. As I said earlier I had really no experince with gcc form cross arm before i started here. I always left out linux compiler of my embended world.
I am working on this now since a few days, maybe someone else got experince in this he/she wants to share. Thansk for reading.
Hello everyone,
when making a localized ROM people often face the problem of finding proper localized packages/MUI, especially for non-standard packages.
Many localized ROMs are the result of a lot of translation work that may have already been done by someone else.
So the idea is that we collect working packages in a central place where we can collect matching localizations. After all, most WM6.5 packages should be device and OS version independent so we could essentially share across all devices.
What do you think about this idea? Obviously it would not be trivial to implement because we would need some kind of shared storage where everyone can contribute. The simpler solution may be a collection thread or a separate forum with links to rapidshare et al.
TSW TOOLS - encoder/decoder for tsw files (Toshiba G910 and Toshiba TG01 SD card update). The destination file created at same directory as source file.
http://cotulla.pp.ru/Misc.html
http://forum.xda-developers.com/showthread.php?p=5428057
its god or bad?
¨kiler129
Junior Member Join Date: Aug 2007
Location: Siedlce
Posts: 10
nicus wrote msg to Cotulla (G910 tsw decrypter). Cotulla send keys but don`t reply about TG01 tsw decryption.
TSW files for G910 looks similary to G910 but use diff key for DES encryption.
Quote:yes, there used new keys
"12345678" in G910 and "54470152" в TG01
-Cotulla
If anyone have exp with WM programming or decompiling WM software please contact me or nicus (at this forum know as nico101 - http://forum.xda-developers.com/member.php?u=595282)
Any help is wanted
#335
Today, 07:06 PM
Cotulla
Senior Member Join Date: Sep 2007
Posts: 495
who interesting I created new tool.
you can find it on my site http://cotulla.pp.ru/Misc.html "TSW TOOLS".
oh my god, that maybe the philosopher stone of the TG-01.
Some guy at MoDaCo posted how to bypass the operator cheking, now if we can encrypt/decrypt roms, the circle may be closed!
looks like mods have given up on TG01
the device is highly encrypted!
not the mods fault, but toshiba's near-sighted attitude.
their loss, i sold mine. dead device.
well all i can say if the tg01 is dying a death i do not give out much hope for toshibas TG02 thats going threw the fcc. plus apparantly theres a tg03 to come too.
i do not mind sticking till theres an update for it, maybe 1 or 2 more updates, windows mobile 7 would be nice tho too fingers crossed
Hello Ace Users!
Screenshots coming soon.
RTL Language will be added thanks to BehradGH. Remember to thank him too.
Many Thanks
EmoBoiix3, fla.sh (Dev of fla.sh ROM) And me Jekle_Ace and our tester consegregate
AOSP will include all the vanilla android components like Gingerbread Keyboard, Gingerbread launcher, As well as no samsung clutter or customizations. GUESS WHAT NO ANNOYING SAMSUNG BOOT ANIMATION!!! We are trying to keep it as Vanilla As possible but certain applications and customization's will be there to improve the usability and functionality. But nothing too drastic.
Please don't expect a fully working build straight away. We will have RIL (Network) Working amongst other things. ETA is not available but a beta release will be available As soon as we get things up and running and satisfied with the quality of OUR Work. We have not flashed it to our device(s)
yet but is working great with the emulator.
We will not settle for arguments and petty squabbling over things on this topic. Nor asking for ETA's and begging for fixes. We are very busy with this project and we want our work to be valued. If you are not satisfied with our big effort.
Please use another ROM or Make AOSP yourself. Eh?
Feel free to post any concerns and problems you face with it.
We are considering to make a different version to work with different GSM Bands so all ace users will be able to be use there Ace's whatever there region. Don't expect it for all regions when the European based release is available.
Feel free to press the thanks button, It will make my day. And thank EmoBoiix3 and fla.sh for there big contributions to the project and mine!
Please help us . If you do , we will be eternally grateful
EmoBoiix3 said:
Please help us . If you do , we will be eternally grateful
Click to expand...
Click to collapse
guys ask AOSP developers for other samsung galaxy phones .they might be able to help you....
hallowen said:
guys ask AOSP developers for other samsung galaxy phones .they might be able to help you....
Click to expand...
Click to collapse
We did use our brains and try to solve the issue ourselves. As this aosp rom is for the Ace community
We are trying to ask for help from others. We also asked in the Chef Central, Android forum. Could you point us to anyone?
Sent from my GT-S5830 using XDA App
hallowen said:
guys ask AOSP developers for other samsung galaxy phones .they might be able to help you....
Click to expand...
Click to collapse
We tried asking around Chef Central to no avail.....
Can u share the make file of Cooper from github?
letsurock said:
Can u share the make file of Cooper from github?
Click to expand...
Click to collapse
Which one ? Sorry , there's 2 makefile(s) here
If you want aosp rom, help us to make it possible
Sent from my GT-S5830 using XDA App
PM Android-Desire since he's made an AOSP himself, maybe he'll be willing to help out.
consegregate said:
PM Android-Desire since he's made an AOSP himself, maybe he'll be willing to help out.
Click to expand...
Click to collapse
His account has been disabled , and I hate him .
consegregate said:
PM Android-Desire since he's made an AOSP himself, maybe he'll be willing to help out.
Click to expand...
Click to collapse
hes already banned from xda few days ago by moderator because insulting/attacking other user (i think that particular user who being insulted by him is EmoBoiix3). theres no point in seeking help from such childlish behave guy like that. besides, that aosp rom his been bragged about all this time is just his saying, no proof of it even existed.
btw my advice would be pm-ing other user on other device forum who had already compiled and released their aosp rom here in xda. maybe they can help
EmoBoiix3 said:
Which one ? Sorry , there's 2 makefile(s) here
Click to expand...
Click to collapse
Both would be great
I meant to write that to see if he indeed had the rom.. so he's banned. Now, how about contacting trapacska? he's got a build working but without many functionalities but he should be able to give help somehow.
consegregate said:
I meant to write that to see if he indeed had the rom.. so he's banned. Now, how about contacting trapacska? he's got a build working but without many functionalities but he should be able to give help somehow.
Click to expand...
Click to collapse
+1
Good idea . /10char
letsurock said:
Both would be great
Click to expand...
Click to collapse
Which one do you want ?
Error
Code:
build/core/base_rules.mk:162: *** hardware/msm7k/libaudio: MODULE.TARGET.SHARED_LIBRARIES.libaudiopolicy already defined by device/samsung/cooper/libaudio
Possible Solution
Go to the Android/hardware/msm7k/Android.mk 'and remove from the line-qsd8k libgralloc and libaudio
Code:
msm7k_adreno_dirs: = $ (common_msm_dirs) boot qsd8k libgralloc libaudio
If this solves the error than
Another possible error that may occur after that
Code:
Buildinfo Target: out / target / product / cooper / system / build.prop
/ Bin / bash:-c: line 0: unexpected EOF on Reaching a `" '
/ Bin / bash:-c: line 1: syntax error: unexpected end of file
make: *** [out / target / product / cooper / system / build.prop] Error 1
make: *** Removing file `out / target / product / cooper / system / build.prop
Possible solution
Go to build / core / Makefile and
Code:
$ (If $ (ADDITIONAL_BUILD_PROPERTIES), \
$ (Hide) echo>> $ @; \
"#">> echo $ @; \
echo "# ADDITIONAL_BUILD_PROPERTIES">> $ @; \
"#">> echo $ @;)
$ (Hide) $ (foreach line $ (ADDITIONAL_BUILD_PROPERTIES), \
echo "$ (line)">> $ @;)
Next error occur that may occur
Code:
Checking API: checkapi-last
(Unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE value has changed from "100-Continue" to "100-continue"
******************************
You have tried to change the API from what has been Previously released in
an SDK. Please fix the errors Listed above.
******************************
make: *** [out / target / common / obj / PACKAGING / checkapi-last-timestamp] Error 38
Possible solution
Go to the external/apache-http/src/org/apache/http/protocol/HTTP.java and change this line "100-continue" to "100-Continue"
Code:
public static final String EXPECT_CONTINUE = "100-continue";
skynet28 said:
Error
Code:
build/core/base_rules.mk:162: *** hardware/msm7k/libaudio: MODULE.TARGET.SHARED_LIBRARIES.libaudiopolicy already defined by device/samsung/cooper/libaudio
Possible Solution
Go to the Android/hardware/msm7k/Android.mk 'and remove from the line-qsd8k libgralloc and libaudio
Code:
msm7k_adreno_dirs: = $ (common_msm_dirs) boot qsd8k libgralloc libaudio
If this solves the error than
Another possible error that may occur after that
Code:
Buildinfo Target: out / target / product / cooper / system / build.prop
/ Bin / bash:-c: line 0: unexpected EOF on Reaching a `" '
/ Bin / bash:-c: line 1: syntax error: unexpected end of file
make: *** [out / target / product / cooper / system / build.prop] Error 1
make: *** Removing file `out / target / product / cooper / system / build.prop
Possible solution
Go to build / core / Makefile and
Code:
$ (If $ (ADDITIONAL_BUILD_PROPERTIES), \
$ (Hide) echo>> $ @; \
"#">> echo $ @; \
echo "# ADDITIONAL_BUILD_PROPERTIES">> $ @; \
"#">> echo $ @;)
$ (Hide) $ (foreach line $ (ADDITIONAL_BUILD_PROPERTIES), \
echo "$ (line)">> $ @;)
Next error occur that may occur
Code:
Checking API: checkapi-last
(Unknown): error 17: Field org.apache.http.protocol.HTTP.EXPECT_CONTINUE value has changed from "100-Continue" to "100-continue"
******************************
You have tried to change the API from what has been Previously released in
an SDK. Please fix the errors Listed above.
******************************
make: *** [out / target / common / obj / PACKAGING / checkapi-last-timestamp] Error 38
Possible solution
Go to the external/apache-http/src/org/apache/http/protocol/HTTP.java and change this line "100-continue" to "100-Continue"
Code:
public static final String EXPECT_CONTINUE = "100-continue";
Click to expand...
Click to collapse
Thank you we are trying this now! You are a LEGEND!
skynet28 said:
Error
Code:
build/core/base_rules.mk:162: *** hardware/msm7k/libaudio: MODULE.TARGET.SHARED_LIBRARIES.libaudiopolicy already defined by device/samsung/cooper/libaudio
Possible Solution
Go to the Android/hardware/msm7k/Android.mk 'and remove from the line-qsd8k libgralloc and libaudio
Click to expand...
Click to collapse
Should the Android.mk be done like this ?
Code:
common_msm_dirs := libcopybit liblights libopencorehw librpc libstagefrighthw
msm7k_dirs := $(common_msm_dirs) boot
qsd8k_dirs := $(common_msm_dirs) libgralloc-qsd8k libaudio-qsd8k dspcrashd
msm7x30_dirs := liblights libgralloc-qsd8k librpc libaudio-qdsp5v2
msm7k_adreno_dirs: = $ (common_msm_dirs) boot qsd8k libgralloc libaudio
ifeq ($(TARGET_BOARD_PLATFORM),msm7k)
include $(call all-named-subdir-makefiles,$(msm7k_dirs))
else
ifeq ($(TARGET_BOARD_PLATFORM),qsd8k)
include $(call all-named-subdir-makefiles,$(qsd8k_dirs))
else
ifeq ($(TARGET_BOARD_PLATFORM),msm7x30)
include $(call all-named-subdir-makefiles,$(msm7x30_dirs))
endif
endif
endif
I tried it like this and I get a new error about libril , exact same message .
Thanks a ton, syknet28
Let's continue our work, team...
EDIT: New error
fla.sh said:
Thanks a ton, syknet28
Let's continue our work, team...
EDIT: New error
Click to expand...
Click to collapse
It's just errors , no rush , don't have to get paranoid .
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
memewarrior said:
Sup XDA, there is one question about porting the sailfish OS. I am guided by the official documentation, according to the latest guide on HADK - https://sailfishos.org/wp-content/u...OS-HardwareAdaptationDevelopmentKit-2.0.1.pdf
I encountered a problem with the point 7.2.1. When performing the rpm/dxd/helpers/build_packages.sh. there is installation and assembly of packages, but it breaks off when creating a middlevare, namely, the libhybris. Here is the complete log of the assembly - https://paste.debian.net/plain/997702
As I understood from the logs myself to build the libhybris, I need to use the compiler with C++11 support, but in the scratchbox2 the old version of the gcc-4.6.3 version is used, which does not understand the standart C++11. I tried to change the CFLAGS from "--std=gnu++11" to "--std=gnu++0x" , but the libhybris does not compile with the flag of the old standards.
What do you propose to do? How to update the compiler in a scratchbox2 target?
P.S. wrote it via google translate, dont be offended pls
Click to expand...
Click to collapse
Heyyo, the guide has a messed up sb2 section.
I can't load your Pastebin link but please check my thread here to see how I resolved the bad sb2 guide
https://together.jolla.com/question/172682/unknown-tag-systemd_requires/
Also, just in case you get stuck on 8.5 of that guide here's how I fixed that too
https://together.jolla.com/question...cregister-for-85-building-the-image-with-mic/