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] (8/12) CM6 Experiment Nightly Build Checker

I made this app that checks for the latest nightlies. It is for all of us who are obsessed with constantly checking for nightlies. So far it only checks for Nexus One nightlies. It is the first app I have ever made so it will probably force close. Sorry!
I'm not responsible for anything that this does to your device. It works fine for my nexus one.
Test it out and let me know!
Known Bugs: when u first start it, it notifies you of a new build, this will be fixed in the next release.
Can't cancel download
Doesn't auto-select link for all phones. PM me if it's not selecting for your phone. (it defaults to nexus one if it can't set it)
Alpha 5 adds boatloads of features. Auto Download doesn't work yet, its just there to taunt you in the settings. Time Zone display should work correctly. Copy MD5 to clipboard button. Less force closes.
CM Forum Link
Let me know if the notifications work. I didn't really have time to test them as I only get one shot every time a new build is released.
Also please tell me how battery life is with and without auto refresh on.
If anybody knows how to programatically reboot into recovery please PM me!
Release Notes:
Alpha 5 is completely rewritten to add NOTIFICATIONS (maybe, im not sure if they actually work), less force closes, fixed time zone, md5 to clipboard, progress bar, automatically sets directory for more phones
Alpha 4 selects which build to download based on your phone model and lets you choose download method (browser or sd card)
Alpha 3 displays the nightlies in your time zone (let me know if this works right)
Alpha 2 adds a toast and reverses the order so the latest nightly appears at the top
Alpha 1 initial release

Just what I wanted. Thank you so much.

thanks, once you get notifications working, this will be epic. but i think it will be quite difficult without getting cooperation from the hosting provider.

Nice, going to check this one out! Thanks!

rom manager does this

^only works if you're using clockmod recovery, im not
thanx op

hey the time zone for california is off by an hour (early), maybe it doesn't take into consideration daylight savings?? Anyways I would prefer it stayed in gmt. thanks for this

ogdobber said:
hey the time zone for california is off by an hour (early), maybe it doesn't take into consideration daylight savings?? Anyways I would prefer it stayed in gmt. thanks for this
Click to expand...
Click to collapse
Exactly what I was about to post!
Thanks DEV!

Any chance of adding some kind of an easy way to know the last rom I downloaded? I know I can use a file manager to check but I'll admit I'm lazy and i think that it would be very useful

e4604 said:
^only works if you're using clockmod recovery, im not
thanx op
Click to expand...
Click to collapse
Too bad for me.
Dev, can you use CMupdater?

FC on EVO. Latest Nightly.

mattrb said:
FC on EVO. Latest Nightly.
Click to expand...
Click to collapse
sorry, i made a silly mistake in the code. this doesn't work on anything but nexus one for now.
anyways, im completely reworking this app now that i know what im doing to add all the requested features and make it faster and more responsive.

I wanted to report a UI bug. When you select one of the nightly builds from the list and then select another rom, the second rom details are the same as the first one selected.
It looks like the popup values are only set on the first selection.

new update! let me know how it goes

Crashes every time I try to set update frequency to once a day.
Code:
W/System.err( 3722): at com.nelson.GetNightly.GetNightly.onResume(GetNightly.java:143)
W/System.err( 3722): at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1149)
W/System.err( 3722): at android.app.Activity.performResume(Activity.java:3823)
W/System.err( 3722): at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3118)
W/System.err( 3722): at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3143)
W/System.err( 3722): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2059)
W/System.err( 3722): at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err( 3722): at android.os.Looper.loop(Looper.java:123)
W/System.err( 3722): at android.app.ActivityThread.main(ActivityThread.java:4627)
W/System.err( 3722): at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err( 3722): at java.lang.reflect.Method.invoke(Method.java:521)
W/System.err( 3722): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
W/System.err( 3722): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
W/System.err( 3722): at dalvik.system.NativeStart.main(Native Method)
I/ASK ( 2111): onUnbindInput
D/LocationMasfClient( 2033): getNetworkLocation(): Returning cache location with accuracy 1425.0
D/dalvikvm( 2497): GC_FOR_MALLOC freed 5138 objects / 500376 bytes in 51ms
W/Resources( 3722): Converting to string: TypedValue{t=0x10/d=0x3c a=-1}
D/dalvikvm( 3722): GC_FOR_MALLOC freed 8026 objects / 416352 bytes in 36ms
D/dalvikvm( 2111): GC_EXPLICIT freed 40 objects / 1416 bytes in 51ms
I/ActivityManager( 2033): Displayed activity com.nelson.GetNightly/.Preferences: 386 ms (total 386 ms)
I/dalvikvm( 3722): Jit: resizing JitTable from 4096 to 8192
D/AndroidRuntime( 3722): Shutting down VM
W/dalvikvm( 3722): threadid=1: thread exiting with uncaught exception (group=0x4001d7e8)
I/Process ( 3722): Sending signal. PID: 3722 SIG: 9
I/ASK ( 2111): onUnbindInput
D/dalvikvm( 2033): GC_EXTERNAL_ALLOC freed 5065 objects / 238576 bytes in 90ms
D/dalvikvm( 2033): GC_EXTERNAL_ALLOC freed 2149 objects / 94952 bytes in 78ms
D/dalvikvm( 2033): GC_EXTERNAL_ALLOC freed 161 objects / 6464 bytes in 79ms

