Related
Found the solution!
It was by matlacki, basically just reflash stock ruu 1.32, re-root and restore your nanadroid and it's all good.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
==================================================
Btw i am using build 30
For those who having this proximity sensor issue like myself , I done a test.
Go to setting > CyanogenMod setting >display > automatic backlight > > tick use custom > edit other levels.
For me I can see my sensor functioning will. 7 for total darkness and 59 for din light and 190+ for lamp.
Now try to make a call and watch the screen go off. You can't on it back but there's still ringing tone.
I used my nexus one flash to shine on the sensor and my screen turned back on.
Now go back to the edit other lvl notice that the light sensor doesn't response to the different brightness.
A reboot will fix the problem but if there's s phone call,this bug starts again. Try it!!!
And share your results. If there's ppl with the same as mine, it might be a cm7 bug and not s proximity sensor failure
Its not a CM7 bug. I have never had the proximity sensor problem on any ROM, be it stock or otherwise.
I'm also using build 30 and no proximity sensor problem to report.
i want to believe its not a CM7 bug.
For the past 2 weeks when I was using various CM7 builds, I do not have any proximity issues as described by other users till yesterday, it just popped up.
Nandroid to my old backup (which has no such the problem), and problem still persist.
flashed back to RUU 1.32 rom and the sensor is working in sense rom.
So now i cant even send back for a replacement.
matlacki said:
I had the same problem yesterday and I found the solution (it works for me). Flashed stock RUU 1.32, rooted again, eng/radio-s off, again, flashed CW7 bulid 30 and my proxymity sensor is back to normal.
Click to expand...
Click to collapse
I have done the same and now my proximity sensor is working again when restored from my CM7 nanadroid.
This doesnt make any sense?!
This problem started yesterday evening for me. 5days of CM7 without issues and now this dealbreaker. Need to pull battery after end of a call.
Sent from my Desire HD using XDA App
try flashing 1.32 RUU and redo the whole rooting again > and back to CM7.
seems unreal but it really did solve my problem..
Okay...
I'm having the same problem, i just checked it with the program "Sensorlist" which gives me info about the proximity sensor....
With CM7 it doesn't work, but with stock rooted ROM it works fine...
So it must be a problem with the CM7 software....
Has anyone solved the problem, so it doesn't come back?
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
My findings (with input from Apache14):
- The proximity issue only affects those with a non-Sharp LCD.
- The kernel source code released by HTC does not contain the correct code to handle this device. I am still looking for solutions.
- On the 1.32 kernel, when proximity is required, some polling mechanism is activated. I assume this is needed as there is no Interrupt hooked up on a hardware level on this LCD/chip (same sensor uC however).
- There is no source code for this. Not in HTC released kernel source or CM or AOSP.
Currently I am looking at either:
- Getting the latest source code for the DHD kernel which HTC has failed to release. The source code corresponds to some RUU older than 1.32.
or
- Hacking the kernel to do the same polling as present in the 1.32 kernel binaries.
McKebapp said:
Solved my Problem, too.
And I guess I've found the reason for the Problem.
Within the last Days, I've played around a little with the ambient light sensor settings. Both, system side and also with the additional cyanogen settings.
Why do I come to that conclusion?
Well, I made a Backup of all my Apps and Settings via TitaniumBackup.
Then I:
- Wiped my phone via CW + Full-Wipe.zip
- Flashed this 1.72 via CW http://forum.xda-developers.com/showthread.php?t=884327. Tested it = everything fine.
- Wiped again + clean installed PNK_AB CM7. Testet it = everything fine.
- Restored my Apps + Settings. Failure retuned after restart.
Now I was sure, it is Software related.
- So I wiped the data partition via CW and restarted. Everything fine again. Even after Reboot.
- Time to restore Apps + Settings, but this time without the settings from the Cyanogen Apps/Settings, Debug App and SpareParts. Everything fine in first, but the problem retourned after reboot.
- So again: wiping data = everything fine. Rebooted about five times, te be sure. Everything fine.
- Restored Apps + Settings: without: Cyanogen Apps/Settings, Debug App, SpareParts AND SystemSettings.
Voila: The Problem was away and didn't even come back after several reboots.
So my conclusion:
CM7 ambient light settings and system ambient light settings mess each other up. Dunno, which is causing the problem, but it is solved for me, yet.
What's your Opinion guys?
Click to expand...
Click to collapse
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Numsefis said:
how can you remove these parts from the Rom? "the Cyanogen Apps/Settings, Debug App and SpareParts. "?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Didn't remove them from the ROM.
I simply unticked them while/before restoring my FullBackup with TitaniumBackup.
For those that cant get proximity sensor to work on custom kernel/ROMS, try the following (no root required):
Code:
echo '0x50530b0c 0x140b0b0c' > /sys/devices/virtual/optical_sensors/proximity/ps_kadc
This will adjust the calibration values. The 0b part is the 'low tide' aka FAR start and 0c is the 'high tide' aka NEAR start.
IOW, values below FAR start is FAR, and values above NEAR start is NEAR.
Tested this on latest Buzz (Apache14) kernel.
Need to somehow make this persistent, and make sure it does not get reset during normal operation.
Stay tuned
Update: Still thinking of how to apply this at boot, maybe 'init.d' ? Also havent been reset during normal operation.
Thanks for the info
ok but how do you appli that ?
Text editor ? etc.
Flashing default (stock ruu) kernel
did it for me. Prox sensor working as intended.
Sent from my Revolutionized Desire HD using XDA App
I wrote an app to fix this.
See http://forum.xda-developers.com/showthread.php?p=11312762#post11312762.
Great work Leppie!
I had this problem, wile on CM6, started after I installed ADW EX. Used to use launcher pro, but realy liked the transisions in ex, so started using that, and got this problem. Updated to CM7, stil had the problem, no matter rom version. Went back to launcher pro, and now it works like normal. Thinking ther might be something with the launcher, and mabye a hardwere thing in some phones.
I am now on nihtly CM7 34, I think, and no problem.
So for those having this prob, try to switch to another launcher, and reboot a couple of times.
Hope this helps
how did you downgrade?
with Recovery?! or with Gold card?!
i have done both ways but didn't solve my problem :-(
please give me a link of Stock rom ruu!
Hello.
This is where you can look at the tutorial and get the files to install if you feel like jumping into it ...
ICS Step by step and files
Note: if you do flash this and it hangs at the boot screen, pull the battery and flash it again and it should work. Some have had to do it 3 times.
I take no credit for this ROM and full props go to the developers of the above post and all those working to make this happen.
First the look and feel of ICS is nothing short of superb. The speed as of now is similar to all the other ROMS I have tried with a little chop here and there but nothing major.
Yes lots of little issues and items that do not work like the camera and GPS but not a huge deal for me so I am willing to stick to it.
Battery so far is decent. 13 hours and 43 min. on the first charge to calibrate and sitting at 24% still. This included allot of playing with the phone and reboots to test jigs
As for the issues that are somewhat bothersome, they include the following.
1. No home or search button. I know same as usual when installing an i9000 ROM but the key mappings from the GB ROMS does not work.
2. BLN (issue all around) will remain lit until you wake the phone to get the notification.
3. They had to do some funky stuff to get 3G to work so it lags to start. Not a huge deal cause it does start and remain working.
I will be continuing to use this ROM and hopefully everything will be working soon (these guys are flying. Also I have been told that the folks over at Glitch are already working on the kernels for the ICS port so that is promising as well.
If there are any other out there running this on our phone chime in with your thoughts or fixes if you have any.
Thanx
Bucky
Thanks for starting this thread. Can't wait to hear about your progress.
Alpha 7
Hey here is the update ...
Installed the Alpha 7 update today and I have to say this rom is fantastic.
1. Camera is fixed and works like a charm.
2. GPS locked in seconds and accurate indoors!! Big improvment over all other roms I have used.
3. HW Acceleration is fixed and working from what I can tell
4. You Tube is fixed and can watch video
Still on the not working list
1. Can not plug the phone in while off as it just restarts. this is a work in progress and known issue
2. Can not record video
3. Will not read a SIM card for contacts and so on (thank god for Google sync)
4. Still no home or search buttons (I think I may need to work on that on myself unless a kernel is released)
SO my review so far ...
No real issues with the general use of the phone. Text, phone, email and web are solid, I have installed apps from the market with no issues and not one FC yet. Battery life is good and nothing is taking over. I have been able to use the phone all day and still have lots left over before going to bed and plugging in. I have not been through a full battery as of yet but that is what I am working on now.
Memory - Last I looked I had 174MB of memory remaining which is the highest I have seen.
ICS is really smooth and fast while moving around. I am going to continue to play with it and report back here for everyone.
I don't use a whole lot of apps so there won't be much regarding those.
Thanx for stopping by and I will post pics when I can.
Bucky
Nevermind
Sent from my SCH-I500 using XDA App
Thanks for the update. From your review, it sounds like an awesome rom. Can't wait to try it but need them to fix the video recording first. Although I might just cave and try it out just to see what the fuss is all about
Can always restore my current setup... lol.
Update ...
been getting the SOD today and not sure why, I mentioned above that the HW acceleration was working, I misunderstood and it is not fully working yet.
I found that the system partition is very small. There was an update which required copying libs and there was not enough space left to do this (2MB). Not too sure if this is due to coming from MIUI or just a ROM issue.
Alpha 8 was released but had quite a few issues so not flashing that one.
Daily use has been great so far (except for the SOD) with no reception or data issues.
I am still working on the home and search buttons but I think that will get fixed with a kernel update. I tried the keymap file but these buttons do not even register in recovery so I get nothing in the ROM either.
More to come ...
Haven't tried this (likely won't as I need the phone for work) but buck have you tried the manual key fix - some directions in our thread on putting on Darkys 10.3.
Sent from T959D running Miui
Yup been there done that no go
Sent from my GT-I9000 using XDA App
Hey buck , was doing some searching in teamhacksung's thread about their ICS port, and someone suggested to change the following and then the key mapping for our phones will work properly. Not sure if the file system is the same for both, but definitely a bit of info if it isn't!
All you have to do is change this part on**arch/arm/mach-s5pv210/mach-aries.c*
*Original**(line 1216~1221)
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*0,*
*0*
----------------------------------------------------------------------------*
*Edited*
static const int touch_keypad_code[] = {
#if defined (CONFIG_SAMSUNG_GALAXYS) || defined (CONFIG_SAMSUNG_GALAXYSB)
KEY_MENU,
KEY_BACK,
*KEY_HOME,*
*KEY_SEARCH*
Sent from my GT-I9000 (T959 mod) using XDA App
Thank for the input. After flashing bata 1 all the buttons are working. More to come: )
Sent from my GT-I9000 using XDA App
Hey, have a telus fascinate too. Know how to flash and all that fun stuff. Just don't fully follow where you make the changes for key mapping...if you could just guide me in the right direction, I can figure the rest out...
changes in the kernel zip? the beta zip? after flashing? something completely different?
thanks a lot!
There are no changes to be made with this ROM, they are built in. Just flash and all good.
I will post update tonight after work.
Sent from my GT-I9000 using XDA App
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
havoksupertwit said:
yeah sorry realized that immediately after posting / flashing to the new rom.
have you tried out BT audio? I can connect to different devices but audio won't stream
Click to expand...
Click to collapse
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
bucknetbucky said:
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
Calibrated my phone this morning. Heavy use today configuring everything but about 52% now (sooo 5 hours or use?)
Why god! Whhyyy!!
bucknetbucky said:
There are allot of BT related posts in the QA. I personally do not use any BT but I do have a headset that I will try when I get home.
Seems to be a battery drain issue too as my phone is now dead but I have not calibrated so we will see after I do that.
Click to expand...
Click to collapse
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
iwebsource said:
AT LEAST YOU GUYS HAVE IT RUNNING!!
I am having a hell of a time trying to get it to work. I have tried so many different ways to get it up and running but no luck.
I've tried installing it from MIUI 3 times but all I get when trying to boot into ICS for the first time is a Black Screen after the FuguMod boot screen.
The funny thing is that the 4 soft buttons at the bottom light up still.
So I then decided to try the JVT way:
-Flashed JVT DARKYROM (ODIN)
-Lagfix OFF
-FULL WIPEs (factory reset, cache, dalvik)
-FLASHED CM7.1 STABLE
-FULL WIPEs (factory reset, cache, dalvik)
-Flash ICS BETA1
-Flash kernel
-FOR THE SECOND TIME:
-Flash ICS BETA1 AGAIN
-Flash kernel AGAIN
Same issue, black screen after the FuguMod boot screen, buttons still light up.
So i tried a couple more times in a few different ways based off what I have already tried, but this time, before booting into ICS for the first time, I installed the 'Superuser-3.0.6-efgh-signed.zip' package.
Same issue. I'm not having any luck here.
Click to expand...
Click to collapse
OK so here is what I did ...
Started from MIUI 1.11.18
1. Do a nandroid backup
2. download all the files to the SD card. This includes the ROM, Kernel and super user fix
Links:
Kernel:http://ice-cream-sandwich-sgs.googlecode.com/files/FuguModICS_GT-I9000_update.zip
ROM:http://ice-cream-sandwich-sgs.googlecode.com/files/ICS_4.0.1_r1-Beta1-i9000.zip
Super User:http://ice-cream-sandwich-sgs.googlecode.com/files/Superuser-3.0.6-efgh-signed.zip
3. Boot to recovery and do factory reset, wipe cache and davlik cache
4. Install the Kernel first and reboot now
5. Boot into recovery factory reset and wipe cache and Davlik and Install the ROM then reboot now
6 Boot back to recovery and install the Kernel again with out the wipe
7. If after reboot you do not have root then boot to recovery and flash super user fix
8. reboot and it should be working at least it was for me
It seems to me that you are missing the first flash of the kernel before the ROM. It sets up the file system from what I gather
Note: If needed flash the kernel and rom then kernel again with all the wipes as mentioned above.
I know there are allot of folks having issues getting it to run. Not too sure if it was the way I installed MIUI that might have made the difference.
My battery is charging now so I can calibrate it and see how it goes after that (it drained pretty quick today) lol.
I hope you can get it going cause it truly is awesome
Still not working:
Can not charge with the phone off
Google TTS stops working
Phone will not vibrate for SMS or email when in silent mode
BLN stays on for notifications until the phone is taken out of sleep (can be turned off)
Compass is why off (have not attempted to calibrate yet though)
11 MB left in the system partition (not much but I do not think there will be many changes there)
Video play back is choppy and some will not play
Bucky
regarding the black screen:
- had that too... I let it sit on the black screen for 2-3 minutes and then it went to the boot screen animation (a multi-coloured )...that for a few minutes...then finally booted.
How i got it working:
a) Started on MIUI...booted into clockwork
b) Backup
c) Wipe data / factory reset and cache and dalvik cache
d) Install rom and then kernel
e) Restart
f) Install rom and then kernel
g) Restart and wait very patiently for a little while
h) Once it all works, can reboot into clockwork and install superuser
Good luck! I really think the rom is nearly stable enough for daily use...
-------
Also have the no vibrate on silent... haven't tried the other stuff yet.
Oh and TTS hasn't crashed on this version yet for me...
Astrid glitches a little to a lot.
Changing from google tts to picco tts solves the problem there. As for the other stuff it is all reported as known.
I am using as a daily on my phone and no issues with general use. Still testing battery and that seems to be a bit of an issue with regard to Android OS as usual
Sent from my GT-I9000 using XDA App
So to install this ROM I would just have to install it as per totallydubbed's instructions? I don't want to flash miui if I don't have to to try this out.
Sent from my GT-I9000 (T959 mod) using XDA App
hi
i have a problem with my u8800pro. i have installed a cyanogenmod7 rom and when i press the lockscren button the device shut down instead of locking and i have to reboot it
anyone have the same problem?
Nope.
Sent from my ragelis
Check CM7 thread. I think I've seen complain about this. Didn't happen to me though.
I've got exactly the same problem. And can't find how to solve it. Moreover it turns off instead of locking when time for locking comes.
If anybody knows what causes it and how to solve this problem - please help.
It also happens whit MIUI ROM
Yes the same with me.
Here is 2.2 froyo stock rom http://forum.xda-developers.com/showthread.php?t=1315823
Oi! I had the same prob, the system worked like it should but as soon as I pushed the power button to go to sleep the device reeboted. You need to make sure that you clean the Dalvik cache, wipe data, wipe partition, before you install your Cyanogen ROM. I did that and it helped.
Hey friends!
I am using Mb526 for quite a while now.I am having a strange problem of signal freezing within 10-30minutes of booting the phone, cm9 was fine.. but as soon as i switched to cm10 there is a strange problem that the signal bars freeze/there is no outgoing call/the data packet doesnt work and in this case, nothing helps to get it back to working except a complete reboot. this happens suddenly and is self triggered at any point of time because of which i miss important calls and messages. i have tried to do the following
1)set the governor to conservative at default clock settings.(someone suggested this)
2)removed phone.apk and all its associated apk's from HWA's settings
Is there a patch for this? ive tried installing jellybean kernel too(in MIG edition rom but it gives me another problem that the signal is off). please someone help my poor defy :'(
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
itsnotmeatall said:
Are you wiping everything (cache, dalvik, data and system) pre flashing?
Try flashing a wipe script.(search for it, it basically wipes everything for you. You have to be careful to use a script that does not wipe your sd card as well)
Click to expand...
Click to collapse
before every possible flash..i do factory reset twice..dalvik and battery once
esidyo said:
before every possible flash..i do factory reset twice..dalvik and battery once
Click to expand...
Click to collapse
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
itsnotmeatall said:
Have you tried going back to CM9 to see if everything works as before? That way you can rule out a hardware problem.
Click to expand...
Click to collapse
Everything works fine in Ms2ginger
esidyo said:
Everything works fine in Ms2ginger
Click to expand...
Click to collapse
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
itsnotmeatall said:
Have you tried with all the different basebands? This was what worked for me when I was having a problem with no incoming calls. There is a baseband changer app in Play.
If that doesn't work - Since flashing a different kernel is getting you a different problem maybe you should try various kernels. One of them might work.
Click to expand...
Click to collapse
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
esidyo said:
tried that.. tried jelly x kernel and switching basebands... going back to cm9.. atleast it was stable :\
Click to expand...
Click to collapse
Now even in cm9 it is unstable... i have seen as soon as i try to underclock it, the problem comes.. phone works fine without underclocking. even when the phone doesnt reboot... it still has that problem of signal freezing...
Hello everyone!
I'm trying to watch some movies from Google Play Movies but everytimes it gives me this error: "There was a problem while playing, touch to retry.. or reboot the phone" (I don't know if it's the correct translation, my language is italian).
I googled a lot, and I found some possible solutions, like:
- reinstall the application
- clean app's data and cache
- wipe dalvik
- switch to 3g / change wifi
- enable AwesomePlayer instead of NuPlayer
- set the governor to "persistence"
I tried everything, but the problem is still there. I even tried to change rom and kernel but it hasn't solved it!
So I lost my hopes, and switched to Netflix.. but here, same problem! After pushing the play button, it starts a loop with the "loading in progress".. I tried the solutions above, but I haven't solved it yet
Am I the only one with this issue? How can I fix this?
Thanks, and sorry for my bad english
EDIT: I just discovered that by enabling the "simulate secondary screen" option under Developer settings, the movie magically starts into the secondary screen (this works for google play movies only... not for netflix). Anyone knows the reason?
I haven't come across this problem before. It sounds like the kind of bug you might encounter if you are using a custom ROM or kernel. If you are, you could try flashing back to a stock build and see if the problem goes away.
If you are using a stock ROM and kernel, it sounds like you have tried almost everything and it might be time to perform a factory reset. Obviously this is not a common problem with the Galaxy S6 Edge Plus, so it might be the result of a settings change you have made. The quickest way to test the theory will be to perform a factory reset - you can backup first if you want to.
If that doesn't solve the problem, it must be an issue with your WiFi or mobile data provider... but this is a very unlikely possibility.
Good luck with the problem.
nobnut said:
I haven't come across this problem before. It sounds like the kind of bug you might encounter if you are using a custom ROM or kernel. If you are, you could try flashing back to a stock build and see if the problem goes away.
If you are using a stock ROM and kernel, it sounds like you have tried almost everything and it might be time to perform a factory reset. Obviously this is not a common problem with the Galaxy S6 Edge Plus, so it might be the result of a settings change you have made. The quickest way to test the theory will be to perform a factory reset - you can backup first if you want to.
If that doesn't solve the problem, it must be an issue with your WiFi or mobile data provider... but this is a very unlikely possibility.
Good luck with the problem.
Click to expand...
Click to collapse
Thank you for your suggestions
At the moment I'm using Audax ROM and Kernel, but I had the same issue with the stock rom + arter97 kernel..
I had a look to the logcat, and by searching the errors on google I found other users in my same situation (with custom ROMs) I tried the fixes suggested but none of them worked
Same problem. Done most of the solutions provided. Nothing Works. Using Wanam Lite on SM-910C. Anyone could help. :-/