yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rycus86:
Black icons on Launcher

Hi!

I had the black icon thingy once on my phone.

I thought I let you know it's not necessary to reboot the phone, force closing it in application menu and going back to home is enough.

It's a bit faster than rebooting the whole OS. :cowboy:
[Galaxy S I9000 Android Development] dafnos:
Does this rom support video calls???
[Galaxy S I9000 Android Development] gabbarsingh2000:
No.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] pmos69:
If you mean 3G video calls, no. Only stock ROMs do that.

If you mean gtalk, etc video calls, yes.
[Galaxy S I9000 Android Development] Rootax:
EDIT : wrong thread :o
[Galaxy S I9000 Android Development] AllNamesTaken:
Google play can't seem to work, I reinstalled rom + google play zip twice, Also wiped cache and dalvik cache before doing this.

Also Apollo crashes sometimes,

Both give, Unfortunately stopped working error, How do I resolve this?
[Galaxy S I9000 Android Development] pmos69:
Why are you installing google play from a zip?
[Galaxy S I9000 Android Development] Skmcheung:
I had thought so too, but after a reboot today its occurred again, saying I've outright got no external SD...

My SD hasn't been wiped tho, its accessible when mounted in recovery.

I've tried wiping cache, Dalvik, fix perms etc.

I guess I'll wait for the next build :)

- full wipe, 20120801 build with stick kernel... even Double Twist still says I'm connected to a PC....

Edit: files are back after trying the usual media storage and media app cache wipes... I just didn't wait long enough, doh. Doesn't change the fact my media still disappears at times :(
[Galaxy S I9000 Android Development] AlwaysDroid:
Would it be possible to use the I/O fix from the transformer that was featured on the portal to fix our I/O issues?
[Galaxy S I9000 Android Development] pmos69:
What they describe is actually the same as the very first lagfixes for the i9000 did (move /data to an external sd card).

The fixes actually worked, wich is a bit strange given the fact that the movinand supposedly has better performance than external sd cards.

But from actual experience, somehow in actual use it doesn't seem to have.
[Galaxy S I9000 Android Development] yahyoh:
ya its look really work i've took look here http://xdaforums.com/showthread.php?t=1803252

but how sdcard faster than nand :eek:

i think data work on ext4 does make it yaffs2 any better ?
[Galaxy S I9000 Android Development] pmos69:
Current /data on movinand is ext4.

The early lagfixes (and this one too) use a ext4 partition on the sd card.

...so the filesystem is not what makes a difference.

Looking at actual benchmark results, and taking into account that the class rating of sd cards specifies

minimum

garanteed performance, not maximum values that can be achieved, the values seem sound.

It's the actual performance of the movinand chip that seems very low in comparison to its specs. Perhaps there's some other hardware bottleneck limiting the movinand's performance.
[Galaxy S I9000 Android Development] yahyoh:
what about optimization libsqlite and sqlite maybe it will help a little to reduce lag and it will give slightly better io

here is mount command from my s2 look like most of partitions run on ext4 not like s1 wich on s1 : system - efs - cache - radio work on yaffs2 only data work on ext4

a/local/bin:$PATH <
app_38@android:/ $ mount
rootfs on / type rootfs (ro,noatime)
proc on /proc type proc (rw,noatime)
sysfs on /sys type sysfs (rw,noatime)
tmpfs on /dev type tmpfs (rw,nosuid,noatime,mode=755)
devpts on /dev/pts type devpts (rw,noatime,mode=600)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,noatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,noatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/res/dev/system on /system type ext4 (ro,relatime,barrier=1,data=ordered)
tmpfs on /system/lib/modules type tmpfs (rw,noatime)
/res/dev/cache on /cache type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/res/dev/data on /data type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p1 on /efs type ext4 (rw,nosuid,nodev,noatime,barrier=1,data=ordered)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,noatime)
tmpfs on /mnt/ntfs type tmpfs (rw,noatime)
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch****t=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/259:3 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch****t=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /storage/sdcard0/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/dm-0 on /mnt/asec/com.DefiantDev.SkiSafari-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-1 on /mnt/asec/se.nena.nenamark2-2 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-2 on /mnt/asec/com.robotinvader.knightmare-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-3 on /mnt/asec/com.qualcomm.qx.neocore-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-4 on /mnt/asec/com.uplayonline.traincrisis-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-5 on /mnt/asec/com.doodle.cheesetower-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-6 on /mnt/asec/com.picsart.studio-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-7 on /mnt/asec/com.games2win.parkingfrenzy-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-8 on /mnt/asec/com.gameresort.stupidzombies-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-9 on /mnt/asec/se.nena.nenamark1-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
/dev/block/dm-10 on /mnt/asec/com.turner.asmajormayhem-1 type ext4 (ro,dirsync,nosuid,nodev,noatime,barrier=1)
app_38@android:/ $
[Galaxy S I9000 Android Development] AlwaysDroid:
I can't imagine what else could be causing it. I find this all very interesting. I never seemed to have lag at all on stock kernel. Also, I know this applies only to custom kernels, but I am finding that disabling fsync makes everything smoother. Probably cause the kernel has time to control other things, instead of constantly waiting for fsync to write its data to our slow chip. So disabling fsync could be a feature put into stock kernel that might help
[Galaxy S I9000 Android Development] yahyoh:
but disable fsync is dangerous to lose data

