yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] aybarrap1:
For me I have tried it both on and off. Could not discern any major hit on the battery life. However, I did notice a slight improvement when I turned off the approach option (moving your hand within 6 inches). My phone kept turning on the screen all the time since it resides next to me at my work desk. While the option was neat I found that after i turned the approach option turned off, just slightly disturbing the phone by touch was enough to light up the screen for notifications
[Samsung Galaxy S7 Questions and Answers] wisepds:
First, sorry for my english.

My galaxy S7 have this problem (Video).

Video is in Spanish, but i think the malfunction is obvious...touch screen.

anybody with this failure?

Regards from Seville.

https://www.youtube.com/watch?v=3pK8cxZqaZU#t=191
[Samsung Galaxy S7 Edge Questions and Answers] DroidBiteApple:
Hi,

Coming from a much smaller device (iPhone 5s), i would like to know if it is possible to handle the S7 Edge one handed.

I recently tried a friend's Nexus 6P and as amazing as it is, i couldn't type a message using only one hand without feeling that the phone is going to drop any second, and all of those far stretches with my thumb made my hand tired.

Cheers!
[Samsung Galaxy S7 Edge Questions and Answers] mvpulsts:
In settings look under advanced features for "one handed operation" play around with that and see if its something that helps
[Samsung Galaxy S7 Edge Questions and Answers] h3ck:
Honestly, coming from an iPhone 5s ( 4 inch phone), it's gonna feel unwieldy. It will most likely feel "too big", however this is probably the most ergonomic "big" phone you will find. I used to have the note series (note 2, 3, 4, not 5), and that was always my biggest gripe. You get used to it but ultimately there was always a moment where I would feel that it was too big (wouldn't fit in cup holder, needed special mount, etc.) I recently switched back to a "normal" sized phone and had the s6 for about a year.

Recently, I switched to the s7 edge. Results: I absolutely love it. Can still one hand the phone, but also have bigger screen. It feels like cheating. Big phone in "normal" phone footprint. To me, Samsung hit a home run in design.

TL;DR - That was a long way of saying, go to your local best buy or electronics store and hold it in your hand. Feel the shape, etc. But ultimately me doing that and then owning it, I haven't regretted it. Btw it fits in a cup holder. [emoji2] Lol
[Samsung Galaxy S7 Edge Questions and Answers] DroidBiteApple:
Thank you very much! The "long" response is much appreciated.

You're probably right, i just need to try it out myself.

This phone seems close to perfect to me, if it only had usb-c, better speakers and faster updates it would have been perfect... I'm going to buy i anyways =]
[Samsung Galaxy S7 Edge Questions and Answers] h3ck:
Honestly, I understand the speakers and faster updates. But at this point the benefits of TouchWiz outweigh the benefits of stock to me. Speakers will always be a pain point as long as they are not boom sound lol

As far as USB-C, I will take fast charging everyday over USB-C. When they make a USB-C fast charge, then sign me up.

But honestly, I've been around the phone game a while (see sig lol). This is definitely as close to perfect as you can get. The notoriously iPhone leaning The Verge site even rated S7 edge higher than the iPhones. Take that for whatever it's worth. Good luck, hope you love it. I do.
[Samsung Galaxy S7 Edge Questions and Answers] tango007:
Yes you can

Its not related to the size of ur smartphone . The exact issue with you , is you are not use to with big screen size . Yes it will take some time but you can use it by one hand :o:o:o
[Samsung Galaxy S7 Edge Questions and Answers] nudawa:
I can comfortably use the device with one hand on many main task like making calls, quick short messages, browse the webs, browse the device... despite the fact that I am a fairly small person (man, 163cm). There is nothing, really, nothing you can complain about this phone. It runs Touchwiz but it is as fast as the stock Android, no more bloatwares and some benefits of touchwiz like edge screen is great. The grip is great, no more discomfort from sharp edges, the device sits nicely in your hands like it belongs there, you will have a hard time putting it down because it feels so good.

