yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] Gondya bhau:
rebooted on unlocking the screen....rebooted from cyanogenmod loading sign
[Samsung Galaxy SL i9003] cukierkas:
Hello there. To say the truth, have nothing bad to say. No reboots, no sods, bt pairs smooth, no signal drops, everything runs fast and fluid. A lot wakelocks by Android system during night in flight mode, but battery level drops not so visible, maybe 5% during night. Not to good, but no too bad in overall.

Good job losco, happy to use your creation.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] resetez:
Hi guys, yours orientation sensors are working fine on actual version?

...this using for App Compass / Google map / Google Sky Map ...
[Samsung Galaxy SL i9003] cukierkas:
not using any of it, so can't confirm.
[Samsung Galaxy SL i9003] ndttung8487:
our device didn't have gyro sensor so i think it won't accurate.
[Samsung Galaxy SL i9003] rockybb96:
Can't flash the kernel for 3.0, downloaded

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

placed in internal sd card, tried to flash and it says flash aborted :/

running on 2.3.6 DDLE1

Rom- FLYonGB By LoLaTiOn
[Samsung Galaxy SL i9003] ndttung8487:
you have to flash right kernel. kernel 3.0 use for cm10 so you have to stay on cm10.
[Samsung Galaxy SL i9003] rockybb96:
oh so kernel 3.0 doesnt work with stock ? O.o
[Samsung Galaxy SL i9003] Gondya bhau:
keep flashing like this and you are gonna brick your phone real soon......
[Samsung Galaxy SL i9003] ndttung8487:
yes. you should read all Losco's first topic very carefully before do anything related to rom on your device if you don't want to mess it up
[Samsung Galaxy SL i9003] barrubba:
Hi, i'm on Lola LIKE-S4 2.0 version..

Is better 2.3.or 3 kernel? in terms of stability, battery, reactivity.

in the instruction for 10.1/10.2 i don't see any cache and dalvik formatting step. Is normal?

20130929 is better only in terms of battery drain?

thanks
[Samsung Galaxy SL i9003] ndttung8487:
my opinion kernel 3.0 is better than 2.0 with many improvements. wipe cache or dalvik make device run smoother on new rom,so you should do it before flashing any new rom. i use cm10 from Losco for daily driver. sometimes i change to cm 10.2 for experience. but which rom is better, i can't answer because it depends on how you use your phone.so take a try to all roms and decide for yourself. ofcourse latest rom not always the best but it brings lots of improvements.
[Samsung Galaxy SL i9003] barrubba:
to install YourZgapps XS:

After installing your favorite ROM, follow the steps below to install YourZgapps...

1) Copy YourZgapps zip to sdcard

2) Boot into recovery

3) Wipe cache/dalvik

4) Flash YourZgapps zip from sdcard*

5) Wipe cache/dalvik

6) Reboot system and enjoy!

CyanogenMod 10.1/10.2:

Download the zip of the ROM and save it into the external SD or the internal memory

Reboot to recovery

Flash the downloaded zip

optional: Flash Google Apps

optional: Flash mobiledata_off.zip if you want mobile data off during the first setup

Wipe data/factory reset

Reboot

?? which is the right step way to install gapps? after orbefore first reboot?

thks
[Samsung Galaxy SL i9003] Darktitor:
Install it at the same moment as the custom rom you want :D

Envoyé depuis mon GT-I9195 avec Tapatalk
[Samsung Galaxy SL i9003] ndttung8487:
in conclusion:

1. wipe data/cache/dalvik/(system too if you want).

2. flash the rom as your choice

3. flash gapps.

4. wipe dalvik cache

5. reboot and start using!!!
[Samsung Galaxy SL i9003] ASMI1:
It is recommended to reboot recovery between step 2 and 3 to prevent home button from not working sometimes.
[Samsung Galaxy SL i9003] cukierkas:
Hello there, how are you?

Got one reboot after screen unlocking. Before that phone was extremely laggy.

http://www.speedyshare.com/XtVJT/kmsg.txt

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] barrubba:
performance setting

in performance setting which is the best?

on demand 300/1000 ROW?

and for ram management? zram/clean resources/ksm/hidden app ??

16 bit/scrolling cache ??

thanks
[Samsung Galaxy SL i9003] loSconosciuto:
So it wasn't a real reboot and so last_kmsg is not useful. logcat + dmesg is what I need for these situations. Thanks anyway. (I checked the log anyway and it's fine)

