yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] individual666:
Build 14, stock kernel, came from build 13 without wiping (as recommended in op)

Bugs I've noticed:

Random soft reboots

Screen doesn't reacts on touch during trying to answer phone call coming to phone - very often.

Besides it - good sw.

SGS with ICS. CM9.
[Galaxy S I9000 Android Development] jacobuscuracao:
also got the 'lockscreen won't unlock when receiving a call' - not all the time, but sometimes. haven't tried the power button yet so next time I'll try (this time tried the bottom button, didn't help, neither did trying to swipe)
[Galaxy S I9000 Android Development] wogfella:
You have something funny going on

I have no issue as you have described.

I suggest fixing permissions via recovery or possibly reflashing / factory resetting.
[Galaxy S I9000 Android Development] creative0100:
I'm still having dramas with voice calls.

I am presuming this is the HHB. On incoming calls, I can hear them but they can't hear me. I dial out and no issues at all.

Running B13 stock. Tried a few modems and it happened on all of them. I don't fancy trying B14 as it seems a little less stable to me reading through the thread and B13 has been absolutely spot on, except for this!

I also had this issue on B12.

Any quick fix to see me through to B15?
[Galaxy S I9000 Android Development] pawitp:
It only works with another ICS phone.
[Galaxy S I9000 Android Development] raksan:
Confirmed, I could dialed both cases with no problem.
[Galaxy S I9000 Android Development] chrome6boy:
Do you use Voodoo Control? If so, try changing the "Recording Preset" to Original instead of the default "balanced". This might solve your problem...
[Galaxy S I9000 Android Development] rschenck:
That isn't HHB which is when you can't hear but the person calling you can hear you just fine. You are suffering from something else.

The suggestion to change your Voodoo sound settings is a good one. I would disable every setting you can and see if that solves it.
[Galaxy S I9000 Android Development] creative0100:
No voodoo control here. In fact no control of anything except stock stuff that came with the rom. Stock kernel also. I have had zero problems with the rom and have no need to change anything.

I tried the workaround i read somewhere for HHB of turning the speaker on and off when I answer the call and this seems to work for now so it may be something related?
[Galaxy S I9000 Android Development] chrome6boy:
Some others on this thread have this problem and their solution has been to flash a suitable modem. Try Perka's or Silkydude's modem threads and hopefully your problem gets solved.

Worst case scenario would be to try a clean flash and see if the problem persists...
[Galaxy S I9000 Android Development] rschenck:
Since the stock kernel includes VooDoo Sound, you may also want to install the free Voodoo Control app and make sure everything is set properly....you never know, stuff happens and ROM installs can do strange things.
[Galaxy S I9000 Android Development] Torlo:
It works for me after fix permissions

Sent from my Galaxy S
[Galaxy S I9000 Android Development] got-petrol:
Mines all stock I've fixed permissions and still the same I'm glad I don't have to phone any numbers with 000
[Galaxy S I9000 Android Development] creative0100:
Ok.. For the fourth time I have typed this... This bloody iPad is going to be launched soon!:mad:

I already have perka's app installed. ;) tried 4 or 5 different modems so far and they are all the same.

Installed, checked and tested. Still the same. Happens on EVERY incoming call, not just one or two.

Best way to describe it is it sounds like there is a lot of interference/static. The on/off of the speaker works though so I can cope with that for now.

Would you like a logcat? Might show something?

I will do a fresh install, I just can't be bothered right now as apart from this, the rom is perfect with zero errors or problems.
[Galaxy S I9000 Android Development] rschenck:
Your situation seems pretty unique so I tend to doubt it is ROM related especially if it is unaffected by multiple modem swaps. That leaves...

1) App Interference? Try uninstalling one by one any third party app that uses your speakers such as music apps, see if any of them could be responsible.

2) Bad Install? Try to reflash the ROM, see if that clears it up.

3) Hardware issue? Maybe it is just coininkidink that your speaker/antenna decided to crap out right now. Try flashing back to stock (preferable a pre ICS Nandroid) to see if the problem goes away.

4) Aliens? Avoid open fields or tall figures with large black eyes and wrap your phone in tin foil, just in case
[Galaxy S I9000 Android Development] guijarrelson:
Calendar FCs always if you change the time zone of the calendar. Another bug os when you try to get some info about calendar showed.
[Galaxy S I9000 Android Development] sawari:
Previously I experienced call out disconnected after 2 seconds with cm7 and miui roms but not on Sammy roms. After months of trial and error I changed my simcard and the problem solve. So may be you problem is hardware or even simcard like mine.
[Galaxy S I9000 Android Development] Bizen-Ya:
I have it here too, on a French network.

