yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] xKLoWNx:
Here is one of the latest fixes hope this helps..

If you're having slowness and are using ext2 for your apps2sd, get this file and flash it (flash_image boot xxx):

http://n0rp.chemlab.org/android/testing/boot-extfix.img

You might also need to wipe dalvik-cache.

__________________

Google ION - CyanogenMod-4.2.10 + Recovery 1.4

Twitter: cyanogen

Website: http://www.cyanogenmod.com

Issue Tracker: http://code.google.com/p/cyanogenmod/issues/list

Wiki: http://wiki.cyanogenmod.com

If you like my stuff, buy me a beer!
[G1 Android Development] JustinHorne:
Holy crap. That fixed it.

THANK YOU! :)
[G1 Android Development] skrki:
No, you are wrong. If he posts solutions again, then the people will take this for granted and continue spamming the board with repeated questions. We want you to learn to search, and follow the rules of the forum and this thread.

And you people need not search 900+ pages, but only read the posts since the latest update.

In addition, you should read the posts that contain links, and maybe set your user settings to display 50 posts per page. Now, how obvious was that?

The solution to your problem is even more obvious, hence you aren't getting replies. You have a corrupt file. The first this you should do is re-download. Then do a md5sum check. Your (only) post here should be: I have this problem, I've done the md5sum verification, and I'm still facing the error....'.
[G1 Android Development] geppo1975:
Hi....its a bug of dialer/contacts 2.0!!!update at 2.01 and it function!
[G1 Android Development] tmon4ju:
My experience

Well, Id say that something is wrong with this version. I'm not going to post all of my problems. But i've been working with cy's roms for a while, and I know what to do to correct things. None of the usual fixes work for me. And for the people who say, that you have " never wiped " and things are working good. I Doubt that. I think you just settle for what you get. I don't settle for any force closes. I'm using 4.2.9.1 now. And it's good. I look forward to the updates, but this one is not happening. Something is wrong. I get slowness, from the start, screen freezing, a force close at the begining, and overall slowness (really slow). And I wiped (everything), tried the DRC83_base_defanged, ran fix permissions. Still didn't fix it. Hopefully cyanogen notices that there is a problem and fixes things. Not complaining, I went back to my 4.2.9.1. Keep up the good work Cyanogen, but i'm bored and don't have anything to do, if I can't update my phone..
[G1 Android Development] PsychoI3oy:
I last wiped before upgrading between JF 1.51 and CM 3.6.4.

In 4.2.10.1 I have had 0 unexpected force closes. The first boot my desktop didn't load icons, but a reboot fixed that. Everything has been working smoothly (except the few known issues WRT contacts and download window) and I honestly don't see what is causing everyone's problems.
[G1 Android Development] 86Apex:
Sorry to burst your bubble, but I haven't had any slowness or FC's since upgrading. No wipe, just cleared dalvik after flashing. Sorry you're having problems.
[G1 Android Development] damwid:
I have observed several times the phone reboot to recovery when doing some operations with 4.2.10.1, anyone has the same problem?
[G1 Android Development] codito:
I don't see anywhere here where you flashed the fix for the whole slowness issue that's been discussed over and over in the thread.
[G1 Android Development] retaliator:
app2sd question

Merry Christmas to you all folks.

Does anyone have a link to a video with instructions for settings app2sd or easy to read step by step instructions.

note: for some reasons it is not possible to make connection with my pc.

Thanks in advance...
[G1 Android Development] vincom2:
http://androidandme.com/2009/08/news/how-to-manually-partition-your-sd-card-for-android-apps2sd/
[G1 Android Development] retaliator:
Thanks for answering.

Unfortunately, it is not possible to make connection between my HTC Magic and my computer. (I tried to do this several times.)

I have a terminal programm on my phone but I don't know this wordks the same.
[G1 Android Development] sp33dyS:
I've rooted my phone yesterday, loaded CM 4.2.10.1 and it's working very well.

But I had to enter APN settings by myself and I've got some FC's when I try to access Bell volume control and Multimedia volume control in Settings menu.
[G1 Android Development] PsychoI3oy:
Your old settings probably have ringtones selected that aren't there anymore. CM ships with only one ringtone to save space. See the first post for audio-resources.zip, unzip it on the sdcard, and reboot. Then pick your ringtone(s) and notification noises again and the volume adjustments should be fine.
[G1 Android Development] sp33dyS:
Yeah, that was the problem. Thanks.
[G1 Android Development] snellx:
I've been using CM for several months now and never had a special problem. All upgrades without wiping, just dalvik-cache.

