yashsingh1/xdaforums huggingface dataset:
[Galaxy Ace S5830 Android Development] Axel2033:
Please HELP)

log of errow

target Strip: sensorservice (out/target/product/cooper/obj/EXECUTABLES/sensorservice_intermediates/sensorservice)

Install: out/target/product/cooper/system/bin/sensorservice

prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/../lib/gcc/arm-linux-androideabi/4.4.3/../../../../arm-linux-androideabi/bin/ld: out/target/product/cooper/obj/SHARED_LIBRARIES/libmedia_intermediates/IMediaRecorder.o: in function .LTHUNK2:frameworks/base/include/binder/IInterface.h:44: error: undefined reference to 'android::ICameraRecordingProxy::asInterface(android::sp<android::IBinder> const&)'

collect2: ld returned 1 exit status

make: *** [out/target/product/cooper/obj/SHARED_LIBRARIES/libmedia_intermediates/LINKED/libmedia.so] Ошибка 1

make: *** Ожидание завершения заданий...
[Galaxy Ace S5830 Android Development] CallMeVentus:
Axel , camera is the number one problem the Galaxy Ace is facing

It might mean that you're missing a file that it references itself to
[Galaxy Ace S5830 Android Development] kevinkrs:
Send us your zip please. And the logcat.
[Galaxy Ace S5830 Android Development] pujitjuneja:
Camera is a problem in every build. ZTE blade, skate and all others to which it has been ported to
[Galaxy Ace S5830 Android Development] Wayland_ACE:
Send zImage or rom, please :)
[Galaxy Ace S5830 Android Development] djsky2011:
uploading to dropbox now, ill inbox u the link before someone does something stupid lol
[Galaxy Ace S5830 Android Development] slaid480:
hay wait wait might be aprop in VM heap size because when last time in cm7 i changed to 12 MB the phone hd the same problem I noticed too that init.rc need some modification
[Galaxy Ace S5830 Android Development] djsky2011:
this may help, its for galaxy 3http://review.cyanogenmod.com/#q,status:merged+branch:ics,p,001983ed0000291f
[Galaxy Ace S5830 Android Development] Axel2033:
cm9 :)

Please hepl me my team)
[Galaxy Ace S5830 Android Development] slaid480:
OK go go to work
[Galaxy Ace S5830 Android Development] free2live:
Any progress?

Sent from my mind
[Galaxy Ace S5830 Android Development] Cool_On3:
anyone have fix this?
[Galaxy Ace S5830 Android Development] free2live:
Great job

I am not not a big dev myself but i'm glad someone is working on this. If you think i can do something to help do not hesitate to ask. Maybe an alpha build will be ready by the end of the year...if more people get involved
[Galaxy Ace S5830 Android Development] kills999:
How about using files from compiled ICS from other ARMv6 devices like the optimus one,ZTE Blade,Huwaei Ideos.....Most of them have the same MSM7227 chipset as ours

EDIT:- check this out....

http://aosp.mikegapinski.cba.pl/?page_id=14

somebody managed to get a working port on the GT540 optimus with hardware acceleration enabled.....seeing this ICS should easily work on our ACE
[Galaxy Ace S5830 Android Development] daredj:
You should enable Wiki on github, we can explain how to work with the project!

Also, it should be better to merge all repos in one, maybe it's better work all togheter to bring ICS to our ACE!

Greetings!
[Galaxy Ace S5830 Android Development] Axel2033:
https://github.com/TeamHackAce
[Galaxy Ace S5830 Android Development] OiToBi:
Well sorry m NT dev bt still I loved GitHub name :))

Sent from Wherever I was last using XDA :]
[Galaxy Ace S5830 Android Development] slaid480:
axel2033 you just creat this github right ??
[Galaxy Ace S5830 Android Development] daredj:
Good Job!

We can start to bring ICS to ACE ;)
[Galaxy Ace S5830 Android Development] CallMeVentus:
Thanks for adding man :)

