yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] hollandais:
Yes, I've the same problem, and also on my G Tab 2 P 5110 with the nightly 20131002, but I can't say that I had it before, I don't use this fonction.

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] idCyber:
Tapatalk 4 works fine
[Galaxy S I9000 Android Development] gargeya_369:
My xda app is working fine...

I am also getting notifications wen ever anyone posts...
[Galaxy S I9000 Android Development] hollandais:
It's not the place here, but my tapatalk 4 doesn't send me notifications anymore, I should look myself.

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] kasper_h:
Changelog of 3.3.1 - 02-Oct-2013

-Updated CM10.2 codebase to 3-Oct

-Fixed the Settings>buttons FC

-Fixed translation error in Mackay Settings

-Removed reboottocwm.zip script as kernel is TWRP-only

-Added option for delayed SMS sending

Downloads:

XDAfileserver

Rootaxbox
[Galaxy S I9000 Android Development] kasper_h:
Anyone having issues with screen turning itself off spontaneously? I have this issue since about a week (I actually also have the issue that the screen sometimes does not turn on when I press the power button, so the opposite of the new behaviour). I am a bit afraid that my phone is getting old, but if others have the same it may be just a firmware issue...
[Galaxy S I9000 Android Development] warhead1978:
i think it is an issue on active display timeout option...
[Galaxy S I9000 Android Development] tsatomas:
maybe these issues comes from Cm, I had them for a while in my tab2 (with pacman rom,that has part of cm ) but after an update they fixed . by the way I know you are involved in Rom for galaxy tab,can I have a link or details? (you can pm if you like due to off topic)
[Galaxy S I9000 Android Development] saszseb:
No.

Power button works fine here.
[Galaxy S I9000 Android Development] thETImo:
Occasional hickups here.

Sent from my Nokia RinGo
[Galaxy S I9000 Android Development] Ramsey:
Hmm.. I don't have active display enabled, and I don't have the issue of the screen shutting off but sometimes when I want to wake the device with the home button, I may have to press twice. I think the power button works everytime, just some lag sometimes and I don't understand why it lags.. Could be google sync causing slowdowns in our old phone.

Yes our phone is getting old, I'm surprised it's so reliable though! I got it in June 2010 when it first came out, but I don't know how long it will last. I am afraid it may die one day lol. I'm waiting for an awesome camera phone before my next purchase, something like the 808 pureview camera quality but with a LG G2/Note 3 cpu/gpu hardware.
[Galaxy S I9000 Android Development] Adalbert52:
I have long been a fan of Kasper and his work. Everything was OK to version 3.2.9. Flashing 3.3.0 and 3.3.1 unfortunately end in failure. Phone is frozen on reboot screen. It does not help either hard reset or flash clean GB.

Sorry for my english.
[Galaxy S I9000 Android Development] BigBadBoy:
I saw it happen today and then I saw your post...

But, I can reproduce the behaviour:

- cover light sensor for about 10s (simulate «in pocket»)

- uncover light sensor (remove from pocket)

- unlock the phone

- cover light sensor and screen turns off

I have Active Display on... it seems that it's not recognizing that the wake up was manual... there was no notification to display...
[Galaxy S I9000 Android Development] kasper_h:
For me it also happens when the phone is just lying on the table without being covered...
[Galaxy S I9000 Android Development] Ramsey:
I'm having an issue and I have no idea if it's related to our phone, the ROM, the country I'm in, or the service. But when it comes to a phone call where I have to select 1 or 2 or whatever number, sometimes it doesn't work, I have to reset the phone call. Let's say it does work, then during the phone call, many times it disconnects on its own!

That doesn't happen to me when I talk to people who have normal phone numbers.

Is that a ROM problem? do you think it's because I froze Cell broadcast?
[Galaxy S I9000 Android Development] mamoto66:
Kasper,Some co-HTCMania Spain have problem:bears no screenshots,but to others if this is my case.Any idea?Thanks.
[Galaxy S I9000 Android Development] kasper_h:
I frequently use my phone for calling (how bizarre for a phone ;)) and never have such issues.

I didn't freeze sim toolkit or cell broadcast, but I don't believe they may be causing this.

Could you try getting a logcat?

