yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] toddmworth:
Yes there is a delay... Of course apps take longer to start from nothing, than to wake up from ram. This is totally normal.
[Galaxy S I9000 Android Development] KennyLegend:
I still didn't notice any lag.
[Galaxy S I9000 Android Development] memphisraynz:
After flashing a nightly a while back I have lost the vibrate function when notifications come through.

Haptic feedback and vibrate during some games still works but i cant seem to work out what has caused this. I have searched through the thread and disabled and re-enabled all vibrate notifications but cant seem to get it to work.

I am running nightly 88 with stock kernel

any possibilities guys?

Thanks
[Galaxy S I9000 Android Development] got_milk:
After flashing and bootlooping and flashing and bootlooping and more of that, I think I've managed to extract the entire bootloader from the new Bell I9000M KG3 Gingerbread release.

WARNING: I have NOT tested this! Flash at your own risk, I am not responsible for loss of data or device failure due to this package!

Known Issues:

- On initial startup, graphic distortion appears instead of the Samsung I9000M logo. Does not affect boot process or device operation.
[Galaxy S I9000 Android Development] utsmaster18:
What's a signature?
[Galaxy S I9000 Android Development] AmTx:
Hello guys,

Firstly,thanks for this nice firmware.

1. I have problem withu Market.It crashes after 5-10 seconds after opening.Tried installing google apps,bt nothing.

