Hello guys,
i'm new to the Galaxy Note and the Forum, start by thanking everyone for the great job you have done and are doing.
- Before:
I bought a Galaxy Note, I am fine and i love him like a son (maybe because I have no children).
There was the original version of Android 4.1.2 firmware N7000XXLSA with NO brand.
I flashed from the original recovery kernel that is here (forum.xda-developers.com/showthread.php?t=1901191) to be precise "Philz-cwm6-XXLSA-DBT-v3.99" (I do not know why I chose this among others, perhaps because it reminded me of the original LSA final XXLSA and makes me wonder: the "Philz-cwm6-ZCLS8-CHN-v3.99" is newer than the one I flashed?).
From ClockworkModRecovery I installed, after fullwipe, the last Nightly of CyanogenMod 10.1 and the gapps (as I did on other phones like Nexus S and Nexus 7 and it is always gone smoothly).
- The problem:
Everything works fine (apart from a phenomenon of Battery Drain, but I have to recalibrate it and recharging from consuming it all off for at least 4 hours and then delete the stats etc ...), but there is one thing wrong: the monitor.
The icons on the desktop can be seen very well, ultra bright and the text looks really HD! (I come from Nexus S and I also have the Nexus 7, bright colors and blacks amazing!) But the background, some photos appear, or the shades of black phone menus you see badly.
If I use MXPlayer to see a video all blacks are pixelated, gradients are sheared.
As if it was in safe mode, type windows xp in safe mode that NOT loaded the video card drivers.
I read around on the issue and there was talk of color banding, 16bit software compared to 24bit monitors hardware, but in essence what?
Depends on the kernel?
I have to go in customer care to replace the monitor (which also occasionally changes almost imperceptibly color, for example while navigating, then on the white background of the pages, from white light turns yellow, then brown, and so on).
What do you recommend? Does anyone have or have had the same problem?
UPDATE:
This morning I tried the phone around, the street outside and the problem seems to disappear.
I set auto brightness. So maybe with strong light, increasing the brightness of the blacks are softened better.
Now I'm recovering from the last original software Samsung Kies, the much-hyped premium suite, see what happens and if the problem remains.
Thanks in advance to all.
I recommend go back to a non leak firmware which is not buggy like this one. Then see if you can reproduce. Remember those JB roms are buggy leaks. Best to use the kernel phills made explicitly for the rom version you are running.
Regarding colour changes this usually is due to powersaving apps or settings. Remove and/or disable those. especially the one in the stock browser. This a known old issue not necessary caused by hardware.
battery drain issues van best be analysed according to ahalfords sticky on wakelocks.
... please?
What does it take porting Sony Stamina mode (SuperStamna.apk) to Xperia V with KK?
A custom kernel with certain drivers, as well as some files.
The kernel is the problem here, we dont have the sources.
but you are a pro developper you can do it <3
I was told kernel writing is the high art.
Sure it is.. The problem is, there are very few tutorials in kernel development out there, and Kernels are written in C code, which I dont know.
There are a few Xperias with KK including Stamina. I mean, for a developer who speaks C it might be not to difficult copying and modifying the Stamina portion accordingly for the V. Not that I want to sound like demanding, I have no rights as I myself am unable to program anything except my TV remote control. I do understand that the V is not anymore in the iris of a developer. On the other hand I believe there is a good chance the last 0.5 % sleep power draw will be eliminated, too. That's 4 % in a night, not the 1/100 % that switching off a processor gets, and then even with side effects.
What you say is right. The problem is still that we dont know what code exactly to copy, where to make adjustments to enable this stamina driver and we dont even know if there is any source code published.
I guess there is no Xperia with the same chipset that uses Sony KK?
Dont think so. :/
Several users (including myself) have pointed out that the automatic brightness doesn't work as before the 6.0.1 update.
Here are some of the reports:
kom-pakt said:
One of the few drawbacks I noticed just today is that the auto brightness seems a lot less responsive. For example it's very sunny today and most of the time when pulling the phone out of my pocket the display was still stuck on low brightness. It might just be a conflict with xposed or something else I'm running.
Click to expand...
Click to collapse
GFixx said:
I have a bug with automatic screen brightness, if I unlock the phone at the sun I do not see almost nothing
G800F ITV 1CQA1
Someone can confirm?
(GPS and Volume seems fine)
Click to expand...
Click to collapse
milad9896 said:
I also have this problem sometimes
Click to expand...
Click to collapse
So far I've tried running the phone without anything on it like Xposed or any apps beside the stock ones and it hasn't fixed the issue. What I do know is that it's definitely not a hardware issue since the light sensor works as it's supposed - you can test yours by entering the service menu by typing *#0*# from the dialer. I am currently running the German DBT firmware but I'm currently in the process of flashing the South East Europe SEE firmware which is different only in the security patch, so if the problem persists then I will know for sure it's not a DBT-only problem.
How many of you have this issue as well? Also, which version of the firmware are you running?
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Myke72 said:
Me too. Also DBT FW with 6.01. Flashlight has also an issue in the dark.
Gesendet von meinem SM-G800F mit Tapatalk
Click to expand...
Click to collapse
I am currently running the South East Europe (SEE) firmware but I haven't tested it extensively so I can't say if it's any better.
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
So Samsung's solution for this is to use manual brightness? Really Samsung?
I have the same after upgrade to 6.0.1, it's unbelievable such a bug in official release
any fix for this?
I installed Auto Brightness app, but it seems Samsung display goes above 100% in sun, third party apps can't do it
Does anyone have realy bad battery Problems too? (See my thread...)
GFixx said:
I wrote to Samsung to report the brightness bug and they said
"I'm sorry about the problem you are having, but are not officially anomalies on this issue."
"This is because with the automatic adjustment of brightness, of course, the stronger the external light source, the lower the brightness of the device.
In any case, since the restore operation has had positive consequences, I invite you to use the manual brightness adjustment when you can not see the screen properly.
alternatively, if the problem is particularly heavy, you will be able to view the problem at one of our authorized service centers. "
Click to expand...
Click to collapse
I have the same problem - I made a video of it below. It's a serious usability problem - makes it very hard to use in sunlight.
As a kind of workaround you can put your thumb over the light sensor as you wake it up, then it will wake up dim but still visible. Eventually it will adjust and brighten to match the sunlight. But this is slow and awkward and needs two hands.
The reply you got from Samsung is ridiculous. For a start, the stronger the external light source, the stronger the brightness of the device - they have it the wrong way around. Anyway, it is obviously a major usability problem and I can't believe they are dismissing it. (And manual brightness is not an answer of course.)
Phone specification:
Model number: SM-G800F
Android version: 6.0.1
Baseband version: G800FXXU1CQA1
Kernel version: 3.4.39-10294723 [email protected]#1 Wed Jan 4 12:03:16 KST 2017
Build number: MMB29K.G800FXXU1CQA1
SE for Android status: Enforcing SEPF_SECMOBILE_6.0.1_0033 Wed Jan 04 12:28:05 2017
It works fine on my G800H with latest Polish stock ROM
I don't use to write in the forum, but I must say 'me too'. If someone knows a working Marshmallow ROM for the G800F. The thumb "workaaround" is the only one working for me..
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
kom-pakt said:
I strongly encourage everyone facing this problem to write an e-mail to Samsung through their official website. In your e-mails make sure you note that this problem is definitely caused by a software issue and not a hardware issue - the auto brightness worked fine with KitKat and Lollipop, but not with Marshmallow. We need to bring this to their attention so they can fix it in a firmware update and the only way to do this is to send them as many reports as possible.
Click to expand...
Click to collapse
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
alex3453 said:
I'll do this. Do you know the best email address to use? Also I'll drop in at the nearby Samsung shop (hopefully on a sunny day) and see what they say.
I'm surprised that this bug isn't much more widely talked about given that it's a major usability problem, and given that the S5 mini is a popular phone (hundreds of thousands, maybe millions?, sold). So I wonder if it's possible that there is something special about our phones, and the bug doesn't happen on most people's devices. But I can't think what it would be. I've not done anything unusual with my phone - it's just a standard out-of-the box phone running the official operating system.
Click to expand...
Click to collapse
Use the official Samsung website (for your region) to report the issue. Browse a bit and you'll find the form.
It's strange that the number of people affected by this issue seems relatively small, keeping in mind that XDA is a forum where a typical user is usually a power user. Also it's not a region-specific issue or caused by an app or something else. For example I thought that maybe Xposed is causing a conflict so I did a complete wipe and flashed a fresh firmware, used the phone like that without any apps for a couple of days but the autobrightness issue was still there. Tried a different firmware version as well but nothing helps. Again, it's definitely not a hardware issue - test yours by typing *#0*# from the dialpad to enter the service menu and test the sensor yourself.
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
ffoucault said:
I solved the problem disabling the automatic brightness function and using Lux Lite as workaround instead
Click to expand...
Click to collapse
bravur said:
I have this issue too. Hungary (Telenor) G800FXXU1CQA1. The service does not find any problem. I refered severel minor issues (among autobrightness failure), but I did not managed to talk to them, and they wrote that there is not any hardware problem with the phone. They recalibrated the sensors, so that might help.
Lux Lite solved the problem, thanks!
Click to expand...
Click to collapse
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
foulke said:
Hello I have the brightness issue too (G800FXXU1CQD1) official french ROM, since I upgraded to 6.0.1.
I also had some strange charging issue.
I tried with different wall chargers. When I plug them, the charging led doesn't turn on. The battery charging icon in the status line on top doesn't indicate charging.
But if I leave the device for some time and reboot, the battery level increases. So it means that it charges !!
Once I tried removing battery and it recovered, but not every time...
Click to expand...
Click to collapse
Did you try the basic stuff like reflashing the firmware and such?
kom-pakt said:
Lux Lite is only a workaround, but not an acceptable solution. That would be an official update from Samsung which solves the problem caused by their original update.
Did you try the basic stuff like reflashing the firmware and such?
Click to expand...
Click to collapse
No. I don't want to use Odin for the moment.
By the way I installed Lux, and it works fine.
I'm surprised you're happy with Lux, official Samsung can do much more brighter screen in strong sun then Lux
By the way, I removed Lux since. Because it requires too much app permission than I think it should (contacts...)
So I'm looking for an another solution
Good news!
Yesterday I jus tried to install the latest firmware available on sammobile (for G800F) - the one for nordic countries -.. and now the brightness control is working perfectly!
Seems that this 'not' problem was fixed in latests releases :good:
Hello everybody, i am glad i write my first post here.
I don't want to bore u, so i get straight to the point.
I have a Xiaomi Mi 9 M1902F1G with Miui Eu 12.0.2 (QFAEUXM) and i have a very low ScreenOnTime, i installed miui Eu variant 3 days ago, and i can t get more than 4 hrs SOT.
The thing is, i changed my display because i broke the digitizer( some liquid went inside ) and since then my battery is rubbish, to be more exact before changing the display i got like 5-7 hrs SOT on miui Global.
I want u guys to keep in mind that i first changed miui global to crdroid because i thought it was a soft problem, the screen still did not respond like it would before so i paid more than 120 euros to change the display with another original one( at least that is what they told me, they also told me that they order the display based on IMEI ) and now is working is it should, but i seem to belive this one is more....blackish, i mean don t get me wrong, it seems greater than before, the colors are more sharp( or maybe i think so bcs when he was at the repair shop i used a IPS screen )
Raysteff66 , the admin for crdroid told me that i installed his soft wrong, i told him i had Global MIUI not Eu, so after a week of using crdroid( witch was very good too, except battery life ) i installed Miui Eu, and the battery is the same.
The question is: What can i do? Is the screen not original or did i do somethink wrong? I installed the softs with Fastboot and unlocked with miflash.
I hope someone can help me, i ran out of ideas.
Thx so much in advance and i hope all of u are well.
I now remembered that my phone was heating up very badly when i used crdroid, i don t have this problem on miui, also i remembered that now the battery drops very fast when i use my BT headphones, did not do that when i installed miui eu variant ( first day )