Btw am having errors with android/device/samsung/cooper/recovery_ui.c when using your device_cooper_cm9 config .
[Galaxy Ace S5830 Android Development] Axel2033:
I have it problem too
[Galaxy Ace S5830 Android Development] CallMeVentus:
The AOSP doesn't have this problem , but with libmedia instead .
[Galaxy Ace S5830 Android Development] slaid480:
when my bri will be back,I will tell him to upload the config file that he use to make ics aosp booting on his ACE;)
[Galaxy Ace S5830 Android Development] CallMeVentus:
Wow thaks Slaid !
[Galaxy Ace S5830 Android Development] slaid480:
no prop my bro;)
[Galaxy Ace S5830 Android Development] tomsons26:
New CM9 vendor

https://github.com/CyanogenMod/android_vendor_cm
[Galaxy Ace S5830 Android Development] CallMeVentus:
Thank you ! This will be beneficial to us .
[Galaxy Ace S5830 Android Development] lagloose:
Hello folks,

as i already said, i was busy this weekend. But seems that you guys were busy as a bee :-).

When i was back yesterday evening i took some hours to try a first compile with the CM9 ICS Sources using coolya's config files and ran almost exactly in the same problems as with AOSP. I think armv6 support is a major problem. Especially the audio and web modules obviously need special (armv6) processor instructions to complete compilation.

( @Axel: You already told me to include the armv6.mk file from GB Branch, but this didn't do it for me out of the box. Could you be more specific on what to change ?).

Additionally there are obviously some include files missing (i.e. LZO Module)...

Anyway, i will now have a look at 'our' new git repositories and see how they work. I think our major first goal should be to have a booting image...

Before i forget; during my waiting for compilation, i found this link on modaco, which i think can be helpful for us because the author ran into similar problems like we do...

http://android.modaco.com/topic/348898-ics-compiled-for-zte-blade/

To the people who wrote to me via PM. Thank you very very much for all your offers to help. If you want to know how to start, have a look here: http://wiki.cyanogenmod.com/wiki/Building_from_source and here: http://xdaforums.com/showthread.php?t=1354865 Please understand that we cannot give a 'programming tutorial' here. So concerning the basics, you are on your're own.

Last but not least: Please people don't ask for ETA !. The usual statement: It's done, when it's done...
[Galaxy Ace S5830 Android Development] CallMeVentus:
Try to comment out the file , since we won't use the compiled recovery.img
[Galaxy Ace S5830 Android Development] lagloose:
Next fix; external/webrtc for armv5 here:

https://github.com/lagloose/platform_external_webrtc

(How can i add it to TeamHackAce ?)
[Galaxy Ace S5830 Android Development] slaid480:
ask axeel2033,I think he can add it;)
[Galaxy Ace S5830 Android Development] lagloose:
Still stuck at creating OTA package...

I never used 'fastboot flash' with my ACE. So anybody can tell me, if it is safe to try to flash system.img and boot.img via fastboot ?
[Galaxy Ace S5830 Android Development] CallMeVentus:
The Ace does not have fastboot . If you have otapackage , do tell us . As in the .zip
[Galaxy Ace S5830 Android Development] traduz:
Make a flashable zip and people will test it :)

Just w8ing ^^
[Galaxy Ace S5830 Android Development] letsurock:
Try testing in Android Emulator
[Galaxy Ace S5830 Android Development] hero2003:
i've faild on unyaffs system.img

>unyaffs system.img

3 [main] unyaffs 3372 _cygtls::handle_exceptions: Exception: STATUS_ACCESS

_VIOLATION

911 [main] unyaffs 3372 open_stackdumpfile: Dumping stack trace to unyaffs.e

xe.stackdump

and attached it dumps.

i've tested on windows , need someone to test it on mac or linux maybe work on there.
[Galaxy Ace S5830 Android Development] Axel2033:
armv6-vtp

not v5
[Galaxy Ace S5830 Android Development] lagloose:
Ok, i've created a flashabe image using the dsixda package. It generated the following updater-script

---

show_progress(0.1, 0);

format("MTD", "system");

mount("MTD", "system", "/system");

package_extract_dir("system", "/system");

set_perm_recursive(0, 0, 0755, 0644, "/system");

set_perm_recursive(0, 2000, 0755, 0755, "/system/bin");

