yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] timal:
Upper right hand corner it spins (ha) when you are waiting on the phone.

Like the old hour glass on computers.
[G1 Android Development] pistol4413:
They r the little yellow things that come up when something is loading. Like the market or a browser page. Well after about a half hour it seems the default cpu scalling cyan has in here is best. I ran at 528 min and max and it seemed slower than the default scalling to me. Comeone else should try to confim this
[G1 Android Development] badfaz:
Seems like none of the widgets work at all on the 4.1.5...or is it just on mine?
[G1 Android Development] cyanogen:
Can you put this on the issue tracker please? There are a bunch of NPEs in the new ActivityManager that I've been picking thru.

There is an API for gestures that developers can use, but it was removed from the launcher and apps. We could probably pull some of it back, but I don't know how stable it is.
[G1 Android Development] circa85:
I know I could do that, but that would be stepping backwards since 4.0 was based off of 3.9.10 and lacks the global search. also, Cyanogen had mentioned that he would be merging it back in sometime soon
[G1 Android Development] timal:
My bluetooth and gps widgets are working. The gps one gave a wait to force close message once.
[G1 Android Development] igashu:
Digital zoom is not zoom, you can often get better results just enlarging and cropping in Photoshop :)

I for one actually think there are benefits to sticking with the AOSP versions of camera/gallery.
[G1 Android Development] pistol4413:
my widgets work fine. this is looking better by the minute i might just make the switch now. there i a little lag switching from app to app. i know others have noticed. overall this isnt bad at all
[G1 Android Development] jovan285:
wrong post
[G1 Android Development] darthlukan:
Installed from clean wipe (as always with experimental) it was zooming. Now I have clocks maxed with setcpu and my userinit (no cc or backing just straight linux swap) and this sucker is flying! Hats off to you my friend.

In case anyone else missed it from my last post, I'm using 32MB of swap in my userinit.sh file and clocking for speed. Setcpu benched my phone with internal and sd memory widgets running at 545ms tapped out. Thanks again cyanogen!
[G1 Android Development] Smokuevo:
same on my end on MT3G. got no problems running 4.0.4 on it other then some crashes.

G1 on the other hand runs beautifuly.. wish i could run 4.1.5 on the mytouch though with widgets and no issues like i have

also a side note.. i performed a wipe on the MT3G and nothing solves the issues with the widgets.( Problem Loading Widget )
[G1 Android Development] cyanogen:
I haven't had much time to test on the Magic. My wife has been on a crazy work schedule lately so I haven't seen her or her myTouch. Will try and do some testing this week.
[G1 Android Development] pistol4413:
as great as this rom i cyan im going back to stable. just for a big longer as the experiment roms progress. thanx man ur the best
[G1 Android Development] Afirejar:
Just wiped and flashed. German localization has improved as far as I can see. The initial setup wasn't German last time, and the annoying 'h' after the time display is gone. The menu for repeating alarms in the alarm clock still shows numbers instead of weekdays and I still can't set the calendar to start weeks on Mondays.

I had issues entering my Google account data and syncing over gprs (network coverage sucks in my area). I could solve this by deleting the MMS apn. I will try reentering the second apn and see what happens, after I reinstalled all the apps. If the problem persists I'll try to pull a log to see what happens.

The phone seems incredibly slow at the moment. I'll wait some time and see, if this improves.

Also, just before wiping I downloaded aTrackDog to export a list of installed apps. When I was back at the home screen after flashing and the initial setup, the first thing that happend was aTrackDog downloading itself. Is that expected?
[G1 Android Development] timal:
I am running it on the ion (magic/mytouch) works great.
[G1 Android Development] DAKIDD236:
i still can't open protected apps, i get "The application XXX (process.com.xxx.) has stopped unexpectedly.. Please try again."

