Database Users

[HELP] Loss of response on G2 screen !?!?

I have been experiencing unresponsive spots on my screen. For example, in portrait mode, in Titanium Backup, I am unable to get Wipe Data button to work BUT both the Delete & Uninstall buttons, above & below it, will trigger instead. I have also experienced this happening in the Play Store where the Uninstall button will not respond. It seems to be happening in roughly the same area on my screen.
This just started happening recently & I would like to know if this is a known issue or what ?!
I am running the latest Mahdi ROM 7/9 with dr87's stock kernel on my VS980. I have since tried going back to the 7/7 build as well as trying Render & barts modded Dori kernel.
Please reply via PM if possible, many thanks !
*** I have been trying the 'Show Touches' Development Tool and it (obviously) still happens but it is showing touches in the area that is in question. IDK what this proves > not a hardware issue ?! Help .... please.

[Q] S4 i9506 solk2 port - thanks, and issues observed

Hi - I'm very new to the forum and less new to custom ROMs and software.
In the last few days I installed solk2's unofficial CyanogenMod port, 20140711 root build. Went well; overjoyed to be rid of Samsung's bloatware. Thanks!
Since then, updated to first 20140808 and now 20140813. Used CWM recovery (installed via theunlockr dot com/2013/12/09/install-custom-recovery-samsung-galaxy-s4-gt-i9506shv-e330s/) directly instead of CM Updater - updater downloads the builds but when it reboots into recovery to apply them the process there cannot find the build file to install.
I've noticed:
1) When making / receiving calls, the face sensor doesn't appear to work any more - before CM, the sensor would notice when the phone is held to my cheek and blank the display, and light it up when I move the phone away. No longer.
2) The front start button doesn't appear to wake up the device from sleep any more (maybe I've missed a setting to toggle for that?)
3) the CM updater doesn't appear to work, as mentioned above
4) CyanDelta doesn't know about this set of nightlies I think - I've tried it a couple of times and it doesn't pick up deltas
5) the power button doesn't wake the device when it has darkened due to being on a call; instead it may cause the device to flash its screen up but then immediately darken again
1 & 5 make it quite difficult to control the phone during calls. Initially I thought this might have to do with ShakeCall, but the issues persist after uninstalling that.
I've cleared my cache and dalvik cache after the most recent flash to 0813.

I should say, this is relating to http://forum.xda-developers.com/showthread.php?t=2767448 and I'd have posted there but I cannot yet.

This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?

Is this the right place to ask, even? Does @solk2 work?

pfm102 said:
This is still an issue for me with cm-11-20140909.
Is there anything I can do to help find and fix these items?
Click to expand...
Click to collapse
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.

solk2 said:
Proximity sensor fixed a long ago. There something wrong in yours phone. Install this recovery. Then try clean install of latest nightly or SNAPSHOT-M10 and set update recovery in Developer settings. Recovery you have has different mount points so thats why it can't find updates.
Delta updates isn't supported though.
Click to expand...
Click to collapse
Thank you very much - I'm running 20140914 and the proximity sensor now works during calls.

help on resolving my lg g2 cm12 problems or going back to stock

Hello guys. I'm in trouble!
My lg g2 (vs980) is not universal, and I'm from Nigeria which makes it difficult for me to get OTA updates so I decided to look for an alternative way of getting lollipop. So I followed the steps in a youtube video by a developer (probably from xda). Haven rooted my phone with stump, I downloaded cm12, gapps, efs back up thread, autorec, some jellybean radios and latest twrp recovery all from xda developers forum. Following the guidelines, I install autorec and "downgraded my boot older", then I boot into recovery, flash the latest twrp, whip data as instructed, flash the cm12, flash the gapps, everything as instructed and then I reboot. I don't know what went wrong.
Happy I was, as here comes the lollipop but little did I know that this indeed would be my worst experience on a device ever.
My sim card doesn't show anymore, Media; videos and music no longer play - in fact, anything that has to do with sound even from third part no longer works, games no longer play at all and camera no longer works. The only thing that works well is the wifi connections with which I'm able to post this now. I consider the fact that autorotation, auto brightness, knock on, slide aside and quick window are not working as minor problems but obviously, I can't do without the earlier ones mentioned. Pls I seriously need help on either how to resolve those issues or better steal, how to go back to my normal lovable lg g2 that I used to know. Pls help me I can't use my phone for anything. I really missed my phone and I need it back. ​

