yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] loSconosciuto:
Last kernel build of the year with a not so useful feature.

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

DoubleTap2wake/Knock knock/whatever (Google for more info)

Enable it from DeviceParts.

The home button makes DoubleTap2wake not so useful, but I wanted to see how it works and I must say that it works pretty well. The device can sleep normally when DoubleTap2wake is active with no noticeable power consumption. Touching the screen continuosly however can have an impact on battery life, but I can't be more precise.

The tap must be quite fast and you have to tap with one finger around a rather small area (120x120 pixels). I could probably make it "easier" to use.

Note: you well know how easily the screen stop working randomly and turning on and then off the screen is required. Well, it's the same here, when it happens DoubleTap2wake has no effect and using the power key or home button is required. A calibration is issued as soon as the screen is on though, so the touchscreen should work once the screen is on.

Also, DoubleTap2wake must be enabled when the screen is on (it could happen that DeviceParts restore the saved value while the screen is off...).

Here the patch.

One of the reboot was probably caused by the overclock, but just one of them.

That's a weird log:

...
[130501.892028] twl4030-audio twl4030-audio: Resource has been disabled already (0)
[130502.169097] PM: suspend of devices complete after 281.677 msecs
[130502.169769] PM: late suspend of devices complete after 0.640 msecs
[ 20.748168] Successfully put all powerdomains to target state
[ 20.748474] Suspended for 590.578 seconds
[ 20.748596] wakeup wake lock: alarm
...

It looks like two different logs were appeneded. Anyway there are no errors.

The issue with contant numbers is quite common, it happens also on other (old?) devices.
[Samsung Galaxy SL i9003] cukierkas:
thanks, knocking works perfectly.

you the man :)
[Samsung Galaxy SL i9003] mehran 92:
Thanks for the new feature! :victory:

Happy new year! :laugh:
[Samsung Galaxy SL i9003] eduCoder:
I could not find DeviceParts anywhere. I remember seeing it in early CM roms, but where is it now?!
[Samsung Galaxy SL i9003] cukierkas:
Morning in a 2014th year :)

Settings, advanced, screen. Just tick it.
[Samsung Galaxy SL i9003] eduCoder:
Yeah, found it there, but there is nothing called DeviceParts!
[Samsung Galaxy SL i9003] The_GMAN:
Tried your latest kernel but reboots keep on happening. Will just have to reset it....later...
[Samsung Galaxy SL i9003] loneagl:
Tried the new kernel and the touch to focus is totally awesome. However, sometimes I remove the phone from pocket and the screen is on, dead to touch. When I unlock lots of apps like calendar, calculator, alarm, etc are opened up and the phone is all hot.
[Samsung Galaxy SL i9003] cukierkas:
that never happened to me, strange. The phone is always in my front pocket.

another strange thing happened to me today.

at the end of call, I pressed END CALL buttons and message appeared that com.android.contacts just stopped. afterwards it didn't started. rebooted phone, all phone contacts and logs were empty, just vanished. There is a thought, that gapps crashed, because all calendar entries gone aswell.

