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.

Aldiko + Cyanogen 5.0.2-5.0.5

Anyone else use Aldiko with one of those CM releases?
I'm noticing that when you exit the book and return it returns to the beginning of the chapter which isn't normal behavior here. I don't know if it did this with the stock N1 or not but I know it isn't supposed to reset to chapter beginning nor did that happen on the G1.

It does not do that on my stock N1, but I haven't used cyanogenmod to see if the behavior changes directly due to that.

DevPhone1337 said:
It does not do that on my stock N1, but I haven't used cyanogenmod to see if the behavior changes directly due to that.
Click to expand...
Click to collapse
It's what I'm kind of thinking is the X factor causing this.

im getting the same behavior. i recall aldiko working fine for the day i had my nexus before rooting it.

sinbot said:
Anyone else use Aldiko with one of those CM releases?
I'm noticing that when you exit the book and return it returns to the beginning of the chapter which isn't normal behavior here. I don't know if it did this with the stock N1 or not but I know it isn't supposed to reset to chapter beginning nor did that happen on the G1.
Click to expand...
Click to collapse
I've had it do that for a while, then on the last upgrade I did a wipe and fix permissions. Might want to try uninstall/reinstall before trying a wipe.

Hmm. Tried wipe reinstall and all that. I'm not so much annoyed as curious what would cause that in a custom ROM.

Mine has same issue, hope it will be solved soon.

Have you emailed the author of the app? Why just sit around and hope it eventually gets fixed?

On mine, with CM 5.0.3, it messed up the book titles on the first screen, where it shows the recently opened books at the top. When I click on the actual bookshelf, it's fine. Not sure about the chapter thing, though...

It worked fine when I first got my nexus one.
Then when i rooted and installed a baked rom it went to **** resetting chapetrs after close.

On my N1, Aldiko has always reset to the beginning of the chapter. I have only recently rooted my phone and installed CM on it, and the app still resets to the beginning when I exit out. I always thought it was supposed to do that and it was quite annoying to have to remember to save a bookmark every time I finished reading.

prettyboy85712 said:
Have you emailed the author of the app? Why just sit around and hope it eventually gets fixed?
Click to expand...
Click to collapse
I don't think this is app's issue cause aldiko worked well with stock rom. When I root the phone and install Cyanogen 5, the issue came.

sinbot said:
Hmm. Tried wipe reinstall and all that. I'm not so much annoyed as curious what would cause that in a custom ROM.
Click to expand...
Click to collapse
I wish I checked the logs when this was happening. I suspect it has something to do with write access to save a default bookmark. Did the wipe help? Other things to try is recovery > others > fix permissions and wipe > dalvik cache

tamarian said:
I wish I checked the logs when this was happening. I suspect it has something to do with write access to save a default bookmark. Did the wipe help? Other things to try is recovery > others > fix permissions and wipe > dalvik cache
Click to expand...
Click to collapse
I don't think it'll solve the issue, cause everytime I upgrade Cyanogen ROM, I always do wipe data and dalvik cache.

same here, just wrote to customer support...

prettyboy85712 said:
Have you emailed the author of the app? Why just sit around and hope it eventually gets fixed?
Click to expand...
Click to collapse
Why did you assume I hadn't? I was trying to see if it was a problem with Android 2.1 or Cyanogenmod.

