[ALPHA][ROM][4.2.2] CyanogenMod 10.1 for Samsung Galaxy SL - Alpha 9

[chongns]

No offence taken.. but I want to know if I have followed the correct method?

And Ya sure, I'll try updating adb...

Sent from my fingers to your face..!

if you use -d option, you may not get enough log

-v time will include timestamps in the logcats
-d will export the complete log.

If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.

edit:
@kishankpadiyar

ok, found your mistake, you should turn screen on and off , than take the log. :fingers-crossed:

 

[Ottonet]

Bluetooth and auto-brightness review

Hi all,

Tested this rom a little more, with some attention to auto brightness feature and bluetooth used in a car handsfree environment.

Auto brightness seems to be working strangely.
If tested it off plug and in preview mode, it never gives the lower and the upper limit readings.
I.e.: in a totally dark room, at night, the lower value given is around 145-148 lux.
In full daylight, the upper value is around 640-650 lux.
Don't know Anything about light, lighting and illumination, but is sounds weird to me, given that the system setting range from 7 (or is it 9? Anyway...) to 2200+ lux.
Sensitivity is good enough, though. Maybe some conversion miscalculation is undergoing here, but I do not consider this as an awful problem.

Some days ago I wrote that Bt connects promptly to my car's handsfree device. I am not so sure anymore, I had some failures, here, and now I have to determin to which extension is my fault, and wether ther rom fails or not in connecting always at tne first strike.
However, it is not difficult to make it work, if not at once, with a couple of trials.
The sound quality is variable. Has been good in some cases, very, very bad in others.
What bothered me a bit is that if I close the conversation, the phone remains hooked to the handsfree device, if it is the person I am talking with to hang up, then the connection is lost, and BT must be swiched off and on again to get connected.

------ added after some more tests -----

When you connect to an handsfree device for the first time Androirds warn you saying that "Android whants to be given the permission of reading your phone contacts". A chackmarks allows not to be asked anymore.
Well, if the "do not ask anymore" checkmark is not checked, the phone is unable to gain the connection at the end of a call (Both if it is terminated by the caller or by the receiver)
If the "do not ask anymore" checkmark IS checked, the the connection is preserved after a call.
In Italy it is forbidden to make phone calls unless an handsfree device is used.
Now I can confirm with full certainty that the feature is FULLY FUNCTIONAL and can be used with the only problem of VERY bad sound quality.


What are your experiences with these features?

 

[RockIndia]

Live Wallpaper Issue

hii after flashing a6 i was unable to play any videos and another thing is my touch was being hanged than i should do restart or leave the phone for few minutes
again touch is working
sorry for bad english

@navinash.avi Same happen to me when i use Live Wallpaper.

Did you faced the same while using the live wallpaper ?

I will try to get log for the same and will post it.

 

[chung1213]

Is it only me? The phone still stops charging when it reached 100%

Sent from my GT-I9003 using xda app-developers app

 

[navinash.avi]

@navinash.avi Same happen to me when i use Live Wallpaper.

Did you faced the same while using the live wallpaper ?

I will try to get log for the same and will post it.

no live wallapaper but the touch hanged a while

 

[christopher2018]

Blacklight logcat

My Logcat procedure:

1. type in command in terminal:

logcat -v time -f /sdcard/logcat.txt

2. Push the lock button to turn the screen off.

3. After a few seconds, blacklight comes up.

4. After about 15 seconds, push the home button and unlock the phone.

5. ^C to terminate the logcat command

Here are two logcat extracts.

Please look into this issue, dhiru
Thank you for your hard work!

 

[loSconosciuto]

I already have plenty of logs (thanks to @poluyan_stas). I think dmesg is more appropriate for this, but it doesn't show anything useful. I had to add debug lines by myself, but still I couldn't find anything. All I know is that the backlight is automatically turned on whenever something wakes the phone through /sys/power/state. You can't avoid these wakeups since they are necessary.
I identified the cause of the blacklight issue time ago. Not exactly the cause, but it's what preventing it in stock ROMs.
Not so much ago I even posted about it here. Dhiru is aware of it, so there's no need to spam him.

If you normally have the blacklight issue, try this command

su
echo 0 > /debug/pm_debug/enable_off_mode

The issue should reappear. I'm sure it happens if you don't enable the off mode on boot.

In my opinion it's weird that some of you need the off mode enabled to keep the backlight off and that's why I've been looking for an alternative solution, but I couldn't find anything. The problem with the off mode is that it makes the kernel 3.0 unusable, unless you keep the device awake all the time.

We are not ignoring the problem, it's just very difficult for us. It took me a while to understand that the problem was the off mode.



If you don't want to miss calls because of the insensitive touchscreen: Settings > Accessibility > Home button answers call. EDIT2: obviously, we will try to fix this issue as well, there's no need to report it over and over.

As for the battery issue, I verified what @Adriian44 was saying about the discharge (not about the backlight setting), found the problem and it's now fixed. Wait for the next release.

Auto brightness seems to be working strangely.
If tested it off plug and in preview mode, it never gives the lower and the upper limit readings.
I.e.: in a totally dark room, at night, the lower value given is around 145-148 lux.
In full daylight, the upper value is around 640-650 lux.
Don't know Anything about light, lighting and illumination, but is sounds weird to me, given that the system setting range from 7 (or is it 9? Anyway...) to 2200+ lux.
Sensitivity is good enough, though. Maybe some conversion miscalculation is undergoing here, but I do not consider this as an awful problem.

