[Q] Google Search not working - Verizon Samsung Galaxy S III

Im having an issue with google search. Whenever I want to use the microphone to say words rather than type them its just automatically shuts down be it a text, youtube, or google now. im running PACMAN ROM 4.2.1 and the latests Gapps anyone else having this issue ?

I've noticed this in my app as well for some users. The logCat show this:
02-16 20:31:42.774 W/AudioPolicyManagerBase( 632): getInput() could not find device for inputSource 1
02-16 20:31:42.774 E/AudioRecord( 2739): Could not get audio input for record source 1
02-16 20:31:42.774 E/AudioRecord-JNI( 2739): Error creating AudioRecord instance: initialization check failed.
02-16 20:31:42.774 E/AudioRecord-Java( 2739): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.

Related

anybody has the APK for Gesture Search?

it says here for android 2.0 and up but we might be able to get to work on 1.6 .
I'd like to see this, too. Curious if it'll run on CyanogenMod.
here you go,
got it off the market just this min.
Firerat said:
here you go,
got it off the market just this min.
Click to expand...
Click to collapse
Thanks 10char
Firerat said:
here you go,
got it off the market just this min.
Click to expand...
Click to collapse
Thank you very much.
is there a way to port it back for g1?
ralpho said:
is there a way to port it back for g1?
Click to expand...
Click to collapse
its working on my g1
but I have eclair rom ( CaNNoN Complete 1.2 )
I'm guessing you have a cupcake, donut
make yourself a sig
click/tap edit my sig , in my sig
been using since this morning, its not bad.
I often get frustrated scrolling through the app draw, but now with a gestures icon on home screen I can just open it up and start 'writing'
it is a little slow between letters, but I imagine it will get better as it is developed and it is still faster than messing about in the app draw.
gets a thumbs up from me
Welp, I was so eager to get this working on CyanogenMod I dove in and spent the last few hours trying to figure it out :
Installed VirtualBox and Ubuntu
Installed the SDK, apktool, and other various required bits
Decoded the APK
Edited the AndroidManifest.xml to change minSdkVersion from 5 to 4
Rebuilt the APK
Set up a keystore and resigned the APK with my key (this part took awhile and I still don't really know what other options I have if any...)
INSTALLED THE APP SUCCESSFULLY
Bad news though. Although the app opens and starts giving you the opening wizard, it seems the service that "Queries data sources" in the background freaks out and requires a force close. The logcat:
Code:
I/ActivityManager( 100): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10100000 cmp=com.google.android.apps.gesturesearch/.GShell }
I/ActivityManager( 100): Start proc com.google.android.apps.gesturesearch for activity com.google.android.apps.gesturesearch/.GShell: pid=12360 uid=10097 gids={3003}
W/InputManagerService( 100): Window already focused, ignoring focus gain of: [email protected]
I/ActivityThread(12360): Publishing provider com.google.android.apps.gesturesearch.history: com.google.android.apps.gesturesearch.data.QueryHistoryProvider
I/ActivityThread(12360): Publishing provider com.google.android.apps.gesturesearch.index: com.google.android.apps.gesturesearch.data.IndexProvider
W/dalvikvm(12360): VFY: unable to resolve static field 26 (CONTENT_URI) in Landroid/provider/ContactsContract$Data;
D/dalvikvm(12360): VFY: replacing opcode 0x62 at 0x0025
D/dalvikvm(12360): Making a copy of Lcom/google/android/apps/gesturesearch/search/SearchItemView;.setIcon code (440 bytes)
D/dalvikvm(12360): GC freed 1792 objects / 184456 bytes in 175ms
I/ActivityManager( 100): Displayed activity com.google.android.apps.gesturesearch/.GShell: 2116 ms (total 2116 ms)
W/dalvikvm(12360): VFY: unable to resolve static field 25 (CONTENT_URI) in Landroid/provider/ContactsContract$Contacts;
D/dalvikvm(12360): VFY: replacing opcode 0x62 at 0x0003
D/dalvikvm(12360): Making a copy of Lcom/google/android/apps/gesturesearch/search/DataMultiContacts;.queryPhoneNumbers code (128 bytes)
W/dalvikvm(12360): VFY: unable to resolve static field 25 (CONTENT_URI) in Landroid/provider/ContactsContract$Contacts;
D/dalvikvm(12360): VFY: replacing opcode 0x62 at 0x0016
D/dalvikvm(12360): Making a copy of Lcom/google/android/apps/gesturesearch/search/DataMultiContacts;.prepare code (140 bytes)
W/dalvikvm(12360): threadid=15: thread exiting with uncaught exception (group=0x4001e180)
E/AndroidRuntime(12360): Uncaught handler: thread AsyncTask #1 exiting due to uncaught exception
E/AndroidRuntime(12360): java.lang.RuntimeException: An error occured while executing doInBackground()
E/AndroidRuntime(12360): at android.os.AsyncTask$3.done(AsyncTask.java:200)
E/AndroidRuntime(12360): at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273)
E/AndroidRuntime(12360): at java.util.concurrent.FutureTask.setException(FutureTask.java:124)
E/AndroidRuntime(12360): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:307)
E/AndroidRuntime(12360): at java.util.concurrent.FutureTask.run(FutureTask.java:137)
E/AndroidRuntime(12360): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1068)
E/AndroidRuntime(12360): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:561)
E/AndroidRuntime(12360): at java.lang.Thread.run(Thread.java:1096)
E/AndroidRuntime(12360): Caused by: java.lang.NoClassDefFoundError: android.provider.ContactsContract$Contacts
E/AndroidRuntime(12360): at com.google.android.apps.gesturesearch.search.DataMultiContacts.prepare(DataMultiContacts.java:68)
E/AndroidRuntime(12360): at com.google.android.apps.gesturesearch.search.IndexingTask.doInBackground(IndexingTask.java:126)
E/AndroidRuntime(12360): at com.google.android.apps.gesturesearch.search.IndexingTask.doInBackground(IndexingTask.java:23)
E/AndroidRuntime(12360): at android.os.AsyncTask$2.call(AsyncTask.java:185)
E/AndroidRuntime(12360): at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:305)
E/AndroidRuntime(12360): ... 4 more
I/Process ( 100): Sending signal. PID: 12360 SIG: 3
I/dalvikvm(12360): threadid=7: reacting to signal 3
I/dalvikvm(12360): Wrote stack trace to '/data/anr/traces.txt'
These logs are a little above my head, though, and beyond my research capabilities at the moment (feeling a little defeated and TIRED ). Do they look like a result of my modification of the app or a framework limitation of CM's 1.6?
I'd appreciate any feedback, even if it's a "NO, STOP TRYING TO MAKE THIS WORK AND JUST SWITCH TO ECLAIR ALREADY" I attached the modified APK if anyone wants to play with it.
mttmllns said:
Do they look like a result of my modification of the app or a framework limitation of CM's 1.6?
Click to expand...
Click to collapse
Second one.
Code:
java.lang.NoClassDefFoundError: android.provider.ContactsContract$Contacts
http://developer.android.com/intl/de/reference/android/provider/ContactsContract.Contacts.html
It was added in API level 5 (Android 2.0) and apparently it wasn't ported to CM1.4.x .
Brut.all said:
It was added in API level 5 (Android 2.0) and apparently it wasn't ported to CM1.4.x .
Click to expand...
Click to collapse
Cool, thanks for the quick response. Thanks for the great app, too!
Google just put it out for 1.6. Woot!
http://googlemobile.blogspot.com/2010/03/gesture-search-now-available-for.html
Thanks for the heads up.
Spot On
I've been wanting an app like this for a while now. It work great. Now to reassign some buttons and shortcuts and remove redundancies...
Just a heads up. Enabling the ability to search music as well led to one hell of a bugfest. After doing so, it led Rings Extended to force close everytime something requiring changing a sound was messed with. That in turn disbaled all notifications I had set. It also completely "removed" my music from the music app. It was still on my card, but the music app did not recognize this. All this happened after enable said feature and THEN rebooting. Taking the music search off made rings extended no longer FC and all my sounds were back and my music once again showed up. Hope this helps out anyone with a similair occurence.
Up!
Anybody has the apk for Gesture Search 2.0 ? (this version presumably is compatible with N7 but is marked as incompatible on the Play Store)
TIA