tamarian said:
I wish I checked the logs when this was happening. I suspect it has something to do with write access to save a default bookmark. Did the wipe help? Other things to try is recovery > others > fix permissions and wipe > dalvik cache
Click to expand...
Click to collapse
I did get a logcat of it and sent it to the developer. I don't know if it was helpful or not This is what I sent:
***My actions were
Open Aldiko
Select book
Advance page
hit back button
reopen book and it's back at the chapter start
***
I/ActivityManager( 90): Start proc com.android.aldiko for activity com.android
.aldiko/.ui.HomeScreen: pid=8846 uid=10050 gids={3003, 1015}
I/WindowManager( 90): Setting rotation to 1, animFlags=0
I/ActivityManager( 90): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=2 layout=34}
V/RenderScript_jni( 195): surfaceDestroyed
V/RenderScript( 195): setSurface 0 0 0x0
D/ViewFlipper( 195): updateRunning() mVisible=false, mStarted=true, mUserPresen
t=true, mRunning=false
I/ActivityThread( 8846): Publishing provider com.android.aldiko.provider.catalog
: com.android.aldiko.provider.CatalogContentProvider
D/dalvikvm( 186): GC freed 7113 objects / 282680 bytes in 116ms
I/ActivityThread( 8846): Publishing provider com.android.aldiko.provider.library
: com.android.aldiko.provider.LibraryContentProvider
I/ActivityThread( 8846): Publishing provider com.android.aldiko.provider.BookVie
wSearchSuggestions: com.android.aldiko.provider.BookViewSearchSuggestionsProvide
r
I/ActivityThread( 8846): Publishing provider com.android.aldiko.provider.filesys
tem: com.android.aldiko.provider.FileSystemContentProvider
D/dalvikvm( 90): GC freed 10381 objects / 460088 bytes in 183ms
D/dalvikvm( 8846): GC freed 2490 objects / 150656 bytes in 75ms
D/dalvikvm( 8846): GC freed 700 objects / 187736 bytes in 40ms
D/webviewglue( 8846): nativeDestroy view: 0x11c380
E/webcoreglue( 8846): The real object has been deleted
W/IInputConnectionWrapper( 195): showStatusIcon on inactive InputConnection
I/ActivityManager( 90): Displayed activity com.android.aldiko/.ui.HomeScreen:
1576 ms (total 1576 ms)
D/dalvikvm( 90): GC freed 2344 objects / 103752 bytes in 129ms
I/ActivityManager( 90): Starting activity: Intent { act=android.intent.action.
VIEW dat=content://com.android.aldiko.provider.library/books/3 cmp=com.android.a
ldiko/.bookview.BookViewActivity }
I/WindowManager( 90): Setting rotation to 0, animFlags=0
I/ActivityManager( 90): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=1 layout=34}
W/Resources( 8846): Converting to int: TypedValue{t=0x3/d=0x331 "2" a=2 r=0x7f07
0000}
D/dalvikvm( 186): GC freed 1039 objects / 47712 bytes in 135ms
D/dalvikvm( 8846): GC freed 1552 objects / 156664 bytes in 77ms
I/ActivityManager( 90): Displayed activity com.android.aldiko/.bookview.BookVi
ewActivity: 759 ms (total 759 ms)
D/dalvikvm( 8846): GC freed 2481 objects / 1076552 bytes in 86ms
D/dalvikvm( 8846): GC freed 1793 objects / 754368 bytes in 66ms
D/dalvikvm( 90): GC freed 2055 objects / 102296 bytes in 131ms
D/dalvikvm( 8846): GC freed 4245 objects / 797224 bytes in 48ms
W/InputManagerService( 90): Window already focused, ignoring focus gain of: co
[email protected]
W/KeyCharacterMap( 8846): No keyboard for id 65540
W/KeyCharacterMap( 8846): Using default keymap: /system/usr/keychars/qwerty.kcm.
bin
W/ActivityManager( 90): Activity pause timeout for HistoryRecord{45f41cb0 com.
android.aldiko/.bookview.BookViewActivity}
I/WindowManager( 90): Setting rotation to 1, animFlags=0
I/ActivityManager( 90): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=2 layout=34}
D/dalvikvm( 186): GC freed 1019 objects / 46840 bytes in 297ms
D/dalvikvm( 90): GC freed 2318 objects / 110032 bytes in 107ms
D/dalvikvm( 90): GC freed 621 objects / 24688 bytes in 133ms
I/ActivityManager( 90): Starting activity: Intent { act=android.intent.action.
VIEW dat=content://com.android.aldiko.provider.library/books/3 cmp=com.android.a
ldiko/.bookview.BookViewActivity }
I/WindowManager( 90): Setting rotation to 0, animFlags=0
I/ActivityManager( 90): Config changed: { scale=1.0 imsi=310/260 loc=en_US tou
ch=3 keys=1/1/2 nav=3/1 orien=1 layout=34}
D/dalvikvm( 186): GC freed 681 objects / 33784 bytes in 121ms
W/Resources( 8846): Converting to int: TypedValue{t=0x3/d=0x331 "2" a=2 r=0x7f07
0000}
D/dalvikvm( 8846): GC freed 5208 objects / 491072 bytes in 40ms
D/webviewglue( 8846): nativeDestroy view: 0x413c00
E/webcoreglue( 8846): The real object has been deleted
I/ActivityManager( 90): Displayed activity com.android.aldiko/.bookview.BookVi
ewActivity: 630 ms (total 630 ms)
D/dalvikvm( 8846): GC freed 3877 objects / 1295976 bytes in 72ms
D/dalvikvm( 90): GC freed 1444 objects / 68328 bytes in 117ms
D/dalvikvm( 8846): GC freed 2851 objects / 1043544 bytes in 37ms
W/InputManagerService( 90): Window already focused, ignoring focus gain of: co
[email protected]
D/WifiService( 90): ACTION_BATTERY_CHANGED pluggedType: 2
D/NetworkLocationProvider( 90): onCellLocationChanged [35809,33391]
D/dalvikvm( 557): GC freed 7521 objects / 469560 bytes in 136ms
D/NetworkLocationProvider( 90): onCellLocationChanged [35809,33392]

