Database Info

Possible major problem with new Hero ROMs

I have been using the new Fatal1ty ROM on my G1 and was seemingly having no problems whatsoever HOWEVER it transpires that people have been sending me sms messages and they have not been coming through at all. this has happened twice with one person and once with at least FIVE people in the past 24 hours.
Scouring these forums it appears that people using the JACHero ROMs are not immune to this problem either. I PLEAD with the developers here to find the root of this problem and solve it before working on making Rosie more efficient. SMS messaging is a CRUCIAL aspect of of day-to-day life for most people, and many could be unaware that they are even suffering from missing texts. The problem for me is arbitrary with no predictability, I have received messages from those whose didn't come through yesterday subsequently, so there is no problem with my network; however the original messages are still AWOL.
In the meantime I'm not touching these Hero builds and I'm going back to cupcake.
Please don't flame me, I'm not trying to put a dampener on people's enjoyment of these ROMS but I think this problem is deserving of its own thread rather than the occasional mention in a huge ROM thread which could leave it overlooked.

leoni1980 said:
I have been using the new Fatal1ty ROM on my G1 and was seemingly having no problems whatsoever HOWEVER it transpires that people have been sending me sms messages and they have not been coming through at all. this has happened twice with one person and once with at least FIVE people in the past 24 hours.
Scouring these forums it appears that people using the JACHero ROMs are not immune to this problem either. I PLEAD with the developers here to find the root of this problem and solve it before working on making Rosie more efficient. SMS messaging is a CRUCIAL aspect of of day-to-day life for most people, and many could be unaware that they are even suffering from missing texts. The problem for me is arbitrary with no predictability, I have received messages from those whose didn't come through yesterday subsequently, so there is no problem with my network; however the original messages are still AWOL.
In the meantime I'm not touching these Hero builds and I'm going back to cupcake.
Please don't flame me, I'm not trying to put a dampener on people's enjoyment of these ROMS but I think this problem is deserving of its own thread rather than the occasional mention in a huge ROM thread which could leave it overlooked.
Click to expand...
Click to collapse
This thread was really pointless this has been discussed plenty of times as well as slight fixes...check your apn settings...or open up messaging go into settings and uncheck auto retrieve then reboot and then go back and check it off....this has seem to work for some people and has also been a known tmobile issue...

Hmm. Im on the latest jac build of hero. And the only issue im having is with mms's which is a known problem.
I tend to get 300 sms's a day and the person sending me these sms's would sure as hell let me know if i didn't reply to one for some reason lol.
I do use chomp sms rather then the default one though. Not sure if this might be fixing the problem people are having.

Klarato said:
Hmm. Im on the latest jac build of hero. And the only issue im having is with mms's which is a known problem.
I tend to get 300 sms's a day and the person sending me these sms's would sure as hell let me know if i didn't reply to one for some reason lol.
I do use chomp sms rather then the default one though. Not sure if this might be fixing the problem people are having.
Click to expand...
Click to collapse
If you are on tmobile check your apn settings with the link in my Sig..hope that helps

Hey mate,
Im on three in Australia. Thanks anyway.
Are the right APN settings meant to fix the MMS? As i am fairly sure i have the right settings for my provider.
-Klara

i only missed one text today from 1 person
i guess it was more of my fault cuz i was in sams club and my 3g and edge were constantly switching so that couldve caused my problem
but other than that i havent been missing texts

