[ROM] CyanogenMod - This is Bat Country! (EXPERIMENTAL) [9/18 - v4.1.11.1]

[rotonbanana]

been having trouble since the last stable build with the updater. it goes to about 6/** mb then it stops dl. this is both on edge and with wifi. est. time also stops. has the bar in the pull down but when i pull it down and click on the status bar it opens either to the download screen yet there is no yellow bar filled or the amount of mb completed and no time..or it resets the whole update program

 

[userfriendlyme]

been having trouble since the last stable build with the updater. it goes to about 6/** mb then it stops dl. this is both on edge and with wifi. est. time also stops. has the bar in the pull down but when i pull it down and click on the status bar it opens either to the download screen yet there is no yellow bar filled or the amount of mb completed and no time..or it resets the whole update program

Are you using the latest updater? have you tried uninstalling the updater and reinstalling it?

 

[tekkitan]

I want to go from 5 home screens to 3 - should this let me do this on the very latest 4.1.11.1 build? I cant seem to find it thats all...

What did you do? Quote a post from cyan from two months ago? This was taken out weeks ago, maybe even a month ago.

 

[tekkitan]

I REPEAT THERE IS NO OPTION TO CHANGE YOUR HOMESCREEN IN THIS ROM....

Sorry guys You have to try the rom that has the advanced launcher in it

They only need to install the Advanced Launcher. No need to reflash another version of the ROM.

 

[Jigga0o7]

I don't see that it's been posted just yet, so I just wanted to say that I am extremely impressed with 4.1.11.1. I have no problems to report whatsoever, and if I didn't see others having so many issues I'd say this would be a strong candidate for becoming the new stable release. Excellent work Cyan, always so quick to fix any issue.

 

[tekkitan]

I don't see that it's been posted just yet, so I just wanted to say that I am extremely impressed with 4.1.11.1. I have no problems to report whatsoever, and if I didn't see others having so many issues I'd say this would be a strong candidate for becoming the new stable release. Excellent work Cyan, always so quick to fix any issue.

I think a lot of it is the usual PEBKAC (does this work with smart phones?) problem. I am not seeing any issues and have been running 4.1.11.1 all night. Digging the speed and somehow I have 10mb of memory more free than usual according to Advanced Task Manager.

 

[userfriendlyme]

They only need to install the Advanced Launcher. No need to reflash another version of the ROM.

The advanced launcher i do not think works with 4.1.11 thats why i suggested another rom or the stable release maybe where i remember it being compatible with.

 

[Bavilo]

The advanced launcher i do not think works with 4.1.11 thats why i suggested another rom or the stable release maybe where i remember it being compatible with.

Advanced Launcher works just fine.

 

[userfriendlyme]

Advanced Launcher works just fine.

Hence why i said "I do Not think". i wasnt sure but i do no it works on his previous updates which is why i suggested. rather then him post 20 more pages on the guy who told him to update to the advanced launcher and messed up his phone lol

 

[kumar_r100]

cant sign in MSN, it said Error Unable to get phone no from your sim??

 

[elzee]

I can happily now say that 4.1.11.1 is great!

It also appears that the Black Screen Freeze issue I've been suffering through is now resolved. This was accomplished by reformatting my SD Card using adb. I followed an excellent guide at this website .. http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/

I'm now slowly loading up the G1 with Widgets and Apps to see how far I can get before FC's start appearing on a regular basis.

keruano: I thank you for your advice and kind assistance. You were right!

Cyanogen thank you again for all your great work also.

 

[himom]

Camcorder audio is working, but I need to speak directly into the mic for it to pick it up. Didn't see any other setting for it, but it's not picking up audio very well.

 

[tekkitan]

Hence why i said "I do Not think". i wasnt sure but i do no it works on his previous updates which is why i suggested. rather then him post 20 more pages on the guy who told him to update to the advanced launcher and messed up his phone lol

Yes but when you replied to him, you worded it as if you were 100% sure he'd have to goto another ROM. Nothing about "you think". Just trying to keep false info out of the thread as all we need are people reading your post and replying a week later about it.

 

[robbiekhan]

I've decided to stick to the latest v4.1.11.1 for the moment as I found the force closes to be related to my mass restoration of backed up apps - MyBackupPro and ASTRO were force closing on every 2nd app restore which was tedious as I have 48 apps

All done now though and it's fast.

VERY fast...!

Edit*
And WHOAH just how fast is the browsing scrolling now?!

 

[antonief]

So far so good, works fine for me no problems.

 

[jaaronmoody]

my music app is acting all screwy., even after a wipe. my bt audio works in a call but not music. the music widget is not loading on the home screen. when i manually open up a song in the app it plays, but no audio through bt, and the song seems to be fast forwarding through it with the counter skipping intermittently.

 

[bokkoman]

Nice work! I hope you include more dictionaries for other languages, because the word suggestion does not work for some of them. ie dutch and german, and i believe there are more that do not work.

Besides that, i'm loving this rom! I hope a stable release will come soon.

 

[2leaponover1]

This is much better than 4.10.1 I was having all sorts of problems with that. I am now at 4.11.1 and the only issue i have is the end key has stopped going to home then sleep. It's not doing anything right now. Other than that, the initial force closes but then ran fix_permissions and rebooted and everything is hunky dory now.

 

[cc6321]

thanks for your hard work cyan..

this question for anyone else since i know cyan deserves a well deserved break once again..

just wondering if theres any way to get open home working without wiping tho..

heres a logcat..

D/dalvikvm(  477): GC(0) freed 622 objects / 234288 bytes in 282ms
D/dalvikvm(  477): GC(0) freed 613 objects / 232576 bytes in 286ms
D/dalvikvm(  477): GC(0) freed 608 objects / 222656 bytes in 284ms
I/Process (  646): Sending signal. PID: 646 SIG: 9
I/ActivityManager(  132): Process com.betterandroid.openhome2 (pid 646) has died.
I/WindowManager(  132): WIN DEATH: Window{439dc0a8 com.betterandroid.openhome2/com.betterandroid.openhome2.Launcher paused=false}
I/ActivityManager(  132): Start proc com.betterandroid.openhome2 for activity com.betterandroid.openhome2/.Launcher: pid=655 uid=10092 gids={3003, 3002, 3001}
W/UsageStats(  132): Something wrong here, didn't expect com.betterandroid.openhome2 to be resumed
I/ActivityThread(  655): Publishing provider com.betterandroid.openhome.livefolder.weather: com.betterandroid.openhome2.weather.WeatherProvider
I/ActivityThread(  655): Publishing provider com.betterandroid.openhome2.settings: com.betterandroid.openhome2.LauncherProvider
D/dalvikvm(  655): GC(2) freed 2418 objects / 169856 bytes in 98ms
E/dalvikvm(  655): Could not find method android.provider.Sync$Settings$QueryMap.getListenForNetworkTickles, referenced from method com.betterandroid.openhome2.widget.SettingsAppWidgetProvider2.getBackgroundDataState
W/dalvikvm(  655): VFY: unable to resolve virtual method 458: Landroid/provider/Sync$Settings$QueryMap;.getListenForNetworkTickles ()Z
W/dalvikvm(  655): VFY:  rejecting opcode 0x6e at 0x0000
W/dalvikvm(  655): VFY:  rejected Lcom/betterandroid/openhome2/widget/SettingsAppWidgetProvider2;.getBackgroundDataState (Landroid/provider/Sync$Settings$QueryMap;)Z
W/dalvikvm(  655): Verifier rejected class Lcom/betterandroid/openhome2/widget/SettingsAppWidgetProvider2;
W/System.err(  655): java.lang.VerifyError: com.betterandroid.openhome2.widget.SettingsAppWidgetProvider2
W/System.err(  655): 	at com.betterandroid.openhome2.Launcher.reloadSkin(Launcher.java:2773)
W/System.err(  655): 	at com.betterandroid.openhome2.Launcher.onCreate2(Launcher.java:2908)
W/System.err(  655): 	at com.betterandroid.openhome2.Launcher.onCreate(Launcher.java:291)
W/System.err(  655): 	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
W/System.err(  655): 	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2364)
W/System.err(  655): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2417)
W/System.err(  655): 	at android.app.ActivityThread.access$2100(ActivityThread.java:116)
W/System.err(  655): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
W/System.err(  655): 	at android.os.Handler.dispatchMessage(Handler.java:99)
W/System.err(  655): 	at android.os.Looper.loop(Looper.java:123)
W/System.err(  655): 	at android.app.ActivityThread.main(ActivityThread.java:4203)
W/System.err(  655): 	at java.lang.reflect.Method.invokeNative(Native Method)
W/System.err(  655): 	at java.lang.reflect.Method.invoke(Method.java:521)
W/System.err(  655): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
W/System.err(  655): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
W/System.err(  655): 	at dalvik.system.NativeStart.main(Native Method)
I/NotificationService(  132): enqueueToast pkg=com.betterandroid.openhome2 callback=android.app.ITransientNotification$Stub$Proxy@43a15500 duration=1
D/AndroidRuntime(  655): Shutting down VM
W/dalvikvm(  655): threadid=3: thread exiting with uncaught exception (group=0x4001e210)
E/AndroidRuntime(  655): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime(  655): java.lang.RuntimeException: Unable to resume activity {com.betterandroid.openhome2/com.betterandroid.openhome2.Launcher}: java.lang.NullPointerException
E/AndroidRuntime(  655): 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2851)
E/AndroidRuntime(  655): 	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2866)
E/AndroidRuntime(  655): 	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2420)
E/AndroidRuntime(  655): 	at android.app.ActivityThread.access$2100(ActivityThread.java:116)
E/AndroidRuntime(  655): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1794)
E/AndroidRuntime(  655): 	at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(  655): 	at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(  655): 	at android.app.ActivityThread.main(ActivityThread.java:4203)
E/AndroidRuntime(  655): 	at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(  655): 	at java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime(  655): 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime(  655): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:549)
E/AndroidRuntime(  655): 	at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(  655): Caused by: java.lang.NullPointerException
E/AndroidRuntime(  655): 	at com.betterandroid.openhome2.Launcher.onResume(Launcher.java:3046)
E/AndroidRuntime(  655): 	at android.app.Instrumentation.callActivityOnResume(Instrumentation.java:1225)
E/AndroidRuntime(  655): 	at android.app.Activity.performResume(Activity.java:3559)
E/AndroidRuntime(  655): 	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2838)
E/AndroidRuntime(  655): 	... 12 more
I/Process (  132): Sending signal. PID: 655 SIG: 3
I/dalvikvm(  655): threadid=7: reacting to signal 3
I/dalvikvm(  655): Wrote stack trace to '/data/anr/traces.txt'
D/dalvikvm(  477): GC(0) freed 4565 objects / 620528 bytes in 337ms
D/dalvikvm(  477): GC(0) freed 8359 objects / 692440 bytes in 340ms
D/dalvikvm(  477): GC(0) freed 4641 objects / 399616 bytes in 134ms
D/dalvikvm(  477): GC(0) freed 1767 objects / 203584 bytes in 314ms
D/dalvikvm(  477): GC(0) freed 379 objects / 138744 bytes in 302ms
D/dalvikvm(  477): GC(0) freed 336 objects / 186896 bytes in 125ms
D/dalvikvm(  477): GC(0) freed 282 objects / 53072 bytes in 113ms
D/dalvikvm(  477): GC(0) freed 260 objects / 8744 bytes in 120ms
D/dalvikvm(  477): GC(0) freed 1457 objects / 96216 bytes in 323ms
D/dalvikvm(  477): GC(0) freed 129 objects / 46416 bytes in 306ms
D/dalvikvm(  477): GC(0) freed 922 objects / 72488 bytes in 324ms
D/dalvikvm(  477): GC(0) freed 3488 objects / 162624 bytes in 323ms
D/dalvikvm(  477): GC(0) freed 445 objects / 57400 bytes in 314ms
D/dalvikvm(  477): GC(0) freed 131 objects / 47280 bytes in 304ms
D/dalvikvm(  477): GC(0) freed 267 objects / 51760 bytes in 304ms
W/ActivityManager(  132): Activity idle timeout for HistoryRecord{43ab7b20 com.betterandroid.openhome2/.Launcher}
D/dalvikvm(  477): GC(0) freed 152 objects / 47888 bytes in 293ms
D/dalvikvm(  477): GC(0) freed 286 objects / 51960 bytes in 314ms
D/dalvikvm(  477): GC(0) freed 276 objects / 51456 bytes in 304ms
D/dalvikvm(  477): GC(0) freed 130 objects / 46888 bytes in 305ms

Same for me. Has anyone else figured out how to get rid of this error and get Open Home to start? Thanks. For me, the stack trace also has:

<code>
E/dalvikvm( 9162): Could not find method android.provider.Sync$Settings$QueryMap
.getListenForNetworkTickles, referenced from method com.betterandroid.openhome2.
widget.SettingsAppWidgetProvider2.getBackgroundDataState
E/AndroidRuntime( 9162): Uncaught handler: thread main exiting due to uncaught e
xception
</code>

 

[gadiator]

I got still a FC when i want to change Camera Settings