Coming from iPhone 6 and I'm absolutely fell in love with the S7e.
[Samsung Galaxy S7 Edge Questions and Answers] DroidBiteApple:
Sorry for the newbie question but how is the s7 outweigh stock Android?
[Samsung Galaxy S7 Edge Questions and Answers] nudawa:
It has some Samsung's exclusive-built factors like the edge screen, always on display, edge panels, etc...
[Samsung Galaxy S7 Edge Questions and Answers] CPT.YU:
Ok so I'm one of those people that like to use the phone while charging (don't ask why)...but anyways since i do this, I disable fast charging to prevent overheating and overall battery damage. However, whenever i disable it and check the notification bar it says its still fast charging. I try this process over and over and it always switches back to fast charging almost immediately:eek::eek::eek: anyone else having this issue? Might just have to take it back for a new one but it just annoying cause i already set my phone up with all my stuff...

lmk, and thanks to everyone ahead of time!

Edit: But other then this issue im really having no other problems and really loving this phone!
[Samsung Galaxy S7 Edge Questions and Answers] Leelouster:
Have you tried disconnecting your phone while it's charging, THEN disabling the fast charging and plugging it back in to see if that works? Maybe it's not letting you because it's already in the "Fast Charge" state to begin with. :)
[Samsung Galaxy S7 Edge Questions and Answers] Juuls:
If you use your phone while charging 'Fast Charge' is disabled according to the manual, so no need to disabled it, maybe that gives a conflict (bug in programming e.g.).
[One (M9) Q&A, Help & Troubleshooting] lcsboy:
It seems that Sense 7 remove this feature, but my Butterfly 2 (Sense 6) has this great feature.

So Android 6 (Sense 7) must no support this feature.

I tried AndroidTetherTool, but it can not work for M9.

Is there any one can help me to enable this function?
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Apparently adb "settings put global tether_dun_required 0"
[One (M9) Q&A, Help & Troubleshooting] lcsboy:
After I tried the command and reboot the system, it doesn't work.
[One (M9) Q&A, Help & Troubleshooting] shivadow:
Not surprising in the slightest.. Htc butcher the roms. In that case I doubt it will ever work on htc unless an app comes along with a workaround.
[One (M9) Q&A, Help & Troubleshooting] lcsboy:
Actually, hTC can support Tether for Wifi.

There is a app Reverse Tethering to work in my M9, if set to mode 1.

But it is not freeware, and many App can not work in this network.

Is anyone to have better suggestion or solution?
[Moto G Q&A, Help & Troubleshooting] Spleeny97:
Hello

My phone is a MM 1032 and carrier is SFR (France)

Like said in the title I cannot share my internet with PC

Chrome says DNS problem BUT when I directly put IP address in the browser it said "connexion too long"

I have tested:"

"tether_dun_required > 0"

Set DNS to 8.8.8.8 & 8.8.4.4

Added DUN in my apn

Set a DUN only apn

Changed my phone's ROM"

With another carrier > it works

With my SIM card in another phone > it works

If I plug USB cable > it works....

I really don't understand what is the problem
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
This will allow you to type normally while in a call, without the numbers being locked on in other applications. I could not find this anywhere so I did so tinkering and found this key to be the problem. I saw many other people that had the same problem here is the fix. Quite simple.

Just change the following key.

\ HKLM\Software\OEM\PhoneSetting\

“enablekeyboardmaping” to 1

Update. this fix is not currently working
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Wow nice tips!

Was wondering how to get rid of this in my rom.

This was very helpfull

EDIT: Didn't worked for me. Tried some different typo but still no luck :/
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
no problem, thought I had to share it would only be fair.
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Can you maybe elaborate a bit more you tweak? I am maybe missing something :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
Nope, this is not working

Either 1 or 0, DWORD value
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
oh man.. are we close to finding a fix?!?
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
this worked for me. I am running

WM6 5.2.1620 build 18125.0.4.2

ROM 3.61.502.1

the AT&T version

after I changed this it worked right away no reset needed
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
post a cab please
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
i dont see this in the reg at all.....
[8525, TyTN, MDA Vario II, JasJam ROM Development] mcorrie1121:
Might have to create it.

