yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] yadavjpr:
- How long is the delay : 4-5 Seconds

- Is the delay consistent : Yes but yesterday I installed new nightly build after 15 days, delay time was 2-3 seconds for first 1-2 hours but now delay time is 4-5 seconds.

- Does it occur if you do a factory reset? If not, how do you make it occur? Any apps/settings : Didn't try factory reset now days but I did factory reset when you released first Kitkat build and factory reset didn't solve this problem that time.

- How many apps do you have running : gapps(gmail, hangout, G+, youtube etc), whatsapp, MX Player, PicSay Pro, Google Authenticator, Barcode scanner and 2 small banking apps with auto sync off

- What other things have you tried and how did it affect the issue?

- Logcat : Sorry I can't provide logcat now. I am on vacation in another city :)

- Bug report format?

What is your--

Phone model: GT-I9000

Radio (baseband): I9000XXJVK

CM version: CM11-2014-01-02

CM Download url: get.cm

Gapps version: gapps-kk-20131119

Did you--

wipe: Yes

restore with titanium backup: Never

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: Tried once (before 1 month) but revert back after 2 dyas

other modifications:

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

---------- Post added at 11:30 AM ---------- Previous post was at 11:11 AM ----------

As I know, M1 is not released for our device.

Changelog for M2(Since Fri Nov 22, 2013):

http://jenkins.cyanogenmod.org/job/android/53822/artifact/archive/CHANGES.txt
[Galaxy S I9000 Android Development] pawitp:
Does a reboot bring the delay down to 2 - 3 seconds?

Can you try 2014-01-03 as some users have reported improvements.
[Galaxy S I9000 Android Development] yadavjpr:
No

Sorry, I can't try before monday due to unavailability high speed internet.
[Galaxy S I9000 Android Development] sas_sas:
deleted
[Galaxy S I9000 Android Development] nekuy:
Is there any difference between 2014-01-03 nightly and M2 snapshot? I have ~2 sec delay on both. But zero delay to see line busy if I call phone's own number.
[Galaxy S I9000 Android Development] pawitp:
20140103 contains more recent code than M2.
[Galaxy S I9000 Android Development] :
Incremental updates

Look what's coming up in next nightly!!!! :)

http://review.cyanogenmod.org/#/c/56832/
[Galaxy S I9000 Android Development] jv.batista:
finally...
[Galaxy S I9000 Android Development] Blackherted:
what is it? :eek:
[Galaxy S I9000 Android Development] Nezys:
I guess Delta updates..

Inviato dal mio GT-I9000 utilizzando Tapatalk
[Galaxy S I9000 Android Development] geckoas:
Delay on incomming calls

Yesterday i upgraded my I9000 from CM10.2.0 to CM11 Nightly 20130103 and also got excessive delays during incomming calls.

What is your--

Phone model: Galaxy S I9000

Radio (baseband): I9000XXJW4

CM version: 11-20140103-NIGHTLY-galaxysmtd

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

Gapps version: 20131208

Did you--

wipe: Cache - Yes / Dalvik - Yes / Data - NO

restore with titanium backup: NO

reboot after having the issue: NO / Phone was started today morning

Are you using--

a task killer: NO

a non-stock kernel: NO

CMSettings/Performance settings (other than stock): Ondemand / Row / ZRAM 18% / Min Freq 200Mhz

ART Runtime: NO

other modifications: Jelly Bean Extreme Orange Theme / Nova Launcher / Unlock with swipe / GoDialer

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

The delay between recognition of the incomming call (vibrating) , over output of the ringtone to the display of the screen with the caller UI is different either the phone is shorter( 3-4 seconds) when the phone is active and longer (~ 12 seconds ) when the phone is in standby.

Enclosed you find a logcat of the delay when the phone was in standby:

- Started recording of logcat and switched phone to standby

- Called phone

- At the second ring on the external line the phone started vibration 21:14:26.089

- After 4 seconds the phone started playing the ringtone 21:14:30.089

- After 12 seconds the phone lighted the scren and displayed the caller UI 21:14:38.527