Which Nougat rom for N900T(T-Mobile)?

I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor

tibimakai said:
I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor
Click to expand...
Click to collapse
Just go to the regular Note 3 development section and grab the AryaMod Port S7Edge Port, and it works on the T-Mobile N900T as well. Most of the ROM's over there will work on this phone.
Or this https://forum.xda-developers.com/galaxy-note-3/development/rom-t3565746

tibimakai said:
I have asked in the specific threads, but I'm getting ignored.
I have tried the HTLE version, but my phone won't take that version. It shows error, that is not for my phone.
Any help would be appreciated.
Thank you in advance,
Tibor
Click to expand...
Click to collapse
Why don't you ask/look in the T Mobile forum ???

I haven't found any that allow for proper GPS locking. You can get location, but the satellites won't stay locked. Aside from that, I haven't been unable to install any of the Nougat or Note7 ports on my T-Mobile phone. Some aren't 100% stable though, and that goes for almost any device.
It's fun to play with them, I guess, but so far the only safe daily driver is the stock ROM, if you want full stability, battery life, GPS, 100% functional. Personally I can't wonder if my alarm will go off, or if the battery will randomly drain, and shoddy GPS is an issue since I'm not currently using a standalone GPS device. I don't know about you, but the possibility of my phone crashing or rebooting during a call, while navigating, or while relying on the alarm is just not worth the eye candy that you can get just by rooting and installing aftermarket tweaks.
I've run two of the Cyanogenmod 14.1 based roms, maybe more, and they all had those issues. Same thing with the Phronesis ROMs. All are unreliable for every day use.
So, in short, I don't there is a best Nougat ROM, because I can't see using any of them aside from dual booting into them here and there, out of boredom, and to check if things have improved.

Thanks for that. I was afraid of this, that they are not reliable. I guess, I will just have to wait, for the Note8 then.

Guys, if your problem is that your phone is seeing satellites but never actually locks, there's a fix for that. Grab the gps.conf from this thread: https://forum.xda-developers.com/ga...-devs-fix-gps-users-ntp-to-localhost-t3531891
Move that gps.conf to /system/etc/ through whichever means you prefer (recovery, root file manager, whatever), set it to 0644 permissions (rw-r--r--), reboot and you should never have trouble getting a GPS lock again (until you flash another rom, then just do it again). Long story short, there's a stupid bug with most ROMs out there that they're trying to sync to the GPS satellites using data from a server over the internet instead of the (very accurate) internal clock, and since there's a delay over the internet it can't sync and never locks. That gps.conf fixes that issue.

I have ended up, installing this update and it seems like it's working great, except when I reboot it, it's going in reboot loop. The only way I can boot it up, if I remove the battery for a while.
I did not try gps, yet.

I'm using RR rom 7.1.1. It works great

Do you have, US T-Mobile phone? If yes, than from where did you get that rom?

Flashlight being used by another app. Camera doesn't work

After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa

TommyQuid said:
After flashing the unbranded firmware and rooting the phone, I'm not able to use the camera app. Opening it just says "Camera Failed. In the slide down menu, the flashlight icon is turned on even though I'm not actually using the flashlight. and I cant turn it off either. How do I fix this?
I've tried: clearing data & cache of camera app, clearing the cache partition, setting default settings of the camera app, changed camera storage from SD card to internal & vice versa
Click to expand...
Click to collapse
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.

kanesglove said:
Sucks no one responded to your post. I rooted my sons S7 Edge and sometime after it acquired the same issue yours has/has. I had another S7 Edge phone so I ended up rooting that one and giving it to him. I still have his old one with the camera fail issue but I've yet to try to figure out what caused it to happen. I know my response doesn't help with info or duration from OP post to reply, I just wanted to let you know that your post wasn't ignored by everyone. Unfortunately I have nothing substantial to contribute.
Click to expand...
Click to collapse
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.