As I said, there are a lot of partial wakelocks because there are almost no kernel wakelocks. I wrote a kernel module once to see if adding a dummy wakelock would have got rid of the very frequent "awake" bars in the battery history graph and I was right. That also decreased the used of partial wakelocks, as obvious. What I really didn't (and still don't) understand is why the time spent awake because of a kernel wakelock is not "logged" in the graph, unlike the time spent awake because of a partial wakelock.

If you want to try it: keep_me_awake.zip (module + init script to load it + modified DeviceParts to tweak it).

Try the default duration set by DeviceParts, it should be 600ms.

I fixed that long ago.

Actually, all of what I post here is intended for (my) CM10 only, that shouldn't be surprising.

The log is fine. I'd like to see a logcat when it happens, but you need to get that (if adb is working, which is what I think happens) while the device is not working..

EDIT: Sorry, I opened the wrong file. SOD or reboot? According to the log the device was rebooted after an error occurred. I think this happened to me, but only once (the log is pretty specific about what happened).

Thanks for the log.

Keep trying the options until you find something you like. There are no best combinations.

The only thing I can say is that I mainly used and optimized ondemand, never used the other CPU governors.

Anyway, after days of use I can say that that I was right about the reboots and my last kernels fixed the problem. All the devices should work for days with no reboots, unlike before when only few could do that.

PS: there are no errors in the steps to flash the ROM, if you follow them, you'll be fine.
[Samsung Galaxy SL i9003] ndttung8487:
Ok Losco, now my phone run very smooth. I'm using your latest rom and have no reboots or sod at all, but one question: sometimes my app unable to run so i have to kill it manually, reopen, but sometimes i have to reboot the phone. how can i take log for you?

Those are: Youtube, MxPlayer, Skype.
[Samsung Galaxy SL i9003] Darktitor:
Hi [MENTION=2677572]Loscon[/MENTION]oscuito:)

My brother will buy a new battery replacement for his Galaxy SL :) It's an Anker battery with 1800mah of capacity !!

Does it need any modification in the rom to change the stock capacity from 1600 to 1800mah ?

Thanks in advance

Sincerly yours

Darktitor

Envoyé depuis mon GT-I9195 avec Tapatalk
[Samsung Galaxy SL i9003] cukierkas:
If its a Chinese miracle, be sure to check the real capacity. And don't be upset if you'll find 1300 or even less.

Losco, that was a hot reboot if I naming it right. Jump to cm logo without Sammy's startup and kernel's running line.

By the way, about two way call recording feature without loudspeaker, is it posible to have it on kernel3? Or you don't want to bother yourself with this feature? I remember we had talked about earlier, but still, this feature is needed and not forgotten.

Regards

Sent from my GT-I9003
[Samsung Galaxy SL i9003] ndttung8487:
I face with one SOD, I just can collect kmsg log here
[Samsung Galaxy SL i9003] barrubba:
Im on 20130929,the problem is that when I receive a call, and answers, the default speaker is internal and not bt. So I must select it from combo box. Why

Inviato dal mio GT-I9003 con Tapatalk now Free
[Samsung Galaxy SL i9003] cukierkas:
Want say one more thank-you for the magic. Latest rom version, zram 10%, hidden apps 6, 3 permanent apps in background, 2 of them are browser and exchange mail app :)

No oc, phone is fast and responsible.

Fantastic, especially having in mind outdated hardware.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
About wakelocks, yep, it look really weird :mad:

Will try your zip later on.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
device parts

default one was 700ms, reduced to 500ms.

results in the morning :)

Evening edit, another reboot

http://www.speedyshare.com/g5hhd/kmsg2.txt

Take care
[Samsung Galaxy SL i9003] mehran 92:
hi

im using 20131001 Rom for a week and its very smooth but i found a weird problem

sometimes cpu goes to 1000MHz and stays in that! even when i change the max cpu frequency to lower values it still stays like that and the only solution is to reboot.

i think the reason of battery drop during night is this.by the way i think without this bug my battery backup is much better than kernel 2.6.35

thanks
[Samsung Galaxy SL i9003] ndttung8487:
Hi Losco, i move back to 20130929 to use now as i have to travel some days. Because the rom 20130929 is the most stable with speed,battery and not have any sod or reboot. Maybe my device accept that rom and suitable with that. But ofcourse i'll always try your newest rom. Thank you so much for supporting from you. [MENTION=2606021]cukierkas[/MENTION]: can i ask you question. Did you face any issue on 20130929? thanks alot!
[Samsung Galaxy SL i9003] cukierkas:
No, it was stable as rock. With newest I had 4 reboots in 3 or 5 days. Other than that, everything is grant.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
logcat