- After this I rejected the call: 21:14:38.535

I hope this description and the enclosed logcat helps you to find the cause for that.

Despite of this, the rom is faster than 10.2.0 and I asume than ever and the old I9000 flys

regards geckoas
[Galaxy S I9000 Android Development] pawitp:
Thank you for the detailed report.

- Can you try uninstalling GO Dialer/GO SMS and see if it has any effect?

- Using adb shell, run "busybox top" and see if any process is excessively using the CPU while you're waiting for the screen to appear or not. Take a few screenshots.
[Galaxy S I9000 Android Development] geckoas:
Hello pawitp,

Uninstalled GO SMS and GO DIALER with no effect to delay.

- Phone at sleep when call started.

-vibration starts after first ring on external line.

- ringtone starts after 4th ring on external line.

- screen and UI starts after 9th ring on external line.

This for the first time. Want to try adb busy box in the afternoon.

Greetings geckoas

EDIT:

When I wake the phone by pressing power-button or home-button after first vibration, the screen goes on instantly and the incall-UI is displayed after about 1 - 2 seconds.
[Galaxy S I9000 Android Development] Onliner09:
Exactly the same behaviour also on my device:

What is your-- Phone model: GT-I9000

Radio (baseband): I9000XXJW4

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

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

Gapps version: Gapps-kk-20131119.zip

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: other modifications: No

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

Gesendet von meinem GT-N8010 mit Tapatalk 4
[Galaxy S I9000 Android Development] cheeseous:
[MENTION=3117667]pawitp[/MENTION] [MENTION=3398651]Onliner09[/MENTION] [MENTION=4640593]geckoas[/MENTION]

Also trying to reproduce this issue... And I can't! I only have maybe 2-4 sec of delay...

The only thing that is different in your setup is the modem... I use JVT and you two don't!

Maybe you should try another modem and see if that solves your issue...!?!

And kudos [MENTION=3117667]pawitp[/MENTION]... My old S never felt better!!! ?
[Galaxy S I9000 Android Development] hornet_II:
Installed cm11M2 yesterday. So far I am very happy. Much better than cm10.2 stable.

Khopungkap Pawitp
[Galaxy S I9000 Android Development] astrosp4c3:
In last version (20140105) we have 371mb of ram , i didnt notice this change in last changelog..however better have more :D