kanesglove said:
So I ended up putting that phone back to stock then rooting it again and it had the exact same issue yours has. I did a clean root too and the issue is still present. From there I decided to again run it back to stock and this time do a nand erase all and repartition the device. After all was finished I checked the device and I'll be goddamned... it still has the same issue. So if the problem persists after all that reformatting is it safe to say that it's a hardware issue? I'm out of ideas. Sorry I couldn't help you.
Click to expand...
Click to collapse
you guys offer little information at all so this is why no one helps you. Maybe tell what firmware version you flashed what root version you did etc. There is a big difference between bootloader revB/11 and the others

Holy ****. Did I just get constructive suggestions from jrkruse?! Dude if you told me I could fix my phone by sucking a fart out of a wallaby's ass I'd do it cuz the advice came from you, and if there's one thing I know it's that you know your ****. You're ****in' awesome. I feel so special now. Ok sorry about that...
Well, I'm not too sure about the OP but I can tell you about the phone I have that seems to have the same issue.
My S7 Edge is a SM-G935V on android 7.0 on update 4BQK2. Prior to rooting I put everything to stock then I did a NAND erase and repartition. No issues with any of that.
I rooted my phone from this post
G935V Root Method. No Lag! No Heat!
G935V Root Method. No Lag! No Heat!
I AM NOT RESPONSIBLE FOR ANY OF YOUR ISSUES! ALL I CAN DO IS RECOMMEND A GOOD PSYCHOLOGIST! Hey guys. Stumbled on this by accident. I HAVE ABSOLUTELY NO IDEA WHY IT WORKS, BUT IT DOES. THE METHOD HAS BEEN TESTED BY ME AND A FEW OTHER PEOPLE HERE...
forum.xda-developers.com
which directs to your older method for gaining root privileges.
[DISCONTINUED] ROOT Method For Nougat
DISCONTINUED New Thread Found Here This Root Method For S7 Nougat Nougat_S7_Root_2_82_All_Carriers_V2.zip Includes Fingerprint Fix [Latest Verison] Nougat_S7_Root_2_81_All_Carriers_V2.zip Includes Fingerprint Fix Nougat_S7_Root_2_79_All.zip...
forum.xda-developers.com
I also flashed Unzip the Nougat_S7_Root_2_82_All_Carriers_V2.
Then I flashed the BL file in the BL slot from the G935U firmware with odin checking "Phone Bootloader Update". I used the BL file from G935UUES4BRA1 since it's the closest update for the U brand to the firmware this phone is on (G935VVRU4BQK2)
I'm aware that there are newer methods for gaining root access but I chose this method cuz I used it back in 2017-2018, I had read all the posts in the thread, and I knew it worked.
I currently have 3 S7 Edge phones all on the same firmware and build and are all rooted with the same combo method I just explained. The other 2 phones also have xposed installed and they both work well.. expect mine says weird stuff instead of the callers information. I think it only does it if they're a contact but in the notification tab it says an example like this 5556661234;verstat=No-TN-Validation. No clue how to fix that.
The phone that is having the same issue as the OP still had access to the private/secure folder when it was rooted; which I thought was weird cuz mine doesn't and from what I understood private mode gets disabled if the phone's rooted. Maybe it only gets disabled if you install xposed? I don't know. My son had the phone with the issue and it was his first smart phone and he dropped it a few times (with a case) so I was thinking it's an effect from something he downloaded from the play store (he's 20 now but pretty still very ignorant with android). Now I'm not sure if it's a software or hardware issue since the problem persisted after the NAND erase.
Something to note about my sons old phone also is that it has 2 thin pink lines running down one side of the screen (defective/dead pixels) and when the screen turns off it it flashes once before actually turning off. One time over the phone I tried troubleshooting the issue with him and he ended up being able to use his camera immediately after rebooting the phone though once he exited the camera app it wouldn't open again. We were trying a bunch of things, force closing any app I thought would be related to the issue. Not sure what allowed it work when it did, but even now right after a reboot the camera app still crashes.

This was long ago, I've since lost the phone. But, I was on the A bootloader and on OREO rooted using @/billa's method using an ENGboot file. I tried everything possible to get the camera to work including flashing back to stock but nothing helped. I just gave up finally. @kanesglove maybe try safely updating the firmware. Hope it helps