yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] loSconosciuto:
Changing the minfree values could be more effective maybe (don't ask me how or what to set).

I think I will also include the extra free kbytes tunable (brief description here) which is used in KitKat (framework patch). The framework patch is not required since it's a kernel feature, but it can be easily included to automatically configure the tunable.

However I still hadn't tried it, so I don't if there are noticeable benefits. It's not the only change done to make KitKat more RAM friendly (I just gave a quick look at the changes), but it's worth a shot.

Ouch... Maybe I shouldn't manually release st_wakelock but let the 5 seconds pass, but I suspect this could impact battery life (don't know yet). I will provide a kernel sooner or later.

I don't think it was the overclock. There was a crash while doing something on a FAT partition.

My script simply dumps the log as is is into a handy file.

The size of the logs is specified in bytes, this is the current configuration:

dmesg:	256KB
last_kmsg:	1MB (if I remember correctly), but it contains the dmesg, so 256KB
logcat:
- main:	256KB
- system:	256KB
- radio:	256KB (not taken by my script)
- events:	256KB (not taken by my script)

That said, I can't do an estimate because it depends on many factors. For example if the device is suspended most of the time, you can have days logged. If there are many errors you can end up with just few minutes logged.

You can see how much was logged by reading the log. It contains three different logs (dmesg, last_kmsg and logcat). Each of them is separated by the others, to find where each of them begins, look for:

###### dmesg

###### /proc/last_kmsg

--------- beginning of /dev/log/main

--------- beginning of /dev/log/system

The logcat reports the date and time at the beginning of each line.

The numbers at the beginning of the lines of the dmesg (and hence of the last_kmsg too) represent the seconds (with six decimals) passed since bootup. From time to time you can see the date and time clearly written, such as in the lines beginning with "request_suspend_state: wakeup ". From those lines you can calculate the exact instant each line was printed.

On a different note, did anyone experienced any fake-SOD? They don't happen to me usually, so as soon as you get one of them, please report (with logs, so that I can see it was actually a fake SOD). Thanks.
[Samsung Galaxy SL i9003] cukierkas:
Min free values are easily editable with rom toolbox, but, speaking frankly, I have no idea what values are better. About free, default value was 2xxxkb, made it 9xxx.

Thanks in advance.

By the way, are you thinking to concentrate on kitkat? Does Art really works better, faster? Or just it's a wasting if time migrate to kitkat?

Looking forward to the next kernel with Bt fixes and other improvements.

Regards.
[Samsung Galaxy SL i9003] cukierkas:
Forgot to add a screen capture.
[Samsung Galaxy SL i9003] The_GMAN:
The Next Level of Qwerty

[MENTION=4349695]loSconosciuto[/MENTION] I think its time we went to the next level of Qwerty: Android 4.4. Its a better rom for our device, better battery life and more free resources for system to use. overclock that and we will have a super fast rom.

Could you please, please consider moving on to android 4.4, please? :o

That would be the best thing that has ever happened to our device :good:
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

i got many random reboots today with different kernels

it was like a boot loop,after booting to home screen after about 10 secs phone rebooted again and again...

i could get 2 logs

after flashing rom with wipe data and flashing latest kernel,random reboots reduced but still i face some reboots.

One more thing:

with the kernels after 20131201 battery use is awesome and no signal drop!!! :victory:

thank you so much :good:
[Samsung Galaxy SL i9003] loSconosciuto:
Good to hear that I'm not the only one with this problem, it happened the same thing today to me.

The problem was a file system corruption of the /data partition. Since you had the exact same problem, I can say the problem was the patch to the mmc driver that I reverted few days ago to see if it was necessary. I'd say it is.

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

Reincluded mmc driver patch to avoid issues with the internal mmc

st_wakelock will always lasts 5 seconds [MENTION=2606021]cukierkas[/MENTION]: tell me if there are improvements or regressions involving BT)

Included extra_free_kbytes, default value 4500 (see my previous post)

Reduced delay while checking the battery from 500ms to 200ms (if you have fake SODs, please report)

Reverted lowmemorykiller changes. Tell me if you still have random freezes

EDIT: zram is again disabled by default. Enable it from the settings if you want it.

Flash also fix_data.zip, it's a script to check /data and fix eventual corruptions which are causing reboots. The script simply runs the following:

