yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] enomther:
Hey DOHCtor,

Yea I likely will not create a "base" that makes MT3G work out-of-the-box ... I mean it boots with the current base ... it just can't auto-rotate, wifi is dead, etc.

By and large, the base alone is fairly unfunctional anyways ... no tether, no busybox, no nothin cool.

If you really wanted a "base" .. you could just grab HTC's ION build. (Only get root through adb, but whatev)

Anyhow ... the expansion pack will be better suited for users wanting to rid themselves of unwanted "features/apps" in the next update.

~enom~
[G1 Android Development] enomther:
This is definitely the "theme" and the blur xml animation files causing this ... not much can be done. And it's occurring on pretty much any build using these animations.

~enom~
[G1 Android Development] enomther:
Disabling/Enabling most features can be handled by expsetup .. in the terminal app

su
expsetup

Select the appropriate options you desire.

~enom~
[G1 Android Development] enomther:
V_RocKs,

Yup ... this and the "faint" vibrations of the built-in IME are amongst the most annoying of "features" (lol) in the new Donut builds. Hopefully we'll see updates to donut addressing these ...

For now, gotta add the dang area codes to your contacts to rid yourself of the caller id problem you have.

~enom~
[G1 Android Development] olearyp:
...and I know I just mentioned it a bit ago, but Contacts Clean-Up handles adding area codes quickly and easily.
[G1 Android Development] bmj1086:
If you're using the MT3G, like me, I would suggest the HTC ADP 1.6. The widgets do that when you first load them, I have done this on two MT3Gs now and you have to add the power widget, turn gps off, remove it and readd it. When you add the Weather/clock widget you have to reboot. Not sure what it is and there's no way I can tell now but I can tell you that this worked for me twice on my phone and once on my friends. Glad you figured it out.
[G1 Android Development] DOHCtor:
It's all good man. I got the base MT3G from here, which includes netfilter. I even pulled the boot.img and flashed it to your base tmo g1 1.6 rom for my brother and now he too can tether :D.

But yea, I feel that you have drifted away from what you originally wanted to do, which was to stay as close to stock as possible, rom stability, and options options options! lol But now now the expansion pack pushes aLauncher and loccy's browser without giving an option not to install. But it's all good, I remove them through adb and push the original files in.

BTW, google maps doesn't need to be replaced and put in vsapps anymore, the 1.6 rom uses the new gmaps (I know you already know heh).

I still love what you're doing and will be giving another donation soon.
[G1 Android Development] SG_Shadow:
phone number parsing issue

I reported this issue a couple of pages back. Enomther is aware of the issue and is working to resolve it. Let's try and remain patient.
[G1 Android Development] kyuhasz:
Does anyone have any ideas. . .

I tried installing the Donut TMO DRC83 1.9.2 ROM onto my rooted G1. I was successufl in doing the base, however, the Expansion Pack did not work. I tried it many times and the screen just went blank/black.

I did run the base update and it works fine. I'm just having trouble with the expansion pack. I Tried the first two on the left of the link below (The TMO DRC83 and the HTC ADP) and successuflly updated the base for both, but both expansion packs didn't work. I had successfully rooted my phone about a month ago with the latest JF Cupcake and successfully had tethered via bluetooth, used APS2SD, multi-touch, etc. . . It started to get a little glitchy and now that Donut is out, I was hoping to do an update. I did download the Cyanogen's 1.4 (trakball screen) image prior to my last JF ROM, and that still seems to be working fine. Like I said, I know it's rooted because I did successfully store tons of apps on my SD, used multi-touch, teathered etc.

Could I have unrooted my phone accidentally? I'm considering unrooting, but APS2SD was priceless. Any ideas? I apologize, I'm very unkowledgible about this kind of stuff.

Thanks, Ken

Download Files I found/used - CLICK HERE
[G1 Android Development] will4958:
Installing the expansion pack after updating to Donut.

I followed all the steps to the letter, and the base rom itself runs fine. However, after installing the expansion pack with the Advanced Launcher, I started to experience various problems, depending on what I tried to do. On several occasions, I would try to click the Search button in the new Android Market, and after about a second or so the phone would reboot. Even the Google search on the home screen wouldn't work. Also, if I use Backup for Root to restore my apps, certain ones like Steel, won't work and produce constant Force Closes. While the new rom does look nice, it's not really worth all the hassle, unless someone can tell me what the heck is going on, of course. For now, I'm going back to the last stable build from Cyanogenmod, 4.0.4 and one of his snazzy themes. If someone knows how to correct the errors I described, please let me know. Thanks in advance.
[G1 Android Development] olearyp:
*sigh* So you've used Cyanogen and JF before. And you're using Apps2SD, meaning you have an ext2, ext3, or ext4 partition. And you get a blank/black screen after installing the expansion pack.