[Q] LG Google TV - 47G2 - Blank Screen

I honestly didn't know where to post this, and this seemed like the most appropriate place. If I guessed wrong, please point me in the right direction.
The Problem: TV turns on and after 33 seconds the screen goes blank (instead of continuing to play live TV)
The Workaround: Hit the home button, then select the live TV and it starts again.
Here is the thread that details the issue in more detail:
http://www.googletvforum.org/forum/lg-internet-tv/5787-lg-g2-tv-problems.html
I installed the SDK so I could get some logs. It seems like once android is fully loaded is when the problem occurs. Here is the logcat of when the TV stops responding and goes to the blank screen.
The Question: Could someone take a look at the logcat below and give me an idea of what is causing this?
Code:
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
I/ActivityThread( 1668): Pub com.android.deskclock: com.android.deskclock.AlarmProvider
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
V/AlarmClock( 1668): AlarmInitReceiver finished
I/LGStartUpReceiver( 1304): BOOT COMPLETE ~!!!
I/LGStartUpReceiver( 1304):
D/dalvikvm( 1311): GC_CONCURRENT freed 2224K, 41% free 14892K/25223K, paused 9ms+3ms
D/dalvikvm( 1257): GC_CONCURRENT freed 186K, 10% free 4721K/5191K, paused 1ms+1ms
I/EzScan ( 1304): Start EZSCAN JNI registration
E/EzScan ( 1304): result = 0
E/TVControl( 1304): Start register_tvapi_tvcontrol_time
E/TVControl( 1304): result = 0
I/API_Cm ( 1304):
I/API_Cm ( 1304): Start CM API JNI function ~~!!
E/Hotkey ( 1304): Start register_tvapi_tvcontrol_hotkey
E/Hotkey ( 1304): result = 0
I/API_Tuner( 1304):
I/API_Tuner( 1304): Start TUNER API JNI function ~~!!
I/API_Mcb ( 1304):
I/API_Mcb ( 1304): Start MCB API JNI function ~~!!
I/API_Mheg( 1304):
I/API_Mheg( 1304): Start MHEG API JNI function ~~!!
I/API_Ci ( 1304):
I/API_Ci ( 1304): Start CI API JNI function ~~!!
I/API_IRBlaster( 1304):
I/API_IRBlaster( 1304): Start IRBLASTER API JNI function ~~!!
I/API_IRBlaster( 1304):
I/API_IRBlaster( 1304): Start IRBLASTER TVAPI JNI function ~~!!
I/ManualScan( 1304): Start MANUALSCAN JNI registration
E/ManualScan( 1304): result = 0
I/API_ModelDef( 1304):
I/API_ModelDef( 1304): Start Model Definition API JNI function ~~!!
I/InstartControl( 1304): #####register_tvapi_tvcontrol_instart #####
I/API_Dcc ( 1304):
I/API_Dcc ( 1304): Start DCC API JNI function ~~!!
E/GuideUtil( 1304): Start register_tvapi_tvcontrol_guideutil
E/GuideUtil( 1304): result = 0
E/ResourceClient( 1304): Start register_tvapi_tvcontrol_resource_client
E/ResourceClient( 1304): result = 0
I/API_Utility( 1304):
I/API_Utility( 1304): [JNI][API_Utiltity_SetBootComplete2TV] before Native function call
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
I/API_Utility( 1304):
I/API_Utility( 1304): [JNI][API_Utiltity_SetBootComplete2TV] after Native function call
I/LGStartUpReceiver( 1304): Start DTVService
D/LGStartUpReceiver( 1304): Boot intent is TvPlayer.
I/LGStartUpReceiver( 1304): Make tv-stack IDLE
I/TVControl( 1304):
I/TVControl( 1304): [JNI][PathControl_GoToTvIdleState] before Native function call
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
I//system/chrome/bin/chrome( 1609): [1:1:26695000:ERROR:native_library_linux.cc(32)] dlopen failed when trying to open /system/chr
ome/bin/libskia_helper.so: /system/chrome/bin/libskia_helper.so: cannot open shared object file: No such file or directory
I//system/chrome/bin/chrome( 1609): [1:1:26695000:ERROR:image_operations_plugin.cc(32)] Could not find plugin: /system/chrome/bin/
libskia_helper.so
I//system/chrome/bin/chrome( 1609): (chrome:1648): GLib-WARNING **: getpwuid_r(): failed due to unknown user id (1098)
I/TVControl( 1304):
I/TVControl( 1304): [JNI][PathControl_GoToTvIdleState] after Native function call
I/DTVService( 1304): onCreate
I/DTVService( 1304): startService
I/TvListener-JNI( 1304): android_connect_client
I/DtvService( 1304): Register dtv service client!!!!
I/IdtvService( 926): REGISTERD CLIENT !!!!!
I/DtvService( 1304): dtvService::setListener
D/TimeReceiver( 1304): TimeChanged Receive intent android.intent.action.BOOT_COMPLETED
I/TVControl( 1304):
I/TVControl( 1304): [JNI][Java_Time_setTime] before Native function call
I/TVControl( 1304):
I/TVControl( 1304): [JNI][Java_Time_setTime] after Native function call
D/TimeReceiver( 1304): Time 2012/9/19 23:20 -240
D/TimeReceiver( 1304): State auto falsenetwork truedaylight true
D/dalvikvm( 1462): GC_CONCURRENT freed 304K, 16% free 3186K/3783K, paused 1ms+6ms
I/CrashReportService.BootReceiver( 1164): got BOOT_COMPLETED event, starting service
I/ActivityManager( 1164): Start proc com.google.tv.crashreport for service com.google.tv.crashreport/.CrashReportService: pid=1701
uid=1000 gids={3003, 1007, 3002, 3001}
D/dalvikvm( 1164): No JNI_OnLoad found in /system/lib/libcrashcounter_jni.so 0x2bea46a0, skipping init
W/CrashCounter.StartupReceiver( 1164): Failed to clear crash counter, -2
I/Chrome ( 1563): Chrome loaded!
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
D/dalvikvm( 1059): GC_EXPLICIT freed 11K, 15% free 2723K/3203K, paused 6ms+2ms
W/System.err( 1311): Error reading from ./org/apache/harmony/awt/www/content/image/gif_charset_UTF_8.class
^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Google for those E/ logs, E is log level error so probably those indicate the problem. I see a function that always returns 0 while it should return something else, have you tried talking to LG?
Sent from my GT-I9100 running CM10
Multiple people have called and gotten zero response from LG.
Sent from my Nexus 7 using xda app-developers app
Any other thoughts?
Can't you reinstall the fw or wipe data?
Sent from my GT-I9100 running CM10
Several have tried and it didn't fix the issue.
Reinstall fw and wipe data? Do you have root?
Sent from my GT-I9100 running CM10
MemoryController said:
Reinstall fw and wipe data? Do you have root?
Sent from my GT-I9100 running CM10
Click to expand...
Click to collapse
I don't think anyone has root. Doing the flash wipe option in the stock build.