maybe reduce sync in libsqlite will help ( idk if that can happend :D )
[Galaxy S I9000 Android Development] pmos69:
Yes, but disabling fsync has issues also.

You can also try setting /data to writeback mode:

Enable writeback mode on /data:

su
tune2fs -o journal_data_writeback /dev/block/mmcblk0p2

and reboot.

Disable writeback mode on /data:

su
tune2fs -o journal_data /dev/block/mmcblk0p2

and reboot.

The setting "sticks", and is used the next time the volume is mounted (at boot).

It gives only a small improvement, but anything helps.

Note that writeback mode does not disable the journal. It simply writes the journal first.

The mode is actually similar to what some other journaling filesystems use by default (XFS, JFS, and ReiserFS) - metadata journaling.

Disabling journaling, although possible would be risky.
[Galaxy S I9000 Android Development] AlwaysDroid:
Even on ICS I have disabled fsync and have never lost any data. Maybe its a bit over hyped?
[Galaxy S I9000 Android Development] pmos69:
Don't know much about the S2 storage...

On the S1, yaffs2 is used over the oneNand flash. Yaffs2 is designed to work directly over flash.

ext4 (/data) is used over the moviNand flash, which acts like a block device.

The internal sdcard partition (fat) uses the remaining moviNand storage.
[Galaxy S I9000 Android Development] pawitp:
0804: Fix having to toggle airplane mode for those using SIM PIN.
[Galaxy S I9000 Android Development] packhex:
Great! Download now

Thanks
[Galaxy S I9000 Android Development] AlwaysDroid:
Awesome, work! Thanks :D
[Galaxy S I9000 Android Development] anil76:
awesome..thanks Pawitp !

Now look forward to the fix of vanishing ringtone and media ..the greed never ends :)
[Galaxy S I9000 Android Development] Abyv:
Does it mean that i need to know my pin for my sim? when i flash? to this new build? Bcoz its asking me for a passowrd to decrypt storage?
[Galaxy S I9000 Android Development] DanielSanchez:
Lol
[Galaxy S I9000 Android Development] Abyv:
Huh?
[Galaxy S I9000 Android Development] matesc:
Ty to reboot, or fixing permissions. Did you wipe cache and dalvik cache before flashing the new build? Also check the MD5.

The fix means, that you do not have to toggle airplane mode on startup to get data connection. Only for those people with PIN on SIM.

Very useful! (Similar to +1, solves nothing, as your post!)
[Galaxy S I9000 Android Development] DanielSanchez:
This subject has been discussed a million times before, and if you still don't know how to repair it, then I'm sorry, but my answer will always be "lol".

PS... why would you tell him to wipe dalvik...

Dalvik is always wiped after an update.
[Galaxy S I9000 Android Development] Abyv:
Thank for the answer and the help. Matesc

To Daniel I know my question was stupid tooo but hey if all are Pawitp here then why do we need XDA? we all learn from here and with much interest. Still love my SGS eventhough i have i9300. So dont joke around too much..might get u into trouble one day
[Galaxy S I9000 Android Development] l4m3:
New build/fix works like a charm!!! Thanks!

Gesendet von meinem GT-I9000 mit Tapatalk 2
[Galaxy S I9000 Android Development] DROCSID:
I'll try to upload to my mirror this afternoon. Even on vacation the flashing saga continues. Thanks Pawitp, your updated version with this fix is very welcome.
[Galaxy S I9000 Android Development] bhu1:
Mirror mirror on the wall, is mediafire the fastest from them all ???
[Galaxy S I9000 Android Development] Christophe86:
disabled fsync to see the difference in performance and smoothness. phone - jellybean - is indeed smoother, apps and their content load significantly faster. so it seems that the io of our beloved sgs is indeed not the fastest..

