yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] Drizzt_Kueh:
I could catch this SOD again, but in the latest release, the today release.

I'm attaching the last_kmsg log.

Kernel Version: 3.0.101-04347-g1997abf

Cyanogenmod version: 10-20131104-UNOFFICIAL-galaxysl

Thank you!

PD: Also tried adb to get the logs without rebooting, the device didn't response.
[Samsung Galaxy SL i9003] cukierkas:
Hello. Sad story at my side. Lost my imei. Updated yesterday to newest version, everything was grant until fly mode. After it couldn't start rilj fully, have no signal, can't ring or send SMS. Mobile data at my wonder works, but no possibility to use it as a phone :(

Imei showed wrong, maybe that is the reason?

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
One more thing. Network search works, but can't log in to my provider. :(

Sent from my GT-I9003
[Samsung Galaxy SL i9003] acuicultor:
Do you tried to roll back to stock maybe it helps you, hope you can fix it.
[Samsung Galaxy SL i9003] cukierkas:
Wow, miracle happened :)

Even thought of searching for a new phone :)

Recopied efs folder from backup to /system and rebooted. Everything works fine for now. Scared now to use flight mode at last two versions of kernel.

By the way, returned to 1028 kernel back, tried a flight mode again, everything works fine for now. Wow, that was a long hour for me :)

to return to bluetooth after flight mode. it cannot pair automatically. still needed to turn off bluetooth and turn it on again. afterwards everything works fine.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
Short off topic. Lately xda application behaves very strange, can't press thanks button, if I press it, thanks goes to another post as I think another post is marked, nor I'm marking the post I want.

As you see on screenshot, strange gaps appears at top of the page and some post are lost, simply I can't read them. If I tap that gap, xda application force closes. And if I want to edit my own post, I mark it, pressing edit, modify, another my post is exposed. So the only way to edit is to load webview, login and modify that post.

I did reinstalled it, cleared apps cache, wiped cache and dalvic from cwm :) Nothing helped. Is it me or someone has this issue as well?

Sorry for offtopic, but hope you guys will suggest something:)

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] maksimus0021:
Hi. @cukierkas :) I also had (XDA Premium v2.2.1). I installed the XDA Premium v4_4.0.5, now everything is fine. True, this version is slightly slower. :)
[Samsung Galaxy SL i9003] acuicultor:
The same happens to me sometimes on different roms. I think is xda app problem related.
[Samsung Galaxy SL i9003] cukierkas:
Thanks. Installed xda premium 4, everything is fine and way nicer :)
[Samsung Galaxy SL i9003] klau7:
Maybe it is because xda app isn't updated since 2012. I have the same issue on my tablet running android 4.3.
[Samsung Galaxy SL i9003] eduCoder:
Classic tapatalk 2 (originally premium) is free now and is working well. You can get it here:

https://support.tapatalk.com/threads/not-ready-to-upgrade-try-this.20754/
[Samsung Galaxy SL i9003] marras:
Before the latest version, i had 1/2 sods each day...with the latest, flashed a day ago, seems that sods disappear. I had only a reboot during listening music. But not a sod for now. All seems to work fine, with zram to 26% also the ram management it's good
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131106-galaxysl-signed.zip

Possibility to fully charge the battery, don't do it to prolongue the life of your battery (my battery is already almost dead, so...) (DeviceParts)

Possibility to disable the USB functions. I currently need this because the cable of my wall charger is giving me some issues and I have other USB chargers which are improperly detected, causing "latona_usb_wakelock" to be held all the time. (DeviceParts)

Other minor changes

I'm not sure if I'll keep using those changes and I didn't test them properly.

Kernel patches on GDrive.

There are some weird messages related to WiFi which are spamming the dmesg. There something wrong with your WiFi network, a lot of packages are discarded:

wl12xx: WARNING corrupted packet in RX with status: 0x1

Anyway, apart from that, I couldn't find anything interesting. I will take a better look when I have some more time, maybe I missed something.

Current setting:

kmsg: 256K

logcat: 128K * 3 (main, radio, events)

Our CyanogenMod builds do not use the real /efs partition, but a copy created while flashing CM over a stock ROM. If you lose your /efs content while using CyanogenMod, restoring a stock ROM

could

bring it back. In any case, as long as you have a

working

backup, there's nothing to be worried about.