anyone have a fix for this?.. it's really annoying.. I wiped 2 times, I deleted and reinstalled and I keep getting that message.
[G1 Android Development] cyanogen:
Picking stuff here and there from the Donut drop for 3.9.1. Lots of new stuff in the Dalvik VM, I ported the power widget, some other things here and there..
[G1 Android Development] k0nzious:
when shall it be here?

oh great bringer of donuts.
[G1 Android Development] PaPer android:
Dont be greedy, your Donut crumbs will come when he is ready
[G1 Android Development] k0nzious:
i'll wait.
[G1 Android Development] yomamaster:
Home screen redraw

Strange. I noticed the complete opposite. I jacked it back up to 5 home screens and the redraw on the home screen seems to be significantly slower than before. This is using 3.9 with a 32 mb swapfile. I haven't played around with compcache in 3.9, but in previous versions, it didn't seem to make a whole lot of difference.
[G1 Android Development] PaPer android:
I was just givin ya a hard time, im gonna be staying up late tonight just incase anything goes down.......
[G1 Android Development] cyanogen:
For anyone following me on Github, I killed the Dalvik fork because I'm just using the full Donut branch now.
[G1 Android Development] G1-evolve:
You been saying an update for the passed couple days! :p
[G1 Android Development] Glen L:
anyone got market downloading working?

I already edited the build.prop but still no market downloads
[G1 Android Development] shotad:
i can't wait till 3.9.1 with the cool donut widget!
[G1 Android Development] zimphishmonger:
Cyan, Are you recommending we not use compcache for the time being? I remember you mentioning that the G1 hardware is up to snuff for swap and compcache?
[G1 Android Development] shotad:
didn't he say to set the compcache to 0? i did that and it runs fine for me..

echo 0 > /proc/sys/vm/page-cluster;

:)
[G1 Android Development] zimphishmonger:
Thanks! I'll give that a shot and see how it works out. I'm currently using 16000 size and 15 swappiness, hopefully it wont fill up too quickly.
[G1 Android Development] paulskerr:
experimental

dude this is the sweetest rom yet, extremely nice work. Hats of to you.
[G1 Android Development] Glen L:
anyone get their market working?
[G1 Android Development] mdavidf:
Sorry, but you're making sound as if everyone's Market wasn't/isn't working. Mine has been working fine since I flashed 3.9.

I did a complete wipe (including SD Card) when I installed 3.9.
[G1 Android Development] mrnote8:
i've had absolutely no probs with the market
[G1 Android Development] uwonsum:
I tested the following settings in userinit.sh with compcache and the performance was quite good:

#!/system/bin/sh

insmod /system/modules/lib/modules/2.6.29-cm/compcache/xvmalloc.ko;
insmod /system/modules/lib/modules/2.6.29-cm/compcache/ramzswap.ko disksize_kb=32768;
mknod /dev/ramzswap0 b 253 0;
echo 16 > /proc/sys/vm/swappiness;

## Experimental settings
echo 1 > /proc/sys/vm/page-cluster;
echo 3 > /proc/sys/vm/laptop_mode;
echo 5000 > /proc/sys/vm/dirty_expire_centisecs;
echo 800 > /proc/sys/vm/dirty_writeback_centisecs;
echo 10 > /proc/sys/vm/dirty_background_ratio;
echo 16 > /proc/sys/vm/dirty_ratio;
##
swapon /dev/ramzswap0;
exit;

If you are wondering why swappiness is set so low compared to what most people are using, larger swappiness means more CPU is used--you don't want that. These may not be the optimal configurations, but I can guarantee the default kernel settings is not the best for this device since it was not designed to take advantage of swap. You can test these settings and see how it works for you.
[G1 Android Development] Glen L:
hmm that's odd, i did a complete wipe as well. anyways, I just did another wipe and flashed. market's now working again
[G1 Android Development] pinaytoy93:
soooooooooooo is anyone elses gmail sync not working? any tips? i disabled and enabled gmail sync and no luck. i cant even send emails from my phone. help please? thanks in advance.
[G1 Android Development] pistol4413:
how wat about going into the recovery repairing filesystems then in the console running

