yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] loSconosciuto:
:silly:, I don't know what I did.

Happy birthday by the way.

Maybe if I'll find something not relying on Xposed, I don't want to include it by default, that's something the user should add. But since there's a simple module for Xposed, just use that.

I've already thought about giving to a such big /cache partition a reason to exist. The thing is that I really don't need more space, so I really didn't care much about it.

I don't want to do a repartition and I'm not sure it's big enough for the dalvik-cache. I could use it for the temp downloads instead of /data, but I always forgot to do it. Also, I don't want to use it for a swap partition, this is another thing you can do on your own.

Same here, Airplane mode all night long. I tried the app once and it worked as expected. I will try again when I have some spare time.

You have to add it. Do what rovo98 wrote. Create a copy of 50-cm.sh (name the file as you want, just keep ".sh" as file extension, otherwise it won't work), change the file list after "list_files() {" as in rovo98's post and you are done. I did the same thing for "keep_me_awake", you'll see there's a script for it, along with one for gapps.

Most likely not kernel issues, mostly because the kernel is the same.

I suspect the SOD wasn't a real SOD, but the usual semi-SOD. It happened to me a few times, unfortunately it had always happened in the wrong moments and I've never been able to debug it. It looks like the device is awake, but the devices suspended with the early suspend api are not resumed for some reason.

Anyway, I couldn't have made taking logs more simple (vol up + vol down + power, see the first post). Please post them when reporting issues.

So changing the UART owner can have this effect? Weird.
[Samsung Galaxy SL i9003] cukierkas:
one more easy way to gain some more free MB and freshness of the rom.

xposed + greenify. donate version of greenify allows to freeze and system apps, but that can be easily made with same android settings.

xposed framework allows greenify to cut relations between apps (like swipe + gplay, xda premium + gplay, rom toolbox + gplay etc). that reduces wakelocks of gaps heavily. before that I used to have more than hour of gapps alive, now its reduced to 20 mins. that leads to more ram to other apps and better battery backup..

one short ot, with this happy trio (magic losco knowledge, xposed and greenify) cm10 nearly equals with battery backup to GB :good:

now i'm getting 4hrs of screen time, more than hour of talk time (with BT headset) and lots of exchange mails with lullaby time for a kid during one session ;):good:

regards.
[Samsung Galaxy SL i9003] catarifrangente:
[MENTION=4349695]loSconosciuto[/MENTION]

Had a SOD while phone charging.

I'm posting the log, hoping it'll be useful.
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

with the latest kernel i face many signal drops

and i faced the previous bug (cpu stuck at 1000MHz) again but this time it happened when listening to music with power amp.

Thanks for your quick updates.
[Samsung Galaxy SL i9003] loSconosciuto:
Did you try to take logs when the device wasn't responding? If that's the case, did the LEDs blink?

I think the log you posted was taken after a restart that you forced by removing the battery. Doing that is almost never necessary, keeping the power button pressed forces a reboot almost always, it always worked for me. When the battery is removed, /proc/last_kmsg is not created.

If you didn't remove the battery, then it wasn't a SOD, but your device was simply off.

Signal drops are not a kernel issue, at least not a

new

kernel issue, I didn't touch anything related to radio in the last kernels I posted.

Regarding the other issue, I'm not sure it happened while listening to music, I can see you played videos too and probably it took you some time to realize there was something wrong.

The problem is that there's a DSP bridge handle left open and hence omap-dsp can't be suspended. I don't know why this happens, maybe there's a problem in the OMX. I couldn't see any error in your logs, but there's a lot of stuff in there so I maybe missed something.

[MENTION=2606021]cukierkas[/MENTION]

I tried again the app, but I couldn't replicate your issues with BT. I tried many combinations: BT on, Airplane off, BT off... etc, but BT always turned on. I also tried to do some things manually, nothing caused issues.

With "hangs" you mean that you can't turn it off or on because the toggle is gray and can't be pressed or do you mean that it turns on, but you can't use it? Because I simply tried to turn it on.
[Samsung Galaxy SL i9003] cukierkas:
Hello, thanks for answer. Yes, toggle becomes gray and no chance to switch off or on. Restart helps only. At my case bluetooth doesn't turn on properly after flight mode in long period (long deep sleep). If the phone was touched, for example to see the time in the morning, then bt will turn on, maybe because phone was waken. If the phone won't be touched, bt wouldn't turn on properly. Bt time to ON for me is 0750, flight mode switches off at 0710.

Regards, I guess the best thing to catch that ghost is to get that time proper logcat. Isn't it? Thanks.
[Samsung Galaxy SL i9003] catarifrangente:
@ loSconosciuto

I pull uot battery, I didn't know that I can take logs even when in SoD...:o
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131129-galaxysl-signed.zip

This is experimental. I raised the SGX functional clock from 200MHz to 266MHz. This should improve 2D and 3D graphics performance.

I'll think of a way to make it optional, but for now, test it and see if battery life is affected in a noticeable way.

Patches on GDrive.

Try to get some logs. I will try again anyway.

It depends, technically nothing should work, but what if it's not a real SOD, but it looks like such? In that case logs are maybe taken and if LEDs blink, then it's not a SOD.

In any case, logs taken after the device was powered off are of no help since the interesting part is lost. That's why you should force a reboot keeping the power button pressed.
[Samsung Galaxy SL i9003] cukierkas:
To say the truth I can't find the way to try and see the difference in performance. But my kid says that temple run 1st runs smoother. Battery backup will be later.

Regards.
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Not a sod, just couldn't turn on screen with home button, nor with ON button.

http://www.speedyshare.com/ZK2Ec/log-131201-005917.txt
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131201-galaxysl-signed

I really didn't like the hard-coded GPU overclock, so I made it optional. You can do that from DeviceParts (included in the zip) or from terminal emulator. For example, for 200MHz:

su
echo 200000000 > /sys/devices/platform/omap/pvrsrvkm.0/sgx_fck_rate

Not all the frequencies are allowed and there's no way for you to set anything above 266MHz or below 66MHz.

I've also made the Active Power Management timeout configurable. The default value is 100ms (TI suggests values between 50ms and 100ms. Stock kernels use 2ms.). This will determine how frequently the SGX clocks are disabled to save power. For example, for 50ms, do the following:

su
echo 50 > /sys/module/pvrsrvkm/parameters/sgx_apm_latency

You can try to change values and see if you can get better battery life.

I also ported the SIO switch driver from the 2.6.35 kernel.

It allows to change the owner of the UART, which is MODEM in this release, to see if the network issues you had were due to it.

I'll soon upload the patches on GDrive or Github.

Usual fake-SOD. I don't know why it happens. It's interesting that it mostly happen while the device is left alone charging.

@ everyone

Could you please flash debug_script.zip? All it does is to create an init script which will enable some debug messages that I hope will be useful to debug the problem.

All I see from the logs you posted is that the device is awake, but something is not right. Unfortunately there are no error messages and I'm not able to replicate the problem, it's pretty random and happens rarely.

If I can't find anything, I'll try to see what happens forcing the device to stay awake a bit more while the battery is charging increasing the duration of "max17040-battery".
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Thanks for updating. I've left gpu clock at 200, to say the truth haven't seen any difference comparing with 266.

Settled apm latency to 50. Will see in a run the difference. TI says there is difference, so let's try it. Installed debug script as well, hope it will help to to catch the black cat in a dark room :)

Regards, happy user.

Ps, status clock hanged twice in previous kernel version. Hope that was only a small thing.
[Samsung Galaxy SL i9003] loSconosciuto:
I uploaded an updated version of kernel-cm-10-20131201-galaxysl-signed.zip (the old version is still available, but I renamed it).

I made an error in the overclocking code and did some other unimportant changes here and there.

All the patches are on GDrive.

The difference should be mostly noticeable with complex graphics.

The clock in the statusbar shouldn't have anything to do with the kernel, it's a bug somewhere in the framework.
[Samsung Galaxy SL i9003] mehran 92:
After overclocking the gpu now it can run asphalt 8 with some lags but without overclock i cant even play it!! It almost freezes!

thanks for this update
[Samsung Galaxy SL i9003] cukierkas:
Morning. Second fake sod per 2 days. That never happened before, especially when charging. http://www.speedyshare.com/pKp8X/log-131202-053550.txt

Updating to newest version. Regards.
[Samsung Galaxy SL i9003] cukierkas:
Hello. One more fast reboot

http://www.speedyshare.com/smeaS/log-131202-185815.txt

Edit. Sorry, I've forgotten one more log, I have made it during fake sod period. After some ON button presses device rebooted. So afterwards I made log, posted above. Hope, you'll find something useful.

http://www.speedyshare.com/DRkCQ/log-131202-185743.txt

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
Still nothing useful. I guess you can delete the init script (90pm_debug), nothing happens if you keep it.

Let's go with plan B:

kernel-cm-10-20131201-galaxysl-signed.zip

The check of the temperature of the battery is now delayed of 100ms (I added "msleep(100)" right after this line to be exact). This should result in a slightly longer awake time (the battery is checked once every 10 minutes when the device is asleep, so not much).

Till know I've always had the impression that the fake SODs happen only when the device is awakened to check the status of the battery, which takes a really small amount of time. Let's see what happens slowing things down. I don't have a reasonable explanation of why I'm doing this, I just wanna try it.

If you often have this kind of SODs, please report your impressions.

Also, did you notice any improvement regarding the phone signal starting from yesterday's builds?

log-131202-185815.txt and log-131202-185743.txt are basically the same log, only few lines change. Not surprising considering that they were taken a minute apart from each other.

Anyway, a SIGSEGV involving system_server caused a restart of the framework. At least this wasn't a kernel crash.
[Samsung Galaxy SL i9003] cukierkas:
Morning. Thanks for update. About 3g, don't know really, didn't bothered to keep eye on it, but it seems stronger, no signal drops discovered. One thing works for sure, bt turns on automatically second morning in a row. That's glad, good job :) And one more thanks for TI driver, 50ms latency seems to conserve battery better and better ram management with cpu observed.

Second thing. Rilj seems to have awake time more than hour per session. That is your magic or my mistake locking com.android.contacts into memory?

Merci, regards.
[Samsung Galaxy SL i9003] catarifrangente:
I'm getting back to your rom, I was taking a look to kitkat.

How can I be useful?

Do I have to flash your debug script or is it already included in yhe kernel? sry for the question but I'm quite noob.
[Samsung Galaxy SL i9003] cukierkas:
Losco, does qwerty kernel possible to adopt to dhiru's kitkat release? Have a wish to try it, but phone is needed as a daily driver. Thanks for the answer.

---------- Post added at 09:44 PM ---------- Previous post was at 09:43 PM ----------

No, debug script is not needed. Install latest kernel version instead. Please read the last page carefully.
[Samsung Galaxy SL i9003] cukierkas:
Short brainstorming about rilj. Bigger rilj activity observed when stock dialer is used. With third app, like exdialer, witch does the same, finds the person and calls, rilj awake time is max 2mins per session.

Another thing, about fake sods, as you named it. None appeared, that new wakelock max or something like that, awake maybe for 20 seconds per session. That's nothing.

Third thing, about gapps awake time. I managed to reduce it to 5 mins max per session with help of xposed + per app hacking module. Android.gsf service wakelock is now not active at all. The only thing is needed to keep that service running and prevent wake locks.
[Samsung Galaxy SL i9003] cukierkas:
Edit, attaching another screen.
[Samsung Galaxy SL i9003] loSconosciuto:
I got a fakeSOD, the device wasn't charging and couldn't see why it happened. I just could grab the logs.

I really don't know where's the problem and the fact that it happens so rarely makes it hard to debug. It's like as if the device hangs while trying to entering mem state (deep sleep), waiting for something to happen without finishing.

Anyway, yesterday I uploaded a build in which I've lowered the Active Power Management timeout from 100ms to 50ms. No other changes, I just wanted to replace the earlier build with this to get rid of the useless delay.

[MENTION=2606021]cukierkas[/MENTION]

Thanks for the feedback, really appreciated.

If RILJ time is equal to the "In call" time, it's probably nothing to be worried about, but I'm not sure. I honestly don't know why you observed a difference using third party apps. In any case, locking the contacts app shouldn't be a problem.

Regarding KitKat, Dhiru is merging my changes, so in terms of stability it shouldn't be that different.

Maybe the last two builds include a kernel less stable than others, but I didn't try any of them so I'm not sure.
[Samsung Galaxy SL i9003] cukierkas:
no, sadly rilj awake time isn't equal to talk time.

about kitkat, waiting for bt to be fixed. as I understood right, thats upstream bug, not omaps?

noise recognition will be implement as well?
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Some logs for today.

First is about bluetooth crash in the middle of voice call. Of course, it was unusable afterwards.

http://www.speedyshare.com/844MJ/log-131206-145321.txt

Secondary one is about reboot, which appeared while trying to add new event into calendar.

http://www.speedyshare.com/smmVS/log-131206-163335.txt

Hope you'll find something.

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131206-galaxysl-signed.zip

This kernel includes a fix for a security bug. Big thanks to Steven676 for pointing me the bug.

Other than that, I included a couple of changes I was testing: http://sprunge.us/YAbY, http://sprunge.us/TJbc

The first one revert some changes I included long ago in the mmc driver. Now that the kernel is quite stable, I reverted part of them to see how things work. Report any kind of issue.

I wouldn't say it was a bug. The flag controlling whether BT stuff needed to be built or not was changed and this broke BT. Dhiru already took care of it.

Noise recognition is already implemented.

Bluetooth: hci0 link tx timeout
Bluetooth: hci0 killing stalled connection *
Bluetooth: hci0 command tx timeout

There was an issue with the connection and probably this is something not expected.

The next time it happens, see if a simple framework restart fixes the problem:

su
restart

If it does, it shouldn't be a kernel problem, at least not entirely.
[Samsung Galaxy SL i9003] catarifrangente:
Sod, or fake sod, in the morning.

Phose was in charge.

I'm uploading log on gdrive because is too large.

I think sod was happened in the very last part of the log though.

Hope to be of help.

Cheers

https://drive.google.com/file/d/0B3Wd70NYT_m-c3Frc05uRW42ZWc/edit?usp=sharing
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131207-galaxysl-signed.zip

There is an issue with the security bug fix which leads to memory leaks, here the additional new fix.

Please update the kernel.

I can see it, it happened an hour before you tried to turn the screen on.

The good thing about fake SODs when compared to actual SODs is that alarms work as for all the other apps...

Please try the last build I posted, I'd like to know if anything changes with the changes to the mmc driver.
[Samsung Galaxy SL i9003] The_GMAN:
Why has the max overclock been reduced from 1200mhz to 1100mhz? Am really disappointed :(

And I am experiencing phone freezes, only solution is to force reboot. its really annoying.

**************************************************************************************************

Edit: Let me include more details:

The phone freezes when I am using mobile data. I am using your latest builds:-

- kernel-cm-10-20131207

- Rom cm-10-20131106

Should I attach anything to help you get to the problem?

And please increase the max frequency back to 1200mhz as I can run games better with that frequency. It will be much appreciated. Those who don't want to run that frequency can simply not use it.

Thanks for your hard work man.
[Samsung Galaxy SL i9003] cukierkas:
You always have an opportunity to try other, not so smooth and polished rom. It's your call. So say thank you or go away :)

Losco, one small discovery. Turned off the permission to com.android.phone to look up for location. And suddenly all rilj awakes just gone :)

I guess, that's the answer.

One more thing. Reduced hidden apps to 5, as [MENTION=4473033]LoLaTiOn[/MENTION] did at xgamers rom. And yes, everything is way way way smother now.

Merci for update, regards.
[Samsung Galaxy SL i9003] The_GMAN:
If that was directed to me, I was just tryin to help by reporting a few things here and there. I am not leaving Qwerty Rom ever, its the best rom there is for i9003! :mad:

How exactly did you turn off the permissions to com.android.phone? could you please tell me? I hate those partial wake-locks...
[Samsung Galaxy SL i9003] cukierkas:
http://xdaforums.com/showthread.php?t=2437377
[Samsung Galaxy SL i9003] catarifrangente:
Another sod with latest kernel. I could not take log but it happened same of yesterday. It seems that it happens while phone is fully charged, and I keep it connected to the charger. Weird.
[Samsung Galaxy SL i9003] loSconosciuto:
1200MHz is unstable, so no, I won't include it until I figure out what's wrong. It had always been unstable, almost stable I'd say, until some recent changes.

You can now increase the SGX clock now. I don't play games, but that should help.

I've no idea what you mean with "freezes". Posting logs would indeed be more helpful. The next time one of these freezes happen, press "vol down + vol up + power" and give me the file you'll find in /sdcard/logs_qwerty/log-DATE.txt

It doesn't happen when the phone is fully charged. It's a coincidence that you notice it when it's fully charged.

I'd always suspected it has to do with the "battery driver" because these fakes SODs usually happen when the battery is checked, or very close to a battery check. There's also to consider that while charging the battery is checked every minute instead of the usual 10 minutes, so if there's a bug hidden somewhere, it makes sense that it mostly happens while charging. However we have also to consider that we are using the same driver of the Galaxy Nexus, so maybe the problem is not stritckly in the driver.

Anyway, I stumbled upon this patch and decided to try it. Here what I did.

I've also noticed that one of the experimental patches I used in my previous build was causing issues. (Powerdomain (core_pwrdm) didn't enter target state 0)