Good to know.
[Samsung Galaxy SL i9003] cukierkas:
In that case you should replace the battery. I'm using this, http://dx.com/p/replacement-3-7v-17...msung-i897-i9000-i9003-i9010-i9088-more-93330

but as I see, its sold out. Really good battery, holds better than original :)
[Samsung Galaxy SL i9003] cukierkas:
What does st_wake_lock stands for? And why it keeps phone awake for 4 hours? Screenshots attached.

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
Is its time comparable to the time you spent using your BT headset? I mean using, not simply paired.

I could revert this if there are no issues with BT headsets without it (read the commit message) and if it impacts battery life too much (this has to be verified). I could also decrease the timeout of omap-serial (also this one is due to BT).

I think I'll post some kernels to test.

On an unrelated note, yesterday I uploaded a new CM10 build (cm-10-20131106-UNOFFICIAL-galaxysl.zip). I did some little changes here and there, nothing big:

I updated the kernel with some little changes, most of which were included in my standalone kernel releases.

The battery capacity is always visible while charging when the device is off (the capacity changes color according to the background now)

Minor changes here and there
[Samsung Galaxy SL i9003] cukierkas:
Yes, I think it was Bluetooth headsets fault, it doesn't unpaired properly, because Bluetooth icon on status bar was blue, nor I wasn't using it and was aware from it. Will try last build during the day.

Regards.
[Samsung Galaxy SL i9003] cukierkas:
Edit : updated, working fine. In my personal opinion zram 10% is better:)

Airplane mode doesn't lost imei :)
[Samsung Galaxy SL i9003] cukierkas:
Hm, st wakelock still can't be slerpy, even when Bluetooth is not used, just turned on :(
[Samsung Galaxy SL i9003] loSconosciuto:
Try kernel-cm-10-20131109-galaxysl-signed.zip, I got rid of st_wake_lock and decreased the timeout of omap-serial. I'll see if I can further optimize its use, but things should be better now.
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Well, I'm impressed, with last kernel situation is way better :)

Android seems to sleep better, bt headset works as it should, charge holds better :)

By the way, what st wakelock was entitled to do? Why it was so unsleepy?

Regards.
[Samsung Galaxy SL i9003] cukierkas:
View attachment 2381535View attachment 2381534

Sorry for second post, this app don't let me to attach files while editing the post.

Regards.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Using last CM release for the last 5 days. No SOD's, no reboots, no "forever" signal lost suffered until now.

Using the last kernel the last 5 hours. Same as above.

Fantastic work! Excellent!
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131111-galaxysl-signed.zip

I brought back st_wakelock, which should be now used when data is sent to the device, and got rid of omap-serial.

As always, the changes were not tested in a comprehensive way, I never use BT. I tried to send some files with the device in deep sleep to see if it could receive them.

If the device is in deep sleep with BT on and nothing paired and nothing sending data to it through BT, st_wakelock shouldn't be used.

Fix some BT issues, but it wasn't correctly implemented causing an abnormal awake time. Now it should work properly.

Yeah, it took me a while to find that this was the reason of the reboots, mostly because all the crashes were random with no specific informations in the logs. It was my fault, because that OPP was already disabled, but I didn't know why and when I enabled it there were no apparent issues.

I then came across this and this which made me re-revert that change.

EDIT:

Regarding the signal loss. That week (I don't know if you read all my posts) I issues with my mobile operator, I frequently had this in my dmesg:

SRDY TimeOUT!!! MRDY : [I]*[/I], SRDY : [I]*[/I]

and sometimes, after those

SRDY TimeOut Count Over.

In my old kernel releases, when this message appeared, I had no way to recover the signal if not rebooting and couldn't switch to airplane mode.

Check if you have those messages in your dmesg:

su
dmesg | grep ipc

I no longer have those messages, I had them only that specific week, but I'd like to know if those of you with continuous signal loss can see them or not.
[Samsung Galaxy SL i9003] cukierkas:
Will try during the day. At mean time, very nice kitkat theme

https://play.google.com/store/apps/details?id=com.steel89ita.android44
[Samsung Galaxy SL i9003] Drizzt_Kueh:
I have a lot of lines (actually 209) like this in my dmesg:

<4>[72795.548828] [ipc_spi] Got ONEDRAM_CMD_SUSPEND_REQ
<4>[72797.132843] [ipc_spi] Got ONEDRAM_CMD_RESUME_REQ

CM Version: 10-20131106

Kernel version 3.0.101-04351-gcc3c146

Edit:

I forgot this. I'm attaching a video where the impossibility to change to another mode can be seen:

https://www.youtube.com/watch?v=Cpir0ralbWk

This video is too short, because video restrictions, but I could try all day with the same result...
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

hi ! if you remember,about a month ago i faced a bug that phone stuck at 1000 MHs even when i set the cpu clock to lower values like 600 or 800MHs,now it happened again and i see that after almost one and a half of hour,phone didn't go to deep sleep (sleep time reported from an app (system tuner pro) is 0.0 seconds)

Im attaching the logcat and hope to help you.

im sorry because i couldnt get d_mesg.

And there is a small bug that i cant set the vibrator intensity, after touching it galaxy sl settings crashes.

CM version:20131106

kernel: 3.0.101-04350-gff548b3 20131111

Sorry for my bad english!
[Samsung Galaxy SL i9003] cukierkas:
Hello again. Glad yo use the latest version, st_wakelock seems to sleep properly. Thank you. Now trying phone with zram 28% and oc to 1200. It fast, fluid, but mp3 glitches again via browsing or in other app. As I'm heavy multitasker, I had increased hidden apps to 15. That works either, zram seems to fill much faster. But I understand one thing. When CPU is used more? When zram drive is smaller or bigger? In opinion, when drive is smaller, more compression is used. In that case,more CPU. Am I right?

edit. the world is not so good as i expected.

we are having same st_wakelock unhappy :)

logs and screenshot attached.

Regards.

Edit 2

Is there a chance to backport to cm10 kitkats deskclock?

http://xdaforums.com/showthread.php?t=2507136
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131112-galaxysl-signed.zip

I'm sorry, but st_wakelock was acquired even when BT was off and not always released. This caused a very high awake time when BT was off. I switched to a more secure timed out wakelock.
[MENTION=4915822]mehran 92[/MENTION] That's most likely the reason why your device didn't sleep.

These messages are normal. Their number decreased on my device since I changed mobile operator, but they have to do with the processing of the received data, don't know exactly what.

You should let the device change mode before attempting to change it again. I don't know if it can be "fixed", but that's how it had always been.