if i enable auto refresh, do i still need to set refresh frequency? or does it mean that if auto refresh is on, it will automatically refresh based on your frequency?

Karolis said:
Crashes every time I try to set update frequency to once a day.
Click to expand...
Click to collapse
looks like i skipped over the value for 6 hours. so if you set it to 12 hours, it should refresh every 24 hours. this will be fixed in the next release
NguyenHuu said:
if i enable auto refresh, do i still need to set refresh frequency? or does it mean that if auto refresh is on, it will automatically refresh based on your frequency?
Click to expand...
Click to collapse
if you enable auto-refresh it will automatically refresh based on your frequency. i'll try to make this more clear in the next release.

nellyspageli said:
looks like i skipped over the value for 6 hours. so if you set it to 12 hours, it should refresh every 24 hours. this will be fixed in the next release
if you enable auto-refresh it will automatically refresh based on your frequency. i'll try to make this more clear in the next release.
Click to expand...
Click to collapse
notifications seem to work if app is running. maybe next step is to allow for sound? i also noticed that, if the app isnt running in background it wont notify. when i rebooted my phone, the app doesnt auto load so i did not get any notifications. i saw in the forums that new nightly is up, so i loaded up the app and then it finally notify me.
maybe add an option to have it load on boot

Not working anymore! They changed the site!

djdarkknight96 said:
Not working anymore! They changed the site!
Click to expand...
Click to collapse
Not only did they change the site but they changed from build dates to build numbers.

[Q] App development: strange problems on Froyo

I have recently released my first app (a soundboard) and am now receiving complaints from Froyo users that while the app appears compatible, it does not work properly. The MinSDK version in my manifest is 8, but the build target is 15.
My app starts with a splash screen, then there is a main menu, which then starts the main activity, where there are 7 tabs. Each tab holds about 20 sounds, consisting of a textview and 4 imagebuttons. Together with Ad banners, this comes up to about 500 views in one activity. Eclipse warned me that more than 80 views might be bad for performance, but even low grade phones like the Samsung Galaxy Y are able to run the app effortlessly.
The min SDK I set for my app is level 8, Froyo and now after I got negative feedback and tested it, I found out, on Froyo the activity does not start.
Is there a fixed limit of 80 views per activity for Android 2.2? I could not find information on that anywhere.
This is the error I see in the Developer Console constantly:
Code:
java.lang.VerifyError: com.cheftony.psychsoundfree.Nicknames
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1429)
at android.app.Instrumentation.newActivity(Instrumentation.java:1021)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2577)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2679)
at android.app.ActivityThread.access$2300(ActivityThread.java:125)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2033)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:123)
at android.app.ActivityThread.main(ActivityThread.java:4627)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:521)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:902)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:660)
at dalvik.system.NativeStart.main(Native Method)
What should I do? I was thinking about modifying the main menu to start different activities based on the android version of the device, i.e. starting my regular old activity on any phone with Gingerbread or higher and creating a new one, where the interface is split up into several activities so there are not too many views per activity, which is a lot of work and basically would split up the app and double the work that goes into updating it.
Or should I just exclude Froyo devices? How important is it to still support Froyo today?
Are these few people left with old OS versions worth more than 50% of the work I'd have to put into my up for future updates?