e2fsck -fpv /dev/block/mmcblk0p3

I can't fix from an updater script (in a simple way) /dev/block/mmcblk0p2 which is /cache. Format it manually from the mount and storage menu in recovery.

There's also /dev/block/mmcblk0p1 which needs a check, it's the internal SD card, but that should be automatically checked on reboot by Android. I'll properly verify this and provide another flashable zip in case it's not.

I'm sorry for the inconvenience.

EDIT:

Here also an update to use the 720p video decoder only for HD videos. The regular decoder will be used otherwise: mediacodecs_update.zip

EDIT2: It seems it doesn't work properly. Restore the original /system/etc/media_codecs.xml, if you need an updater zip just tell me.

[MENTION=4655907]The_GMAN[/MENTION] [MENTION=2606021]cukierkas[/MENTION]

I haven't tried KitKat yet. I've been inderectly contribuiting to it working on CM10 (did you see Dhiru's repos by chance?).

What I think is that KitKat is designed for modern devices with low RAM. Starting from Android 4.2 I've noticed that more processing power is required.

If you put side by side this device and the Nexus S, both running CM10, you'll notice that the latter is overall faster, but not so much.

Do the same comparison with CM10.1 or newer, the difference is quite obvious. Our device can't even smoothly scroll the settings.

There's nothing I need badly on newer versions of Android, so I'll keep using CM10.

Maybe I'm wrong regarding CM11, but I can't see why it should be lighter in terms of processing power required when compared to CM10.2, it's an OS designed to run on new devices.
[Samsung Galaxy SL i9003] cukierkas:
Thanks for updates. Will inform more about results tomorrow.

About repos. Sorry, I don't watch that kind of stuff, but thanks for sharing your knowledge.

Speaking about kitkat. Yes, I've heard, that it's need at least 2 core cpu for proper work. But another thing. ART. Does it works better than ordinary virtual machine? Don't know, still thinking to try and see the difference. The other thing, speaking about outdated hardware. maybe we shoud play with ics instead, as f.e. se arc s users still do. or there is no big difference between cm9 and cm10?

Regards.
[Samsung Galaxy SL i9003] The_GMAN:
Thanks for letting us know loSco, but u could still give it a try to see the outcome. If the performance we get is lower than the current cm10 Qwerty then we leave it and concentrate on cm10.

If there is a future rom that has the chance of giving the performance of Qwerty, its cm11. After that I don't think there will be any newer Android version cutout for older devices like i9003.

cm11 is the best shot we have and after that there won't be any, so please try.

Does that theme work on Qwerty? I only see support for android 4.2

Thnx for theme.:)
[Samsung Galaxy SL i9003] loneagl:
First off,I would like to thank loSco for stubbornly developing on a single version of android and optimizing it to the fullest.Have been using it a couple of days n it's very definitely snappy, especially the scrolling.

And using the kit Kat theme for cm10, I can fool myself into actually using the cm11, let alone the common android-using muggle on the street.
[Samsung Galaxy SL i9003] cukierkas:
Morning. Short log about Bt, which wasn't turned automatically and afterwards manually toggling it. That happens after flight mode.

Everything grant after reboot. Log attached.

http://www.speedyshare.com/RN8kU/log-131212-074452.txt

edit2: still having problems with headset connection. sometimes works, sometimes doesn't. log attached

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

today i had some freezes after watching some videos

also after playing a video suddenly video stop and mx player and any other player couldn't play videos until restat

here is the freeze and video playback logs
[Samsung Galaxy SL i9003] loSconosciuto:
[MENTION=2606021]cukierkas[/MENTION]

ART: I've read just few things about it, so I can't answer your question.

CM9: I honestly can't remember how it was, but CM10 is fine for me. Arc S users still use ICS because that's the latest official ROM. Users usually use official ROMs and custom ROMs based on it. The real difference is between GB and all the other releases, I don't know if you ever tried CM7, but that thing flied, but the developement was abandoned at an early stage in favor of ICS, which required a huge amount of work. GB is the ROM for a really smooth experience on this device.

Anyway, if you are comparing the SL with the Arc S, note that the GPU of the latter is better which should help in the smoothness of the UI and probably even the CPU is better, but I'm not sure of this.