bump for readers

Anybody else having issue of the book titles looking like morse code on the Recent Read row?

SiNJiN76 said:
Anybody else having issue of the book titles looking like morse code on the Recent Read row?
Click to expand...
Click to collapse
+1.
I've tried other roms, here is my result:
With Enomther 1.7.1 and stock rom: Things are ok, Aldiko starts with the page which I read before, not the chapter; the book titles are ok.
With Cyanogen 5.x and CyanogenMod rom Bakedgoods: There are issues, Aldiko reset at the beginning of the chapter, the book titles on the recent read look like you said, can't see it.
Sorry for my bad English

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

com.htc.bg closes on Facebook Sync!

I have a problem... when I sync facebook, the process com.htc.bg closes.
These are the steps that I have done:
1. Wiped Dalvik, Factory, SD ext, etc... then reflashed - failed
2. Add Facebook for Sense, removed, scrolled contacts, readded... repeat - failed
3. Added Facebook for Android - failed
4. Removed Facebook for Android - failed
5. lowered AutoKiller back to default - failed
6. Prayed... - ??
Any ideas?? I will post logcat.
Logcat:
Code:
V/SocialNetworkSyncManager( 2572): MSG_START_SYNC: facebook , syncType:65535 , t
ime: 2010-04-05 15:54:22
D/SocialNetworkSyncManager( 2572): mDuringSync is TRUE at MSG_START_SYNC , faceb
ook , time: 2010-04-05 15:54:22
D/dalvikvm( 2572): GC freed 5185 objects / 349904 bytes in 193ms
D/SocialNetwork-SimpleFacebookInterface( 2572): NO GZIP
D/SocialNetwork-UserSyncTask( 2572): Got user SUCCESS
D/SocialNetwork-UserSyncTask( 2572): Got user object by ID: 1291050488
D/SocialNetwork-UserSyncTask( 2572): Start to write user info:1291050488
D/SocialNetwork-UserSyncTask( 2572): END to writing user info: 1291050488
D/SocialNetwork-UserSyncTask( 2572): starting FacebookDbWriter
D/SocialNetwork-UserSyncTask( 2572): Start sync friends
D/SocialNetwork-UserSyncTask( 2572): 1291050488 start get friends
I/SyncControl_People( 2486): Sync active detected - Account: [[email protected]
ail.com/com.google], authority: subscribedfeeds, autoSyncFlag: 1
I/SyncControl_Dialer( 181): Sync active detected - Account: [[email protected]
ail.com/com.google], authority: subscribedfeeds, autoSyncFlag: 1
D/dalvikvm( 163): GC freed 199 objects / 9120 bytes in 226ms
D/dalvikvm( 166): GC freed 320 objects / 12400 bytes in 175ms
D/SocialNetwork-SimpleFacebookInterface( 2572): GZIP encoded stream
D/dalvikvm( 2572): GC freed 2852 objects / 234400 bytes in 179ms
D/dalvikvm( 2572): GC freed 116 objects / 96456 bytes in 175ms
D/dalvikvm( 2572): GC freed 8 objects / 83264 bytes in 178ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 4.230MB for 186670-byte allocat
ion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 182ms
D/dalvikvm( 2572): GC freed 10 objects / 124840 bytes in 172ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 4.378MB for 280000-byte allocat
ion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 190ms
D/dalvikvm( 2572): GC freed 15 objects / 187304 bytes in 176ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 4.601MB for 419996-byte allocat
ion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 189ms
D/dalvikvm( 2572): GC freed 20 objects / 280872 bytes in 172ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 4.935MB for 629990-byte allocat
ion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 194ms
D/dalvikvm( 2572): GC freed 28 objects / 421256 bytes in 177ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 5.436MB for 944980-byte allocat
ion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 188ms
D/dalvikvm( 2572): GC freed 42 objects / 632040 bytes in 174ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 6.187MB for 1417466-byte alloca
tion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 204ms
D/dalvikvm( 2572): GC freed 61 objects / 948088 bytes in 173ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 7.313MB for 2126194-byte alloca
tion
D/dalvikvm( 2572): GC freed 0 objects / 0 bytes in 212ms
D/dalvikvm( 2572): GC freed 89 objects / 1422088 bytes in 178ms
I/dalvikvm-heap( 2572): Grow heap (frag case) to 9.003MB for 3189286-byte alloca
tion
D/CIQ ( 112): throwUI05 com.htc.bg
W/ContentService( 112): binderDied() at ObserverNode name services
D/CIQ ( 112): processName com.htc.bg
I/ActivityManager( 112): Process com.htc.bg (pid 2572) has died.