But in the 4.2.10.1-Version my radio just doesn't start. Baseband-Version is showing "unknown" and I get "radionotloaded"-errors in the logcat.

Beside this "small" Problem everything is running pretty fast, without fc or whatever. But sometimes I need the phone-function... ;) so I am back on .9.1 and wait for the next release. If the radio still doesn't work I have to take a deeper look on this... so far it seems, that I'm the only one with this issue and I hope the next release runs for me...
[G1 Android Development] tmon4ju:
Yes

Who posted it, and where is it at? And right. I read the thread everyday. Don't see nothing. Is it official or what?
[G1 Android Development] Stewartwi:
I just started having this issue tonight. I was on the phone with my brother and my wife called in on three way and then boom the radio dropped out and it wouldn't let me make any calls out until I rebooted the phone. Then finally after about 20 minutes or so it just started working again really strange stuff.
[G1 Android Development] desmphil:
Having an issue sending SMS message when clicking on TO

I have the latest version 4.2.10.1 upgraded from previous versions.

When i go to messaging, new message, and click on the icon, it crashed.

Here's the log.

Anyone having the same bug?

12-26 08:48:40.307 I/ActivityManager( 141): Starting activity: Intent { act=android.intent.action.GET_CONTENT typ=vnd.android.cursor.item/phone cmp=com.android.contacts/.ContactsListActivity }

12-26 08:48:40.337 I/System.out( 455): null

12-26 08:48:40.597 D/dalvikvm( 465): GC freed 4682 objects / 276576 bytes in 115ms

12-26 08:48:40.857 D/AndroidRuntime( 465): Shutting down VM

12-26 08:48:40.857 W/dalvikvm( 465): threadid=3: thread exiting with uncaught exception (group=0x4001e170)
[G1 Android Development] snellx:
just tried it again.

Here is the radio log from ddms.
[G1 Android Development] snottily:
Fix for slowness issue (ext3/4 mounting bug)

quite official:

http://xdaforums.com/showpost.php?p=5208921&postcount=8880

how to install that fix:

http://wiki.cyanogenmod.com/index.php/How_to_install_testing_kernels

or, in the terminal app do:

$ su <enter>

# flash_image boot /sdcard/boot-extfix.img <enter>

# reboot <enter>

all of the above was posted in the early hours of dec 24. in this thread.
[G1 Android Development] randomness55:
a bit of a noob question here but I was wondering, I want to wipe the dalvik cache when I upgrade to .10.1 and I wanted to know if I should wipe it before or after flashing the ROM? thanks
[G1 Android Development] vincom2:
I'm not sure... I think if you su and unmount the sdcard first it might be possible (again I'm not sure, someone please correct if I'm wrong, but I think "umount /sdcard" will do it).

I was going to suggest recovery console, but then I noticed you have a magic >.>

I think the best way would be to install this recovery: http://xdaforums.com/showthread.php?t=530492 and use the interactive partitioner. Never used it myself so I can't help you there though.
[G1 Android Development] Ace42:
You wipe before...Wiping after will leave you in a bad place..
[G1 Android Development] detox702:
All he did was repost the same problems, hence creating the same type of post he was railing against.

If you want us to learn to search, fix search. If I search for "BlackPaddy 4.2.9.1 Theme", and my first response is to a WINDOWS ROM and the first page is nothing even related to what I wanted, then, I think, something's wrong.

Finally, that isn't an obvious problem(Edit: Obvious *Solution*), because when a file doesn't download correctly, and you download it again from the same place and it still doesn't work, and you do it even a third time, its just a waste of bandwidth. If you actually have a working copy of 4.2.10, would you be so kind as to post it on a new mirror?
[G1 Android Development] MrS.Mirage:
Where can i find this APN list?
[G1 Android Development] Ace42:
When in settings-->Wireless->Acess point
[G1 Android Development] Chosen_on184:
This has been addressed by a lot of people including myself. Go two to three pages back and you will see that i asked for a mirror to a file by wysie that fixed this problem. three post later someone mirrored the file with megaupload. flash that file and it fixes the messaging bug ...

here is the thread with the file .. if you have the file already can you post on another download site ... ex .. megaupload ....