[APP]Viber version 2.3.3 Crashing everywhere

Hi people!
I know that at least one user here is from the Viber development team, so please, fix the very Latest Version (2.3.3). It´s simply crashes just after update. 1st I thought was a problem with my Motorola Razr I but after take a look at Google Play it seems to bug on Galaxy S2 and S3, Xperia S...
The big problem is because automatic update will not be possible anymore... I found here on XDA in an old thread someone asking an older version so I have installed it again.
Thank you!!
Hi kfirbr,
Could you please post the logcat output of the crash?
See if that part is enough:
02-20 20:47:17.149 D/StatusBar.NetworkController( 411): Wimax=0/(null) ""
02-20 20:47:17.149 D/StatusBar.NetworkController( 411): DataTypeShown=7f020134/com.android.systemui:drawable/zz_moto_stat_sys_data_not_connected_e Activity=0/(null) "Edge"
02-20 20:47:17.259 I/BootReceiver( 329): Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
02-20 20:47:17.279 I/WindowManager( 329): WIN DEATH: Window{2121fbc8 com.viber.voip/com.viber.voip.IdleActivity paused=false}
02-20 20:47:17.279 I/ActivityManager( 329): Process com.viber.voip (pid 19969) has died.
02-20 20:47:17.279 W/ActivityManager( 329): Force removing ActivityRecord{215588e8 com.viber.voip/.IdleActivity}: app died, no saved state
02-20 20:47:17.279 I/WindowManager( 329): WIN DEATH: Window{2120f840 com.viber.voip/com.viber.voip.IdleActivity paused=false}
02-20 20:47:17.309 W/IMGSRV ( 329): :0: gralloc_device_alloc: ID: 4651 handle: 0x95f8660 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.309 W/IMGSRV (19585): :0: gralloc_register_buffer: ID: 4651 handle: 0x97b9f10 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.319 W/IMGSRV ( 329): :0: gralloc_device_free: ID: 4650 handle: 0x9635660 size: 540 x 888 fmt: 2 usage: 0x933
02-20 20:47:17.329 D/Zygote ( 189): Process 19969 terminated by signal (11)
02-20 20:47:17.329 W/IMGSRV ( 329): :0: gralloc_device_alloc: ID: 4652 handle: 0x953a990 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.329 W/InputManagerService( 329): Window already focused, ignoring focus gain of: [email protected]
02-20 20:47:17.339 W/IMGSRV (19585): :0: gralloc_register_buffer: ID: 4652 handle: 0x9e4b6a0 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.339 I/Launcher(19585): onResume
02-20 20:47:17.339 I/ActivityManager( 329): Resumed Activity: com.motorola.homescreen/.Launcher totalTime: 320764 ms
02-20 20:47:17.339 I/CBStartup(19776): CB Startup : Action : android.intent.action.SERVICE_STATE
02-20 20:47:17.379 I/CBUtils (19776): ServiceState 0
02-20 20:47:17.379 I/CBUtils (19776): ServiceState 2
02-20 20:47:17.389 I/TransactionService(19746): Start transaction service, app version=.line=MSG-STAB-03.customer=timbr.device=smi.build=8.7.1I-110_SML-12.release=4.0.4.type=user.model=XT890.modelno=XT890.blur version=Blur_Version.871.110.12009.XT890.TIM.en.BR.time=09/22/12 (versionName=8.0.0.221 Build 85) (versionCode=80000221) (log=false) (ut=false) (config=false)
02-20 20:47:17.429 I/SmsReceiverService(19746): SMS-STATUS - start sms receiver service, app version=.line=MSG-STAB-03.customer=timbr.device=smi.build=8.7.1I-110_SML-12.release=4.0.4.type=user.model=XT890.modelno=XT890.blur version=Blur_Version.871.110.12009.XT890.TIM.en.BR.time=09/22/12 (versionName=8.0.0.221 Build 85) (versionCode=80000221) (log=false) (ut=false) (config=false)
02-20 20:47:17.439 W/RetryScheduler(19746): alarm already set, ignore request to set alarm again
02-20 20:47:17.559 V/ModemStatsService( 467): receive intent android.intent.action.DROPBOX_ENTRY_ADDED
02-20 20:47:17.559 V/ModemStatsService( 467): receive intent, tagname is SYSTEM_TOMBSTONE time is 1361404037573
02-20 20:47:17.599 I/CBUtils (19776): Reading database: KEY_NAME= db_key_channel
02-20 20:47:17.599 E/CBUtils (19776): setting cbChannel 50
02-20 20:47:17.599 E/CBUtils (19776): Updating CB information. Send Event to RIL
02-20 20:47:17.599 I/CBUtils (19776): Reading database: KEY_NAME= db_key_status
Viber support just sent an answer:
"Sorry for the confusion but Viber is not compatible with your device and we will not be able to provide technical support since it is untested."
How? Until the very last update Viber was perfect with my Razr I. Right now I am running 2.3.0 version and it runs flawless as I cannot find the previous a version.
The problem is not only with my Razr I, as I told them, but it´s ok for while...
More one comment. Actually that version it´s not giving a FC, but simply loads and exits without any message.
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Vibers crashes on launch
Viber Team said:
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Click to expand...
Click to collapse
Well, I just installed the latest version and keeps crashing on launch on my Razr i... not good
Please note that Viber does not officially support your device (Razr i) yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/Hm5k9p
We are continuously working to adapt Viber to more and more devices, and we hope to make your device fully compatible soon. When we have news, we'll let you know.
Hi all,
Please check out our special version of Viber for Intel devices (including Razr i): http://helpme.viber.com/index.php?/...g-issues-with-your-intel-device-and-viber-235
We'd appreciate your feedback on this new version.
Enjoy!
Hi and thank you for the answer.
That version is working fine indeed. MayI know what kind of instruction Viber fails to load on the RAZR I device?
Hurled by a Razr I
@kfirbr -
We're glad to hear all works well now
We would prefer not disclosing the technical details of the version, as it involves some of Viber's core coding and functionality. We apologize if this is not the answer you were looking for :/
Hi,
We are excited and proud to announce that we have just released a brand new product: Viber Desktop, as well as a major new update to our mobile application: Viber 3.0 for iOS and Android.
- What is Viber Desktop?
Viber for Windows/Mac lets you send free messages and make free calls to other Viber users, on any device and network, in any country!
Viber syncs your contacts, messages and call history with your mobile device, so you can start the conversation on the Viber mobile application and continue from the comfort of your PC.
In Viber Desktop you can find HD-quality voice calls, video calls, text and photo messaging, group conversations, and many more!
You can check out the cool tutorial for Viber Desktop here: https://www.youtube.com/watch?v=NEqS5W-KfRw
Download Viber, enter your phone number, and start connecting with your friends for free, from your computer!
- What's new in Viber 3.0 for iOS and Android?
Video messages, Online status and "Last online" feature, new package of fun stickers, improved user interface as well as enhanced photo experience, and much more.
Note that Viber is now designed according to Google's guidelines for android apps based on the HOLO theme (Android only).
As usual, we're here to receive your feedback and thoughts, and we'd be more than happy to assist you with any matter.
Best regards,
the Viber Team.
Viber call for ZTE Blade III pro
Hi Viber Member,
I have problem with viber calls on my cell ZTE Blade III Pro. The phone supports messages and viber calls and people can call me but not hear me, from my side, I hear perfectly. I tried to reinstal the app but it has the same problem.
Please tell me and help me if u have a solution or how to fix the problem.
Thanks :angel:
Samsung galaxy star not compatible with viber
Why is Samsung galaxy S5282 star running android jelly bean not compatible with viber?
Viber Team said:
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Click to expand...
Click to collapse
@Macedonian girl -
Hi there,
Please make sure you are not running a custom ROM on your device.
If you aren't, and the problem persists, then we would appreciate if you could take a minute and report the details to our support team using this direct link: http://bit.ly/ukGVJ0 (when you submit the ticket, please make sure to add the URL of our conversation). With this information, our development team will hopefully be able to find the source of the problem, and ultimately resolve it.
Thanks in advance
@peter12965 -
We are continuously working to adapt Viber to more and more devices, and we hope to make your device fully compatible soon. When we have news, we'll let you know.
peter12965 said:
Why is Samsung galaxy S5282 star running android jelly bean not compatible with viber?
Click to expand...
Click to collapse
It still says "Your device isn't compatible with this version" when I tried to install from Google Play.
@peter12965 -
You may try to download it directly from our HelpDesk, at: http://helpme.viber.com/index.php?/...View/100/16/cant-download-from-android-market
However, if the device is not officially compatible, we can't guarantee that it will function fully.
electricdude said:
Well, I just installed the latest version and keeps crashing on launch on my Razr i... not good
Click to expand...
Click to collapse
The same problem for galaxy S3
@mishkaxda -
Are you running a Custom ROM on your Galaxy S3?
Viber Team said:
@mishkaxda -
Are you running a Custom ROM on your Galaxy S3?
Click to expand...
Click to collapse
So here is the story,
I was running stock rom and I had successfully installed viber and it worked properly. After viber update I encountered with the bug. Then I moved to custom rom (latest paranoid android) and there was the same issue. I thought is was devise specific and then I asked my friend to install viber on galaxy note one (custom rom) there was the same problem. After that I asked my second friend to try installing viber on his brand new HTC ONE (which we have just unpacked) but there was exactly same problem on stock HTC ONE.
I am wondering maybe it is region specific?

