Related
Update March 25, 2013:
Solved!! The folks over at Thinktube Inc. have developed a fix and submitted it to CyanogenMod and AOSP for merging into their code:
http://b-real.org/2013/ad-hoc-ibss-m...h-cyanogenmod/
http://www.thinktube.com/android-tech/46-android-wifi-ibss
Essentially the EASIEST solution is to ROOT your phone, and install the CyanogenMod nightly as of March 25 or later (note: you will have to wait until the nightly is actually BUILT, since as of today it is not ready yet).
I have not tested this solution out myself, however others within this thread have confirmed it working.
Please if anyone develops a easier patch or a step-by-step for people who do NOT want to use CyanogenMod, post and I will update the OP
Cheers!
WiKiD24
-------------------------------------------------------
Update Oct 9, 2012:
- Nexus 7 v4.1.2 did not add Wi-Fi Ad-Hoc Support with the stock update from Google.
To do: Check if any WPA-Supplicant changes previously tested in v4.1.1 now work in 4.1.2
- Workaround (Recommended): Bluetooth Tethering to Nexus 7 Tablet (via Bluetooth DUN Profile). "BlueVPN" from Google Play Store.
Tested successfully on many Nokia Symbian phones (N7, E71, E72), and others.
However, many applications on Nexus 7 Tablet do not support it (without fixes from the developers)
Confirmed working applications:
- Pulse
- Google Chrome
- Dolphin Browser
- Facebook
- Ebuddy
- Youtube
- Others (I am too lazy to add them all)
Confirmed NOT working applications:
- Gmail
- Email
- Google Search
- Google Play Store
- Dropbox
- Words with Friends
- Scramble with Friends
- Others (I am too lazy to add them all)
More details can be found here: http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
Issue: Sometimes the phone/tablet do not connect (randomly), due to issues with either the phone or the tablet.
To resolve: Turn on and off bluetooth on phone, Turn on & off bluetooth on tablet. Try again. If does not work, reboot phone and tablet and try again. Should work.
-Workaround: Android Phone to Nexus 7 Tablet (via "FoxFI" App on Phone, "FoxFi Addon" App on Tablet, or via "PDANet", or via "Wireless Tether App")
http://forum.xda-developers.com/showpost.php?p=29763582&postcount=27
- Workaround: USB Tethering ANY Phone to Nexus 7 Tablet (via "PPP Widget" App on Tablet, requires rooted Nexus 7)
http://forum.xda-developers.com/showpost.php?p=32431103&postcount=51
- Workaround: Windows WiFi Laptop Tethering to Nexus 7 Tablet
http://www.youtube.com/watch?v=klHzMyYFGeQ
-------------------------------------------------------
Hi All,
I've just recently gotten a Nexus 7 and need to be able to enable Ad-Hoc wifi on the tablet.
I also own a Asus TF101 and previously had the same problem however there was a fix for that.
The solution was to replace the wpa_supplicant file in the /system/bin folder, however I do not know the code to change it.
If anyone has the technical know-how, they would be able to reverse-engineer it and apply the same fix.
http://forum.xda-developers.com/showthread.php?t=1370955
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/2752...less-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/gitw...upplicant.conf
I posted a possible solution in QnA section. Thread title is similar to this one. Check it out. Doesn't involve any coding. Prime had a similar issue on a few firmware updates. This was solved for us(before Asus came around to enabling it themselves) by adding in a wifi supplicant file and renaming an older one. Then setting permissions on the new file. Here is the link to that thread. There's a good chance it will work without the file needing to be modded. It came from a galaxy tab LR something and worked fine on prime. Its worth checking out.
http://forum.xda-developers.com/showthread.php?t=1438297
thanks for the tip and I tried it out, which is essentially the same type of solution but it didn't think work as there is no wpa_supplicant2 file in the nexus 7.
http://forum.xda-developers.com/showthread.php?t=1777413
here's some more useful information for enabling ad hoc:
http://szym.net/2010/12/adhoc-wifi-in-android/
http://www.slatedroid.com/topic/27522-howto-connect-to-ad-hoc-wireless-hotspots/
http://www.olsr.org/?q=olsr_on_android
http://hostap.epitest.fi/gitweb/git...ob_plain;f=wpa_supplicant/wpa_supplicant.conf
I'm doing what I can right now to try and enable it.
Some more experienced android users whom know what they're doing would be better than me trying it out, though!!
Did any of those sources of information get you any closer to enabling ad-hoc?
Just FYI that Nexus S "ad hoc enabling file" doesn't work on NS with Jelly Bean.
nexususer0101 said:
Did any of those sources of information get you any closer to enabling ad-hoc?
Click to expand...
Click to collapse
None yet, I need some help to do so. There is a file called "wpa_cli" that I need copied from another device, because I can't find it on the internet.
If anyone could find it in their "/system/bin" folder and attach it to this tread, I could certainly try it.
I've also requested the same thing in the Q&A forum here: http://forum.xda-developers.com/showthread.php?t=1793437
Bumping; I have the same condition. I'm in Italy and bought an internet package for my laptop--I'm sharing it with all my other devices but the N7 doesn't see the adhoc connection. Like OP said, I had a Transformer TF101 and remember flashing a file to fix it.
Thanks in advance.
Just an FYI: Also checked my GNex for a wpa_cli and came up empty.
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
One more "me too".
I'm here to share my sympathy to everyone else's pain as I have a nexus 7 that I can't connect to my phone's adhoc Hotspot. I have also posted my query in Android Central, but no one seems to have been able to know a fix as of yet. (topic can be found here: Android Forums at AndroidCentral.com > Google Nexus 7 Tablet Forum > Nexus 7 Rooting ROM's & Hack's > *** CONNECTING TO Adhoc WiFi WITH THE NEXUS 7 ***)
As I said in that thread.. not being able to connect to phones hotspot makes my beautiful nexus 7 feel like a handicapped tablet.
wikid24 said:
Just wanted to give quick update, i have not been able to find anyone to help me and also my life is kinda hectic right now... Hopefully someone will be able to pick up where I left off, in the meantime my nexus 7 is pretty much useless to me until resolved.
Click to expand...
Click to collapse
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. on prime we had this exact same problem. Then we found the supplicant file to replace one we had and then adhoc tethering worked after that. You only need to be rooted to do this as you need to rename a file and insert new supplicant in there and set permissions. You can always backup and rename original file. So if it doesn't work, you can easily revert back to stock file. I have a feeling this new file will work. Just haven't tried myself yet as I haven't brought tablet outdoors yet to need tethering. I might eventually see if it works if no one else does.
Look at the thread I linked in second post and you will see prime owners had exact same problem and we solved it. It worked for the transformer 300 also. Will likely work for nexus 7 also. The file is, in a sense, universal.
demandarin said:
I haven't seen any reports/posts of people checking out or trying what I mentioned in post #2..lol. .
Click to expand...
Click to collapse
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
rdelfin said:
I have tried. It does not work -- WiFi refuses to turn back on with this new supplicant file. And yes, I made sure to follow your instructions exactly as described in the procedure.
With the N7, there is no such thing as a wpa_supplicant2 file originally in /system/bin (only the one without the '2' exists in the N7 which is the one running the show here, I know this for a fact as when restoring this file, the WiFi in the N7 becomes functional again). So I tried this same file you provide both with and without the '2', with no better results.
I suspect that only a developer that knows what he's doing would be able to come up with a new wpa_supplicant file specifically tweaked for the N7 (as opposed to using one that did the trick for the Prime or for the Xoom or whathaveyou).
Thanks for the suggested idea though... anything else you think we should try?
Click to expand...
Click to collapse
They likely will implement it through a future update. Hopefully that's sooner than later. Ill ask motley, kernel developer.
I toyed with this for a while...
If you install Power Controls (Power Controls) you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Demented-Idiot said:
I toyed with this for a while...
If you install Power Controls you can add a button that turns on the Wifi Hotspot.
Problems:
you cant change any settings in current settings UI
Appears to be default "Android_AP" SSID and whatever the default password is (i dont recall if this is a random code or not)
Its a start!
Click to expand...
Click to collapse
Could you explain exactly what this does? I didn't understand what it is being implied with this being a start? with this you can actually connect to adhoc?
idk if anyone has looked...but has anyone looked into editing the Wifi-Direct api to make adhoc networks visible in there? Since wifi-direct is made for p2p connections. it's android.net.wifi.p2p.WifiP2pManager info about it is here http://developer.android.com/guide/topics/connectivity/wifip2p.html like I said...don't know if it's much help
I also wanted to post a quick reply, since I've been an insomniac yesterday.
From my previous posts I posted this link here as well, I edited the wpa_supplicant.conf file from the /system/etc/wifi folder and modified with the following settings, however I don't think that it even reads the wpa_supplicant.conf file either. Can anyone either confirm or deny that the wpa_supplicant.conf file is being used on the N7??
-------------------
update_config=1
ctrl_interface=wlan0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="Bondphone"
mode=1
frequency=2412
key_mgmt=NONE
wep_key0="1234567890123"
wep_key1=1234567890123
wep_tx_keyidx=1
priority=3
auth_alg=SHARED
}
------------------------
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
jenda.69 said:
wikid24: I don't know if N7 (or my NS) reads this file but it definitely reads /data/misc/wifi/wpa_supplicant.conf. Only problem is that I can't turn wifi on after ANY change in this file. Sometimes even if I revert my backup file, wifi won't launch and I must delete it to make wifi working again.
I found this thread on XDA
http://forum.xda-developers.com/showthread.php?t=1806937
It is edited wpa_supplicant file for Asus Transformer but it allows me to turn on wifi even on NS. But it doesn't show me any ad hoc networks. Maybe with non-stock kernel...?
And I also found ad hoc patch for source code of older version of wpa_supplicant. But I'm not able to try if it is possible to apply it on JB version too.
http://szym.net/android/wpa_supplicant-ibss.patch
Click to expand...
Click to collapse
jenda, I think you may have solved a big piece to the puzzle!!
You can copy the file to another directory, and THAN you can open the file! I noticed I had all my pre-saved wifi addresses in this file!
If someone can please copy the "/data/misc/wifi/wpa_supplicant.conf" file to another directory, modify it, than overwrite the old file, it should work!! *fingers crossed*
(unfortunately I am busy for a few days, don't know if I'll be able to make the change for a while)
I'm using an unrooted Razr-I XT890 with Android 4.1.2
When using the app "Syncthing-android" I run into what seems to be a Razr-I specific problem described below.
Syncthing is a multi-platform secure syncing app and Syncthing-android is a port to the Android platform.
The particular problem is that the the config data (node identity, keys etc) get lost after a reboot of the phone.
When used the memory status of the app shows 72 KB of "data", and 0 KB after a reboot.
One line in the logcat caught my attention:
Code:
W/ApplicationContext(386): Unable to create files directory /data/data/com.nutomic.syncthingandroid/files
However, if the app is exited or "killed" and restarted, the data is still available and the app uses them.
But it is gone after a reboot. According the original developer this happens only on my system.
I'm hoping that somebody recognizes this pattern and can give me/us a hint to its origin.
I'm not the developer of that particular app, rather an interested user, who happens to be a developer, but not very proficcent when it comes to Android apps. However terms like "logcat", "intent" or "service" don't scare me
Sorry if this sub-forum is not the correct one for posting this kind of question. The one which seems more appropriate is not accessible to me.
This relates to issue 24 of syncthing-android on github - sorry, I can't post external links here yet.
Hey,
I am not an expert on this matter, but I saw it ones coming through the Google issues. This was it:https://code.google.com/p/android/issues/detail?id=8886. It could be a permission problem, most likely and in this issue tracker it has been resolved in android 4.4. Some phones do have it others don't, just like the Recovery's here. Some don't have any problems with using them, while others do.
Verstuurd van mijn GT-P5110
Thank you for your suggestion.
We found the bug (see original thread on GitHub).
For future reference:
The "official" folder to store persistent data can be obtained by the API call getFilesDir().
The deleoper used getApplicationInto().dataDir
The first one points to /data/data/appname/files/
The second one points to /data/data/appname/
It seems that the Razr (contrary to other phones) deletes files in /data/data/appname/ which are not stored in a subfolder.
This is a small issue I've noticed. I have a module by the name of [KK] Translucent Recent. When in the modules list, it is listed at the bottom of my list. However, when in the download list, it's listed first (in the installed section). This is a small inconsistency problem that I noticed and thought I should point out. Being that this is low priority, I'll be happy if it gets fixed whenever the devs have some spare time. Thanks!
Thanks. I assume that's because the download list is sorted by SQLite, whereas the module list is sorted in Java. Not sure about the exact implementations or ways to change it... Maybe something that somebody else could look into?
rovo89 said:
Thanks. I assume that's because the download list is sorted by SQLite, whereas the module list is sorted in Java. Not sure about the exact implementations or ways to change it... Maybe something that somebody else could look into?
Click to expand...
Click to collapse
I just pushed a commit to fix this. The installed modules list now uses collation for sorting, fixing the [KK] entry and case (in)sensitivity as well.
Cool, thanks! I didn't even know that the term "collation" exists outside of databases.
rovo89 said:
Cool, thanks! I didn't even know that the term "collation" exists outside of databases.
Click to expand...
Click to collapse
Neither did I
Decided to make an open source tap to wake app since implementations will need root to write to the /sys folder. The way tap to wake works is modifying a file to tell the system if it's on or off.
See this commit to see google's original implementation:
https://android.googlesource.com/device/moto/shamu/+/2084f7d0cf50baf394759d175bc28ad80cf7cace^!/#F0
The app is very rudimentary as it's really a simple toggle. It's a completely no frills UI and implementation.
It works by writing "AUTO" or "OFF" to /sys/bus/i2c/devices/1-004a/tsp
By default the file is restored each boot which is why the app asks to be ran on boot.
The full source code can be viewed on github: https://github.com/chrisj951/Tap-To-Wake-Nexus-6
Now we just need it to detect the proximity sensor. Thanks!
Is this any different than the other tap to wake app posted in this same forum?
VTEChump said:
Is this any different than the other tap to wake app posted in this same forum?
Click to expand...
Click to collapse
Apart from little differences, both do essentially the same thing. I mean no offense to ChrisJ941, but I think mine is slightly more polished.
naxir said:
Apart from little differences, both do essentially the same thing. I mean no offense to ChrisJ941, but I think mine is slightly more polished.
Click to expand...
Click to collapse
You two should work together if you ask me.
Also in the source code, are the red lines, the lines that begin with the dashes, mean those were removed from the source code?
If anyone uses tasker and wants to replicate this:
1. Make a new task
2. Select "Scripts," then "Run Shell"
3. Put this in as the command: echo "AUTO" > /sys/bus/i2c/devices/1-004a/tsp
4. Check the box that says "Use root"
5. Set up a profile that runs on device boot which runs the new task that you just made.
Also, try running the task once to make sure that it works and to grant Tasker root privileges if you haven't already.
VTEChump said:
Is this any different than the other tap to wake app posted in this same forum?
Click to expand...
Click to collapse
At the time of making it was the only one to auto-restart through reboot
It is open source (you can compile it to know nothing more than needed is going on in the background)
I dislike allowing root to apps which I can't verify aren't doing something else behind the scenes. (Not implying the other author is, but I don't like taking the risk)
stuff said:
You two should work together if you ask me.
Also in the source code, are the red lines, the lines that begin with the dashes, mean those were removed from the source code?
Click to expand...
Click to collapse
Yes, the red lines are what google removed from the source code (with the commit message being "shamu: disable double tap in power HAL")
Thank you for releasing an open source version, I got a bad taste in my mouth when naxir was talking about monetizing his and didn't want to talk about the technical details until you revealed in the thread. We need more openness/communication in the community so we can have awesome things.
Not that I blame naxir for looking out for his best interests but withholding the technical details didn't sit well with me.
privatekey said:
Thank you for releasing an open source version, I got a bad taste in my mouth when naxir was talking about monetizing his and didn't want to talk about the technical details until you revealed in the thread. We need more openness/communication in the community so we can have awesome things.
Not that I blame naxir for looking out for his best interests but withholding the technical details didn't sit well with me.
Click to expand...
Click to collapse
That is the primary reason I made this, since it does require root.
privatekey said:
Thank you for releasing an open source version, I got a bad taste in my mouth when naxir was talking about monetizing his and didn't want to talk about the technical details until you revealed in the thread. We need more openness/communication in the community so we can have awesome things.
Not that I blame naxir for looking out for his best interests but withholding the technical details didn't sit well with me.
Click to expand...
Click to collapse
ChrisJ951 said:
That is the primary reason I made this, since it does require root.
Click to expand...
Click to collapse
That's a fair point. I have now published my implementation on Github as well.
Great app! Better than Naxirs. Is it possible for you to have it on the Play Store?
Thanks for this app! I've been waiting for something like this, too cool.
monkey hung said:
Great app! Better than Naxirs. Is it possible for you to have it on the Play Store?
Click to expand...
Click to collapse
Just out of curiosity, how I'd this better than Naxirs app? Debating on which one to use.
stacio88 said:
Just out of curiosity, how I'd this better than Naxirs app? Debating on which one to use.
Click to expand...
Click to collapse
They both do they same thing one member just asked for donations if you wanted to by buying it on the play store. I've used both of them and they both work just fine.
Mr. Steve said:
If anyone uses tasker and wants to replicate this:
1. Make a new task
2. Select "Scripts," then "Run Shell"
3. Put this in as the command: echo "AUTO" > /sys/bus/i2c/devices/1-004a/tsp
4. Check the box that says "Use root"
5. Set up a profile that runs on device boot which runs the new task that you just made.
Also, try running the task once to make sure that it works and to grant Tasker root privileges if you haven't already.
Click to expand...
Click to collapse
As a Nexus 5 owner and soon-to-be a Nexus 6 owner, I'd use this instead of an app - no offense intended here, I'm just a DIY guy.
I'd add a little delay in the first line of the task, as the Tasker suggests: search for 'Wait' on 'Select Action Category' and put a delay of 5 ~ 8 seconds, this will give a little time to Android to start all the things and then run the script.
I have a script for another purpose on my N5 and I put a delay of 7 seconds.
Grushteniak said:
As a Nexus 5 owner and soon-to-be a Nexus 6 owner, I'd use this instead of an app - no offense intended here, I'm just a DIY guy.
I'd add a little delay in the first line of the task, as the Tasker suggests: search for 'Wait' on 'Select Action Category' and put a delay of 5 ~ 8 seconds, this will give a little time to Android to start all the things and then run the script.
I have a script for another purpose on my N5 and I put a delay of 7 seconds.
Click to expand...
Click to collapse
I went the Tasker route too. The delay is a good idea - thanks.
Are people seeing sporadic results using this? For me, it will work well sometimes, and other times will require up to 10 taps to wake the device.
When I turn on ambient display (which does nothing, as I have lock screen set to "none") I seem to get more consistent results, but still doesn't work 100% of the time.
Mr. Steve said:
If anyone uses tasker and wants to replicate this:
1. Make a new task
2. Select "Scripts," then "Run Shell"
3. Put this in as the command: echo "AUTO" > /sys/bus/i2c/devices/1-004a/tsp
4. Check the box that says "Use root"
5. Set up a profile that runs on device boot which runs the new task that you just made.
Also, try running the task once to make sure that it works and to grant Tasker root privileges if you haven't already.
Click to expand...
Click to collapse
I got this error-
tmp-mksh: <stdin>[2]: can't create /sys/bus/i2c/devices/1-004a/tsp: No such file or directory?
Click to expand...
Click to collapse
yashgumaste said:
I got this error-
Click to expand...
Click to collapse
I don't have a Nexus 6 anymore so I'm not sure how helpful I'm going to be with this one. From what I can tell from some quick researching, it looks like Google changed something when Marshmallow was rolled out so this method of enabling double tap to wake will no longer work. The easiest way I can find to enable d2tw appears to now be to just use a custom kernel. My recommendation from back when I still had my N6 would be to use either Leankernel or Franco Kernel, but I haven't kept up with the N6 dev scene since I got my 6P in November.
This may be an odd question and I might be completely out of my depth. I got a swanky new set of bluetooth headphones for my Nexus 6 earlier this week so that I can surreptitiously play more games with audio at work. I noticed a handful of the games I wanted to play had incredibly bizarre sound distortions.
Doing some digging and asking elsewhere pointed me to a defect in the Unity engine that describes this exact case. (Tried to post a URL here but apparently I have too few posts. Unity Issue tracker 758142)
Apparently this is a feature that is only supported by some devices, so I was hoping there might be a way to bypass or toggle this feature until the Unity defect is fixed and some of these game makers update their apps.
Any pointers?
Okay, seemed to have figured it out myself:
Using Root Explorer, renamed /etc/permissions/android.hardware.audio.low_latency.xml to .bak and restarted
Some games not having the issue, now.
Make a backup!
spamman5r said:
This may be an odd question and I might be completely out of my depth. I got a swanky new set of bluetooth headphones for my Nexus 6 earlier this week so that I can surreptitiously play more games with audio at work. I noticed a handful of the games I wanted to play had incredibly bizarre sound distortions.
Doing some digging and asking elsewhere pointed me to a defect in the Unity engine that describes this exact case. (Tried to post a URL here but apparently I have too few posts. Unity Issue tracker 758142)
Apparently this is a feature that is only supported by some devices, so I was hoping there might be a way to bypass or toggle this feature until the Unity defect is fixed and some of these game makers update their apps.
Any pointers?
Click to expand...
Click to collapse
Only supported by some phones or only supported by some bluetooth devices?
helix139 said:
Only supported by some phones or only supported by some bluetooth devices?
Click to expand...
Click to collapse
Only supported by certain phones, apparently. Here's the relevant extract from the android configuration XML mentioned in my reply comment:
Code:
<!-- This is the feature indicating low-latency audio, as specified by the
CDD. ONLY devices that meet the CDD's requirements may declare this
feature. -->
<permissions>
<feature name="android.hardware.audio.low_latency" />
</permissions>
this could help fixing some games, but it's lowering the sound quality.
could someone give me a backup of this file ?
happy tree said:
could someone give me a backup of this file ?
Click to expand...
Click to collapse
I'm not sure I follow you. The OP talks about renaming the file to prevent it getting used. Did you try that, but delete it instead?
Anyway, you should use the version of the file that belongs to your rom. If you deleted that, just dirty-flash your rom to get it back.
If your rom comes without the file, then we must assume that the rom developer found that to be the best. Talk to your dev if he is active.
If you just dump an old version of the file into a new rom, there is no telling what will happen. But feel free to try. The contents of the file is listed in a previous post.
---------- Post added at 05:19 PM ---------- Previous post was at 04:40 PM ----------
happy tree said:
could someone give me a backup of this file ?
Click to expand...
Click to collapse
Okay, I just read some more. This file doesn't seem to change the system behavior. It just sets a flag that apps can read and that tells them that the phone supports low latency.
In the OP's case, some games used different code when they found the flag, leading to the problem. But I assume that that has been fixed long ago.
You can find the original file here:
https://android.googlesource.com/pl...ta/etc/android.hardware.audio.low_latency.xml
I looked at the folder indicated, but on my rom (Nitrogen Pie) the file isn't there. However, if I can trust the app I used (System Info for Android), the flag is set anyway. So it seems it gets set elsewhere.
thanks bro, but i already flashed the ROM again, sorry for late reply