If /sdcard/Pictures/Screenshots has been deleted by the user, it will not get recreated automatically and will lead to problems with screenshot saving.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] Ramsey:
Sorry I won't be able to provide a logcat. 1. I don't know how to and I don't have much time now. 2. It will be hard to reproduce since it doesn't happen all the time, and it's only with certain companies.
[Galaxy S I9000 Android Development] kasper_h:
OK, but then I also won't be able to do anything to try and solve it....
[Galaxy S I9000 Android Development] dkGof:
I have discovered what seems to be a memory leak in SystemUI, slowly over a couple of days the memory usage of SystemUI creeps up over 200m+ of memory which results in alot of launcher reloads, and generally slow performance switching between apps.

Rebooting or force closing SystemUI to make it reload seems to fix this for a couple of days until it has grown in memory footprint again.

Im not excactly sure when this started, since i might not have discovered it because of frequent reboots, but i know i saw it first in 3.2.8 althoug it might not be when it actually started.

If i can do some testing to help figure out why this is happening im happy to help.

/Gof
[Galaxy S I9000 Android Development] kasper_h:
Interesting observation. I test so many kernels that I never go without rebooting for more than a day or two. I have no idea whether there are apps or adb commands that may help finding more details about RAM assignment, never dived into that...
[Galaxy S I9000 Android Development] thETImo:
I haven't seen the weather icon of cLock on my lock screen since v3.2.4 unless I use the analogue clock. Really odd...

Sent from my Nokia RinGo
[Galaxy S I9000 Android Development] matcho13579:
Same behaviour, but after about 10 hours without restart
[Galaxy S I9000 Android Development] kasper_h:
LockClock is currently being redesigned upstream, so I am not putting any of my time in it.

That is quite extreme, only 10 hours. I would be very happy if someone has an idea how to further troubleshoot this issue, as I have no experience in that.
[Galaxy S I9000 Android Development] matcho13579:
Me neither, I can only change minifree values, but already tried that with no result.

Oh, actually it's 13, not 10 hours, but still awful. I'm considering reverting back to 4.2.2, my device could have been turned on for about a week with no hiccups.
[Galaxy S I9000 Android Development] tsatomas:
may be you should try an app that free memory auto, I use autokiller memory optimizer(play store) which have some tweaks and I have very rare issues like that.
[Galaxy S I9000 Android Development] Rootax:
Same problem here, have to stay on 3.2.8. After that, stuck on the galaxy s screen, even after 20 minutes.
[Galaxy S I9000 Android Development] kasper_h:
So not even a bootanimation? Could you see whether you can capture a logcat? If flashing semaphore kernel, could you please collect the /cache/boot_old.txt file and send it to me? I can't understand why it works fine for most people and causes bootloops for others :S
[Galaxy S I9000 Android Development] matcho13579:
Tried that, but I don't trust to apps like that, Android is intelligent enough to kill processes itself.

Actually, if it's SystemUI what is cause of these problems, it cannot be killed so easily, so I'm using soft reboot via Xposed Installer, there is such an option
[Galaxy S I9000 Android Development] Darkimmortal:
No idea what's changed, but 3.3.1 seems to be dramatically faster than 3.2.8 - nice job :)
[Galaxy S I9000 Android Development] Rootax:
No, no boot animation. The phone was cold so nothing was happening I guess. My priority was to use my phone again, I didn't think about semaphore so no logcat, sorry :/
[Galaxy S I9000 Android Development] hollandais:
I'm one of them who flashed all the latest rom's, and I've not had your problems.

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] Ramsey:
One of the inconveniences of CM based ROMs. I prefer AOSP and AOKP as in 4.2.2 it could run for a week and a half without rebooting it and without slowdowns. I always had problems with CM. I remember Gingerbread Darky ROMs, which were terribly buggy, and it starts out fast for the first 10 minutes after installation, then lag and crashes for the next 2 weeks and suddenly the whole system would crash, causing a restart, and then I find that all apps and settings were deleted, meaning it used to do a system format on its own every 2 weeks. I was using another CM based ROM Gingerbread 2 years and a half ago and I was once outside in another city that I don't know, and my phone restarted while I was using it and defaults to original settings, removing all apps. I had to go back to normal Samsung firmwares until the release of Jelly Bean.

I'm glad CM is much better now since 4.2.1 but there are still issues. I am not sure if other phones have it, but if it's always the same issue, then I don't know how well their new business will go...
[Galaxy S I9000 Android Development] kasper_h:
Small update to 3.3.2

Fixes the error that causes screen off when proximity sensors gets covered (and active display is enabled).

And some other small bugfixes

And the latest 0.509 kernel

Downloads:

XDAfileserver