Sent by i9000 KitKat ^-^
[Galaxy S I9000 Android Development] downhere:
Pawitp modified the memory allocation for jpeg encoder in order to gain more RAM...
[Galaxy S I9000 Android Development] freakymod2120:
Yes i flashed latest nightly 10 minutes before and now we`ve got 3 MB more RAM ...it is great which improvements pawitp finds to "upgrade" our RAM

Here are the links to the commits for the JEPG-optimization ...like downhere noticed...

http://review.cyanogenmod.org/#/c/56795/

http://review.cyanogenmod.org/#/c/56791/

http://review.cyanogenmod.org/#/c/56792/

And with next nightly we get some more RAM because of more ZRAM (instead of 64MB 128 MB...)

http://review.cyanogenmod.org/#/c/56892/

Great pawitp thanks for the great great support and development for our i9000 :good::good:
[Galaxy S I9000 Android Development] Nash123:
Hi Pawitp. Made an observation. Bug or (security)feature? If you disable locking via tiles it won't be remembered after a reboot. It needs to be enabled and disabled again to be disabled.

It is my first kk-nightly btw. Switched today from 10.2-stable.

Great work btw! Thx for keeping our device alive. I started with eclair several years ago and now we have kitkat thanks to you and all who contribute :)
[Galaxy S I9000 Android Development] pawitp:
For general issues, install -M2 build and file a report on jira.cyanogenmod.org
[Galaxy S I9000 Android Development] geckoas:
Hello Pawitp,

can't get adb to work. It shows "error: device offline" even if I use "adb kill-server" and connect to different USB-Ports on my computer.

But the delay seems to have gone after i installed XXJVT Modem instead of XXJW4 that i used before, as "cheeseous" posted

- The ringtone apears short after the first vibration and the screen goes on within 3-4 seconds. This is acceptable for me.

Afterwords I installed XXJW4 modem to crosscheck with the same short delay.

Now I'm back on XXJVT, with again the same short delay.

Thanks for all your assistance.

EDIT:

Got adb to work after installation of latest Samsung USB drivers from Android-sync V 1.112
[Galaxy S I9000 Android Development] nekuy:
You can run "htop" command on phone terminal emulator instead of "busybox top" on PC adb shell.
[Galaxy S I9000 Android Development] fatino:
I also wanna confirm incoming call lag. About 2-3 seconds for me. Sorry no logs but I wanna point out that its probably not a modem problem. Its ringing(icon in notifications pops up, even my KDE Connect report on my computer comes) so the connection works only call ui lags. For me even 2 call uis poped up. One with big red bar as if I was calling (wat) and second on top of that with swiping ring to either answer or dissmiss. I dont think it was like that before.

Also next at call call ui comes faster so it kinda stays in ram. Maybe there is a problem.

EDIT: At systempanel before call there wasnt com.android.incallui system process. Its there after the call though and dissapears after some time. Maybe somethings with that.

EDIT2: Its gotta have to do something with how 4.4 handles core android services. They are separate now. So maybe there is the way to keep incallui service always in memory.
[Galaxy S I9000 Android Development] Jammed_Death:
how can i lower the speaker sound? Got an headache at every call...
[Galaxy S I9000 Android Development] pawitp:
I consider 2 - 3 seconds as acceptable. The issue is that some people are claiming to see > 5 seconds delay every time (so process being in the RAM or not would probably be irrelevant)
[Galaxy S I9000 Android Development] fatino:
One time it lagged my phone hard and it took about 10 until it crashed. It was because my phone was under higher load. It depends what I do idle its 2-3 sec. When phone is doing sth more. So I think its the service problem. It has to load each time. So it depends who has what open and how many other services are running. Just my theory.

EDIT: Im almost certain it has sth to do with com.android.incallui service not staying in memory. As I said it dissapears few sec after call. I guess this service was separeted from core android in kitkat in order to save ram. On other versions on android call ui was almost instant.

Again just my theory you might wanna look into that. Maybe some way to keep this process in memory.

EDIT2: Found sth interesting https://code.google.com/p/android/issues/detail?id=64271

Wysłane z mojego GT-I9000 przy użyciu Tapatalka
[Galaxy S I9000 Android Development] jv.batista:
That actually makes sense and I think it's easy to test. Maybe pawitp or someone else could compile a test version with that changed to see if it makes any difference.
[Galaxy S I9000 Android Development] Amrod_Ringeril:
My two cents on this. I use modem JW4 and that's my phone's behaviour when I receive a call:

First tone -> Vibrates instantly, rings almost instantly.

Second tone -> Right in the middle of it, I can already answer, screen is active.

As I already mentioned a few days ago, mine had a slight delay that I could live with (between 1/2 seconds more to react than now), but improved when I installed 20140103 nightly.

Just to clarify that it isn't a modem issue. I'm all on stock, modem JW4 and a lot of apps installed.
[Galaxy S I9000 Android Development] hornet_II:
Call lag:

It starts ringing an vibrating right away. The screen turns on in 2-3 seconds.

Clean install with all the wipes, all stock.

In spite of this glitch I am a happy and grateful user.

My best regards to Pawitp and the developers
[Galaxy S I9000 Android Development] karbon222:
met someone with a problem in the dialing number .. when I press boxes to select the number at the bottom I have a blank white rectangle when I get the key back, and again I press boxes opens dialing

I cleaned the cache dialup and phone applications, new versions nighlty not help

when I installed cm 11 I did a full wipe, the first version was that of December 29, then only another future updates

checked on a basic kernel CM11 and sempahore,

I know that others do not quite have reported this problem, but maybe someone with the same met or solved the problem. Other functions work without a problem.

Thanks for a great version 4.4 pawitp
[Galaxy S I9000 Android Development] pawitp:
Unfortunately, it's not as simple as the bug report since InCallUI is no longer its own package, but a part of Dialer (for reason only unknown to Googlers since the commit message references an internal bug number.)

For testing, I've compiled and attached a version of Dialer with the persistent flag, but it's not a very good idea because it will keep the Dialer (with call logs, etc.) always in the memory. Push it to /system/priv-app/ and reboot.
[Galaxy S I9000 Android Development] jv.batista:
after the update i'm gonna make a backup and try that.

btw: wasn't it supposed to be delta updates already?
[Galaxy S I9000 Android Development] pawitp:
Only support was added to the updater, I don't know when or if incremental updates will be generated (especially for nightlies).
[Galaxy S I9000 Android Development] fatino:
Ill test it as soon as possible.

Wysłane z mojego GT-I9000 przy użyciu Tapatalka
[Galaxy S I9000 Android Development] jv.batista:
so, it goes like this. First call from my land line took around 8 seconds to light up the phone, the following ones light up the screen between the first and the second calling ring on the land line phone, that is around 2 seconds...

with the new apk. going to try with the old after lunch...

even after 20min the call still takes ~2s to light up the phone, so it keeps the same behavior whether its consecutive calls and spaced ones.

in consecutive calls the report is the same for the old dialer. have to wait a bit to see if it keeps this way. what I probably need is a longer test period...

going to keep the new dialer for a full day... will report tomorrow...
[Galaxy S I9000 Android Development] 2k4ever:
call delay

today, i installed CM11 M2 coming from ICS so I still have to find my way around.

thanks for the great work btw!

however i recieved 2 calls and want to share my experience with the call delay:

first call: i was using the phone, phone startet ringing and a black screen (statusbar was visible) appeard.

I'm using EZanswer and i could take the call with the volume buttons as i normally would.

second (test) call - here it gets interesting:

10 minutes after reboot, not having used the phone and screen off.

phone startet ringing immediately and between first and second ring, the call screen appeared.

however after 1 or 2 sec, the call screen was replaced by a a black screen (statusbar was visible)

Therefore, i would argue that loading the UI even if not in RAM is not the problem, but there has to be some bug in the UI itself or there is some overlay loaded on top of it

EDIT: using EZanswer i can reproduce and circumwent the problem!

when activating the Full screen Image mode, I'm NOT getting the black overlay and i can see the regular call screen

hopefully, someone of you having the same prolbems can try out the 2 day trial version and confirm this
[Galaxy S I9000 Android Development] Justchillz:
Here on my SGS1 with the latest NB; SWIPE is not working ):

I can swipe and see the trace, but no text is placed..
[Galaxy S I9000 Android Development] freakymod2120:
On CM11 swipe never work on my device ... i thought it was only me ...maybe the commit for KK comes later ...
[Galaxy S I9000 Android Development] pawitp:
Are you using the gapps package in the OP? Some might not come with the required library.
[Galaxy S I9000 Android Development] freakymod2120:
Short feedback to latest nightly (20140106)

Hi pawitp,

here a short feedback about the latest nightly:

- Known issue "Privacy guard icon not disappearing when exited app" is solved, i have tested with every app i use privacy guard, when exiting the app the icon disappear now :good:

The entry in the know issues can be deleted ...when there is no veto on anyone ...

- The first steps i have tested after flashing the new nightly are great with new ZRAM-Config (128MB). the browser works smoother - in my opinion- especially when opening 4 or more tabs ...and the phone is waking up a little bit faster (from sleep) ...but it is only a snapshot actually ...

So now i`m curious about other opinion/feelings about the latest nightly and new ZRAM-setting ...