synch'ed will google, all contacts and calendar entries returned to place where they should, restored phone log from my backup. afterwards everything is grand. sadly, didn't made logs, just forgot, that I have that possibility to make so easily :(

that never happened before. maybe there is a connection to lately restore I made some days ago from cm11 back to cm10 (cm11>recovery>factory reset>format /system & /data>recovery reboot> cm10 restore> cache clear, dalvic clear> reboot to system)

regards.
[Samsung Galaxy SL i9003] cukierkas:
Silly question, if you fellas allow me.

What does this setting stands for.?

Cpu frequency in deep sleep state?

Because there is no difference if I tick more than 600, but [MENTION=409989]300[/MENTION] and less, having loads problems, like pairing, call screen lag, music glitches etc.

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
cm-10-20140102-UNOFFICIAL-galaxysl.zip

I polished the code of DoubleTap2Wake and added a "double tap on the statusbar to sleep" gesture (backported from CM11, enable it from the status bar settings).

DoubleTap2Wake is now configurable, but there's no handy way to do it, you have to do it from terminal emulator:

su
cd /sys/devices/platform/omap/omap_i2c.3/i2c-3/3-004a
echo [I]VALUE[/I] > dt2w_[I]PARAMETER[/I] [COLOR="Grey"]#delta_x, delta_y, timeout_max, timeout_min[/COLOR]

I honestly don't know what's happening, all your logs show different reasons for the reboots and I couldn't find any link between them. I don't think it was any of the recent changes.

DeviceParts is the name of the apk, "Advanced" in the settings is a link to open that apk, which is not shown in the app drawer.

That's why is optional ;). I can't explain why your phone was hot.

No, restoring can't cause such issues.

It happened to me once. I had no errors, but all my contacts and calendar notes disappeared. A simple resync solved the problem.

When the screen is off the device is not necessarily sleeping. That setting limits the CPU frequency in this situation.

Try to set "performance" as CPU governor for a while. Apps like CPUSpy will show you that only two frequencies will be used. Limiting the screen off frequency could be useful when the device has to do something with the screen off and the best performance is not required (listening to music for example). Forcing 300MHz is not a good idea, a lot of stuff is done when the screen is off and 300MHz is a way too low frequency for anything.
[Samsung Galaxy SL i9003] ageback:
I've encountered several SODs with 1214 build and kernals after it.

My question is how can I catch SOD log? So that the dev can analize it.
[Samsung Galaxy SL i9003] cukierkas:
updated, working fine.

nice job, glad to use it :)
[Samsung Galaxy SL i9003] cukierkas:
Hello. How to check fast dormancy status on cm10? And disable if it's possible.

On gb I used to enter *#9900# code and disable it. What to do in cm10? Thanks.
[Samsung Galaxy SL i9003] loSconosciuto:
The usual "vold down + vol up + power" and post the file that is generated in /sdcard/logs_qwerty/.

Force a reboot pressing the power button, otherwise logs would be of no help and try to grab them also during the SOD and see if LEDs blink or the file is generated.

As far as I know, there are no ways to do it.

DeviceParts allows you to force UMTS and it does that sending a command to the SamsungServiceMode app. Maybe something similar is possible to disable fast dormancy, but honestly I don't know how to do it nor I care enough to find a solution (I want fast dormancy enabled, HSPA all the time is just a waste of power). pawitp (I9000 mantainer and one of the major contributor to all the RIL related stuff we are using) probably knows the answer, but I don't want to bother him.

Anyway, aside from the standard *#06#, I think all the other working codes follow the following pattern: *#*#NUMBERS#*#*
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

I noticed that the compass doesn't show the right direction. It shows the direction with exactly 180 degrees difference.

Is there any way to calibrate it?
[Samsung Galaxy SL i9003] loSconosciuto:
The only way I can think of is to alter the data manually, but that requires a recompilation of the sensor HAL or kernel.

Note that the accelerometer calibration that can be performed from DeviceParts is broken ("system" can't write the file for the calibration, but manually doing that as root does nothing...).

The orientation sensor is not working very well for me, especially indoors. I don't think it's a problem of the driver or the HAL in my case, but I've never used it enough to be sure.
[Samsung Galaxy SL i9003] ageback:
20140102 build got one sod and after long-press power reboot I got the log.
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Today got the situation, when lock screen was active, but device was unable to switch off the screen by him self.

Log attached. http://www.speedyshare.com/zjMnF/log-140106-203155.txt

One more thing. Can I ask for a favor?

Can you make the option, that screen turning on by home button would be choose able?

Thanks.

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
There are no errors in the last_kmsg. However I can see there were issues with the GPU when you took the log, so I suspect the device was laggy right after the reboot (it was already reported once, never happened to me).

I thought the option was already included. I could backport it, but an alternative solution would be editing the keylaout file:

Open /system/usr/keylayout/zeus_key.kl and comment out the "WAKE" flag of the home button like this:

...
key 102 HOME [COLOR="Red"]#[/COLOR]WAKE
...

or delete "WAKE" entirely, but in this way you just have to remove "#" to re-enable it. Not very handy (a restart/reboot is required), but simple.
[Samsung Galaxy SL i9003] cukierkas:
Yes, working properly. :)
[Samsung Galaxy SL i9003] Drizzt_Kueh:
SOD and unexpected reboots returned with latest version

Hi [MENTION=4349695]loSconosciuto[/MENTION], I'm suffering, after a while without problems, SODs (semi SODs - the phone still is working but the screen won't wake up) and unexpected reboots. I'll post the logs when I can get'em.