No changes required.

I must have read it wrong, I thought you wrote SOD. Anyway, I saw that some weird things related to the GPU driver were happening, but the reboot was caused by something else.

Call recording could require some work which I'd prefer to avoid.

I found that there's a function in libsecril-client.so (a proprietary lib we use) that is probably meant for that. Its name is "SetCallRecord" and I found the same string in a stock libaudio.so. The bad thing is that there's no source code, so it's pretty hard to know exactly what that function does and how to use it. It's maybe possible to record calls even without the help of RIL, but honestly I'd prefer not to do it since it could require a lot of work and I'm sure I'll never record a call.

Clean as always, no errors. I'd like to see a logcat.

Did you excluded the kernel as cause of the SODs? Did they happen with kernel-cm-10-20131004-galaxysl-signed.zip and 20130929?

I've never used BT for anything, so I don't know why it happens, if it's normal etc... Maybe someone using BT will know the answer.

But yet it looks like there's almost no power consumption. Things didn't change for me when I used "keep_me_awake", the "awake" bars disappeared, less partial wakelocks were used, but the consumption remained the same.

FYI the awake time due to the wakelock will be far more less than 500ms. You can see the max time from the dmesg or BBS. With 700ms my device is kept awake for around 77ms because of the wakelock.

That's weird, it has never happened to me. Provide me some logs, dmesg and logcat, the next time it happens.
[Samsung Galaxy SL i9003] cukierkas:
I must to apologise, I was talking about 0926 release. I didn't tried that version just because full screen pull notifications were removed.

Losco, you are right. As for my observations, system wakelocks were reduced drastically. Awake bar is more cleaner now. :)

Thanks for clearing situation about call recording. And yes, we can use a third app, but it uses only loudspeaker or records only one side.

what about second reboot kmsg. Have you founded smth useful?

Sent from my GT-I9003
[Samsung Galaxy SL i9003] sh7adeh:
4 october version stable as rock thanks losco and dhiru

your work is appreciated
[Samsung Galaxy SL i9003] cukierkas:
Little report of keep-awake zip. Android wakelocks reduced dramatically, picture shows a beautiful usage, no bars as before. Battery backup is worse or I talk much, -35% with 46 min bt headset talk time and 1h20min of screen time. Wakelock time is set to 500ms, as we talked before, screenshots attached. By the way, yesterday was interesting situation, ril crashed after short voice call, call was hanged for some minutes with unknown id, nor callers name was shown properly during call time. Wifi was on during call. Restarted, everything grant afterwards. Sadly, no log taked.

Regards

Sent from my GT-I9003
[Samsung Galaxy SL i9003] Gondya bhau:
i faced a soft reboot (like last time)....this time though on connecting the charger...attached a log....hope its the right one this time :p:p

and with keep me awake, awake bars do dissapear.....battery drain was 3% overnight compared to 5% before flash....will check again tonight and confirm if there has been any improvement.....
[Samsung Galaxy SL i9003] loSconosciuto:
cm-10-20131010-UNOFFICIAL-galaxysl.zip

I just included Dhiru's fix for BT pairing while in deep sleep, re-enabled the touchscreen threshold controls so that you can adjust the sensitivity of the screen from DeviceParts and fix a couple of things. No big changes then, so I uploaded a flashable kernel (kernel-cm-10-20131010-galaxysl-signed.zip) for those of you who don't want to download the entire build.

I've also updated keep_me_awake.zip (more info here) so that the module and the script to load it is preserved during ROM upgrades. Delete "/system/addon.d/90-keep_me_awake.sh" and upgrade to get rid of it or delete "/system/etc/init.d/keep_me_awake" to disable it without upgrading or set the duration of the wakelock to 0ms from DeviceParts. DeviceParts is removed from the zip, it's included in my last build (the option appears only if the module is loaded).

[MENTION=2606021]cukierkas[/MENTION]

I read your log, saw what happened, but let's say it's too generic to exactly know what happened, at least with no in-depth analysis.

[MENTION=4463931]Gondya bhau[/MENTION]