offcourse, keep in mind, cm10 is still in early development.. look at cm9 these days, that's running quite lag free on our sgs. we'll need to have some patience - yes, very difficult for some :p - until jb is more stable.
[Galaxy S I9000 Android Development] DROCSID:
No ;)
[Galaxy S I9000 Android Development] Abyv:
IMEI

Try to flash from xxjvu but seems that everytime i flash on to cm10 IMEI is lost. Any clue? Anyone lost IMEI on the latest build?
[Galaxy S I9000 Android Development] strickyy:
I lose my IMEI whatever I do, so you might do, as well. So backup your efs folder, and restore it when on CM10, and you shall be good.
[Galaxy S I9000 Android Development] Abyv:
Thanks for the reply, So save a copy to SD card? Then..? How to replace it ..would u know?
[Galaxy S I9000 Android Development] firenxe:
You may be flashing gingerbread modems, download ics modems from perka's file stash and flash those instead
[Galaxy S I9000 Android Development] Abyv:
So flash ICS modem then , Full wipe to CM10?
[Galaxy S I9000 Android Development] strickyy:
That doesn't matter afaik. Even the CM7 modems, work exactly the same (atleast they should).
[Galaxy S I9000 Android Development] anil76:
some issues with 08/04 build

Flashed (after wiping cache + formatting /system) rom & gapps --> at start up it stuck at starting apps (after optimizing apps) --> removed battery and then booted again -->stuck at cm9 boot animation (repeated battery removal and switch on process but still stuck at boot animation)

Flashed again....it worked . But there is a lot of lag (I never experienced such lag with last few builds)...a couple of times I get the message "system is not responding".

However I do see few things working which were not working earlier :-

1) I did not need to toggle air plane mode to connect to data

2) widgets before lockscreen is now working.

3) When screen is locked , long press volume is seeking next/prev tracks. Though I had un-install apolo to make it work with google play music.
[Galaxy S I9000 Android Development] Rat2000:
Today will be my first day that i will install Jeally Bean on my device.

Where is a list of known bugs??? or is there something i should not do or i shoud do afther i install this rom???
[Galaxy S I9000 Android Development] jacobuscuracao:
I use Nitrality to both create the backup and to restore it.

the manual method doesn't really work for me
[Galaxy S I9000 Android Development] awandroid89:
bug: Empty gallery and music application in default application for some people and me also..and SD card cant be detect by computer.

other is minor bug.. :cowboy:
[Galaxy S I9000 Android Development] steftouch76:
Hello,

Everythings I've Tried works fine for now except :

playstore, Apollo and youtube. Each time it's a force closed...

Any suggestions to solve this trouble without deleting everything previously installed ?

Thnaks

[edit : Solved]

I've just un-installed the applications with trouble and re-installed the APK

Now everything works fine
[Galaxy S I9000 Android Development] SnoopyDog:
I installed the latest build from today. I had various random crashes of gallery (inside camera app) and google search. I'm using the 20120726 gapps.

After first boot, everything was working fine but from one sudden to the next the gallery crashed when i opened the camera. From this moment on, the gallery was empty. So i cleared the app data for the gallery, cleared dalvic cache and after the boot finished, also google search permanently crashed.

I rebooted again and now both apps seem to work again. Playstore never crashed for me right now :confused:
[Galaxy S I9000 Android Development] pmos69:
http://code.google.com/p/sgscm10/issues/list
[Galaxy S I9000 Android Development] pmos69:
If anybody has trouble compiling their own CM10, I posted a step-by-step guide here:

http://xdaforums.com/showthread.php?t=1813924
[Galaxy S I9000 Android Development] strickyy:
I have an awkward bug with the new build. The screen turns itself on every x minutes. I lock the device, and for 5 mins for example, it turns itself on, on the lockscreen.
[Galaxy S I9000 Android Development] a0a0:
Fantastic :good:
[Galaxy S I9000 Android Development] Paulroberts:
use ES File Explorer File Manager and turn on the root options then copy and paste.

you can use other root apps like root explorer too.

Nitrality didn't work for me when i lost mine.
[Galaxy S I9000 Android Development] Paulroberts:
in the meantime here's a torrent of 20120804 if anyone wants it

magnet:?xt=urn:btih:4E88C84254634AB1CEB72A5A2ACC2AB8131D059E
[Galaxy S I9000 Android Development] jacobuscuracao:
it would be if it were a general problem, but it doesn't appear to be.