set_perm(0, 3003, 06755, "/system/bin/ip");

set_perm(0, 3003, 02750, "/system/bin/netcfg");

set_perm(0, 3004, 02755, "/system/bin/ping");

set_perm(0, 2000, 06750, "/system/bin/run-as");

set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluetooth");

set_perm(0, 0, 0755, "/system/etc/bluetooth");

set_perm(1000, 1000, 0640, "/system/etc/bluetooth/auto_pairing.conf");

set_perm(3002, 3002, 0444, "/system/etc/bluetooth/blacklist.conf");

set_perm_recursive(1002, 1002, 0755, 0440, "/system/etc/bluez");

set_perm(0, 0, 0755, "/system/etc/bluez");

set_perm(1002, 1002, 0440, "/system/etc/dbus.conf");

set_perm(1014, 2000, 0550, "/system/etc/dhcpcd/dhcpcd-run-hooks");

set_perm(0, 2000, 0550, "/system/etc/init.goldfish.sh");

set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");

set_perm_recursive(0, 0, 0755, 0555, "/system/etc/ppp");

set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor");

set_perm_recursive(0, 2000, 0755, 0755, "/system/vendor/bin");

set_perm_recursive(0, 2000, 0755, 0644, "/system/vendor/etc");

set_perm(0, 0, 0644, "/system/vendor/etc/gps.xml");

