viber doesn't use the proximity sensor - Samsung Galaxy Nexus

Hi there I've just noticed that viber doesn't use the proximity sensor to turn of the screen when you talk does anyone know how to fix this?

no problems here.
The screen turns off whenever my hand covers the proximity sensors

did you change any config?

nope. what ROM are you running?

aokp

It doesn't actually turn off, I've noticed this too, what it does do, is turn the screen off, but not the backlight. So it's still wasting battery, and it bugs me cause I'm OCD about things like this! It's been bugging me for quite some time!

but is this due to aokp rom ?

Nhialor said:
It doesn't actually turn off, I've noticed this too, what it does do, is turn the screen off, but not the backlight. So it's still wasting battery, and it bugs me cause I'm OCD about things like this! It's been bugging me for quite some time!
Click to expand...
Click to collapse
Can you elaborate on that?

Viber
Hi,
This is a member of the Viber R&D Team!
If you are running Viber on a customized ROM, it may result in side effects. At this stage, due to the large variety of customized ROMs available, we support only the basic ones, such as CM7 and MIUI.
If you have any question about Viber - please feel free to ask.
Thank you,
Viber Team

Thanks for the help an reply really good customer service. I use aok :-(
Sent from my Galaxy Nexus using Tapatalk

alvespt said:
Thanks for the help an reply really good customer service. I use aok :-(
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
What device are you using exactly?
Have you tried testing the proximity sensor when using Stock ROM on your phone?
Also - have you made sure that inside Viber's settings the proximity sensor option is turned on?

Viber Team said:
What device are you using exactly?
Have you tried testing the proximity sensor when using Stock ROM on your phone?
Also - have you made sure that inside Viber's settings the proximity sensor option is turned on?
Click to expand...
Click to collapse
Using the Galaxy Nexus on stock ICS the screen turns off but the navigation buttons still are lighted up and that wastes a lot of battery

@rock7632 -
Have you checked the setting inside Viber that I've mentioned in my previous post?

Hi I have Viber 2.1.6 on HTC One X with original Rom 4.0.3 ...and I can not find any settings inside Viber for proximity senzor...
...during phonecalling from Viber it created problems, because screen is active...

petob said:
Hi I have Viber 2.1.6 on HTC One X with original Rom 4.0.3 ...and I can not find any settings inside Viber for proximity senzor...
...during phonecalling from Viber it created problems, because screen is active...
Click to expand...
Click to collapse
Hi,
Are you sure you couldn't find the proximity sensor option inside Viber's settings?
It should be inside More-->Settings
If you still can't find it, please contact our support team through this direct link: http://bit.ly/ukGVJ0, and they'll guide you through a solution (or log the error, and make sure it's fix in future versions).

On Razr I, intel cpu based phone, there is no proximity settings in latest viber app. And ofcurse screen doesnt turn off on call :/
Wysyłane z mojego XT890 za pomocą Tapatalk 2

Viber keeps the screen on during calls both on my stock s2 and stock nexus, and there is no proximity option in the settings menu.

We are planning to release a major update to Viber soon. Once released, please try it out and let us know if the problem persists. We'll be right here to receive your feedback.
Thank you in advance, and we apologize for the temporary inconvenience.

Viber Team said:
We are planning to release a major update to Viber soon. Once released, please try it out and let us know if the problem persists. We'll be right here to receive your feedback.
Thank you in advance, and we apologize for the temporary inconvenience.
Click to expand...
Click to collapse
I got answer from your support, that i should reinstall application
no comment
You give us much more helpful information
Wysyłane z mojego XT890 za pomocą Tapatalk 2

We try to give equally helpful support They might have misunderstood your problem slightly.
Anyway, we're right here (and staying here) to hear your feedback and comments

Related

Viber icon in status bar even at the end of a call

Even after the end of a call, the purple color Viber phone icon doesn't go off the status bar. When i swipe down on the screen, it shows "Call in progress" with the call duration frozen.
This has happened to me on more than 2 occasions; I tried uninstalling, and re-installing, but no joy.
Any thoughts?
That's a known viber app issue, same thing always happens on my Sony Arc. I usually just ignore it.
Sent from my HTC One X using Tapatalk 2
Rycon33 said:
That's a known viber app issue, same thing always happens on my Sony Arc. I usually just ignore it.
Click to expand...
Click to collapse
Thanks, bro
Viber
Hi,
This is a member of the Viber R&D Team!
C56X- What device do you have?
Thanks in advance.
Viber Team said:
C56X- What device do you have?
Click to expand...
Click to collapse
HTC One X
@C56X -
Thanks for the info.
Please note that Viber does not officially support your device yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/rqbZEw
However, we invite you to report this issue to our support team in the meanwhile, so they can take a look at it and hopefully solve it in the future
Here's the direct link: http://bit.ly/ukGVJ0

[Q] Navigation map inverted

Hi,
Network: Verizon
Device: Samsung Galaxy Nexus
Android Version: 4.1.1
Few weeks back I got updated to Jelly Bean, since then the map in my "Navigation" app sometimes show as inverted, can anyone please let me know how should fix it or if there are any updates.
If you need any more information I will be glad to update the thread.
Regards,
Arup
same thing happened to me actually..
it was after the app updated and it seems like it corrected itself after a couple days
arupsarkar said:
Hi,
Network: Verizon
Device: Samsung Galaxy Nexus
Android Version: 4.1.1
Few weeks back I got updated to Jelly Bean, since then the map in my "Navigation" app sometimes show as inverted, can anyone please let me know how should fix it or if there are any updates.
If you need any more information I will be glad to update the thread.
Regards,
Arup
Click to expand...
Click to collapse
same thing happened to me actually..
it was after the app updated and it seems like it corrected itself after a couple days
Click to expand...
Click to collapse
It will do that when you enter a tunnel or something (and thus the overall ambient light is decreased), Or put your finger on the brightness sensor while the navigation is on (try it) You either have a ROM that has an issue with brightness sensors, Or the brightness sensor on your phone is messed up/Covered up by something.
Tbh i really like the look of the inverted maps xD
Bewinxed said:
It will do that when you enter a tunnel (and thus the overall ambient light is decreased) You either have a ROM that has an issue with brightness sensors, Or the brightness sensor on your phone is messed up/Covered up by something.
Tbh i really like the look of the inverted maps xD
Click to expand...
Click to collapse
I think he means the direction is wrong...
like it faces on the screen the opposite way than you're actually going
You have to allow the compass to recalibrate itself. Go outside, turn on maps with GPS, and wave it around in figure 8s for a while.
Sent from my Galaxy Nexus using xda app-developers app
You checked "Yes this is a question"
Guess which subforum it belongs in?
Questions go in Q&A
Thread Moved
Thank you for your cooperation
Friendly Neighborhood Moderator
crixley said:
I think he means the direction is wrong...
like it faces on the screen the opposite way than you're actually going
Click to expand...
Click to collapse
A friend have the direction problem with his S-II, Someone have an idea forma a solution? I'm not sure will be related to the compass because it happen only when si in navigation mode, not when he use maps...
Edit: solution found for him, simply removed the battery...

[Mod][Fix]Lockscreen fix when accessibility option is enabled

Hi guys! Again here's another mod from me. This mod should fix the lockscreen issue when any apps requiring accessibility is enabled.
Just push the apk in
Code:
/system/app/
replacing the original one with this mod.
Sorry guys was not able to make a flashable zip my phone is the only device I have right now to access the internet(no computer) so would really appreciate it if someone can make a flashable zip for me
Update
Added flashable zip
Download here
And as always... Deodexed ROMs only. Don't flash in a pure stock odexed ROM it will break your lockscreen.
Riyal said:
Hi guys! Again here's another mod from me. This mod should fix the lockscreen issue when any apps requiring accessibility is enabled.
Just push the apk in
Code:
/system/app/
replacing the original one with this mod.
Sorry guys was not able to make a flashable zip my phone is the only device I have right now to access the internet(no computer) so would really appreciate it if someone can make a flashable zip for me
And as always... Deodexed ROMs only. Don't flash in a pure stock odexed ROM it will break your lockscreen.
Click to expand...
Click to collapse
Great, was waiting for this one. thx.
Hi! Added flashable zip
Question....
May I ask what were the issues with the apps using open accessibility? I use Knock2+
and if I need the fix, which out of the two attachment do I need? Do I need to flash both of them? or just the second one as the file name suggested its purposes?
Just come across this thread from a post on the trickdroid forums...
This is great....just installed the zip on my HTC One and its seems to be working perfect at the moment....if theres any issues I'll post up after a days use...
It's made me a happy chappie tonight..:good:
Cheers
M.
Cloudyherb said:
May I ask what were the issues with the apps using open accessibility? I use Knock2+
and if I need the fix, which out of the two attachment do I need? Do I need to flash both of them? or just the second one as the file name suggested its purposes?
Click to expand...
Click to collapse
For instance, I have a pebble watch that requires the pebble app. The pebble app requires that you start the service for pebble in the accessibility settings. So an option at the top under services you have to turn on. As soon as you turn on one of the services there - as far as I know any service not just pebble - it will make the lockscreen broken. So from that point on just touching the lockscreen anywhere will unlock the device. You don't have to swipe up the lock or clock anymore. And you can't pull any of the app icons up to load into those. It just unlocks the device as soon as you touch the screen. The big problem with this is if the phone is ringing in your pocket. As you pull it out of your pocket and it rubs against your leg/pants, it will unlock/answer the call. Now occasionally I don't want to answer the phone. Its been a big problem.
Thanks to the OP for this fix. You are a life saver! Or at least a sanity saver.
sponge_worthy said:
For instance, I have a pebble watch that requires the pebble app. The pebble app requires that you start the service for pebble in the accessibility settings. So an option at the top under services you have to turn on. As soon as you turn on one of the services there - as far as I know any service not just pebble - it will make the lockscreen broken. So from that point on just touching the lockscreen anywhere will unlock the device. You don't have to swipe up the lock or clock anymore. And you can't pull any of the app icons up to load into those. It just unlocks the device as soon as you touch the screen. The big problem with this is if the phone is ringing in your pocket. As you pull it out of your pocket and it rubs against your leg/pants, it will unlock/answer the call. Now occasionally I don't want to answer the phone. Its been a big problem.
Thanks to the OP for this fix. You are a life saver! Or at least a sanity saver.
Click to expand...
Click to collapse
wow is was wondering about this today i noticed that i no longer have to drag the icon up to unlock it. thanks for clearing this up.
sweet! didn't realize it was a problem with the base
thanks bro
Sent from my HTC One using Tapatalk 4 Beta
stuck on loading screen
I flashed the zip in the download link and now my phone won't go past the "starting apps" screen after boot and before lockscreen shows.
I even reflashed the rom (dirty) and it won't work. Can you make a flashable file which puts the original files back so I can adb push it on my One.
I am on Trickdroid 5.5.1. by the way.
Please Help.
Columbo4Life said:
I flashed the zip in the download link and now my phone won't go past the "starting apps" screen after boot and before lockscreen shows.
I even reflashed the rom (dirty) and it won't work. Can you make a flashable file which puts the original files back so I can adb push it on my One.
I am on Trickdroid 5.5.1. by the way.
Please Help.
Click to expand...
Click to collapse
I have replied to your PM. Please check your inbox
I can't reproduce your problem so please try wiping dalvik cache or deleting the folder /data/data/com.htc.idlescreen.base/
And if it still persists try doing a factory reset instead.
Doing a dirty install of the Trickdroid ROM should have restored the original lockscreen app so I'm pretty sure it's something to do with your dalvik-cache.
Just try wiping dalvik-cache for now it shouldn't delete anything so it's safe.
So I guess the fix can only be used if you're rooted and that sucks cause I am not
Sent from my HTCONE using xda premium
MRFERRARI23 said:
So I guess the fix can only be used if you're rooted and that sucks cause I am not
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Yes no other way at all sorry Better issue this bug to HTC then and wait for an update with a fix.
Is there a specific place to report these bugs? I mentioned this issue to them on the technical support form, but I'm not sure if it's the right place.
Either way, thanks for the help OP.
Yes it should be on the technical support.
@OT
triple 9 thanks haha hope it's my lucky day.
Riyal said:
Yes it should be on the technical support.
@OT
triple 9 thanks haha hope it's my lucky day.
Click to expand...
Click to collapse
Confirmed working on the Sprint HTC One with ViperROM, can I post this on the Sprint HTC One forum?
Go ahead I hold no ownership on any of my mods Everytime I post something for free in the internet I consider it already to be freely useable by anyone. So feel free to redistribute, remodify or whatever you want to do with it
Riyal said:
Go ahead I hold no ownership on any of my mods Everytime I post something for free in the internet I consider it already to be freely useable by anyone. So feel free to redistribute, remodify or whatever you want to do with it
Click to expand...
Click to collapse
Thanks, I will give you credit anyways!
I was wondering if this mod would negate the option to disable exchange server security? I've flashed trickdroid and applied this mod, but now my exchange server is requiring a password/pin on unlock. I'd like to be able to disable this when I'm home in tasker and I have that setup, but now it doesn't work. I think it was this mod that removed that feature from TrickDroid. Do you know the answer?
@Riyal since installing this fix I have a problem with the proximity sensor while on a call. Sometimes the screen goes black as soon as the call connects and the screen doesn't come back on. Sometimes the screen doesn't turn off when I hold the phone to my face and sometimes it does turn off but won't turn on again.
Is this problem related to this fix? Is anyone else experiencing this?
Sent from my HTC One using xda-developers app
sponge_worthy said:
I was wondering if this mod would negate the option to disable exchange server security? I've flashed trickdroid and applied this mod, but now my exchange server is requiring a password/pin on unlock. I'd like to be able to disable this when I'm home in tasker and I have that setup, but now it doesn't work. I think it was this mod that removed that feature from TrickDroid. Do you know the answer?
Click to expand...
Click to collapse
Hi! I'm not sure about the exchange server mod as I am not using it. I'll take a look at the mod soon and see what was modified on it and see if it conflicts with my mod.
And by the way could you give me a tutorial/guide on how and where to get an exchange account to test? Pardon but I don't really use that feature at all.
Anyways I am using exchange activesync on my phone right now but only using live.com account. And I'm not sure if having a private exchange server is needed.
tdingene said:
@Riyal since installing this fix I have a problem with the proximity sensor while on a call. Sometimes the screen goes black as soon as the call connects and the screen doesn't come back on. Sometimes the screen doesn't turn off when I hold the phone to my face and sometimes it does turn off but won't turn on again.
Is this problem related to this fix? Is anyone else experiencing this?
Sent from my HTC One using xda-developers app
Click to expand...
Click to collapse
Hi! Proximity sensor works perfectly well with my mod here. I have already called a number of times with the mod installed and I am also using tasker and I can't reproduce the problem

[Q] Xperia Acro S - Proximity Sensor problem after update to JellyBean

Dear all
After one month using my Xperia Acro S updated to JellyBean I realized that the proximity sensor is not working.
During a call the screen doesn't turn off avoiding touch on the screen, but before the update, with ICS, it was working very well.
What I tried to do, but without result:
1st recover JB by device
2nd recover JB by PC Companion
3rd flash JB by Flashtool
I tried to Google, but I didn't find a solution to fix this problem for Acro S...
I tried *#*#7378423#*#* and tested the sensor, and it always shows "off"
I tried lots of softwares that make changes to the sensor, and they don't work (recognize the sensor?)
After sometime I realized that the problem may be the JB and not the device, as the ICS was working, so I flashed to ICS again to confirm. As I expected the sensor was working properly: I typed *#*#7378423#*#* again and checked the sensor and it changes to "on" everytime I cover the sensor.
Somebody is experiencing the same problem? Could you fix it? How?
Thanks...
marceloyudi said:
Dear all
After one month using my Xperia Acro S updated to JellyBean I realized that the proximity sensor is not working.
During a call the screen doesn't turn off avoiding touch on the screen, but before the update, with ICS, it was working very well.
What I tried to do, but without result:
1st recover JB by device
2nd recover JB by PC Companion
3rd flash JB by Flashtool
I tried to Google, but I didn't find a solution to fix this problem for Acro S...
I tried *#*#7378423#*#* and tested the sensor, and it always shows "off"
I tried lots of softwares that make changes to the sensor, and they don't work (recognize the sensor?)
After sometime I realized that the problem may be the JB and not the device, as the ICS was working, so I flashed to ICS again to confirm. As I expected the sensor was working properly: I typed *#*#7378423#*#* again and checked the sensor and it changes to "on" everytime I cover the sensor.
Somebody is experiencing the same problem? Could you fix it? How?
Thanks...
Click to expand...
Click to collapse
Try to reFLASH again and do a total wipe clean from recovery, including dalvik's cache.
FTF file
zupadroid said:
Try to reFLASH again and do a total wipe clean from recovery, including dalvik's cache.
Click to expand...
Click to collapse
Hi Zupa... thanks for the suggestion!!
Do you have the original Xperia Acro S JB FTF file to send to me?
I want to try with the original one
Thanks
marceloyudi said:
Hi Zupa... thanks for the suggestion!!
Do you have the original Xperia Acro S JB FTF file to send to me?
I want to try with the original one
Thanks
Click to expand...
Click to collapse
Yes : http://forum.xda-developers.com/showthread.php?t=2302477
Still with problems
zupadroid said:
Yes : http://forum.xda-developers.com/showthread.php?t=2302477
Click to expand...
Click to collapse
Hi...
I proceeded as suggested and it still doesn't work. I flashed with the new Flashing tool 0.9.11.0 by Bin4ry and Androxyde and the sensor is not working.
I flashed to ICS again and it works very well, I don't understand...
What I noticed is that the sensor seems to work together with the light sensor, in the same position. Somebody knows if the sensor is the same? In the ICS the proximity sensor works when I cover the same part of light sensor (left from the speaker) and not in the right between the speaker and front camera.
Any other suggestions?
Thanks
Nobody knows?
Nobody has other suggestions?
marceloyudi said:
Nobody has other suggestions?
Click to expand...
Click to collapse
just flash back to ICS and check, if its the same, may be you have got your sensor damaged..
...
bluechip850 said:
just flash back to ICS and check, if its the same, may be you have got your sensor damaged..
Click to expand...
Click to collapse
Hi bluechip850
Thanks for the suggestion, but as I told I tried this and the sensor is working well in ICS.
By the way, I'm still using ICS due to the sensor is not working in JB.
I really would like to use JB, mainly because I noticed that the battery in ICS gets low faster that JB.
Any other suggestions?
Thanks
Wait for the new update.
skywalkerdroid said:
Wait for the new update.
Click to expand...
Click to collapse
can confirm it is JB 4.1 and 4.2 bug, xperia s lt26i offical Sony JB, xperia z1 offical Sony JB , proximity sensor off and stay off all the time, prestigio 4044 same, prestigion 5050 same, samsung s4 same. Don't have more phones to try, will test as I get any other in hads. So far only bug I found in JB but anoying one as it dont lock screen when call is on and phone on ear, so I press a lot of buttons during talk
.
Fanta_BH said:
can confirm it is JB 4.1 and 4.2 bug, xperia s lt26i offical Sony JB, xperia z1 offical Sony JB , proximity sensor off and stay off all the time, prestigio 4044 same, prestigion 5050 same, samsung s4 same. Don't have more phones to try, will test as I get any other in hads. So far only bug I found in JB but anoying one as it dont lock screen when call is on and phone on ear, so I press a lot of buttons during talk
Click to expand...
Click to collapse
Fanta_BH
My phone is a Xperia Acro S (LT26W) JB 4.1.2
I need to power the screen off manually every time I want to answer or make a call. I just fast press the button of the power just to turn off the screen and avoid to touch the screen accidentally.
When I finish the call I also need to fast press the button again so I can access the screen options again.
It is so boring, but I just found this solution until the next update. I didn't find any other solution or software to change or turn on the proximity sensor. I actually found some scripts, but I don't have experience to change the system and I don't want to kill my phone, so I decided to wait to the next update instead of downgrade to ICS again, which was working well, because of the improvements that JB provides.
If you find some information that can fix the proximity sensor, please tell me...
Fanta_BH said:
can confirm it is JB 4.1 and 4.2 bug, xperia s lt26i offical Sony JB, xperia z1 offical Sony JB , proximity sensor off and stay off all the time, prestigio 4044 same, prestigion 5050 same, samsung s4 same. Don't have more phones to try, will test as I get any other in hads. So far only bug I found in JB but anoying one as it dont lock screen when call is on and phone on ear, so I press a lot of buttons during talk
Click to expand...
Click to collapse
can add now, smart screen off when enabled, do job, proximitiy sensor starts working again. get it here from forum or from playstore on playstore it is taged as Smart Screen off lite.
---------- Post added at 10:52 PM ---------- Previous post was at 10:14 PM ----------
Fanta_BH said:
can add now, smart screen off when enabled, do job, proximitiy sensor starts working again. get it here from forum or from playstore on playstore it is taged as Smart Screen off lite.
Click to expand...
Click to collapse
well forgot to say, was searching on net and got that infor about software "smart screen off" it is made by someone from here on XDA. Decided to give it a try, installed it from playstore, it makes one icon on deesktop which function like simple button, when u press button proxim. sensor starts working and acting normaly, when u press it again it switch off so proxim sensor again not working as it is JB bug so JB keeps it off all the time when there is no other software which will enabled it directly, so go go try it I hope it will work for you as well.
Didn't work
Fanta_BH said:
can add now, smart screen off when enabled, do job, proximitiy sensor starts working again. get it here from forum or from playstore on playstore it is taged as Smart Screen off lite.
---------- Post added at 10:52 PM ---------- Previous post was at 10:14 PM ----------
well forgot to say, was searching on net and got that infor about software "smart screen off" it is made by someone from here on XDA. Decided to give it a try, installed it from playstore, it makes one icon on deesktop which function like simple button, when u press button proxim. sensor starts working and acting normaly, when u press it again it switch off so proxim sensor again not working as it is JB bug so JB keeps it off all the time when there is no other software which will enabled it directly, so go go try it I hope it will work for you as well.
Click to expand...
Click to collapse
Fanta_BH
I wouldn't like to say that just the software couldn't work.
The proximity sensor in actually disabled in my phone. I need to turn it on first to use any software to manage the proximity sensor. I thought that this software you told would enable the sensor, not just manage it.
Anyway thanks, if you have another suggestion I would be pleased to try
It seems like somewhere in the system a value to have the proximity sensor on during a call is set to off, find where its located and copy it over from ICS to jb and you should be good to go
Sent from my SGH-I747 using xda app-developers app
Instruction
thanitos said:
It seems like somewhere in the system a value to have the proximity sensor on during a call is set to off, find where its located and copy it over from ICS to jb and you should be good to go
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanitos
Nice idea, but can you explain or send a link how to access the system and make this changes?
Thanks
This is just an idea, if someone has a build.prop on the same phone and same version that has no issues with proximity post it here then OP flash to jb delete your build.prop and paste theres in your system folder. Else you could try copying your build.prop from ICS and pasting it in jb. Supposably that is where the issue lies on some phones. You may also want to flash a jb firmware that isn't stock, any ROM from the xperia s section should work. For editing the build.prop you need root and a root browser then go into system and at the bottom is build.prop. you may also want to read your build.prop and see if there are any lines for proximity in there
It seems as though you're not in touch with the android system, no offence, so I'd take the easy route and flash a jelly bean firmware from the across s section, this should work perfectly fine for you because its simply the stock ROM that's the issue and had a regression and most devs will fix this in their ROM.
How to root
http://forum.xda-developers.com/showthread.php?t=1834291
[Tut] Rooting the Acro S the easy way
Sent from my SGH-I747 using xda app-developers app
Maybe it works
thanitos said:
This is just an idea, if someone has a build.prop on the same phone and same version that has no issues with proximity post it here then OP flash to jb delete your build.prop and paste theres in your system folder. Else you could try copying your build.prop from ICS and pasting it in jb. Supposably that is where the issue lies on some phones. You may also want to flash a jb firmware that isn't stock, any ROM from the xperia s section should work. For editing the build.prop you need root and a root browser then go into system and at the bottom is build.prop. you may also want to read your build.prop and see if there are any lines for proximity in there
How to root
http://forum.xda-developers.com/showthread.php?t=1834291
[Tut] Rooting the Acro S the easy way
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I actually have my phone rooted, but the system folder just shows PIM folder
Should I do something more than just root?
----edit----
Sorry I didn't see, I should have root browser... installing to try
I'd just flash a jb ROM from the acro s section that's not stock
In my sony Ion I have two Proximity tweaks in the rom I use, try adding these and see if it helps at all,
ro.lge.proximity.delay=25
mot.proximity.delay=25
Sent from my SGH-I747 using xda app-developers app
marceloyudi said:
Fanta_BH
I wouldn't like to say that just the software couldn't work.
The proximity sensor in actually disabled in my phone. I need to turn it on first to use any software to manage the proximity sensor. I thought that this software you told would enable the sensor, not just manage it.
Anyway thanks, if you have another suggestion I would be pleased to try
Click to expand...
Click to collapse
Well at my lt26i it is same, prox sensor in settings is always off, so it is disabled and can not be enabled, but still software I said somehow when I press button for software enable it do enable prox. sensor and it working but its controled by software not by systme itself. And I dont getting it as with software enabled system still showing prox sensor as disabled.
Fanta_BH said:
Well at my lt26i it is same, prox sensor in settings is always off, so it is disabled and can not be enabled, but still software I said somehow when I press button for software enable it do enable prox. sensor and it working but its controled by software not by systme itself. And I dont getting it as with software enabled system still showing prox sensor as disabled.
Click to expand...
Click to collapse
Thanks for the explanation, but in my Acro S it didn't work very well. In my oppinion is more effective to press power button quickly to turn off the screen, because sometimes the software seems that is not running and it doesn't turn the screen off automatically....
thanitos said:
I'd just flash a jb ROM from the acro s section that's not stock
In my sony Ion I have two Proximity tweaks in the rom I use, try adding these and see if it helps at all,
ro.lge.proximity.delay=25
mot.proximity.delay=25
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanitos
Where I should type this lines? Can you give me extra instructions?
I have boot browser in my phone now

OpenKirin AOSP Collection

Project will reborn as a new Project openkirin banned my work
Will Push them new
Bug: proximity sensor for case open/close are not working in this ROM.
Aside from this, things have been very smooth and stable, and it's s great start
CrazyPeter said:
Bug: proximity sensor for case open/close are not working in this ROM.
Aside from this, things have been very smooth and stable, and it's s great start
Click to expand...
Click to collapse
Working on it after pie release
I remember you from my old z2 times. Now i have Samsung tab s3, but thinking about switching to mediapad m5 as development on my current tab is very little. happy to see you here. thanks for your effort
I installed your Resurrection Remix a couple of weeks ago. I am really enjoying it, and not running into many problems, aside from the aforementioned magnetic case not turning on and off the tablet. I do want to ask you though (and forgive me, I'm not super tech savvy in regards to this, so my questions might be a bit dumb), does the kernel you use allow for over and under clocking? I've tried setting this in "Kernel Adiutor" and the cpu speeds I set never stick.... however changing the governors does. And does your kernel allow for fast/quick charge?
Regardless, thanks a ton for bringing a bunch of ROMs to the M5, I really appreciate it!
*Edit*: I just wanted to add, that one problem I am running into is that sometimes my bluetooth crashes. Seems to be random, and only starts working again when I reboot the system.
@rcstar6696
Thanks to you and your Friends for your good work !
This is a nice AND simple AND safe way to bring RR(1 of 4 from you) on Huawei OREO devices.
I hope my Donation help you !
JamesBott said:
@rcstar6696
Thanks to you and your Friends for your good work !
This is a nice AND simple AND safe way to bring RR(1 of 4 from you) on Huawei OREO devices.
I hope my Donation help you !
Click to expand...
Click to collapse
Thank you very much
@rcstar6696
deleted
JamesBott said:
@rcstar6696
if you need look here in DE
https://www.android-hilfe.de/forum/...3359/huawei-oreo-rr-los-openkirin.886228.html
Click to expand...
Click to collapse
Please delete this thread i don't want to mess with android Hilfe again
If you don't delete it i report the thread. Thank you
Do these ROMs work on both LTE and Wi-Fi only variants of the tablet?
Likely a problem with ASOP, but WiFi only tablets have an annoying amount of phone like features that can be disabled (or detected and removed);
No SIM card icon
No SIM card message
Volume buttons control ringtone , should control media volume
I'm sure there are other annoyances
CrazyPeter said:
Likely a problem with ASOP, but WiFi only tablets have an annoying amount of phone like features that can be disabled (or detected and removed);
No SIM card icon
No SIM card message
Volume buttons control ringtone , should control media volume
I'm sure there are other annoyances
Click to expand...
Click to collapse
I also have an Wifi only Mediapad and long searched for a fix for this.
A few days ago I found an answer and added this line to my build.prop:
Code:
ro.radio.noril=yes
Especially the "No SIM card - No service" text in the notification tray bother me and after adding the line it was gone and also the Settings for mobile networks disappeared.
I could deactivated the Phone and Messenger App, I don't know if it was impossible before.
About the Volume buttons, I am not sure, cuz I use the App "Volume Pie" that's default controls media volume anywhere.
Hmm... Why exactly did they ban your work?
Marcopoloy13 said:
I also have an Wifi only Mediapad and long searched for a fix for this.
A few days ago I found an answer and added this line to my build.prop:
Code:
ro.radio.noril=yes
Especially the "No SIM card - No service" text in the notification tray bother me and after adding the line it was gone and also the Settings for mobile networks disappeared.
I could deactivated the Phone and Messenger App, I don't know if it was impossible before.
About the Volume buttons, I am not sure, cuz I use the App "Volume Pie" that's default controls media volume anywhere.
Click to expand...
Click to collapse
Thanks, that fixed the SIM card messages, just need a patch to get sensible tablet control of the volume buttons.
I would seriously avoid this, there is something very bad smelling about OpenKirin.
The developers want to remain anonymous, there is no source code for audit, and of you ask awkward questions along these lines on the telegram channel they suddenly get very abusive.
All signs that something is not entirely right and there is something to hide.. (included malware or data harvesting???).
Huawei is now a huge player, and therefore a prime candidate for mass day harvesting from anyone that flashes a closed source ROM like this.
Anyone knows how to root after installing LOS?
Usually I would use TWRP to get it, but the stock recovery does not support it.
Gesendet von meinem CMR-AL09 mit Tapatalk
---------- Post added at 06:13 PM ---------- Previous post was at 06:10 PM ----------
CrazyPeter said:
I would seriously avoid this, there is something very bad smelling about OpenKirin.
The developers want to remain anonymous, there is no source code for audit, and of you ask awkward questions along these lines on the telegram channel they suddenly get very abusive.
All signs that something is not entirely right and there is something to hide.. (included malware or data harvesting???).
Huawei is now a huge player, and therefore a prime candidate for mass day harvesting from anyone that flashes a closed source ROM like this.
Click to expand...
Click to collapse
https://openkirin.net/about/
That doesn't look like they try to hide something
Gesendet von meinem CMR-AL09 mit Tapatalk
Signor Rossi said:
[/COLOR]https://openkirin.net/about/
That doesn't look like they try to hide something
Gesendet von meinem CMR-AL09 mit Tapatalk
Click to expand...
Click to collapse
Obviously nobody actually knows these people, I was looking for a source code link to audit and compile...
@Signor Rossi it's actually the same procedure as from this this thread https://forum.xda-developers.com/mediapad-m5/how-to/root-root-guide-huawei-mediapad-m5-t3786157.
What's the difference between the ROMs?
Well, check the ROMs own development pages. Openkirin simply build them for us, that's all. They are not "making" them.
Gesendet von meinem HTC U11 life mit Tapatalk

Categories

Resources