yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] Derrian:
river@river:~/android$ make sync
cd /home/river/android/system; repo sync -j16
Fetching projects: 69% (170/246) remote: Counting objects: 28, done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 15 (delta 6), reused 13 (delta 4)
Fetching projects: 72% (178/246) fatal: The remote end hung up unexpectedly
Unpacking objects: 100% (15/15), done.acking objects: 46% (7/15)
From git://github.com/CyanogenMod/android_packages_apps_Bluetooth
8ec45f2..6d0ad4e gingerbread -> github/gingerbread
Fetching projects: 84% (207/246) remote: Counting objects: 200, done.
remote: Compressing objects: 100% (69/69), done.
remote: Total 165 (delta 96), reused 117 (delta 48)
Receiving objects: 100% (165/165), 16.32 KiB, done.s: 0% (1/165)
remote: Counting objects: 11, done.
remote: Compressing objects: 100% (3/3), done.
remote: Total 6 (delta 3), reused 6 (delta 3)
Resolving deltas: 100% (96/96), completed with 23 local objects.
remote: Counting objects: 15, done.
remote: Compressing objects: 100% (7/7), done.
remote: Total 8 (delta 6), reused 3 (delta 1)
Unpacking objects: 100% (6/6), done.
From git://github.com/CyanogenMod/android_packages_apps_Trebuchet
b4b057a..cbe0a6f ics -> github/ics
From git://github.com/CyanogenMod/android_packages_inputmethods_LatinIME
5c49e8c..e9dcfc7 gingerbread -> github/gingerbread
Unpacking objects: 100% (8/8), done.npacking objects: 75% (6/8)
From git://github.com/CyanogenMod/android_packages_apps_Settings
978aeb5..775bbd3 gingerbread -> github/gingerbread
Fetching projects: 99% (244/246) fatal: The remote end hung up unexpectedly
error: Cannot fetch teamhacksung/android_packages_apps_Filemanager

error: Exited sync due to fetch errors
make: *** [sync] Error 1
river@river:~/android$ make sync
cd /home/river/android/system; repo sync -j16
Fetching projects: 74% (182/245) fatal: The remote end hung up unexpectedly
Fetching projects: 99% (243/245) fatal: The remote end hung up unexpectedly
error: Cannot fetch teamhacksung/android_packages_apps_Filemanager

error: Exited sync due to fetch errors
make: *** [sync] Error 1
river@river:~/android$

guy's , any idea why I'm erroring out here?
[Galaxy Tab  Android Development] Neleor:
^I'm getting the exact same, hopefully I got all the commits when I synched this afternoon. I'll try building.
[Galaxy Tab  Android Development] devilng:
hi everybody! at first, thanks to the thread-starter for the great instructions. I really want to make a rom, but I have a problem. there is no possible way to load recovery on my device, becauce it felt down and crashed something inside( so I will be very glad for somebody to make a flashable TAR for odin because now I can flash only via cable. also, I want to know how to do that by myself if anybody knows. pm is preferred bacause of thread requirements. thanks for attention
[Galaxy Tab  Android Development] 1sthandy:
just try this: Install Guide

the new kernel have no recovery! yet

Greetings
[Galaxy Tab  Android Development] humberos:
@diz,

Which kernel did you install and why it don't have recovery?
[Galaxy Tab  Android Development] Derrian:
got the sync to work, had to remove

<project path="packages/apps/Filemanager" name="teamhacksung/android_packages_apps_Filemanager" />

From the manifest.xml and from the project list.
[Galaxy Tab  Android Development] Disconn3ct:
Keeps bombing on me:

E/libEGL ( 175): eglGetDisplay:139 error 300c (EGL_BAD_PARAMETER)
E/libEGL ( 175): eglInitialize:155 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 175): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
E/libEGL ( 175): validate_display:188 error 3008 (EGL_BAD_DISPLAY)
F/libc ( 175): Fatal signal 11 (SIGSEGV) at 0xdeadbaad (code=1)
I/DEBUG ( 114): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 114): Build fingerprint: 'samsung/cm_galaxytab/galaxytab:4.0.3/MR1/eng.dis.20120113.223608:eng/test-keys'
I/DEBUG ( 114): pid: 175, tid: 176 >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 114): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad
I/DEBUG ( 114): r0 deadbaad r1 00000001 r2 a0000000 r3 00000000
I/DEBUG ( 114): r4 00000000 r5 00000027 r6 00000000 r7 00000000
I/DEBUG ( 114): r8 100ffeb0 r9 40025490 10 0000fe78 fp 0000fc00
I/DEBUG ( 114): ip ffffffff sp 100ffd28 lr 40044f79 pc 40041694 cpsr 60000030
I/DEBUG ( 114): d0 5f4441425f4c4744 d1 43faf00000000049
[Galaxy Tab  Android Development] dizgustipated:
Kindly send me your zip..
[Galaxy Tab  Android Development] dizgustipated:
I am unsure exactly which kernel it was.