In this case, I'm posting a last_kmsg log after an unexpected reboot. I did just rebooted the cellphone manually, sent a sms and the device reboot by itself.

I hope it helps you to figure out if it's a regression or a new bug.
[Samsung Galaxy SL i9003] cukierkas:
Hello to everyone. Having fun using this rom. Tried and kitkat, tried and gb on last weekend, returned to qwerty with the smile on my face :)

Now lets talk about small issues.

Blue tooth. Still having stalled situation on closing the connection between headset and the phone. Connection is closed, but bt icon on status bar still shows the connection and afterwards bt is unstable until I re-enabling it. And still the same after flight mode, bt can't start automatically on certain time with Tasker or phone scheduler. It starts somewhere hidden, no connections can't be established until reboot. Afterwards without enabling anything, bt works grand. Voice quality is perfect, have nothing to add except thank you for your fine job:)

Can anything be done more with bt stability?

2g mode doesn't stick after flight mode or reboot. You've said earlier, that is the way it should be, but on gb everything stays as user confirmed. Still hope that this function could be working.

Call two way recording. On my nexus 5 it works, so still hoping have this feature implemented. If not, sad, it's your call. Founded some xposed modules about it, but simply it doesn't work.

Anyway, this is most advanced and user friendly rom I've ever used, so hats off to your knowledge.

Regards, happy user.
[Samsung Galaxy SL i9003] loSconosciuto:
Uff, I though I got rid of those SODs.

I couldn't see anything in your log ("usual" memory management issue, couldn't find the problem yet), except that I made a little mistake in dt2w that I fixed (unbalanced IRQ wake enable/disable, nothing to be worried about). I uploaded a kernel with the fix: kernel-cm-10-20140108-galaxysl-signed.zip

For those building the kernel on their own. I rebased my kernel repo, the fix is included in aa45d2.

The 2G issue is more a workaround not to brake things. I've never tried to anything about it, but those who worked on RILJ knew what they were doing. I find interesting that my device usally uses 3G only mode, which is what I was using on stock. I wonder if stock ROMs save the preferred mode somewhere (I'm thinking about the param partition, no accessible with the 3.0 kernel or any 2.6.35 kernel using MTD, unless the right modules are inserted). I would expected 2G/3G to be the default mode, 3G only is a weird one.

I really don't know what to do with bluetooth, logs didn't reveal anything and it seems that to experience those issues BT has to be used a lot, so I will never be able to debug them.

