yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pawitp:
- Bug report format

- Logcat + logcat -b radio

- Last nightly it worked fine in

- Do you get a data connection ("E", "3G" or "H"), but no internet access or no connection at all?

- Same with Wi-Fi, can you get an IP, but it doesn't work? Or is there any other problem?

The only real explanation I can think of is your AP has unadvertised half-broken IPv6 support that's assigning you the IPv6 address (why your other devices don't pick it up, I don't know), but doesn't support routing over it. There's no way to disable IPv6 that I know of, but you could try setting a static IP address.
[Galaxy S I9000 Android Development] PxGold:
Keep InCallUI in memory should be in the next nightly (1/21/14)!
[Galaxy S I9000 Android Development] steevo_bass:
I'm not able to set the volume with key when in lockscreen.. Am I the only one??

There is any option to block the launcher like in cm 10??
[Galaxy S I9000 Android Development] tetakpatak:
[MENTION=2531728]steevo_bass[/MENTION] it seems to be a feature of all KK roms
[Galaxy S I9000 Android Development] ranjib:
Since 01142014 the Galaxy doesn't charge in the cradle anymore.
[Galaxy S I9000 Android Development] kodea:
I have broken sync too and google services begin crashing and wifi/carrier icons turn orange. For about 2 months now.
[Galaxy S I9000 Android Development] shreeindia:
Best kernel for CM11?? any advises?
[Galaxy S I9000 Android Development] test123456789012:
I'd go for Stock CM or Mackay Kernel, based on pawtip's kernel (the CMA version, 0.607). Gear Kernel (based on Semaphore) would be a great choice performance wise but I've had issues with lost IMEI in the past, so until this is solved, go for those mentioned above. I've always been a big fan of Semaphore because of it's auto brightness algorythm but development has somewhat slowed down (probably because of it's rock solid stability) and it hasn't got CMA (yet?).

You can't go wrong with stock though. Hope this helps.
[Galaxy S I9000 Android Development] CeesitarJet:
Can someone share me USB Driver for debug? I've installed Samsung USB Drivers but it doesn't work. Please :(

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] tetakpatak:
Check my sticky help thread,the linked driver version should work.

After the installation, you must connect the phone to your PC with the USB cable and wait until installation process is completed automatically (about 1 minute)

---------- Post added at 02:22 PM ---------- Previous post was at 02:17 PM ----------

This is wrong thread for such question, mate. Pawitp's stock CM11 kernel is great and for special features you can browse elsewhere.
[Galaxy S I9000 Android Development] guijarrelson:
Today's nightly must solve incoming calls lag.

Could you confirm that?

Tapatalked from SGS CM 11
[Galaxy S I9000 Android Development] CeesitarJet:
Can you to write the link? I'm not able to find

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] guijarrelson:
I tested the new build without wipe, and the incoming call lag continues.

Tapatalked from SGS CM 11
[Galaxy S I9000 Android Development] pawitp:
details, bug report format, logcat.
[Galaxy S I9000 Android Development] karbon222:
for me is ok, call is on screenn in first ring...

before its second ring, after i saw call

great rom pawit, thx
[Galaxy S I9000 Android Development] ayed78:
i use manual that provide by pawitp no problem...woks great on mackay omni,c-rom...in slimkat too....
[Galaxy S I9000 Android Development] dk147in:
in latest nightly (2101) the call UI lag is fixed the ringing sound comes immediately and UI appears with the very first ring almost test several times and always it came before the 2nd ring come.

Great ROM thanks [MENTION=3391555]pawt[/MENTION]ip.

But I noticed the call UI is not transparent as the caller picture is superimposed by black square until i pick the call, after i picked the call picture appeared in full.... is that a bug or still some work in progress in this direction.

Thanks for the great ROM...

Edit: I am using it with dirty flash with everything as stock.
[Galaxy S I9000 Android Development] pawitp:
If you're talking about a translucent black square, it is working as intended. It's there so you can see the UI for picking up the call regardless of the color of the contact picture.
[Galaxy S I9000 Android Development] ivan_dinchev:
What is your--

Phone model: I9000

Radio (baseband): XXJVT

CM version: CM11 (cm-11-20140121-NIGHTLY-galaxysmtd.zip)

CM Download url: http://download.cyanogenmod.org/?device=galaxysmtd

Gapps version: gapps-kk-20140105

Did you--

wipe: No

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

CMSettings/Performance settings (other than stock): No