This problem occurs to me too.
Even when I use chompSMS. Android receives the message, but i doesn't "give" it to the messaging app(s).
I think this is a memory issue, android seems to terminate even system processes sometimes. (I think it is)
I'm going to test it.
EDIT:Yes, memory issue... it worked while on homescreen.
Opened brwoser, send another test sms, no message got.
)
D/dalvikvm( 597): GC freed 6958 objects / 760784 bytes in 177ms
I/ActivityManager( 102): Process com.android.settings (pid 468) has died. ?
I/ActivityManager( 102): Start proc com.android.mms for broadcast com.android.m
ms/.transaction.PrivilegedSmsReceiver: pid=619 uid=10017 gids={3003}
W/dalvikvm( 619): Refusing to reopen boot DEX '/system/framework/com.htc.androi
d.pimlib.jar'
I/ActivityManager( 102): Start proc com.p1.chompsms for broadcast com.p1.chomps
ms/.sms.SmsReceivedReceiver: pid=627 uid=10065 gids={3003}
D/dalvikvm( 33): GC freed 271 objects / 10232 bytes in 187ms
I/ActivityManager( 102): Process com.android.mms (pid 619) has died.
D/dalvikvm( 33): GC freed 47 objects / 2024 bytes in 400ms
I/ActivityThread( 627): Publishing provider com.p1.chompsms.provider.ChompProvi
der: com.p1.chompsms.provider.ChompProvider
D/dalvikvm( 33): GC freed 2 objects / 48 bytes in 289ms
I/ActivityManager( 102): Process com.google.android.gm (pid 488) has died.
I/ActivityManager( 102): Low Memory: No more background processes.
W/TabControl( 597): Free WebView cache
D/dalvikvm( 175): GC freed 1118 objects / 55248 bytes in 855ms

maxisma said:
This problem occurs to me too.
Even when I use chompSMS. Android receives the message, but i doesn't "give" it to the messaging app(s).
I think this is a memory issue, android seems to terminate even system processes sometimes. (I think it is)
I'm going to test it.
EDIT:Yes, memory issue... it worked while on homescreen.
Opened brwoser, send another test sms, no message got.
)
D/dalvikvm( 597): GC freed 6958 objects / 760784 bytes in 177ms
I/ActivityManager( 102): Process com.android.settings (pid 468) has died. ?
I/ActivityManager( 102): Start proc com.android.mms for broadcast com.android.m
ms/.transaction.PrivilegedSmsReceiver: pid=619 uid=10017 gids={3003}
W/dalvikvm( 619): Refusing to reopen boot DEX '/system/framework/com.htc.androi
d.pimlib.jar'
I/ActivityManager( 102): Start proc com.p1.chompsms for broadcast com.p1.chomps
ms/.sms.SmsReceivedReceiver: pid=627 uid=10065 gids={3003}
D/dalvikvm( 33): GC freed 271 objects / 10232 bytes in 187ms
I/ActivityManager( 102): Process com.android.mms (pid 619) has died.
D/dalvikvm( 33): GC freed 47 objects / 2024 bytes in 400ms
I/ActivityThread( 627): Publishing provider com.p1.chompsms.provider.ChompProvi
der: com.p1.chompsms.provider.ChompProvider
D/dalvikvm( 33): GC freed 2 objects / 48 bytes in 289ms
I/ActivityManager( 102): Process com.google.android.gm (pid 488) has died.
I/ActivityManager( 102): Low Memory: No more background processes.
W/TabControl( 597): Free WebView cache
D/dalvikvm( 175): GC freed 1118 objects / 55248 bytes in 855ms
Click to expand...
Click to collapse
I can confirm this. Pretty useless to me now. Gonna go back to CMOD till this get worked out.

maxisma said:
This problem occurs to me too.
Even when I use chompSMS. Android receives the message, but i doesn't "give" it to the messaging app(s).
I think this is a memory issue, android seems to terminate even system processes sometimes. (I think it is)
I'm going to test it.
EDIT:Yes, memory issue... it worked while on homescreen.
Opened brwoser, send another test sms, no message got.
)
D/dalvikvm( 597): GC freed 6958 objects / 760784 bytes in 177ms
I/ActivityManager( 102): Process com.android.settings (pid 468) has died. ?
I/ActivityManager( 102): Start proc com.android.mms for broadcast com.android.m
ms/.transaction.PrivilegedSmsReceiver: pid=619 uid=10017 gids={3003}
W/dalvikvm( 619): Refusing to reopen boot DEX '/system/framework/com.htc.androi
d.pimlib.jar'
I/ActivityManager( 102): Start proc com.p1.chompsms for broadcast com.p1.chomps
ms/.sms.SmsReceivedReceiver: pid=627 uid=10065 gids={3003}
D/dalvikvm( 33): GC freed 271 objects / 10232 bytes in 187ms
I/ActivityManager( 102): Process com.android.mms (pid 619) has died.
D/dalvikvm( 33): GC freed 47 objects / 2024 bytes in 400ms
I/ActivityThread( 627): Publishing provider com.p1.chompsms.provider.ChompProvi
der: com.p1.chompsms.provider.ChompProvider
D/dalvikvm( 33): GC freed 2 objects / 48 bytes in 289ms
I/ActivityManager( 102): Process com.google.android.gm (pid 488) has died.
I/ActivityManager( 102): Low Memory: No more background processes.
W/TabControl( 597): Free WebView cache
D/dalvikvm( 175): GC freed 1118 objects / 55248 bytes in 855ms
Click to expand...
Click to collapse
I noticed that you are runing at 528 MHz... I did not have any problems until I boosted speed, try going back to default speed range and rebooting.... Just an idea...I'm doing it now..