Post 1, and possibly over half my posts on this forum (all in this thread), will indicate that you failed to clear out your ext partition before installing the expansion pack. Solution: Wipe, reformat the ext partition, flash base, flash expansion, reboot. Enjoy!
[G1 Android Development] SG_Shadow:
rule of thumb...

1) Back up apps

2) If possible, install RA-dream-v1.2.2 recovery image.

3) Boot Into Recovery

4) Wipe

5) Format EXT

6) Wipe, again

7) Flash Rom

8) Flash Expansion

9) Boot, enjoy!
[G1 Android Development] olearyp:
1) Since you said you followed the instructions "to the letter," I'll assume you both wiped and cleared or reformatted your ext2/ext3/ext4 partition on your SD card.

2) Backup for Root ain't perfect, folks. Some applications just won't like looking at old data. Before giving up though, try to reboot to recovery and run the fix_permissions script. If that doesn't work, though, I'd suggest removing and reinstalling the offending applications.

EDIT: My internal snark limiter has just engaged, and I realized I have reached a maximum level of acceptable sarcasm in my last few posts. Since this is primarily due to people who didn't search/didn't read the first post (will4958: I don't mean you), I'll not be answering any more of those posts for a little while. I've just been trying to keep some load off of enom so he can keep bringing us great ROM awesomeness. Other dedicated TheOfficial users, please feel free to fill in the blanks. Enom appreciates donations, but he also appreciates us helping him out on the thread (I have proof in PM form!). I'll still be monitoring the thread and will jump back in when I can bring back the helpful attitude. Later, y'all!
[G1 Android Development] jonstanley2:
curious

would there be any cause for the AdvancedLauncher on htc1.6 to force close often and reload?

Mine does it randomly

any suggestions?
[G1 Android Development] will4958:
Creating ext3(4).

Wow, quick response. Apparently, creating the ext3(4) partitions was the only thing I didn't do. How would I do this on a 1gig card, and is it really necessary? Also, how would I go about applying this fix_permissions script? Thanks.
[G1 Android Development] will4958:
Uncooperative apps.

I forgot to mention... I did try uninstalling then reinstalling the offending apps that kept Force Closing, but sadly, it didn't work.
[G1 Android Development] enomther:
will4958,

ext partitions are NOT required to run this ROM ... just want to be clear. The reason this was suggested was b/c many who are having trouble ... are experiencing such b/c they did not clean/reformat pre-existing ext partitions.

That said, if you lack an ext partition, you don't have to create one ... simply reboot into recovery, perform wipe, flash base w/anyzip option, immediately flash expansion v1.9.2 w/anyzip option, reboot.

With a pure FAT32 sdcard, the above steps should work 100% of the time.

~enom~
[G1 Android Development] iinokturnolii:
<--- NOOB!

im getting a black screen right after the green mt3g screen when reboot after rom install... how do i get back alive?
[G1 Android Development] V_RocKs:
Thanks for the reply!

I gotta go enter in a couple dozen area cods... yippie!
[G1 Android Development] SG_Shadow:
1) Reboot into recovery

2) Wipe

3) Install base ROM

4) [Optional] Install expansion pack