set_perm_recursive(0, 0, 0755, 0644, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/firmware");

set_perm(0, 2000, 0755, "/system/vendor/lib");

set_perm(0, 2000, 0755, "/system/vendor/lib/egl");

set_perm(0, 2000, 0755, "/system/vendor/lib/hw");

set_perm_recursive(0, 2000, 0755, 0755, "/system/xbin");

show_progress(0.1, 10);

show_progress(0.2, 0);

assert(package_extract_file("boot.img", "/tmp/boot.img"),

write_raw_image("/tmp/boot.img", "boot"),

delete("/tmp/boot.img"));

show_progress(0.2, 10);

unmount("/system");

---

Seems to me that it will only touch the system partition, so it should be not dangerous to try to flash this. What do you people say ?

(Just want to be shure, that it doesn't crash my recovery or anything else and send my device into Nirvana....)
[Galaxy Ace S5830 Android Development] djsky2011:
Do u need a volunteer then?
[Galaxy Ace S5830 Android Development] kills999:
it should be fine as long as system partition on the phone can fit everything! and download mode should work in any case
[Galaxy Ace S5830 Android Development] dragonnn:
And what about boot partition? I think it can brick you phone:confused:.
[Galaxy Ace S5830 Android Development] djsky2011:
as long as ur recovery img is fine, there shouldn't be a problem
[Galaxy Ace S5830 Android Development] CallMeVentus:
He was right to not use the recovery.img , because the custom keymapping file was commented out .

---------- Post added at 11:22 PM ---------- Previous post was at 11:21 PM ----------

The boot.img , at the worst case , will just cause reboots .
[Galaxy Ace S5830 Android Development] evil_penguin:
Great work !

Someone going to try ?

+1 for all developers involved ,great work !
[Galaxy Ace S5830 Android Development] lagloose:
Ok, flashing gave me: 'assert failed: write_raw image("/tmp/boot.img", "boot")' Status 7, bla bla bla....

After flashing i stayed in recovery and had a look via adb. Found the boot.img under /tmp and the following contens in '/tmp/recovery.log'

-- Installing: /sdcard/cooper_signed_120611_103326.zip

Finding update package...

I:Update location: /sdcard/cooper_signed_120611_103326.zip

Opening update package...

Installing update...

format: no mtd partition named "system"mount: no mtd partition named "system"minzip: Extracted file "/system/app/ApplicationsProvider.apk"

minzip: Extracted file "/system/app/BackupRestoreConfirmation.apk"

minzip: Extracted file "/system/app/Bluetooth.apk"

minzip: Extracted file "/system/app/Browser.apk"

minzip: Extracted file "/system/app/Calculator.apk"

... and so on...

and at the end:

....

write_raw_image: no mtd partition named "boot"

script aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")

assert failed: write_raw_image("/tmp/boot.img", "boot")xtracted file "/system/xbin/showmap"

minzip: Extracted file "/system/xbin/showslab"

minzip: Extracted file "/system/xbin/sqlite3"

minzip: Extracted file "/system/xbin/ssh"

minzip: Extracted file "/system/xbin/strace"

minzip: Extracted file "/system/xbin/su"

E:Error in /sdcard/cooper_signed_120611_103326.zip

(Status 7)

Installation aborted.

---

As i already said, i am not a ROM-Cook :confused:

Any ideas ?
[Galaxy Ace S5830 Android Development] CallMeVentus:
It's because the boot.img is over 4MB , try another boot.img or repack your current boot.img to make ir smaller
[Galaxy Ace S5830 Android Development] djsky2011:
repack is a better idea, careful of over compressing tho
[Galaxy Ace S5830 Android Development] Axel2033:
Sorry now I have some problems with internet I think you han use it

astboot -w

fastboot flash boot boot.img

fastboot flash system system.img

fastboot reboot

for flash images
[Galaxy Ace S5830 Android Development] dragonnn:
Axel2033 i think this wouldn't work because ace doesn't have fastboot.
[Galaxy Ace S5830 Android Development] djsky2011:
only htc and most non samsung devices use fastboot. A flashable img is what we need
[Galaxy Ace S5830 Android Development] lagloose:
Repack? How exactly? I used dsixda for cooking. The only thing i see is taking some files out of the boot.img. Or is there a way of better compression?
[Galaxy Ace S5830 Android Development] djsky2011:
ok in that case what is the current size of the boot. img, we can remove some items... u should message Jusada he is an expert in ROM cooking, dunno if he uses dsixda though
[Galaxy Ace S5830 Android Development] jusada:
You called? And thanks for the kind words. Right, so what's the problem and how can I help? I will warn my Ubuntu is down right now, upgraded my system and having driver issues. But use windows for most things anyway.
[Galaxy Ace S5830 Android Development] lagloose:
Thanks for youre help jusada :)

Situation is, that i have finished an AOSP compilation of ICS. No doubt that there are a lot of files missing, but my (our) first goal is to have a first boot. I created a flashable image by using dsixda package. But flashing gave me an 'assert failed' while trying to flash the kernel. Obviously this can happen, when the boot.img file is bigger than 4 Mb.

I will upload the image and send you the link via PM. Hopefully you can help us.... :)
[Galaxy Ace S5830 Android Development] jusada:
what kernel have you used? I believe emoboiix had a simular issue with aosp gb, I'm unsure if he found a solution.
[Galaxy Ace S5830 Android Development] dragonnn:
What about making a flashable image for ODIN? The boot.img in for example 2.3.4 KPH have about 6MB.
[Galaxy Ace S5830 Android Development] slaid480:
an ODIN flashable version will delete everthing even cwm that can save from brick
[Galaxy Ace S5830 Android Development] dragonnn:
slaid480 what about making a onepackage firmware for ODIN with only system.rfs and boot.img (the original package have "amss arm11boot boot.img csc.rfs mibib oemsbl qcsbl recovery.img	system.rfs"). Will ODIN allow to flash this package?
[Galaxy Ace S5830 Android Development] tomsons26:
Its not the boot image after setting it to use flash_image it flashed but after that OUR BIGGEST and BESTEST FRIEND ERROR (STATUS 7) crawled from its cave

The only known solution for Status 7 is installing the newest stock firmware available

And for the GPU, EGL and chipset libs hope this site might help

https://developer.qualcomm.com/
[Galaxy Ace S5830 Android Development] jusada:
looking at it I don't think its the boot img. on cwm5 I'm getting a meta-inf error, witch cmw are you using? If I alter the boot img I get the status 7 error.
[Galaxy Ace S5830 Android Development] djsky2011:
your updater-script is trying to put boot.img somewhere it shouldnt go

use this script to flash

ui_print("Flashing Boot.img...");

package_extract_file("boot.img", "/dev/block/mmcblk0p5");
[Galaxy Ace S5830 Android Development] CallMeVentus:
But we don't have a bootloader !