I got it directly from cdesai.

Do you have recovery?

No data stats here either ;(

If you have a source, before the two stage init, and before it had to be a bootimg, could you kindly send?

I wish to revert back to using zimages

PS

In your screenshots, which from are you using?
[Galaxy Tab  Android Development] humberos:
Hey!

You can use our source (at github) for build boot.img or zImage.

boot.img

Just run build.sh script

zImage

You have to update initramfs path in p1_cm9_defconfig file.

After, type the follow commands (in kernel folder):

$ make -j4 ARCH=arm p1_cm9_defconfig

$ make -j4

You can get zImage file into Kernel/arch/arm/boot/zImage

About my screenshot, I did it on my own CM9 (compiled using our github).

I made a new recovery, removed sdcard/android wipes and included battery stats. I will upload it soon.

If you want something from me, just yell!
[Galaxy Tab  Android Development] 1sthandy:
i get this Error by sync

Fetching projects: 100% (244/244), done.
fatal: This operation must be run in a work tree
Syncing work tree: 100% (244/244), done.

error: device/google/accessory/arduino/: device/google/accessory/arduino checkout 09f89c2c101b1e1fe85010e5e48404a3f01eb644
make: *** [sync] Error 1
[Galaxy Tab  Android Development] stimpz0r:
ahhh damn! i completely forgot about that step. explains why the kernels weren't working after i resynced the kernel / initramfs source.

anyway, off to mess around again. :)

EDIT: hmm im getting the same as Disconn3ct, and its what ive got the last few times (services crapping out constantly)...

running make clean in the main directory (using diz's Makefile) doesnt clean out the out/ directory, so i changed directory to system and run a make clean and it cleaned it out... i dont think it could be anything else that would be causing these errors so i will try a rebuild overnight and see if it makes a difference.
[Galaxy Tab  Android Development] ayysir:
i have a boot.img that works courtesy of svetum compiling it

seems booting problems stems from rom issues now. But running cm9 with no problem with recovery
[Galaxy Tab  Android Development] stekarson:
Maybe a bit "offtopic" but I've been wondering for a long time now - "make bacon" - what does it do and why is it called that?
[Galaxy Tab  Android Development] dizgustipated:
Seems the Supplied boot.img has recovery.

The issue is on my end.

I am unable ,do to ram issues, to create a bacon zip.

I've had to write the updater script half blind. It was okay for a zImage, but the new boot.img is unique.

So if someone could kindly send me or pastebin their updater script created by make bacon or make otapackage, I'll set the recovery straight, as the updater script seems the issue.
[Galaxy Tab  Android Development] duhovnikov:
Well, all goes to humberos :) I just used his github sources and compiled it (known as svetum @ irc)
[Galaxy Tab  Android Development] ayysir:
With your boot.img I was able to make a signed zip including the boot.img and redrebel's compiled build.

Later today ill up the zip in the irc to see if it works from cm7 or another rom to cm9
[Galaxy Tab  Android Development] devilng:
to 1sthandy. no guy. I'm not on new kernel or so on. there is problems with my own galaxy tab. it crashed and I can't boot it into recovery. at all. so can anybody help?
[Galaxy Tab  Android Development] reddog69:
boots back to recovery

mine compiles fine but it boot back to recovery i would appreciate any guidance
[Galaxy Tab  Android Development] reddog69:
help

i have compiled diz and straight cm9 and diz boots back to recovery and straight cm9 boots to black screen any advice guys.noticed the connect error is fixed
[Galaxy Tab  Android Development] priyana:
Hi Humberos,

for the uninitiated like me, how do we incorporate that recovery into the build?
[Galaxy Tab  Android Development] stimpz0r:
you need to download the kernel source and initramfs source from sgt7 github and compile the kernel to make that work, check out cdesai's thread for links.

in other news, i finally compiled a working version! the latest sync + a make clean in the system directory got me a working build! :D

for those of you who want a quick and easier way to remove Phone.apk (to stop the constant com.android.phone error), i simply did the following after make build:

make snapshot
cd snapshot/current/system/app
rm Phone.apk

and then, no error!

ive only had a few minutes to test out the latest build, but here are a few things ive noticed:

touchscreen seems to be less responsive