Maybe you'll just have to re-flash and maybe this time with a factory reset. After all, it only takes an additional 10 minutes or so to start with a clean slate
[Galaxy S I9000 Android Development] strickyy:
Anyone??? This has occured like many times before, such an awful bug..
[Galaxy S I9000 Android Development] matesc:
Running latest cm10 build.

No problem with meda, ringtones, no FC, Camera works, Apollo and Gallery also (except Gallery settings).

No microlags, finally they're gone :D seems to be the smoothest JB rom for now! Almost as fast as Slim ICS. Impressive.

The battery life seems to be much better than before.

So I stay with stock kernel for now. :)
[Galaxy S I9000 Android Development] maverick340:
For some reason my gtalk is really delaying in sending the IM. I type and hit and and it takes almost a few seconds before it appears in the chat window. As such there is a lag in the conversation. Anyone else facing this problem? I am on Wi-Fi and stock build 20120801 (1st Aug)
[Galaxy S I9000 Android Development] msri3here:
Cool!!! will try it :good::good:
[Galaxy S I9000 Android Development] Abyv:
Last build is nicely flowing. Had issues wen I flashed over - lost imei and couldn't get to cm10 from GB. But back on cm10 after flashing ICS on GB

Thanks to Paw and CM team again
[Galaxy S I9000 Android Development] DROCSID:
Is it just me that from- to time a get, when my phone is just in my pocket,

a continuously bootloop? And semaphore doesn't do the trick but Devil does?

Even grabbing the stock kernel from the ROM and flashing in Heimdall won't

work (and logs are not possible to take off the phone).

Hmmmm........
[Galaxy S I9000 Android Development] kevin2516:
I've had random bootloops too hehe, on semaphore.
[Galaxy S I9000 Android Development] Bonta768:
pmos, have you tried noatime instead of relatime ?
[Galaxy S I9000 Android Development] Krusade:
whats working and what is not? ;) wud definitely love to upgrade :))))
[Galaxy S I9000 Android Development] pmos69:
I think pawitp is already using noatime for the /data partition.