fix_permissions
[G1 Android Development] angelghost:
great job ，thank you ,but my messeging and phone is still slow,why?

no wipe ,can wipe help???
[G1 Android Development] pistol4413:
post a log so that can be answered better
[G1 Android Development] elzee:
This was the condition I had on 4.1.4. Grab a copy of the latest fix_permissions.sh script and run it in the terminal.

Reboot and you should have widgets again. Some of my widgets are missing .. but I put that down to the fact that they are not 1.6 compatible. Neither was dxTop but they have since put out an upgrade which now works on 1.5 upwards. This also may explain why my widgets are now running too.

HTH!
[G1 Android Development] DAKIDD236:
i did that already, i still get the fc's:confused:
[G1 Android Development] Afirejar:
Calendar widget only displays "error loading widget".

I/ActivityManager( 153): Starting activity: Intent { act=android.appwidget.acti
on.APPWIDGET_PICK cmp=com.android.settings/.AppWidgetPickActivity (has extras) }

W/InputManagerService( 153): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Proxy@437cbd60
I/ActivityManager( 153): Displayed activity com.android.settings/.AppWidgetPick
Activity: 2526 ms (total 2526 ms)
D/Launcher( 298): dumping extras content=Bundle[{appWidgetId=6}]
W/ResourceType( 153): No package identifier when getting value for resource num
ber 0x7f060001
W/InputManagerService( 153): Window already focused, ignoring focus gain of: co
m.android.internal.view.IInputMethodClient$Stub$Proxy@439969c0
D/Searchables( 153): Checking component ComponentInfo{com.google.android.provid
ers.enhancedgooglesearch/com.google.android.providers.enhancedgooglesearch.Launc
her}
D/HomeLoaders( 298): application intent received: android.intent.action.PACKAGE
_CHANGED, replacing=false
D/HomeLoaders( 298): --> package:com.android.providers.calendar
D/HomeLoaders( 298): --> sync package com.android.providers.calendar
I/ActivityManager( 153): Start proc com.android.voicedialer for broadcast com.a
ndroid.voicedialer/.VoiceDialerReceiver: pid=1892 uid=10005 gids={3002}
D/VoiceDialerReceiver( 1892): onReceive Intent { act=android.intent.action.PACKA
GE_CHANGED dat=package:com.android.providers.calendar flg=0x20000000 cmp=com.and
roid.voicedialer/.VoiceDialerReceiver (has extras) }
D/RecognizerEngine( 1892): deleteCachedGrammarFiles /data/data/com.android.voice
dialer/files/openentries.txt
I/ActivityManager( 153): Process com.android.voicedialer (pid 1892) has died.
I/ActivityManager( 153): Stopping service: com.android.providers.calendar/.Cale
ndarAppWidgetService

Also Weather Widget Donate has some issues. Trying to put a weather widget onto a full homescreen shows the expected error message (not enough room), but also brings up the configuration window for the (non-existant) widget. Successfully placing the widget has it stuck at "loading data..."

Edit: Well, rebooting has fixed both these problems. The weather widget loaded its data and the calendar is showing where I tried to place it before the reboot.
[G1 Android Development] ninjavampire:
correct version

I don't know if this is just wear and tear on my phone but my home button doesn't seem to work after flashing to 4.1.5. Is anyone else having this issue or is it just my phone?
[G1 Android Development] cyanogen:
Are you on a Dream or Magic? I'm worried that the sensors driver for sapphire isn't working so well. I don't have the updated version for Donut so it's using the trout version.
[G1 Android Development] rikupw:
recently downloaded apps before wipe, redownloading after wipe

as a matter of fact, I have had that same experience every since jesusfrekes roms, so I'm guessing it has something to do with the google checkin service, don't fret, just one less thing for you to install :P haha, if you use it *shrugs*
[G1 Android Development] fahadayaz:
ME TOO!!