sound does not work (tested in Google Music and by setting alarm tones)

brightness control doesnt work

no google apps (need to find a new version of gapps)

external sd card doesn't mount

red borders

gallery stops working after first use (images disappear)

and now for a list of things that do work (that i've tested):

wifi

rotation

recent apps

UPDATE: it seems after the gallery stopped working, the touchscreen started working a lot better. will look in to that later on.

also planning to try a fresh built humberto kernel, will report when xda comes back from its darkness. :)
[Galaxy Tab  Android Development] Jal84:
Hi all,

I managed to build the ROM over night, but it doesn't boot. I followed all the steps from 1 to 8 (skipped steps 5 and 6a)... then flashed. I have the P1000, and I read somewhere that the default zImage is for P1000.

Anybody managed to boot ?

Will try to post a logcat from home tonight.
[Galaxy Tab  Android Development] Jal84:
Here's the logcat

http://pastebin.com/8eHHvvtE
[Galaxy Tab  Android Development] Disconn3ct:
"me too"

I think there is something wrong with the repo, but I'm finishing my new -really- clean build (make clean ; rm -rf .ccache ; ccache -C ; cd system ; make clean) so we'll see..

(Diz pm'd me to suggest a full fresh clean build & try again. he also suggested grabbing the vendor/cm stuff from github as a zip, which I did)

Update: Just finished the build, whee! same error though.

I/DEBUG ( 114): pid: 212, tid: 213 >>> /system/bin/surfaceflinger <<<
I/DEBUG ( 114): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr deadbaad

(Same with 'bacon' so at least that's something.)
[Galaxy Tab  Android Development] jiminitaur:
diz, I'd like to take a moment to let you know that I think you and everyone who supports your little 'experiment' by keeping zips off the board are grade A a-holes.

All I wanted was to try the ROM and see how stable it is. It should take me a download and ten minutes, but no, I can't without potentially hours of work and wait, because you have taken it upon yourself to tell people that they aren't doing enough, aren't independent enough, aren't renaissance enough, or whatever.

Saying f everyone who doesn't conform to your definition of independence is not cool, and 'doing it for their own good' is a poor excuse, so f you back.
[Galaxy Tab  Android Development] o_tiger:
Sure it would be nice to take and try! But I personally prefer that real developers do their work behind closed doors. So they don't have to support alpha builds. I hope they will make a better progress in same time. This is better for us! Also in this tread I have learned a lot! Keep on going!
[Galaxy Tab  Android Development] Disconn3ct:
..because CLEARLY absolutely nobody would ever take an alpha and start screaming for support. ESPECIALLY not someone as polite, undemanding and nice as this guy.

</sarcasm>

Want to try it out? Do some reading. There are no fewer than 3 different builds floating around, plus a few more hidden in the threads. I'd be very surprised if 10 minutes of work (its obvious you are a slow reader) didn't turn up at LEAST 8 different downloads you could try. Guys like you are the -reason- the builds aren't being posted publically..
[Galaxy Tab  Android Development] Andy:
Well, lets all feel sorry for you because you can't have ICS. Aww...

How awful it must be, to be you.

If you want to try it, compile it yourself. The instructions are very clear, its very easy to do. But then again, you just want 10 minutes of work, not the knowledge & understanding of how these things are put together.

If your too lazy to learn, or even search then quite frankly you shouldn't even be on XDA.
[Galaxy Tab  Android Development] Hybridesque:
I gave it a go with the CM9 thread before this thread tipped up, making up a virtual Ubuntu 11.10 machine and getting the repo sync'd etc.. but I didn't feel comfortable at all with it, so I've resigned myself to waiting.
[Galaxy Tab  Android Development] Derrian:
Lol. Wow. Little cry baby wants everything handed to him on a plate.

People seem to forget, this is XdaDevelopers. Not XdaUsers.

This site is and always will be about the developers. It is their playground to share ideas and creativity.

It is also our playground to a lesser degree, a playground where we can come and LEARN, and to enjoy what the devs do decide to share with us. When THEY are ready.

So don't come here *****ing like a spoiled child because diz and the other devs are not prepared to release a PRE-RELEASE from that even even ready to be called an alpha version.

It's not "I want, give it to me."
[Galaxy Tab  Android Development] stimpz0r:
hey has anyone here also built a recent version of cdesai's cm9 and can tell me if the sound works or not? i see by the OP in the thread that it is mentioned it works, and i cant remember for the life of me whether i noticed it working or not when i did my last build before i started on this project. it also seems that the booting version i had doesnt boot anymore.

i ask this because i am looking into ways to get audio working, and i wanted to see what the differences would be between the versions. i cant personally see any at the moment (drivers all look the same on both versions), but i could be wasting my time looking for them if the te4m's version doesnt have working sound either.

in other news, i compiled humberos kernel / initramfs and used it with my working build. not only does it work, but it seems to make bluetooth work better than the supplied image. i can also confirm that data stats work on these kernels, and recovery as well.

@humberos will the newer recovery allow restorations of older recovery nandroid backups? i ask this because i have a nandroid backup of ics alpha 3 (which i use as my daily driver due to sound working on it) and it didnt seem to restore the backup properly. i had to flash your alpha 3 kernel and use the old recovery to get it to restore properly. if thats not supposed to happen then at least you know someones tested nandroid restores :)
[Galaxy Tab  Android Development] rafaeker19:
i got the following error trying to sync, i have tried changing to https in manifest.xml.

but i got the same error, also trying to add -f command when syncing.

fatal: Not a git repository: '/media/AOSP/cm9/.repo/projects/bionic.git'
Fetching projects: 42% (104/247) fatal: Not a git repository: '/media/AOSP/cm9/.repo/projects/bionic.git'
Fetching projects: 88% (218/247) error: Cannot fetch CyanogenMod/android_bionic
Fetching projects: 90% (223/247)
error: Exited sync due to fetch errors
[Galaxy Tab  Android Development] adi6262:
any one experiencing constant SD card un-mounting ?

vids and photos from gallery and songs from music app disappearing ?

(re appears after unmounting and mounting SD card again )
[Galaxy Tab  Android Development] Derrian:
You need to delete bionic.git and re-sync
[Galaxy Tab  Android Development] dizgustipated:
Sound, audio recording and dsp manager (currently only tested with music) voodoo sound and audio effects all work in this build.

Ive also placed global menu options
[Galaxy Tab  Android Development] Jal84:
Hi All,

Just got these errors while building again with a fresh sync

http://pastebin.com/826CrFsZ
[Galaxy Tab  Android Development] Derrian:
Bah XD

Hey Diz, I'm still unable to get a boot, even using HumberOS' precompiled Zimage

[logcat] http://pastebin.com/HVq3GujG

Do you have any ideas?
[Galaxy Tab  Android Development] stimpz0r:
hmm thats weird, the last two builds ive done (the latest being a sync/build from last night) have no working audio. logcat gives me these results:

12:32:01.457 Error AudioFlinger 137 createTrack_l() Bad parameter: sampleRate 44100 format 1, channelMask 0x00000001 "for output 0xffb8 with format 1
12:32:01.457 Error AudioTrack 225 AudioFlinger could not create track, status: -22
12:32:01.497 Error SoundPool 225 Error creating AudioTrack

i also noticed this during boot, which could be part of the explination:

21:47:03.375 Info AudioFlinger 113 AudioFlinger's thread 0x104a8 ready to run
21:47:03.375 Warning AudioFlinger 113 Thread AudioOut_1 cannot connect to the power manager service

also in regards to the global menu options, none of the reboot options seem to work correctly for me (they all reboot back to system).
[Galaxy Tab  Android Development] dizgustipated:
I updated the git today

;)