If you press "vol up + vol down + power" dmesg and logcat will be automatically taken and saved in /sdcard/logs_qwerty/**. The file will also includes build date, number etc... so you just need to post the file.

Working fine here. Try to replicate the issue, grab the logcat and post it here. Then, try to clear the data of the app from the settings.

I never tried to use 15 background apps with this kernel which has a better memory management. 10 was fine for me and kept using it. I actually don't know the exact impact of that setting, I didn't play with it that much.

Anyway, the compression should be independent from the size of the partition. So, the bigger the partition, the more data can be stored and since everything inside the partition is compressed, the more data the CPU has to compress and decompress. I don't know if the zRam has a noticeable impact on battery life and I can't say how battery life differ if the partition is XMB big instead of YMB.

I will have a look at it, the new alarm picker seems even easier to use than the current one, which I love by the way.
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

as you said I tried to replicate the vibrator issue and here is the log

by the way after clearing its data it fixed

Thanks for your tips.
[Samsung Galaxy SL i9003] catarifrangente:
[MENTION=4349695]loSconosciuto[/MENTION]

Is there any chance to have a fix in gyroscope?

Apps like sky map are working in vertical rotation but not in horizontal.
[Samsung Galaxy SL i9003] loSconosciuto:
[MENTION=4915822]mehran 92[/MENTION]

Thanks for the log. It's what I expected, an incompatibility of the app with the saved setting.

When I implemented the slider for the vibration intensity I didn't bother to avoid conflicts.

[MENTION=2606021]cukierkas[/MENTION]

I almost forgot. Could you please set keep_me_awake to zero when testing BT pairing (I saw from your logs that you are using it)?

The few milliseconds spent awake because of it, fixes BT pairing when the device is in deep sleep, even without st_wakelock and omap-serial.

Regarding DeskClock, backporting requires too much work. The prebuilt apk should work on Android 4.2+, maybe with some little bugs. Use third party apps if you want the new look.

Sky Map is working fine on my device, so I don't know what you mean. All the sensors are working fine, there are no known issues.

The orientation sensor is sometimes not perfect, but that's because we don't have a gyroscope. It's a virtual sensor which combines the data of the magnetic sensor (which sometimes report completely wrong values) and the accelerometer to determine the orientation of the device.

Make sure nothing is interfering with the magnetic sensor, that could easily happen.

Make also sure that both the sensor are working properly with apps like "Android Sensor Box".
[Samsung Galaxy SL i9003] shaktishekhar:
DEL
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

the problem that phone stucks at 1000 MHz, happened again

i set cpu to 600 MHz but phone still stuck at 1000 MHz and drained much battery and didnt go to sleep

here is the log, hope that can help

sorry for my bad english !
[Samsung Galaxy SL i9003] loSconosciuto:
The deep sleep issue is due to a crash. I can't say what happened because the crash happened before you realized there was something wrong, at least 4 hours before. All I know is that the problem has to due with the DSP. Your dmesg is full of:

pm_op(): platform_pm_suspend+0x0/0x5c returns -1
PM: Device omap-dsp failed to suspend: error -1

which was what prevented the device from entering deep sleep.

I also found in your logcats (including the one you posted the other day) this:

D/TIOMX_CORE(1453): Found component OMX.TI.MP3.decode with refCount 0 pHandle (0x40bd5908)
D/OMX_MP3 (1453): OMX_ComponentInit():206 Entering OMX_ComponentInit
D/TI_LCML (1453): LCML PATCH init
D/TI_LCML (1453): InitMMCodecEx():312
D/TI_LCML (1453): ****************LCML ERROR : DSP ************************
D/TI_LCML (1453): InitMMCodecEx():312 Error: Attach processor : Err Num = -5
D/TI_LCML (1453): InitMMCodecEx():312
D/TI_LCML (1453): ****************LCML ERROR : DSP ************************
D/OMX_MP3 (1453): MP3DEC_HandleCommand():721 721 :: Error : InitMMCodec failed...>>>>>>
E/OMXCodec(1453): [OMX.TI.MP3.decode] ERROR(0x8000100a, 2)
W/OMXCodec(1453): Dropping OMX EVENT message - we're in ERROR state.

The DSP Bridge driver can set the CPU at 1GHz even if you limited it to something lower, so I'd say that the driver set the CPU to 1GHz, something crashed and the original constraint wasn't restored.

You were probably watching a video or listening to music when the crash happened.

I will see if I can find a way to replicate the problem, but I don't use my phone as multimedia device, so it could take a while. If it happens again, grab the logs and post.
[Samsung Galaxy SL i9003] mehran 92:
Yes it happened after watching video

and sure i will post more logs when it happen again

there is something that i should tell, i have disabled the DSP manager,can it be the problem?
[Samsung Galaxy SL i9003] vishal24387:
[MENTION=4349695]loSconosciuto[/MENTION]

Hi, I can see that you are really very much interested in cm10 rom development :) I am using dhiru's cm10.1 alpha 9 rom. I think its very stable rom. I am experiencing a little bit higher battery drain when we use 2g net. It need a little bit modification at kernel lavel to make it even more stable and more battery friendly. If possible can u work on cm10.1 kernel to have better cm10.1 kernel?? :)

Thanks in advance...!!
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Reduced awake time to 0ms, logs attached. Still having high awake time :(

Bt pairing sometimes forgets to unpair.

Rest is fine, glad to use such polished rom with fast and smart support. View attachment 2391952View attachment 2391953

http://www.speedyshare.com/d5An4/sdcard0.zip
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

Hi,that bug happened again twice and here is the logs.

sorry the logs are too big to upload as a text file.
[Samsung Galaxy SL i9003] loSconosciuto:
Nope, DSP manager is not the problem.

I'm not working indipendently, if take a look at Dhiru's repos, you'll see that a lot of stuff is made by me. There are really little differences between my kernel and his, at least for what the device specific code is concerned.

Anyway, my kernel sources can be easily used for CM10.2, I added a kernel defconfig for this (latona_cm10.2_defconfig) and the only change required for CM10.1 would be "CONFIG_LEDS_LATONA_BACKLIGHT_TIMEOUT=y" in order to have functional LEDs backlight on touch.

The problem here is that you are using what seems to be an unmantained ROM. Ask Dhiru to update the kernel or switch to CM10.2 if he no longer supports CM10.1, which is using an old kernel with some known and already fixed problems.

What you mean with "forgets to unpair"?

Anyway, I'm more interested in knowing if there's any difference between the last kernel I posted and older kernel when it comes to BT pairing. Is BT pairing now working as good as before (when there was omap-serial)?

Regarding the awake time, that's not bad at all, at least in my opinion. "Awake" is not that high and the difference between "Awake" and "Screen On" is almost equal to "Phone On". If the screen is off while in call (I don't know how it works with a BT headset), that's good in my opinion.

What do you do exactly? I'd like to replicate this problem, it would make things easier for me.

Can you tell me if you changed the max CPU frequency, what CPU governor you are using and which apps you use to play videos?

Are you using things like the HW+ decoders of MX player?
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

yes im using the HW+ decoders of MX player and here is my settings:

min:300

max:1000

governor:ondemand

most of the time it happens with mp4 videos
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131116-galaxysl-signed.zip

I updated low memory killer, ashmem, binder and interactive (now set as default CPU governor).

I also updated powerHAL, which is included in the zip, to support both ondemand and interactive.

Ondemand is probably more performant than before, I don't know if that impacts battery life that much.

Note: the tuning parameters of ondemand and interactive are set to the ones I defined in powerHAL whenever the governor changes.

Kernel patches available here.

I was also informed that the navbar is not set to the desidered height after a reboot and that it's necessary to toggle its state.

Flash navbar-fixes.zip which should fix this minor problem.

I tried to play some HD videos with MX player and its HW+ decoders. There are definitely issues, but the solution is simple: use the standard HW decoders. They are capable of playing HD videos flawlessly. I didn't have any problem with them in my tests, try to switch back to them and see if it keeps happening.
[Samsung Galaxy SL i9003] catarifrangente:
Google maps' last update fails when installing due to an error. It asks me for a more recent SDK version. I'm on your last build with 20131116 kernel. Is it only a problem of mine? Thanks

EDIT: now all is working fine. I think that there were some issues with Google servers.
[Samsung Galaxy SL i9003] cukierkas:
ROM is fast and fluid, as it should be:)

Happy to use it. Regards.
[Samsung Galaxy SL i9003] mehran 92:
I disabled the HW+ decoder and enabled the DSP manager but it happened again and now im sure that hw+ isn't the problem.

And i noticed one thing that i think that the problem is with SW decoder because after playing some mp4 videos i noticed that they played with sw decoder and after that i tried to play them using HW decoder but it cant play!

i can play .mkv videos with HW decoder but it cant play .mp4 videos with the resolation of 640*352 with HW decoder.

i tested many videos but all of the mp4 videos(640*352) can only be played with SW decoder and after that the same bug happened.

Hope this can help!
[Samsung Galaxy SL i9003] cukierkas:
hello there. Finally founded some time to fill some gaps.

Losco, thanks for the last update, rom is now even smarter and faster. Using it with 10 background apps and zram 26%. Phone doesn't start to lag after couple of days as with 10 or 18% of zram. I gues it depends on partition size. If it's bigger, and has more MB free - the less compresion is used, so in my observation it runs smoother.

About awake time. Still having about 2Hrs awake per session (100%-20, 10% of battery) of android system, but can't find wich wakelock is guilty. At partitial wakeloks AlarmMAnager eats more than 55mins, googleplay more than 30mins.At kernel wakelocks biggest unsleeper svnet (about 20mins) and powermanager (about 15mins). Wakelock duration is set to 0ms, as you have said, and afterwards awake time was a little bit reduced. No impacts to bluetooth, works fine, pairing unpairing with last kernel is perfect, except old bug (bluetooth doesn't turns on by phonescheduler after flight mode. If I switch it manualy by myself - works fine, but I do like when bt is swiched on/off when I needed). Another thing, with same scheduler, it doesnt turn on bluetooth in deep sleep when X minutes is passed (more than 10mins. Guessing some modules are switched off in some period of time, correct me if I'm wrong). Unpairing works fine with last version (you had asked me what I mean about it). That is, when I'm leaving the car with internal headset or moving more than 10 meters from phone with ear piece, ear piece or phone should disconnect devices from each other because of lack of signal strength, but signal is lost and connection is still alive (according to bluetooth blue icon on status bar. At case with previous version st_wakelock was active till I manually rebooted the device, because BT was unusable. When device is disconnected, icon appears grey.)

turbo boost mode. People talk its works even better than zram. Will it work with your kernel? Didn't tried yet, but thinking to. This mode is about to use /cache, which is nearly empty at this kernel with 293 MB partition and only 4MB is used) for swap space.

Regards.