528 MHz shouldn't be the problem..
i think it's like this:
1. Brwoser starts, eats much memory
2. Android detects an incoming SMS, starts giving it to an app
3. App is starting, want's memory which isn't avaible
4. App get's killed, SMS is lost
I'll look how it works with Swapper enabled..

On JAC Hero 2.3.3
I can confir that this issue has happened for me today also. I had to call the 2 people I was expecting a reply to to confirm that they had sent me a reply SMS. I am on the UK T-Mobile.. I may also have to revert to the Cyan fast rom until this is sorted out... I'm glad you guys have confirmed that this is a general issue rather than my Update issues.

I did the same thing you did to confirm the issue. In some instances, the messaging app got killed.
Then, I saw on the JACHero thread that you need to disable "automatic retreival" from the messaging app, reboot, then enable it.
I ran the same test afterwards, and 10 messages in a row during high usage of browser with flash on the htc.com page, I have not had any missed messages.
Hopefully, that's the fix. I know it sounds strange.
EDIT: Never mind, it still happens.

npace said:
I did the same thing you did to confirm the issue. In some instances, the messaging app got killed.
Then, I saw on the JACHero thread that you need to disable "automatic retreival" from the messaging app, reboot, then enable it.
I ran the same test afterwards, and 10 messages in a row during high usage of browser with flash on the htc.com page, I have not had any missed messages.
Hopefully, that's the fix. I know it sounds strange.
Click to expand...
Click to collapse
I think this has worked, got a txt almost straight after I did this... Will have to confirm this over time though. Hero 2.3.3 and the Optimised Rosie are the closest to a fully usable Hero now and the more I use it the more I like it... Lack of SMS would have to be a deal breaker for me, already had an argument with the GF about that!

I submitted it as a bug at http://code.google.com/p/jacheroplus

I'm glad I'm not the only one having this problem. I text more than I talk on my phone. It seems that when I ask some to text me it works but then a friend will text something and I won't get it. If this issue gets sorted out then JACHero is my rom of choice.

abteer said:
I'm glad I'm not the only one having this problem. I text more than I talk on my phone. It seems that when I ask some to text me it works but then a friend will text something and I won't get it. If this issue gets sorted out then JACHero is my rom of choice.
Click to expand...
Click to collapse
The same for me!
This sms problem is the only that stops me from using stably JacHero rom

Anyone know if they still get this problem with Swapper enabled? I haven't lost any text messages, but I might just not know it... hehe

Guys I jsut got off the phone with T-Mobile, I live in USA Midwest, and they have confirmed they are having problems with their sms/mms servers.
It first started where their servers would report completely wrong times and your texts would show wrong times from people received, and I guess this is what is causing problems with certain people receiving their sms and certain not.

sxfx said:
Guys I jsut got off the phone with T-Mobile, I live in USA Midwest, and they have confirmed they are having problems with their sms/mms servers.
It first started where their servers would report completely wrong times and your texts would show wrong times from people received, and I guess this is what is causing problems with certain people receiving their sms and certain not.
Click to expand...
Click to collapse
It occurs on o2 Germany too.

