Develop Bugs

[howto] get Orbot (Tor network) transparent proxying working

*REQUIRES ROOT*
Warning: Follow these directions at your own risk! I take no responsibility for any damage to your phone, personal information, dog, cat, or grandmother that may result from you voluntarily following these directions. If you blame me, I will laugh at you.
This information is partially from: http://forum.xda-developers.com/showthread.php?t=760472
This is my first topic post, so please let me know if you find it helpful!
I could not find a tutorial on getting Orbot transparent proxying to work on my SPH-D710, so this is how I got it working. I hope this is not a repost, but as I said I could not find a specific tutorial/howto.
It seems to me that the issue with Orbot on our phones has to do with the iptables that is included with Orbot. Even if you tell Orbot to use the default iptables (/system/bin/iptables), it still does not work.
(1) Install "Droidwall" and "Orbot" from the Android market.
(2) Open Droidwall so that it installs the necessary binaries.
(3) Do the following in adb or the terminal: (I prefer using adb)
Code:
[B]# cd /data/data/[/B]
[B]# find ./ -iname "*iptables*"[/B]
./com.mgranja.iptables
./org.torproject.android/app_bin/iptables
./com.googlecode.droidwall.free/app_bin/iptables_armv5
[B]# cp ./com.googlecode.droidwall.free/app_bin/iptables_armv5 ./org.torproject.android/app_bin/[/B]
[B]# cd /data/data/org.torproject.android/app_bin/[/B]
[B]# mv ./iptables ./iptables.ORIGINAL[/B]
[B]# mv ./iptables_armv5 ./iptables[/B]
(4) Open Orbot and go to (menu) -> Settings. Make sure to enable "Request Root Access," "Transparent Proxying" and "Tor Everything."
(5) On the bottom of the settings page, ensure that "Use Default Iptables" is NOT selected!
(6) Open Orbot, long press the 'power' button to start Tor. In the menu there is an option to make sure ("check") that you are connected through the Tor network.
Enjoy!
Sent from my SPH-D710 using Tapatalk

IPTABLES is your firewall.
So I wouldn't mess with them unless you know what you are doing.
You sound like you don't know what your doing if you have to "download" it.

kthejoker20 said:
IPTABLES is your firewall.
So I wouldn't mess with them unless you know what you are doing.
You sound like you don't know what your doing if you have to "download" it.
Click to expand...
Click to collapse
I agree that you shouldn't mess with it unless you know what you're doing. The app mentioned simply updates the version in /system/bin that came with your ROM -- whether or not you want to do this is up to you. (I just edited and removed the portion you made reference to.)
Regardless, in order to get Orbot working on the phone with transparent proxying, the main thing is to tell Orbot to use the default iptables in the ROM rather than the one Orbot comes with (/data/data/org.torproject.android/app_bin/iptables).
EDIT: With the edits made to my original post, this is now irrelevant.

I use to do this back in the day. At times it's handy however, the speeds are insanely slow so I stopped using it and just dealt with the fact that the carrier would see my every move on the network. They can do that regardless of the fact that you're using a proxy anyway so it just seemed like a waste. Slow speeds + they can still track me or fast speeds + they can still track me. Using Tor on a phone only prevents the site you're visiting from knowing who and where you are - not the carrier.
Just wanted to make that clear for anyone that doesn't know.

The speed is definitely a pain, but if you are willing to sacrifice some anonymity (probably a lot) you can configure Tor to only use nodes within your country - which I tested and got much faster speeds.
While your carrier can track that you are using their network, they cannot see what specifically you are doing. Tor encrypts all traffic from your phone -> entrance node -> intermediary nodes -> exit node (and vice versa). The only unencrypted leg of the journey is between the exit node and the destination host.
If anyone wants to read more https://www.torproject.org/about/overview.html.en
Sent from my SPH-D710 using Tapatalk

working
This worked for me, thank you so much. im runing a modded stock rom on my Lg Optimus black and it hasnt iptables, now everithing is fully working, thanks! now i can use facebook from mi phone on my work "restricted" network hehe

