yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] cukierkas:
Yes, proximity sometimes doesn't turn on the screen during talk time. Even with modificated phone.apk

and that happening when call is longer than 10min.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] AmmarGitham:
Is it a known bug?...The magnetic sensor shows wrong readings. Point in the wrong direction.
[Samsung Galaxy SL i9003] cukierkas:
Never tried, don't know :)

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
Finally some feedback.

I guess you are talking about this, which lowers the RAM reserved for the camera.

We are currently reserving 30MB of RAM for ION and I don't want to mess with it.

Regarding overclock I've already said that I couldn't even get a stable overclock at 1.2GHz with SmartReflex enabled, 1.1GHz only (which is not enabled in my kernels that I posted). I don't want to mess with that stuff, at least for now. Underclocking on the other hand doesn't seem so useful, our platform is optimized to run at 300MHz and adding another OPP would mean mess with SmartReflex, which is designed to work with 4 OPP.

I'm sorry, I wrote hot reboot in the first post, but I meant warm reboot. If the splashscreen is not shown, /proc/last_kmsg won't be there since it's generated after a warn reboot.

I won't use some compiler optimization flags in my next build and see if the ROM will become more stable. I noticed some rare runtime errors and some of the flags I'm using didn't really make any difference.

If you don't have /system/addons.d/*-gapps.sh because you didn't use the official gapps installer or for some other reason, gapps are not backed up during ROM upgrades.

The apk you had in /data most likely was the update of the Play Store, which still requires some things in /system (I guess)

It took some time for someone to notice it. I got rid of that more than a month ago, more or less when it was removed from CM10.1. Read Steve Kondik's comment here.

That could be hard for me with no BT headset, I'll see what I can find. Could you try to set as minimum CPU freq 600MHz and see if it keeps happening? (probably yes).

EDIT2: The reason why I'm asking this is that I remember that the old WiFi driver was requiring at least 600MHz while transferring data, but I'm not sure of this.

Mmm, I'll look into that again.

I wasn't aware of that and at first glance it seems you are right, the values reported seem to be wrong. I will look into that also.

EDIT: Weird, I had to reboot to do other things and now the sensor is working properly. It was reporting wrong values before that, like constant 200uT, but now, in the same room, I get a wider range of realistic values.

I've also noticed that this morning the battery was fully charged (it should stop at 96%). I don't know how that happened, I suspect it has to do with STATUS_CHARGE_TIMEOVER, I'll see this one also. I must have slept more than usual.
[Samsung Galaxy SL i9003] shaktishekhar:
I restored to the old update on old kernel i faced many issues wid d update and kernel 3.x like wile on call proxmity sensor dosnot turn on screen all d time bluetooth music keeps on breaking wile using wifi and wile downloding anything on wifi oe just using internet or wile any kind of sending reciving happining on the wifi the cpu usages gets higer like 90-100% cpu when Rx Tx 0 than cpu usages goes to 0 same as cm 10.1
[Samsung Galaxy SL i9003] AmmarGitham:
Ok, so another reboot. This time happened while I was reinstalling Whatsapp. Speaking of which, I lost all my conversations of Whatsapp in the night, I have no idea how, so to restore the messages I had to reinstall it. This time I have the last_kmsg file... Attached.
[Samsung Galaxy SL i9003] cukierkas:
Hello boys. Never had any reboots, everything is fluid. I'm even satisfied with Bluetooth. :)

Losco, funny battery icon in off mode when charging:) It's doesn't fills itself, bottom is not used :)

That's fine with me, its just an observation.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] abderrezak:
hi loScono , I just have a request to include Low Auto Brightness mod's on All next building
[Samsung Galaxy SL i9003] loSconosciuto:
I noticed that IO file operation have a big impact on the performance. Read operations makes the CPU stay at the max frequency, but there's impact in the performance, write operations on the other hand seems to slow down the device, a lot, more compared to the old kernel, at least in my opinion. Maybe the problem with WiFi is related to it.

The proximity sensor issue is a known problem and I mostly fixed it, read my previous posts. cukierkas said it still happens with very long calls though.