am using a g1 (dream)

any fixes cyan?
[G1 Android Development] guitarfreak846:
I have a G1 and I reformatted my ext2/3 partition (I was on Madaco HERO), wiped, then flashed and the home button works fine.
[G1 Android Development] clefky10:
Messaging is extremely slow and various applications force close, but other than that all good.
[G1 Android Development] bootleg16:
i think i will wait for a stable release.

paid apps force close.

home button doesnt work

messsaging is really sluggish
[G1 Android Development] fahadayaz:
i wanted to know how to solve this without wiping. its happened to me before when flashing a higher rom, but i didnt care for wiping then so i just did it. i want to find out what might be the cause though and how to fix it. interestingly, wiping and then using my backup to restore application data keeps the problem. even if i flash to an earlier rom, the problem still persists.
[G1 Android Development] kerauno:
Works perfectly on my "G1" (Dream)
[G1 Android Development] kerauno:
Did you do a wipe and then install ROM?

I experienced same problems when i first installed 4.1.x and worked great after I wiped and reinstalled the ROM.
[G1 Android Development] t1h5ta3:
http://www.infoworld.com/d/developer-world/google-unwraps-apps-partner-program-522

google search is your friend...;)
[G1 Android Development] liquidchen:
sorry, double post, please delete it...
[G1 Android Development] almus:
have 4.1.5 installed.

After updating I was having a problem with the call button (the green button) it was still active but was no longer mapped to anything (pressing it from the home screen did nothing and pressing it twice would not cause a redial), I did a hard reset and things look good but, since I am using the built in apps2cd a hard reset does not remove all of my applications. Is there some way to actually reset (remove all apps, settings, everything) while apps2cd is working?
[G1 Android Development] Charrion:
BFS?

From one of Cyan's recent tweets:

Silly question I'm sure, but what is BFS? Just curious.
[G1 Android Development] fahadayaz:
erm, BtrFS?
[G1 Android Development] alapapa:
i use BFS to mean breadth-first search (as opposed to depth first).

could it be that?
[G1 Android Development] fahadayaz:
lol seems more likely that my idea, seeing that donut has global search :p
[G1 Android Development] alapapa:
lol Brain Fsck Scheduler

http://ck.kolivas.org/patches/bfs/bfs-faq.txt

interesting
[G1 Android Development] 3Shirts:
BFS is designed for exactly this kind of small computer application. Should work very nicely in theory and, from the sounds of cyanogens tweets, in practice!
[G1 Android Development] S3bast1an:
Please wait, and NEVER expect an experimental to run like a stable.

:eek:

S.
[G1 Android Development] velazcod:
AWESOME!

btw just sent beer money!!!
[G1 Android Development] snyper2k2:
I adjusted to 96mb linux swap on this ron, with 60 swappiness and its probably the fastest most speedy rom I ever ran :-)...Its been running for hours now, and i have been playing with the phone and surfing all day. Mucho fast.

Buying you beer when this one goes stable.
[G1 Android Development] blueheeler:
I really do like the new camera.

However, having a new child, we take a lot of indoor pics.

That said, the HTC camera has badly needed brightness controls.

If Cyanogen decides to keep the current camera, I can switch to SnapPhoto Pro if I have to, no big deal. If we have a vote, I sure would like to see the HTC camera return.

If y'all don't mind me asking:

Can we just push the HTC Camera from a previous build? Is the framework already there, or would it require a lot of trial and error on my end?

Thanks.
[G1 Android Development] ThR1LL:
I just reinstalled Handcent since 4.1.4 didn't really like it and now I seem to always get a FC when I try to edit the vibrate pattern in notifications. I haven't tested it out with receiving messages and using the popup since that was the reason I uninstalled but I attached my log for the vibrate patter FC.
[G1 Android Development] blueheeler:
A note to users of programs such as Backup For Root Users or MyBackup or smaller b/r programs such as Bookmarks Backup & Restore:

Use the phone's program BEFORE restoring any data!

For example: BEFORE you restore your bookmarks (using any of the backup/restore programs), start your Browser first ... then you can restore your bookmarks.

I'm not sure if that pertains to everything else, but I do know that if you restore your bookmarks before running the browser, Browser seems to crash and throw up FCs that even reboots don't solve. It took re-flashing 3 times to figure that one out (yep, I'm kinda slow).

Just a tip.
[G1 Android Development] nk111:
global search still not working

I still have this issue in 4.1.5 :(

I wonder why this only seems to affect some (german? not english?) users?

As you can see in the logcat from the linked post above the search is executed with an url like this:

http://www.google.com/complete/search?hl=en&gl=de&client=ms-android-tmobile-de&source=android-browser-type&q=test

which is actually the suggest url, not the search url...
[G1 Android Development] Lelongue:
Second this issue, I'm on a Dutch G1...
[G1 Android Development] amarkow2:
browser and global search still not working...restarted and what not....i did a nandroid backup but it errors out why i try to restore...how do i go back?
[G1 Android Development] godfather123189:
camera/camcorder

hey buddy not to be much of a bother

but i was wondering if it would be possible for you to port the old camera/camcorder from like 4.04 to the new builds of android 1.6

thanks in advance,

Ray
[G1 Android Development] traspler:
How about including the nano editor from farmatito (http://xdaforums.com/showthread.php?t=556944)? That be great :)
[G1 Android Development] yukkio:
Hi, I've installed 4.1.5 in my magic. I've a problem with acore proccess. For example: If I run Astro in landscape mode and I back to home (pressing home button) I get acore error:

D/AndroidRuntime(27368): Shutting down VM
W/dalvikvm(27368): threadid=3: thread exiting with uncaught exception (group=0x4
001e210)
E/AndroidRuntime(27368): Uncaught handler: thread main exiting due to uncaught e
xception
E/AndroidRuntime(27368): java.lang.ClassCastException: android.view.AbsSavedStat
e$1
E/AndroidRuntime(27368): at com.android.launcher.Workspace.onRestoreInsta
nceState(Workspace.java:903)
E/AndroidRuntime(27368): at android.view.View.dispatchRestoreInstanceStat
e(View.java:5689)
E/AndroidRuntime(27368): at android.view.ViewGroup.dispatchRestoreInstanc
eState(ViewGroup.java:1121)
E/AndroidRuntime(27368): at android.view.ViewGroup.dispatchRestoreInstanc
eState(ViewGroup.java:1125)
E/AndroidRuntime(27368): at android.view.ViewGroup.dispatchRestoreInstanc
eState(ViewGroup.java:1125)
E/AndroidRuntime(27368): at android.view.View.restoreHierarchyState(View.
java:5668)
E/AndroidRuntime(27368): at com.android.internal.policy.impl.PhoneWindow.
restoreHierarchyState(PhoneWindow.java:1506)
E/AndroidRuntime(27368): at android.app.Activity.onRestoreInstanceState(A
ctivity.java:833)
E/AndroidRuntime(27368): at com.android.launcher.Launcher.finishBindDeskt
opItems(Launcher.java:1508)
E/AndroidRuntime(27368): at com.android.launcher.Launcher.bindItems(Launc
her.java:1472)
E/AndroidRuntime(27368): at com.android.launcher.Launcher.access$2400(Lau
ncher.java:90)
E/AndroidRuntime(27368): at com.android.launcher.Launcher$DesktopBinder.h
andleMessage(Launcher.java:2225)
E/AndroidRuntime(27368): at android.os.Handler.dispatchMessage(Handler.ja
va:99)
E/AndroidRuntime(27368): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime(27368): at android.app.ActivityThread.main(ActivityThrea
d.java:4203)
E/AndroidRuntime(27368): at java.lang.reflect.Method.invokeNative(Native
Method)
E/AndroidRuntime(27368): at java.lang.reflect.Method.invoke(Method.java:5
21)
E/AndroidRuntime(27368): at com.android.internal.os.ZygoteInit$MethodAndA
rgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime(27368): at com.android.internal.os.ZygoteInit.main(Zygot
eInit.java:549)
E/AndroidRuntime(27368): at dalvik.system.NativeStart.main(Native Method)

I/Process ( 132): Sending signal. PID: 27368 SIG: 3
I/dalvikvm(27368): threadid=7: reacting to signal 3
I/dalvikvm(27368): Wrote stack trace to '/data/anr/traces.txt'
I/DumpStateReceiver( 132): Added state dump to 1 crashes
W/ActivityManager( 132): Launch timeout has expired, giving up wake lock!

This problem always is when I install a ROM with " global search".

Also I've seen it takes just a little bit more when you open a program.

Thank you.

BR.
[G1 Android Development] CableBurner:
the new rom is great!

but the call end issue has still exists:

the problem is, that the end-button doesnt work until the call in screen is shown and the phone of my call-partner rings...

its quite annoying if you call somebody by mistake (sausage-like-fingers) and arent able to interrupt dialing

i also posted this on in the bug-tracker, issue 259
[G1 Android Development] bhilgeman:
Pull the system.img, data.img, and boot.img files off your nandroid backup and use fastboot to restore your phone...

1) put those 3 files in a folder on your pc

2) in cmd promt cd that folder

3) on phone hold camera while powering on phone