tor
You can also run tor from the terminal and from /data/data/*. It's much easier and you can delete all the iptables and orbot stuff. The default datadir for tor isn't working so I started tor with -datadir. For example tor -datadir /mnt/sdcard/tor.

Thank you I have been trying to get this running on my phone for a second.

Phpdna said:
You can also run tor from the terminal and from /data/data/*. It's much easier and I have deleted all the iptables and orbot stuff. Because the default datadir for tor isn't working on my device I started tor with -datadir. For example tor -datadir /mnt/sdcard/tor.
Click to expand...
Click to collapse
What are you doing exactly?
Can You explain more?

santasolo said:
What are you doing exactly?
Can You explain more?
Click to expand...
Click to collapse
I was trying to run tor without orbot. Orbot is too heavy for my mobile. I find tor is an app in /data and we can start it from the terminal with the datadir switch. I guess Orbot works, too, but I'm not so sure.

Very interesting post. Thanks for the info.

DankVader said:
Very interesting post. Thanks for the info.
Click to expand...
Click to collapse
If my answer is helpful please consider to thank me. Thank you!

I thought I did. But I must have forgotten to. Correcting that now. :victory:

[DEV-WIP] MIC testing (To enable GoogleNow function in JB)

NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs

times_infinity said:
Perfect person to probably ask for help would be supercurio, although his specialty is wolfson codecs
Click to expand...
Click to collapse
Yeah you're right .
Envoyé depuis mon GT-I9000 avec Tapatalk

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bear ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T

webdroidmt said:
This would be great! Btw, is your rom's codename Jelly Bear?
Mike T
Click to expand...
Click to collapse
Nice catch!

I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.

You guys could try (sp?)Meltus as well...the Volume+ guy.
Sent from my Galaxy Nexus using xda app-developers app

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
W/dalvikvm( 3429): threadid=1: thread exiting with uncaught exception (group=0x41199300)
E/AndroidRuntime( 3429): FATAL EXCEPTION: main
E/AndroidRuntime( 3429): java.lang.IllegalArgumentException: requested provider network doesn't exisit
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1429)
E/AndroidRuntime( 3429): at android.os.Parcel.readException(Parcel.java:1379)
E/AndroidRuntime( 3429): at android.location.ILocationManager$Stub$Proxy.requestLocationUpdates(ILocationManager.java:646)
E/AndroidRuntime( 3429): at android.location.LocationManager._requestLocationUpdates(LocationManager.java:660)
E/AndroidRuntime( 3429): at android.location.LocationManager.requestLocationUpdates(LocationManager.java:482)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.inject.SystemLocationManagerInjectable.requestLocationUpdates(SystemLocationManagerInjectable.java:33)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.registerForAndroidNlpFix(LocationOracleImpl.java:495)
E/AndroidRuntime( 3429): at com.google.android.apps.sidekick.LocationOracleImpl.start(LocationOracleImpl.java:139)
E/AndroidRuntime( 3429): at com.google.android.velvet.VelvetApplication.startTgServices(VelvetApplication.java:175)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity.completeOptIn(FirstRunActivity.java:350)
E/AndroidRuntime( 3429): at com.google.android.velvet.tg.FirstRunActivity$OptInHander.handleMessage(FirstRunActivity.java:421)
E/AndroidRuntime( 3429): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3429): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3429): at android.app.ActivityThread.main(ActivityThread.java:4745)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3429): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)
E/AndroidRuntime( 3429): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)
E/AndroidRuntime( 3429): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 257): Force finishing activity com.google.android.googlequicksearchbox/com.google.android.velvet.tg.FirstRunActivity
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Even if the mic isn't the issue I would still like to see this implemented this would let many more apps function like shazam, voice typing and of course voice search...
Sent from my Amazon Kindle Fire using xda premium

roothorick said:
I don't think the Google Now crash is related to the microphone....
Here's the logcat I'm getting:
Code:
{removed}
That doesn't look microphone-related. I think our smoking gun is Wi-Fi location. Unfortunately, disabling location services didn't help :/ Hash, when you get the 2nd part of Wi-Fi location working, try Now and see what it does.
Click to expand...
Click to collapse
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.

Hashcode said:
NOTE: This requires some knowledge of the ALSA subsystem. If you're not comfortable doing this, PLEASE DONT. You can in theory damage the audio hardware with bad settings.
With the migration to Jelly Bean, we can see how powerful having a working MIC would be.
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Also, you can install "AlsaMixer" from the Market which gives you a bit of control over the audio system's low level devices.
I feel like if we can get a few devs / knowledgeable users looking at these settings, that we could identify where in our audio driver the mixer for the MIC is getting off track.
THE GOAL:
Get a small list of mixer changes (tinymix / AlsaMixer) which enable the MIC for use in the OS.
Then I can replicate those in the audio driver.
GAME ON.
Click to expand...
Click to collapse
No ALSA experience other than ticking a box or two on my Puppy Linux install - sure wish I did.
This needs to be nailed down for Jelly Bean to work well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Hashcode said:
Ah, I was seeing an "AudioRecord" error talking about trying to use a non-existant device. This error above I can work on.
Click to expand...
Click to collapse
This is purely speculation, but did the other stacktrace come from the 7/11 build? Maybe your half-fix for Wi-Fi location actually broke things, and we actually have TWO blockers here. We won't know for sure until you get location working all the way though.

BUMP
Sent from my PC36100 using xda premium

Alsa mixer keeps installing
I had no luck trying to experiment with alsa mixer sound variables - I installed it from store successfully, but anytime I leave alsa mixer in a way to check is external mic working with some recording app, when I come back to alsa mixer it demands to be again installed. Someone went further with alsa mixer on Kindle JB?

No luck
I've tested it as well but without luck!.
Hoping it works in the near future...

any one here
hope this will work

minhchick said:
any one here
hope this will work
Click to expand...
Click to collapse
Seems it won't.

BrooklynNY said:
Seems it won't.
Click to expand...
Click to collapse
I wouldnt hold my breath...

Hashcode said:
On my latest AOSP Jelly Bean ROM (7/13), I have 3 new binaries so that anyone who is comfortable with the audio system can jump in and help:
tinymix
tinycap
tinyplay
Click to expand...
Click to collapse
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.

stylon said:
Hi Hash, I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did: tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16......
Click to expand...
Click to collapse
Can it be done with this ROM?

stylon said:
Hi Hash,
I've no idea wether anybody else tried, but I just did on your CM10.1 ROM (actually no nightly, I've build one myself as I wanted to learn more about the build process, but it's very close to the latest nightly). And guess what... 2 minutes into trying... it WORKS!!!!! :good::good::good:
Here's what I did:
tinycap xxx.wav -d 3 -c 1 -r 16000 -b 16
I used some regular white Apple iPhone Headset I had lying around (those with the 4-ring plug and the mic in the vol +/- housing).
Except for trying the other capture devices, I promise... I did nothing else, not even played around with tinymix. -d 3 was important... 0 doesn't have capture and the other capture devices didn't even like these simple settings. Now, let's get the audio routed to Google Voice Search .
Best,
STYLON
P.S.: please check out my backlight fix... I fear that what we've there now drains the batteries as even though it seems to be off (screen really completely dark), it's not off very often for me.
Click to expand...
Click to collapse
I'm not sure hashcode follows this thread anymore...you may want to PM him or try him on another thread
Sent from my GT-N7000 using Tapatalk 2

Google Now Voice Search kills Voice Search Systemwide

Hi all,
i've got an odd issue and wonder if somebody else has this.
I'm on pabx' AOSP ROM rc19.
When using Voice Search in Google Now it works the first time. After switching to another app and returning Voice Search fails with something like "Could not be understood". It fails immediately and doesn't even try to record anything.
PLUS: at this point voice recording fails in any app (e.g android voice input / swiftkey, what so ever).
when i force kill Google Search App, everything works again. so this somehow seems to block voice input.
maybe someone can reproduce this..
here's my logcat..
Code:
W/AudioFlinger( 193): findSuitableHwDev_l() loading well know audio hw modules
W/AudioFlinger( 193): loadHwModule() module primary already loaded
W/AudioFlinger( 193): loadHwModule() module a2dp already loaded
E/AudioFlinger( 193): int android::load_audio_interface(char const*, audio_hw_device_t**) couldn't load audio hw module audio.usb (No such file or directory)
I/AudioFlinger( 193): loadHwModule() error -2 loading module usb
E/AudioRecord(10035): Could not get audio input for record source 6
E/AudioRecord-JNI(10035): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java(10035): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
D/dalvikvm(10035): GC_FOR_ALLOC freed 455K, 16% free 15471K/18248K, paused 28ms, total 28ms
I/dalvikvm-heap(10035): Grow heap (frag case) to 15.439MB for 320016-byte allocation
D/dalvikvm(10035): GC_FOR_ALLOC freed 7K, 16% free 15776K/18564K, paused 27ms, total 27ms
I/AudioService( 576): AudioFocus requestAudioFocus() from [email protected][email protected]
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(10035): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
I/VS.G3EngineManager(10035): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 3 ms
I/decoder (10035): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err(10035): java.io.IOException: AudioRecord failed to initialize.
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
W/System.err(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
W/System.err(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err(10035): at java.io.InputStream.read(InputStream.java:163)
W/System.err(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
D/dalvikvm(10035): threadid=49: thread exiting, not yet detached (count=0)
E/VS.G3EngineManager(10035): Error running recognition: 3
W/Search.ConcurrentUtils(10035): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/AudioService( 576): AudioFocus abandonAudioFocus() from [email protected][email protected]
E/UberRecognizerController(10035): onError
E/UberRecognizerController(10035): com.google.android.speech.exception.AudioRecognizeException: Audio error
E/UberRecognizerController(10035): at com.google.android.speech.embedded.Greco3Recognizer.read(Greco3Recognizer.java:98)
E/UberRecognizerController(10035): at dalvik.system.NativeStart.run(Native Method)
E/UberRecognizerController(10035): Caused by: java.io.IOException: AudioRecord failed to initialize.
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:88)
E/UberRecognizerController(10035): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:159)
E/UberRecognizerController(10035): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
E/UberRecognizerController(10035): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
E/UberRecognizerController(10035): at java.io.InputStream.read(InputStream.java:163)
E/UberRecognizerController(10035): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:198)
E/UberRecognizerController(10035): Got error after recognizing []

I had exactly the same thing few weeks ago on a number of roms, couldn't get a fix so just settled on a rom that didn't have the issue
Sent from my HTC One X using xda premium

Thanks for your reply.
can you tell me on which roms you experienced the issue and on which it does not occur?
on AOKP it doesn't work either.
Sense ROMs seem to be working..
I also sent a feedback report to google but i don't think there will be any response.

It worked on sense ROMs but I don't like them, most aokp and aosp ROMs had the the problem but for some reason it works fine on xenonhd and slimbean. I like slim so I just stuck with it
Sent from my HTC One X using xda premium

I digged in a little bit deeper and it's really odd.
on the first launch google now initializes in my local language:
Code:
I/VS.G3EngineManager(23710): create_rm: m=ENDPOINTER_VOICESEARCH,l=de-DE
I/VS.G3EngineManager(23710): Brought up new g3 instance :/data/data/com.google.android.googlequicksearchbox/app_g3_models/de-DE/endpointer_voicesearch.config for: de-DEin: 34 ms
which works.
after returning it tries to bring up
Code:
I/VS.G3EngineManager(30287): create_rm: m=ENDPOINTER_VOICESEARCH,l=en-US
W/Search.ConcurrentUtils(30287): Executor queue length is now 2. Perhaps some tasks are too long, or the pool is too small. [GrecoExecutor-1]
I/VS.G3EngineManager(30287): Brought up new g3 instance :/system/usr/srec/en-US/endpointer_voicesearch.config for: en-USin: 2 ms
I/decoder (30287): ERROR: Exception thrown from GoogleRecognizer.read()
which than fails.
when setting the system language to english it works all the time.
Do you still use a different language than EN_US on SlimBean (I suppose you did) ? or might that be the reason it is working on Slim ?

Phone and search are set to eng UK. Just tried changing to eng generic on Google now and the problem returns, changed back to eng UK and still problem then cleared app cache in system setting and all is fine again. So looks like you found something, good job
Sent from my HTC One X using xda premium

thanks for trying.
would be awesome if someone with a sense rom could try as well.
But i guess it will be an AOSP / 4.2.2 issue only.
maybe one of the dev's can have a look into it.. would be awesome to get this one figured out.

seems like the latest google search / now update solved the problem for me.
maybe you can confirm !?

Newbies advancedsettings.xml

Hello, everyone!! So this is my first post. Currently, I've owned my amazon fire tv for about a week. I've installed not rooted XBMC gotham 13.2. I'm a complete newbie to say the least. Also, i've never written files or anything before this file. I noticed that allot of the information being passed around out on the internet, is for people who have some tech skills. Even-though, I haven't had any prior experience writing files, I was able to put together an advancedsettings.xml file(I was able to push it through via adbFire). I was wondering if someone could tell me if the file is accurate and if I am doing damage in anyway? Another question I have is is there a way to keep track of what you watch via add-ons and have that information show up on the home-screen so that you can just go to the next episode? Furthermore, I was looking at my free memory and it went from 520 mb to 1003mb, I don't understand why. Maybe someone can fill me whats going on with this file setting. Thanks... And I apoligize for all the questions but I think they would be valuable to other newbies, once again thank you....:good:
<advancedsettings>
<network>
<autodetectpingtime>30</autodetectpingtime>
<buffermode>1</buffermode>
<cachemembuffersize>34603008</cachemembuffersize>
<curllowspeedtime>5</curllowspeedtime>
<readbufferfactor>10</readbufferfactor>
</network>
<gui>
<algorithmdirtyregions>3</algorithmdirtyregions>
<nofliptimeout>0</nofliptimeout>
</gui>
<videoscanner>
<ignoreerors>true</ignoreerrors>
</videoscanner>
</advancedsettings>

<ignoreerors>true</ignoreerrors> typo in this line

Tight_wad said:
<ignoreerors>true</ignoreerrors> typo in this line
Click to expand...
Click to collapse
Thank you, I was trying to figure-out why my log was posting " ERROR: Error loading special://profile/advancedsettings.xml, Line 14 Error reading end tag". Good find...:good:

Personally I never use advancedsettings.xml anymore, it was much more popular in older versions of XBMC, but the latest stable should run best under default settings.

Norcal707 said:
Hello, everyone!! So this is my first post. Currently, I've owned my amazon fire tv for about a week. I've installed not rooted XBMC gotham 13.2. I'm a complete newbie to say the least. Also, i've never written files or anything before this file. I noticed that allot of the information being passed around out on the internet, is for people who have some tech skills. Even-though, I haven't had any prior experience writing files, I was able to put together an advancedsettings.xml file(I was able to push it through via adbFire). I was wondering if someone could tell me if the file is accurate and if I am doing damage in anyway? Another question I have is is there a way to keep track of what you watch via add-ons and have that information show up on the home-screen so that you can just go to the next episode? Furthermore, I was looking at my free memory and it went from 520 mb to 1003mb, I don't understand why. Maybe someone can fill me whats going on with this file setting. Thanks... And I apoligize for all the questions but I think they would be valuable to other newbies, once again thank you....:good:
<advancedsettings>
<network>
<autodetectpingtime>30</autodetectpingtime>
<buffermode>1</buffermode>
<cachemembuffersize>34603008</cachemembuffersize>
<curllowspeedtime>5</curllowspeedtime>
<readbufferfactor>10</readbufferfactor>
</network>
<gui>
<algorithmdirtyregions>3</algorithmdirtyregions>
<nofliptimeout>0</nofliptimeout>
</gui>
<videoscanner>
<ignoreerors>true</ignoreerrors>
</videoscanner>
</advancedsettings>
Click to expand...
Click to collapse
Very helpfull! Fixed all on aftv
Sent from my iPhone using Tapatalk

TV ADDONS said:
Personally I never use advancedsettings.xml anymore, it was much more popular in older versions of XBMC, but the latest stable should run best under default settings.
Click to expand...
Click to collapse
I've kind of noticed that, I'm actually thinking about throwing out advancesettings.xml and resulting back to default settings. Nevertheless, seems to run good either way. I'm now dealing with the "low space" error on my fire tv finally was able to get recently add episodes on the home screen which is nice, but the thumbnails seem to be killing space. I've used all but 732 mb

Does some body have a good advanced xml settings for aftv other than this?? Please share if you do!!!!!!
Sent from my iPhone using Tapatalk

Xavier000 said:
Does some body have a good advanced xml settings for aftv other than this?? Please share if you do!!!!!!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
What is it you are looking to achieve?

Tight_wad said:
What is it you are looking to achieve?
Click to expand...
Click to collapse
Smoother playback on live channels
Sent from my iPhone using Tapatalk

Norcal707 said:
I've kind of noticed that, I'm actually thinking about throwing out advancesettings.xml and resulting back to default settings. Nevertheless, seems to run good either way. I'm now dealing with the "low space" error on my fire tv finally was able to get recently add episodes on the home screen which is nice, but the thumbnails seem to be killing space. I've used all but 732 mb
Click to expand...
Click to collapse
How else would you change the path so that thumbnails are stored on an external drive?
"<advancedsettings>
<pathsubstitution>
<substitute>
<from>/storage/emulated/0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/Thumbnails/</from>
<to>/storage/emulated/0/usbstorage/sda1/xbmcthumbnails/</to>
</substitute>
</pathsubstitution>
</advancedsettings>"

jmerrilljr2 said:
How else would you change the path so that thumbnails are stored on an external drive?
"<advancedsettings>
<pathsubstitution>
<substitute>
<from>/storage/emulated/0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/Thumbnails/</from>
<to>/storage/emulated/0/usbstorage/sda1/xbmcthumbnails/</to>
</substitute>
</pathsubstitution>
</advancedsettings>"
Click to expand...
Click to collapse
Do you have to towel root xbmc or can you leave it sideloaded when applying that setting?

Yeah, you need to be rooted to mount an external drive.

Norcal707 said:
Do you have to towel root xbmc or can you leave it sideloaded when applying that setting?
Click to expand...
Click to collapse
The <to>/storage/emulated/0/usbstorage/sda1/xbmcthumbnails/</to> can be a network drive as well. Without needing root... Put MySQL (or MariaDB) on a server and get your library on the network too. I think my library DB files were almost 3/4 of a gig.

KarlP said:
The <to>/storage/emulated/0/usbstorage/sda1/xbmcthumbnails/</to> can be a network drive as well. Without needing root... Put MySQL (or MariaDB) on a server and get your library on the network too. I think my library DB files were almost 3/4 of a gig.
Click to expand...
Click to collapse
Can you put your Library from xbmc on Amazon fire tv on MySQL without issues? and do you have to download MySQL onto another computer?

after I've added this to my advancedsettings, will it move my thumbnails to the new location retroactively or is this "from now on" (as in new media added to the library after this setting was added) thumbnails will be stored in the new location?

Question Needed: a step-by-step guide to get the GAPPs including all Google services working on the Fold?

I have the Fold with the Chinese ROM, but I need the Google services support for some of my apps (German Corona app and a phone app - they need some special Google/Apple functions for Bluetooth and the Google notifications). Does anybody have a step-by-step guide to get the Google services including all GAPPs working on the Fold? There is so much outdated (and some maybe even wrong) information on the Internet that such a guide would set the record straight for MiUI 12.5...Thanks!

All google services are already baked into the mi mix fold.
Go into their own app store app, search for Google play, it'll come up as an update. After that it'll show up in the app drawer, sign in and use like any Google android phone

Thanks! I'll try it.

oherzog said:
Thanks! I'll try it.
Click to expand...
Click to collapse
Worked?

It worked mostly, but two weak items are left:
1. I didn't get Google maps work with the Mi Fit app in Germany - it just doesn't display the map but tracks the run.
2. The German Corona Warn App doesn't connect to the corresponding Google services:
com.google.android.gms.common.api.ApiException: 17: API: Nearby.EXPOSURE_NOTIFICATION_API is not available on this device. Connection failed with: ConnectionResult{statusCode=UNKNOWN_ERROR_CODE(39501), resolution=null, message=null}
com.google.android.gms.common.api.ApiException: 17: API: Nearby.EXPOSURE_NOTIFICATION_API is not available on this device. Connection failed with: ConnectionResult{statusCode=UNKNOWN_ERROR_CODE(39501), resolution=null, message=null}
at androidx.transition.ViewGroupUtilsApi14.trySetResultOrApiException(ViewGroupUtilsApi14.java:3)
at com.google.android.gms.internal.nearby.zzan.onResult(com.google.android.gms[email protected]@18.0.3:1)
at com.google.android.gms.common.api.internal.IStatusCallback$Stub.zaa(com.google.android.gms[email protected]@17.5.0:2)
at com.google.android.gms.internal.base.zaa.onTransact(com.google.android.gms[email protected]@17.5.0:3)
at android.os.Binder.execTransactInternal(Binder.java:1162)
at android.os.Binder.execTransact(Binder.java:1126)
Any hints would be welcome!
Otherwise, the Fold works great!