The Whatsapp thing is really weird.

The reboot happened because of KSM, but I'm not saying you should disable it.

I don't know why reboots are no more happening to me, but the first days I used this kernel I had some of them, they were all due to paging issues. I don't know what I'm doing different.

Try the last kernel I posted, after some days of use I can say it's stable and it has a lot of bug fixes.

It seems correct to me. I thought about using the same images of our stock ROMs, but there are few differences that don't make it possible.

The opensource charger use 8 images, and only 6 of them are used for the animation: 0%, 20%, 40%, 80%, 100%, while the closed source charger use 20 images (5% step) just for the battery. The reason behind this could be that unlike the old charger, the images are inside the boot.img and it's better to use the least amount of space, but that's a supposition.

Also, unlike the current charger, only the five dots below the battery were animated, the battery icon reflected the current percentage.

I don't want to modify the current charger to behave like that, I don't even care about it. I'm not sure weather to keep using the images you see now or revert back to the default ones ("Nexus style").

As reference:

Stock ROM

Open source (Nexus style)

Current (taken from the S2)

PS: I can't understand how my battery was fully charged, I know there's something not perfectly right in the code (I'll publish the changes I've already done), but still I can't understand how that happened. It has probably to do with the USB port of my device which is a bit loose and moving the cable can cause frequent disconnections/re-connections.

config_autoBrightnessLevels

config_autoBrightnessLcdBacklightValues

config_screenBrightnessDim

and I've been using this config for a year. Adding more levels is useless because of the way the light sensor is reporting the lux values (see this, I'm using "lux (old)").

There's no need to mod anything by the way: Settings > Display > Automatic backlight > Edit other levels. This option was available even in CM7.

The only problem is that the manual brightness can't be set below (20?) if I remember correctly, unless I changed it or unless you set as "Screen dim level" (same setting page) something lower than that.
[Samsung Galaxy SL i9003] cukierkas:
As for my opinion, everything is grant with current battery icon. Lets leave it like it is, that doesn't impact anything.

about low backlight. Use custom dim level, as I do.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] abderrezak:
flashing the last rom and kernel and i face wifi issus .

edit : try this and do not help me

To make WiFi work, you have to manually create that file.

Open terminal emulator and run:

Code:

su

mkdir -p /efs/imei/

echo -n 08:00:28:12:03:58 > /efs/imei/.nvmac.info

still no MAC .

edit 2 : i have my imei and i dont lose it ...
[Samsung Galaxy SL i9003] cukierkas:
one more thing. Guys, what would you suggest about google services? It works in background, keeps the os awake for more than a hour per day :eek:

Autosynch is off, background data aswell. All backups to google, etc are off.

And still, it keeps android awake and that affects the battery life.

What are you doing about it?

I can live without gapps, is it the only solution?

greenify allows to hypernate apps, but only, when its users, not system. Converted some google stuff to user apps, but that doesn't help much :(

for mean time I just frozed them all :)
[Samsung Galaxy SL i9003] xda_emanuel:
Have you tried to flash xs gapps? Btw android is optimized to run this process in background, for push notification etc, expecially for google service i think theres soomething weird because its impossibile that a base process will affect the battery so hardly. Take a look on xgapps, only 25 mb and report back .
[Samsung Galaxy SL i9003] loSconosciuto:
cm-10-20130909-UNOFFICIAL-galaxysl.zip

Updated sdram timing data

Fixed some recharging conditions in the fuelgauge driver

Switched to kernel 3.0.94 (the one I posted three days ago + the two fixes above)

Updated "Allow showing statusbar on top of fullscreen window." (I was still using the patchset 12)

Less aggressive compiler optimizations.

Flip to dismiss/snooze removed from DeskClock (it was just crashing)

Issues with the proximity sensor while in call mostly fixed

Minor changes here and there

[MENTION=4409632]ammar786[/MENTION] magnetic sensor bug confirmed. It happened again, I don't know the cause yet nor how to trig it.