http://xdaforums.com/showthread.php?t=599194 << link to the thread >>

http://www.megaupload.com/?d=8H1MWNO1 << link to the file >> flash like any other update file and messaging fixed after reboot

Rule of thumb when searching this thread before you post always go back 5 pages and read through every post .. 9/10 times you will see your problem being addressed with a solution to it .....

First started doing cyan roms i used to wonder why people had a hard time just answering questions .. but the truth is .. it does get annoying when someone ask a question and the answer was just a few pages back ( not saying anything against your post ... just a general statement) ...so my rule of thumb is always go back 5-6 pages and read through before posting a issue i encounter cuz 9/10 times it was already addressed
[G1 Android Development] _zygo_:
Or at least take a look at the thread's update date (this one says [UPDATED 12/23 - v4.2.10.1]) and back up to that date and start reading from there. That's like, 20, 25 pages with the default page count? Searching is getting a little tough, though. Advanced search helps quite a bit. Searching for "dialer" in the last week + newer brings up the new Contacts.apk link and download in the first result.

Back on topic, I didn't want to wipe to get this ROM to work properly. I kept getting the home screen FC and google account FC. I normally don't wipe, but did in 4.2.6 (phone and SD) to get rid of the incoming-call crash issue. Last night I wiped everything, repartitioned my SD (ext4,) pushed defanged base, 4.2.10.1, and new Contacts.apk, flashed both and pushed the new apk, and didn't have a single force close or error message after reboot. Has been working perfectly since. If Psycho hasn't wiped in six months, more power to him. I think a flaky theme (I tried a couple) or app can wreak havoc, even after you flash over them. I can tell by my icons that remnants remain. Took about 20 minutes to wipe, flash, and load all of my apps.
[G1 Android Development] thephantom007:
Question about WIFI conection

I post this question here because its the rom im using and i been searching on internet about this problem but with any result, im having this issue, unfortunately i live in a place where its poor signal and my phone most of the time its on EDGE mode so y connect my phone through my wireless network to use the internet and all the stuff u know, but most of the time it says its not internet connection and i have to reload the web page on my phone until it loads its the same for the market app, did some one its having the same issue? i change the range of my router and everything on my pc and i still having the same issue, dont know what else to do
[G1 Android Development] randomness55:
oh alright, thanks for letting me know. what happens if you wipe the dalvik after your flash the ROM? i'm a bit nervous now cause when I upgraded to .10.1 this morning I wiped the dalvik after...
[G1 Android Development] desmphil:
Well if you wonder why people have a hard time and you found this annoying.

This is what i did, and this is always what i do search 10 pages back. Rule of thumb, tracking bugs and fixes shouldn't be listed in a blog but more in issue tracker where you can track each of them separately.... this thread as over 1000 pages.. the search isn't the most sophisticated one either.

The main page should include a list of know issue since the release of the current release. It would be easier for everyone and save pages and therefore time for everyone searching thousands of page where information can be outdated.

Whatever... your not the first one to make the same comments but you dont do anything to have it resolved.
[G1 Android Development] Nickedynick:
I wiped earlier after installing the new build and have had no problems since. As far as I know the only downside is that it takes longer to turn on the first time after you wipe it.

No preferences are saved in dalvik cache, but when you install different versions of things it can get cluttered and slow down your phone. Especially new ROMs. The reason CyanogenMod takes ages to start the first time it runs is that it goes about writing new files to the cache.
[G1 Android Development] randomness55:
Oh alright. Well, I haven't noticed any problems since my upgrade this morning, everything seems normal so hopefully everything remains good
[G1 Android Development] Chosen_on184:
to my knowledge nothing .. the cache is regenerated once you reboot the phone ... only thing that happens to wiping the cache wether before or after flashing a rom .. is that the phone will take a tad bit longer to boot cuz its re writing everything .....
[G1 Android Development] randomness55:
alright, i should be ok then. thanks!
[G1 Android Development] highvista:
My habit has been to run fix_permissions and delete my dalvik cache files from the console right after each upgrade, before booting the new ROM. I've had no problems at all. So wiping after is definitely not a problem.
[G1 Android Development] randomness55:
that is actually what I did using the console also

I usually run fix_permissions after every upgrade. This was the first time I wiped the dalvik cache
[G1 Android Development] Tawm:
Just updated to 4.2.10.1 and it is extremely slow.