4) plug phone into pc w/ usb

5) press back button

6) screen should say fastboot usb now

7) at cmd promts type: fastboot flash system system.img [press enter]

8) type: fastboot flash userdata data.img [press enter]

9) type: fastboot flash boot boot.img

10) type fastboot reboot
[G1 Android Development] ninjavampire:
home button

i am using a dream, i flashed back to your stable rom 4.0.4 and it still doesn't work, so i must assume that this is just due to wear and tear on my phone.

the only think that made me think it was maybe something in the new experimental version was that when i press the home button the keys light up and the screen will unlock or turn on. The home button is picking up that i am hitting it but it is just not doing the home button function.

if you think this could be an issue with the rom please let me know, but im pretty sure now that i have flashed back to 4.0.4 and it still doesn't work that it is just wear and tear on my phone.
[G1 Android Development] cyanogen:
I solved the performance issues, will do a release after work tonight. Good stuff, it's not only fast, it's faster than pretty much any ROM I've released :)
[G1 Android Development] cyanogen:
Yeah, the drivers that control the keypad and other things are different in Donut, that's why I asked. But if it still happens on 4.0.4 then you probably have a hardware issue. I'd backup and wipe to be sure though.
[G1 Android Development] Afirejar:
Following up on my original issues: The second APN works now, seems it was a temporary problem, perhaps I just had poor reception.

Phone still doesn't feel really fast, but it got better. Maybe it's just me, but app startup time feels slower compared to the latest stable build.
[G1 Android Development] nurre:
Sounds really good! I'll jump on the 4.1 bandwagon after tonight, saw your BFS notes on twitter and I've been wanting to see what BFS could do for android so I can't wait any longer ;)
[G1 Android Development] kevo:
I've not noticed any performance issues with 4.1.5 so far

It seems quicker for me than your roms have been for a good few versions now. I'm still getting by without wiping. One of the early 3.X's was the last time I wiped iirc.

Particularly the browser in 4.1.5 seems faster than its ever been for me.

Cheers cyan
[G1 Android Development] dreamhunterr:
Awesome; like others have said, I only find it sluggish when opening new applications, the rest does feel like a breeze already

Keep up the good work!
[G1 Android Development] mattg:
I had exactly the same problem on my magic and flashing back to 4.0.4 didn't fix. Wiping and reflashing did the trick though. I also found that before wiping I couldn't get the phone to lock even with the options set in the security menu.