Rootaxbox
[Galaxy S I9000 Android Development] Hampy:
Flashed 3.3.0 yesterday but keyboard fc so i cannot type anything, my back button dont work, my menu soft button dont work, went back to 3.2.9.
[Galaxy S I9000 Android Development] filipevale:
Anyone having sound quality issues? sounds like there is some kind of reverb effect always on, music sounds poorly.
[Galaxy S I9000 Android Development] Ramsey:
Did that happen with other keyboards or only the JB one? I use TouchPal X and I don't have an FC problem. I do have a problem though where sometimes it minimizes itself and won't come up again until I press home button. Kind of annoying. Did not happen in 4.2.
[Galaxy S I9000 Android Development] Hampy:
Didnt try any other keyboard.
[Galaxy S I9000 Android Development] Ramsey:
Hmm. I'm on 3.3.2 now and I am experiencing crashes in games when I never had them..

By the way, I still can't bootup normally so I had to again odin flash semaphore.

However, I tried to install the following Mackay kernels to test:

502 CWM: working fine, can bootup

508 CWM: working fine, can bootup

509 TWRP: working fine, can bootup

I am assuming that something is going wrong during the installation of Mackay ROM with the Mackay Kernel since Mackay 3.2.9 if I remember correctly.. Since the kernel is working fine when I install it alone..

I'm back to 3.3.0 now and I installed the mackay kernel right after installing the ROM, before rebooting, and it works fine.
[Galaxy S I9000 Android Development] saszseb:
No prob with stock keyboard here.

---------- Post added at 06:19 AM ---------- Previous post was at 06:05 AM ----------

Nothing wrong with the install of last Mackay's ROMs.
[Galaxy S I9000 Android Development] gargeya_369:
+1

---------- Post added at 10:35 AM ---------- Previous post was at 09:52 AM ----------

flash gapps provided.....the keyboard and the touch buttons will work
[Galaxy S I9000 Android Development] kasper_h:
For keyboard issues, you should indeed reflash gapps and make sure to flash the correct gapps (for JB4.3).

For the kernel, I just compared the flash scripts for a separate kernel flash and for the ROM flash. These are not the same: when flashing only the kernel, the boot partition is wiped before being written, which does not happen for ROM flashing. But the behaviour of my ROM script is 100% identical to stock CM10.2 flash scripts, so if you have a problem with my ROM you should also have a problem when flashing stock ROM (both cases without flashing an additional kernel on top).
[Galaxy S I9000 Android Development] thETImo:
Anyone else feeling the v3.3.1 is a bit laggy? Is the memory leak still possible? Usually the rom has been snappy right after flash, but not this time. I came from v3.2.6.

Sent from my Nokia RinGo
[Galaxy S I9000 Android Development] saszseb:
No flash gapps>>> no problem with keyboard.
[Galaxy S I9000 Android Development] warhead1978:
System UI is going crazy after a while...

My Keyboard closed sometimes (no FC) too, but after reboot and fresh RAM no problems to type here...

I think the bloated Google services stop the smoothness of our "old" phones, no one work with an old phone to create new apps/services/features, the old hardware/software story...

MfG
[Galaxy S I9000 Android Development] tsatomas:
I am in build 3.3.2 without fc in keyboard (using pa gapps)or crazy system ui.

Just for info I have read in Hellybean thread that they also have more or less the same slow down and lag problems so may be it is not coming from the ROM itself but deeper.
[Galaxy S I9000 Android Development] Blondasisko:
Hi, I decided to try JB 4.3 finally, coming from the last Infamous. I flashed 3.3.1 after all wipes. After the second flash and gapps, rebooting lasted forever. So one more flash, this time there was a message "unable to mount data". In fact I could not do it manually in TWRP either. I flashed Semaphore by Odin, and again could not mount data. I formated data then and flashed again. This time it worked. After flash the ROM was very fast. Certainly is not that fast after installing many apps. I also see bloating System-UI, now about 90 MB. Everything else is working fine.
[Galaxy S I9000 Android Development] hollandais:
Hi,

I've never seen this screenshot before, can you tell me where I can do that in settings?

And if this is made with an external app can you tell me which one?

Thanks

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] Rootax:
Yeah same issue with stock cm 10.2 (2-oct). Did they change the install script few days ago or something ?
[Galaxy S I9000 Android Development] kasper_h:
What I am interested in, is what SysUI processes take up this amount of RAM, because that could lead to a better understanding and maybe solution.

But I also think that we are stretching the lifetime of our phone already quite a lot: RAM-wise we are on the very low end. So I doubt this problem can be really solved.