The third 0 is replaced by 1 or 7

i type 000 => i have "00 0"

i type 7 => i have "00 7"

anyway, a phone number beginning with 000 is really strange .. ?
[Galaxy S I9000 Android Development] rschenck:
I have to assume that the handling of multiple zeros is regional, likely based on carrier/sim card settings.

The question therefore isn't whether it works for everyone, but rather why it ISN'T working for some users in regions where it should.
[Galaxy S I9000 Android Development] wogfella:
Don't come to Australia and try to call emergency services then - it's 000!!

It has to be carrier related somehow????

@Pawitp you ever see this kind of hoodoo voodoo before?
[Galaxy S I9000 Android Development] Doctor Phate:
To all the guys with 000 issues:

Have you tried adding your country code?

e.g. I can't type 0007 too (it magically becomes 007), but if I type +390007 it seems to be working :] (+39 is because I'm from Italy)

Could I get some feedback? ^^
[Galaxy S I9000 Android Development] creative0100:
Gaaaahhh *launches this stupid ipad*

1) no other music type app installed. It's a work phone so only have document type apps installed.

2) it started on b12. I came from darkys rom but I think I will flash stock via Odin and then B15 when it comes out.

3) if it was hardware, wouldn't it be all the time? The on/off speaker thing works which to me says software.

4) now this one is the only logical explanation. I Don't recall any lost time and surely the tinfoil will interfere with the signal more... Maybe that's it, my phone is a clone so the higher powers can spy on the human race..
[Galaxy S I9000 Android Development] Lakerdas:
I wouldn't exclude his providers network. I seem to remember that a guy from Finland posted some time ago in the cm7 thread that after facing the HHB he called his provider and talked with technical support. They told him that it was a matter of their networks incompatibility with stock android technology and that they were working on it. I'm not saying that he has HHB, just that this kind of problems might be a network fault.

Same here, greek network.
[Galaxy S I9000 Android Development] revthanki:
The compass on build 14 is behaving very erratically for me. In standalone apps as well as compass dependent apps such as Google Sky Map.

Could someone run a test for me?

Could you download compass and use it to see whether their compass behaves in an erratic, sticky way (you might want to turn off the "show true north" option in settings of the app). Does yours behave the same way?

I've managed to replicate this problem using both the stock pawitp and alternative cm9 compatible kernels.
[Galaxy S I9000 Android Development] FadeFx:
For me compass is working, it is far from smooth, but it does work, on cm7/fugumod it did not work at all, so i am happy with that.

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] rschenck:
I have heard this a couple times, always in the form of "third-party hearsay", that is "I heard from someone who knows someone in <INSERT SOMEWHAT REMOTE COUNTRY> that called their carrier, and a customer service rep told him it was a problem with the infrastructure".

While I won't say it is IMPOSSIBLE I say it is highly improbable...first of all just because I have yet to see any first party account of it, let alone a screen grab of a helpdesk chat or an email from a carrier saying "It's our antennas!".

Secondly, if this WERE true (old infrastructure antennas of carriers causing widespread, random and unavoidable call failures on Android) we would be looking at a Armageekdon that would rival Steve Jobs telling us we were holding it wrong. Blog posts, CNET stories, Google denials, articles by Mike Arrington, articles attacking the articles by Mike Arrington, Tim Cook talking about it in a keynote, Taiwanese animations, Internet memes....the works.

Therefore as there has been no direct evidence, AND no massive outcry....I have to say I suspect this one is pure urban legend.

Actually...maybe we are just holding it wrong?

BTW: If this IS a carrier based global problem, since I coined the term "HelloHello Bug" I will be waiting for my intellectual property check from the blogosphere, thank you.
[Galaxy S I9000 Android Development] FadeFx:
Compared to my vtab compass it looks like the sgs compass is also 20° - 30° off pointing more west...

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] revthanki:
Yup, it seems to be working in the sense that it can tell you roughly where North is. But it's not much better than that.

Has compass been an issue for a while with Galaxy S? I've just come to this phone from the HTC Desire (a much worse phone in most respects but, at least, the compass worked).
[Galaxy S I9000 Android Development] FadeFx:
Yes, compass and gps is an all time issue...View attachment 871626

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