You probably just replace your MAC address with the default one. Restore your /efs partition or just /efs/imei/.nvmac.info to restore your MAC address (it's not to fix WiFi, but to restore your MAC). If you don't have it (why would you?), you can live with the default MAC address.

In any case, what am I supposed to tell you? "i face wifi issus" means everything and nothing at the same time. (read this as: post logs, logcat, dmesg, whatever might be useful, or I won't even bother to reply).

It seems that if you prevent an app from holding partial wakelocks, there will be another to do that. The old kernel did a larger use of kernel wakelocks, making partial wakelocks not so necessary. In the end the difference between awake time and sleep time is the same.

EDIT: I'd say it's time to change the title of the thread.
[Samsung Galaxy SL i9003] cukierkas:
Bravo, rom seems more fluid than before :)

Even with browser locked:)

I'm using phone scheduler, to turn on/off bt, wifi, airplain mode, data. With latest kernel bt don't want to turn on certain time, need to to turn it on manually. That is not to bad, but I guess that this is not third app issue.

Alarm clock works as it should be, no issues detected. Even leveling bubble app works, wicked doesn't wanted to calibrate itself in last rom. Proximity turns on screen, but there wasn't long calls. Will inform later on.

By the way, about bt. After deep sleep, bt don't want to connect to headset automatically, I need to turn on the screen and connect it manually. After this, it connects automatically till long deep sleep period. That was the same in last rom, so I'm guessing, that bt issues are depending on kernel. Hope, some day headset could connect itself and after long night :)

Of course, I didn't tried to make smallest CPU value to 600 in sleep mode, but hope that is not needed to make bt always available. Losco, am I thinking right, that bt just can't wake up properly after long deep sleep? I have seen, that there is the app, witch makes bt always ready, but I'm guessing that this could impact battery life...

Regards :)

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
Try kernel-cm-10-20130910-galaxysl-signed.zip, I just uploaded it.

It's exactly the kernel used in my last build + this adapted + this.

Before updating the kernel, could you please listen to some music with your BT headset, turn the screen off and pause/play and see if it keeps streaming after that? I remember there were issues doing that ([MENTION=4588282]sgatechwork[/MENTION], right?) and the second commit I linked seems to address that issue.

I'm not sure this will fix the problem since I don't know exactly what happens with BT devices, but the code looks promising.

I'm already limiting the CPU freq to 600MHz when the screen is off through power HAL.

From Dhiru's Alpha 7 changelog:

"Bluetooth doesn't turn off when sleeping (However, Pairing and Transfer will require waking up the phone)"
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Hey, I'm back from Dhiru's cm10.1. This is a lot faster and smoother.

Last night, I suffered a SOD, when the phone was plugged to the charger and I was sleeping. I'm attaching the last_kmsg.

Edit:I couldn't attach it before, but i get two at the price of one. Both seem to be different.
[Samsung Galaxy SL i9003] cukierkas:
Not using bt earphones to listen to the music, just simple Nokia bh -218 for talking, so really can't test the music streaming, it just doesn't support it :)

Will update bt connection later on, having somekind problems downloading the kernel.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] AmmarGitham:
I'm a very frequent user of Google Maps on my phone being in a new city. The magnetic sensor points me in the right direction, hoping to see it fixed soon. :)
[Samsung Galaxy SL i9003] xda_emanuel:
Im currently on this rom, i ve bought a new battery yesterday and i noticed an improvement of battery life here, but why everytime i got a reboot the battery drop like 30% or more. Thats happened on gingerbread also, i cant understand.why. i bought this new battery for this, because im working outside all day and i cant recharge the phone 3 time per day. It is pretty annoying and it makes me angry . Everybody who can help me is really appreciated. Thanks advance
[Samsung Galaxy SL i9003] cukierkas:
gone % are returned in some time, usualy in sleep mode, check it and you'll notice it.

yes, there are some drops, but not so bad as on samsung rom :)

