yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] gertjan411:
if you dont want to help then say nothing at all
[Galaxy S I9000 Android Development] stratosk:
I was skeptical about the new partition layout. I tested and I'm convinced that this is a very good solution.

Pawitp is trying for free to keep alive an almost dead device.

If someone doesn't like the solution that pawitp implemented then he can think something different, get the code implement something new and release it for all of us.

Alternatively, he may flash stock android 2.3 or complain to Samsung about no implementation of ICS and JB to SGS.

Edit: a big THANK YOU to pawitp. Bravo!
[Galaxy S I9000 Android Development] upichie:
Seriously... it was talked about a page ago. And the one before that. And even the one before that. And again before that. And before that I think it was too. And even on the page before that it was. And before that one too.

Now stop reading this and search already.
[Galaxy S I9000 Android Development] Casper87:
Totally agree! One question , i have been asked few pages ago, but no one respons... this new partition layout , won't affect chip in time? i mean ... this won't create a fast wearing level?

Thanks... is just a question , not a remark...
[Galaxy S I9000 Android Development] Fr4:
Just a question.. battery life? Is the same than cm9? Better?

From Galaxy S - CyanogenMod 9
[Galaxy S I9000 Android Development] purpleraintoxicity:
are you familier with the term "Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime"

well, he just tought you how to fish :)
[Galaxy S I9000 Android Development] pmos69:
Then stop polluting the thread.

That is a FAQ. It makes no sense to repeat the same answers over and over. The info is already here.
[Galaxy S I9000 Android Development] andoceo:
Lost imei after flashing latest nightly .

Luckily, I don't know how come but I had backup for EFS in /backup/ folder, I've never did it. Anyway I replaced original EFS with the one from backup and voila, the phone is working
[Galaxy S I9000 Android Development] tonimanager:
death phone

unfortunately I had to uninstall this rom because one day in the morning when i tried to make a call the phone was dead. He did no wake, did not recharge and not entered into any maintenance mode.

I remove the battery and after a hour i finally manage to recover to stock rom.

Love this rom, but don't want to risk !

Just to share !
[Galaxy S I9000 Android Development] archzz:
I can say that the battery life is just AWESOME. For me it is a lot better than it was on CM9.
[Galaxy S I9000 Android Development] DeusEx80:
True, it is a very good solution for performance, but not for data space.

For me it is better, if DerTeufel1980 will succeed, this solution:

http://xdaforums.com/showpost.php?p=30446649&postcount=4317

If he succeed, he will resolve performance and data space problems.

Anyway, good work at all :)
[Galaxy S I9000 Android Development] elitevet:
A touching story. Thanks for sharing. Lurkmoar

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] Dopedangel:
Guy don't start a flame war because of my question :cool:

Anyway I installed the first nightly cm10 that was released by the build bot. Before that I was using CM9 with almost no lag now I am getting severe lag so much so that at times the phone is simply unusable. I am wondering why is that as most of you despite having some problems have working phones. I heard the first batches of Samsung phones had slower flash drive compared to the newer ones. I think my phone is from the first batch of phone as I bought the week it was announced in Singapore and it was released first.

By lag I mean the phone performs actions a few seconds after I touch it. But its not consistent usually happens when app is updating or installing. Or google currents is syncing generally when something is downloading to the device I guess/
[Galaxy S I9000 Android Development] jose.celestino:
This thread must be getting famous, judging by the number of posts starting with "don't start a flame war over my question" or "this is just a question, don't hurt me"

:)
[Galaxy S I9000 Android Development] plavez:
Please tell me why the memory is available for all programs 422 mb. And not as usual 1.67gb ?.
[Galaxy S I9000 Android Development] Abyv:
Really ? Please shut up !!!
[Galaxy S I9000 Android Development] Gvdn:
How on earth did u learn to write if u are unable to read?
[Galaxy S I9000 Android Development] BLADESMAN1889:
You are still getting lag now ? even with the new partition in place ? STRANGE !

I was getting this problem before pawitp made the recent changes - I would have to agree with your description - that the phone becomes almost UNUSABLE due to the lag/freeze/black screen of emptiness.

The browser [stock and Chrome] WAS unusable it just wouldn't open as above black screen/freeze. Apps would take 10 - 20 seconds to open !!

However, once I flashed the 2012-08-17 update EVERYTHING was fixed :D
[Galaxy S I9000 Android Development] pmos69:
Both moviNAND and oneNAND have the same issues with wear.

In the end, you'll be discussing 2 not very related things:

- you'll want most io activity on the fastest flash for performance reasons.

- you don't want to wear out your flash devices.

oneNAND is already using yaffs2, which should be better from a wear leveling perspective.

More than that, is a bit difficult.
[Galaxy S I9000 Android Development] Gvdn:
Start all over again. Factory reset and reflash.
[Galaxy S I9000 Android Development] suriya83:
I experience the same. To me it looks like it is related to particular apps, when i use them the phone slows down for 10-30 seconds and becomes unresponsive...

other moments it seem to run good. it happens when i start using google now or gmail i.e.
[Galaxy S I9000 Android Development] Casper87:
@pmos69 Thanks for answer :) feel good to know that.. :)
[Galaxy S I9000 Android Development] Kops:
Same thing here. I asked about this earlier, and was told to wipe/reflash. This does help, but it seems like after a couple days its right back to being slow and unresponsive...sticking with CM9 for now I think.
[Galaxy S I9000 Android Development] alcurtis93:
I think the swapping of /data and /system was a big mistake. I have 1.5gb of free /system space and no /data space left.

Bring on the flaming.
[Galaxy S I9000 Android Development] drakenabarion:
Who are you to decide whether jelly bean becomes usable or not on my phone? If you can think of a better idea that wont essentially exclude this phone from an official cyanogenmod source branch, I'd like to hear it!

Aka, Climb back under the bridge and wait for the billygoats.
[Galaxy S I9000 Android Development] MoneyFace =p:
Harness it. ;)
[Galaxy S I9000 Android Development] alb3rtt:
I'm on the latest nightly and all is great. Its smoother than ever but opening YouTube or play store, etc has like a 2 or 1 second delay. (Like a black screen for a second then the app opens). Also when I open nstools, under CPU governor is says unavailable. Could is be a bug due to jellybean or just a bug in the app itself. (I'm also on semaphore 2.0.6) I've done a clean install and my phone is an early model so that could be why i have the delay.
[Galaxy S I9000 Android Development] ballsofsteel:
Kill him with fire
[Galaxy S I9000 Android Development] k4z1k:
Will I lose any data by installing the latest nightly over alpha 20120817?
[Galaxy S I9000 Android Development] andoceo:
With Nightly 0820 it is possible to have IMEI deleted ( this is what happened to me ) ...
[Galaxy S I9000 Android Development] fatino:
Can someone explain to me why launchers are so weak on JB? They get killed all the time. Redraws after redraws. Nova Launcher, Go launcher. On ICS I could at least use supercharger which now on JB has some problems. Can it be fixed by CM developers?
[Galaxy S I9000 Android Development] r-l:
Updating from nightly 18 to 20 didn't work for me. First i got an error installing the nightly after that i got a bootloop. Finaly when it installed i got a lot of problems. Google account was ****ed up, laggy and when i opend Google play my phone got frozen.

After installing a clean install everything works fine (cleared everything in cwm and reinstalled gapps after flashing nightly)

for the moment i'm happy. no problems for the last 2 hours
[Galaxy S I9000 Android Development] alb3rtt:
Try holo hd launcher. Its running great for me.
[Galaxy S I9000 Android Development] jose.celestino:
Hardly. As pawitp said what's happening is the latest nightly includes new code that checks the validity of the IMEI.

So, if your phone has been working with a dummy IMEI because you lost it somewhere in the past, now, from 0820, it will start complaining.
[Galaxy S I9000 Android Development] flatron2:
Same happened to me. I've installed from JVU and after first try a recovery loop happened (no, no external sdcard or sim card inside :P ).

I released the battery and started in recovery again. Three wipes and a nigthly zip later everything worked fine but after reboot it warned me about invalid imei.

What I've done is open 'Terminal Emulator' and:

- su

- cp /mnt/sdcard/backup/efs/nv_data.bin /efs

- cp /mnt/sdcard/backup/efs/nv_data.bin.md5 /efs

- chown radio:radio /efs/nv_data.*

- chmod 600 /efs/nv_data.*

Reboot after that and happy end! :D
[Galaxy S I9000 Android Development] fatino:
It doesnt have folders in app drawer. Go Launcher and Nova have. Go launcher is better than Nova because it has keep launcher in memory but still it gets killed. Not as usual as Nova but still. I wonder why CM developers dont want to fix it.
[Galaxy S I9000 Android Development] wfm_de:
Started with nightly 0820 coming from CM9, navigon select crashes short after start with java-parcel-exception. No problem with CM9.