tapatalked from GalaxyS
[Galaxy S I9000 Android Development] rschenck:
And if you try to point it towards Shenzhen, the phone crashes?
[Galaxy S I9000 Android Development] Luiwammes:
With regards to the compass being off, could the difference be caused by the differences between the magnetic north and the true north?
[Galaxy S I9000 Android Development] mmmalas:
got a stock build 13.

no modification to OS \ kernel etc.

dialler seems to be locking up every now and then, I have to press home button, then close the dialer to reopen it
[Galaxy S I9000 Android Development] jacobuscuracao:
can you load build 14 and try again?
[Galaxy S I9000 Android Development] insanedreamz:
probably the exact case that I am facing from cm7 later builds and still present to some extent, tried b12/14. I can hear clearly but caller hear my voice with a lot of interference. Mostly happens in 3g. And sometimes networks goes off and call hangs then networks gains strength. Voodoo settings didn't help either, temporary fix is mute-unmute. The second issue I mentioned, low 3g signal is the main culprit I think. None of the modems helped me.
[Galaxy S I9000 Android Development] rschenck:
You are also in the wrong thread....
[Galaxy S I9000 Android Development] jelle2503:
how is devil kernel issue related to this thread at all?

plus its your issue. its not happening on my phone at all
[Galaxy S I9000 Android Development] hhouter:
Build 14 also has this, but 5 seconds after lockup it states that contacts is not responding and if you want to close / wait. After closing, redailing and looking up contacts works again as expected... I got the feeling that this issue exists after longer sleep times of the phone..:confused:
[Galaxy S I9000 Android Development] Goldberger:
Anyone used adownloader torrent program? For me allmost all apps work but that adownloader shuts down phone after a while. I got a over 3gb download there.

I think it worked on miui ics but external memory card did not so changed back to this rom. If someone tested it out i would apreciate any info. Btw got the download to 50% about so far.
[Galaxy S I9000 Android Development] fipsib:
same here! (also if you dial more zeros than 3 & it also happens with the legendary 7)
[Galaxy S I9000 Android Development] mmmalas:
thanks for the responses, I guess I will wait until its fixed.

if there is dump, or logs the developers want me to send, I am happy to do that
[Galaxy S I9000 Android Development] revthanki:
could you have hit the fat32 file size limit of 4gb?
[Galaxy S I9000 Android Development] xmen25:
I too see the same exact problem. Though there is no fixed pattern for this.
[Galaxy S I9000 Android Development] Leegalaxy:
Geez, can you guys do this? Just wondering what happens when you enter this many zeros...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Goldberger:
Well it below 4gb and after downloading rom manager it says ext is 256mb. And i doubt that is the problem because its not even one big file.

Need to test with another torrent prog but that adownloader is fastest.
[Galaxy S I9000 Android Development] rschenck:
Total protonic reversal....
[Galaxy S I9000 Android Development] Leegalaxy:
Just as I suspected! Now if we can figure out the HHB™

That's right I beat you too it...

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Doctor Phate:
Hasn't anyone tried to put their countrycode before the zeros? e.g. +44 000123
[Galaxy S I9000 Android Development] insanedreamz:
App issue? May not be related to this thread.

Edit: adownloader shuts down your phone? :rolleyes:
[Galaxy S I9000 Android Development] mrbock:
Here also i get 007 when i type either 0007 or 00007, after 5 zeroes, if i type a 7 i get 000007.

Just reporting. I'd definitely use the country code before the number.
[Galaxy S I9000 Android Development] Goldberger:
Well its first time for me tough. Few days ago i downloaded 1.5gb with 1.2mb/s and worked fine with another ics and not a single mod before this had that kind of trouble.

I think i test another app and clean install this one at friday because im pretty sure adownloader worked on earlier build just fine
[Galaxy S I9000 Android Development] jacobuscuracao:
on 88% after 8 hours 32 minutes ....

I have Build 14, with whatsapp and google talk and twitter and gmail.

I have mail and exchange disabled and I do not have facebook (I go to facebook via the webpage).

I recently removed IMO beta because although I like the client for my MSN, it's a big drain.

so now I have this amazing battery life. Great stuff, tx Pawit!
[Galaxy S I9000 Android Development] Paulroberts:
same here (t-mobile uk)
[Galaxy S I9000 Android Development] Goldberger:
Tested with another torrent program. Works fine with full speed a while and then phone crashes same as the other app. And those have never done that before on any other rom.

