yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131216-galaxysl-signed.zip

Re-included the workaround for fake-SODs (I hope this really works, even if I don't know why it should)

Reverted all the changes to LKM and binder again

FYI auto trimming was implemented by Google starting from Android 4.3.

Cool, as I said the kernel included in the ROM doesn't include the workaround for the fake-SODs. After only 2 days of use you got one.

Flash the kernel I just posted and let's see if it happens again.

"charger status = 0" means that the device is not charging. Those are normal battery checks. The fact that they are all 50 seconds apart from each other means that the device was not suspended and this is why I call them "fake-SOD". Fake-SODs should cause an higher battery consumption since the device never enters deep sleep (notice how the battery temperature slowly increases. 290 = 29.0°C).

I honestly didn't look much into this minor issue. As of now I don't know what's happening when BT can't be turned on and why turning the screen on make it always work. I'll try to look into it.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
After 7 hours of using the rom (latest ROM + latest kernel version), with a huge amount of hours with the cell plugged to the battery charger, i didn't get any FakeSOD, RealSOD, or unexpected reboot yet...

Impressive work [MENTION=4349695]loSconosciuto[/MENTION], really impressive, you've just build an almost perfect ROM. The well-known video recording sync problem seems to be the only problem i got now. Amazing, thank you SO MUCH.
[Samsung Galaxy SL i9003] cukierkas:
Hello, really must agree with person above. No sods or memory hooks, everything works fine. Was trying 2g only, so must admire, standby time is awesome. Per night lost 2%, Bt doesn't started as I was expected. And using 2g only, svcnet wakelock was active for more than 0,5 hrs.

Good job.
[Samsung Galaxy SL i9003] cukierkas:
Sorry for double posting, Xda premium app doesn't allow to add more than one picture.

View attachment 2459350View attachment 2459348
[Samsung Galaxy SL i9003] The_GMAN:
Yes! there is! When last did u use a GB rom? Try going back to cm7 and use it for a day, you'll be amazed. In GB I can continually browse in 3G for more than 4 hours while in JB i can barely browse for 3 hours. If we compare standby times, GB leaves JB in the dust. I lose about 5% in 10 hrs of standby in GB while in JB its almost a percent per hour.

My main problem with JB is the battery loss after 30%. Say my battery is around 70% and I start browsing in 3G until my battery drops to 30%. Then, when I turn off the data connection and put my phone in deep sleep, my battery will continue to drain as though I am still browsing until it dies. This happens no matter what i do, even if I put it in flight mode. I thought it was my old battery but I even tried buying a new battery. I don't know if this happens to me only but this problem isn't there in GB and is reduced in KitKat.

As for wrongly estimating the discharge rate, that's not because of your old battery, I have a brand new battery and have the same problem and so does every one using cm10+ versions, I am sure. Again this is another problem that is very minimal in GB, I don't know why. Maybe because our phone and battery wasn't designed for JB.

CM10 is just fine, we don't need a super fast rom but if just these battery problems are solved it'll be greatly appreciated.

That's why I am talking of back-porting CM10 features to CM7.
[Samsung Galaxy SL i9003] Gondya bhau:
try cm10 with 2.6 kernel...performance wont be anywhere near the kernel 3 one but standby time is much better..i think its more kernel related than rom related....so even if we get cm7, kernel 3 wont give you the GB like battery life you expect....

[MENTION=4349695]loSconosciuto[/MENTION] while cm10 is pretty good feature wise (even for me), i really think ART will take on a major role in future android versions as it is further optimised and more apps start supporting it.....just my opinion...

havent been using my phone much...just whatsapp and 45 mins worth of calling....
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131218-galaxysl-signed.zip

Change C state latencies and thresholds (stock ones)

(not a kernel thing) Auto fstrim on boot. [2]

Tell me if there's any difference in battery life.

I still don't know why the C state stats are not working.

cat /sys/devices/system/cpu/cpu0/cpuidle/state*/* #only C1 is used according to this
echo 1 > /sys/kernel/debug/tracing/events/power/cpu_idle/enable #enable tracing
cat /sys/kernel/debug/tracing/trace_pipe #all the states are used ?!?

[2] I included fstrim in busybox and added an init service which trims /data and /cache on boot. It can be disabled with

su
setprop persist.sys.auto_fstrim 0 #anything but 0 will re-enable it

Auto fstrim are limited to one every 10 hours and they are done automatically done only on reboot.

I was talking about differences between CM10 and CM10.1/2/11. I know that GB holds better the battery, that's not a mistery, but I can't see why CM11 should be that better when compared to CM10.

It's been a long time since I used a stock ROM. Anyway CM7 used more battery than stock ROMs, but when I used it there were some OMAP PM stuff disabled, such as the off mode.

The fuel gauge chip works independently, it doesn't matter what's the ROM. What could change is how much the battery is stressed, which is likely the cause of the wrong estimation. The Nexus S (and many other devices) use the same chip, so JB is not a problem.

On an unrelated note: you are all saying that KK is made for devices with 512MB of RAM, so it should be the best.

Did you note that Android 4.1 was officially released for the Nexus S, which has (less than if you consider the reserved memory) 512MB of RAM? It works great on it. I think that what we miss is a good GPU for the UI. The heavier UI is what keeps me away from newer versions of Android.

Yeah, I'd like to have a better battery life too, but it's not that easy. Till now I mostly worked on the stability of the kernel and the ROM (and performance too) and I the results are not that bad. I just have some very rare reboots, somewhat similar to those that used to happen rather frequently.

The differences are huge, it's not doable/worth it in my opinion.

The old kernel is probably more optimized, Samsung changed bits of code here and there.

The fact that the backlight is not kept off on your device means there's something not working as before. I know that the off mode is what keeps the backlight off and we have been able to make it work. However you still have issues, the backlight randomly turns on. That could mean that the device is more active with the 3.0 kernel, otherwise the backlight should stay off.

There's no doubt, but it doesn't change the fact that I find newer versions of Android too heavy (I actually didn't test CM11, but...).
[Samsung Galaxy SL i9003] redflash52:
I flashed today this rom. Is really smooth and fast :) really good work!

The only thing is that since i flashed this rom i have only 2g connection :( i have tried to set up everything but it still remain 2g. How could i force a 3g connection?
[Samsung Galaxy SL i9003] Gondya bhau:
i originally thought the backlight staying on (for those 30 seconds) because of the device staying awake.....but in reality, its more of a screen problem than an awake problem..or maybe a combo :p...i can do many things on my phone wherein the device is awake but the backlight stays off....that is by automating tasks to perform at a specified time/state ( with tasker).....basically if i setup tasker to play songs when i connect my headsets, i no longer need to turn on the screen.....so i can keep the backlight off....

from what i remember of your last echo commands on kernel 3....the dim screen echo didnt actually turn the screen off ( the backlight stayed on)....the off echo command did that...but only running that on its own led to weird behaviour.....seeing my phone does get dimmed, the dim seems to be doing its job....albeit the off command which should run after that seems to only occur after around 30 seconds.....and in case of when the device stays awake (like music), never

coming back to the kernel...while i know i must suffer an increased drain due to the backlight....i still feel the standby drain of kernel 3 is more.....say if my phone is in standby for 3 hours....the backlight goes off after 30 seconds....so other than those 30 seconds, i should face the normal drain right ??? even after making considerations for the backlight,the drain is greater than kernel 2 based roms......so yeah...some samsung optimisations are missing.....

phew....some explanation eh.....anyways...i dont wanna sound like a cry baby....i know solving the backlight takes a lot of effort and for the no. of people facing it, its probably not worth it......but from my experience, i can deal with the backlight if the kernel battery life is better....if you could work on that atleast, it would be really great for the people who say have a new battery...or those who use the phone considerably less...:good::good::good:
[Samsung Galaxy SL i9003] cukierkas:
Short mindstorming about last kernel. Don't know what c stands for, but deep sleep seems to be better.

3g always on, exchange about 10 push mails, 1h47min talk time. Cpu at 800, gpu at 266. Scroll cache disabled, don't know, if it's gives any impact to battery. Bt always on. Last day was on 2g,got about 4,7%. Now about 5 with something. That's definitely better. Some weeks ago average was about 7%.

Regards, happy user.
[Samsung Galaxy SL i9003] cukierkas:
Bbs screenshot.
[Samsung Galaxy SL i9003] loSconosciuto:
Little update: the stats are correct, only C1 is used (the most performant and most power demanding state). I've managed to get all the other C-states working, but there are some issues to solve.

Add the toggle to the notification panel or dial "*#*#4636#*#*", there's a setting to change mode there. Be aware that the selected mode is not be restored on reboot. It should be random, but in my case I always get "3G only", which is what I want and so never cared to understand why it happens.

I wasn't saying that the higher power consumption was due to the backlight issues. If you set the brightness to zero, the screen stays off. If the device is suspended, the backlight turns on randomly. That suggests me that there's something sending signals to the backlight controller when the device is supposed to stay "off", something active which is not active with the old kernel. Unfortunately I have no idea of what's going on.

More than not being worth it, it's a pain for me. I tried a lot of stuff already with poluyan_stas, but I gave up. Not having the device in front of me makes debugging nearly impossible, especially for an issue like this, which doesn't leave any trace.

You can find some informations about C-states (and cpuidle) in the first part of this article.
[Samsung Galaxy SL i9003] cukierkas:
Sorry, forgot to add reboot log. It appeared trying to load Xda app.

http://www.speedyshare.com/CPeMj/log-131219-204207.txt

Edit

One more log with Bt stalled at connected state. Hope you'll find something useful.

http://www.speedyshare.com/ksKk3/log-131220-165357.txt
[Samsung Galaxy SL i9003] The_GMAN:
I am back to Qwerty after using CM11 for quite a while now and well...I feel like I upgraded from laggy ICS to JB! Super smooth and fluid.

[MENTION=4349695]loSconosciuto[/MENTION] yeah the battery gauge chip works independently but in the end it has to estimate how much battery the ROM is using, and that's off when estimating JB ROMs.

[MENTION=4463931]Gondya bhau[/MENTION] kernel 2.6 does have really good standby time but my problem:

...is still there in JB even with kernel 2.6. So I think this problem is more ROM related.

EDIT: WOAH!! I can't believe what I just saw, GPU overclock! I don't know when you added GPU over clock but I cant believe I didn't see it. There's a very noticeable difference in UI fluidity and gaming. Thanks so much loSco. Now, how far can you go with the frequency? If you can just clock it to 300 if its stable enough. :D

Also: I just flashed superSu and this ROM is flying! fastest ROM I have used so far. I don't know if its only me but this superSu is amazing. Can others please try it out and give feedback.

For now am stickin with Qwerty until CM11 is fluid enough. It's Qwerty till this phone dies! :cowboy:
[Samsung Galaxy SL i9003] loSconosciuto:
I still can't see the problem. Did you try to see what happens restarting the framework when BT hangs?

su
restart #warning: everything will restart

I even told you about it when you complained about the lower overclock.

Anyway, when you set the SGX functional clock to 266MHz, you are basically changing the source clock (parent clock). The only suitable clock with an higher frequency that I found allows to set the frequency up to 266MHz.
[Samsung Galaxy SL i9003] loneagl:
##Noob question alert##

Can I keep Rom base the same and keep updating the kernel??

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
Su restart always helps. I'm guessing some modules or hw drivers are reloaded. Can you update and kernel 2, would try Bt connection with that one. But last time I was trying it, everything was fine.

By the way, congrats, rom sleep time best ever. And it's fluid and fast, even without zram (cpu at 800). Without locked browser I always have more than 100mb free:)

Noobish off topic : does smaller dpi gives more job to gpu? Because 220 is more suitable for me, but sometimes I have launcher reloads when returning from heavy app. That wasn't with 240. Launcher, browser and dialer are locked to memory. Or that simple shortage of ram?

Regards.
[Samsung Galaxy SL i9003] loneagl:
On the latest build can't increase the processor speed beyond 1000.The device immediately goes into boot loop.
[Samsung Galaxy SL i9003] ageback:
For me OC to 1150 is stable. Also I OC GPU freequence to 266 and it's stable, too.
[Samsung Galaxy SL i9003] loneagl:
Gpu overclock is awesome.really smooth you after that...processor overclock still gives bootloops, even till 1150Mhz
[Samsung Galaxy SL i9003] mehran 92:
I dont know why this happens but it seems battery life is shorter than previous kernels and battery charges faster
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Just saying...

Hi.

After testing it for some time, i was surprise about the performance of CM11 on i9003. Being a newer Android version, it has ALMOST the same performance of your current CM10 version, even without your dedication (at least in a direct way, we know your kernel changes are being applied to Dhirus' kernels and also the other way around) to improve that ROM performance.

I don't like CM11, mainly because the missing gtalk (hangouts is IMHO too heavy), the missing weather and calendar info on the lockscreen without unlocking more resource hunger features, unstability issues, etc. But I DO believe you should take a look to it, because maybe with your direct involvement, the ROM could be more stable, and maybe even faster than this one.

But, as always, is your call... Is your work, your will... and your time...

Regards.

A CM10 happy user.

Thank you. For everything.
[Samsung Galaxy SL i9003] loSconosciuto:
What really matters is the screen resolution, but it's also not so absurd that with a lower DPI more heavy object could be rendered at the same time making the UI heavier than normal. I've never tried to change the DPI, maybe once to try, so I could be wrong. However changing the DPI shouldn't change the memory requirements.

I guess I have to roll back to 1.1GHz.

I think it wasn't because of any of my changes. There are so many factors that could affects battery life, surely I have nothing to do with the faster charging. The kernel simply says "charge" "don't charge", the chip does everything on its own.

I've already decided that I'll use KitKat on a newer device. As long as this is my daily driver, I'll stick with CM10.

I don't think I'll keep using this device as daily driver for long, apps are become way too heavy for it, even the dumb ones, not to mention my 2 years old battery which needs to be continuosly charged (too late for a new battery :p).

Regarding the lockscreen, CyanogenMod should include cLock (formerly Chronus, which is now also a standalone app), which should be more advanced than what's included in CM10.
[Samsung Galaxy SL i9003] cukierkas:
I can send you a battery, got one rather fresh as a spare. Original. If you want of course.

Name the address. That would be a little Christmas present for your knowledge.

Regards.
[Samsung Galaxy SL i9003] loSconosciuto:
I forgot this... Just flash the old version directly. Most of the changes I did since I released the last version using the old kernel were kernel related, so the ROM shouldn't be outdated.

You'll probably need to wipe the settings of DeviceParts, everything else should work as intended.

You probably also have to flash navbar_fixes.zip to have the navbar enabled after a reboot if it was enabled before. Also, if you've never swapped your SD cards, you'll see the checkbox checked, even if SD cards are not swapped. This happens only the first time, toggle the option at least once and it will work as intended. I noticed an error in the code not so long ago and fixed it, but I didn't update that build.

Thanks, really, but I have to say no.

I'll need a new phone in a few weeks, the crappy battery is an execuse to get it sooner ;)
[Samsung Galaxy SL i9003] cukierkas:
What phone you're thinking of? Chinese miracle or nexus5? I gave myself a present for a Christmas Sony z1, this 9003 using for work routine.

About kernel 2. Was using it for a half of the day today. Bt works fine, battery holds better, especially at 2g. But couldn't stand the memory outage. Kernel 3 deals way better. Returned back. Besides, I'm never swaping the cards, so that is useless for me. Year back I had motherboard replaced for same internal memory problems. Afterwards never had any issues.
[Samsung Galaxy SL i9003] Darktitor:
Buy a Galaxy S4 Mini i9195 :p

Great phone !! I've got it from summer :D

Envoyé de mon eeepc en utilisant Tapatalk
[Samsung Galaxy SL i9003] cukierkas:
Merry Christmas everyone :)
[Samsung Galaxy SL i9003] The_GMAN:
Got a bunch of back-to-back reboots. They happened when turning on my device while plugged in. The device turns on and lock screen shows up then after a minute or two it suddenly reboots. Last ksmg attached.
[Samsung Galaxy SL i9003] mehran 92:
got couple of problems (bootloop,freeze,video playback,...)

all of them fixed by forcing a reboot

attaching logs
[Samsung Galaxy SL i9003] Drizzt_Kueh:
So sad :( Ok then.

As I wrote before, CM11 does include cLock, but it only works after activating a switch in the build.prop which also enables a lot of ram hunger features...
[Samsung Galaxy SL i9003] cukierkas:
What are those hungry features?
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Not a lot actually, but...

AFAIK: cLock screen, transparent panel bar, enable widget support on lockscreen

The option is config.low.ram in build.prop.
[Samsung Galaxy SL i9003] catarifrangente:
Is there any possibility of an update of the emojis into KK style?
[Samsung Galaxy SL i9003] loSconosciuto:
I haven't decided yet, I just have few ideas in mind, but I think I'll get something soon.

Oh right, I forgot that even lockscreen widgets are disabled.

AFAIK emojis are now part of KitKat. There are no images inside Mms.apk as it's done in previous versions of CyanogenMod and I have no intention to go through all the source code, find the new images (which probably are not separated files as in CM10), copy them, rename them and put them inside Mms.apk. If you want to do that on your own, emojis in CM10 are inside Mms.apk. You can replace them manually (apks are just zip files. Any time you modify the content of an apk it's better to zipalign it).

[MENTION=4655907]The_GMAN[/MENTION] and [MENTION=4915822]mehran 92[/MENTION]

I'll see the logs when I have some times, thanks for posting them.
[Samsung Galaxy SL i9003] loneagl:
Well I just mistakenly changed the processor speed to 1150MHz and voila - no boot loops..I can't imagine why as nothing was changed..
[Samsung Galaxy SL i9003] The_GMAN:
Getting lots of random reboots lately. last kmsgs attached...
[Samsung Galaxy SL i9003] cukierkas:
Hello there. Decided finally to try kk. So this weekend I'm on it. Gladly must say, that qwerty is most advanced and user friendly rom I've ever tried. Yes, kk has advantages, but I'm waiting for Monday to restore qwerty ASAP. I've left the backup on work computer :)

The best part of kk is advanced dialer and the clock app time selection. So Losco, if it's possible, please adopt it to qwerty. That's really handy.

For other users some thoughts. Exposed framework gives nearly all the settings we got on qwerty, so really recommending have this installed. In overall, kk is good, but to hood to have as a daily driver. I saw advantages of art only some, and they appeared only after day run. So my recommendations would be the same as Losco said once, kk for newer devices, the best on this phone is flyongb for gb lovers and qwerty for holo lovers.

Returning back to qwerty with a smile, like returning to mum's home ;)

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

Lowered overclock to 1.1GHz (http://sprunge.us/Bbia)

Misc changes to the memory management (not properly tested):

- http://sprunge.us/ChOB

- http://sprunge.us/IJRC

- http://sprunge.us/ZKBZ

I'm also having some issues with LED notifications with few apps lately, so here a fix (working with all the builds): liblights-fix.zip

Good to know, but I guess 1.1GHz would be better.

Regarding your question about updating the kernel only, I've just remembered that sometimes I include things like powerHAL in the zip which are not included in newer releases. Nothing important though, flashing the kernel only is fine as acuicultor said. EDIT: The last CM build I uploaded includes all these minor changes except for the auto-trim on boot, which was included in a previous kernel release.

Try not to overclock and see if it keeps happening.

Porting the time picker takes requires too much work and I haven't look at the dialer code, but I guess it's the same. I'm not even good with Java. When Google does changes to system apps, these changes depend on other framework changes which makes backporting hard.

[MENTION=4915822]mehran 92[/MENTION]

I can see you use a lot your device for multimedia stuff and I think your problems are due to that, I don't know exactly what's the problem though.

Anyway, I'm having some issues with my device lately, it becomes really slow sometimes (if I turn the screen off, it takes some times to turn it on again) and waiting or rebooting are the only solutions. I think it's what's happening to you.
[Samsung Galaxy SL i9003] The_GMAN:
I already tried that. In fact I've been using at 1Ghz max all this time but the reboots keep on happening. I'll try your latest kernel and if it doesn't help I'll have to reset it.
[Samsung Galaxy SL i9003] cukierkas:
Hello there, returned from kitkat lately. Glad to be with home rom again, even at 800, thanks losco for wonderful job ;)
[Samsung Galaxy SL i9003] eduCoder:
Today I had reboot while dialing a contact.

Last kmsg attached.

Also, sometimes when getting a call from one of my contacts, the name is not resolved until after 10 seconds or more.

Regards
[Samsung Galaxy SL i9003] cukierkas:
Try to clear cache and dalvic plus be shore to use last version.

Happy new year to all.

Regards.