It's already built into the ROM im using so I can't check.
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
before i changed this key it did not work after i changed it it did. so i just changed it back and the numbers didnt come up. i will post the other keyboard cab i found as soon as i can.

i thought i had it

i will also try setting to 0 and soft rebooting just to make sure.
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
Can you re-confirm the key, sans typos (no offence thepcguy85 :) )
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
after reboot the keys did not revert back. so now i am puzzled, l also loaded this cab with keyboard mapping. please note this cab is only for the AT&T 8525. but i am not sure if it was this cab or not.

we may be able to pull the setting out of this cab if it is the fix.
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
The cab is the same old 8525 keyboard mapping fix.

The key referenced in the OP has typos at the very least.

The ROM referenced in post #7 is the latest AT&T ROM, in which the problem has been fixed.
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
it was not working when i first Flashed the ROM this is however to the best of my knowledge.

could you be of help vp3g?
[8525, TyTN, MDA Vario II, JasJam ROM Development] mcorrie1121:
Many many people have asked him what he did in his 3.61 rom thread. You may read his full response there, but, in short, he cannot replicate it.
[8525, TyTN, MDA Vario II, JasJam ROM Development] EQUiLiiBRiUM:
I checked to see if this would work but my OEM/PhoneSettings Doesn't even have registry key as An Option.

If your saying This , Then that means it has more to Do with Just the Build. I thought it Was the Build that The vp3G ROM was using that corrected the Error but if Fun_Key ROM is using the same Build than It's more than Just the Build .I"ll try Combing Over the Registry Keys in the vp3G ROM and then maybe get some Answers. I"m sure it's been done But what else can we do right now....
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
Right now...load down vp3G's ROM and try and pull out as much of the AT&T as I can!
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
i dont think funkeys is based on 3.61 cuz i was diggin thru the reg and found 3.60 as a ver not 3.61.....hmm
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
I made some mix, but most part should come of 3.61. When I first built my rom there were some issue that denied me to use a full 3.61 through pandora.

But this is in fact a good hint which could allow me to troubleshoot the key mapping issue.
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
i hope this helps you fun_key maybe try rebuilding using just 3.61 as base because i really do like your rom and wish to use it! good luck mate!
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Just did it, but there is still this °§#@#°@#°#@ keyboard mapping bug. It something I could easily live with; but having it fixed would be better!
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
Does this happen on the official WM6 rom as well, or only the cooked ones?
[8525, TyTN, MDA Vario II, JasJam ROM Development] ljinsane:
WTF:confused: ..is just a simple reg editcome on and try
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
if u would read thru the entire thread ud see its just not a simple reg edit.. so "come on and try......reading"
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
Yo, did y'all get this working yet? It's been 24 hours...

Let's just say if it is a reg key, I will gladly consume my Hermes one microchip at a time. :D

*takes penalty for "taunting"
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
its not a reg key.. ive spent hrs comparing them
[8525, TyTN, MDA Vario II, JasJam ROM Development] juzzie:
If it's not a reg key, and the latest Rom's are free of this bug - then it has to be keyboard drivers (some dll or similar files that windows mobile is using). We need to ask a profi in Windows CE platform to recommend the files worth looking at in Windows OS itself. Then we can copy newer drivers (from newer ROMS) to our phones and be done with it. I wonder if there is anybody who knows Windows CE that well:confused:
[8525, TyTN, MDA Vario II, JasJam ROM Development] thepcguy85:
so if its not a reg key how about the phone app. that could be a good start
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
this seems to be the ONLY 3.61 rom that doesnt have this issue tho.. and there are a few based on the 3.61 base that are out.. anyone wanna flash the offical 3.61 bloatware ver and see if the problem is part of that rom too?
[8525, TyTN, MDA Vario II, JasJam ROM Development] its right:
i don't have a device to test, but i will try to help (any time people need help, we should work together), so who wants to test if it by registries, get these steps to make sure:

- download the rom in which this issue has been fixed.

- export these keys: HKEY_CR, HKEY_CU, and HKEY_LM (the main 3 keys) using any reg app

- save the exported files to the SD.

- flash the rom in which the issue is there.

- import the exported files one by one to know which one will fix this (in case of the issue done by the registries).

if you found the reg file will fix this, copy it to your deskyop, right click, then remove the have of the keys, then test it again (of course after formating to get the issue again), if it work, then delete some of the half keys you have kept, and so on.

i hope these steps are clear, and by this i can manage any registry issue in my releases ;).
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
No need... that's where the fix originated.
[8525, TyTN, MDA Vario II, JasJam ROM Development] drutort:
so has more light been shinned on this issue? What kind of testing has been conducted? comparing versions of drivers and applications along with reg settings... thats as extensive as i think it can get... nothing else there could cause such a problem.

good way to start i would think is from the end and work back... start with the application, then reg or the drivers/application versions

it can be though the keyboard mapping or whatever is responsible for the button mapping as well.

No need to look through whole registry and at every file… unless someone randomly placed some file that works as a “live” fix or more of a hack then that is a total different issue.

I think though something like a hack would be a good cheap and temp alternative for now?
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
@drutort: With this and other posts you seem to be flush with ideas of how things should be done around here, however may I remind you that XDA is supposed to be a place where the members collaborate to get them done. Therefore, I respectfully suggest you dive right in on this issue whenever you're ready. :)

http://xdaforums.com/showpost.php?p=1555186&postcount=6

http://xdaforums.com/showpost.php?p=1555452&postcount=8
[8525, TyTN, MDA Vario II, JasJam ROM Development] whistler4ever:
dont mean to sound like a smart ass or anything, but would the key be the one mentioned above or this: EnableKeyboardMapping?

I tried the latter, and it doesn't work, but I just wanted to confirm. I wonder how come Funkey's rom (based on 3.61) supposedly still has the issue while vp3g's rom is in the clear.
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
The answer is that there are different 3.61 base:

-AT&T

-T-Mobile

vp3g's rom is based on the AT&T, and mine on T-Mob I guess. There seems to be very few differences, but the keyboard mapping is one.
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
so build one using the att build! :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
tmob always is behind in the times.. att probli seen the bug and fixed it while tmob is like oh ****.. how do we fix this?!
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
I do not have much time right now, and taking appart the ATT rom to fit it to Pandora require quite some.

I'll maybe think about it during my holliday, but for now there is no better solution
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
ok. thank you much. i might become nerd and attempt to do it and see my results
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
3.60, 3.61... whatever it takes

I thought the T-Mo ROM was 3.60 (not 3.61). I used it's XIP for my v3.60 (hence the name).

I haven't kept up very well with what mattk_r is doing with his Pandora kitchen, however isn't his 7.1 based on the AT&T 3.61 ROM? If so I'd think you'd be able to crank out bugfixed ROMs all day long with it...
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
i assumed the same thing vp.. but i guess tmob has a 3.61 also.. i wonder what base pandora's 3.61 is.. hopefully matt can shed some light on this.. but as fun

_key mentioned his build was from 3.60 and 3.61 not just 3.61 so.. im not sure. but i know when i was diggin in the reg for 1.21 rom alot of keys show 3.60 not 3.61 like ur rom did when i compared them
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
You are fully right. I checked the wiki and all I said on my last post is bull****; I mixed up everything.

So now that my ROM is based on the last pandora, it should be fully 3.61. But, the bug is still present. I'll try to shoot this issue down a bit later, but I am not really good at those kind of troubleshooting.
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
I'm not aware of a T-Mo 3.61.

Well, that tells me it must be somewhere in the imgfs, then. I would suggest creating a Pandora ROM that's as close as possible to the AT&T ROM as a test. Trouble is, that thing has pieces-parts from all over the place so depending where the fix is hiding out it could be quite easy to miss.
[8525, TyTN, MDA Vario II, JasJam ROM Development] drutort:
this might req some effort by those who cooked these popular roms, they would know the best we could be spending weeks until we find something while they might go oh... it was here i think or maybe this... and in no time we could have a solution
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
I ended up de-AT&T'ing vp3G's latest ROM.

