yashsingh1/xdaforums huggingface dataset:
[G4 Q&A, Help & Troubleshooting] fpsq:
My Wifi is for good reasons on channel 13. Which is perfectly legal here. My H815 (root) refuses to connect to it unless it checks my location, based on what country my simcard (sic!) is from! Now my simcard seems to be broken, it won't be recognized by the phone. Or the LG G4 is broken :crying:

As annoying as this is, now I even miss my cell signal AND my wifi signal. You could force Android devices to search on all channels for Wifi. AFAIK this was done editing /data/data/com.android.providers/settings/databases/settings.db Maybe this works in 5.1 the same why, which is why I need to edit this settings.db.

I tweaked this db just perfectly on my Nexus 5 with the app SQLite Editor (Go check it out its great).

On my LG G4 when trying to access the settings.db I always get the error: "The database is currently locked by another process. Try again in a moment or two" By the way: Android-System locksettings.db shows the same behavior.

When I copy the settings.db to /data/data/com.android.providers/settings/ I will get the same error for the COPY of a database!

I need to copy it to my external SD Card and THEN I can access the database. A directory I created on my internal storage /sdcard/Internal is fine to. Now I can open that database. But I do not see the live information + the access rights of that copied settings.db look strange. No owner anymore. ( I use ES File Explorer) I am afraid to edit it and copy it back to:

/data/data/com.android.providers/settings/databases/settings.db

Any idea why I can not access my /data/data/com.android.providers/settings/databases/settings.db ?
[G4 Q&A, Help & Troubleshooting] dominik-p:
Hi,

I had the WiFi Problem when I bought the LG G4 but didn't insert a SIM card.

My WiFi is on channel 13 but it didn't show up on the smartphone.

I contacted the LG support chat. They said I have to insert a SIM card.

When I inserted my German SIM card everything worked fine.

But then I switched on airplane mode and got the message again that not all WiFi network will be shown due to the unkown location.

I see that you are also German.

You can find my (German) solution on android-hilfe.de

Title: "LG G4 WLAN Fix - immer alle Kanäle"

Or here in english:

WiFi Fix - always all channels on 2.4 GHz

http://xdaforums.com/g4/help/wifi-fix-channels-2-4-ghz-t3183160

Did it work?
[G4 Q&A, Help & Troubleshooting] fpsq:
Just saw your post. It reads like a perfect solution! I will try. Dankeschön! [emoji106]

Sent from outer space using telepathy
[G4 Q&A, Help & Troubleshooting] dominik-p:
Bitteschön ;)

Please confirm if it's working.

I testet it on V10c.
[Android Q&A, Help & Troubleshooting] SDUOS2:
xx
[8125, K-JAM, P4300, MDA Vario ROM Development] JIMBABY:
Check out this site

http://www.silentservices.de/btIO.html
[8125, K-JAM, P4300, MDA Vario ROM Development] :
thanks for sharing, i will try this..
[Note Edge Q&A, Help & Troubleshooting] z31k:
Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.

I used the root method from CF-autoroot.

Once it failed I pulled the battery and flashed SuperSU-v2.19zip..

Now I get the binary update notification...

If I can just get some help from anyone that knows what they are doing that would be awesome..

Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing

BTW: I got the 64 su file from root junky...
[Samsung Galaxy S Relay 4G] Bobby Tables:
I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.

I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.

At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
[Samsung Galaxy S Relay 4G] Magamo:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
[Samsung Galaxy S Relay 4G] phred14:
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.

I need a new CWM recovery, latest'n'greatest.

I need and old 10.1 or maybe 10.2 ROM image.

I need the old baseband firmware to go with the old ROM image.

Is this the full list?

There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?

My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
[Samsung Galaxy S Relay 4G] Magamo:
GPS fix:

You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)

Procedure:

Boot into recovery, run a full backup on your device.

flash ICS baseband

Flash CM10.1 Image

Factory Reset

Boot into system (Not sure if this is needed, but I always do.)