MrDanger said:
I have a problem... when I sync facebook, the process com.htc.bg closes.
These are the steps that I have done:
1. Wiped Dalvik, Factory, SD ext, etc... then reflashed - failed
2. Add Facebook for Sense, removed, scrolled contacts, readded... repeat - failed
3. Added Facebook for Android - failed
4. Removed Facebook for Android - failed
5. lowered AutoKiller back to default - failed
6. Prayed... - ??
Any ideas?? I will post logcat.
Click to expand...
Click to collapse
I've been trying to help him, and I can't find a reason why it's doing this. Someone please help him.

Anybody have any kind of insight??

It's happened randomly on mine as well. I really think it's something to do with the AutoKiller or memory settings. I'm on Fresh 2.0d, but eventually got my FB to sync two days later.

jeric71 said:
It's happened randomly on mine as well. I really think it's something to do with the AutoKiller or memory settings. I'm on Fresh 2.0d, but eventually got my FB to sync two days later.
Click to expand...
Click to collapse
There is no random here... every time I plug up... "com.htc.bg" closes.
I dont even know what that is! All I know is that Google Calendars use it to sync too.

Has anyone found a solution to this yet

jimsaf said:
Has anyone found a solution to this yet
Click to expand...
Click to collapse
I ended up having too many friends on my friends list... it caused com.htc.bg to close because it ran out of memory for my friends list.
I just went on a deleting spree.

I had this problem and found that it was cause due to me having a nick name or a middle name on my facebook account. My facebook profile was damian 'damo' holt. However for some reason it didnt like the ' characters and would fail to sync correctly.
I simply removed my middle name from facebook account settings.
Removed my facebook account
cleared date from facebook and contatcs
reboot
re add facebook account wait a short while and all contatcs synced fine. I have 700 facebook friends and dont have a problem since doing this.
Hope this helps.

I don't know how to 'fix' it but, i know how to get rid of it. If you uncheck Sync Contacts it will stop the FC error. Then you can download the FB Sync app in the market for free and use that one. It will also save the picture to your contact so it will be with all your google accounts.

djmace said:
I had this problem and found that it was cause due to me having a nick name or a middle name on my facebook account. My facebook profile was damian 'damo' holt. However for some reason it didnt like the ' characters and would fail to sync correctly.
I simply removed my middle name from facebook account settings.
Removed my facebook account
cleared date from facebook and contatcs
reboot
re add facebook account wait a short while and all contatcs synced fine. I have 700 facebook friends and dont have a problem since doing this.
Hope this helps.
Click to expand...
Click to collapse
Mate, you are nothing short of a genius. That's what the exact issue was for me and now is sorted. I could kiss you right now! My phone is awesome again!

No such luck for me and I've done all of the above things : /

djmace said:
I had this problem and found that it was cause due to me having a nick name or a middle name on my facebook account. My facebook profile was damian 'damo' holt. However for some reason it didnt like the ' characters and would fail to sync correctly.
I simply removed my middle name from facebook account settings.
Removed my facebook account
cleared date from facebook and contatcs
reboot
re add facebook account wait a short while and all contatcs synced fine. I have 700 facebook friends and dont have a problem since doing this.
Hope this helps.
Click to expand...
Click to collapse
The solution works for me !!
There is a "apostrophe" in my last name ...
Since I removed the "apostrophe", from my last name, on my facebook profile, the process com.htc.bg doesn't crash anymore
Thank you so much

no special characters in my name and i don't even have fb enabled on my phone, yet i get this error almost every time i use my phone.

any solutions to this?

can any one help tried all the above with no luck ..

[WIP] How to edit the max sending size for MMS?