I have to say, I have been very impressed with this ROM especailly its stability and speed.

I came from Schaps 3.60a which also worked well, but was more sluggish with BBConnect and the BT issue was annoying.

I was worried that it would be too AT&T to use on a non AT&T network, but things have been great.

The only thing I've noticed is on Schaps if I am in 3G I get 3G Rogers, now it just says Rogers

I would say if it a huge issue, just move over to vp3G's until more people can base new ROMs on his base rom.
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
If that were the case we'd have had one long before now. You need to spend some time boning up on the topic before commenting further, my friend.
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
I am right now banging my head on this issue.

So, it is definietly not depend on the registry. I'll keep you informed if I can find something out. Btw, performing those check is really annoying/boring/...

EDIT: Ok, I think I got it!

FuN_KeY's Rom 1.3.0.1 on its way soon.
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
I'm just wondering why it is so difficult to take v3G's rom base and start from there?

I honeslty don't know the answer, that is why i'm asking
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
^^ very good question..i was wondering myself just didnt want to ask
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
I could, but I'd rather wanted to isolated the faulty DLL, which is allmost done (I modified plenty and it worked, I just need to track down the really faulty one). Let's get some bore again :-/
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
yes! :) very happy to hear ur working on this lol
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Are all the vibrate options available on vp3g's ROM? When I replace the faulty DLL I lose everything about vibrate in notification
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
yes hold down comm and it goes to vibrate
[8525, TyTN, MDA Vario II, JasJam ROM Development] lcohen999:
Yup, Vibrate is there under sound and notifications, notifications
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
couldnt u just skip the vibrate function and install the .cab fix or no vibrate is working at all?
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
I finaly also managed to have the vibrate bug fixed. I learned plenty of things today!
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
are you telling us u fixed keyboard mapping?!?!?!
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Yup, new rom uploading right now
[8525, TyTN, MDA Vario II, JasJam ROM Development] cuboosh:
OGM OMG OMG OMG so where is the problem/fix at?

like where was the problem located
[8525, TyTN, MDA Vario II, JasJam ROM Development] Shamanix:
Can you please share the fix so I can cook it in my next ROM ? :o
[8525, TyTN, MDA Vario II, JasJam ROM Development] whistler4ever:
nice... I was playing around with the same drivers yesterday, but not in the same directory. I ended up defunking my h/w keys altogether, lol

was the vibrate bug an easy fix?
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
Here is comes the true story of the keyboard fix:

Module keybddr.dll was the faulty one. You have to replace it with the one from vp3g's rom (see bellow). It is located at \OEM\OEMDrivers in Pandora

As the file has a different size, it may/will conflict with memory allocation of other files (this is what caused the vibrate issue I reported a few post earlier).

To have this fixed you have to the great G'Reloc (thanks misar) on your entire kitchen.
[8525, TyTN, MDA Vario II, JasJam ROM Development] Shamanix:
Thanks for the files, it`s all I need..
[8525, TyTN, MDA Vario II, JasJam ROM Development] vp3G:
Nice work, fun_key. :)
[8525, TyTN, MDA Vario II, JasJam ROM Development] EQUiLiiBRiUM:
Very Nice Work... I don't have a Reg Folder named keybddr.dll I only have a reg key Keybddr.dll

Is that zip file only for cookers to Put in there Rom ? If so maybe I can Make it into A cab file for People need it. :confused: Can you make it into a cab ?
[8525, TyTN, MDA Vario II, JasJam ROM Development] fun_key:
In fact is is more complex than it looks like:

The fixed keyboarddr.dll deny the use of button5 (thanks to PTT). I am now working on a lightweight implementation of PTT+PTTFix to have this issue also solved.

For the cab, I am not sure this dll can be changed that way; thus I am not so experienced in cab building and really don't want to release an "happy hard reset" cab ;-)