Same problem with app Wetter.info... requested network provider missing...

All other apps on my phone OK.

Has any one a solution ?

EDIT: Problems are solved. Sorry, I used the gapps of CM9. With the CM10-gapps all is ok.

GT9000 mit JB CM10
[Galaxy S I9000 Android Development] omnicronx:
"CM10 just died for i9000. Our maintainer decided to swap the system partition (512mb) with the data partition (2048mb). So now we have over 1500mb free system & precious little data space. Thank you gerrit for accepting this senseless commit...﻿"

So check it out yourself, revert the changes and stop complaining.. (and if you don't know how to revert the changes and build it yourself, who are you exactly to say what is or is not a senseless commit?)

I'm sure pawtip had an idea of what he was doing, and is trying to find a solution.. but fact is our devices do not have enough space for JB, which is going to require some clever thinking to get around it.. So either build it yourself or sit back and let the experts sort it out..
[Galaxy S I9000 Android Development] purpleraintoxicity:
Man...

Be patient...

Its still nightly on the very beggining....

launcher redraws is the least important problem now
[Galaxy S I9000 Android Development] philidor:
Swap partition data/system if you search you will find more information
[Galaxy S I9000 Android Development] kingoftf:
Build 20 works very fine for me, no probs with EFS or any other things, in my opinion it is far better than the Build 18 which at least on my SGS was very laggy. Now everything like "butter"

And very important for my, no message "No space left" so far which I had with Helly Bean and the last two b9 ROMs from Elite.

Same amount of apps and no probs with CM10
[Galaxy S I9000 Android Development] SnoopyDog:
Hm, i just see a second 0820 nightly right now. I had some installation issues from 0818 to 0820 (error message during install and then boot loop) but i managed to resolve. The "first" 0820 is running fine now. All the delays that i had from time to time with the alpha builds are gone now.
[Galaxy S I9000 Android Development] Kshitiz_Indian:
@pawitp

The newest nightly is working great; the lags from the earlier builds are now gone mostly.

However, now opening system apps sometimes causes a 1-2 second 'microfreeze'. I looked around and saw stratosk was mounting /system with data=writeback in Semaphore. I mounted /system with data=writeback myself and those microfreezes were gone- the phone is now faster than ICS.

Could it be implemented in the mainline? Since there is not much sensitive data written to system (is there any at all? :S) it should be relatively safe right?
[Galaxy S I9000 Android Development] jacobuscuracao:
I have 1 Gb of free system and 276 of free /data. For me - with the number of apps I have - that is more than enough.

I understand if you install lots of apps and/or big apps like chrome, space could run out - but a lot of them you can move to sd-card.

So what's the problem? this is the best our phone can do with Jellybean. And I'm happy with that. Otherwise I can go back to CM7, CM9, a rigged copy of CM9 or CM10 or find the money to buy a new SGS III.

I'm very happy with what Pawit has done.
[Galaxy S I9000 Android Development] dongfangri:
Could you tell me how to mount /system with date=writeback? Thanks.
[Galaxy S I9000 Android Development] SnoopyDog:
I've forgot to mention: i also use the Semaphore kernel. It seems, as if this mount option is important for performance :)
[Galaxy S I9000 Android Development] 54P3:
Just installed on friends phone and doesn't seem to recognize sim-card. Anyone knows how to fix this?
[Galaxy S I9000 Android Development] upichie:
Why are there 2 different 08/20 builds? They both have a different md5, so they must be different. Which one has everyone downloaded?
[Galaxy S I9000 Android Development] androkurd:
I've just installed cm-10-20120820-NIGHTLY-galaxysmtd.zip from JW4 and after boot I have received an error message which told me that my imei has changed. This is the first time such thing happened to me. I've heard that I can fix that by installing a stock gingerbread firmware. Anyway, is this a rare event or is this an issue with the nightly? shall I try to install it again or wait for a new nightly ? Thanks!
[Galaxy S I9000 Android Development] mnazim:
There is now code that detects if your IMEI has changed in the CM ROMs. Confirm you have the right IMEI. or Restore your original.
[Galaxy S I9000 Android Development] androkurd:
I've checked my IMEI and I can confirm that it has changed. I'm trying to install it again now if it still doesn't work I will install stock firmware.
[Galaxy S I9000 Android Development] Boosik:
I've got strange battery drain by Google Services. On battery 16hours, Google Services 30% battery drain, Google Services - keep awake 4 hours =O. Whats wrong?
[Galaxy S I9000 Android Development] Kshitiz_Indian:
I could but there's no point. It only stays until a reboot. Plus I am not sure about its safety hence asked pawitp. If you must try, try Semaphore but then post in that thread only!
[Galaxy S I9000 Android Development] rest0ck:
Can someone please link me the change log I am able to understand? :p

Oh and which kernel are working with cm19 nightly ? Only semaphore yet?

rest0ck

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] pawitp:
It shouldn't have any effect on performance at all as nothing is being written there except on boot and on apk installation.
[Galaxy S I9000 Android Development] Michel38280:
Are you sure that's not an IMEI issue? Check the IMEI in Settings > Phone > ...
[Galaxy S I9000 Android Development] Boosik:
I've got Warning that my IMEI has changed, but all is working. I can make calls, sms/mms, 3G and even emergency calls.

