yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Vadrieldur:
Is this rom worth flashing instead of using CM9 Stable?
[Galaxy S I9000 Android Development] nitramcek:
Tnx, have modem now.

I wanna know how to flash Odin firmware with Heimdale. Cos if I understand correctly Heimdale uses different kind of files to flash. So I cant help my selfe with Odin GB firmware i have.

Updated now to latest Nightly, and everything works again. Really strange, but connection come back by it selfe after some hours.

Had wife's phone beside and it worked fine, so couldn't be providers foult.

Well...just lost connection again!

I'm lost too now!

Rebooted again, and connection is back again. Never seen something like that.
[Galaxy S I9000 Android Development] pmos69:
Then I'll be more specific:

- The notion that installing any of the cm10 builds up to today will put your device into an unrecoverable bootloop is a myth. (Perhaps if you drop it while flashing or had a previous bad cwm installed).

- It's true that the 1st flashing of a cm10 build that changes your current partitioning puts/can put the phone into a recoverable bootloop.
[Galaxy S I9000 Android Development] DROCSID:
Hahaha, thats funny. Hook me up on DM, I've got someone @Samsung NL that can you with this issue when you seriously lost it.
[Galaxy S I9000 Android Development] Michel38280:
I have a tutorial ... in French: http://galaxys-team.fr/viewtopic.php?f=6&t=20933&hilit=heimdall ... hope it can help :angel:
[Galaxy S I9000 Android Development] caspeer_costel:
I do consider it worth. It's faster, smoother and just more fun to use. It's still a work in progress but hey it's better :D
[Galaxy S I9000 Android Development] saszseb:
- Odin: you can use it only using Windows.

- Heimdall for Windows, Linux, Mac.

Using Heimdall you need the same files (phone, pda, modem). These 3 files must be unzipped and you'll get the necessary files: dbdata.rfs, factory.rfs, sbl.bin, boot.bin, etc.
[Galaxy S I9000 Android Development] nitramcek:
:o No parla French.

Tutorial is really BIG. Could you tell me in some easy, fast and simple steps to make it work.

I tried to extract .tar from zip firmware and load it into Heimdale, but get "firmware.xml is missing from the package." at the end.

So that's probably not the wright way to do it :)
[Galaxy S I9000 Android Development] saszseb:
Grab "Perka's File Stash" from Play Store! You'll find lots of "ICS modems" in it.
[Galaxy S I9000 Android Development] Gvdn:
Been ages that i bought that but its been ages that it stopped working for me always get and error.
[Galaxy S I9000 Android Development] .:Crack:.:
Hey guys,

did anybody now find out why any browser gets extremely slow after some time(~2 days after flashing with wipe)?

In the beginning page loading was unbelievably fast, but now it takes ~20s to load a page (vs ~2s).

Using Dolphin with heapsize-bla 128mb,64mb,5mb.
[Galaxy S I9000 Android Development] yahyoh:
may i ask how much free ram u have ?
[Galaxy S I9000 Android Development] aambro:
Internet disconnecting while wifi connected

I have this problem since ICS. After the screen turns off, sometimes after a minute, sometimes more, i don't have access to internet anymore. Wi-fi connection is OK, IP is OK, i can browse LAN shared folders.

Here are some lines from logcat that i think are relevant to the problem:

More info on my original post: http://xdaforums.com/showthread.php?t=1846850

PS: I have finally managed to get 10 posts so i can get to smart guys. yay. :)
[Galaxy S I9000 Android Development] kaza:
Hi guys, I did a big mistake, I erased everything inside efs folder and unfortunatly I did the same with my backup folder :crying:, stock roms are not going back to my imei, still with the generic one, the only way to get my imei its with box right?
[Galaxy S I9000 Android Development] purgalm:
And if it does go into boot loop what shall I do? I can't boot into recovery now (but download mode works fine). My guess is that I need to download some odin flashable JB (or GB?), root (or flash already rooted firmware) and then flash CM10 again.

Will Darky 11.0 (JB) be ok?
[Galaxy S I9000 Android Development] Michel38280:
The new nightly is out :good:
[Galaxy S I9000 Android Development] albertobom:
It's the CM9 nightly
[Galaxy S I9000 Android Development] saszseb:
I've just now tried it out. It worked fine here.
[Galaxy S I9000 Android Development] Michel38280:
... oups, sorry :laugh:
[Galaxy S I9000 Android Development] .:Crack:.:
183MB Free
[Galaxy S I9000 Android Development] Sharken:
I always experience that the phone gets slower and slower with time. A reboot always returns the phone to its previous speed.

One way of telling is to enable the CPU-usage overlay from the developer settings.