Once system boots up, shut system down.

Open phone, pull battery.

Wait ~30 seconds, replace battery.

Boot phone.

Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.

Flash JB baseband.

Restore your system backup.

Reboot into system. Your GPS should now work with your current system.
[Samsung Galaxy S Relay 4G] yohan4ws:
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
[Samsung Galaxy S Relay 4G] phred14:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.

My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)

The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.

My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
[Samsung Galaxy S Relay 4G] dzl:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
[Samsung Galaxy S Relay 4G] phred14:
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.

The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
[Samsung Galaxy S Relay 4G] dzl:
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
[Samsung Galaxy S Relay 4G] goukipoo:
20150823

I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.

Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
[Samsung Galaxy S Relay 4G] dzl:
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
[Samsung Galaxy S Relay 4G] TPMJB:
We're still getting nightly releases for this dinosaur?

http://download.cyanogenmod.org/?type=nightly&device=apexqtmo

Crazy! I thought it was all but abandoned!
[Samsung Galaxy S Relay 4G] phred14:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
[Samsung Galaxy S Relay 4G] TPMJB:
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
[Samsung Galaxy S Relay 4G] rpimonitrbtch:
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
[Samsung Galaxy S Relay 4G] kodimagnyl:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........

BW
[Samsung Galaxy S Relay 4G] phred14:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?

I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.

Thanks
[Samsung Galaxy S Relay 4G] emaayan:
i have a rooted stock rom, can i move to the latest cm11 nightly build?
[Samsung Galaxy S Relay 4G] kodimagnyl:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip

http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip

https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip

LJ1modem is the old baseband....

Good luck ;)
[Samsung Galaxy S Relay 4G] phred14:
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.

BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?

Thanks
[Galaxy S6 Edge Q&A, Help & Troubleshooting] pamarakos:
Can someone please with programming skills check on this??

http://xdaforums.com/showthread.php?t=1261060

Of course I m talking for the last version which is on store.

You see if we are in 5.1.1 and root via a kernel it's not working of course because of an "authentication fail" it gives...

Also if I m helping when on 5.0.2 when rooted with pingpong or with cf-root everything was ok, problem begins when flashing twrp.

I m willing to donate and I m sure there is a lot of people also wait on this, even working on other devices as well!

Also there is this

http://xdaforums.com/showthread.php?t=1177692

which was ok but for the first version of the app for older sammy tv

Thanks for your time
[Galaxy S6 Q&A, Help & Troubleshooting] ameyabhagwat:
Hello everyone. I don't know if I'm within the rule book while starting this new thread. But after about half an hour of search, I couldn't find an appropriate thread to post my problem. So I thought creating a new thread would help. Sorry again, if I'm breaking any rule.

So I bought a Samsung Galaxy S6 Edge on the 3rd of August. Took it home, set it up, and just out of curiosity, compared it with another Galaxy S6 and Galaxy S6 Edge in the family. To my utter shock, I found out that the front facing camera on the newly purchased Edge was not as good as the one on the older ones. It was foggy and a lot whitish. The skin tones were coming out different and the colors looked washed out too. And in a relatively dark room, I felt the new Edge didn't let as much light in as the older ones did. I immediately reported it to the service centre and after a lot of speculations and contemplations and prejudice, it was finally replaced. I got a DOA Certificate issued. I took it to the dealer I got the S6 Edge from and this time decided to go for a Galaxy S6. I set it up, got it updated from the service centre to Android 5.1.1. So now, I have this newly purchased Galaxy S6 and the older Galaxy S6 and S6 Edge in the family. I again compared mine with the other two, this time with a bit of apprehension rather than curiosity. Needless to say and shockingly enough, this Galaxy S6 is pretty much like the S6 Edge I got replaced. The Images look darker, skin tone doesn't look fresh, feels like it's not allowing as much light in as it should. Let me mention the fact that the older S6 Edge and S6 have absolutely same front facing cameras. Not even a thin line difference there.