Call recording requires too much work (especially for me that I don't much about ALSA & co.) and I don't have the time for it. Actually, I don't have time for anything currently.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
...

To be honest, maybe you actually did it. Before posting the unexpected reboot log, i've suffered 3 SODs... but after posting it... not once. Neither more unexpected reboots. I'll flash the kernel and test it.

Thank you.
[Samsung Galaxy SL i9003] cukierkas:
hello, thanks for update, but after installing it, seems that double tap to wake doesn't work :(
[Samsung Galaxy SL i9003] loSconosciuto:
Ops, the correct permissions are not set and DeviceParts can't enable dt2w. I didn't notice the problem because I manually enabled dt2w from adb...

I uploaded a new kernel blindly repackaged (I couldn't test it): kernel-cm-10-20140109-galaxysl-signed.zip
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Thanks, but now the option to enable the double tap is disabled (in grey, not able to enable it).

Enviado desde mi GT-I9003 usando Tapatalk 2
[Samsung Galaxy SL i9003] loSconosciuto:
Derp². I think the kernel I just posted doesn't set the correct permissions to the correct file (I unpacked an old kernel), however the option should be clickable. Are you using an old build? Because I changed the name of the file to which DeviceParts has to write to enable dt2w. If you need DeviceParts, here it is.

Same name for the kernel: kernel-cm-10-20140109-galaxysl-signed.zip
[Samsung Galaxy SL i9003] puppynaz:
Small help needed

Hi, [MENTION=4349695]loSconosciuto[/MENTION].

I followed this guide and I wanted to build CM11 roms for myself.

I get this part:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="dhiru1602/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="cm-11.0" />
<project name="dhiru1602/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="cm-11.0" />
<project name="dhiru1602/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-11.0"/>
</manifest>

But instead would things go wrong if I typed:

<project name="sconosciuto/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="latona-3.0.y" />

Or do I need to fork everything else from your repo, itself?

Thanks, en avance. :)
[Samsung Galaxy SL i9003] cukierkas:
thanks, newest kernel seems to solve double tap to wake problem.

no errors, no sods, smooth as it should be.

happy user

Edit. Bt disconnected in the middle of the voice talk. Afterwards Bt unusable, helps only to switch off and on. Log attached.

https://drive.google.com/folderview?id=0BzdEV08prFp3NWdLSkFQQUwwLU0&usp=sharing

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
I'm maintaing two defconfigs, one for CM10 and the other for CM10.2 (no changes required for CM11).

If you want to use my sources, you have to change the defconfig name in device/samsung/galaxysl/BoardConfig.mk

...
# Inline kernel building config
TARGET_KERNEL_CONFIG := [COLOR="RED"]latona_cm10.2_defconfig[/COLOR]
TARGET_KERNEL_SOURCE := kernel/samsung/latona
...

Or you could replace in kernel/samsung/latona arch/arm/configs/latona_defconfig with arch/arm/configs/latona_cm10.2_defconfig and don't do any change to BoardConfig.mk, do as you prefer.

It's better to commit all the changes you do. Look for more info about "git commit" if you are new to git. "repo" could refuse to sync the repos otherwise.

It would also be better to revert a commit for a better compatibility with Android 4.2+:

cd kernel/samsung/latona
git revert [URL="https://github.com/sconosciuto/android_kernel_samsung_latona/commit/4b8ca79f8ce4fd8c8d1becb31b3815cd5bb51fbb"]4b8ca79f8ce4fd8c8d1becb31b3815cd5bb51fbb[/URL]

I also suggest you to pick this commit.

Note that all those changes will be lost (at least if you committed the changes) whenever you do run "repo sync". That's because "repo" will re-sync all the repos inside roomservice.xml. You can avoid this by manually adding the repos, for example:

mkdir -p kernel/samsung/
git clone https://github.com/sconosciuto/android_kernel_samsung_latona kernel/samsung/latona

but then you have to manually update it.

Thanks for reporting that everything is fine.

I have no permissions to open the log.
[Samsung Galaxy SL i9003] cukierkas:
sorry, link updated. from now, will upload all the qwerty logs here. hope that would be easier to manage it :)

regards
[Samsung Galaxy SL i9003] puppynaz:
Thank you so much :)
[Samsung Galaxy SL i9003] cukierkas:
hello there.

sadly, but I decided to disable double tap to wake option. sometimes phone in front jeans pocket becomes hot and screen can't turn off by it self. second day with this option disabled - none of these appeared. device works as it should be.

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

I noticed that when i make a call with viber screen doesn't turn off completely and backlight comes up!

I dont have backlight problem in other situations

Can it be a Rom/Kernel related problem or its related with app?

Can it be usefull to solve the backlight problem with afew users?
[Samsung Galaxy SL i9003] loSconosciuto:
Unfortunately the touchscreen is pretty sensitive to the enviromental changes, so maybe the touchscreen keeps detecting stuff even when there's nothing to sense. I tried to increase the touch threshold ones, but I couldn't notice big differences regarding false detections. It actually made dt2w slightly harder to use, so I preferred not to change the default threshold.

I don't know, I've been hunting that bug for so long that I eventually gave up.

I've never used Viber, but I think the screen should turn off completely. Anyway, I don't have the device with me, so I can't do tests on my own right now, but thanks for the report.
[Samsung Galaxy SL i9003] cukierkas:
what new device you have bought?
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

How can i help with that?
[Samsung Galaxy SL i9003] loSconosciuto:
I've been uncertain till the purchase, I couldn't decide between the Nexus 5 and the Moto G. I ended up buying the latter and I'm very happy with my choice. It was even on sale when I got it :p

Do you mean with the backlight issue? I think that without an affected device there's not much to do. I collected tons of logs and did many tests with poluyan_stas, but I could only partially fix the problem fixing the off-mode. That bug really leave no traces, it's a really weird issue.
[Samsung Galaxy SL i9003] cukierkas:
I'm with nexus 5. Moto g wasn't in my country at that moment. And I'm happy with purchase as well, looking forward to e-ink displays.

Will you stop development of Qwerty?

Still using it on my work routine, so this piece is still with me :)
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Moto G

Really? I got one too! :D