kernel-cm-10-20131208-galaxysl-signed.zip
[Samsung Galaxy SL i9003] The_GMAN:
By freezes I mean the phone gets stuck suddenly especially when I am browsing. The phone just stops responding and remains stuck no matter what I do, what I press or how long I wait. The only option is to force reboot by holding the power button or pulling the battery.

However, I think I found the problem...it was a netspeed script I was using that might be causing it. I deleted the script and that seems to have fixed the problem. I haven't experienced "The Freeze" again for two days now. If it happens again I'll let ya know.
[Samsung Galaxy SL i9003] mehran 92:
I have freeze problem too

it happens randomly but almost every time it happens when im connected to internet
[Samsung Galaxy SL i9003] cukierkas:
Hello. Bt hangs again while unpairing. Log attached.

http://www.speedyshare.com/W8kT6/log-131209-115944.txt

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
Try kernel-cm-10-20131209-galaxysl-signed.zip, I increased the HCI command timeout from 1 second to 2 seconds. I suspect this is the problem, but I'm not sure. I could increase it even more, but 1 second was enough most of the times for you, so I preferred to stay close to the original value. If you still have issues, post some logs.

EDIT: mainline kernel: Bluetooth: Increase HCI command tx timeout ;)

I've also increased the overclock from 1.1GHz to 1.15GHz, which seems to be perfectly stable on my device. Try it and tell me if it's stable, SmartReflex is enabled, so don't assume it's stable if 1.2GHz was (apparently) stable.