ART Runtime: NA

other modifications: None

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Using Dialer I cannot make a call if I tab onto the name of the person I like to call. But if I tab onto his picture I do a call.

I saw for the first time this problem after flashing cm-11-20140117, but in the same time I had call receiving delay. Did clean install of cm-11-20140120-NIGHTLY-galaxysmtd.zip - wiped everything, but the problem was there.

(today's nightly resolved incoming calls lag for me)
[Galaxy S I9000 Android Development] ranjib:
Anyone else?
[Galaxy S I9000 Android Development] tetakpatak:
i9000 help & troubleshooting

Sorry, I have no PC now,just Tapatalk.
[Galaxy S I9000 Android Development] rodman01:
Here is the link to the thread and then you will find in under ref 2: http://xdaforums.com/showthread.php?t=2444308
[Galaxy S I9000 Android Development] tetakpatak:
OK, now I also learned meanwhile how to copy url in Tapatalk. :D

So, [MENTION=5403824]CeesitarJet[/MENTION] it is under 4.1 and JVU bootloader is attached to the OP.
[Galaxy S I9000 Android Development] pawitp:
What do you mean by cannot call? What happens when you tap the name? Which screen are you talking about?
[Galaxy S I9000 Android Development] ivan_dinchev:
When I tab the name of the person I'd like to call appears a message "Unfortunately Dialer has stopped". But if I tap the picture of the same person, everything is OK and I can call him.

I'm talking about the screen which appears when I tap the Dialer button (look at attached pic). The same message appears if I tap the history button (bottom left) on the same picture.

Thank you in advance and best regards!
[Galaxy S I9000 Android Development] :
Hi [MENTION=3117667]pawitp[/MENTION], found some issues after flashing 20140121 over M2.

Catlog attached. As per the log, system cribs "No space left on device" but there is enough space left in the internal storage (600 MB)

What is your--

Phone model: I9000

Radio (baseband): XXVJT

CM version: CM11

CM Download url: get.cm

Gapps version: gapps-kk-20131119

Did you--

wipe: No

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

CMSettings/Performance settings (other than stock): No

ART Runtime: NA

other modifications: None

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Flashed 20140121 over M2 without wipe. gapps, settings, microsoft exchange, nova launcher, whatsapp force closes. Phone was very unstable.

Installed M2 but still apps force closed.

Restored M2 via nandroid backup and everything works fine.
[Galaxy S I9000 Android Development] dk147in:
but in previous nightlies it was transparent (not 100%) but very much able to pick the call while viewing the complete picture of caller, any chance if this can be rectified.

Because importance of caller pic is before you pick the call, to see who is calling and after picking the call the phone is at ear and screen is black.

Due to this black square the face is half cutted for most of the caller pictures...

Hope you understand the phenomena and do the needful.

Thanks

---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------

Today's nightly failed...
[Galaxy S I9000 Android Development] Bejda:
Could be your /datadata partition that is full
[Galaxy S I9000 Android Development] pawitp:
Cannot reproduce. Your package/permission database might be corrupted and you should try a full wipe.

Working as intended, apparently. It's the way that it was originally meant to be in AOSP. See http://review.cyanogenmod.org/#/c/57699/. If you feel that it should be different, file a bug report/feature request at jira.cyanogenmod.org after M3 is out.
[Galaxy S I9000 Android Development] ivan_dinchev:
Thank you [MENTION=3117667]pawitp[/MENTION] !

As I wrote before I did full wipe but didn't help.

Meanwhile today I saw that the Dialer.app in /system/priv-app is zero length. Renamed it and copied there Dialer.app which I took from 20140120. Now everything work perfect.

Regards!
[Galaxy S I9000 Android Development] :
But the problem didn't occur when I restored M2. Didn't notice /datadata size thought. But the apps are pretty much same.

[MENTION=3117667]pawitp[/MENTION], did you get chance to look at the log? Any suggestions?
[Galaxy S I9000 Android Development] pawitp:
Run "df" from adb shell/terminal emulator, you'll probably see that /datadata is full. Of course if you restore an older version, the problem won't occur since the /datadata is the one from when you've backed up. (Apps are stored in /data, apps's data are stored in /datadata)
[Galaxy S I9000 Android Development] :
I'll install nightly again and will check the size of /datadata. In case if it's full, can you please tell me how can I ensure enough space is available?