When the sluggishness occur its always related to spending a lot of time with memory-related calls (Red bar).

Before the new layout in CM10, it was mostly I/O that was the bottleneck (Blue bar).

So something is making the phone slower over time, but what it is is anyones guess. By the way, If you run 'free' from the terminal its true you will see how much memory is available, but since Linux uses remaining free memory for cache that is not a great indicator.

One thing you could try is to make a note of the output from cat /proc/meminfo after a reboot, and again when the phone becomes slow.
[Galaxy S I9000 Android Development] elitevet:
Next nightly includes:

Lack of UPDATE_PACKAGE being set when updater.sh is run from stock
was causing a loss of IMEI when installing.

Thanks to [B]festis74[/B] from XDA for sending me a debug analysis of the
IMEI not being restored.

Change-Id: Ic00a95025f1069692878bbf4da1a0e3bbb538e58

Now, everybody, go buy the man a beer...
[Galaxy S I9000 Android Development] bhu1:
200+ after fresh reboot.
[Galaxy S I9000 Android Development] saszseb:
That's right. I've also experienced it sometimes. The last step before flashing a GB ROM is to flash CM7 initial kernel to get recovery back.
[Galaxy S I9000 Android Development] Sharken:
cat /proc/meminfo

This is a dump of /proc/meminfo right after boot, might help in locating what can cause sluggishness over time
[Galaxy S I9000 Android Development] yahyoh:
so its not ram problem :rolleyes:

may i ask how much uptime ??
[Galaxy S I9000 Android Development] pmos69:
If you go into a boot loop you use the recovery 3 button combo (vol-UP + home + power). Release the buttons as soon as the boot logo appears. Timing is critical.
[Galaxy S I9000 Android Development] yahyoh:
cool i have about 190 after fresh reboot if i delete whatsapp i will have about 200 i think its always run in ram with 2 service :mad: and there no way to stop it from being always in ram ( crap app ) chat on way better but most of people still using whatsapp :silly:
[Galaxy S I9000 Android Development] purgalm:
@up

Hmmm... I thought I tried it... it looked as the installation of CM10 broke CWM... Will try it again with the proper timing :) Fortunately, I've got a nandroid backup :)
[Galaxy S I9000 Android Development] .:Crack:.:
3.5h since last reboot
[Galaxy S I9000 Android Development] purgalm:
All right... I get through that boot loop, but I'm stuck now with restoring my nandroid backup... CWM resotres boot, but can't do the same with /system and /data. I get the following:

and

I don't wanna loose my data :(
[Galaxy S I9000 Android Development] yahyoh:
anyone noticed on the first start the cam its lags a lot for like 10 -15 sec then it will work normally

---------- Post added at 09:54 PM ---------- Previous post was at 09:51 PM ----------

on what cwm build u did the nandroid ??
[Galaxy S I9000 Android Development] purgalm:
@up

I don't know. It was CWM that I flashed together with CM10 dated at July 29th 2012 (or some day around).
[Galaxy S I9000 Android Development] yahyoh:
i think it was 6.0.1 or somthing like that , nandroid should work

but maybe due the new change on cm it will not work , so reflash the same build that u did the nandroid on it then after installing it do reboot recovery then try to restore the nandroid :fingers-crossed:
[Galaxy S I9000 Android Development] mikandlotta:
Wrong

Flashing the stock Samsung ROM, eg. JVU, will rewrite the folders. You are kind of starting from scratch and the hardware info is read in again.

I have read of some who say it did not work. I had one stubborn i9000 that bootlooped once on ICS and I needed to go back to original Froyo then slowly flash newer versions before getting back to CM9.

So, have a crack at a Gingerbread ROM - try the one that is closest to your original region from purchase, check the IMEI and back up the EFS folder before advancing to CM10 again. Many steps, lots of coffee and a few double boots....
[Galaxy S I9000 Android Development] turquoise.ht:
wow

this rom rocks with semaphore 2.0.6s and adw launcher ex
[Galaxy S I9000 Android Development] purgalm:
Great :D I see that the latest flash corrupted my IMEI as well :D I do have backup of efs directory though. Will restoring nandroid backup repair IMEI as well?