5) Reboot, Enjoy
[G1 Android Development] V_RocKs:
Do you have an ext partition? If so, did you remove (delete) it before installing the rom? If not, a few posts back were the instructions...
[G1 Android Development] iinokturnolii:
i can get into recovery, wipe... but i dont know how to install back to base rom (i cant get into my sdcard and i didnt... ext (partioned my sdcard)......
[G1 Android Development] SG_Shadow:
I'm not going through that hassle. I'll just wait for an update or flash to another ROM, depends on how I feel in the next couple of days.
[G1 Android Development] mdavidf:
I'm going to second this...random FCs with AdvLauncher.

I've tried to reproduce it, but it crashes randomly...not often...but it's happened to me at least three times today. On a positive note, I click "Wait" and everything's fine...
[G1 Android Development] iinokturnolii:
i cant reinstall base rom... cause i cant get into my sdcard.... please help
[G1 Android Development] DOHCtor:
Guys, just remove the AdvancedLauncher.apk from /system/app and use the stock one
[G1 Android Development] olearyp:
Oops, sorry for assuming you were partitioned. I just reread my original reply and I see I wasn't clear. Yeah, what enom said about that :-)

Running fix_permissions: Reboot to recovery (same as loading a ROM).

*G1/Dream: Drop to the terminal window--the exact procedure depends on your recovery image--and execute the command "fix_permissions" without the quotes.

*mT3G/Magic/alternative for G1: This might be impossible if you don't have adb installed and working. If you do have adb, run "adb shell fix_permissions" without the quotes from a command prompt/terminal window on your computer.

The fix_permissions will go through each of the application data directories and make sure each app owns its own data. The restore from your backup should have gotten this right, but it might not have. When fix_permissions is done, reboot.
[G1 Android Development] olearyp:
If I'm understanding right, you're stuck with no ROM, and have no SD card reader? In that case, you'll boot to recovery, then:

G1/Dream: Drop to the terminal, run "ums_enable" (w/o quotes), then plug the phone into your computer.

mT3G/Magic: You'll need adb installed and working on your computer. "adb shell ums_enable" in a command prompt/terminal on your computer (w/o quotes), then plug the phone into your computer.

In either case, the SD card will show up as a mass storage device on your computer. Transfer the .zip files you need for the ROM to the card, then:

G1/Dream: "ums_disable" (w/o quotes), then "exit" (w/o quotes)

mT3G/Magic: "adb shell ums_disable" (w/o quotes)

Then go about the ROM install process as normal.
[G1 Android Development] iinokturnolii:
i got it back!! THANKS!!!!!!!!
[G1 Android Development] blueheeler:
Look for an app in the market called Contacts Cleanup. It will make quick work of fixing and standardizing all your contacts.

Not so related to Android, this may not be a defect or problem, they could be forcing everyone to start using area codes. With more and more cities having 2, 3 or more area codes for a relatively small area, this could be a subtle way of saying get your phone numbers correct. Don't know for sure.

At any rate, Contacts Cleanup will get your contacts all the same way, area code included.
[G1 Android Development] blueheeler:
EDIT: Apologies, just saw this was mentioned already. Delete this if you can.

Look for an app in the market called Contacts Cleanup. It will make quick work of fixing and standardizing all your contacts.

Not so related to Android, this may not be a defect or problem, they could be forcing everyone to start using area codes. With more and more cities having 2, 3 or more area codes for a relatively small area, this could be a subtle way of saying get your phone numbers correct. Don't know for sure.

At any rate, Contacts Cleanup will get your contacts all the same way, area code included.

EDIT: Apologies, just saw this was mentioned already. Delete this if you can.
[G1 Android Development] DOHCtor:
I see you are in my area :p
[G1 Android Development] N!co:
I'm having problems installing PDAnet. You have to install it on your PC with the phone connected. The PC installer pushes it to the phone then. It now hangs when it says its installing on the phone.

I've used a few roms and this was never a problem.

Any thoughts?

(1.6 HTC ADP with expansionpack 1.9.2)
[G1 Android Development] coredump777:
As I said a few posts before, Contacts Cleanup will work for NANP but the numbering scheme is completely different on my country, see my post for details, but basically my numbers are stored in the format (0XX-YY) 3333-1234, XX being carrier code and YY area code.

I tried a different dialer but no game, apparently this parsing of phone numbers are not exactly tied to the dial app.

What we need is an app or means to make android match the numbers from the end to the beginning and not trying to match the whole number.\

The same goes for SMS: I send to a contact, and when I receive a reply it comes with the number and Android does not 'know' that the number and the contact are the same.
[G1 Android Development] MrDva:
The post started out as one thing, then I experienced the boot loop while typing out the post.

I'll say this, both builds I tried worked very well until I powered the phone off and back on. The phone boots to the desktop, then after about 15 secs or so goes back to the android boot screen, it does this over and over and over, you can unlock the phone while this is happening sometimes but it will still restart.

This is the process I followed

I was on 1.8.4

I copied my .apk files to a backup folder on my sdcard.

1st install:

I used the ADP base + ADP exp

used Gparted to reformat EXT3 and Linux-Swap

booted into RAV1.2.0G did a wipe

installed ADP base (update.zip)

went to market and downloaded an app

booted into RAV1.2.0G

installed ADP exp

copied my apk's to /system/sd/app & /system/sd/app-private from their respective backup locations

finished setting up e-mail, ringtones, wallpaper etc....

phone goes into the boot loop after a reboot

2nd install:

I used the TMO base + TMO exp

used Gparted to reformat EXT3 and Linux Swap

booted into RAV1.2.0G did a wipe

Installed TMO base (update.zip)

went to market and downloaded an app

booted into RAV1.2.0G

installed TMO EXP

copied my APK's (same as above)

finished setting up e-mail, ringtones, wallpaper etc....

tried to expsetup

phone goes into the boot loop after a reboot

3rd install:

back to ADP base

used Gparted removed partitions EXT3 and Linux swap, recreated partitions

RAV, WIPE

Installed ADP base

went to market and downloaded an app

RAV

installed ADP exp

booted to desktop

rebooted to RAV

Installed Hero theme for ADP

booted up

installed all my apps directly from market

setup e-mail, ringtones, wallpaper, alarms etc....

left work called wife

got home went to bed

woke up, got phone

started trying to find out how to get expsetup to install the vsapps.zip

instructions are vague, read about 50 more pages of forums

got a reply that looked promising

decided to reboot phone as a troubleshooting step before I ran expsetup

BOOT LOOP

head exploded /grin

found a new build, setup that for now

I really like what your doing with the ROMS used 1.8.4 with great results. 1.9.2 is nice, I'm not sure why I'm getting the reboots I'm doing things exactly the way I've done them all along, I've had a number of different ROMS on my phone some Hero, some cupcake.

I see that users were experiencing a similiar issue back in the end of Sept with 1.8.4, maybe it's just me... maybe more need to reboot their phones and see what happens haha....

anyway I'm not giving up,,, but for now I'm really busy at work and the 5 hours I spent is enough for now, I bought the phone EXACTLY for this reason and I'm thinking about buying a second one so I can spend more time messing with the custom roms without messing up my 'production' device :P

Thanks man ;)
[G1 Android Development] daddycat31:
Ok...everything was working fine (alot of forcecloses but not too bad)...but all of a sudden everytime I try to go to the market I get "A network error has occurred. Retry, or cancel and return to the previous screen."