I use cleanmaster regularly but I dont think it looks /datadata for cache!
[Galaxy S I9000 Android Development] canerpense:
Yesterday I installed this rom for just to look, now I wanna re-flash CM10.2 and it gives Status 7 error. "ro.product.device, ro.build.product"
[Galaxy S I9000 Android Development] idCyber:
To return to CM 10.2 from CM11, you must flash Semaphore 3.3.0 or any other Android 4.3 kernel, then reboot to recovery and flash CM10.2
[Galaxy S I9000 Android Development] dmatik:
Happened to my wife's SGS2 several times. Install Storage Analyzer app from Play Store and check carefully the data partition. In my case she had a lot of strange crash logs of some app that took over 1GB space. After that I just used any file explorer with root access and deleted those logs. Problem solved.

Hope it helps.
[Galaxy S I9000 Android Development] :
Thanks mate.
[Galaxy S I9000 Android Development] roshan2989:
is there any option to turn off the animation in camera..it takes time to save...
[Galaxy S I9000 Android Development] quack75:
In the latest nightly 01.23.2014, I have problems with the bluetooth, I'm the only one? I can't do logcat but maybe someone else can help the development

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] ColinB63:
There was a lot of bluetooth changes in the latest nightly. I just tried my bluetooth speaker and it wouldn't connect. I then unpaired it, paired it again and it connects fine.:good:
[Galaxy S I9000 Android Development] goldstein19:
I also have Bluetooth issues in my car. I will try to unpair and pair again. I will report if my problem remains.

Gesendet von meinem Nexus 10 mit Tapatalk
[Galaxy S I9000 Android Development] quack75:
Ok I try to explain my problem: After unpair and pair my bluetooth headset everything works but if the headset is off when activated again the bluetooth switch my phone says "in connection" (? Without any device on ?) For use again my headset i have unpair and pair all the time

I have tried to wipe data in bluetooth app and wipe all cache from recovery without luck

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] ColinB63:
Just tried mine again and I have to unpair and pair each time as well.
[Galaxy S I9000 Android Development] pawitp:
Logcat and bug report format.
[Galaxy S I9000 Android Development] RowanDDR:
Today's build has replaced my wallpaper with an abstract looking blue photo with a white ring in the middle. #justsaying
[Galaxy S I9000 Android Development] jeromeb4u:
Clock giving fc

I am on latest nightly and its smooth as **** thanks to CM

The only problem I have is with the Stock Clock App

It gives Force Close on the widget as well as when I try to open from App Drawer

Any workaround?

Thanks in advance:)
[Galaxy S I9000 Android Development] Onliner09:
+1. Will provide detailled bugreport +logcat tomorrow, since I have to test it in the car.

Gesendet von meinem GT-N8010 mit Tapatalk
[Galaxy S I9000 Android Development] idCyber:
Go into System Settings -> Apps -> All and clear data for Clock app
[Galaxy S I9000 Android Development] rajeshbabushrestha:
please include cma in stock cm kernel... i was using latest mackay kernel with latest nightly and it was awesome... i moved back to stock cm nightly coz of wifi bug but m missing the extra ram...
[Galaxy S I9000 Android Development] nekuy:
http://xdaforums.com/showthread.php?t=2565658 you can try this kernel till CM solve it.

Attached picture shows available ram.
[Galaxy S I9000 Android Development] pawitp:
If Mackay included the CMA patch as-is (which seems to be the case), then it still has a lot of bugs. The bug is very visible in the log when zRAM is enabled, but also manifests elsewhere as failed memory allocations. There are also other issues such as video sometimes failing to play or the FFC sometimes failing to take a picture. I've also experienced memory corruption which lead to disk corruption during development, which I'm not sure if the issue is present in the current version or not.
[Galaxy S I9000 Android Development] Onliner09:
As promised:

What is your--

Phone model: GT-I9000

Radio (baseband): I9000XXJW4

CM version: cm-11-20140123-NIGHTLY-galaxysmtd

CM Download url: http://download.cyanogenmod.org/get/jenkins/56295/cm-11-20140123-NIGHTLY-galaxysmtd.zip

Gapps version:

gapps-kk-20131208

Did you--

wipe: no

restore with titanium backup: no

reboot after having the issue: yes

Are you using--

a task killer: no

a non-stock kernel: no

CMSettings/Performance settings (other than stock): no

ART Runtime: no

