Hi all,
I love the fact that, with S View cover and stock rom, I don't need to press any button to turn the display on or off. Just opening or closing the cover does the trick.
I know that S View doesn't work with CyanogenMod or any other non-TW rom. Could someone confirm whether, in CyanogenMod, at least the screen turns on and off when the cover is opened and closed?
Thanks in advance.
Flash temasek's kernel or unofficial cm11 by temasek. Screen on/off works fine using temasek's kernel..
I think this app might work with cm.
https://play.google.com/store/apps/details?id=com.mobius.sviewplus
Slim Armor View case here. Closing the cover shuts down the screen 95% of the time.
Related
Hi guys,
I've been using ms2ginger 4.0 and just changed to CM10 by Quarx.
The problem is that as soon as i dial a number the screen goes dark and i could use the power button to display the screen in ms2ginger but not in the cm10 edition.
It happens atleast 9 times out of 10.
Any solution, is the screenguard culprit ?
or any fix for the sensor to work properly?
it was wrking perfectly when used the official froyo!!!
trojanx said:
Hi guys,
I've been using ms2ginger 4.0 and just changed to CM10 by Quarx.
The problem is that as soon as i dial a number the screen goes dark and i could use the power button to display the screen in ms2ginger but not in the cm10 edition.
It happens atleast 9 times out of 10.
Any solution, is the screenguard culprit ?
or any fix for the sensor to work properly?
it was wrking perfectly when used the official froyo!!!
Click to expand...
Click to collapse
I'm on CM9 and there is a setting under "System Settings > Display" which says "In accurate proximity". See if that's in CM10 and works for you.
defydent said:
I'm on CM9 and there is a setting under "System Settings > Display" which says "In accurate proximity". See if that's in CM10 and works for you.
Click to expand...
Click to collapse
Thanks for your reply, in cm10 couldn't find that option moved to cm9(mig edition)
the problem is still there after checking the proximity option but not that much
Found a Solution
I was searching all around this place.
Found a solution that the screw just behind the proximity sensor (when you open the back panel) was a bit tight, too much i guess, just loosened that screw to a single round and it is working perfectly.
Maybe help anyone facing the same issue.
P.S. i did open my whole phone once and i guess tightened the screw too much.
Hi, since I updated to Kitkat, sometimes the S-View sceen gets unaligned.
Check it (in this video, I kept opening/closing the cover to let see what is the bug):
S-View unaligned
Plus, other times it can flicker.
I'm stock, rooted and with apex laucher. But it happened also without root and with TW. It seems that could be caused when I'm using my S4 in landscape view (or there is some app in background that it's in landscape mode) and I close the cover, but it's not the rule. Plus, I'm quite sure it happens even in portrait view.
Is anybody else experiencing same issue? I googled but it looks it's only me :-/
Thank you
PS: I've wiped, reflashed, changed rom (DBT, now ITV)... but it's still here.
Same here .. everything goes over to the right of screen and cuts off some of the time and date
Any solutions for that?
bump for interest
After upgrading my 16GB D802 from a beautifully working CM 10 to CM 13 the following problem occured:
After the screen shuts off (either by the phone going to standby or the proximity sensor in case of phone calls), it takes several attempts to activate the screen (you see the backlight turning on, but the screen stays black, then you have to click the power button to go into standby and try again til it works; tapping and pushing the power/standby button to wake the screen up work equally bad)
I tried going back to CM 10. On CM 10 the screen activates and deactivates as it should, but I had problems with very very unstable connections to wifi and cellular (which I had not before). (Also: I was stupid enough to not have made a backup of the previously stable CM 10 installation.)
All in all, I tested CM 13, 12, 11, and 10. 13 and 12 have the screen problem and 10 and 11 have the connection issue.
For all testing I used TWRP and the hybrid bootstacks.
Has someone experiences similar issues?
I would greatly appreciate any help.
Thanks so far!
Kind regards,
toas7
Cyanogenmod does not seem to be the problem. I've got the same issues with e.g. Mokee (MK51.1) and the Turbo ROM (Turbo-d802-4.0).
Might the bootstack be the culprit after all? Is there something that could have been gone wrong?
I tried the (zipped) stock ROM: the problem remains
Edit:
Flashing the modem (with a flashable modem) solved the issue with wifi and cellular on CM 11.
Software or hardware
Hello, I have the same issue but in addition the device is extremely lagged. Although I am still with stock mod and no root, by the moment. Could you help me?
Hi everyone,
I am using the official s cover with stock touchwiz.
Whenever I close the cover, the screen turned off and when I open it, the screen turned on itself. It works as if some proximity apps is installed.
I went to playstore and updated the touchwiz. Surprisingly, that on off feature is gone.
Anyone else having similar issue? This new version is worse than the stock.
Maybe turned on the switch settings/display/keep screen off
mart56 said:
Maybe turned on the switch settings/display/keep screen off
Click to expand...
Click to collapse
Don't think so, rolled back to the stock version and it is working as intended.
Hello, I'm a fresh member of this forum and recently upgraded my Galaxy Samsung S4 (i9505) from stock to AOSP Oreo. After the upgrade everything worked more or less as expected, the ROM is stable enough for daily use.
Unfortunately the S-view is not working like expected, if I open the (original) Samsung s-view cover the screen lights up and if I close the cover the screen goes off, but there is no clock in the display as before. Also with an incoming phone call the screen doesn't show up, or I can pick up the call by wiping over the cover window.
I installed the files below:
Unofficial TWRP recovery.img
JDCTeam-8.1.0-20171209-BETA.zip
open_gapps-arm-8.1-nano-20180119-UNOFFICIAL.zip
Kernel-B--B-PWR-CORE-AOSP-O-v3.2.zip
SR5-SuperSU-v2.82-SR5-20171001224502.zip
Also, I tried the 'S View Lite' app from play store. After closing the cover the screen is shown for a few milliseconds,but no sulution there. I also repeated the installation a few times (thanks for the nice youtube video's) to be sure I made no mistakes.
Because I miss the S-view functionality like it worked before, I post this question on the Q&A (my question on jdcteam-android-source-project-oreo-t3685231 did not get much response). Maybe someone can help me to get it going, tell me if it's working on her/his dvice or tell me I have to live with it like it is ?
there is no lineageOS rom with the Sview.
the Sview is based only on TW rom, so nothing newer more than a 5.0.1 TW rom.
and all Sview apps don't work correctly.
If you want S View, go back to TouchWiz.
If it's ever going to work on AOSP ROMs, it only does to lock the screen instead.
Sent from my Redmi Note 4 using XDA Labs