Many greetings ...

---------- Post added at 05:14 PM ---------- Previous post was at 05:11 PM ----------

For my part: I had no gapps installed actually ...
[Galaxy S I9000 Android Development] nekuy:
Are you using input language other than English? Swipe only works a few selected language. I can use swipe in English but for my local language.
[Galaxy S I9000 Android Development] pawitp:
Swipe typing is Google's proprietary implementation and requires gapps to be installed.
[Galaxy S I9000 Android Development] Justchillz:
Ah I didn't, I still have the Gapps from my older CM 10.2 build. Will try this at once.
[Galaxy S I9000 Android Development] freakymod2120:
Okay i`m sorry for that...:crying:

Another question about ZRAM:

It is a partition, but from where get it is size (128MB) which parition gets reduced for this from system, data, datdata ???...:confused:

---------- Post added at 05:28 PM ---------- Previous post was at 05:27 PM ----------

Yeah and didn`t install the gapps with CM11 ...;)
[Galaxy S I9000 Android Development] jorgemiguel4:
ZRAM uses RAM, so none of those partitions need to be reduced.
[Galaxy S I9000 Android Development] fran_xda:
Hi, did any of you tried to check the smoothness of pulling notifications if Bluetooth is enabled? I am forced to have Bluetooth always on so my notifications are really ugly..
[Galaxy S I9000 Android Development] tomekrk92:
I tried it and.. it really works! With Bluetooth OFF notification bar animation is choppy for me, but with Bluetooth ON it immediately becomes smooth!
[Galaxy S I9000 Android Development] jugster:
Does zram use gzip, or some other algorithm to compress?