Can't figure out why because I haven't downloaded any new apps today or amde any changes...I reflashed the rom and ExpPack and still nothing...I didn't wipe though (wiping is getting really annoying...lol). any suggestions or anyone experiencing this?
[G1 Android Development] SG_Shadow:
phone number parsing issue

It has absolutely nothing to do with any company forcing you to use area codes for areas that you live in. It is a glitch with the ROM, that's it. Cyanogen had the same issue with his stable rom's. Check his logs. He fixed the issue with 4.0.4 stable. You shouldn't have to enter 1 or the area code (if you live in the same area as the person you're calling). This method of dialing is archaic and I refuse to take a step back to pre-cordless phones. I still will wait for an update. I really like this blur theme.
[G1 Android Development] cyberrobin:
I have a T-Mobile G1, and just updated to the dount 1.6 ADP firmware, just because I want to try it ;)

I checked the http://db.androidspin.com/android_b...oid_developer_id=21&NumberOfReleases=10&go=go database and it said the ADP firmware will have a dutch language, but when i just installed the 1.6 firmware, I can't seem to select the dutch language?

What am i doing wrong, does the TMO has a dutch language?

edit: It also's says is has the work mail, flipclock, widget pack, etc. I don't see any of them?
[G1 Android Development] djengizz:
No there is no dutch available yet. I think enomther is working on a version that will include more languages. For now I pulled the CustomLocale.apk from the 1.6 emulator which gives you the possibility to set a custom locale (nl_NL for dutch).

Android will still be in English (or any of the other languages supported) but all the apps supporting dutch will now be in dutch (like the HTC keyboard).

To get the widget pack go to terminal, type su followed by expsetup and from there you can install the widgetpack using option 13.
[G1 Android Development] yukkio:
Enom, will you submit a new release soon? :D

Thank you.

BR.
[G1 Android Development] cyberrobin:
****. Something went wrong..

I tried to install the RA-dream-v1.2.2 recovery, I moved the img to my sdcard, rebooted into fastboot and erased the recovery. After that the fastboot would'nt find any ra-dream image on my sdcard. I rebooted back to normal mode and went into adb, in adb i went to /sdcard/ and found out it was empty. somehow it wont copy the image files to my sdcard..

