Fixes:

• Comcast fails to download more than 1 email
  • Symptom(s): No error message but it stays on “Load More Messages” without ever pulling another email.
• “Messages” Stability Issue
  • Symptom(s): When trying to send a message or exit the “Messaging” application you receive a pop up message that reads “Sorry! Activity Messaging (in application Messaging) is not responding. Force Close Wait”
• WiFi forcing a logout of IM
  • Symptom(s): While using the IM clients on the G1 if you turn on or off WiFi the sessions are terminated and you will need to sign back in.
• No reminders for calendar items.
  • Symptom(s): Missing appointments due to the lack of a reminder.
• G1 hanging at the G1 Screen
  • Symptom(s): A small number of G1 devices hanging at the G1 screen during the initial power up

New Features:

• Support “Check For Upgrades” (New feature to check for system upgrades)
• Voice Search (New Google feature for searching)
• Ability to save pictures recieved as MMS
• Ability to report offensive comments in the Market as SPAM

Related posts

• How to Downgrade your G1 to get Root. (0)
• T-Mobile G1 Nand Flash Dumped! (0)
• Haykuro releases Rodgers Android Rom before Rogers (0)
• WebNetta Interview: Seth Lemons a contributor to the “Wifi Tether for Root Users” app. (0)
• Tutorial: T-Mobile G1 RC30 to JFv1.31 (How to Root a Retail G1) (24)

Stuck Zune

I know it doesn’t run Android, but I happen to have one of these little buggers. And yes, as you can see above, its stuck. Apparently there is some bug with the clock code, I’m guessing the hardware clock runs with a GMT timezone setting. A forum suggested taking the Zune apart (This voids the warranty kids, aw hell we do it all the time… ) and unplugging the battery to reset it. For a bit this seemed to work until the Zune was rebooted.

This did NOT work, not permanently, anyway.  Initially all was well, but then I connected it to my computer to charge and sync with the software.  It almost immediately reset and is frozen again at the logo page.  No doubt I could unfreeze it again, but what’s the point if it’s just going to mess up again when I reconnect it?

So this morning Microsoft came up with a fix, here are the steps:

1. Let the battery die, for me it’s going to be awhile mine was fully charged.
2. Wait until after noon GMT on January 1, 2009 (that’s 7 a.m. Eastern or 4 a.m. Pacific time).
3. Connect your Zune to either a USB port on the back or your computer or to AC power using the Zune AC Adapter and let it charge.

And Presto! A working Zune. We shall see.

UPDATE: Once the battery in my Zune charged and it rebooted all is well.

Related posts

• No related posts.

The first thing we thought of, was making the T-Mobile G1 send the audio to an iPod Speaker set we have.

There is a sea of iPod accessories, so naturally the dock connector has a well known pinout.

Figuring out the pinout for the HTC ExtUSB connector wasn’t too hard, I just split open my hands free adapter I got with my T-Mobile Dash.

Most of the wires were labeled, “L” “R” “M” ect. It took a bit of fiddling to discover that connecting pin 7 to the audio ground ( pin 8 ) turns on the external audio. Sparkfun sells 30 awg (Gauge) wire wrap wire that is perfect for soldering to the ultra tiny pins on both the HTC ExtUSB connector and the iPod Female connector.

We used pins 1, 2, 3, 4, 16, and 23 on the iPod Female connector. If you gently bend the pins out it makes it much easier to solder, but be careful the pins break easy.

1 & 2 are Ground -
3 is Right Audio +
4 is Left Audio +
16 is USB Ground -
23 is USB Power +5

It is important that you do not mix the audio and power grounds or you can get a nasty hum.

On the G1 side of things the upper half of the connector is a standard mini-usb pinout, the bottom is very different.

We used Pins 1, 5, 6, 7, 8, and 10.

1 is USB Power +5v in

5 is USB Ground -

6 is Left Audio +