TARGET_NO_BOOTLOADER := TRUE
[Galaxy Ace S5830 Android Development] CallMeVentus:
It's supposed to be in a temp directory before you copy the boot.img over .

I solved my Status 7 problems using the CM7 boot.img
[Galaxy Ace S5830 Android Development] jusada:
First thing I tryed. But then I not getting the status 7 issue he spoke of.
[Galaxy Ace S5830 Android Development] CallMeVentus:
What error did you get ?
[Galaxy Ace S5830 Android Development] lagloose:
Hi,

Here's what i found out:

- the assert error seems to be NOT dependend on the size of the boot.img. For testing, I took out some big libs so boot.img was < 4Mb but still assert error (Some people mentioned, that the 'assert error' depends on the version of the used update-binary)

- the boot.img i delivered was definitely a boot.img because i could extract and repack it with dsixda without any problem

- the kernel itself was the kernel i had after compilation in my 'out' folder

I than extracted Grif's CM 7.1 and had a look at this files. I took the zImage and updater-script from Grif's ROM an recreated a new flashabe Image. It flashed without any problems. I did not reboot and stayed in recovery. adb shell -> mount /system -> cd /system/lib -> ls ... (all libs there). cd /system/bin -> ls ... (all binaries and links were correct).

Reboot while connected via USB. 'adb logcat'. Result:

--- waiting for device ---

- exec '/system/bin/sh' failed: No such file or directory (2) -

A little irritated i rebooted to recovery and went back to adb shell. Mounted /system looked into /system/bin and sh was there as a link to mksh. Typed ./mksh. Result 'no such file or directory' ??? Could this have something to do with ext4 ?