Where can I get a download link for nightly of CM10 from 29.07.12?
[Galaxy S I9000 Android Development] slaj76:
Page 380.
[Galaxy S I9000 Android Development] Michel38280:
Either wait for the next nightly, IMEI issue will be solved.
[Galaxy S I9000 Android Development] kasper_h:
I don't think IMEI will be solved in next nightly, only new problems will be prevented...
[Galaxy S I9000 Android Development] purgalm:
Simply copying files to /efs directory on the phone solved the problem. Still waiting a couple of minutes for previus CM20 nightly to download and will see if the nandroid restore will work :)
[Galaxy S I9000 Android Development] Michel38280:
You're right !
[Galaxy S I9000 Android Development] sniperviperman:
imei problem resolve would be great. I've even went into hex editing the nv_data.bin file. it was showing not activated and not the product code. but even adding product code and the i-9000 still gives me 0499 imei.
[Galaxy S I9000 Android Development] monjovega:
Just found out when I access video on camera I get an error: "Unfortunately, Gallery has stopped". Any work around for this?
[Galaxy S I9000 Android Development] TaC:
Just press wait and... Wait.
[Galaxy S I9000 Android Development] monjovega:
No luck!
[Galaxy S I9000 Android Development] purgalm:
CWM was updated somewhere between 29.07.12 and 25.08.12 from 6.0.1.0 to 6.0.1.2.

Does it mean that I need to get a fresh install wile upgrading from my current CM10 version?
[Galaxy S I9000 Android Development] .:Crack:.:
works fine after factory reset...
[Galaxy S I9000 Android Development] yahyoh:
u need to full wipe if u want to flash any build after 17/8 :silly:

so backup ur apps and data is best solution :fingers-crossed:

try go backup
[Galaxy S I9000 Android Development] Bejda:
Really it is not that simple,only thing sure on this matter is that some users never ever experienced this while it was(still is?) frequent for some.

Knowing that and presuming you're in the first category i can admit it sound really too fishy in your opinion and you're sure there's a rational reason or fact from user side for this to happen but this is old debate and if indeed there is a logical process behind it still has to be defined..

Stratosk even opened a thread to investigate on this, he wouldn't have lost time with peoples just messing their installation or confusing with the well known "fast [can't mount] loop to recovery" we have when changing partitioning way using cwm.

Hope i understood well your point,maybe it's just me not understanding the "myths" terms used and hope you'll understand what i meant too,the thread is there:

http://xdaforums.com/showthread.php?t=1627689

Not of a great activity these days but not sure why, my opinion leads to new initramfs introduced by Stratosk and Mialwe on their kernel that greatly reduced the risk to encounter such issue, maybe peoples got tired of searching "reasons why" or the phenomena is less frequent since JB (by the way i was feeling safer since JB on this side but it happened again recently).
[Galaxy S I9000 Android Development] monjovega:
Video on camera still not working.
[Galaxy S I9000 Android Development] sh4z:
@bedja semaphores boot loop issue is not relevant here. That's related to flashing a custom kernel. What pmos69 described was related to the partition changes that occur after flashing CM10... What the other thread describes is a generic ICS issue where recovery is lost .. CM10 is JB based firstly and recovery is not lost during installation from my experience...
[Galaxy S I9000 Android Development] _Morfic_:
Looks like your prayers will be answered with the new nighlty new boot animation

Cheers
[Galaxy S I9000 Android Development] Zatta:
Those unrecoverable bootloops exist(ed) not only while flashing custom kernels, also when flashing a normal cm ROM. Classifying that as a myth is not right, it happened, it happens and it will happen. Some suffer it, some don't.

Where are you, Jacobus?

Taptalked u see
[Galaxy S I9000 Android Development] Bejda:
There is no specific "semaphore boot loop issue",it's kinda off-topic ok but peoples were talking about this on this here rom the stockiest way it can be flashed or used (that goes for any rom) or at least from a general point of view.

I just had to precise they're not dreaming, it doesn't necessarily comes from an user mistake and not only a matter of timing to gain back recovery access.
[Galaxy S I9000 Android Development] jbuk__:
I've been using ZSJPE and haven't had any problems with data, in fact it was working fine during the setup wizard.

Incidentally, the setup wizard is impossible to complete if you have 2-step verification enabled, as I needed to receive an SMS verification code, but all notifications (and calls) are suppressed during the setup wizard. This meant I had to exit it by using the hidden method of tapping the 4 corners of the screen in sequence, and then go to Settings > Accounts to set up my Google account manually.
[Galaxy S I9000 Android Development] firro85:
just installed

Hi!

Just installed the new rom, and man i got supriesed when CM9 logo still booted up my phone, thought a was realy ****ed there for a while.

one thing i notice is that its a little harder to get in to recovery, or is it just me?
[Galaxy S I9000 Android Development] dr_iggy:
Try waiting for a few seconds after logo appears, and then release three buttons combo.
[Galaxy S I9000 Android Development] jbuk__:
I have no problems with my usual method of releasing the three buttons as soon as the samsung (GALAXY S GT-I9000) splash appears.
[Galaxy S I9000 Android Development] maverick340:
Is it just me or does anyone else feel like this is a lot slower (laggy and sluggish) compared to v2 released by mkalter?