other modifications: no

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Bluetooth connecting (profile: rSAP) in the car is not working any more. Third party app "rSAP" was used, but with cm-11-20140114-NIGHTLY-galaxysmtd and all earlier CM versions (CM10-10.2) this was everytime working without any issues.
[Galaxy S I9000 Android Development] pawitp:
The logcat does not contain any useful information as it's taken from a device app without using root.

Anyway, I've checked and rSAP is a root app which utilizes private APIs. You'd need to ask the developer of the app to make it compatible with CM's new bluetooth stack.
[Galaxy S I9000 Android Development] dk147in:
In todays nightly there is no Trebuchet launcher whereas the CM change log says so...

Why....
[Galaxy S I9000 Android Development] Onliner09:
Uuups. I upped a new logcat (logcat-v2.zip, this time with root) to my previous post and informed the dev of the rSAP app.

Thx.
[Galaxy S I9000 Android Development] CTown:
Trebuchet was taken out before the next nightly was built, see the log. Here is more info about it.

Also, thanks Pawit for actively maintaining the i9000 and Aires-common. My Vibrant and I really appreciate it.
[Galaxy S I9000 Android Development] xsenman:
Good Day,

@pawitp can you take a look at this thread [Q] Cannot update CM11 nightly anymore because I get fault messing’s. by a junior member who cannot post yet in this forum, with attached logcat.

at the same time, IF you have an FAQ somewhere, I would like to add in	[POLL][FAQ][Discussion] Kit Kat 4.4 / CM 11 for Galaxy S & S Plus [i9000][i9001]

Thanks

Check this out! Links to useful Guides and " Banned " Documentaries ​

http://xdaforums.com/member.php?u=3117667
[Galaxy S I9000 Android Development] Maramu:
Anyone else got problems with the weather app? I just noticed it started showing wrong data. Any suggestions on how to fix this?

Sent from a KitKat SGS using TapaTalk4
[Galaxy S I9000 Android Development] latief.makhdoomi:
there is problem with open weather map ,you better choose yahoo weather in settings it will show correct data.
[Galaxy S I9000 Android Development] Anistruk:
Try clean data of the cLock?

p. s. What theme/icons are you using?

Enviado do meu GT-I9000 através de Tapatalk
[Galaxy S I9000 Android Development] pawitp:
The FAQ is located in the first post.
[Galaxy S I9000 Android Development] Maramu:
I've already cleaned the apps data. However, it seems it started showing the correct data again. If anything goes wrong, I'll switch to Y! Weather.

OFF: I don't use any theme, just stock CM + Nova Launcher + DCikonZ icon pack.
[Galaxy S I9000 Android Development] mr.klee:
Is this a daily driver? I wanna flash it on my girlfriend's phone but she can't deal with too many problems..

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy S I9000 Android Development] jugster:
"Nightly" should give you an indication whether you want an argument with your girlfriend or not.

Other than that it's solid.

Signature? Signature!
[Galaxy S I9000 Android Development] roshan2989:
can be used for daily driver bro...:fingers-crossed:
[Galaxy S I9000 Android Development] mr.klee:
Haha, thanks. I think I'll leave the decision to her then. She might be switching to a Moto G soon anyway.

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy S I9000 Android Development] rajeshbabushrestha:
u said there are bugs and im back to stock cm... anyways jus hopin these bugs will get sorted out someday... anyways thankx a lot for supporting this device this far... whatever smartphone you are buying next... im buying it:good:
[Galaxy S I9000 Android Development] andoceo:
Can I come back to 4.3 cm?

4.4 is simply too much for s1, only lags, when i receive a call it takes a minute to show up display so I can see who's calling me, etc
[Galaxy S I9000 Android Development] nexzor:
which nightly you are on? the phone delay bug was fixed in

20140121. after this you should be fine
[Galaxy S I9000 Android Development] rajeshbabushrestha:
copy the cm 4.3 rom and a custom 4.3 kernel to ur sdcard... reboot to recovery... flash the custom 4.3 kernel and reboot recovery... flash the 4.3 cm rom after performing full wipe... profit:good:
[Galaxy S I9000 Android Development] geckoas:
I use it as daily driver with nightly 21.01.14, Semaphore KK-3.4.0s and bigmem patch.

The InCallUI delay has gone and the phone is faster than with CM stock kernel. InCallUI is displayed after 4 seconds for the first call after reboot and after 2 seconds for following calls.

Thanks to pawitp.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] sanguinesaintly:
More Volume steps