yet, didn't tried xgapps, managed google services frosting them :(
[Samsung Galaxy SL i9003] xda_emanuel:
Regarding xgapps im currently using them, got no problem at all. The phone is smooth and ram friendly. I suggest you to try install xgapps 4.1.2
[Samsung Galaxy SL i9003] resetez:
Hi, is possible to provide a link for xgaps? thx in advance
[Samsung Galaxy SL i9003] Gondya bhau:
http://xdaforums.com/showthread.php?t=2240652
[Samsung Galaxy SL i9003] loSconosciuto:
I found that the values reported by the magnetic sensor are the same with the old kernel and that abnormal magnetic fields are sometimes detected with it as well, so it's not an issue specific of the kernel 3.0.

Normally my device detects 60uT and I'm quite sure it had always been like this (I spent some time checking the values while porting the opensource sensor HAL and I remember how they were), which is an high field, but at least it changes while moving the device and the scale goes up to 200uT. I could modify the sensor HAL to get some more realistic values, maybe doing a simple side by side comparison with another device, but what matters are the intensity variations. I guess no one here uses his phone to know how strong a magnetic field is.

Rarely though the field detected is very strong and the scale is fully used (200uT), so there are some issues detecting intensity variations, but it happens even with the old kernel.

The problem with Maps is another, the cause is the orientation driver, which was updated by Dhiru but it's probably not compatible with our sensor HAL/blob. I restored the old driver, added this fix (I was already aware of that fix since I ported the sensor HAL from Aries) and the orientation sensor is working again.

I uploaded a zip named kernel-cm-10-20130910-galaxysl-orientation-signed.zip.

sod_lk_log.txt: I can see that the device tried to sleep (last part of the log):

PM: Syncing filesystems ... done.
PM: Preparing system for mem sleep

but after those there isn't the usual

PM: Entering mem sleep
Suspending console(s) (use no_console_suspend to debug)

and the device kept doing everything, like checking the current state of the battery.

It's like as if the device was both suspended and awake. The same thing happened to me a few times, but it's no longer happening.

I'm sure that most of the things were working, like sounds, LEDs etc. Probably you could have even called it and the device would have ringed.

I still don't know why it happens, I even don't know why it's no longer happening to me.

EDIT: keep posting logs when these SODs happen, maybe I'll notice something recurrent and I'll be able to track down the issue.

sod2_lk_log.txt: SOD? That looks like the "usual" reboot, caused by a NULL pointer.

Read this. Instead of rebooting, try to power off and then power on the device, maybe waiting a little bit before turning it back on. I don't know if it makes any difference, but it's the only thing you can do.
[Samsung Galaxy SL i9003] Drizzt_Kueh:
Thanks!

As you command! ;)

I saw the same, but I forced the reboot holding the power button for some seconds (maybe at the same time as the phone decided to reboot itself?).

By the way, are there any suspects about the responsable(s) about that "usual" reboots? What can be generating the Null pointer?
[Samsung Galaxy SL i9003] cukierkas:
Hi losco, how are you? Bluetooth turns off as scheduled properly, but doesn't turn on. Using phone schedule for ithttps://play.google.com/store/apps/details?id=com.antonc.phone_schedule.

In other hand, it connects to headset faster, but in order to make the connection, I need to turn on the screen, as it said in dhiru's post. When screen is on, connection established really fast automatically. Using 9-10 kernel.

So, I'm thinking to keep bt all day long.

Regards.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] cukierkas:
Phone schedulers UI.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] RonnYap:
[MENTION=4349695]loSconosciuto[/MENTION]

For me everything work fine..Just video recording(5 minutes duration)..After recording and play video i found sound audio mute(3 to 5 sec) and sound again(6 time audio no sound)..

Sorry my bad english..Dont know how to explain..
[Samsung Galaxy SL i9003] xda_emanuel:
Hey guys i just noticed a weird thing. When i go on options , performance, the max cpu is 600 by default. Thats ok but when i set cpu max 1000 and i sign remember on boot after a while it come back to 600 mhz without i didnt do nothing. Is that a special feature of this rom or a bug? Thanks for everyone
[Samsung Galaxy SL i9003] loSconosciuto:
Kernel oops are not always easy to debug and currently I don't know the cause of the reboots. I will try to debug them, they happen rarely to me.

I tried the app and it's turning bluetooth on, I don't know what we are doing differently.