Is someone here running this ROM without gapps? Because I would be interested to see RAM usage without gapps (to be able to assess whether it is the google framework that is causing the issues).
[Galaxy S I9000 Android Development] kasper_h:
The install script was updated by pawitp to accomodate the changes of minivold in CWM. But these updates do not relate to the kernel flashing part of the script, only the SD-card mounting.

Everyone, can you please supply the following information:

-Which ROM version did you install the last time?

-Which kernel version were you using before flashing the new ROM?

-Which recovery were you flashing from (TWRP or CWM)?

-Did you have a bootloop?

-Any add-on/kernel/script you install on top of the ROM by default?

-Do you have an external SD?

-Do you flash from internal or external SD (where is the zip file located)?

If using TWRP and having this problem, I would like to ask you to do the following steps:

-reboot to recovery

-flash ROM (and nothing else than the ROM)

-go to Advanced -> Copy log to SD

-You can now flash the kernel separately to enable booting your phone

-Reboot the phone, and upload the file /sdcard/recovery.log to any place you like (or copy the contents to a pm to me).

I know this are many questions, but it is the only way to test my hypotheses. The more reports I get (also from people with the problem, because I also need reference data).

My own info:

-Which ROM version did you install the last time?

3.3.1

-Which kernel version were you using before flashing the new ROM?

0.509-twrp

-Which recovery were you flashing from (TWRP or CWM)?

TWRP

-Did you have a bootloop?

no

-Any add-on/kernel/script you install on top of the ROM by default?

no

-Do you have an external SD?

no

-Do you flash from internal or external SD (where is the zip file located)?

internal
[Galaxy S I9000 Android Development] Blondasisko:
for me

-Which ROM version did you install the last time?

3.3.1

-Which kernel version were you using before flashing the new ROM?

last for infamous 4.2.2, do not remember

-Which recovery were you flashing from (TWRP or CWM)?

CWM

-Did you have a bootloop?

no, just stuck on blue bootlogo

-Any add-on/kernel/script you install on top of the ROM by default?

no

-Do you have an external SD?

yes

-Do you flash from internal or external SD (where is the zip file located)?

internal
[Galaxy S I9000 Android Development] idCyber:
First time I came from CM 10.2 01/10/2013 with Semaphore 3.2.0s CWM to Mackay 3.3.0, did not encounter any bootloops from that version to 3.3.1 followed by 3.3.2 using Mackay kernel's TWRP recovery every time, just updating the kernel when new one was released at that time.

My current Info:

-Which ROM version did you install the last time?

3.3.2 coming from 3.3.1

-Which kernel version were you using before flashing the new ROM?

Mackay kernel 0.509 CMC

-Which recovery were you flashing from (TWRP or CWM)?

TWRP

-Did you have a bootloop?

no

-Any add-on/kernel/script you install on top of the ROM by default?

nothing except latest CM10.2 gapps

-Do you have an external SD?

Yes

-Do you flash from internal or external SD (where is the zip file located)?

External SD
[Galaxy S I9000 Android Development] tsatomas:
My info

Which ROM version did you install the last time? Mackay 3.3.2 coming from 3.3.1 ...coming from Mackay4.2

-Which kernel version were you using before flashing the new ROM? Rom kernel

-Which recovery were you flashing from (TWRP or CWM)?cwm since kernel 0.505,after (rom3.2.9) twrp

-Did you have a bootloop? no

-Any add-on/kernel/script you install on top of the ROM by default? No