more specifically, it takes about 3-4 seconds to bring up Talk when I click on a new IM notification. It takes about 2 seconds for the screen to come on after i press the home/power button.
[Galaxy S I9000 Android Development] edgardurao:
Cant create apns. If i save none appear. Anyone?
[Galaxy S I9000 Android Development] e195aea:
Put the mobile in Flight Mode and then desactive. Do it every time you reboot the mobile.

http://code.google.com/p/sgscm10/issues/detail?id=2
[Galaxy S I9000 Android Development] drjonze:
I can't speak to v2 as I've never tried it but I do find some lag with this ROM. Still, for an alpha release, its a lot more stable than I would have thought. Give it time, pawitp will work his usual magic.
[Galaxy S I9000 Android Development] dr_iggy:
...or try flashing other modem for a permanent solution.
[Galaxy S I9000 Android Development] hazwheel:
Dammit! The wife won't let me have her phone to try this out on :eek:
[Galaxy S I9000 Android Development] dr_iggy:
Try other launcher, not the stock one, might help.
[Galaxy S I9000 Android Development] maverick340:
Certainly, i dont meant to nitpick. Pawitp has done amazing and kudos to all the devs working on this. Its fantastic, can not be thanked enough. Was just giving a user feedback :)
[Galaxy S I9000 Android Development] dr_iggy:
Tell her it will be more fancy. ;)
[Galaxy S I9000 Android Development] hazwheel:
I have I have, but she's not buying it "a phones a phone blah blah blah" , you know the sory :(
[Galaxy S I9000 Android Development] Magnumutz:
You poor bastard, my GF would've asked me to do it, if she had an SGS :D

I mean, after showing her the difference between a stock ROM and a custom ROM, she started liking all this.
[Galaxy S I9000 Android Development] hazwheel:
I will wear her down eventually, make her think it's her idea ;)
[Galaxy S I9000 Android Development] Cerbero805:
No, a Nokia 3310 is a phone, this is a all purpose device, wich, amongst other things (lots of things), can make calls.

One does not simply spends hundreds of euros only to make phonecalls.
[Galaxy S I9000 Android Development] hazwheel:
You know what, If her old nokia 3310 would accept her 3g sim, she'd be using it instead of the SGS1 that I so kindly gave her after confiscating her SGS2 :p
[Galaxy S I9000 Android Development] Trainer_H:
does the new rom use /datadata?
[Galaxy S I9000 Android Development] yahyoh:
nope :)
[Galaxy S I9000 Android Development] SnoopyDog:
The latest nightly 0826 is cm9 (?)
[Galaxy S I9000 Android Development] alcurtis93:
There are still cm9 nightlies
[Galaxy S I9000 Android Development] pmos69:
I was simply saying the main issue is the added difficulty in entering recovery after entering the bootloop.

The timing is not that easy to get right even when you know what the issue is, and usually takes some trying even if you know how to do it.

There are a lot of reports of users saying they had to remove the battery, etc to get into recovery. All that proves is cwm is operational.

In fact, it's hard to picture a scenario were cwm is rendered unoperational from the cm10 setup process.