All a little bit fustrating right now. Never thought that this is such complicated. :(

Another question to the people who created a cooper device repository on git; while i had a look at the files in Grif's CM 7.1 i noticed that the '*.ko' Kernel modules like i.e. fsr.ko are a lot smaller than those in the repositories. The prebuild/modules/fsr.ko in the repositories is nearly 1,6 Mb in size, while the fsr.ko in Grif's CM7 is just 364 kB. (That was BTW the reason why the boot.img got such big...) Why is that ?

I could upload my last flashable image if you like, so everyone could try to find a solution..
[Galaxy Ace S5830 Android Development] tomsons26:
Sure upload it

boot size does not matter Axel's latest cm7 build boot is 4,34 MB (4*554*752 bytes) and yours 4,25 MB (4*464*640 bytes) but axel's flashes and boots

- exec '/system/bin/sh' failed: No such file or directory (2) -

Known issue got it too system did not FLASH only format if you run a cwm backup the system partition is empty

I don't understand much about android but the update script, the system is in MTD, the kernel(ramdisk code) thinks that the system is located "EMMC", "/dev/block/stl12", "/system"
[Galaxy Ace S5830 Android Development] djsky2011:
Yeah please upload the latest zip
[Galaxy Ace S5830 Android Development] jusada:
Sorry, I worded that badly. The error I get with the unaltered flash file is not status 7 if I change the boot image then I get status 7.
[Galaxy Ace S5830 Android Development] tomsons26:
We need to contact Kolja and get his proof of concept build code

The Update binary is for ASOP recovery replace it with cwm binary ERROR Status 7 gone!!!!!!!!!!!

Now it FLASHES!!!
[Galaxy Ace S5830 Android Development] lagloose:
Anyway, here's the link to my latest flashabe but NOT WORKING image.

http://www.4shared.com/file/0rVp81wq/cooper_signed_120711_140223.html
[Galaxy Ace S5830 Android Development] CallMeVentus:
Does adb logcat work ? I can try and debug it
[Galaxy Ace S5830 Android Development] tomsons26:
I succesfuly flashed the old build the system patition actualy contains full data :D:cool:;):p, but the boot.img sucks BOOTLOOP:confused::(:mad:
[Galaxy Ace S5830 Android Development] djsky2011:
Are u being serious, can u stay connected to ADB and do a logcat to find out whats causing the bootloop?. This is a breakthrough if what ur saying is true
[Galaxy Ace S5830 Android Development] tomsons26:
Nope logcat does not work it loks like adb is not incloded in kernel (sbin/ missing adbd)
[Galaxy Ace S5830 Android Development] lagloose:
Do you really have a bootloop ? Device restarts ?

or do you just see the white 'ANDROID' on the screen ?
[Galaxy Ace S5830 Android Development] tomsons26:
the white ANDROID count's as bootloop i have had it on stock too, just flashed my cm7 to check if i didn't screw up the phone

To prove that im not trolling an full CWM backup pic attached

Update on latest build

Latest build does not even bootloop stuck at Samsung www.samsung.com screen or at black screen for 2 minutes and then the phone reboots

Im giving up, once someone has a booting build send it to me i will diffidently test it for now im going back to CM7
[Galaxy Ace S5830 Android Development] CallMeVentus:
Okay , we need to repack that boot.img
[Galaxy Ace S5830 Android Development] lagloose:
Hmmm,

maybe we should change to another way...

What about taking a working image of Grif's CM7 and only replace the files which are necessary for ICS. (framerork, framework-libs, apps, fonts etc) ? If this would work, perhaps we could even get out of some hardware issues, which are to be expected anyway, if we use the pure output of the compilation...

What do you think ?
[Galaxy Ace S5830 Android Development] djsky2011:
On the first build did u wipe cache and do a factory reset before flashing... the adb issue could be drivers not loading properly. i have been scratching my head at this all day, must be something we are missing

---------- Post added at 07:06 PM ---------- Previous post was at 06:54 PM ----------

are u creating a flashable zip for that? u suggesting using boot.img from grif's:confused:
[Galaxy Ace S5830 Android Development] CallMeVentus:
This was what I did to get AOSP working:

-Copy the CM7 libs over , but DO NOT OVERWRITE existing libs

-Same thing for /system/bin files

-Same thing for /system/xbin files as well
[Galaxy Ace S5830 Android Development] kevinkrs:
Are you running ice cream sandwitch now?

I have try it but it does nothing, I see only "Android" nothing more.
[Galaxy Ace S5830 Android Development] tomsons26:
AOSP gingerbread right

if so we need ics libs

Hope this helps

Here is ZTE blade ICS ASOP(Galaxy Mini Chipset)

https://github.com/t0mm13b

At least there's boots and runs and basic features work

http://android.modaco.com/topic/348898-ics-compiled-for-zte-blade/page__st__620(Read the whole topic)
[Galaxy Ace S5830 Android Development] Wayland_ACE:
Latest build does not mount /dev/block/stl12 to /system dir. Therefore we cant do logcat, boot etc...
[Galaxy Ace S5830 Android Development] djsky2011:
that's what i was thinking, because logcat doesnt work... an edited updater-script is needed.. i have faith it will boot. Come one guys get us a copy with logcat working so i can start debugging :)
[Galaxy Ace S5830 Android Development] Wayland_ACE:
I put boot.img from another ROM (CM 7.2 KANG) and /system dir is mounting now. I check it by cmd:

adb pull /system/bin ./t

and it start to copy files, BUT

then I try to execute:

adb shell

I still have error:

- exec '/system/bin/sh' failed: No such file or directory (2) -

then:

adb shell /system/bin/sh:

/sbin/sh: /system/bin/sh: not found

So I decided to copy /system/bin folder from my own build and logcat works. Then I copied /system/framework to I decided to see logcat - is starting to dexopt java libraries

Now I have a error:

Library media_jni not found; tried [/vendor/lib/libmedia_jni.so, /system/lib/libmedia_jni.so

P.S sorry for my english grammar :))

update:

I copied /system/lib folder to and error disappears.

Have a lot of errors:

W/SurfaceFlinger( 154): ANDROID_WAIT_FOR_FB_WAKE failed (Bad file number)

W/SurfaceFlinger( 154): ANDROID_WAIT_FOR_FB_SLEEP failed (Bad file number)

---------- Post added at 08:28 PM ---------- Previous post was at 07:58 PM ----------

So, about last error:

I looked to surfaceflinger code and found 2 consts:

But my ACE device:

Any ideas how to create them?