-Do you have an external SD? Yes[

-Do you flash from internal or external SD (where is the zip file located)? Internal

Gapps: PA
[Galaxy S I9000 Android Development] hollandais:
Hereunder my info:

Which ROM version did you install the last time?

Mackay 3.3.2 coming from 3.3.1 ...coming from Mackay4.2

-Which kernel version were you using before flashing the new ROM? Rom kernel

-Which recovery were you flashing from (TWRP or CWM) twrp

-Did you have a bootloop? no

-Any add-on/kernel/script you install on top of the ROM by default? No

-Do you have an external SD? Yes[

-Do you flash from internal or external SD (where is the zip file located)? Internal

Gapps: PA

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] saschc:
Hereunder my info:

Which ROM version did you install the last time?

Mackay 3.3.2 coming from 3.3.0

-Which kernel version were you using before flashing the new ROM? 0.509_CMC

-Which recovery were you flashing from (TWRP or CWM) twrp

-Did you have a bootloop? no

-Any add-on/kernel/script you install on top of the ROM by default? No

-Do you have an external SD? Yes[

-Do you flash from internal or external SD (where is the zip file located)? Internal

Gapps: PA
[Galaxy S I9000 Android Development] fmc000:
-Which ROM version did you install the last time?

3.3.1 coming from 3.3.0, 3.2.9, CM10.2 20130920 with MacKay Kernel

-Which kernel version were you using before flashing the new ROM?

the one included in 3.3.1

-Which recovery were you flashing from (TWRP or CWM)?

TWRP

-Did you have a bootloop?

no (never had one)

-Any add-on/kernel/script you install on top of the ROM by default?

no (only gapps from goo.im)

-Do you have an external SD?

yes

-Do you flash from internal or external SD (where is the zip file located)?

internal
[Galaxy S I9000 Android Development] SKLCH:
It an app called "Android System Info"

you can find it here: https://play.google.com/store/apps/details?id=com.electricsheep.asi
[Galaxy S I9000 Android Development] hollandais:
Thanks,

Downloaded and installed

Envoyé depuis mon GT-P5110 avec Tapatalk 4
[Galaxy S I9000 Android Development] matcho13579:
-Which ROM version did you install the last time?

3.3.0 (came from Helly Bean)

-Which kernel version were you using before flashing the new ROM?

Devil Kernel (after installing Mackay ROM I didn't flash other kernel than the one included in the ROM)

-Which recovery were you flashing from (TWRP or CWM)?

CWM

-Did you have a bootloop?

no (never with Mackay ROM)

-Any add-on/kernel/script you install on top of the ROM by default?

If Xposed is counting as addon, then yes, also I did some Xblast Tools build.prop tweaks

-Do you have an external SD?

yes

-Do you flash from internal or external SD (where is the zip file located)?

internal

Also, when my phone is lagging because of that SystemUI RAM eater bug, back, menu and volume buttons don't work (I can press them, I get haptic feedback but they do notging), it happens in almost all apps (i.e. Facebook, Tapatalk, Google Play, Phone app, Gmail and many others), sometimes they don't work in home app either.
[Galaxy S I9000 Android Development] fmc000:
Thanks. Installed and possibly confirmed the bug, about 60megs of RAM in use by SystemUI after 9 hour of uptime. I just rebooted the phone so we'll see if there's a trend of some kind..
[Galaxy S I9000 Android Development] tsatomas:
It seems logical to me the usage of systemui according to this app but I wonder about this log ''choreographer may be doing much work'' which I don't understand.
[Galaxy S I9000 Android Development] warhead1978:
The app doesn't support logs very well since android 4.+ ... here is CatLog better.

But it shows more processes in RAM as the normal view..

For me I can see which App/process eat RAM or CPU in background...

My services are always the same but the free RAM is always different ... up to 35MB free RAM without using something special it is ok, but then I gets laaaagy ...

MfG
[Galaxy S I9000 Android Development] matcho13579:
[MENTION=3033992]kasper_h[/MENTION] Could you try to remove Active Notification feature to test if it's not causing the SystemUI bug? I was using C-ROM before and I had no such problems until dev of the ROM didn't add the feature into it
[Galaxy S I9000 Android Development] Hampy:
Going back to 4.2.2 "cm-Mackay_ROM_2.99_Final", i think 4.3 versions is the end of the line for a smartphone with so low ram and generally old hardware.
[Galaxy S I9000 Android Development] kasper_h:
Yes, I will do that, as I was thinking the same thing. And active display seems to be not the best programmed patch anyway, if I e.g. see all the switching between active display-app-lockscreen-app...

Edit: I just browsed through the code. If Active Display is disabled it should not be active at all. So has someone tried to disable Active Display to see whether that solved the SystemUI growing large in RAM problem?
[Galaxy S I9000 Android Development] hollandais:
I dont know if it's important, maybe not.

This screenshot was taken after 9 hours sleeping of m'y sgs.

Envoyé depuis mon GT-I9000 avec Tapatalk 4
[Galaxy S I9000 Android Development] matcho13579:
I don't have active display enabled but the problem is still happening.

I did a soft restart 10 minutes ago, SystemUI was consuming about 95 MB of RAM, pretty unusable..

But still try to remove Active Display, because as far as I know, that bug is not present on CM10.2 builds

So if I got it right, you didn't use your phone at all? Maybe if you're not using the phone, SystemUI cannot grow up, but I really don't know why
[Galaxy S I9000 Android Development] hollandais:
That's right, I didn't use my phone at all. I was also sleeping. Wifi was disconected, so there where no updates.
[Galaxy S I9000 Android Development] matcho13579:
And how is it now after you started to use your phone?