BT: At least there were no timeouts. I couldn't find anything in your log, but I maybe missed something, these logs are pretty big and I really looked at it quickly. I'll see it again.

EDIT: There's also something I didn't understand. With "doesn't work" do you mean that you have to reboot the device to turn BT on or just that it takes several attempts to pair a device? I really don't use BT, so I'm not familiar with it and all the issues.

[MENTION=4655907]The_GMAN[/MENTION]

I don't think I could really do much, but the most important thing is that I really have no time right now.

[MENTION=4915822]mehran 92[/MENTION]

Did the freezes started to happen after this release or they have always been there?

I can see from one of the logs that there were some issues with binder (which completely filled the dmesg with errors. So many errors that there are just the last 37 seconds logged in one of them). Try the new release, maybe binder was not the cause of all your issues, but it definitely caused you troubles.

One of the reasons why I drop frequent releases with minor changes is to easily address eventual issues. I usually test everything, but sometimes that's not enough.

I've a question for those of you who usually get fake-SODs: how often do they happen?

As always, please tell me if it's happening with the recent releases.

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

Reverted changes related to st_wakelock which are not doing anything useful

Restored the lowmemorykiller changes

Reverted all the changes to binder
[Samsung Galaxy SL i9003] mehran 92:
[MENTION=4349695]loSconosciuto[/MENTION]

I cant remember well but i think they are happening with the recent kernels
[Samsung Galaxy SL i9003] cukierkas:
updated. will inform later about the results.

still thinking to try kitkat, but too lazy to customize it to my personal needs. what do you thing, if I would make a backup of /data and would restore it on kitkat, would that work perfectly? guess not :)

EDIT. Attaching the log. Bt connection lost in the middle of the voice talk.

http://www.speedyshare.com/meGAN/log-131213-111530.txt

Tried with zram disabled, no, ram fills to fast, having situation with 0MB free :) Enabled zram 26% again. By the way, reduced cpu frequency to 800. Didn't observed a huge difference in performance, but battery holds better.

One more edit. Attaching log, where bt connection was still alive, even headset was disconnected. Sorry for spaming. Just say if I'm disturbing you too much :)

http://www.speedyshare.com/HBFWK/log-131213-173949.txt

Have a great day.
[Samsung Galaxy SL i9003] loSconosciuto:
Upgrades are expected, databses and settings will be automatically adjusted. Downgrades on the other hand are not expected, so take a backup in case you want to revert back to CM10 afterwards. Restoring /data after the first boot should be equal to booting CM11 with no wipes, which again should be fine, but why would you do this extra step?

Don't go back to stock, it's just a waste of time, data wipes are faster and equally effective.

Be aware that the there's not enough space in /system for the complete gapps, I don't know what are the consequences of this, but they can't be good.

Regarding BT (first log), it seems there was an error and the connection was closed.

W/BT HSHFP( 1892): RFCOMM poll() returned success (1), but with an unexpected revents bitmask: 0x18
I/Bluetooth HeadsetBase( 1892): headset read error 5

I guess you didn't have to reboot to have pair your headset again.

I see there are still some tx command timeouts...

In the second log I can see that the connection to your headset was closed twice because it was stalled.

Just a question: is BT that bad when compared to the old kernel in terms of stability?

And no, you are not bothering me.
[Samsung Galaxy SL i9003] cukierkas:
Thanks for your answers. About trying kitkat. I'm just thinking, so thanks for full explain of some future errors. There is some time needed to carry all the upgrades, will leave it for future releases. About Bt stability. I guess kernel 2 was way stable on terms of connecting and disconnecting. There weren't any problems after flight mode to autostart, weren't any sudden drops in middle of talk. But voice quality was terrible, thanks for fixing it. To say the truth, some time passed after kernel 2nd usage, so my thoughts might be not so truth. And yes, there were some sudden stalled situations, but they were really rare.

About ART. Is it possible to implement it to cm10? Just for test purposes.

Regards.
[Samsung Galaxy SL i9003] puppynaz:
Well, I just flashed this ROM (Kernel 3.0 version, obviously) and the last I remember being on this ROM was back in May when only the Kernel 2.6 version of the ROM was out. :p

Is KSM fully functional on this ROM?
[Samsung Galaxy SL i9003] loSconosciuto:
cm-10-20131214-UNOFFICIAL-galaxysl.zip