Could it cause any other problems?
[Galaxy S I9000 Android Development] slaj76:
Check your imei it could be fail.
[Galaxy S I9000 Android Development] kraven001:
Ideally you should use the EFS backup and restore IMEI. You shouldn't "go around" with a fake IMEI.
[Galaxy S I9000 Android Development] Kshitiz_Indian:
Ah okay. Cheers for the reply.

Could it be slower NAND reads then? Are speeds on USB Mass storage and internal write/read speeds (on the same NAND of course) somehow linked? Because all through CM9 I used to get UMS write speeds of around 2MB/s as if it were capped, and read around 3-4MB. Using Devil/Semphore solved it. The behavior is mostly gone in JB since recent builds but I can't help but notice that speeds on the stock kernel are still a bit slower than Devil/Semaphore (could be placebo). Any insight on this situation one could be aware of?

Ignore if it didn't make sense, sorry.
[Galaxy S I9000 Android Development] pawitp:
Only the kernel maintainers would know. If they have a good, proven fix, they should be submitting it back to CM though. I've merged a patch DerTeufel1980 pointed out to me which would have increased on the USB Mass storage speed on Windows a while ago (which is probably the fix you're seeing), but it has no effect on on-device write speed.
[Galaxy S I9000 Android Development] flatron2:
I've set 600 radio:radio because the original files, the ones which failed, where 600 radio:radio files (not because I knew what I was doing :D ). After overwriting that files it started to work, but to try to keep the directory as it was before I had the error (because I don't know if the system needs the rest of the files) I've restored the entire directory. Problem now is that all the files and directories have no permissions and are root owned.

Could anyone please tell me which permission should I set and which owner for the files inside /efs directory? Is 600 radio:radio good enough or should I set it to 666 root:root as I've seen on a friend's SGS (with CM9)?

If someone could post an 'ls -la' of that directory it would be great. Thank you in advance!
[Galaxy S I9000 Android Development] Kshitiz_Indian:
Yeah that would probably be the thing then. If I was more proficient with kernel coding I would look around and find something, but alas. Someday perhaps!

Got it, Thanks! :)
[Galaxy S I9000 Android Development] DROCSID:
I always chown 1001:1001
[Galaxy S I9000 Android Development] guijarrelson:
@ pawitp

Thanks for your work, it's awesome as always.

No problem updating from CM9 to CM10 in the latest nightly. IMEI and /efs folder are ok.

I have a suggest. Could you reduce /system size to increase /data? I think it could be unuseful a lot of free space in /system (some free is great, to sustitute the updated apks from original ones).

Thanks!
[Galaxy S I9000 Android Development] flatron2:
And what about permissions? 600? 666? Thanx again :)
[Galaxy S I9000 Android Development] matesc:
that is not possible, because the current /data partition is on a chip, that only has limited space. Search pawitp's posts, he has already explained it! :D
[Galaxy S I9000 Android Development] guijarrelson:
Oh, I din't see that post... In that case, it could be some problematic in my case with all the apps that I have installed :(

But the ROM works like a harm!
[Galaxy S I9000 Android Development] White girl:
I have IMEI problem, I don't have backup folder in /mnt/sdcard. What should I do?
[Galaxy S I9000 Android Development] matesc:
Search the thread! You can move ~60% of all apps to sdcard.
[Galaxy S I9000 Android Development] elcaro:
I follow what RATBORG suggested couple of days back, which has a chown 1001:1001 and no chmod. That has worked flawlessly twice for me.

Here's my ls -la :
[Galaxy S I9000 Android Development] Sw2rT1:
Hello!

help me in my problem. I can not install the CM10 on a clean system after installing the stock firmware.

