yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] cantIntoCode:
Just updated from the nightly yesterday. Just some feedback:

Most things seem to be working great for me. I don't really use the camera or most of the other things the phone has except to call/text, mobile internet and to play some games. On gameloft games the cut scenes are laggy but thats nothing to worry about, maybe just something that can be fixed in CM7. Battery drain isn't terribly bad but it's still could be worse, I went from 8am this morning till now and I have 34 percent left, only using the phone for some games and around 10 mins or so of phone calls and a few texts :)

In other words I'm pretty sure you can have the AOSP experience and get through the day :D

Looking foward to a public release of CM7 beta. Amazing work guys!
[Galaxy S I9000 Android Development] Boaty:
So what says your current build.prop?
[Galaxy S I9000 Android Development] cantIntoCode:
Still says Beta 3, isn't it just a text string that can be changed to whatever you want? I don't see why everyone is so pissed over this ...
[Galaxy S I9000 Android Development] dcarr622:
It's really a matter of knowing whether or not the update has been applied or not.

I went from stock>initial kernel> beta3>nightly from yesterday, and my About Phone still says Beta3, so i have no idea whether or not I'm actually running the new nightly.
[Galaxy S I9000 Android Development] codeworkx:
Then use this: http://www.codeworkx.de/download/cyanogenmod/CM6.2.0-GalaxyS-NIGHTLY.zip

With updated stings.
[Galaxy S I9000 Android Development] He4dShOt:
It's a new 6.2.0? If it's the same as before, it didn't work...
[Galaxy S I9000 Android Development] codeworkx:
someone has to find out why format_system and fsconvert are not started from updater-script.

can't test because my phone is on CM7.

please report back if someone found the problem.
[Galaxy S I9000 Android Development] the-rock_07:
I went from stock with jpm modem>initial kernel> beta3>nightly 17.12.10>nightly 5.01.11 , and my phone says 6.1.0-Beta4))But I do not see Nexus S codecs!
[Galaxy S I9000 Android Development] offenberg:
Can anyone tell me if I should update from 17.12 nightly to this. What are the differences? I use CM as my default. Thank you
[Galaxy S I9000 Android Development] philippsp:
Guys

Is this rom better and faster as a doc ROM?

Does this ROM support JPY Themes?
[Galaxy S I9000 Android Development] offenberg:
This is the Google exsperience on EPO.

Doc Rom is not faster.

-but remember it is a BETA. Lots of small bugs.
[Galaxy S I9000 Android Development] philippsp:
I want this ROM. Wich version should i take?
[Galaxy S I9000 Android Development] offenberg:
I dont know if you should use the one that these Guys are talking about. I am waiting for the same answer. But I am on nightly from 17.12.2010 and it is working just fine for me.
[Galaxy S I9000 Android Development] My20:
definitely install problem.

quickly but makes many lag

back ROM st

thanks for the work
[Galaxy S I9000 Android Development] philippsp:
Does the Themes work. ? (From JPY)
[Galaxy S I9000 Android Development] maverickzero:
Abslolutely not, JPY is samsung based ROM. CM6.1 is AOSP (meaning is not based on samsung ROM), which means that a theme from JPY wouldnt work at all on CM6.1

I wonder if somebody tried video playback and youtube HQ playback did someone with the newest update already try it?
[Galaxy S I9000 Android Development] offenberg:
Wich theme? Why would you want a SGS theme on cyanogenmod?
[Galaxy S I9000 Android Development] philippsp:
Would that be ok so:

I flash Doc JPM

Than i install the cm6.1 Beta 3

Finish

???

Bahh

what should i Take?

Beta 3 or A december build?
[Galaxy S I9000 Android Development] offenberg:
The nightly build is newer.

You need to visit www.cyanogenmod.com and the SGS forum for instructions
[Galaxy S I9000 Android Development] woeds:
as a workaround, could we just copy over the /system contents from the new nightly, and flash the new zimage?
[Galaxy S I9000 Android Development] Boaty:
Last nightly build gives still the same problem. Still the old system partition, no change in build.prob.

@Above:

I suppose that is not possible, due to permissions etc.
[Galaxy S I9000 Android Development] dcarr622:
So as far as anyone knows, it is not possible to flash latest nightly, or is there a way to do it successfully?
[Galaxy S I9000 Android Development] codeworkx:
Sure.

- Delete system from phone (rm -rf /system)

- mkdir system

- copy system from update with adb push (adb push system/ /system)