Does anyone know of a simple flashable zip to increase the number of volume steps from 15 to 30 ? Or do you recommend using Xposed and a suitable module? Thanks in advance for any help.
[Galaxy S I9000 Android Development] fran_xda:
Hi, I am on Jan 26th nightly and everything seems to work better than M2, except for the choppy notification bar deploy which remains the same: Bluetooth on makes the bar choppy (although eventually can have opposite behavior, Bluetooth off makes it choppy).

How could I help you to solve it pawitp, there are more users having the same issue, not only me. Thank you.
[Galaxy S I9000 Android Development] guijarrelson:
What is your--

Phone model: SGS

Radio (baseband): XXJVT

CM version: cm-11-20140126-NIGHTLY-galaxysmtd

CM Download url: http://download.cyanogenmod.org/?device=galaxysmtd

Gapps version: 20140105

Did you--

wipe: No

restore with titanium backup: No

reboot after having the issue: Yes

Are you using--

a task killer: No

a non-stock kernel: No

CMSettings/Performance settings (other than stock): No

ART Runtime: No

other modifications: No

Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Attached error log of bluetooth, when it tries to connect to handsfree car device.

This device was previously deattached from my device, and from handsfree. When I try to force connection from the SGS, or from the handsfree device, the result is the same: they can't connect.
[Galaxy S I9000 Android Development] HalphaZ:
Hello. I'm using 20140126 nightly and I have a problem with WhatsApp notification sounds. I simply can't ear any notification sound from WhatsApp, instead notifications on system bar and soft key light works as usual.

Maybe I'm the only with this problem...

What can I do?

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] fran_xda:
I can hear the notifications.
[Galaxy S I9000 Android Development] HalphaZ:
Ok, thanks. So I suppose it's a problem on my side.

I don't use Profiles... Maybe I can disable them and see what changes.

Thanks.

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] pawitp:
- What is the model of the handsfree device?

- What do you mean by "detached". Are they unpaired or just disconnected? Can you get a logcat of pairing them?

- Please describe in detail what are the actions you did when you produced each log file.

- Can you confirm that the 20140123 is the very first nightly that has the problem? (i.e. 20140121 doesn't have the problem?)

--- Also get a logcat of a successful connection on a working nightly.
[Galaxy S I9000 Android Development] guijarrelson:
I mean unpair, sorry.

The device is a Parrot CK3100, a very well know device, and with some long life (I bought it some years ago, and it has the firmware update to the very latest version).

I can't confirm if the problem appears in 20140121, because I didn't get my car in that date.

Two logs must be the same, The difference is that catlog records the first one in "real time", when I did the tests. The second one (it has a "2" in the name) is the background log that it catches in the same time when I started the record. I attached it because it can contains more info about.

First of all, I upaired the handsfree in my SGS, and my SGS in mi handsfree device. I paired they before the testings without any error. Then, I switch on bluetooth in SGS with no success connection.

Then, I force to connect to handsfree from SGS. The same state, no success connection. After that, I force the connection from handsfree device. The same result.
[Galaxy S I9000 Android Development] pawitp:
Please revert back to 20140121 nightly and test it (and also get a logcat).
[Galaxy S I9000 Android Development] guijarrelson:
Can I flash that nightly over the latest one without wipe to do this test?
[Galaxy S I9000 Android Development] pawitp:
Generally, yes.
[Galaxy S I9000 Android Development] Makifylmz:
I have issue on nightlies . some notifications not showing normal. I have a screenshot. Everything stock, just changed dpi 182.

http://i.hizliresim.com/wvn9qp.png

http://i.hizliresim.com/w1M5XG.png
[Galaxy S I9000 Android Development] ts1506:
I think you have changed the dpi. Change it to stock 240 and check again.
[Galaxy S I9000 Android Development] Amrod_Ringeril:
Weird.. I have received a phone call today. Phone was ringing, but the dialer didn't show.. Once lost the call, tried to return the call, but dialer.apk is missing. I was in saturday's nightly. I have just updated to today's nightly, and the problem persists.. I'm all on stock and it's the first time I experience something like this...

Before trying to do a full wipe, can anyone try to reproduce?

Thanks in advance!!

EDIT: And it gets even more weird.. once lost the call, if I return the call using the shortcut in the status bar (lost call/redial), it actually makes the call, but there's no sign in the phone, it just shows my desktop and I have no access to the dialer's options.