I am trying to figure out how to change the max sending size for MMS on the EVO. By default when sending pictures it compresses them down to around 60k. It was accomplished on the Nexus One HERE and the G1 HERE. The MMS.apk for the EVO does not have the same file to modify as the Nexus One, and I can't figure out which xml to edit. The default compression for MMS is ridiculous on the EVO, by default when sending pictures it compresses them down to around 60k. We should be able to set it to 300k and not have any problems.
No offense to anyone, but please do NOT reply with "hancent works for this, xxx can do this, such and such fixed this", or any other app/ROM/etc for that matter.
I am asking how to modify the stock EVO MMS app, not how to install a different ROM or app!
Here is the original EVO MMS.apk (Froyo)

the max on the Evo is 2m it would be nice to have more but thats the max the way you see what your max is set to is go to all message screen then press menu go to settings then it will be maximum message size

stercast said:
the max on the Evo is 2m it would be nice to have more but thats the max the way you see what your max is set to is go to all message screen then press menu go to settings then it will be maximum message size
Click to expand...
Click to collapse
I don't think you understand my question/problem. Read the Nexus One link in the OP. The issue is when sending MMS, the EVO compresses the living hell out of any image. That 2mb setting you are referring to is not the same thing, that is an overall message size, not individual image size.

I was wondering if anyone else was annoyed by this. I wish I could help you in some way though..
I hope this gets resolved.

i believe the evio rom fixed this issue

zaft1 said:
i believe the evio rom fixed this issue
Click to expand...
Click to collapse
Well, the dev of that ROM says he fixed this, but not how. It would be nice if he would share the fix with everyone.

I sure hope someone gets this done, the compression is really annoying.
Tapatalk'd on Evo

Could a possible workaround be to zip said pic and send the zip? I don't remember if I tested this or not when I was experimenting with the mms apps.

SteelH
I have looked in the preference_att.xml and preference.xml and found pref_key_mms_max_size. I dont understand binary so I am not much help here.

dwertz said:
SteelH
I have looked in the preference_att.xml and preference.xml and found pref_key_mms_max_size. I dont understand binary so I am not much help here.
Click to expand...
Click to collapse
I saw that as well, but there is no byte size near it to edit like in the Nexus One.

SteelH said:
I saw that as well, but there is no byte size near it to edit like in the Nexus One.
Click to expand...
Click to collapse
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.

MrDSL said:
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.
Click to expand...
Click to collapse
I have asked him, he has not replied. Also, I can tell you simply using the mms.apk from his ROM will not solve the compression problem.

if you use chomp sms there's a selection for no limit on mms size you could pull that apk apart and see what it uses to regulate the size limit

BLOWNCO said:
if you use chomp sms there's a selection for no limit on mms size you could pull that apk apart and see what it uses to regulate the size limit
Click to expand...
Click to collapse
Good suggestion but unfortunately that won't help us.

I hope someone fixes this issue. I always wondered why the stock MMS compresses images so much. Its terrible. I shall be keeping watch for anything.