Glad i'm not the only one then. Seems this problem isn't resolved after all.
I originally installed the Jachero ROM. I installed Handcent and received a couple of messages but when i selected them from the notification bar they had disappeared and i was unable to read them. The next day I tried out the fatal1ty ROM and it was only this morning, approximately 24 hours later that I started to find out that I'd been sent texts but had not received all of them, nor even received a notification.
I am on T-Mobile UK and am absolutely certain it is not a network issue.
With respect to enabling automatic retrieval in message settings, I fail to see how this is relevant as it is my understanding that SMS uses GSM and the APN settings are irrelevant. I could put 'Im a potato' as my APN address and i would still get texts ok in theory.
This really is a HORRIBLE problem, as we NEVER know for certain if we are receiving text messages. I really like the newest Hero releases BUT i simply CANNOT go back to them until someone finds the root cause of this problem and fixes it.

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

[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?

[APP][FOSS][4+] TrebleShot - File Sharing Application

An Open-Source Android application that allows you to send and receive files over available connections, and pause and resume transfer process. For more please visit related Google Play, F-Droid or GitHub pages.
Get it on F-Droid or Google Play or visit GitHub repo https://github.com/genonbeta/TrebleShot for more.

Nice!
Glad to see open source solution for this kind of functionality. I definitely support it.

light and fast thumbs up

Updated: 1.20 Beta 4

This is probably the only open source app of its kind. Every other similar apps are proprietary and heavy garbages.
Would it be possible to include it in f-droid for a lot of us who don't have gapps? It would gain more publicity too. Thanks!

rms112 said:
This is probably the only open source app of its kind. Every other similar apps are proprietary and heavy garbages.
Would it be possible to include it in f-droid for a lot of us who don't have gapps? It would gain more publicity too. Thanks!
Click to expand...
Click to collapse
Thank you for your reply, it means a lot to me and yes, I was thinking of that but haven't had time to make a pull request. I'm hoping to that today. Thanks again

Thanks a lot for publishing in f-droid.

I love your app, I have been using it for a while now.
Any chance you are planing a desktop version?
It would be nice to be able to move files between all my devices in my home network with a nice open source app.

flocke000 said:
I love your app, I have been using it for a while now.
Any chance you are planing a desktop version?
It would be nice to be able to move files between all my devices in my home network with a nice open source app.
Click to expand...
Click to collapse
Thanks for your comment. I'm hoping to start developing a desktop app (most likely to be for linux) after the next release of the android version. I'm currently having some difficulties with my pc setup. Thanks again and hang tight

veli.tasali said:
Thanks for your comment. I'm hoping to start developing a desktop app (most likely to be for linux) after the next release of the android version. I'm currently having some difficulties with my pc setup. Thanks again and hang tight
Click to expand...
Click to collapse
Nice, I'm on Linux most of the time anyways so a Linux version is fine with me
If you use Qt5 to build it it should be easily to port to Windows later on so you might want to consider that

I LOVE this app!
Are there any plans for releasing a Windows desktop app so we can also share files between Android and Windows?

Keeping fingers crossed for a Windows version. Would be a great improvement over FTP transfers. The ability to resume transfer would be really nice.
Thanks for making it available on F-Droid.

Hello @veli.tasali
I tested your app, but for some reason, i am able to finish a transfer from device A to B but not from B to A.
Ive attached the logcat from device A which can accept the transfer, but does not finish the transaction, always errors out.
Secondly, i cant see the device A, if i am connected to a vpn on it, i had to disable the VPN so as to discover it from device B.
Is this a known issue?
Thanks for the opensource app!

ashjas said:
Hello @veli.tasali
I tested your app, but for some reason, i am able to finish a transfer from device A to B but not from B to A.
Ive attached the logcat from device A which can accept the transfer, but does not finish the transaction, always errors out.
Secondly, i cant see the device A, if i am connected to a vpn on it, i had to disable the VPN so as to discover it from device B.
Is this a known issue?
Thanks for the opensource app!
Click to expand...
Click to collapse
For the VPN issue, it is probably because your VPN application routes "wlan0" (Wi-Fi) interface to "tun0" (stands for VPN interface) which causes the request made to the local interface goes to your DNS then as it fails because it is on your device not on the internet. This should be the reason but I don't know if your VPN service can fix this (since I don't know how VPN interfaces are created using Android VPN API).
For the other issue;
Do you use any power management tool or battery tool that kills the application in the background? The log does not tell much.
Only this which says that you cancelled the task
Code:
09-30 11:39:51.031 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Cancel is requested. Exiting.
09-30 11:39:51.031 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Updating file instances to INTERRUPTED
09-30 11:39:51.043 D/NuPlayerDriver( 295): NuPlayerDriver(0xb4893f00) created, clientPid(639)
09-30 11:39:51.050 D/GenericSource( 295): FileSource remote
09-30 11:39:51.069 D/NuPlayerDriver( 295): notifyListener_l(0xb4893f00), (1, 0, 0, -1), loop setting(0, 0)
09-30 11:39:51.098 D/StatusBar( 639): disable<e i a s b h r c s q >
09-30 11:39:51.113 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Removing notification an error is already notified
09-30 11:39:51.114 W/System.err(21803): java.net.SocketException: Socket is closed
09-30 11:39:51.114 W/System.err(21803): at java.net.Socket.getInputStream(Socket.java:930)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.TrebleShot.service.CommunicationService$SeamlessClientHandler.onConnect(CommunicationService.java:1181)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.CoolSocket.CoolSocket.connect(CoolSocket.java:61)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.CoolSocket.CoolSocket$1.run(CoolSocket.java:76)
09-30 11:39:51.121 D/CommunicationService(21803): We have exited
If you think this is an actual issue related to the app, please open an issue on the issue tracker https://github.com/genonbeta/TrebleShot/issues