Regarding the random freezes, post some logs. I too have freezes, but it happens when I try to do too heavy stuff and the device takes some time to becomes usable again. Try to post some logs so that I could see what's happening on your devices.
[Samsung Galaxy SL i9003] cukierkas:
Hello, thanks for trying to help. As I see, I'm the only one who uses BT. Thanks for the things you doing for me :)

For those, who suffer with freezing while browsing.

Try to increase zram to max, reduce along and hidden apps to 5 or 6. As far I've noticed, browser uses huge amount of data, so ram is needed. Why not giving it. See if that helps.

Short of topic. Very nice miui theme. https://play.google.com/store/apps/details?id=com.jasonevil.theme.miuiv5dark
[Samsung Galaxy SL i9003] catarifrangente:
What do you mean for hidden apps? Background apps limit?
[Samsung Galaxy SL i9003] cukierkas:
I

Settings, performance, memory management.

Edit. Still having problems with Bt automatic turn on. With last two versions it's not working as it worked on 1202 version. Thanks in advance.

Regards.

Edit 2. Quick restart while trying to load browser. CPU was at 1150, not sure if it is oc fault, but back of the phone was quite hot. Log attached.

http://www.speedyshare.com/YPT2b/log-131210-191801.txt

Some hours ago got problems with Bt pairing. Toggle bt off and on helped. Was driving, so no logs :)

Short question. What time period does your logging script covers?