Is there a way to be able to dicifer logcat by starting it right when you add the picture and when it autosizes to see what's doing it? Here is a logcat of when I attach a picture to mms when it auto resizes if anyone knows whats doing it.
Code:
D/ComposeMessageActivity( 564): initFocus: true
D/ComposeMessageActivity( 564): syncRecipientListButton:
D/ComposeMessageActivity( 564): mRecipientList.size(): 0
D/Jerry1 ( 564): 2222
I/XT9_C ( 195): [loadDefaultDB] xt9_raw/ldb_0409.ldb size=98056 (loaded)
I/XT9_C ( 195): [registerXT9LDB] ldb_0409.ldb loading [done]
D/XT9_ldb ( 195): wLdbNum=109, first wLdbNum=109, second wLdbNum=0
D/XT9_C ( 195): [registerXT9LDB] current LdbNum=109, First LdbNum=109, Second LdbNum=0
D/dalvikvm( 195): GC_EXTERNAL_ALLOC freed 304 objects / 15192 bytes in 164ms
D/ComposeMessageActivity( 564): get the ContactNameCache
D/MainActivity( 5880): [HTCAlbum][MainActivity][onStop]: Begin
D/dalvikvm( 564): GC_EXTERNAL_ALLOC freed 402 objects / 49256 bytes in 56ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 70 objects / 25688 bytes in 41ms
I/dalvikvm-heap( 564): Grow heap (frag case) to 3.863MB for 63504-byte allocation
D/dalvikvm( 564): GC_FOR_MALLOC freed 0 objects / 0 bytes in 69ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 4 objects / 30840 bytes in 41ms
I/dalvikvm-heap( 564): Grow heap (frag case) to 3.957MB for 129040-byte allocation
D/dalvikvm( 564): GC_FOR_MALLOC freed 0 objects / 0 bytes in 65ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 7 objects / 67784 bytes in 48ms
D/dalvikvm( 564): GC_FOR_MALLOC freed 7 objects / 129272 bytes in 42ms
V/MmsProvider( 212): Insert uri=content://mms/9223372036854775807/part, match=11
D/dalvikvm( 5880): GC_EXPLICIT freed 1562 objects / 103600 bytes in 585ms
D/MainActivity( 5880): [HTCAlbum][MainActivity][onDestroy]: Begin
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/PduPersister( 564): Saving data to: content://mms/part/43
D/MediaPicker( 564): --------original uri: content://mms/part/43, type: null
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/UriImage( 564): ---------mContentType: image/jpeg
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/ComposeMessageActivity( 564): onMediaPicked:media: image/jpeg
I/MessageBodyEditor( 564): addMedia:> [email protected]
D/ComposeMessageActivity( 564): updateMessageBodyContentUI:
V/ComposeMessageActivity( 564): Message type: SMS -> MMS
D/MessageTextEditor( 564): resetCounter:SmsMode> false
D/ComposeMessageActivity( 564): checkReachRecipientMaxNumber> 0, updateUI> true
D/MessageBodyEditor( 564): EditableMediaViewFactory.create()[email protected]
I/EditableMediaViewImpl( 564): onFinishInflate:
D/MessageUtils( 564): loadThumbnailBitmap: content://mms/part/43
D/dalvikvm( 212): GC_FOR_MALLOC freed 11212 objects / 585848 bytes in 60ms
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/dalvikvm( 564): GC_FOR_MALLOC freed 1222 objects / 345504 bytes in 43ms
V/MmsProvider( 212): Query uri=content://mms/part/43, match=12
D/MessageUtils( 564): Create message thumbnail cache file: /data/data/com.android.mms/cache/PART_1282502974576
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: Begin
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: [email protected] size: 0
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: No more clients. release resources.
D/OnlineDataCenter( 5880): [HTCAlbum][OnlineDataCenter][unbindContext]: End 0
I/XT9_C ( 195): [loadDefaultDB] xt9_raw/ldb_0409.ldb size=98056 (loaded)
D/ThumbnailWorker( 5880): [stopWorking] Stop working, now join #-1, Decode Complete!!
I/XT9_C ( 195): [registerXT9LDB] ldb_0409.ldb loading [done]
D/XT9_ldb ( 195): wLdbNum=109, first wLdbNum=109, second wLdbNum=0
D/XT9_C ( 195): [registerXT9LDB] current LdbNum=109, First LdbNum=109, Second LdbNum=0
D/AlbumAdapter( 5880): set thread priority to normal
D/AlbumMapper( 5880): cancel current decode operation
D/AlbumMapper( 5880): cancel current decode operation
D/ThumbnailWorker( 5880): [stopWorking] Stop working, now join #-1, Decode Complete!!
D/AlbumAdapter( 5880): set thread priority to normal
D/AlbumAdapter( 5880): Join worker thread in destroy
D/AlbumAdapter( 5880): Join time: 0
D/dalvikvm( 195): GC_EXTERNAL_ALLOC freed 250 objects / 13312 bytes in 88ms
I/MainActivity( 5880): mWorker finishes jobs at onDestroy().
D/CollectionsActivity( 5880): [HTCAlbum][CollectionsActivity][onDestroy]: Begin
D/AlbColAdap( 5880): [HTCAlbum][AlbumCollectionsAdapter][onDestroy]: Begin
D/AlbColAdap( 5880): [HTCAlbum][AlbumCollectionsAdapter][onDestroy]: End

Yeah someone needs to fix this?

MrDSL said:
Have you asked Calkulin yet if he would let you know what he did to fix it? I would hope the open nature of everything he would gladly help.
Click to expand...
Click to collapse
Good idea Ill shoot him a pm

Calkulins rom sends out mms uncompressed?
Tapatalk'd on Evo

brol1k said:
Calkulins rom sends out mms uncompressed?
Tapatalk'd on Evo
Click to expand...
Click to collapse
His evio rom changelog says mms compression is fixed.
Something else I noticed, if I take an 8MP shot and try to MMS it, it gets squashed down to 60k. If I take a 5MP shot and MMS it, it gets squashed to 300K. Something is clearly screwed up there. So if I send a 5MP image it comes out 5x better than an 8MP image via MMS.