I leave it at the ANDROID boot screen, which is slow on first boot anyways (as normal), but when it gets to the PIN Code screen I just can't do anything it is so slow, this was even after trying downloading the ZIP twice on different computers and falling asleep while it booted last night!

I tried clearing the Dalvick Cache but it didn't seem to help, does anyone have any ideas?

Edit: Sorry, im an ass, ill try the ext fix -facepalm-
[G1 Android Development] joshua_tam:
I don't know whether it is a bug:

I can't connect to my AP that runs at channel 13
[G1 Android Development] cvenk:
normal update - should I say upgrade

AND it's SLOW ......

going back to 9.1
[G1 Android Development] sonny82:
ive been having problems with every rom after 4.2.6. 4.2.7 and 4.2.7.1 the browser and Ebuddy force closes and i have 2 end up rebooting my phone because the screen will go blank. 4.2.8 all the way through to 4.2.9.1 has kinks in theme where the Ebuddy doesnt stay signed on it cuts you off when u switch to a different app. and 4.2.10.1 was slow for me it wouldnt even let me get to the google sign in screen, it just was very laggy and slow. please tell me how 2 fix these problems or has anyone else experienced the same issues? HELP!
[G1 Android Development] deadsoullp:
SMS FAIL!

Hi Friends,

before the update 4.2.10.1, i can´t open my contacts for send the SMS.

Say "Force Close" !

What the solution for this!?

Thanks a lot and big hug for all!!!
[G1 Android Development] Mickey G:
Give this a shot - you probably need to update the Contacts by Wysie file. This fixed my Direct Call and Direct SMS force closes (android.process.acore).

Update the Dialer/Contacts.apk file.

http://xdaforums.com/showthread.php?t=599194

Copy file to the root of your SD card, reboot in recovery, and flash update.

Worked for me – need I say do a Nandroid backup first?
[G1 Android Development] flarbear:
"Wipe" what?

He was asking about "wiping the Dalvik cache" and I think that is OK at any time (but causes a long boot time on the next boot), right?

"Wiping the phone" would be bad right after a flash, though. (And the "bad place" in that case won't be subtle - it won't boot, right?)

This led to half a page of "Uh oh", "no it's OK", "I did it and didn't see a problem" a few hours later. D'oh! So many similar terms with radically different meanings.

You can "wipe" the phone or the Dalvik cache or the ext partition

You can "flash" a ROM, a pair of ROMs (OTA/CM), a recovery, an SPL, a radio(?), a theme

And in the end, people end up saying "wipe it" or "flash it" and the contexts get lost in the quoting/requoting or threaded conversations (or simply when it's late and the eyes aren't working so well)...

It's probably better to use complete phrases/sentences whenever possible to avoid any misreading/misquoting ambiguities.
[G1 Android Development] merdely:
Upgraded my SD card to 16 GB Class 6

Yesterday I got a new Transcend 16 GB Class 6 Micro SD Card. I partitioned it as described in my signature. Then I did a nandroid backup, flashed to 4.2.10.1, fixed UID mappings, cleared the davlik-cache from the console, and *then* I booted to 4.2.10.1 for the first time. I then flashed the CFS memhack boot image in my sig.

So far so good. Music keeps playing and things seem very fast.

In fact I am posting this from my G1!
[G1 Android Development] bmj1086:
I'm willing to bet you're partition ext2 partition.
[G1 Android Development] flarbear:
Thanks jubeh for this heads up. I've read up to the current posts and didn't see if anyone confirmed this officially, but I had a couple of questions about what you are saying here. Unfortunately I think the nature of this issue leads to some double-negative (or reverse-negative) kinds of statements.

You talk about "wrong keys" and "corrected keys" but those terms appear to be from the perspective of something that HTC was trying to fix and in so doing they got it right for them and wrong for us. And so the "wrong" and "corrected" there have nothing to do with whether or not these files work well as a base for CM, right? In this, and in some of your follow up posts it isn't clear when you use those terms if you are meaning "wrong from someone else's perspective that is incidental to what we want" or "wrong for our uses". In particular, in your last post that I quoted it looks like the line that says "correct keys" is the one identifying the build that works fine, but earlier it sounded like you were saying that the builds with the "corrected keys" were the builds that were causing problems, which just confuses the matter further, no?

I'd suggest:

- Not using "wrong" and "corrected" when referring to builds we might (or might not) want to use if they will label the builds contrary to our desires/needs. Try using "incompatible build" and "compatible build" instead