Recovery:

I'm building a new kernel now,

recovery will be apart of it

Sorry my updates are kinda slow,

But after each change I do a make installclean && make clean && make clobber

Maybe overkill, but I like it super clean for each build.

And we all know my Dino of a comp moves slow!
[Galaxy Tab  Android Development] stimpz0r:
yeah i usually flash a latest humberos kernel on after i update. bluetooth works better with that kernel, but still doesnt pair with my computer (which isnt a bother for me as i dont use bluetooth anyway :) ).

i didnt know about installclean and clobber, so i think ill try that one tonight and clean build, perhaps that will make my audio work again. ;)

im building on a dual core 1.8 with 2gb of ram, takes over 5 hours a build... im getting a free pc from work soon (p4 2.8ghz with 1gb ram) so my build times will probably nearly double, but itll be a dedicated build machine so i wont be worried about how long it takes or when i have to do it ;D
[Galaxy Tab  Android Development] Derrian:
It might not be all that bad, I build on a p4 3.2ghz with only a gig of ram, the only time the build really takes a long time is if I delete the repo and start completely clean.
[Galaxy Tab  Android Development] rafaeker19:
i got the following problems trying to use the commands (make bacon, sync, init)

grep: build/target/board/generic/recovery.fstab: File or Directory not Found
o «out/target/product/generic/system/bin/lsof»
[Galaxy Tab  Android Development] stimpz0r:
i usually start completely clean whenever i build to make sure that nothing will conflict, although i only found out the way to truely make it clean off diz yesterday.