New build with just all the pieces I released all these days as separate zips. In this way new users will have everything updated.

The kernel is different from the last I posted, I reverted all the changes to lowmemorykiller (no issues found with them, but I want to be sure) and didn't include the experimental workaround to fix the fake-SODs (I'm not sure it's working, so got rid of it for this buildl).

There are surely some other little changes here and there, but nothing big. The kernel is mostly what differs from the previous build, but if you flashed all the updates I posted, you won't notice many differences.

The quality was probably due to the voice recognition issue that I later fixed.

Backporting ART? I don't know, it's a core component and I'm quite sure it would require a huge amount of work. Since the development started on 2011-06-16 I guess it's technically possible, Google must have test it somehow, but I ain't gonna do it :silly:

It's even working in my 2.6 builds.
[Samsung Galaxy SL i9003] puppynaz:
Also I'd like to point out a minor but a bug. I flashed the latest CM10 build along with gapps and the latest kernel. After the Google Sign-in screen, I couldn't go anywhere. Like there's the Trebuchet launcher, but no icons. It took me hours figuring out where I went wrong or if it was the launcher at fault. So I texted myself from another phone play.google.com/store and somehow download Nova Launcher and then I got out of there. :p

Like the launcher was completely blank. So texting myself play.google.com/store (which opened the app) to download Nova Launcher was the only workaround.
[Samsung Galaxy SL i9003] mehran 92:
I had the same problem too
[Samsung Galaxy SL i9003] cukierkas:
yes, thats true, there is no trebuchet :)

using holo, so never had a problem.
[Samsung Galaxy SL i9003] The_GMAN:
That's really true. The thing is CM10 is really good (probably the best) performance wise but sucks on battery. CM11 has better battery life but far from CM7. With CM11 my battery can last a day while with CM7 my battery could last almost two days and it was so awesome for gaming and so fast. What I would really love is someone to take on CM7 and ramp it up with all the jellybean features. That way we can have top performance from our device while being super stable and maintaining the best battery life. If that happens then we don't need any future android update, not even 4.4. What people forget is that this device was never designed to run jellybean.

I don't know if its possible but if anyone can do it its you, loSco. But sadly, it requires a lot of work and you mentioned you don't have enough time.
[Samsung Galaxy SL i9003] loneagl:
I second cm7 development...as far as I remember only the camera didn't work.if anyone can just theme it up, it would be awesome.
[Samsung Galaxy SL i9003] cukierkas:
hey, please be more specific :)

http://xdaforums.com/showthread.php?t=1374340&highlight=cm7
[Samsung Galaxy SL i9003] puppynaz:
Yes, this one, precisely. The development had stopped in favor of CM9. Someone really needs to work on this.
[Samsung Galaxy SL i9003] cukierkas:
Really don't know is it worth returning to gb, when cm10 works so fine :) Losco, last cm10 version works really fluid , will inform more about bt tomorrow.

Regards.

For those, who want cm7. Try flyongb rom, that was best gb experience for me. Thanks to [MENTION=4473033]LoLaTiOn[/MENTION].
[Samsung Galaxy SL i9003] loSconosciuto:
Weird, I didn't have any issue with Trebuchet and that's my launcher. I would have notice it... Post some logs

Anyway, working on CM7 now would mean throwing away a lot of work, at least for me, other than being a time consuming thing.

I like CM10, not too old, but not too heavy for this phone, even if it's not blazing fast.

We probably all use our device in a different way and CM10 is working ok for me. I would have bought a more powerful device long ago otherwise.

I'm also used to some new feature I don't want to miss.

[MENTION=4655907]The_GMAN[/MENTION]

Is there really such a big difference in battery life? The stand by power consumption had always been good for me, the battery drains really fast when the device is used, a lot. I also think the fuel gauge chip wrongly estimate the discharge under heavy loads, but that could also be due to my ****ty old battery. Whichever version of Android is used, the consumption while in deep sleep shouldn't change, that depends on the kernel. The problem could maybe be the OS waking the device more frequently. I also think that the consumption while the phone is in use doesn't change so much.

I don't know what happened to my phone, but it's faster than usual. It must be because I cleaned it up after a veeeeeeeeery long time.