- set permissions on shell (https://github.com/codeworkx/update/blob/master/META-INF/com/google/android/updater-script#L126)

- tar the zImage and flash with odin

maybe following perms are enough:

chmod +x /system/bin/*

chmod +x /system/xbin/*

chmod 06755 /system/xbin/su

But it only works if you're already on cm.
[Galaxy S I9000 Android Development] dcarr622:
Thanks I'm trying these instructions...for some reason copying over ADB is impossibly slow, and seems to have frozen after less than 30mb. Could this be CM related? Usually I get fine speeds over ADB.

What changed between these recent nightlies and the mid-December ones that causes the update script not to work?
[Galaxy S I9000 Android Development] ashwinds:
Can anyone confirm if the kernel is updated? I am getting:

Linux localhost 2.6.32.9 #1 Fri Dec 17 06:57:34 PST 2010 armv7l GNU/Linux <--- which is the same as the previous nightly...
[Galaxy S I9000 Android Development] dcarr622:
If anyone has gotten this thing flashed let me know...I keep running into errors with /system not being mounted correctly, can't copy things on correctly, etc. I have an update script ready to set perms but I can't even get this dang stuff copied in the right place.

If anyone with more expertise could figure out why the provided nightly .zip is failing that would be wonderful too :)
[Galaxy S I9000 Android Development] dcarr622:
If you install using his instructions, make sure you flash kernel with odin otherwise it won't be changed from what you had before.

DId you get the /system flashed? I'm having issues...can you tell me exactly what you did? Also can you check build date in build.prop?

Thanks :)
[Galaxy S I9000 Android Development] ashwinds:
I use heimdall and it did get flashed - but its the same kernel. I didn't copy over /system.
[Galaxy S I9000 Android Development] dcarr622:
So you are not running newest nightly then? Or if so, how did you get it flashed??
[Galaxy S I9000 Android Development] ashwinds:
No - I am not - I am still on the Dec 17th nightly. And if the kernel is not updated, I dont really know if I should try to bump /system.

If you want to though - I think you can use the format /system inside cwm recovery - that does an rm rf. After that do the adb push and chmods (Make sure you have a nandroid backup - you may well have to advanced restore /system if necessary to get it booting again). Again I dont see the point if kernel is still the old Dec 17th zimage.
[Galaxy S I9000 Android Development] dcarr622:
True. Strange that the kernel hasn't change. Hoping for some clarification from codeworkx (and an updated functional zip at some point if he or somebody finds the problem).

Yeah I tried a bunch of things to get system on and it didn't work. My adb drivers are f*cked or something so speeds are very slow and I can't push on a new zip. I never make nanroid backups =P So time to flash some crap on with Odin and then decide what to do from there :)
[Galaxy S I9000 Android Development] codeworkx:
Kernel isn't updated because it's not necessary. It's the same as in prevoius nightly. But it's different to BETA3.

There are only changes at userspace (system).

Make sure you remove and push system at recovery. Otherwise it's like getting out of your shoes while walking.
[Galaxy S I9000 Android Development] ashwinds:
I did try from recovery - but these files wont go away - so cant delete /system:

rm -rf system
rm: can't remove 'system/nps_fail.jpg': Operation not permitted
rm: can't remove 'system/logo_s1ntt.jpg': Operation not permitted
rm: can't remove 'system/dummy.bin': Operation not permitted
rm: can't remove 'system/ani_upload_1_kernel_panic.jpg': Operation not permitted
rm: can't remove 'system/charging.jpg': Operation not permitted
rm: can't remove 'system/ani_upload_3_forced_upload.jpg': Operation not permitted
rm: can't remove 'system/ani_upload_4_power_reset.jpg': Operation not permitted
rm: can't remove 'system/ani_upload_5_user_fault.jpg': Operation not permitted
rm: can't remove 'system/logo.jpg': Operation not permitted
rm: can't remove 'system/ani_upload_2_cp_crash.jpg': Operation not permitted
rm: can't remove 'system/debug_level.inf': Operation not permitted
rm: can't remove 'system/movinand_checksum_pass': Operation not permitted
rm: can't remove 'system/nps_status': Operation not permitted
rm: can't remove 'system/movinand_checksum_done': Operation not permitted
rm: can't remove 'system/param.blk': Operation not permitted
rm: can't remove 'system/build.prop': Operation not permitted
rm: can't remove 'system': Device or resource busy

If i try to adb push ignoring that - i get:

adb push system/ /system
push: system/app/VpnServices.apk -> /system/app/VpnServices.apk
failed to copy 'system/app/VpnServices.apk' to '/system/app/VpnServices.apk': No such file or directory
[Galaxy S I9000 Android Development] lightning18:
You need to be in recovery to delete system.

I tried copying the system folder manually but its stuck at SGS i9000 boot screen.
[Galaxy S I9000 Android Development] ashwinds:
thats because /system is not fully copied because when you mkdir system, the directory structure is not there - adb push does not copy files if the sub directory is missing. I am trying to manually create these sub directories and will post here if it works (or doesnt)

Update: running into too many sub-folders. Will see if there are other approaches...
[Galaxy S I9000 Android Development] lightning18:
Maybe, you need to mount the system first /dev/block/stl9 as ext4.

What I did was to compress the system in a .tar.gz and extracted it into the /system after deleting all of its contents. Fix the permission and symlinks then rebooted but still no good.
[Galaxy S I9000 Android Development] ashwinds:
The issue was mac specific - For those on macs - it apparently has to be

adb push ./system /system

with ./ in front of the path to the system folder on your mac.

Update: copied successfully, set the permissions

chmod +x /system/bin/*

chmod +x /system/xbin/*

chmod 06755 /system/xbin/su

Also, used Fix permissions from inside recovery - but still stuck at the Galaxy S bootscreen.
[Galaxy S I9000 Android Development] lightning18:
Told you, :)

Please post adb logcat, might help other devs. My guess is that there is a problem with the latest sources.
[Galaxy S I9000 Android Development] ashwinds:
At first I saw this on logcat

fat.format was in xbin - so i copied it to bin and then I saw this on logcat
[Galaxy S I9000 Android Development] codeworkx:
Your problem is:

I/dalvikvm( 2504): Unable to dlopen(/system/lib/libandroid_servers.so): Cannot load library: link_image[2033]: failed to link libandroid_servers.so

This crashes the system.
[Galaxy S I9000 Android Development] woeds:
I know my own limits, and I'll probably wreck my phone trying this. I'll just wait a bit more ;) have you any idea yet on how to create a working update.zip for the latest nightly?
[Galaxy S I9000 Android Development] Whistler_QD:
Maybe you should make a tar file with /system directory, push it to phone through adb and then untar in the right location (after deleting previous files in /system). That should solve te sub directories issue while pushing the whole directory with adb.
[Galaxy S I9000 Android Development] codeworkx:
for me, adb creates whole folder structure.
[Galaxy S I9000 Android Development] ashwinds:
Tried to clear cache, dalvik - still same error repeats. Is there anything else I can try before going back to Dec 18th release?
[Galaxy S I9000 Android Development] ashwinds:
Pl ignore that - on mac i needed to add ./ and the structure was created.
[Galaxy S I9000 Android Development] codeworkx:
check if the file is there
[Galaxy S I9000 Android Development] ashwinds:
It is available:

ls -la /system/lib/libandroid_servers.so

-rwxrwxrwx 1 root root 18176 Jan 6 06:18 /system/lib/libandroid_servers.so
[Galaxy S I9000 Android Development] ashwinds:
Update: compared /system/lib with the folder in Dec 18th release and saw a bunch of lib files missing (170 files vs 158 thereabouts) - copied those files to yesterdays release and adb pushed lib folder againand got it to boot.

Everything seems ok so far... need to check more though.
[Galaxy S I9000 Android Development] woeds:
Great. Do you have the skills to fix the original update.zip?
[Galaxy S I9000 Android Development] ashwinds:
Nope .. this does not fix the update script. Its using adb to remove old system and push the new one after copying a files into /system/lib from the old release.
[Galaxy S I9000 Android Development] dcarr622:
A bit off topic:

Yesterday I was running the Beta3 from December 7th with JL2 Modem. I got absoultey insane GPS performanc e(1m-4m locks, near-perfect accuracy) and very fast WiFi tethering. Battery drain was fairly bad.

Today I am running the December 17th nightly with JL2 Modem. Both GPS and WiFi tethering are broken.

Anyone else have similar experiences? Can anyone running the latest nightly from yesterday confirm if GPS and WiFi tethering are working?
[Galaxy S I9000 Android Development] woeds:
Does hardware accelerated videoplayback work? how about taking pictures and video?
[Galaxy S I9000 Android Development] ashwinds:
Pictures - preview is BW but works fine (as it did in the prev nightly). Video doesnt. Sound recorder works fine now.
[Galaxy S I9000 Android Development] ashwinds:
I dont use either regularly so cant tell how it has changed - but wifi tethering does not seem to work for me (says "Error") but GPS seems to work fine.
[Galaxy S I9000 Android Development] dcarr622:
Very strange. This means that WiFi tethering has broken since Beta3.
[Galaxy S I9000 Android Development] Cygnust:
Hi,

how can we know if the latest nightly update worked ?

Seems like there's no difference ..

Thanks
[Galaxy S I9000 Android Development] dcarr622:
It doesn't work. Something about the update script doesn't work for some reason.

You can try to copy /system over via adb but it's a huge pain =P I gave up due to the errors I kept having.
[Galaxy S I9000 Android Development] riggnix:
so, did anyone manage to flash it yet?
[Galaxy S I9000 Android Development] dcarr622:
I think one guy did by copying system over via adb but I couldn't figure it out. I will probably try again once I'm through with my finals lol

For now I'm on Beta3. The December 17th nightly appears to be much worse than Beta3 from December 7th. WiFi tethering and GPS broke. Here's hoping that the January 5th one has both working.
[Galaxy S I9000 Android Development] cantIntoCode:
Hopefully a fixed release is not too far away :)
[Galaxy S I9000 Android Development] hardmusicfun:
And I hope this is true... Hey, DEVs, give it for people... pleeeeaaaase!!!
[Galaxy S I9000 Android Development] cantIntoCode:
Would you like to be responsible for breaking hundreds of peoples phones? Didn't think so, they want to make sure everything is solid before release.

Codeworkx said that there not releasing CM7 until RC status.

Patience is a virtue !
[Galaxy S I9000 Android Development] hardmusicfun:
O.k. I'll shut up :+(((
[Galaxy S I9000 Android Development] cantIntoCode:
I never meant to come across as rude, I just wanted to state that the devs don't want to be responsible for breaking everyone's phones...
[Galaxy S I9000 Android Development] hardmusicfun:
I'm just kidding... Sorry for non-understanding(and for my English)
[Galaxy S I9000 Android Development] dcarr622:
While codeworkx has made it clear that CM7 is still a ways away and won't be released utnil RC status, I think a lot of us would appreciate a fixed CM6x nightly :)

Unfortunately I don't have the expertise to fix the problem with the latest release and I know that codeworkx can't/won't fix it since he has CM7 on his phone :(
[Galaxy S I9000 Android Development] solidd_swa:
just flash beta3, then flash the nightly on top of it... boots :)
[Galaxy S I9000 Android Development] dcarr622:
Yes but it doesn't actually install anything.
[Galaxy S I9000 Android Development] philippsp:
Does the haptik feedback works now?
[Galaxy S I9000 Android Development] lion2009:
up......................
[Galaxy S I9000 Android Development] cantIntoCode:
dumdidum Kolja

I think the Kernel can now talk to the accelerometer. next: userspace driver #sgs

dumdidum Kolja

GPS: fixed, special thanks to Guipert for testing :-) #sgs

codeworkx Daniel Hillenbrand

mounting of both sdcards on #cm7 for #sgs fixed. good progress today

WOW, what a day so far. Keep up the amazing work guys! Keep up this pace and it won't be too long before it's in the hands of the public :)
[Galaxy S I9000 Android Development] philippsp:
Is the intern sd card working yet??
[Galaxy S I9000 Android Development] adzjwarner:
Read above. Seriously....... Some people! If you read this thread properly I (and anyone else dor that matter....)wouldnt have to trawl through pages and pages of the same questions from people who just cant be bothered!!!!!!

/Rant over

Keep up the good work devs, expect some pocket money when i get paid!
[Galaxy S I9000 Android Development] dcarr622:
Just to bump this thread...just wondering if there are any other folks out there who have the newest CM6.x nightly running, and if there's an easy way to get it working (possibly through the update script)?

If not I'll keep sticking with beta3 until CM7...just want to check thanks :)
[Galaxy S I9000 Android Development] ashwinds:
I cant help with fixing the update script but its not too difficult using adb. The failed boot reported by a few people is due to some missing lib file in the new release. Only additional step needed in codeworkx's instructions is copy missing files from beta3's (or the previous nightly) /system/lib/ into the new /system/lib and adb push them into the phone. Having tried it, I'd have to say I didn't notice too much difference in the daily use from the previous nightly.
[Galaxy S I9000 Android Development] dcarr622:
Thanks, I hadn't done that which might explain why I wasn't having much luck.

Can you tell me if GPS and WiFi Tether work in the newest nightly? They do work well in the beta3 from early December but appeared to break in the nightly from mid-December.

If they don't work, at least for me there isn't much point in trying to get the newer one as I rely on those features.
[Galaxy S I9000 Android Development] ashwinds:
I did post about that a few posts earlier - GPS does and Wifi Tether didnt. Atleast for me.
[Galaxy S I9000 Android Development] dcarr622:
My bad...I'm loosing my mind :cool:. I think I'll stick with beta3 for now. Thanks for the help :) Looking forward to CM7 as we are all :D
[Galaxy S I9000 Android Development] Kangal:
Man this is taking so long (no offence).

CM is the mother to most custom ROMs out there, and if we can get CM7/CM6.1 (hell even just CM6) then it would really steam things up.

I mean the BIT and TV-out enhancements will be quite delicious, as well as the prospect of getting our own MIUI ROM!

The ultimate gaming phone (at the moment) would be the Samsung EPIC 4G with MIUI ROM and a Gamepad (or a Gamegripper).

http://www.youtube.com/watch?v=2407W5bIae8&feature=related

http://www.youtube.com/watch?v=0VI0Wxg5EOU&feature=related

http://www.youtube.com/watch?v=w3Llz40hfpo#t=1m35s
[Galaxy S I9000 Android Development] Kops:
Hey guys the thread title is full of bugs.

What kind of bugs are there, is this not a very stable ROM?
[Galaxy S I9000 Android Development] cantIntoCode:
Patience is a virtue. The guys are working on this as much as they can to fix all the bugs and problems within Cyanogen on the Galaxy S. Give it a few weeks and I'm sure we'll all be able to give it a go.
[Galaxy S I9000 Android Development] chupchip:
As far as I know, closed source part (sgx540) thingy seems to be enough to piss thing off.
[Galaxy S I9000 Android Development] rockard_:
Ok, I'll add my experience. I'm a Captivate-user, so bear in mind some of this might be Captivate-specific.

I had a lot of problems copying over the system partition with adb push. It would hang on different files (for example fortran.nanorc) and never finish. Sometimes my partition would end up as a jfs partition, making the phone crash at boot. I ended up pushing the files in zipped format to /mnt/emmc, and then unpack them in adb shell with unzip-command. From shell, I could then copy all files, set the permissions according to codeworkx three lines above, and reboot.

Note that I started out from 6.1-BETA3 (http://www.codeworkx.de/download/cyanogenmod/CM6.1-GalaxyS-BETA3.zip) and didn't remove /system as codeworkx suggests. I merely overwrote affected files with stuff from the 6.2 zip file (http://www.codeworkx.de/download/cyanogenmod/CM6.2.0-GalaxyS-NIGHTLY.zip)
[Galaxy S I9000 Android Development] ashwinds:
The key point here is you overwrote/replaced files in existing system - that would have retained the old libs intact.
[Galaxy S I9000 Android Development] rockard_:
I disagree. Retaining old libs intact was the key point in your instructions. Thank you for them, they were much appreciated. In my post, though, the key points are:

1. Following the instructions previously given in this thread can leave you with a corrupt system partition and an unbootable phone

2. There is a way to avoid it.

For anyone interested, the steps to follow are:

Make sure your phone is running CyanogenMod 6.1 BETA3

Download CyanogenMod 6.2 NIGHTLY and unpack it to a temporary folder

Go to the unpacked folder, and locate the system folder

Make a zip-archive containing the system folder, for example system.zip

Go into recovery mode, mount the internal sdcard and connect your phone to the computer

Run the following commands:

adb shell

mkdir /mnt/emmc/temp

exit

adb push system.zip /mnt/emmc/temp

adb shell

cd /mnt/emmc/temp

unzip system.zip

cp -r system/* /system

chmod +x /system/bin/*

chmod +x /system/xbin/*

chmod 06755 /system/xbin/su

reboot

It might be a good idea to run a "fix permissions" from ROM Manager or ClockworkMod Recovery.
[Galaxy S I9000 Android Development] ademejia:
i get stuck on step 10 it says no such dir found
[Galaxy S I9000 Android Development] rockard_:
Did you do the mount part of step 5? You also need to run adb from the directory where your system.zip is located. Alternatively give the full path to it when you push it. For example, you have downloaded 6.2 NIGHTLY to D:\downloads\ and unpacked it to D:\downloads\6.2. In that folder you make a system.zip from the system folder. Then you go to command prompt and do like this (if adb is in your PATH variable):

d:
cd downloads\6.2
adb push system.zip /mnt/emmc/temp

Or, if adb is not in your PATH variable:

cd [PATH_TO_ADB]
adb push d:\downloads\6.2\system.zip /mnt/emmc/temp
[Galaxy S I9000 Android Development] yohann22:
..............
[Galaxy S I9000 Android Development] yohann22:
good method ! :D
[Galaxy S I9000 Android Development] gallaxya:
hello

has anyone managed to install a build from soruces CM7 version?if so ... what kernel did you use?

just asking ... i compiled a build, but i am a little nervous about installing it even if, as far i know bricking is close to impossible and the CM7 version is similar in functionality to the 6.2 one...so, daily usage is possible