- Your first post mentions some keys, but in one build that I have (the one I used), I find the string "test-keys" in 4 different places both with and without a prefix of "adp" so I'm not sure if this build is right. In the end, I decided that the line that defines the "ro.build.fingerprint" property was the one you were talking about and that line ends with "adp,test-keys" and so I think my build is fine, but your description was a little vague on that point.

- List some specific MD5 checksums for some builds that you know are incompatible (and maybe some that are compatible) so we don't have to dig into the zips and read the 4 different places where the string "test-keys" appears to try to determine if we have the right one or not. And, reiterating the point above, identify these builds as being compatible or not compatible with CM rather than using the term "corrected" and "wrong" which seems to have gotten confused through your thread.
[G1 Android Development] flarbear:
A suggestion for the changelog.

Right now it says "fix for ext2 mounting problem", but doesn't describe the symptoms people might be experiencing. If my phone was really really slow I probably wouldn't think this line item had anything to do with my experiences (gee, I'm not seeing any ext2 mounting errors...?). It might help if the issue was described by how the users experience it, not by the technical details of what caused it. I'd suggest:

* KNOWN BUG: If your phone is extremely *slow*, use [this boot image] which fixes a problem mounting ext2 partitions that can cause such slowness, until I can release an update.
[G1 Android Development] jgato:
Hi there,

this is my first post, sorry if this is not the right topic...

I am having very much problems with the battery life of my HTC Magic, about 10 hours with a no intensive use.

I have been reading that CM is always running with the cpu overclocked, could it be the problem? should I use some widget to control the overclocked cpu?

CM4.2.10.1

regards,
[G1 Android Development] stoiccontrast:
I had to do the same and 9.1 runs fine. Something is definitely odd with 10.1, it is just doggishly slow/almost inoperable on my phone. Tried reinstalling it again and had to flash back twice.
[G1 Android Development] Brajin:
Cyan tweeted earlier today he was releasing 4.2.10.2 with a bunch of bug fixes. Has anyone tried to apply the 10mb ramhack to the latest cyan....I was running build 10.2 from wes gardner build the sync was acting up on that rom.

T-mobile G1

hard spl

512 mb ext4 96mb swap
[G1 Android Development] merdely:
I'm using the ramhack (see my signature) and have been very happy. Make sure you're using a class 6 SD card. It made a huge difference for me.
[G1 Android Development] merdely:
Boot Image EXT fix

Be sure you've installed the boot.img file with the EXT fix. Other wise, your ext3/4 partition may be mounted as an ext2 filesystem and cause sluggishness.

Here's the image: boot-extfix.img (from the first page of this thread).

Flash is through adb:

./adb shell flash_image boot /sdcard/Download/boot-extfix.img
[G1 Android Development] digitaljeff:
you can try the "overclock widget" by billy culi (its in the market for free) it works great...

however 10hrs seems about right, are you talking lots on the phone? have wifi, 3g and gps turned on?
[G1 Android Development] The_Franchise:
didnt work for me
[G1 Android Development] circusreject:
I'm using the 4.2.9.1 BFS RAM hack http://xdaforums.com/showthread.php?t=566410 with Cyan 2.10.1 and it's lightening fast. I used RA-1.5.2 recovery to upgraded ext2 to ext4 and all is well. Haven't run fix_permissions yet but probably will if any issues come up.
[G1 Android Development] zimphishmonger:
Have the same issue here, Hopefully it will be one of the bugs that gets fixed w/ tonites update.
[G1 Android Development] njgheewala:
Ahhhhhhhhhh! I did not realize that...that is why you guys are the experts! :D
[G1 Android Development] cloverdale:
I have done nothing to the cpu clock, but I still have about 16-24 hours with no intensive use, and about 5-8 hours with intensive use.
[G1 Android Development] tnt8902:
broken link

There's a broken link when you have to download the rc29. Can anyone supply me a link for it. I got a new g1 with 1.6 and have to root it the old fashion way.....
[G1 Android Development] tmon4ju:
Seeing that I am not using ext2 didn't think this applied to me, I'm using ext3.
[G1 Android Development] snottily:
go to console, type 'mount' and check what gets reported. the problem isn't what you selected to be used, the problem is what the OS sees and mounts.
[G1 Android Development] tmon4ju:
Ah, ok it says ext2. Thanks, i'll give it another try.