[APP]Viber version 2.3.3 Crashing everywhere

Hi people!
I know that at least one user here is from the Viber development team, so please, fix the very Latest Version (2.3.3). It´s simply crashes just after update. 1st I thought was a problem with my Motorola Razr I but after take a look at Google Play it seems to bug on Galaxy S2 and S3, Xperia S...
The big problem is because automatic update will not be possible anymore... I found here on XDA in an old thread someone asking an older version so I have installed it again.
Thank you!!
Hi kfirbr,
Could you please post the logcat output of the crash?
See if that part is enough:
02-20 20:47:17.149 D/StatusBar.NetworkController( 411): Wimax=0/(null) ""
02-20 20:47:17.149 D/StatusBar.NetworkController( 411): DataTypeShown=7f020134/com.android.systemui:drawable/zz_moto_stat_sys_data_not_connected_e Activity=0/(null) "Edge"
02-20 20:47:17.259 I/BootReceiver( 329): Copying /data/tombstones/tombstone_02 to DropBox (SYSTEM_TOMBSTONE)
02-20 20:47:17.279 I/WindowManager( 329): WIN DEATH: Window{2121fbc8 com.viber.voip/com.viber.voip.IdleActivity paused=false}
02-20 20:47:17.279 I/ActivityManager( 329): Process com.viber.voip (pid 19969) has died.
02-20 20:47:17.279 W/ActivityManager( 329): Force removing ActivityRecord{215588e8 com.viber.voip/.IdleActivity}: app died, no saved state
02-20 20:47:17.279 I/WindowManager( 329): WIN DEATH: Window{2120f840 com.viber.voip/com.viber.voip.IdleActivity paused=false}
02-20 20:47:17.309 W/IMGSRV ( 329): :0: gralloc_device_alloc: ID: 4651 handle: 0x95f8660 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.309 W/IMGSRV (19585): :0: gralloc_register_buffer: ID: 4651 handle: 0x97b9f10 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.319 W/IMGSRV ( 329): :0: gralloc_device_free: ID: 4650 handle: 0x9635660 size: 540 x 888 fmt: 2 usage: 0x933
02-20 20:47:17.329 D/Zygote ( 189): Process 19969 terminated by signal (11)
02-20 20:47:17.329 W/IMGSRV ( 329): :0: gralloc_device_alloc: ID: 4652 handle: 0x953a990 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.329 W/InputManagerService( 329): Window already focused, ignoring focus gain of: [email protected]
02-20 20:47:17.339 W/IMGSRV (19585): :0: gralloc_register_buffer: ID: 4652 handle: 0x9e4b6a0 size: 540 x 888 fmt: 5 usage: 0xb00
02-20 20:47:17.339 I/Launcher(19585): onResume
02-20 20:47:17.339 I/ActivityManager( 329): Resumed Activity: com.motorola.homescreen/.Launcher totalTime: 320764 ms
02-20 20:47:17.339 I/CBStartup(19776): CB Startup : Action : android.intent.action.SERVICE_STATE
02-20 20:47:17.379 I/CBUtils (19776): ServiceState 0
02-20 20:47:17.379 I/CBUtils (19776): ServiceState 2
02-20 20:47:17.389 I/TransactionService(19746): Start transaction service, app version=.line=MSG-STAB-03.customer=timbr.device=smi.build=8.7.1I-110_SML-12.release=4.0.4.type=user.model=XT890.modelno=XT890.blur version=Blur_Version.871.110.12009.XT890.TIM.en.BR.time=09/22/12 (versionName=8.0.0.221 Build 85) (versionCode=80000221) (log=false) (ut=false) (config=false)
02-20 20:47:17.429 I/SmsReceiverService(19746): SMS-STATUS - start sms receiver service, app version=.line=MSG-STAB-03.customer=timbr.device=smi.build=8.7.1I-110_SML-12.release=4.0.4.type=user.model=XT890.modelno=XT890.blur version=Blur_Version.871.110.12009.XT890.TIM.en.BR.time=09/22/12 (versionName=8.0.0.221 Build 85) (versionCode=80000221) (log=false) (ut=false) (config=false)
02-20 20:47:17.439 W/RetryScheduler(19746): alarm already set, ignore request to set alarm again
02-20 20:47:17.559 V/ModemStatsService( 467): receive intent android.intent.action.DROPBOX_ENTRY_ADDED
02-20 20:47:17.559 V/ModemStatsService( 467): receive intent, tagname is SYSTEM_TOMBSTONE time is 1361404037573
02-20 20:47:17.599 I/CBUtils (19776): Reading database: KEY_NAME= db_key_channel
02-20 20:47:17.599 E/CBUtils (19776): setting cbChannel 50
02-20 20:47:17.599 E/CBUtils (19776): Updating CB information. Send Event to RIL
02-20 20:47:17.599 I/CBUtils (19776): Reading database: KEY_NAME= db_key_status
Viber support just sent an answer:
"Sorry for the confusion but Viber is not compatible with your device and we will not be able to provide technical support since it is untested."
How? Until the very last update Viber was perfect with my Razr I. Right now I am running 2.3.0 version and it runs flawless as I cannot find the previous a version.
The problem is not only with my Razr I, as I told them, but it´s ok for while...
More one comment. Actually that version it´s not giving a FC, but simply loads and exits without any message.
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Vibers crashes on launch
Viber Team said:
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Click to expand...
Click to collapse
Well, I just installed the latest version and keeps crashing on launch on my Razr i... not good
Please note that Viber does not officially support your device (Razr i) yet, and that may be the reason for the problems you are experiencing. Here is the full list of officially supported devices: http://bit.ly/Hm5k9p
We are continuously working to adapt Viber to more and more devices, and we hope to make your device fully compatible soon. When we have news, we'll let you know.
Hi all,
Please check out our special version of Viber for Intel devices (including Razr i): http://helpme.viber.com/index.php?/...g-issues-with-your-intel-device-and-viber-235
We'd appreciate your feedback on this new version.
Enjoy!
Hi and thank you for the answer.
That version is working fine indeed. MayI know what kind of instruction Viber fails to load on the RAZR I device?
Hurled by a Razr I
@kfirbr -
We're glad to hear all works well now
We would prefer not disclosing the technical details of the version, as it involves some of Viber's core coding and functionality. We apologize if this is not the answer you were looking for :/
Hi,
We are excited and proud to announce that we have just released a brand new product: Viber Desktop, as well as a major new update to our mobile application: Viber 3.0 for iOS and Android.
- What is Viber Desktop?
Viber for Windows/Mac lets you send free messages and make free calls to other Viber users, on any device and network, in any country!
Viber syncs your contacts, messages and call history with your mobile device, so you can start the conversation on the Viber mobile application and continue from the comfort of your PC.
In Viber Desktop you can find HD-quality voice calls, video calls, text and photo messaging, group conversations, and many more!
You can check out the cool tutorial for Viber Desktop here: https://www.youtube.com/watch?v=NEqS5W-KfRw
Download Viber, enter your phone number, and start connecting with your friends for free, from your computer!
- What's new in Viber 3.0 for iOS and Android?
Video messages, Online status and "Last online" feature, new package of fun stickers, improved user interface as well as enhanced photo experience, and much more.
Note that Viber is now designed according to Google's guidelines for android apps based on the HOLO theme (Android only).
As usual, we're here to receive your feedback and thoughts, and we'd be more than happy to assist you with any matter.
Best regards,
the Viber Team.
Viber call for ZTE Blade III pro
Hi Viber Member,
I have problem with viber calls on my cell ZTE Blade III Pro. The phone supports messages and viber calls and people can call me but not hear me, from my side, I hear perfectly. I tried to reinstal the app but it has the same problem.
Please tell me and help me if u have a solution or how to fix the problem.
Thanks :angel:
Samsung galaxy star not compatible with viber
Why is Samsung galaxy S5282 star running android jelly bean not compatible with viber?
Viber Team said:
Hi there!
This is Viber's rep. I'm here to help.
@kfirbr - The last version of Viber 2.3.5 should fix this issue, Please try to uninstall>reinstall from Google Play and let us know if the issue persists.
Thanks, Viber Team
Click to expand...
Click to collapse
@Macedonian girl -
Hi there,
Please make sure you are not running a custom ROM on your device.
If you aren't, and the problem persists, then we would appreciate if you could take a minute and report the details to our support team using this direct link: http://bit.ly/ukGVJ0 (when you submit the ticket, please make sure to add the URL of our conversation). With this information, our development team will hopefully be able to find the source of the problem, and ultimately resolve it.
Thanks in advance
@peter12965 -
We are continuously working to adapt Viber to more and more devices, and we hope to make your device fully compatible soon. When we have news, we'll let you know.
peter12965 said:
Why is Samsung galaxy S5282 star running android jelly bean not compatible with viber?
Click to expand...
Click to collapse
It still says "Your device isn't compatible with this version" when I tried to install from Google Play.
@peter12965 -
You may try to download it directly from our HelpDesk, at: http://helpme.viber.com/index.php?/...View/100/16/cant-download-from-android-market
However, if the device is not officially compatible, we can't guarantee that it will function fully.
electricdude said:
Well, I just installed the latest version and keeps crashing on launch on my Razr i... not good
Click to expand...
Click to collapse
The same problem for galaxy S3
@mishkaxda -
Are you running a Custom ROM on your Galaxy S3?
Viber Team said:
@mishkaxda -
Are you running a Custom ROM on your Galaxy S3?
Click to expand...
Click to collapse
So here is the story,
I was running stock rom and I had successfully installed viber and it worked properly. After viber update I encountered with the bug. Then I moved to custom rom (latest paranoid android) and there was the same issue. I thought is was devise specific and then I asked my friend to install viber on galaxy note one (custom rom) there was the same problem. After that I asked my second friend to try installing viber on his brand new HTC ONE (which we have just unpacked) but there was exactly same problem on stock HTC ONE.
I am wondering maybe it is region specific?