All i can do now is to test on clean install but dont got usb cable until tomorrow.
[Galaxy S I9000 Android Development] TigerCourage:
My battery after I calibrated it today...

Edit: It's been like 15 minutes since I'm on 1% and the phone doesn't turn off looool. The most long lasting 1% of my phone's life XD
[Galaxy S I9000 Android Development] mithosu:
Kernel

I have a question about kernel.

I have Glitch v14B1 but I don't know if it has all the things that are in the standard kernel of CM9.

Are them in sync? or the CM9 kernel dose not change?
[Galaxy S I9000 Android Development] dkreventon:
Anyone experiencing an issue like: someone is calling you (he hears he is calling you) but your phone is frozen. The only way to activate it is keep power button pressed for 10sec and reboot the phone.

Happened to me on some roms / builds.

I dunno if build 14 is good replace for my 2.3.6 semaphone. Tried build 11 and 12 but experienced lots of FC
[Galaxy S I9000 Android Development] Doctor Phate:
That should be the Sleep of Death :eek::eek::eek:
[Galaxy S I9000 Android Development] dkreventon:
It is a very bad bug since you may be waiting a courier to call and your phone may freeze. Restarting it manually before going to sleep will postpone the bug.

The only thing is that I don't know if it happens on cm9 build 14.

Also, any major bugs you guys experiencing? (others than listed on 1st post)
[Galaxy S I9000 Android Development] Doctor Phate:
Which kernel are you using? Is Deep Idle disabled?
[Galaxy S I9000 Android Development] habylab:
I'm not getting any sent time on my texts, any ideas before I reflash JVU modem?
[Galaxy S I9000 Android Development] dkreventon:
This happened on various roms (stock and custom), I don't remember any for sure.

Just asking if this happens on build 14 or around this rom

One thing I hate from CM7 and all 4.0 is that there is no delivery report like in 2.2 and 2.3, you just get a little text on screen and that's it.
[Galaxy S I9000 Android Development] _Drifter_:
We only help people that used the standard kernel. If u use Glitch, then ask on Glitch thread or change to the standard kernel.
[Galaxy S I9000 Android Development] Rootax:
There is. You have an icon on the message if delivered. Plus you can long press on the message and show the report.
[Galaxy S I9000 Android Development] habylab:
Sorry is this answering me? About a week or so ago I got sent times, no more.
[Galaxy S I9000 Android Development] dkreventon:
please reformulate, I don't understand
[Galaxy S I9000 Android Development] bajica:
Any of you guys hawe problem where screen wont turn off, i set it to 30 sec delay but 5 mins later it is still on
[Galaxy S I9000 Android Development] kova4a:
Just download from the market GO SMS Pro - it's free and way better than the stock android messaging app. You can get delivery reports and everything you want.
[Galaxy S I9000 Android Development] habylab:
On texts I don't get sent times, only received. Any help or fixes?
[Galaxy S I9000 Android Development] habylab:
Had that since I got the phone a year ago! Read what I said, different to that.
[Galaxy S I9000 Android Development] Besthiroeu:
Happened to me today first time. Im on b14 with stock kernel.
[Galaxy S I9000 Android Development] rootusr:
Same happened to me today, I had to reboot the phone, Build 14 stock Kernel
[Galaxy S I9000 Android Development] insanedreamz:
Phone app is having FCs, on build 14. It was the first time I was trying to merge all duplicate contacts, installed Go Contacts Ex just for the sake of merging duplicates. After I was done, I checked my contacts, everything was fine. Then I uninstalled Go Contacts and tried to open phone app. It said "unfortunately, contacts has stopped" something like that. Reboot, app data clear didn't help. Finally reflashed b14 WITHOUT WIPE, and I have lost one day's sms ie. Of 25th Jan. No idea what happened and why.
[Galaxy S I9000 Android Development] filcar:
Hi, i can´t download mms... Can anyone help me?
[Galaxy S I9000 Android Development] pawitp:
If your phone is rebooting, post the requested info. If a stock app is force closing or not responding, post a logcat. Simply saying that it crashes doesn't help, post logs!
[Galaxy S I9000 Android Development] bobshute:
This may be a bit off topic but it is about CM9 with the stock Trebuchet launcher and there's lots of smart people here.