In your opinion, is pairing faster with this kernel or it's just as fast as before? You could try to flash a previous kernel and do some tests. Not that I need it, I'm just curious.

Give me the exact steps to replicate the problem or some logs, because I tried few things and audio always worked.

Ops, bug. I will fix it EDIT: and this also.
[Samsung Galaxy SL i9003] AmmarGitham:
Hi,

So another reboot. last_kmsg is here. Hope it helps.
[Samsung Galaxy SL i9003] cukierkas:
Hello. I cleared the cache, dalvic, reinstalled the scheduler app- that doesn't helps. I hope I know why bt turns on for you - it still active in 1 hour period approximately. Try to set the scheduler to turn it on in the morning.

About kernel pairing speed. Its not so lighting fact difference, but difference is not more than two seconds. And still, bt speach quality is with noises, but really better than with kernel 2.

Morning edit: bt turned on automatically, so, guessing that will stay. Great job! Have nothing to add, except crazy gapps wakelocks :) More than hour active device with autosync turned off, and all gapps services running (before I froze them, now all of them running without my intervention. Even with xsgapps, xda Manuel suggested me). Thinking to try your next release without gapps, just to see how battery life will stay. As for now, 3hrs of screen time with rather fresh battery (3months) comparing with gb, 4-5hrs.

Sent from my GT-I9003
[Samsung Galaxy SL i9003] loSconosciuto:
Camera HAL fix for third party apps: libcamera-fix.zip. I tried only Skype and it's working, laggy as always, but it works.

Or you rebooted the device and then took the log or some apps or something else requested a reboot. That's a wanted and normal reboot.

To get rid of gapps, delete /system/addon.d/70-gapps.sh and then update the ROM. You then have to manually delete the updates you installed through the Play store and the update of the Play store.

Anyway, don't be obsessed with partial wakelocks.

I assume you are using BBS.

The toal time of partial wakelocks is increased even if they are held when the screen is on adn some other partial wakelocks are already preventing the suspension. I'm saying this because the sum of the total time of all the partial wakelocks is higher than the awake time and sometimes the total time of just a partial wakelock is higher than the difference "screen on time - awake time", so it's the only thing that makes sense.

Partial wakelocks held when the screen is on or when another partial wakelock is held don't really matter since the device is obviously awake.

I think that the partial wakelocks tab is to identify which app is increasing the use of PowerManagerService, which is the placeholder for all the partial wakelocks. Surely PowerManagerService is keeping the device awake a lot, but that's required to have a functional device. Previously we had the omnipresent samsung-battery which lowered the use of all the other kernel wakelocks (kernel wakelocks are considered only when they are preventing the suspension and if there's another wakelock active, they are not considered. For example svent is a 6 seconds long wakelock, but you can see that the total time is far less than 6 seconds*count). That's to say that probably Google Apps are not draining the battery so much as you think. And as I said, if you manage to get rid of it, you'll probably have something else to keep the device awake. The only way to get rid of partial wakelocks is to use a smartphone like a feature phone.

Take under control the difference between awake time and screen on time. That's one of the thing that really matters, unless you do several things while the screen is off such as listening to music.

Battery life is better with stock ROMs, I know that since the first time I flashed CyanogenMod (maybe things changed lately and obviously it depends on how you use your phone, so there's no need to post screenshots of your battery life to prove I'm wrong) and I'm okay with that. That doesn't mean I'm not interested in improving battery life, I wouldn't have spent weeks trying to get the off-mode working otherwise.
[Samsung Galaxy SL i9003] AmmarGitham:
That's odd. I didn't request a reboot. Hmmm, odd.
[Samsung Galaxy SL i9003] cukierkas:
Speaking frankly, yes, I'm little angry with wakeloks. Take a look to screenshots. Device is more than hour active in screen off mode. That is 4% per hour when in idle time it should be about 1%. Comparing with gb at this time. And yes, that's the price of custom. Or I'm looking for a black cat in a dark room?

Yes, I'm using bbs.

1st screenshot shows the thing you wanted to fix?

Sent from my GT-I9003