There are conditions where (especially outdoors during daytime) the three front facing cameras perform almost the same. It is when you come indoors that the new S6's camera takes a beating. I don't know what the reason is. All three of them boot the same Android 5.1.1. The Display settings are the same (there's no question of it as I clicked images and put them on my Laptop to compare) and so are the Camera settings. I even reset the new S6 to no avail.

Does anyone have any suggestions as to why the two back-to-back Phones had a problem, if at all it is a problem that is! Or is it that Sammy has started optimizing their front facing cams differently? The S6 Edge was manufactured in May 2015 whereas the replacement S6 got was manufactured in March 2015. No connection whatsoever there. And yes, the display tone on the S6 Edge is slightly warmer. The older S6 has a different display and the newer one is yet again in its own territory.

Will really appreciate any help from any one.

Should I report this to the service centre? Or are there any solutions?

The battery life is ridiculous too, especially after I got it updated to Android 5.1.1.

Thanks again.

Kind regards.
[Galaxy S6 Q&A, Help & Troubleshooting] the Doctor:
Questions and troubleshooting issues aren't to be posted in the General section, but here:

http://xdaforums.com/galaxy-s6/help

The mods will move it shortly. Good luck troubleshooting your problem.
[Galaxy S6 Q&A, Help & Troubleshooting] Obagleyfreer:
Older Galaxy S6s had a different camera module, they used a Sony module.

Newer Galaxy S6 uses a Samsung module.

A lot of people prefer the older Sony cameras.
[Galaxy S6 Q&A, Help & Troubleshooting] ultraquantum:
I think he is talking about the front camera. Its the rear facing camera that has got two modules, The Sony IMX and the Samsung ISOCELL. Regarding the front camera, we still dont have proper information as to which is which.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
Ok, so I have been looking into some of the SuperSU.zip files and sound that there are a few that actually dont make the phone go into boot loop. I double checked the system/xbin and su is installed as well as busybox. Then When I replace a 64 bit su file into Superuser 2.19, supersu app keeps telling me to update the binaries. Thats where Im stuck. So to recap.

I used the root method from CF-autoroot.

Once it failed I pulled the battery and flashed SuperSU-v2.19zip..

Now I get the binary update notification...

If I can just get some help from anyone that knows what they are doing that would be awesome..

Here is the Modded zip.. https://drive.google.com/file/d/0B6opNIGQWcVYT1JRMmtrNFUtbE0/view?usp=sharing

BTW: I got the 64 su file from root junky...
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
I know you've tried a lot more than posted here, not sure if all attempts but did you try CWM recovery in any of the superuser flashes?

I think the su binary is dependent on the application. SuperSU is telling you update the binary and going no further?

TWRP and SuperSU are bound to Google's interactive shell limitations to remain in Google Play. They may not be the most capable sources to deal with latest Samsung increased security. Those may be reasons older applications targeted to lollipop are working better than latest.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
I have tried that... the earlier builds flash without bootloop.. v2.16-2.19, newer builds, v2.30 on up, send it to bootloop.. i just felt i was getting closer with the modded su and the notification.

Ive been at it for like 2 weeks.. lol..
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
So beta 2.49 SuperSU fails also? Have you tried its su binary with those earlier builds targeted at lollipop? Maybe there was a reason for beta; can't be released in Play, no terms would apply to it. Wishful thinking?

None of the su binaries work?

Regards,

Edit: by definition, the terms indicated how interactive shell interacts with SEAndroid or SELinux. Maybe the /system/vendor/lib/liboemcrypto.so and /system/lib/libselinux.so need to be swapped with the first Lollipop tar that dropped? OB7 for Sprint Note 4.

Edit 2: if using custom kernel, don't need liboemcrypto.so
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] pbedard:
How can u swap it with a locked boooader
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
The OP says he can flash mods. I'm assuming here and you know the consequences of such, but thought it also possible to mount system and use the TWRP file manager to edit system.

I'm still OB7 but following with interest regarding the root of OG5 and recovery methods.