Signature? Signature!
[Galaxy S I9000 Android Development] geckoas:
Where can I activate ZRAM? The setting is not longer available under "Performance/Memory Management" after upgrade to 20130106 Nightly.

sent from my galaxy I9000 running CM11 with tapatalk
[Galaxy S I9000 Android Development] hertzschi:
Commit Message of

http://review.cyanogenmod.org/#/c/56891/ says:

That's also what I see now, I had max. ZRAM compression and now AndroidSystem and SystemUi use slightly more memory than before.

So you can't adjust ZRAM compression for now I suppose
[Galaxy S I9000 Android Development] didhiy:
afaik, it use lzo
[Galaxy S I9000 Android Development] palera:
Tried that too and it works...Weird :-S
[Galaxy S I9000 Android Development] octolith:
Umm, this is weird, but turning on bluetooth really makes the animation of swiping notifications faster. And it's not a placebo, I can confirm this.
[Galaxy S I9000 Android Development] zuphus:
I does not make any difference here (all stock/0601 nightly)

---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------

In both cases the phone is very smooth!
[Galaxy S I9000 Android Development] PxGold:
But it looks like they also made this change:

"aries-common: increase zRAM to 128 MB

This gets compressed to ~40 MB on RAM and may provide benefits

to multitasking."

http://review.cyanogenmod.org/#/c/56892/
[Galaxy S I9000 Android Development] fatino:
Okay so. I tested everything and I came into conclusion. com.android.service.incallui is definitly responsible for the delay. First boot first call 3 seconds delay(it looks like app is loading content for the first time) after the call process com.android.incallui stays running. Second call while this process running, almost no delay (looks like app is loading from ram). Process is still running, after opening some other programms it gets killed. Third call 3 seconds delay again. So it is definitly com.android.incallui not staying in ram problem. Loading times depend on what you do.

I tried your new Dialer.apk. Sure it keeps my dialer in memory but process com.android.incallui doesnt.

I hope you can find another way to keep this process in memory.
[Galaxy S I9000 Android Development] fran_xda:
Well, actually for me is just the opposite: choppy if Bluetooth is on.. ¿?
[Galaxy S I9000 Android Development] knuckles1978:
Confirmed.. I even removed the Bluetooth tile from my quick settings, and still having Bluetooth switched on makes the animation of the notification shade much nicer than if Bluetooth is switched off.

If you try just holding onto the notification shade and keep moving your finger up and down the full height of the screen at a reasonable speed, you will be able to see that with Bluetooth switched on it follows your finger much better. Switch Bluetooth off and try the same thing, and you'll see the notification starting to lag behind your finger the faster you go. Quite a big difference.

Very strange indeed...