Where are Network Unlock Key stored?

I'm in the quest of open lining my SM-G532F. For starters when typing `#7465625*638*#` on my phone keypad, an application pop ups which asks me to enter a number of digits (I assume it to be 8 digits number). This package name is `com.sec.android.app.personalization` when I compared running `sudo ps aux | grep perso` with the application running and one without.
With this, and obtaining the PID from `ps aux`, I managed to attached gdb to the PID and analyze it. It spawns about 8 threads with thread 1 breaking at __epoll_pwait:
Code:
(gdb) info thread
Id Target Id Frame
* 1 LWP 21739 "personalization" 0xb6d4cb18 in __epoll_pwait () from target:/system/lib/libc.so
2 LWP 21744 "Signal Catcher" 0xb6d4cdec in __rt_sigtimedwait () from target:/system/lib/libc.so
3 LWP 21745 "ReferenceQueueD" 0xb6d22738 in syscall () from target:/system/lib/libc.so
4 LWP 21746 "FinalizerDaemon" 0xb6d22738 in syscall () from target:/system/lib/libc.so
5 LWP 21747 "FinalizerWatchd" 0xb6d22738 in syscall () from target:/system/lib/libc.so
6 LWP 21748 "HeapTaskDaemon" 0xb6d22738 in syscall () from target:/system/lib/libc.so
7 LWP 21749 "Binder_1" 0xb6d4cc40 in __ioctl () from target:/system/lib/libc.so
8 LWP 21750 "Binder_2" 0xb6d4cc40 in __ioctl () from target:/system/lib/libc.so
Very not interesting. What I wanted to do now is dump the memory and search for the string, "Enter Network Lock Key", to confirm I'm in the right track. But the problem right now is '/proc/pid/maps' has a ton of memory and it would take days to dump it in. So I only decided to dump only the line containing `stack ` and `libpersona.so` from /proc/pid/maps cat /proc/pid/maps | grep libpersona.so | grep stack > ~/maps
I added libpersona.so because I suspect something fishy with it. (1) It rhymes with package name (very logical I think), (2) it is mapped to /proc/pid/maps, (3) it references symbols of strcmp which used to comparing string,
And then using memdump from https://security.stackexchange.com/a/109068 (Modifying "/proc/%s/maps" to "maps" so it uses the one I catted)
But still, I haven't got a clear sign of it.
As a last resort I would brute force all 1,814,400 permutations.

Categories

Resources