yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ready4thebreak:
I'm beginning to believe a lot of these issues are coming about from Java errors(which I've never seen a ROM have before). Myself and others are getting Java errors from AdFree. Cyanogen came out with a new update because the CM Updater app was broken by Java exceptions. And now people are having issues with Spotify(Read post http://xdaforums.com/showpost.php?p=5076085&postcount=6938)

E/AndroidRuntime( 8297): java.lang.ExceptionInInitializerError

So I don't know a ton about exactly how Android runs, but I know a lot of its framework is based around Java, so I'm beginning to think, Messed up Java= Messed Up Android.
[G1 Android Development] ragflan:
I even took out my phone manual to check if I am inserting the sim card right, and I am. The SIM card was fine with 4.2.6 but now even if I flash 4.2.6, the sim card says NO SERVICE.
[G1 Android Development] ragflan:
Is it just my computer or does everyone not see the links on http://developer.htc.com/adp.html#s3

I've been checking their site all day long. No links, just text for the 1.6 signed_dream_devphone_userdebug-ota-14721.zip
[G1 Android Development] ZilverZurfarn:
Nope, it's not you. The links are gone since a couple of days. The jury is till out on what to make of that.

/Mats
[G1 Android Development] ragflan:
Hi! Could you offer me any advice on what to do with my situation? I've been trying to get into my phone all day long. The flashing process either fails or go through but shows NO SERVICE. I can do the whole initial setup procedure (the phone -does not- warn me about no sim card being found). But when setup completes, it says no networks connection. Then I skip setup procedure and try to connect over WiFi but everything FCs.

Tried reflashing and formatting all partitions and removing and remaking them, then tried flashing 1.6 and 4.2.7.1 (and 4.2.6 when 4.2.7.1 didn't work). Anything else I can try?
[G1 Android Development] ZilverZurfarn:
Yes, try running logcat while booting and see if you can spot any errors that may give you (or someone else) a clue to why your phone misbehaves.

/Mats
[G1 Android Development] ruipedrovalente:
I had the same problem but them i installed bc-4.2.7-ebi1_bfs-signed.zip and the problem was solved.

you can download it here http://xdaforums.com/showthread.php?t=592377.

Best regards
[G1 Android Development] ragflan:
That's for Magic/MyTouch3G phones right?
[G1 Android Development] ragflan:
Hi. I'm so sorry to be a burden. I'm still very new to this. I got these intructions from the Android Developer site.

I have the SDK installed. I connect the phone to the computer, select Device -> Logcat, then I boot the phone. Correct?
[G1 Android Development] plasmadragon007:
For all who can't find the signed-dream_devphone_userdebug-ota-14721.zip, I have a post on page 691 of this thread that has two link's to download it from a mirror and the op who posted the websites.
[G1 Android Development] plasmadragon007:
What operating system are you using?
[G1 Android Development] ZilverZurfarn:
Connect the phone to your computer. Open a command window. Boot the phone. Type

adb logcat

in the command window, and you'll see

Waiting for device...

or similar, then lots & lots of text will start appearing on screen after a few seconds.

/Mats
[G1 Android Development] guillaumemarques:
I can't find any size settings into messaging... Where could I find it ?
[G1 Android Development] FatBoyExtraordinaire:
Thanks for the confirmation. Should save me some stressing over whether or not I'mma F up and unroot my phone or something.
[G1 Android Development] ragflan:
Hi, I am using Windows 7.
[G1 Android Development] ragflan:
Thank you! I'm gonna try that tomorrow morning. 12am here in Melbourne...
[G1 Android Development] scasio:
Weekdays

Hello!

Since version 4.2.6. my week starts with sunday. I'm from Germany and i have enabled the german language on my htc magic.

Also in the alarm clock i see only numbers instead of short weekdays names.

Is there a way to change the start to the week to monday?

Regards!

Lars
[G1 Android Development] Nepomukky:
I am still stuck with the problem I described above.

adb logcat doesn't help a lot. I only see the - wating for device - message. The Magic reboots when it still displays the boot logo. There are no logcat outputs at this time. So the device loops displaying the boot logo all the time without any logcat output.

I cleared dalvik-cache (rm -rf /data/dalvik-cache/* via adb shell when in cm-recovery), too. I reformatted the SD card (just one big FAT32 partition, I don't use Apps2SD or Swap). I tried booting the device without the SD card plugged in. I tried another Recovery Image (RA-magic-v1.3.1) performing all the wipe methods (wipe data, wipe cache, wipe dalvik-cache) before rebooting the first time after the update.

Nothing worked. Still there are these boot loops. Even if I flash ADP DRC83 first again, followed by CM 4.2.7 or 4.2.7.1

For the sake of completeness: I flashed the splash screen (boot logo) a long time ago (when CM 4.0.4 was up-to-date). But I don't think it has something to do with this issue. I updated several CM versions since that time.

My HBOOT mode displays:

SAPPHIRE PVT 32B ENG S-OFF H

HBOOT-1.33.2004 (SAPP10000)

CPLD-10

RADIO-2.22.19.26I

I don't know what could cause the problem. I guess I tried it now for the hundreds time. :(
[G1 Android Development] Joe333x:
i found my issue, i some how managed to add a number to the black list without even knowing
[G1 Android Development] okubax:
upgrade to CyanogenMod v4.2.7.1 went smoothly with no errors for me on the G1. Phone boots up much faster than on the previous release and menus are more responsive.

10/10
[G1 Android Development] skrki:
Considering you have ENG SPL, you can try booting into the ADP image, see if that one boots up. You will have stock Donut in this case, and it will erase your (custom) recovery.

If you CAN boot into stock 1.6, then you will need this to get your recovery back:

http://wiki.cyanogenmod.com/index.php/RE-recovery-img

(I suggest you take Amon_RA's RAv1.3.2, and follow the second method from the Wiki, the one that uses bootloader)

Once you get your recovery back, just boot into it and flash CM4.2.x without a wipe. Reboot and hope for the best.

However, if you can not boot into stock Donut, then there might be something physically wrong with your device, though I can't be sure.

Good luck!
[G1 Android Development] Nepomukky:
Thanks a lot for this hint.

Indeed I CAN boot the ADP image.

I restarted in fastboot mode, started the Amon RA recovery (fastboot boot recovery.img) and flashed the CM 4.2.7.1

After the reboot the boot screen loops again. :(

Very strange!
[G1 Android Development] skrki:
OK, now that's a real pain! Check the md5sum of your download, though this should be the first thing to be done (and I took it you did that...until now) If that doesn't match, then you have a bad download! If they do match, then I'm all out of ideas :(
[G1 Android Development] Nepomukky:
I checked the md5sum, of course. ;)

I repeated the procedure you proposed with several CM updates.

Wiping, flashing ADP, booting ADP, flashing CM without wipe.

With 4.2.6 it works, no problems.

But neither 4.2.7 nor 4.2.7.1 can be booted. There's always this frustrating loop of the boot logo.

Nonetheless thank you very much for your hints.

Unless anyone has another brilliant idea, I will restore my 4.2.6 nandroid backup, wait for Cyanogen's next update and hope that it will work for me again.
[G1 Android Development] skrki:
Hmm.. well that's too bad. But I've had that happen with certain Sense ROMs... like, everybody was happy as hell, saying the ROM is great and all, but for me it just would not boot! Then again, with those ROMs, cooks sometimes provide several different boot images (kernels) so if one doesn't work, another one may.. But with the CM, this doesn't appear to be the case. You have his normal kernel and maybe an untested/unstable BFS kernel, and that's it! This is at least the obvious, maybe some kernels that fly around XDA would be possible to boot, but I don't usually have the time to dig that deep.

I hope some future release works out for you!
[G1 Android Development] ruipedrovalente:
Yep, it's for a Magic
[G1 Android Development] obe1:
logcat on adb

im running the latest cyanogen mod and just for giggles i ran logcat to see how my phone runs and see the process and i noticed 3 process/apps keept dieying in the back ground like every 10 seconds google voice, google media, and google gapps. examples

I/activitymanager(141) : process com.google.process.gapps (pid 23367) has died

I/activitymanager(141) : process android.process.media (pid 23356) has died

is this suppose to happen in the background i dont get forecloses just wondering why they keep dieying just wondering if this is normal.

Sorry heres the google voice crashing log every 15 seconds for voice

W/ActivityManager( 141): Scheduling restart of crashed service com.google.andro

id.apps.gtalkservice/com.google.android.gtalkservice.service.GTalkService in 360

8064ms

I/ActivityManager( 141): Killing app com.google.android.apps.googlevoice (pid 2

3466) because provider com.google.android.providers.settings.GoogleSettingsProvi

der is in dying process com.google.process.gapps

anyone else seeing this on logcat with latest cyanogen maybe this happen all along I just never went into logcat just so were clear I DO NOT GET FORECLOSE MESSAGES.
[G1 Android Development] skrki:
That one seems to be for Magic 32A. What it does is gets you ADP rooted base, so you can install the CM, and then patches up the kernel for users with 32A devices. This is what I got from the OP...

The image you were suggested to download is the BFS kernel for CM4.2.7, but I'm pretty sure that's a port for 32A devices.

Another suggestion would be to get Cyanogen's BFS kernel 4.2.7. I'm sure it's posted somewhere in this thread. Basically, you would replace the 4.2.7.1 kernel with a previous version... that might work, but I'm guessing all the changes on the "low level" (that Cyanogen stated in the OP) would be gone this way.

Have a spare boot image at hand if you choose to flash that EBI port... just in case things go wrong ;)
[G1 Android Development] pcrodent:
Thanks for your help! I found that the Market will download more or less properly if I connect to my secure WiFi network, so I'm good for now. Hope I can download stuff while on the go again soon though..

Ooh, if you'll permit me the cockiness of requesting stuff without being able to properly give back, it would be great if I could select the predictive input language separately from the phone OS language. The thing is, I hate the crippled translations of English tech lingo into Dutch (in the OS language), but have to do most of my texting etc. in Dutch... That's really the only thing I'm still missing on this phone. (well, that and the google nav thing working in my country, but that's not something that's up to you guys :) as far as you're concerned: great job so far, thanks!)
[G1 Android Development] misha:
Reboot issue

Hey guys/girls.

I have been running CyanogenMod for a very long time. SUPER Happy with it.

With a few of last release I have started running in to the following issue.

In my car the phone stands in the holder horizontally, therefore any action I do starts from a landscape view. (use it for Google Navigation and music navigation, sound out via AUX)

Steps to make the phone reboot:

1.	landscape view

2.	toggle Bluetooth ON via widget

3.	wait for headset and phone to connect

4.	press on a shortcut (anycut) to make a direct phone call to an existing contact

5.	Phone REBOOTS trying to make a call!

If I do the same in portrait mode, everything is good.

Any ideas?
[G1 Android Development] moorhuhn:
hi

is there a possibility to save the stuff on the ext3 patition?

because my cyanogen rom is very slow.

i don't think it's because of the rom but my device.

so i want to wipe everything but before that i want a backup from the ext3 partition with all my apps.

there are some special entries in the Amon-RA-Recovery like move apps to SD aso.

or Bart backup.

I dont know these things.

Is it usable for my purpose?

Please help speeding my rom.
[G1 Android Development] droiddv:
I just installed the 4.2.7.1 after a full wipe, I tried t-mobile's visual voicemail this morning, f/c, tried rebooting and starting the program several times, f/c no matter what I do. Is anyone else having this issue? Or should I try a complete wipe and flash both roms again. Only change I made was pushing a Contacts.apk to the rom. For the eclair dialer. I wouldn't imagine that would cause any problems with the visual voicemail, but who knows.

Quick note, I resolved my issue. :) I had to turn off Wi-Fi.

:confused::confused::confused:

I have been also experiencing random reboots.
[G1 Android Development] randomness55:
So I deleted some stuff from my memory card and this time Nandroid worked! So I guess that's all it was. Thanks for the suggestion

I flashed 4.2.7.1 this morning and so far it's been working pretty good. Haven't had time to mess around with it but so far no random reboots so that's already a plus
[G1 Android Development] rakjer:
No need for a huge discussion on this, but since the intro of the "compcache toggle" in spare parts, which has worked better for you. on or off.

Just reply "on" or "off".

Off for me.
[G1 Android Development] caseyf75:
Hello all - I'm new to Cyanogen and love it so far, just have some things I'm still trying to figure out. Can anyone point me to instructions on importing the *.ogg ringtones that come with the rom? I can't seem to find a utility to move them from the sd card to the phone. Thanks!
[G1 Android Development] meuhlavache:
Just put the "audio" folder from the .zip on your root sdcard folder, they'll be recognized by your phone.
[G1 Android Development] schyzo001:
Hi,

I flashed with the lastest ROM, but as i already had the gMail problem, I decided to follow the "Full Update Guide" to start from the begining (http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_MT3G/Magic_Firmware_to_CyanogenMod)

But I have a very big problem on step 6 : I restarted the phone, and I have to login with my Google account.

But I have the following message :

"You don't have a network connection.

This should be a temporary problem or your SIM card may not be provisioned for data services. Please try again when you are connected. If it continues, call Customer Care."

I saw that someone has the same problem and he solved it by adding a new APN...but I really don't know how to do this...

PLEASE HELP MEEEEE !!! :'-(
[G1 Android Development] bbuchacher:
ahh this thread always makes my mornings go by better. All the noobs who dont know how to follow simple instructions. hehehe. No issues here, rom is running fine, i have all my google apps, i know how to count so following numbered steps is pretty easy for me, If anyone needs help with understanding which comes first 1.

or

2.

or 3.

send me a PM

great job cyan as always
[G1 Android Development] randomness55:
2 self-reboots in the past 2 hours. I guess I should just try wiping then reinstalling the ROM.
[G1 Android Development] schyzo001:
@bbuchacher :

Is that an answer ?

Yes I'm a "noob" as you said...but I followed all instructions, starting by the first one.

Also, as I'm french, it's not so easy for me...

Now my phone doesn't work, and I'm just asking for some help !
[G1 Android Development] bbuchacher:
sigh, no it was just a general response to the past 600 pages..

anyways let ur phone sit on the login screen for a couple minutes, sometimes it takes a minute for the data connection to turn on after you flash a rom.

otherwise reflash your radio,

if you dont know where to get the radio

start over and reflash HTC adp recovery image and then reflash latest cyanogen.
[G1 Android Development] dan-htc-touch:
what carrier are you with? it's possible that you have a new one, and your apn has not been added to the list yet. good news is, you can skip the sign in step, and log onto wifi before setting up you g-mail acct.
[G1 Android Development] antonief:
When Google starts just hit the menu button and add your providers apn.
[G1 Android Development] Estyle:
widgets not work well on 4.1.999.. i did wipe wipe ext ... so back to 4.1.11.1
[G1 Android Development] virdi:
@cyanogen weird BUG in v4.1.999

Updated from ext3 formatted/wiped v4.1.99 to 4.1.99 (as per directions) and it restored all the applications I had even before the "fresh" install of v4.1.99, that was 2 installations ago (even before flashing ADP1)

Detailed explanation:

1. Install A:

Installed 4.1.11.1

Installed applications A1, A2, A3 and so on...

2. Format ext3 partition from recovery:

mount /system/
rm -rf /system/sd/

3. Emptied FAT partition of the sdcard (including all existing nandroid backups)

4. Install B:

Installed 4.1.99 as per directions (wipe, ADP1, CMv4.1.99)

Installed applications B1, B2 ,B3 and so on...

Worked fine, with only applications visible in the panel being B1, B2, B3...

5. Install C:

Installed 4.1.999 on top of 4.1.99 (of Install B)

Rebooted

Problem: All applications from Install A as well as Install B are available.

So, now I have applications A1, A2, A3... B1, B2, B3... and so on...

Weird and creepy. Any thoughts? Any help? (or is it just the sdcard going bad?, but why would it do such creepy things)
[G1 Android Development] kerauno:
You should not fill up thread asking these questions. Try it first. If you have a problem then search to see if others have posted. If you don't see anything, then post a question.

Anytime you experience problems with a beta or experimental, you should start clean. Wipe, install rom. remove dalvik-cache.

Cyanogen,

Well done as always! I'm thinking this is 4.2. Glad you are back! Bluetooth is a must for me. I never put the phone to my ear. I had to fall back to 4.1.11 until it was resolved.

Also, I know you use copilot, here's a tip if you have not found out. Turn off the sound that is played when clicking or moving around. It makes copilot faster moving around the menus.

Oh. DId you include the "Slide ME (Sam) app? Looks and works good for installing apps from sd card.
[G1 Android Development] Major_Skidmark:
Having same mega-lagging problem when stock compcache settings used. My G1 slows down to glacial speed. Free shows 24 meg and 0 avail. I am going back to swap partition only. (128 meg swap partition on a class 6 card) Which performs much better. I've tried the obligatory fix_permissions and reboots while on compcache and no help. Gonna tinker some more.
[G1 Android Development] j5goog:
can you use Amon Ra's Custom Recovery v1.2.2 for the G1 instead of the cm recovery 1.4 for this new rom?
[G1 Android Development] ganny:
The Recovery image has nothing to do with the ROM...
[G1 Android Development] zhector323:
So simple

well im not sure if anyones tried it but when the 999 release came out i was away from my computer. so i thought i might try it without it. so i took these steps:

coming from 4.1.99 without any custom theme

-downloaded astro file manager in the market

-downloaded the 999 zip file directly to my phone

-used astro to move the file to sd card instead from downloads folder

-turn off my phone

-boot it into cyans recovery image

-flash

worked out perfect for me. now running 4.1.999 which runs smother than 99 and I did it all straight from my phone. hope it helps. :)
[G1 Android Development] roadrunnerx7:
you know, it might have been a good idea to inculde the "little" fact that if you have a theme on, you should be warned you'll need to WIPE to get it working. not sure if this is true actually, but i tried going from 4.1.99(with the gchrome) to 4.1.999. got nothing but acore force closes. ridiculous.

anyway thanks i guess.
[G1 Android Development] sacredsoul:
Originally from Akirah donut. Upgraded to 4.1.99 without a wipe of the ext. Bunch of force closes. did fix permissions. all was smooth. this was a couple of days ago. then upgraded to 4.1.999. more force close. fixed permissions again. running smooth as ever now. thanks cyanogen! Cheers! :)

EDIT : @roadrunnerx7, I came from a gchromes 4.1.99, didnt wipe and updated to 4.1.999. I saw loads of force closes as I said earlier. But I didnt read them all. Mostly apps. So just ran fix permissions. All's good. No more FC's.
[G1 Android Development] PsychoI3oy:
you mounted /system, then you removed the directory /system/sd. You never mounted the ext* partition on the sd card.

You should have:

mount /system

mount /system/sd

rm -r /system/sd/app*

rm /system/sd/dalvik-cache/*

nothing weird and creepy about it.
[G1 Android Development] zhector323:
sorry didnt know about that. ive only been on the forum for a few days. i didnt really know to add something like that but is a good addition.
[G1 Android Development] lb fam:
Kernal panic

I got a kernal panic when I was browsing the web (xda of course) when all of a sudden the phone rebooted itself. Could not get a log because I was in the midst of updating my wifes phone. Everything is running extremely fast and smooth on both phones. The only issue I really see is when you hit the power button it does not kill the screen. Thanks again for the great build Cy.
[G1 Android Development] flashfox:
T-Mobile G1: I just went from 4.1.11.1 to 4.1.99 then to 4.1.999. I followed the instructions (http://www.simplehelp.net/2009/10/04...android-phone/) and I did NOT wipe my phone between 4.1.11.1 and 4.1.99.

1. All of the applications which were running in 4.1.11.1 are working in 4.1.999.

2. Google apps are working just fine (Market 2, Maps, Sherpa, My Account, Gmail, etc.)

3. Apps are running from SD card (I had partitioned a 8GB card with FAT32 and EXT3)

Kernal Panic --> As a FYI, When I press the power button on my G1 it does kill the screen.
[G1 Android Development] PsychoI3oy:
logs from crashes will be in /data/dontpanic/

and 'end button behavior' in spare parts only works with 'sleep', as has been the case for the last 3 experimental versions.
[G1 Android Development] zimphishmonger:
kill-screen issue can be 'fixed' (more of a work around) by using Spare Parts.

EDIT: Not quick enough, haha
[G1 Android Development] virdi:
I followed those commands from the Q&A section.

@PsychoI3oy: Thanks for the reply... but my question remains inspite of that:

Where were those applications (A1, A2, A3...) when I was using Install B?

How can they appear all of a sudden on the third installation?
[G1 Android Development] jaapschaap:
Wow this is great, flashed ADP... reboot (before i knew that's not required)... Well i wanted to flash this ROM but excadently i flashed the Gchrome team onto my adp ROM :P It did work, but now i need to get root again, back to RC27 and do the telnet trick, BUT still i do not have recovery back... I just cannot fix it, ofcourse i tried: http://xdaforums.com/showthread.php?t=442480 (about 10 times repeated) and in telnet it doesn't get any errors but still no recovery :S Anyone know a solution?

Sorry for bad englisch ;)
[G1 Android Development] PsychoI3oy:
Because you removed the mountpoint for the a2sd partition, it probably tried using the /data/app directory with whatever was in it (instead of symlinking it) then when you upgraded again, a2sd did what it's supposed to and copied all the B apps over to the sd card in addition to your A apps, then mounted the sd card.

Suffice it to say nothing weird or creepy is happening. Further explanation on mountpoints/symlinks/the a2sd setup/etc. is beyond the scope of this thread.

ETA: check your PM for a more thorough explanation.
[G1 Android Development] Zerodime:
I think thats a pretty unique Problem.

I wiped, flashed htc-recovery and CM999 but after the reboot (after i entered my Google-credentials) i get the following Log-Messages in the G1-screen

This seems to go on and on.

I can nandroid back to my first rom, but i would like to play with the new one ;)