[solved] can sombody brings the Gallery2.apk to work without gfx acceleration?

[Short story]
Is there somebody, who has time and inclination to modify the AOSP Gallery2(.apk) app to get that to work on Android versions without graphics acceleration features?
[Long version]
I'm using the latest Replicant ROM. This is shipped with the legacy /system/app/Gallery.apk which has serious problems to show previews of images, and some image contents at all...
Replicant comes without OpenGL ES. So that's the case why the Gallery2.apk (which heavily relies on graphics acceleration features) crashes when I try to start that app with the following traces:
Code:
I/ActivityManager(2868): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.gallery3d/.app.GalleryActivity} from pid 3196
I/ActivityManager(2868): Start proc com.android.gallery3d for activity com.android.gallery3d/.app.GalleryActivity: pid=25408 uid=10066 gids={50066, 1006, 3003, 1015, 1028}
W/Trace (25408): error opening trace file: No such file or directory (2)
V/StateManager(25408): startState class com.android.gallery3d.app.AlbumSetPage
D/libEGL (25408): loaded /system/lib/egl/libGLES_android.so
W/dalvikvm(25408): threadid=12: thread exiting with uncaught exception (group=0x40cfc930)
E/AndroidRuntime(25408): FATAL EXCEPTION: GLThread 503
E/AndroidRuntime(25408): java.lang.IllegalArgumentException: No configs match configSpec
E/AndroidRuntime(25408): at android.opengl.GLSurfaceView$BaseConfigChooser.chooseConfig(GLSurfaceView.java:865)
E/AndroidRuntime(25408): at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:1026)
E/AndroidRuntime(25408): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1403)
E/AndroidRuntime(25408): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1242)
W/ActivityManager(2868): Force finishing activity com.android.gallery3d/.app.GalleryActivity
I've sent an email to a Replicant developer before, with the question, why Replicant doesn't use Gallery2? The answer was:
"On Replicant, it is too slow to be usable, has parts missing and many bugs because of the incomplete software-only graphics stack implementation we use".
I've temporary tested to add the proprietary OpenGL ES bits (on my Samsung Galaxy S2 [i9100]):
/system/lib/libMali.so
/system/lib/libUMP.so
/system/lib/egl/egl.cfg
/system/lib/egl/libEGL_mali.so
/system/lib/egl/libGLES_android.so
/system/lib/egl/libGLESv1_CM_mali.so
/system/lib/egl/libGLESv2_mali.so
/system/lib/hw/gralloc.exynos4.so
which enables graphics acceleration, and made the Gallery2.apk work. But I deleted them again, because I don't want to use that non free bits. So that's the reason why I'm using Replicant...
I also haven't found any open source alternatives for the Gallery2 app.
Tips are very welcome, too!
(I just asked the developer of
QuickPic: https://play.google.com/store/apps/details?id=com.alensw.PicFolder
if he doesn't want to release his app as open source in the future, but sadly he declined).
Now I'm searching for somebody, which could modify the Gallery2 sources:
https://android.googlesource.com/platform/packages/apps/Gallery2/
to get a patched version of the app to work on BLOB less Android versions.
I don't know the best practice way to find someone for that job. If somebody would give it a try, but don't wants to do that for free, you could leave a donation information and I would try to animate people to make a donation for you, (of course including myself).
Thanks for any answers, hints or any further help.

[reward] I want YOU
Nobody?
Pretty please with sugar on top :fingers-crossed:

Time is a healer...
A working app, which is exactly what I was searching for has landed to the F-Droid store, called
LeafPic: https://f-droid.org/repository/browse/?fdid=com.horaapps.leafpic
(So this thread could be closed)