(At least on my phone it is, and I think I didn't change anything)
[Galaxy S I9000 Android Development] gaurav2009:
really i have to say last build was smooth and fast......i tried the first alpha build and moved back to slimics but today i decided to try latest build and i am shocked and happy no bugs from me happy with everything thxx pawitp and teamhacksung... :D
[Galaxy S I9000 Android Development] pmos69:
Everything is working except the coffee maker and 3D printer.

The warp drive is also limited to warp 3, while this is alpha. Warp 5 will be enabled in betas.

It's all listed here: http://code.google.com/p/sgscm10/issues/list
[Galaxy S I9000 Android Development] snapper.fishes:
A little hiccough with custom Widgets disappearing after reboot, and some degree of lag (can get quite bad if you use data intensive apps such as flipboard) , but otherwise everything is working as it should.
[Galaxy S I9000 Android Development] andoceo:
I am the only one who encounter problems with Google Reader ?

'Unfortunately Google Reader has stopped'
[Galaxy S I9000 Android Development] pawitp:
http://wiki.cyanogenmod.com/wiki/Logcat
[Galaxy S I9000 Android Development] pmos69:
Working fine here.

Try clearing its data...
[Galaxy S I9000 Android Development] AlwaysDroid:
Even with a custom kernel the battery is awesome, super smooth and all my ringtones. Just that Apollo keeps force closing :/ can't listen to music until I download another app.
[Galaxy S I9000 Android Development] punticci:
Which is the different?

Ok, i can't understand..which is the real different between this cm10 and the helly bean? Someone can explain to me? I heard that the helly bean is more similiar to CM9 and this CM10 rom is the real CM10..is it correct? (sorry for my bad english)
[Galaxy S I9000 Android Development] yahyoh:
datadata :cyclops:
[Galaxy S I9000 Android Development] rajeshbabushrestha:
Helly Bean is based on CM10 and has /datadata partition (cm9 also has this partition)... CM10 doesnt have this partition and still very fast... except for few users... jus read the thread if u want to have more info...
[Galaxy S I9000 Android Development] ImSo3K:
I can't get it work, I mean I have CM9, I wiped everything thing (factory/data, cache), then installed the rom and afterwards the gapps, I rebooted the phone but every time it's rebooting to CWM, I tried re-install and I got an error while doing it, I tried to install if from another JB rom but still same error so I went back to CM9...
[Galaxy S I9000 Android Development] pmos69:
Helly Bean uses a /datadata partition mounted over oneNAND, like CM9.

That's the only similarity between Helly Bean and CM9.

CM10 mounts the dalvik cache over oneNand (altough a smaller partition than the previous datadata).

Helly Bean uses the Devil kernel (JB), not the CM10 kernel.

Helly Bean replaces, AFAIK, some of the stock apps.
[Galaxy S I9000 Android Development] drBiGBuG:
I solved flashing "CM10 Fixes.zip" -> CM10Fixes.zip after ROM flash
[Galaxy S I9000 Android Development] Gentox:
Updated mirrors in SIG.

Keep up the great work guys. ;)
[Galaxy S I9000 Android Development] oscar73:
Tha lag is real very bad for when some apps are sucking data....
[Galaxy S I9000 Android Development] jacobuscuracao:
I don't know what it is but reading XDA I get the urge to raise my income with currency trading
[Galaxy S I9000 Android Development] gevamran:
i wish from the developer to fix the media scanning issues. i open gallery and all is ok then i play some music. then everything disappear :( i need to reboot till everything be ok :( is there any fix??
[Galaxy S I9000 Android Development] SiriusCybernetik:
Maybe you should redirect your wishes to someone who has more experience with them?

I suggest 'Santa Claus'
[Galaxy S I9000 Android Development] gevamran:
hmmmmm kidding or what exactly? :S
[Galaxy S I9000 Android Development] Skmcheung:
There have been a fair few suggestions for solutions if you search the thread for clear media storage data (including some file permission modifying ones )
[Galaxy S I9000 Android Development] punticci:
But, how much is faster cm10 than helly bean?now i have the helly bean but i'm really confused..i can't choose xD. What i want is to have the best jelly bean rom in rapidity and stability.

Inviato dal mio GT-I9000 con Tapatalk 2
[Galaxy S I9000 Android Development] mikandlotta:
Well, this is not being ignored. I am sure that Pawitp and the clever devs are trying to get that sorted. Be patient, add it to your Christmas wishlist - it is on ours.....

If you cannot live with it you can ask for a refund of what you paid and go back to an older rom that 'works'.

This is an exciting rom, but is still 'unofficial' and 'alpha' So tread carefully, and try not to upset the devs...

pax!
[Galaxy S I9000 Android Development] AlwaysDroid:
Eenie meenie miny mo catch a tiger by the toe if he hollers let him go, etc....

Jk xD

Some people had lags on this, seems to he better now though. Theoretically though, hellybean should be faster because /data is on the faster internal chip, but this works perfectly fine like cm9 for me
[Galaxy S I9000 Android Development] pmos69:
But you can't expect people here to be trying all the JB ROMs everyday just to make comparisons and answer this kind of questions, can you? ;)

Builds come out everyday and things are constantly changing.

CM10 is in alpha stage.
[Galaxy S I9000 Android Development] rkaede:
its all in the OP first post anyway

and please dont compare it each ROM into another. they have their own flavour as what the dev want it to be. just like the CM9/7. Which in the end is providing us the option to use whatever we want.
[Galaxy S I9000 Android Development] jacobuscuracao:
well, we do have to be at least a little bit honest: there's only one Cyanogenmod, on which most other Rom's are based.

Without the work from Cm-team and Pawit, there would be no Hellybean or any other Bean on our I9000.

With all respect for the modifications they make, they make relatively small changes to the big chunk of work delivered by Cm and Pawit and then present it as "their' Rom - with 'thanks' to Cm and pawit. I guess that's OK as it's open source and all, but there could be a little more acknowledgement for the work Cm and Pawit did to enable them.
[Galaxy S I9000 Android Development] yahyoh:
i was trying compare template run cm9 vs cm10 vs s2 with cm10

on s1 cm10 always every 2 or 3 second GC_EXPLICIT trying to clearing dalvik which cuz alot of lag

on s1 cm9 GC_EXPLICIT clearing dalvik like every 1 minute or 40 sec which cuz little lag but not like cm10

on s2 cm10 i didnt see this thing GC_EXPLICIT at all :rolleyes: when game running

is s1 dalvik is too small to make GC_EXPLICIT clearing it very fast which cuz lags in games like template run
[Galaxy S I9000 Android Development] pmos69:
Well, the s2 has more memory, so it's natural it doesn't need to do as many "house cleaning" to clear memory.

Between c9 and c10, the difference seems to be the JB apps seem to be larger.

The most interesting comparison would be between the g1 and the nexus s running cm10...