Are you planning, eventually, to getting involved into the development for that phone? (Sorry for the off-topic)
[Samsung Galaxy SL i9003] loSconosciuto:
You can never go wrong with a Nexus.

Probably there won't be major changes, mostly because I've no time for it, but I'll be here.

I don't know, surely not for a while, for the same reason above. I didn't even unlock the bootloader yet...

For now I just downloaded the kernel source code (the memory management changes of this kernel are taken from the Moto G ;)) and followed dhacker29's work.
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

After some tests with older kernels and recent ones i think that cClock(or c stat ,i dont know! :( ) causes battery drain faster!

Is it normal?
[Samsung Galaxy SL i9003] loSconosciuto:
Maybe, or maybe it's something else. I've never noticed many changes battery-wise. I always had a bad battery life, so...

If you could be a bit more specific, I could see the changes made between the releases. If the kernels you tested have a name like 3.0.xy-zzzzzzzz, post that, if not, give me the name/date of the release.
[Samsung Galaxy SL i9003] mehran 92:
i think that kernel-cm-10-20131201-galaxysl-signed.zip has better battery backup and after that battery consumption slowly raised and in the latest kernel it become better. but not as good as kernel-cm-10-20131201-galaxysl-signed.zip
[Samsung Galaxy SL i9003] loSconosciuto:
I think there were no changes that could impact battery life in a noticeable way since that release, maybe it was something else altering the results of your tests.
[Samsung Galaxy SL i9003] mehran 92:
I remember in one of kernels you said that you activated the C state and you wanted to test battery life!

Maybe that is the problem

I see that most of the time device is in deep sleep (90%) but it drains about 5.5-6% per hour!

I remember that before it was 0.4-0.5% per hour!

My batter is two months old!
[Samsung Galaxy SL i9003] loSconosciuto:
I verified that the C states are not working (it's the same for all the other OMAP3 devices running the 3.0 kernel), so no matter what I set, C1 only will be used.

I tried to fix them porting some changes from the old kernel, but there are still some issues that makes the device unstable.
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Again blue tooth crashed in the middle of voice talk. Log attached in my Google drive, the link is some posts above.

About battery drain. Didn't observed such huge drain, I'm having per night on flight mode max 2%, per working hours on 3g always on not more than 4% .

Yes, stand-by is not so good as on gb, but this is the price of cm10.

Regards.
[Samsung Galaxy SL i9003] mehran 92:
i had 0.4% per hour with kernel 3.0.101 in standby before but now its 5-6% per hour
[Samsung Galaxy SL i9003] Mercedec777:
similar situation. kernel set of 30/12/13 was better to keep

Отправлено с моего GT-I9003 через Tapatalk
[Samsung Galaxy SL i9003] loSconosciuto:
I took a look at your logs, but I couldn't identify the problem. Those logs are pretty huge and most likely I missed something, I could only see some errors here and there, but I'm still clueless.

I can also see you are still using "keep_me_awake". Isn't it affecting battery life in any way?

The thing is that I can't see what could have lead to the higher power consumption. Maybe the string you can get from the kernel version (you can also grab a log and post it, it's reported right in the first line) could help me, I'm worried there's a commit I forgot about that I reverted.

I would exclude the higher awake time due to max17040, I've been using that change for a lot of time even if I pushed it on my public repo after some time and should have a minimal impact on battery life.

I also can't explain why you would notice any improvement with the last release. I didn't do much to increase battery life, mostly little changes trying to improve the memory management.

There are no kernel released on that date, I guess you mean kernel-cm-10-20131229-galaxysl-signed.zip or kernel-cm-10-20131231-galaxysl-signed.zip. Still, I don't know what could be wrong.
[Samsung Galaxy SL i9003] Mercedec777:
yes, you're right, it 31/12/13. Sorry for inattention

Отправлено с моего GT-I9003 через Tapatalk
[Samsung Galaxy SL i9003] cukierkas:
hello there. to say the truth, I don't see any impact to battery life :)

was already forgotten about this options, thanks for refreshing.

returned to default value, will see, how it will behave.

for mean time,returning to kernel2 cm10 version.

tired to charge twice per day, will see, maybe it will hold better. in other hand, one litlle so little mind is telling me to return back to gb. don't want it, but for sake of crap battery will try that later or maybe someday.

regards.