Edit: If L Speed Mod flashes successfully, default mode should give more freedom if using ADB and it doesn't need root. I think it's all shell scripts. (ADB Insecure required for booted mode adb access.)
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] pbedard:
Yea i debloated it wothout root in an adb abell
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
Ill look into it flashing l speed mods.. maybe that can be a door... I know that Selinux and fix permissions can be applied via TWRP. SU binaries are applied.. they were in the system folders. So su is where its supposed to be. Busybox is where its supposed to be, 2.49 does not work just older builds. Its all a matter of figuring out how to update binaries??
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
I would love to debloat in adb shell, however whenever I make a shell environment the device will not detect in adb shell. regular adb commands is fine, just when I start shell.. Suggestions?
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
Flashing speed mod did not help.. Same issue with the binaries not being updated.. Anyone got anymore ideas?
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
I'm out of ideas. Maybe the kernel devs will figure it out when source drops. Everything seems to be pointing that direction due to S6 exploit required.

Did L Speed Mod do anything to help with adb access or adb shell? I have to use ADB Insecure to use adb in booted mode with stock OB7 kernel; initial lollipop release. I was hoping that would help TW 5.1.1 as well.

Did you get the init.d test to pass? Here's a good tutorial; I think it's the developer's tut.

https://youtu.be/zOUrd04dvI4
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
Thank you for the link.. I'm going to try that out when i get some time. I didnt try adb on this run.. I Will test it.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] samep:
You're welcome. Just try the default settings once you know init.d works. Maybe you won't need root since you can flash scripts.

Hang in there. I don't think it will long. It would sure be nice if all carriers got a developer edition. I'm all for security but not at the price of losing root. I still prefer the stock kernel. Now I may be looking for a near stock kernel again.
[Sprint  Galaxy Note 4 Q&A, Help & Troubleshooting] z31k:
Well, that's the thing. I need all the help i can get. I posted over here because you guys have development. I have been watching your forum like a hawk, just waiting for you guys to get 5.1.1. Lol....We dont in the sprint note edge forum. But i figure its the same hardware.

So with all that said, i really appreciate your help. Its a great step at a fresh direction.
[Galaxy Tab S Q&A, Help & Troubleshooting] thorvindr:
I'm somewhat certain I already know the answer to this but I just need confirmation.

With a locked bootloader, flashing anything other than stock will be unsuccessful, right? I've just rooted my t807a and am looking to get xposed running. I just don't want to brick this thing now that I've FINALLY got it rooted.

So what's the bad? What happens if I try to flash a custom recovery? Will it flash and then not work? Will it fail to flash? Will I be bricked/caught in a bootloop?

Right off the bat, let me make one thing abundantly clear: I do not care if I trip Knox. I assume the warranty is voided as soon as I take a new device out of the box so I really don't care if Samsung or AT&T finds out that I've been misbehaving.

In case it matters:

Model: SAMSUNG-SM-T807A

Android version: 5.0.2

Baseband version: T807AUCU1BOD4

Kernel version: 3.4.39-4727547

Build number: LRX22G.T807AUCU1BOD4

Device Status: Custom
[Galaxy Tab S Q&A, Help & Troubleshooting] gingerdude:
Okay I'm no genius, but maybe do a search on using the app flashify to flash custom recovery (twrp) ......obviously the right file for your device.

I've used thus before on other devices and it work well but do your research . Flash at own risk.
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
DO NOT flash a custom recovery or kernel on a bootloader locked device!

Unless you want a nice brick.

If you want xposed use Flashfire.
[Galaxy Tab S Q&A, Help & Troubleshooting] thorvindr:
Just to make sure I understand what you're telling me: even with a locked bootloader, it should be safe to use Flashfire to apply the xposed .zip? I'm not familiar with Flashfire yet, so I'm off to educate myself.
[Galaxy Tab S Q&A, Help & Troubleshooting] ashyx:
Modifying or flashing a custom rom is fine, the bootloader doesn't really care, neither does knox seemingly.