You are totally right about this and I'm trying to understand what's wrong. I got the sensor working properly, but I need to connect the USB cable and then turn the sensor on

If anyone is interested, I ported the new GP2A driver to my 2.6.35 kernel to see if the driver is working as "good" as the old driver. With my changes, the sensor reports the same values of the old driver and there's no need to connect the USB cable.
The changes are here. EDIT: I'm not sure I tried the exact changes. You have to add vaux1 and vaux2 to the board code in order to use these changes. See the platform code of the old kernel.

 

[rodero95]

Hello all:
The latest changes made to the battery driver to show the right percentage, in my case, just make the device always show 100% battery percentage, until it gets to 0%, when it automatically shuts down.
Also, I'm testing some changes I've added to the atmel maxtouch driver, basically, a calibration when the touchscreen is resumed (see
this and this). I've also seen some other possible fixes for this problem which may have to do with the issue, I'll try them if this doesn't makes things better.

EDIT: Up to now, I can confirm this code is working, as I have had some cases when the screen (due to some sweat in the hands) has started to detect false touches and become unuseable (something which happened in stock also) and, after locking and unlocking the device (something which used to work with the old driver) the touchscreen starts working OK again, so the next step is to add a key combo to launch a recalibration to avoid locking and unlocking the screen, as sconosciuto did.

 

[Drizzt_Kueh]

Known Bugs on OP

@rodero95, and @loSconosciuto, we see that you know some bugs that we are experimenting. Can you send a list to Dhiru to update the known bugs on OP? Modifying it, should decrease the repeated bug reports IMHO.
Just saying.

 

[kishankpadiyar]

If you normally have the blacklight issue, try this command

su
echo 0 > /debug/pm_debug/enable_off_mode

The issue should reappear. I'm sure it happens if you don't enable the off mode on boot.

I tried this code, but i get error

sh: cant create /debug/pm_debug/enable_off_mode: permission denied

I have given SU permission, what else i have to do..? Please do tell.. thanks

 

[arindammanidas]

Which kernel are you on? 3.x or 2.x?

Sent from my Huawei Ascend Y300!

 

[kishankpadiyar]

Which kernel are you on? 3.x or 2.x?

Sent from my Huawei Ascend Y300!

3.x... dhiru's default kernel..

Sent from my fingers to your face..!

 

[arindammanidas]

3.x... dhiru's default kernel..

Sent from my fingers to your face..!

What losconoscuito meant was that if you set enable_off_mode to 0 on 2.x aosp/cm kernel , the backlight issue will return...

Sent from my Huawei Ascend Y300!

 

[Adriian44]

I'm Sorry, the problem with the load of the battery, really, does not treat itself about the sheen of the screen, it is a problem of an excessive consumption of battery, (it is my conclusion). Why? Because when the phone does not have SIM card, when I went down the sheen of the screen, the problem was solved, but when I put the SIM card in the phone, 3G consumes already more battery and it returned the problem with the load of the battery.

Then in my opinion, the problem with the load of the battery is caused by an excessive consumption of battery. Is it possible? @rodero95 said to me that he did not have this problem. I am going to try to solve the problem with his help, if I solve the problem, I inform you about everything what I realized to solve the problem with the load of the battery. Thanks.

 

[kralin]

Even with a clean install (kpe-ddlf-cfroot-cm10.1a6) I was suffering a terrible battery drain, and after two charging cycles things didn't make a significant difference.
After swap sd (swap sd 10.1 a6 LoLaTiOn) in recovery I get a bootloop everytime I try.
Its weird because I m using hellybean (dhiru's cm10.1 alpha6 based) and the battery drain is quite better. Is very stable and also swap sd and Pie controls works fine so I dont know.

Sent from my GT-I9003 using xda app-developers app

 

[LoLaTiOn]

you talk about the first Alpha version 6 I think that was replaced
I am referring to the swap that works the same way on all Rom A6 [Updated]

for the battery it is possible that the java layer changes slightly consumption but as your swap does not work I think you confused !!

 

[kralin]

Ok I'll try to download again the alpha 6 ROM and flash it and see how battery goes without swapping anything and later, if swap works as it should , I'll check the battery again.
Thanks

Sent from my GT-I9003 using xda app-developers app

 

[rodero95]

Hi all:
Just an update after a day using my changes to the touchscreen driver. The problem has completely gone, now, if the touchscreen detects some false touches, like when there's sweat on the screen or something, locking and unlocking the device solves the problem, instead of stop responding. I can fully confirm this now as it has happened several times during the day and it has always worked.

Sent from my GT-I9003 using xda premium

 

[quan815]

Hi all:
Just an update after a day using my changes to the touchscreen driver. The problem has completely gone, now, if the touchscreen detects some false touches, like when there's sweat on the screen or something, locking and unlocking the device solves the problem, instead of stop responding. I can fully confirm this now as it has happened several times during the day and it has always worked.

Sent from my GT-I9003 using xda premium

Can u make a patch for us? It annoyed me a lot.Sometimes I late reply my girl friend because of this problem then she angry me

 

[Cpin0312]

Can your backup system software through titanium pro? I can't backup it and uninstall system software

Sent from my GT-I9003 using xda premium