copying using adb: adb push c:\recovery-RA-dream-v1.2.2.img /sdcard/recovery-RA-dream-v1.2.2.img gives the following error: 'Read-only file system'.

How will I get the recovery console back now..?

edit:

tried to format the sdcard back to normal, tried again to place the files on the sdcard, and the sdcard still seems to be empty in adb.
[G1 Android Development] olearyp:
OT: I agree that it's something with the ROM, but argue that it's not "archaic" or a "step back" to dial 10 digits. In fact, that's something quite recent, as metropolitan areas have been forced to overlay area codes. Atlanta, for instance (area codes 404, 770, and 678) has required 10-digit dialing for about 15 years or so, since there's no way for the local exchange (on a landline) to know which area code you have. There USED to be, but no more. And if we look at the history of phone numbers, even more parts used to be optional depending on the locality of the call. The telcos have only been working to make dialing more uniform, which I'm sure will culminate in 10-digit dialing for all (which I understand is how the Europeans do it anyways).

I'm used to it, as a 404 myself, but can understand if you're not used to it. But at a certain point, you are programming the number into your phone, so it's not really more work for you except initially adding the contact. Plus, if you ever moved your number to a new area code (new work phone or something?), hey, your contact list is all ready to go! :)

That said, yeah, the phone knows its own area code so it should be possible to figure it out. And I won't try to convince you that it's not ROM-swappingly bad, but I'm differently neurotic and would go crazy if my contact numbers were formatted differently from one another. If it was forbidden to dial local area codes I'd go nuts. :o

Also, I agree that the blur theme is pretty sweet. So we've got that going for us!

Sorry about the semi-rant, hope you're a good sport SG_Shadow.
[G1 Android Development] olearyp:
Possible your SD card is pooched. Try checking it in an SD card reader. Last-ditch effort would be to reformat the card, preferably with a computer.

EDIT: Probably dead, Jim. Get another SD card and see if that works any better.
[G1 Android Development] cyberrobin:
Hoping it's not dead.. will try another complete clean 1 GB card when i'm back home..

the following worked in the windows command line:

fastboot boot c:\tmp\recovery-RA-dream-v1.2.2.img

Lets see what I can try now :D

edit :

Installed recovery using adb, just reinstalled the donut rom, and now im installing the expansion without a reboot.

expansion is installing, rebooting now. I hope I dont get the black screen again. :)
[G1 Android Development] LucidREM:
Recovery Flash

did you try flashing the recovery within Terminal instead of fastboot and adb? just opening Terminal and typing:

# flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img

would normally work
[G1 Android Development] coredump777:
Erm. Aside from the number parsing nuisance, I am experiencing a new problem.

I was using 1.8.x until last night, when I decided to update from TMO 1.8.5 to the most recent ADP. I only flashed the images, no wipe or reformat of ext2 partitions. Now my phone process force closes everytime I receive a call or try to see the call log.

I suppose I should format the ext partitions and re-flash the phone, but do I need a wipe? Please, dont say yes :P
[G1 Android Development] bfreexxx:
Only One Ring?

My phone is only ringing once for incoming calls since I flashed to ADP 1.6. I did a search in this thread and it doesn't seem to come up. Is it the particular ringtone I'm using? Anybody else having this issue?
[G1 Android Development] olearyp:
Hate this for you, but TMO->ADP or vice-versa is a change between two completely different ROMs, so: Yes. Good luck.
[G1 Android Development] Land Of The Trill:
What files would I have to pull from the expansion pack and push to the base rooted build in order to have all the root benefits on the base version cause I hate how its done right now with one pack and the other build is rooted can anyone help?
[G1 Android Development] cyberrobin:
Its fixed now :) I could not get in to the terminal because the extensionpack was installed wrong and I was getting the black screen. :)

But it all is fixed and it works perfect!
[G1 Android Development] kyuhasz:
Sorry, I didn't see that I needed to repartion, there's a sea of posts. I will give this a try in the next day or two and let everyone know the outcome.

Thanks for your help!
[G1 Android Development] kyuhasz:
Ok. I'll try these steps. May be a day (or few) before I have the time, but will let you know how it turns out.

Thanks for your help.
[G1 Android Development] bmj1086:
I'm getting a FC every time I try to open Media Volume in Settings > Sound & Display. I ran ddms and here's what I got. Anybody know what it might be?