which brings me to my next point. i now have working audio! all the clicks and sounds are working perfectly! :D

i used diz's method:

make installclean && make clean && make clobber

and its working fine! but there is something else i noticed, and changed before i did my make build. when looking at Android.mk in the device/samsung/galaxytab/libaudio directory, i noticed something at the top of the file that bugged me:

ifeq ($(TARGET_DEVICE),[B]vzwtab[/B])

when i was building i noticed a message about there being no recovery files for TARGET_DEVICE galaxytab, so i stopped the build, made clean using diz's method above, and commented out the ifeq line and its corresponding endif at the bottom of the file and did a make build again.

im not entirely sure if this was infact the exact reason for why it worked, it simply could've been the proper clean, but in a programming sense, the whole file, and in fact the following files:

libcamera/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)
libhwcomposer/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)
liblights/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)
libs3cjpeg/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)
libstagefrighthw/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)

would be ignored due to our TARGET_DEVICE being galaxytab and not vzwtab.

anyway, main thing is it works now! so ive got my daily driver now. :D
[Galaxy Tab  Android Development] cdesai:
^^LOL, that's my bad, n then even diz didnt see it, nobody did till now xD
[Galaxy Tab  Android Development] dizgustipated:
Sorry!

configurations I got from jt1134 githib, ill attend to it when I get back
[Galaxy Tab  Android Development] eaut:
the same is also in

device/samsung/galaxytab/sec_mm/Android.mk:ifeq ($(TARGET_DEVICE),vzwtab)

not sure what it does though
[Galaxy Tab  Android Development] stimpz0r:
haha oh well at least im glad to have contributed in some way, even if it is a small one :)

theres another change that was fixed already in the te4ms build that was picked up by spanner3003, in device/samsung/galaxytab/galaxytab.mk:

- frameworks/base/data/etc/android.hardware.telephony.[B]cdma[/B].xml:system/etc/permissions/android.hardware.telephony.[B]cdma[/B].xml \
+ frameworks/base/data/etc/android.hardware.telephony.[B]gsm[/B].xml:system/etc/permissions/android.hardware.telephony.[B]gsm[/B].xml \

i found it when i was searching today for the fixes that spanner3003 and sbradymobile made, so i could add them to my current version. im going to build with their fixes and see how it goes.

thats weird, i didnt pick up on that one when i grep -R'd the directory for vzwtab, good find as well :D
[Galaxy Tab  Android Development] interloper:
Best thread ever!
[Windows Mobile Development and Hacking General] ezorla:
Hello there!

I have been trying to cook a ROM for my LG Fathom. I am using ervius visual kitchen aka LG Kitchen 2.3 First of all, I have general computer skills. I have updated firmware and stuff. But to be honest, I am new into "cooking ROM."

Well, my problem is;

When I use, latest Ervius kitchen (12.6.3), I click dump nbh,nb payload and I select payload file that I have created by OSNBTOOL from original rom.bin file. It works some then gives me an error;

h t t p ://img13.imageshack.us/img13/9453/1263bo.jpg

It tells me I should have a ruu signed nbh. But unfortunately I dont have it. And I have no idea how to obtain it. I have original .bin ROM file (Actually it is decrypted)

When I try to use an older version of the kitchen which is prepared for direct cooking, (here everything needed for cooking is prepared according to author) I am getting another message;

h t t p://img249.imageshack.us/img249/2095/1082n.jpg

So, my questions can be idiotic since I have no real experience. What is wrong here?

I am using a windows 7 64bit machine. Visual C 2008 and other stuff is installed. I tried with windows xp by virtual machine, but no success.

Any help would be appreciated!
[Windows Mobile Development and Hacking General] spocky12:
Lg roms are a bit special, and can't be extracted like it's done on htc phones. Try using my kitchen (link in my signature).
[Windows Mobile Development and Hacking General] ezorla:
Hi spocky i have Tried your "ready" Kitchen but the Resultat is the Same..

I have Mentioned AnD uploaded a Photo of ist Here. Maybe i Should reinstall Windows..
[Samsung Galaxy Nexus] mfdemicco:
I can't find any.
[Samsung Galaxy Nexus] IN8skillz:
I think IMoseyon has a lean kernel. Most likely posted on root, tho I haven't used it.
[Samsung Galaxy Nexus] @rbiter:
Hardly any for gsm also. Part of the reason I'm sure is developers have access to 4.0.3 so why waste time on point 2 when the latest is around the corner.