Did you notice any difference in the performance? Did you flash any kernel after you've flashed the ROM? I wonder if the lowmemorykiller changes are good or not...
[Samsung Galaxy SL i9003] cukierkas:
Can you explain more what changes you did to low memory killer.?

Last 4 days reduced cpu to 800, so it's hard to tell :)

No, no other kernels, just your last cm version.
[Samsung Galaxy SL i9003] puppynaz:
Try from scratch, perhaps? Wipe/data and flash your latest CM build. And if you get stuck, text yourself from some another number any URL which will open the browser app. :p

It's not a big issue, tho. But perhaps replacing Trebuchet with some other minimal launcher could do. :)
[Samsung Galaxy SL i9003] loSconosciuto:
It was probably what I did to my device: removed some old and unused apps, removed a lot of junk and freed up some space and then trimmed /data (never noticed big differences afterwards, but maybe this time it was necessary).

Anyway, I updated the low memory killer to the version used in the 3.4 kernel, these are the changes with their description (the last commit in the list is not mine, I've just noticed I messed the authorship). Not many changes.

Yes, I tried it, and it worked perfectly. It bothers me that something important like the launcher is not working properly on a fresh install. I suspect some upstream changes broke it for us, it's intended to run on CM10.2 after all. I reverted some recent changes done to improve the out of the box experience and few other changes, repacked the ROM and uploaded it. Same name as before, but I appended to the name of the old one "bokenTrebuchet".

If you have time, try it.

Anyway, I like Trebuchet and it's one of the few free and open source launchers.
[Samsung Galaxy SL i9003] cukierkas:
Never heard anything about trimming. Thanks :)

This one helped for me as well!

Regards.

Morning edit. Something hooked the Android in flight mode. Bbs couldn't find it, because of fake sod and reboot. Hope log will indicate something.

http://www.speedyshare.com/mexcN/log-131216-065602.txt

edit2: maybe that could be the cause, max17040 state? charger was not pluged in, wanted to check how many battery capacity I would loose during the night. Lost more than 30%, endedd with the fake SOD :)

[ 5091.899902] max17040 4-0036: online = 1 vcell = 3878750 soc = 63 status = 2 health = 1 temp = 270 charger status = 0
[ 5091.908691] max17040 4-0036: online = 1 vcell = 3878750 soc = 63 status = 2 health = 1 temp = 270 charger status = 0
[ 5142.016418] max17040 4-0036: online = 1 vcell = 3881250 soc = 62 status = 2 health = 1 temp = 280 charger status = 0
[ 5192.517700] max17040 4-0036: online = 1 vcell = 3880000 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5242.549072] max17040 4-0036: online = 1 vcell = 3878750 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5292.580291] max17040 4-0036: online = 1 vcell = 3878750 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5342.660095] max17040 4-0036: online = 1 vcell = 3877500 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5393.179534] max17040 4-0036: online = 1 vcell = 3876250 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5443.669036] max17040 4-0036: online = 1 vcell = 3876250 soc = 62 status = 2 health = 1 temp = 290 charger status = 0
[ 5494.044921] max17040 4-0036: online = 1 vcell = 3875000 soc = 62 status = 2 health = 1 temp = 300 charger status = 0
[ 5544.239715] max17040 4-0036: online = 1 vcell = 3873750 soc = 62 status = 2 health = 1 temp = 300 charger status = 0
[ 5594.296417] max17040 4-0036: online = 1 vcell = 3873750 soc = 62 status = 2 health = 1 temp = 300 charger status = 0
[ 5644.330688] max17040 4-0036: online = 1 vcell = 3872500 soc = 62 status = 2 health = 1 temp = 300 charger status = 0
[ 5694.362670] max17040 4-0036: online = 1 vcell = 3871250 soc = 62 status = 2 health = 1 temp = 300 charger status = 0
[ 5744.421478] max17040 4-0036: online = 1 vcell = 3871250 soc = 62 status = 2 health = 1 temp = 300 charger status = 0

edit3:

bt turned on successfully, maybe because of active screen at certain time (as you notice, screenshot time is 7:39, time to bt turn on at 7:40). I was saying the same some days ago - autoturning on works good when screen is active or little time passed after the active screen state. Problems appears if screen wasn't touched after the flight mode before time to turn bt automatically. Hope you're getting the idea :)

Regards.