7 is marked “AG” on the T-Mobile Dash headset board, connect this one to pin 8 to enable audio.

8 is Audio Ground -

10 is Right Audio +

Now we wire the two connectors together like so:
iPod pin – HTC ExtUSB pin

1 ———— 8

3 ———— 10

4 ———— 6

16 ———— 5

23 ———— 1

Don’t forget to solder together pins 1 & 2 on the iPod side and pins 7 & 8 on the G1 side.

When its done it looks like this:

So we have audio from Audio player and YouTube, and the speaker dock charges the G1 too.

Have fun!

Related posts

• No related posts.

Related posts

• T-Mobile G1 Nand Flash Dumped! (0)
• WebNetta Interview: Seth Lemons a contributor to the “Wifi Tether for Root Users” app. (0)
• Rooted RC33 Posted, JFv1.41 *Updated* (0)
• How to Downgrade your G1 to get Root. (0)
• Haykuro releases Rodgers Android Rom before Rogers (0)

<Eddie C. Dost>
now it is clear why we do not see the full nand device. If the
msm_nand driver registers partitions, it will not register the
device itself, so we cannot access this as char device.
Could you compile a kernel where you remove the two lines containing
the word “else” in drivers/mtd/devices/msm_nand.c, lines 1237 and 1263?
With this the msm_nand.c driver will register the whole device as
7th device after the 6 partions. A dump of the partitions is not really
interesting, as we know what is on there. Maybe you can also change
line 72 in drivers/mtd/mtdcore.c from DEBUG(0, “mtd:…”) to
printk(”mtd:…”);

Once you have this, and the kernel is booted you should see seven
nand devices registered in the kernel boot log you get with “dmesg”.

Now, please create the device nodes for the 7ths nand:
mknod /dev/mtd/mtd6 c 90 12
mknod /dev/mtd/mtd6ro c 90 13
Then you should be able to dump the nand image before the partitions
used by linux:
dd if=/dev/mtd/mtd6ro of=<path to dump> bs=2048 count=18944
which should produce around 38797312 bytes of data. This data is the
start of the nand interesting to analyze and the “misc” partition, to
verify we have it dumped correctly.

<Jay Freeman>

That got exactly the expected amount of data: 38797312 bytes. More
importantly:

# strings mtd6ro | head -n 3
0.95.0000
Dream SPL EVT
Shipped

This is followed by a bunch of ARM code. Congratulations, you won! ;P

(By the way, I find this sort of thing both really fun and really important,
so don’t think you’re taking up my time: I’m thankful you are also working
on G1 hacks. I only didn’t respond to the e-mail asking me to try out the
other nand dumper because today was too busy, still recovering from
Thanksgiving break.)

For people who have root’d G1’s, get this boot.img (which is compatible with
my previous ones, but has a slightly updated Bluetooth driver Google
committed and Eddie’s MTD hack):
http://test.saurik.com/g1-hackers/boot-mtd.img. I’ll have this hack in my
next update image as well (as it seems completely harmless: it just
activates more devices).

You can install this with “flash_image boot boot-mtd.img”, after which you
should reboot. (It also has all my other standard modifications to mount and
init, so you can use this and keep using whatever cool stuff you have setup,
although note I removed “include” from init and corrected it to using
“import”, although I doubt many are using that.)

Past that, you should use Eddie’s dd command (you don’t need to make the
device nodes, as init does this for us: it has a udev-alike in it).

dd if=/dev/mtd/mtd6ro of=<path to dump> bs=2048 count=18944

UPDATE:

Nand Dump file here http://www.2shared.com/file/4394944/b791a62e/nand.html

Related posts

• Rooted RC33 Posted, JFv1.41 *Updated* (0)
• How to Downgrade your G1 to get Root. (0)
• G1 USB Connector (0)
• WebNetta Interview: Seth Lemons a contributor to the “Wifi Tether for Root Users” app. (0)
• Haykuro releases Rodgers Android Rom before Rogers (0)