There are all the kind of logs in there, unfortunately they are not complete and the reason for the restart is not logged (I can see part of the "service '**' died", so few lines more would have been enough). See if there's an option in the app to dump the entire logs.

I have a request. Could anyone try to transfer anything with MTP to the external SD (when memories are not swapped) and see from the device if it's copied there or inside the internal memory? I made UMS default because it's not working properly for me, but I don't know if it's a common issue. I tried to understand the cause, but I couldn't find anything.
[Samsung Galaxy SL i9003] cukierkas:
about mtp. upgraded just kernel, deleted keepmeawake from init-d, before that made wakelock duration to 0ms

I do have problems even opening the phone. screenshots atached.

all drivers were installed correctly, windows do find the phone properly. but can get in to it or get anything from it :)

windows 7 prof, 32bit

edit, picture exporting working :)

regards
[Samsung Galaxy SL i9003] mehran 92:
today i faced my first SOD.im on kernel 20131004 with 20131001 build

on kernel 20131001 i never faced a SOD or random reboot.

btw here it is my last_kmsg hope it is useful
[Samsung Galaxy SL i9003] barrubba:
Battery life is OK but I see in deep sleep, during night a sort of usage (in battery tab), but I don't know what is the process..

Inviato dal mio GT-I9003 con Tapatalk now Free
[Samsung Galaxy SL i9003] barrubba:
Why @1.2 is unstable? Reboot loop!

Inviato dal mio GT-I9003 con Tapatalk now Free
[Samsung Galaxy SL i9003] acuicultor:
Whaaaat??????
[Samsung Galaxy SL i9003] barrubba:
Is not stable setting frequency CPU at 1200. Phone reboot continuously

Inviato dal mio GT-I9003 con Tapatalk now Free
[Samsung Galaxy SL i9003] ndttung8487:
so simple solution: you shouldn't oc your device!
[Samsung Galaxy SL i9003] loSconosciuto:
Thanks for testing. I tried MTP again and I found it's working correctly and that my problem wasn't the device, at least not only.

That would be the first SOD with something logged. Unfortunately it's not helpful. Normally that would have lead to a reboot, but something went wrong. There are no informations at all about what caused the crash though.

I'd say it's just a coincidence that it happened using the last build.

Ok, this is the last time I repeat this and I'll link this to the first post.

It has been always like this. I had the same kind of activity when I once drastically reduced the use of the "samsung-battery" wakelock of the old battery driver (thread link). I don't know why this happens, I think there's a bug somewhere. Or the time spent awake because of a kernel wakelock is not considered in the same way of the time spent awake because of a partial wakelock (when I hold a kernel wakelock I often don't see any awake bar in the stats. If you hold a kernel wakelock, I guess partial wakelocks are not taken in account), resulting in an apparent less awake time, or some errors are made while collecting stats when the device stays awake for a very short amount of time, resulting in an apparent more awake time (even if the device is awake, there's almost no power consumption, at least according to the stats).

I even wrote a simple kernel module which simulates the behaviour of the old battery driver, confirming what I've just wrote. (post link).

Don't compare the stats with Android 4.2+, since things obviously changed. In Android 4.1 the "Screen on" time is a subgroup of the "Awake" time, this is obvious looking at the stats. In Android 4.2+ however this is not true, the "Awake" bars in the graph are quite rare and for each "Screen on" bar there isn't the corresponding "Awake" bar.

In any case, battery stats are just a rough approximation of the consumption. Our power_profile.xml is not even customized, Samsung simply took the one of the Nexus S. This leads to even more approximated stats.

Never said it was stable for every device (more info here). Better add this info to the first post.

About the last kernel update:

the touchscreen sensitivity controls are still broken, I got a reboot because of them, exactly when DeviceParts tried to restore the saved value right after a reboot. I'll remove them again, I honestly don't care about them. I re-added thinking that the problem was another, but apparentely it's not.
[Samsung Galaxy SL i9003] ndttung8487:
Hi Losco, i can confirm that mostly reboot or sod comes from my battery. i didn't know why is that. but i buy a new original samsung sl battery, and do a fresh install on newest rom, it keeps stable as rock till now. more than 3days without any reboot,sod... i try flash again and using my high capacity battery and see many sods,reboot even i ask dealer change me a new one. its name is SCUD. . so i guess i will keep using the original one. thanks alot for your hard work. tomorrow i will bring my phone to my friend whom work for samsung care center to write back my imei. i still using 0049xx.
[Samsung Galaxy SL i9003] sh7adeh:
No its not related with ur battery . I have twice sod every day with latest kernel. Phone have a sod while sleeping and sometimes phone freezes and touch screen stops .. it usually happened after restarting mobile and use it immediately after bootanimation .. sometimes device become too slow although im using greenify app .. i gavent faced mtp problem after installing suitable driver for windows 8