(Can't comment on setups of other roms because of my limited knowledge about them)
[Galaxy S I9000 Android Development] edgardurao:
Lol. Run from that... checked updates with cwm and give ok to that. Lost everything and had to reinstall cm10 again.

Next time will pay more attention for shure.
[Galaxy S I9000 Android Development] pmos69:
Ouch
[Galaxy S I9000 Android Development] jacobuscuracao:
it's been a long time since I had a bootloop.

However, nowadays we have fairly simple solutions for it - flash Semaphore via odin.

I know that the Roms are better now (because of CM-development) and CWM is also improved.

Consequently, I don't think we should look at it the same way that we did before - the environment is different now.

but a developer can probably explain to us why the SGS has some features (or lack of features) that still make it possible.
[Galaxy S I9000 Android Development] RowanDDR:
Whoops. I've accidenty installed cm9 nightly over the top of cm10! Now I have a bootloop! Download mode and recovery mode still works. What can I do to get back to cm10 most easily? Thanks in advance.
[Galaxy S I9000 Android Development] Bejda:
Keep trying recovery first.

If no success try a .tar version of semaphore (maybe the ICS one) as PDA via Odin auto-reboot unticked and if recovery is back reflash your cm10.
[Galaxy S I9000 Android Development] RowanDDR:
Thanks. After a few reflashes of cm10 in recovery I'm back to normal.
[Galaxy S I9000 Android Development] Bejda:
If it's only loops with fast passage in recovery saying "can't mount..." it's only due to partition change between in this here case cm9 and cm10 and then is normal.

The thing is to get back to recovery to flash rom again.
[Galaxy S I9000 Android Development] TaC:
Working perfect for me in A-25th nightly with semaphore kernel.
[Galaxy S I9000 Android Development] monjovega:
Getting message: "Unfortunately, Gallery has stopped".

---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------

Using the same CM-08252012 w/ semaphone 2.0.6.
[Galaxy S I9000 Android Development] pawitp:
If you're using third party kernels, please do not discuss your problems here.
[Galaxy S I9000 Android Development] jugster:
I also had the boot loop problem. For me it was looping at the battery image, and it also turned itself on automatically if I inserted battery and started looping the battery thing. With or without actual cable inserted.

Flashing cm10 nightly 24 solved that for me somehow. I used to think maybe it was hardware related, usb short circuit or something, but seeing as how it worked just flashing another rom it gets harder to maintain that line of thinking. Flashed nightly 25 over 24 still works all right. I hope flashing 26 will too.

Signature? Signature!

---------- Post added at 03:56 AM ---------- Previous post was at 03:53 AM ----------

Also I meant to say, from that boot loop it was very hard, like 1/20 chance to get the into recovery with three button combo. I can imagine for those not hitting the keys exactly right that they would indeed say cwm was broken. I for one however do not believe it ever was.

Signature? Signature!
[Galaxy S I9000 Android Development] lh1366:
gallery flash quit

anybody have this problem? how to fix it?
[Galaxy S I9000 Android Development] jugster:
Works for me in 26.

Signature? Signature!
[Galaxy S I9000 Android Development] lh1366:
stock kernel also has this problem :confused:
[Galaxy S I9000 Android Development] kfheaven:
0826 is up....:thumbup:
[Galaxy S I9000 Android Development] yadavjpr:
Seem new boot animation is included in today's nightly.

http://changelog.bbqdroid.org/#galaxysmtd/cm10/1346026346
[Galaxy S I9000 Android Development] trut:
Last nightly stil have IMEI check ?
[Galaxy S I9000 Android Development] monjovega:
Sorry boss. I did not know problem related with the kernel. Thanks.
[Galaxy S I9000 Android Development] SAINI99:
Partition sizes

what is the partition sizes in latest cm10 after build 17

please run this type of app and paste screenshot

https://play.google.com/store/apps/details?id=partitions.info.pro&feature=search_result
[Galaxy S I9000 Android Development] Ciprilik:
why does CM 10 have only a few couple hundred of MB on Internal Storage and CM9 has 1.9 GB? The size of the Internal Storage partition in CM10 will affect the number of apps you can install without moving them to Usb Storage or it's the same size allocated for apps as CM9 and CM10's different partition method only shows a couple hundred MB without affecting the size for apps? I want to switch to JB if I can still install alot of apps on Internal Storage like I do on CM9.

(Sad to see that CM9's Cid from the bootanimation is not in CM10 too)
[Galaxy S I9000 Android Development] scubadude:
Why not read. This question is answered all over this and other jb threads on multiple occasions.

Best bet search for pawitp posts in this thread and all will become clear.

Sorry I am not more helpful...
[Galaxy S I9000 Android Development] Ciprilik:
I understand the irony and I like it a bit but a little help with a direct answer to my question if you guys know more than I do about CM10's partition system could be useful. It's kinda hard to search for an answer by reading 500 pages and other JB related threads. I just got my i9000 last week and after I rooted it, I installed CM9.
[Galaxy S I9000 Android Development] albertobom:
Yes.

Sent from my GT-I9000

---------- Post added at 06:25 AM ---------- Previous post was at 06:24 AM ----------

Yes, new boot animation has arrived. It's cool but I was expecting more. :p

Sent from my GT-I9000

---------- Post added at 06:28 AM ---------- Previous post was at 06:25 AM ----------

The new nightly is very fast. Thanks pawitp.

We all owe you. ;)

Now we are ready for new features.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] scubadude:
There are not that many pawitp posts to look at in this thread.

The bottom line is a large amount of people had serious lag issues to the point where jelly bean was almost unusable with the old partition layout. This way majority of people are okay. The rom is super fast now. if you have lots of apps it is recommended to move them to sd card.
[Galaxy S I9000 Android Development] karol1981:
Cant connect phone to pc with usb cable- phone reboot bulid 26.08 - only me have this problem??
[Galaxy S I9000 Android Development] Vadrieldur:
Nope i don't have any problem with the usb connection.