The problem: after installing CM10 and click on reboot system now, the system will not boot. system will go into recovery. Wipe and install the system again does not help me.

problem is solved as follows:

1) installing the stock firmware (JW1)

2) installing a custom kernel (speedmod)

3) full wipe

4) installing CM9 stable release

5) boot into CM9, then boot into recovery, full-wipe and install CM10

6) reboot system now

7) system again comes into recovery. I do a full-wipe and install CM10 again.
[Galaxy S I9000 Android Development] Tzarski:
Hi everybody. I was upgrading from CM10 18.08.2012 to CM10 20.08.2012 the second one. Now after i restart my phone it says: "WARNING! A problem was detected with your device. Your device IMEI number is invalid. An Invalid IMEI number could cause network issues including the inability to call emergency numbers" For some reason i do not have any problem with the network coverage and I'm able to send and receive calls and SMS. When I dial *#06# the IMEI number is the following one: 004999010640000, and it is nothing close to the IMEI number printed on the sticker behind the battery. Please advice what should i do since there is no backup of the EFS folder on my SD Card.

Any help or information will be highly appreciated.

Thank you in advance for your time.
[Galaxy S I9000 Android Development] yaatzek:
In fact you are wasting our time. Read the thread!
[Galaxy S I9000 Android Development] AndyP85:
What is the difference between CM10 18/08/2012 and CM10 20/08/2012? :confused:
[Galaxy S I9000 Android Development] White girl:
I have the exact problem, and the IMEI number displayed after dialing *#06# is the same as yours, and I do not have backup folder in /mnt/sdcard/ Is there any solution?
[Galaxy S I9000 Android Development] elcaro:
The last 4-5 pages have the solution for this.
[Galaxy S I9000 Android Development] guijarrelson:
I submitted an issue in the official site : https://code.google.com/p/sgscm10/issues/detail?id=134

All was going well, but when the battery is nearly at 15 %, the advertisement makes unstable the system and don't respond.
[Galaxy S I9000 Android Development] elcaro:
Flash stock Samsung GB ROM and you will get back your EFS folder. Take a backup of that and flash CM10. In case you still lose your EFS, you can restore it from the backup.

---------- Post added at 11:27 PM ---------- Previous post was at 11:25 PM ----------

2 days worth of changes..http://cm10nightlies.nechko.com/index.php?device=galaxysmtd&translations=
[Galaxy S I9000 Android Development] phees:
Your procedure only accidentally results in kind of the right way to flash this ROM. Compare yours with the correct procedure as given by pawitp in the FIRST post of this thread and you should be able to spot the difference. (I added that below, to make it even easier.)

Pawitp's original procedures:

Installation

- First time flashing CM10 to your Galaxy S (or coming from another ROM)?

Root your device and install ClockworkMod Recovery.

Reboot into Recovery using 3-button-combo

Do a Nandroid backup!

WIPE (wipe data/factory reset + wipe cache partition)

Install the ROM from internal sdcard using ClockworkMod Recovery

Optionally install the Google Addon

- Upgrading from CM7/CM9?

Do a Nandroid Backup!

WIPE (wipe data/factory reset + wipe cache partition)

Install the ROM from internal sdcard using ClockworkMod Recovery

Optionally install the Google Addon

- Upgrading from another CM10 Build?

Do a Nandroid Backup! WARNING: Upgrading from version before 20120817 will wipe your phone

Install the ROM from internal sdcard using ClockworkMod Recovery

Optionally install the Google Addon
[Galaxy S I9000 Android Development] SGSdabbler:
cm10 running smoothly. Only problem experienced was Beautiful widgets finding my location. What fixed that was checking all the options under 'location services' under settings.
[Galaxy S I9000 Android Development] Tzarski:
Hi I found an old backup of the EFS folder on my computer and i fixed my problem following this nine steps here: http://xdaforums.com/showthread.php?t=1264021
[Galaxy S I9000 Android Development] mobydeek:
So theres a whole bunch of people with EFS/IMEI problems...

But, Why exactly, does this happen?!

Is it a user flashing problem? Or an issue to do with the way ClockworkMod flashes CM? Has anyone read a post/article on this before?

You would have thought that with the geniuses working on CyanogenMod, that it would never happen, no? (No hate)

*** EDIT ***

Im not asking why the warning shows up. Im asking why the IMEI gets wiped? corrupted? at all in the first place.

But thanks anyway mikandlotta.

Only "explanation" I found so far

http://www.jayceooi.com/tag/efs/