Below I have a screenshot of the home page of my NookColor. My Nook is running CM9 with the stock Trebuchet launcher. I know it's from a Nook install but other than the device tree it from CM9 nightlies.

I like the layout with the apps icon in the top right, search icon top left, statusbar at the bottom with ICS soft buttons and no dock.

Somehow both Trebuchet (and Nova) launchers know if they are being installed on a tablet vs a phone. I would like to spoof the launcher to give me the Tablet UI on my phone and see if I like it.

Any clues of where the launchers determine which Ui to use? Build prop maybe?
[Galaxy S I9000 Android Development] Jason123420:
Agreed.. this looks way better
[Galaxy S I9000 Android Development] wogfella:
Guys - can we stop posting about 0000000000 issues? Especially people saying "hey I can't do that either!"

I don't know if anyone has noticed, but Pawitp has put the issue on the "known bugs" on the OP.

So....unless we can post something along the lines of "I *had* it but now I don't and *here's why*" then I reckon we're just wasting post space.

Mods feel free to remove and rebuke me if you disagree.
[Galaxy S I9000 Android Development] creative0100:
A little update.

I have been playing around with apps to see if any are causing my not so HHB bug.

It was only then I noticed the DSP app. Now, as it's an app included in the rom, I have never used it and everything was disabled but I removed it with titanium backup and made a few test calls to my phone..... Clear as a bell!

So it may be DSP messing with the calls..
[Galaxy S I9000 Android Development] xt700:
Does it only happen when plugged in? maybe you ticked "stay awake" in develepor options. just an idea
[Galaxy S I9000 Android Development] utsmaster18:
For all the people who cleared data for the music player to work properly, what media scanner did you use from the market to Rescan?

For some reason my phone won't Rescan anything even after reboot, unplugging from computer, nothing. All the scanners I saw in the market were old and the ones I tried were not opening due to Ics incompatibility.

Thanks
[Galaxy S I9000 Android Development] Leegalaxy:
I don't think anyone is using a rescan app. Rather, they are going into dev tools and choosing media provider. Then rescan SD. However, this hasn't worked for me. My google music app is only showing songs from my music account. Not from my phone. Ever since b14.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] xchasa:
I just reboot from recovery.

Open music app then close quickly.

Open again a minute later and all music is shown and plays fine.
[Galaxy S I9000 Android Development] pramathesh:
Anyone else getting FC on Dice Player!? Isn't there an extended settings option as there was in Cm7 where you could have custom brightness levels and have a slew of options for notification power widgets. Seriously missing the notification power widget customization and Dice Player.
[Galaxy S I9000 Android Development] prembox:
Check OP. Don't you see a link there to the CMSettings Alpha download?
[Galaxy S I9000 Android Development] Zatta:
Just download CMsettings.zip from the OP. Flash it, set your settings as far as they are available.

Taptalked u see
[Galaxy S I9000 Android Development] rschenck:
Yep, cmsettings will give you what you seek....and Dice is working fine for me. Try clearing its cache from Manage Apps or fixing permissions.
[Galaxy S I9000 Android Development] pramathesh:
It worked. Thanks for the prompt and quick reply... :)
[Galaxy S I9000 Android Development] rschenck:
I would suspect it is based on DPI, like the Market. If you change your DPI to 160 or so, the Market sees your device as a Tablet and gives you info accordingly.

Lots of DPI changing apps on the market, try it and see.
[Galaxy S I9000 Android Development] zeitgeist181:
Bug report?

i cant play hd videos in my samsung smart Tv with tv out!! i can play it with my phone!:(
[Galaxy S I9000 Android Development] saintblu:
Install CM9 failed

Hi all,

I need help. I failed in installing CM9

My previous rom was CM7.1.

I tried to flash ICS_4.0.3.0(RC3.1)_GalaxyS_Full. The phone rebooted and stuck on the CM9 platypus screen for more than an hour.

Now I'm stuck because recovery failed to load with the platypus screen.

How do I get back to flash the recovery ? any kernel I should install with odin ? I still can get into download mode
[Galaxy S I9000 Android Development] jscurtu:
That wont do it , i think it depends on the actually resolution.
[Galaxy S I9000 Android Development] xrayA4T:
High Battery Drain when not on wifi

Hi, I searched the thread and did not see anyone else mention this. I get excessive battery drain when away from my wifi networks. BetterBatteryStats lists powermanagerservice and wlan_rx_wake as the major culprits. Does anyone know where to start looking? I'm on build 13.