About battery condumption sometimes its pretened to be good as before on last kernel based on 2.6.6 qwerty kernel but with better performance sure but rarely mobile consume battery when sleeping more than 2-3 % per hour with no use at all

I tried to use bluetooth with sending files to pc but always failed dont know why but i check pc device and dont see any problem // will try it with another mobile maybe something broken in windows .

I want to thank you losco for ur great work and ofcourse cant forget the big magician dhiru for his big efforts
[Samsung Galaxy SL i9003] cukierkas:
had problems today with my headset, didn't wanted to transfer voice from phone to itself.

repairing helped.
[Samsung Galaxy SL i9003] zhiyong:
get a sod while a SMS Received

last_kmsg attachView attachment 2329052
[Samsung Galaxy SL i9003] loSconosciuto:
Log is fine, as always.

Can anyone give me the content of /data/tombstones and /data/anr/traces.txt after a SOD happened or preferibely a logcat taken while the device is not responding (as I said, I suspect is a semi-SOD with almost everything working, including adb)?

I'm not experiencing SODs, so I can't do much with no informations at all.
[Samsung Galaxy SL i9003] loSconosciuto:
kernel-cm-10-20131017-galaxysl-signed.zip

Since SODs are pretty random and I'd like to see a logcat when it happens (as I said a few times, I suspect it's not a real SOD), I made a kernel which grabs it when both the volume keys are pressed. Let's see if in this way I'll receive anything. It's a really ugly "hack", but it seems to be the only way to get something.

EDIT: it shouldn't work while the device is in deep sleep. Try to press some buttons until the LEDs blink while pressing both the volume keys. If LEDs blink, the log was taken and you can reboot. Try to plug the device to a computer and then press both the volume keys if nothing works.

Without experiencing any of these SOD I can't say if this "hack" is actually working or not.

EDIT2: I uploaded another version of the kernel, which does the same thing, but you can also grab logs with "home button + volume down", in case the volume keys can't wake up the device (I didn't check this).

If the device is not responding, press both the volume keys. A new file will be created (/data/logs_kernel/log-MonthDay-Time.txt) and LEDs should blink. If they do blink, it means that the device is working.

Other than that, it's now possible to set the voltage of OPP5 from DeviceParts. It will be set on every reboot (DeviceParts sets a persistent prop which is read by an init service to set the desidered voltage before OPP5 is enabled). This is mainly for those who couldn't get a stable device at 1.2GHz.

This also means there are more chances to do something wrong and get stuck in a bootloop if you didn't test the changes well enough. That's why I made a simple flashable zip (disable_opp5.zip) which un-ticks the "Set on boot" option of the settings. This obviously won't work in case you use a third party app to set the max CPU frequency.

As I said, when you have a reboot because of OC, in your /proc/last_kmsg you should see:

Internal error: Oops - undefined instruction: 0 [#1] PREEMPT SMP

OC is not the only thing that could cause that, but it's very unlike to have it for other reasons as of now.

The patches are on GDrive.
[Samsung Galaxy SL i9003] cukierkas:
Hello. To say the truth, never had any sods with last kernel. Even memory leaks didn't appeared as I talked before with 10 hidden apps in background. Rom is fluid and really usable. :)

Regards, happy user.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] sh7adeh:
+1
[Samsung Galaxy SL i9003] ASMI1:
+1

Hey Losco you are the best:thumbup:
[Samsung Galaxy SL i9003] ndttung8487:
What kernel did you use? What stock program did you freeze/delete? Thank you.
[Samsung Galaxy SL i9003] Gondya bhau:
hope this gives some info.....reboot happened immediately (say 2 mins) after flashing the lastest kernel and rebooting.....i took a log at the end of the horizontal blue loading bar.....before cm animation....

EDIT:

added another one
[Samsung Galaxy SL i9003] cukierkas:
Hello, using 1004 rom and 1010 kernel. Hidden apps 10, zram 10%, frozen apps in screenshot. Dialer and browser locked in memory, exchange app with service as well. Using as daily rom for work related routine.

Regards.

Sent from my GT-I9003