veli.tasali said:
For the VPN issue, it is probably because your VPN application routes "wlan0" (Wi-Fi) interface to "tun0" (stands for VPN interface) which causes the request made to the local interface goes to your DNS then as it fails because it is on your device not on the internet. This should be the reason but I don't know if your VPN service can fix this (since I don't know how VPN interfaces are created using Android VPN API).
For the other issue;
Do you use any power management tool or battery tool that kills the application in the background? The log does not tell much.
Only this which says that you cancelled the task
Code:
09-30 11:39:51.031 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Cancel is requested. Exiting.
09-30 11:39:51.031 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Updating file instances to INTERRUPTED
09-30 11:39:51.043 D/NuPlayerDriver( 295): NuPlayerDriver(0xb4893f00) created, clientPid(639)
09-30 11:39:51.050 D/GenericSource( 295): FileSource remote
09-30 11:39:51.069 D/NuPlayerDriver( 295): notifyListener_l(0xb4893f00), (1, 0, 0, -1), loop setting(0, 0)
09-30 11:39:51.098 D/StatusBar( 639): disable
09-30 11:39:51.113 D/CommunicationService(21803): SeamlessClientHandler.onConnect(): Removing notification an error is already notified
09-30 11:39:51.114 W/System.err(21803): java.net.SocketException: Socket is closed
09-30 11:39:51.114 W/System.err(21803): at java.net.Socket.getInputStream(Socket.java:930)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.TrebleShot.service.CommunicationService$SeamlessClientHandler.onConnect(CommunicationService.java:1181)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.CoolSocket.CoolSocket.connect(CoolSocket.java:61)
09-30 11:39:51.115 W/System.err(21803): at com.genonbeta.CoolSocket.CoolSocket$1.run(CoolSocket.java:76)
09-30 11:39:51.121 D/CommunicationService(21803): We have exited
If you think this is an actual issue related to the app, please open an issue on the issue tracker https://github.com/genonbeta/TrebleShot/issues
Click to expand...
Click to collapse
I dont cancel the transfer. It errors out on its own. The recieving device is on LOS 15.1.
The log is full log, not trimmed in any way.
This happens while i am in the app's foreground activity, so no question of app in background. And no power management settings that i am enforcing.

is there a way to transfer files to a phone that doesnt have this app installed? I tried sending something to my laptop using a hotspot on Android 8.1 but nothing happens even after my laptop connects to the network.
If it cant are there any file transfer apps that allow the reciever to not have this app installed on their phone>?