2.Also when I change vibration settings it doesn`t use them.Allways is the same vibration type.And for me it is too strong.

Maybe I should write in another topic,but if anyone could help,it would be nice:

LED notification is not working properly (sometimes,with sms).I have instaled CM7 firstly,and then GlitchV11 kernel. What I can try?
[Galaxy S I9000 Android Development] ramanadodda:
1) Go to ROM manager, and click "Fix permissions"

2) It will prompt you "are you sure..." then click on "Yes" button.

3) Takes 2 to 3 minutes to fix permissions.

4) Reboot.

If the above procedure doesn't fix the problem, re-flash the nightly as I had color settings problem and external SD not working problem with Glitch.
[Galaxy S I9000 Android Development] siky_dude:
Hehe..man, galnet took this from cm7.

Cm7 had this feature first, read more often.

What works in cm7 works on miui, and viceversa :)

Miui = iphony cm7
[Galaxy S I9000 Android Development] kobik77:
My MIUI looks far from iPhone ;)

It's more like feature reach and ultra customized CM7.
[Galaxy S I9000 Android Development] ramanadodda:
CM7 is like DEBIAN LINUX

Where as MIUI is like UBUNTU (variant of DEBIAN)
[Galaxy S I9000 Android Development] joeyoong:
how can i set fix ip address on CM7?? running on latest nightly #88

i have check the fix ip address under the Advanced menu and added my fix ip address on to it. Then i save.

the ip address show still is from DHCP server. even i connect and reconnect or turn off wifi and turn on wifi.
[Galaxy S I9000 Android Development] kraven001:
Actually I restored the nandroid backup and it worked. Then I follower the responsible pedestrian steps in the wiki and flashed #88.

All is/was good except for the kswapd0 abnormal CPU usage (got that from day 1 anyways - don't know why, maybe not so many use watchdog lite and are notified of system processes eating up CPU - hope I'm not that special).

Flashed fugu, wasn't impressed.

Flashed Neo 9 and everything stabilized.

Will wait for stable versions of Neo 17.

About full factory reset and go through stock, I don't see the point. I was on stock with a full wipe before. I factory reset and restored apps with titanium. I don't really see benefits of going through this process again other than cleanup of my internal sd.

Will follow the behavior for some time and see how it scales.
[Galaxy S I9000 Android Development] alinescoo:
I've used CM7 for a day :) n80 and went back to stock because one major annoyance: during phone calls the others couldn't hear me. CM7 can have bells and wishles if it can't make the main's phone job, calling, it doesn't really make sense.

Has anything changed in this matter or is the same behavior ?
[Galaxy S I9000 Android Development] Hrithan2020:
Maybe a flash of different modem would help?

I found that unlike stock , CM7 had a huge variance with different modems. [ ZSJPG for instance, which worked very well on stock Samsung ROMs, would frequenlty lose connection to the network..]
[Galaxy S I9000 Android Development] ingbrzy:
Hello..

What are difference between Froyo and GB bootloaders with CM7 build 88...?

I have Froyo bootloader with build 88 and have no problem except battery life... it last just 10-12 hours with idle phone...

I am thinking about try GB bootloader if it will cause better battery life...

Thanks for every answer...!
[Galaxy S I9000 Android Development] kmrdeva:
Seems to happen intermittently to me too. So far not a major annoyance, I just hold and unhold the call and voila! the other party hears me fine again.
[Galaxy S I9000 Android Development] FadeFx:
Pawit, now i did charge overnight using stock Samsung wall charger, i tend to wake up before my alarm goes off in the morning (guess I'm getting old...) and then i browse xda and some news pages while still connected. Now i use it for prox 30min already and i guess the device should have started to charge again as i should have drained 10+% but it sits at 100% 4195mv all the time. When i disconnect, values stay the same. Gonna reboot now to see what happens.

Later:

After reboot i am on 97% and 4023mv, but a 20sec later its 95% 4071mv

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] kmrdeva:
Same here, no lag and no 'black screen of wait' for me with cm7, like I used to get with stock and photoshopped roms. Sometimes though, when first opening an app, I do notice a slight delay when the app launches on screen i.e. the app's title bar and name appear but actual content takes a while longer to show. Perfectly acceptable IMHO, no different than on ios or bb.
[Galaxy S I9000 Android Development] rschenck:
Depends on the app, but it can take as long as 5 or 6 seconds for some.

I am not weeping over it.
[Galaxy S I9000 Android Development] rschenck:
Very wise.

Congrats and welcome home.
[Galaxy S I9000 Android Development] utsmaster18:
Display 106% ftw!

Btw my battery lasted that long after a whole lot of **** done to it. Installed, downloaded data and played a whole bunch of game loft hd games, facebook, xda, twitter internet a whole bunch of stuff. Display been on for 4 hours and talk for 1 hour. Stock kernel. Wifi, 3g, data sync, gps through internet all on

Happy camper :)

What's a signature?
[Galaxy S I9000 Android Development] gaspernemec:
Hehe +10
[Galaxy S I9000 Android Development] gaspernemec:
Yeah go to gingerbread bootloaders. I had awful life with Froyo ones as well. I couldn't reach my phones battery to last more than a day with no heavy usage. Now it can get to 1.5 day with quite heavy usage+my battery is not calibrated.
[Galaxy S I9000 Android Development] ramanadodda:
+1 :d:d:d:d:d:d:d:d
[Galaxy S I9000 Android Development] pawitp:
I'm going to say that that's pretty normal. (Besides the voltage value.)
[Galaxy S I9000 Android Development] FadeFx:
That's what i mean, 97% should still be above 4100 i think .If i don't use my phone now, it will still drain 3%hr...

----------------------------------------

tapatalked
[Galaxy S I9000 Android Development] melorib:
No need, just be carefull to really close Skype, Latitude and other apps that linger around otherwise...
[Galaxy S I9000 Android Development] montymintypie:
Ok, now here's a strange one. Earlier today, things on my phone started to force close. A LOT of things. Browser, Maps, gservices (or similar), messaging, Superuser...

I've tried:

Rebooting (herp)

Permissions fix

Cache clear

Dalvik cache clear

/system format

Ultimate kernel cleaning script V2

Reflash of #88 (with cache clear etc)

Regardless of this, I can't fix it. So, I'm pretty much ready to factory reset and fix it all, as I can rollback to a Titanium backup from 2-3 days ago (Titanium force closes too, so no backup before this :\)

Finally when I got home (oh, did I mention Settings.apk, Market.apk and other assorted apks disappeared after one of the reflashes?) I plugged 'er in, fired up logcat and opened one of the crashing apps.

Spoiler content hidden.

AHA! It's related to database writes. Throwing a disk I/O error whenever it attempts to. Now, this has actually got me a tad worried. Chance of SD card corruption or NAND failure? Or should a factory reset do the trick?

Also, I get the feeling this thread isn't really the prime place to be posting this. Recommend I move to CyanogenMod forums? I've gone here because I don't have an account there yet. :p

P.S. spoiler tags are nonexistant, at least if the preview is correct, and I CBF chucking it on Pastebin. Any good way to compress that for people who don't want to read my logcat?

Edit: /proc/last_kmesg is nonexistant, dmesg shows nothing of use.
[Galaxy S I9000 Android Development] sago62:
Hello guys, now back from holidays .... I downloaded # 88, but consumes a lot even with up to 1000 MHz ... normal?

thanks:D
[Galaxy S I9000 Android Development] rschenck:
Welcome back...but it is pretty tough to help you when we don't know what "a lot" means to you.

Do you mean it uses 5% an hour when idle, or do you mean that when you boot up Asphalt 9 it drains the battery in a few minutes then consumes the souls of all children and fuzzy animals in the room?
[Galaxy S I9000 Android Development] rschenck:
Yes, that is normal behavior due to the "100% Camouflage" fix.
[Galaxy S I9000 Android Development] Dr. Strange:
somewhat offtopic...

Somewhat off topic but still an interesting bit of news:

Kondik joins Samsung Mobile, see more at the link below

http://www.androidpolice.com/2011/0...ile-and-their-babies-will-be-picture-perfect/
[Galaxy S I9000 Android Development] sago62:
.... you're always very nice in the answers ... eh eh eh:D

I noticed that in standby consumes much more ... if I do overclock not talk about it ... is the same to you?
[Galaxy S I9000 Android Development] rschenck:
Congrats to him, it is always fabulous to hear of someone turning what they love into a career.

Perhaps this is a benefit from Samsung supporting TeamHacksung with the sgs2?

I have to say that is good news for cyanogen, Samsung and android overall...however don't expect him to be sneaking the ril source code out the back door.
[Galaxy S I9000 Android Development] KennyLegend:
A full hard reset and sd card format is what's needed here without restoring apps from titanium. Restore one by one till you find the culprit that's doing it.

If you can't understand why or see the point....then just continue on with your abnormal cpu usage.
[Galaxy S I9000 Android Development] rschenck:
I have not seen any notable change in battery life with 88, and I am oc'ed to 1200.

Check your battery use table to see what is using your idle power.
[Galaxy S I9000 Android Development] Dr. Strange:
Well, no, I'm not expecting him to do that... But maybe he can package it nicely and give it a push through the front door. ;)
[Galaxy S I9000 Android Development] sago62:
maybe it's better if you do not flash new nightly every day, leave time to calibrate the battery ..;)
[Galaxy S I9000 Android Development] rschenck:
I think that is very good advice. At this point I only flash nightlies that include changes I want or that include kernel updates. Lately that works out to flashing every 4 or 5 nightlies, but before that I stuck with RC1 for several weeks.

I STRONGLY recommend reading the changelogs and digging deeper if need be to see if a nightly is worth installing, or can be skipped.
[Galaxy S I9000 Android Development] alinescoo:
Thank you for you answer. In this case is a big NO NO for me, I just want to use the phone in a normal way, answer -> talk -> hear :)
[Galaxy S I9000 Android Development] montymintypie:
Sorry for the shameless bump, but anyone got any ideas about my post? I mean, I posted a logcat and everything :(

I'm keeping my phone in a non-functional state in case it could provide useful information, so it'd be swell to get a reply saying whether I should factory reset or not.
[Galaxy S I9000 Android Development] alinescoo:
Who is in charge of this page: What's missing in CM7 page should write there that Calling does not work properly all the time. I think is a very important thing that's not mentioned.
[Galaxy S I9000 Android Development] ramanadodda:
Nice to here that Steve joining Samsung :)
[Galaxy S I9000 Android Development] Dr. Strange:
+1

tenchars
[Galaxy S I9000 Android Development] J_Force:
With which kernel are you nowadays? I am just waiting for glitch v12 since I can't choose an alternative.
[Galaxy S I9000 Android Development] rschenck:
The trouble is that it is a very random problem due to the ril issues, effecting only a few users and not consistently. It comes and goes.

It has been discussed a great deal in this thread....some people solve it by flashing a new nightly, others with a different modem, sometimes it just goes away on its own. However it seems to be different each time.

Go figger...
[Galaxy S I9000 Android Development] Einride:
In adb shell:

busybox mount

and

busybox df -h

What's the output of those commands? Preferrably in pastebin, since scroll bars suck.
[Galaxy S I9000 Android Development] montymintypie:
http://pastebin.com/ujE0ymB9 second command starts at line 27.

I think this may have identified the issue. Uhhh... What exactly is stored in datadata? Isn't that an alias for /data/data? Got no clue why in the world that would be full. :confused: Although I think it might explain why things aren't working as they should...
[Galaxy S I9000 Android Development] Einride:
Yep, /datadata is full and it can cause all kinds of weird stuff, but mostly apps just FC :P

A quick way of checking what's taking up a lot of space in /datadata:

busybox du -d1 -h /datadata

Many games tend to throw large libraries in there taking up valuable space. Uninstalling something is the only solution I'm afraid.

Edit: The reason why /datadata is smaller than on Samsung stock roms is because it's been moved to the OneNAND (Tegrak's "lag fix" for stock roms can do the same). The upside of this is it's fast as hell, the downside is, as you've already noticed, the smaller partition size. It's a reasonable price to pay in my opinion. Others might disagree, of course... (we're on the Internet, of course someone will disagree!)
[Galaxy S I9000 Android Development] DROCSID:
Congratz Cyanogenmod-team!! Cyanogenmod is taking over the world :D.
[Galaxy S I9000 Android Development] d3vil:
Hi there,

Can anyone please test the compass with this ROM, see if it interfears with the accelerometer like in gingerbread ROMs?

TIA
[Galaxy S I9000 Android Development] mobidzid:
And what about the 30MB-limited /cache so we can't install some updates, like for Catan? I think that should be mentioned in the Wiki.
[Galaxy S I9000 Android Development] KennyLegend:
Are you using a theme by any chance? I had something similiar 2 weeks ago. Restored and reflashed a few different nightlies to no avail. Removed ikandee theme and reflashed nightly and all was good again.

If its no this, and ur gonna factory reset, why not start fresh ....old jm9 stock rom, hard reset , GB, root, cm7. Guaranteed to do the trick. Read my post a few back on this.
[Galaxy S I9000 Android Development] mobidzid:
Has anyone else also noticed that XDA Application takes a lot of resources and is one of the main battery drainers recently? It doesn't happen every day and usually force-stopping and rechecking Notifications (in app's settings) helps, but still that's odd...
[Galaxy S I9000 Android Development] KennyLegend:
Not for me....probably my most used app and sits at about 3% of my battery usage.
[Galaxy S I9000 Android Development] upichie:
At what size do you start seeing problems?
[Galaxy S I9000 Android Development] ethanfel:
Actually, after a while (i update my nightly after like 2-3 weeks) my apps take like 3-4s for being launched, sometimes more, sometimes less.

just reflashed 89 and things are back to normal. But there's obviously something wrong. No biggy tough, when it happens i'm updating my cm7.
[Galaxy S I9000 Android Development] Einride:
At any point an application or process doesn't have enough space in /datadata to store/change a file in that partition. Which could be at 2+ MB free space left or <100 KB. It depends entirely on the application, although I'll admit the latter is probably the most common :)
[Galaxy S I9000 Android Development] montymintypie:
For me, I just moved some apps to SD, which freed up about 35MB. Rebooted, still issues with missing apps (no force closes though) so I reflashed again and the apps were still missing. No problems though, just restored with Titanium, then reflashed the Gapps package. All is well!

I always did wonder why Cyanogen was just that fast. Good to know at least why that happened (instead of blindly wiping over and over!). :) I'll be more careful with what I install - and start moving some non critical apps to the 'ol sd. Quick question though, does that move to internal or external? My external is only Class 2 (hooray for 32GB though!) and I sure as hell don't want apps struggling to launch from it.
[Galaxy S I9000 Android Development] kraven001:
I can understand the reason to do that in order to start clean and pinpoint some app that is doing the abnormal cpu usage. But in that case I would expect a certain app to have drainage not the kswapd0. What is still a mystery to me why only the kswapd0 causes the issue, and the big problem is that I saw this day one after restoring things directly from the market without data (only after that I did the titanium restore).

Anyways I will try that also when time permits and see how it goes. I am reluctant to go all the way back to sammy rom and back to CM7 due to repeated flashes that take time and I don't want to be "married" to the phone.

Will most likely go half way and factory reset CM7 and start fresh (cleaning also internal SD card).

As I was stating before, with Neo 9 things work properly.
[Galaxy S I9000 Android Development] katsooba:
Rschenck, whi said something about sneaking it? We just want to 'have a looksie' ;-)

I promise, no touch haha

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Einride:
I guess moving them to the SD card could free up space too, completely forgot about that :o

It is moved to the internal SD (/mnt/sdcard/), not the external (/mnt/emmc), so your slow 32 GB is safe :)
[Galaxy S I9000 Android Development] montymintypie:
Great to hear. :D

Now just to work out how to mount nandroid backups... Accidentally restored the wrong stuff in Titanium and now my messages are 5 days old...

busybox mount -r -t yaffs2 /sdcard/clockworkmod/backup/2011-08-16.04.11.52/datadata.img /mnt/datamnt
mount: can't setup loop device: No such file or directory

Don't have to try and help with this one if you don't want to, not a top priority :)

Edit: turns out CM7 default kernel has no loopback support. Time to go harass a kernel developer... :rolleyes:
[Galaxy S I9000 Android Development] Einride:
Try a mount loop (-o loop).

Edit: Err, didn't see the error message mount gave. Check that both the img file exists (exact path and filename) and that /mnt/datamnt actually exists. You need to create the folder to mount it in.
[Galaxy S I9000 Android Development] montymintypie:
Missed my edit ;)

Tried misspelling both paths differently one at a time, both failed with a different error. Turns out default kernel fails bigtime at loop devices.
[Galaxy S I9000 Android Development] Einride:
Copy the img file to a Linux machine (Ubuntu in VirtualBox works wonders), mount it and push the files manually with adb if you need selective restore. Otherwise, just restore data and datadata in recovery.
[Galaxy S I9000 Android Development] suua:
Thx mate :)
[Galaxy S I9000 Android Development] suua:
Ok, did not knew that, btw usely I read on all CM7 based roms but I have been off for kinda long time now :)

Anyway thx ;)
[Galaxy S I9000 Android Development] aoprea:
+ also automatic brightness not working properly
[Galaxy S I9000 Android Development] siky_dude:
-1, auto brightness working top notch :D
[Galaxy S I9000 Android Development] montymintypie:
*sigh* I'll go dig out my crusty old linux box then... On second thoughts, when am I ever going to read the messages from the past 2 days again... :p
[Galaxy S I9000 Android Development] madd0g:
Yep working here aswell :]

Fresh CM7 SGS user, had it on Desire 1 yr ago and loved it (until Gingerbread Oxygen came out). Now got bored with Samsung stock laggyness (saw that Froyo bootloaders aren't needed anymore), flashed #88 nightly and loving it!

One question about LED notifications, I read that stock CM7 kernel supports "BLN" out of the box without the app. But I cannot see the LED settings in CyanogenMod Settings section. Any info about that ?
[Galaxy S I9000 Android Development] montymintypie:
I think the out of the box support was deprecated a while back (meaning: #15), so just install a custom kernel (Glitch is lovely and I use it, but there are MANY others) and grab the BLN app :) Someone correct me if I'm wrong...
[Galaxy S I9000 Android Development] uberberben:
With custom kernels LEDs are working out of the box without any settings. You can schedule them with quiet hours in cyanogen settings.
[Galaxy S I9000 Android Development] madd0g:
Ah ok, thanks guys, think I'll go for NEO 09-redux_V5 then, seems ok.

I don't O/C anyway, would keep stock and LED support if it was possible. What would be the most "stockest" kernel (if any) ? :]
[Galaxy S I9000 Android Development] :
I'm on darky 10.2...is it correct to full wipe and simply flashing latest nightly / gapps over it?

Thanks!

Sent from me
[Galaxy S I9000 Android Development] montymintypie:
Yep, I did that, worked a treat!
[Galaxy S I9000 Android Development] pawitp:
I'm afraid I can't reproduce the 3%/hour idle drain problem. The battery driver used is exactly the same as that of the Nexus S except for the cosmetic 100%. (Note: The stock Nexus S doesn't charge to 100% either). A reboot will clear the cosmetic 100% and shows the actual battery level.
[Galaxy S I9000 Android Development] AmTx:
Hello again,

I`ve installed firstly glitches kernel(v11),then CM7,but LED notification isn`t still working.

What can I try?

Still have problem with market crashes.Used fix permisions.
[Galaxy S I9000 Android Development] mobidzid:
Works nice for me - see my setup in the sig.

BTW: you do realise you overwrote Glitch with CM7's stock kernel, right?

Market crashes on me, too, but only once and right after reboot. I can use it afterwards without problems. I guess that's the initial check for updates that's crashing...
[Galaxy S I9000 Android Development] zacharias.maladroit:
this is a non-stock & non-officially supported kernel

ask in its thread: http://xdaforums.com/showthread.php?t=1041532
[Galaxy S I9000 Android Development] rschenck:
Thanks...if it happens again I will do that...hopefully I wont have to.
[Galaxy S I9000 Android Development] josteink:
I hope you didn't take my comment as any form of critique. Like I said, this is a problem on stock firmwares as well and I'm perfectly able to live with things as they are.

I just mentioned that any additional improvements you could conjur up, trough black magic, stealing secret Samsung source or whatever means, if they were to come, would be most welcome.

I can't recall a single 3G smartphone I've had which has had good battery-life. I certainly don't expect miracles. Just take the above post as a statement of respect for the work done so far and confidence in your ability to deliver improvements :)
[Galaxy S I9000 Android Development] codeworkx:
You did it again.

Battery drain is no issue or problem.

It's a high-end piece of hardware which is battery powered. That's amazing.

The problem are the bad batterys they ship, not the battery drain.

Smartphones are going faster, faster, faster and more efficient.

What do batterys do? Nothing.