yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] vilord:
defianceX7 and others who are having trouble with the data extraction...

You don't want to extract data.gz yourself. You want to put data.gz on your card as is.

If you are seeing an error about e2fsmk not found then it means that the data image is missing, and you need to put data.gz back on your card.

----

If you are getting errors about google partner setup, then you are using a data file from 1.1, and it won't work. If you need a different data file let me know and I'll try something different, but don't try to use a 1.1 data file.
[Touch CDMA Android Development] craig0r:
I would figure that enabling GPS in Settings might just have the GPS on, but in a passive mode, becoming active when an app requests it. That was what I interpreted the little status bar icon to indicate.

I'm getting the exact same symptoms as you.

I noticed another thing. Once you get a lock in Maps, it doesn't keep the lock, and won't obtain a new lock until you close Maps and go back in. There's been two pages of posts since I left work that I haven't bothered to look at, so my apologies if I'm just repeating what other people have said.
[Touch CDMA Android Development] tatnai:
been running first dzos 1.1, then 1.5, now vilrod's ion for a week. have kept my old data.img from 1.1, but even with the 6/21 update would still get an error on startup. everything else worked fine.

downloaded today's 6/23 files (all files). ran a fresh install (fresh data.gz). I waited 30min for android to load, stuck at the same linux screen as noted above. went back to my old data.img; previously have not had a problem loading a new data.gz, just had to wait long enough. still get google partner error on startup, and some errors in the new google maps, but everything seems to work fine. don't know why I can't load this one. would like to do a fresh start, can someone walk me through how to unpack the data.gz
[Touch CDMA Android Development] grktaurus83:
Haha! I seem to have gotten myself into a pickle without intending to.

I know how easily files can be shared among builds and how hard you guys work for that. Most people don't, though, and I'm really glad you posted that so everyone has a little better understanding of it.

Basically what I was saying was the shortened one-size-fits-all response for people who are having issues upgrading. It's not that the pieced together builds are at fault (because as you said they are made to work together), it's that some people might be upgrading only a few of the files and mistakenly not upgrading the correct ones. This is especially true with new people to Android and these threads.

That advice is basically a debug tool. Instead of trying to figure out which files they might not have upgraded, having people start off from a single author's files more easily ensures that they are using a complete set of files that are up to date (especially with a big change like this and for the time that vilord's kernel is different than dzo's). This also helps distinguish between upgrade problems on the user's end, a true bug, or a hardware error.

I suggest that if you're having problems, try doing this as a sanity check. That's all.

Oh, and I didn't mean "frankenversion" as an insult~ HAHA! It's just how I refer to stuff that is taken from different sources, even when it's perfectly ok to be that way. Most of my stuff is some kind of frankenbuild. It just ocurred to me that maybe that rubbed people the wrong way~
[Touch CDMA Android Development] vilord:
From a few days ago, describing the lcd_density option:

http://osdir.com/ml/android-platform/2009-06/msg00308.html

It looks like the "correct" value for our phones would be 120, but that will not be supported by market apps etc until donut is released.

Does anyone care to try 120 to see if that looks right in maps/gmail/etc?
[Touch CDMA Android Development] grktaurus83:
Ah, awesome it's not just me. Well, that's not so awesome, but at least it's repeatable and that will help tracking down the issue.

Yea, enabling the GPS in settings should only power it up and leave it waiting for requests from other applications. I only saw the little satellite icon once I entered maps and it was trying to get a lock. So I figured that icon shows up every time it tries to get a lock or use the GPS service somehow. I only see the icon the first time I start up GPS and enter maps, and never again after that. Even after turning off GPS and turning it back on again.
[Touch CDMA Android Development] grktaurus83:
I'll try that out right now.

Edit: Nope, Gmail still overlaps.
[Touch CDMA Android Development] vilord:
That is what it will do when it is done.

Right now, the GPS chip is off all the time whether or not you turn on GPS in settings. Then when you go into an app that uses it, it will turn on and ask for a lock.

Thats all it has been tested to do. More will come, but this is why it is preliminary.
[Touch CDMA Android Development] drprince89:
I redownloaded the data.gz file a third time and it booted fine once, i will see if it stays this way.
[Touch CDMA Android Development] mssmison:
I have uploaded my files to the google code site http://code.google.com/p/vogue-android/downloads/list

I will be added them there from now on and updating here when I do. I have closed my thread. There's just too many different places to find files now :)
[Touch CDMA Android Development] katmandu421:
To clarify, we should be letting android extract data.gz into data.img the first time booting and not extracting with a 7-zip-ish utility prior to loading?

I've always extracted first, and i've also always had problems is why im asking.
[Touch CDMA Android Development] grktaurus83:
Since the setting doesn't power up the chip when you toggle it on, does it actually power off the chip when you go into settings and toggle it off? Seems like it might not, from what you're saying.

But it seems to be doing _something_ since we can't seem to connect again afterwars.
[Touch CDMA Android Development] vilord:
That is correct. Just put data.gz onto the root of your card, the initrd will do the rest (it will extract it, change it to data.img, etc)
[Touch CDMA Android Development] nuttsak:
Is there any chance of porting the HTC Hero ROM to the Vogue? It looks like there is a ROM out there now for the G1...

http://xdaforums.com/showthread.php?t=521059
[Touch CDMA Android Development] drprince89:
that rom is now on the google code site for this project, im curious as to whether we can use it.
[Touch CDMA Android Development] grktaurus83:
Awesome!

I'm glad it's all getting consolidated, though I know it's always sad to see your own thread/site go away. *sigh*

Edit: Your systemionhero1.img is only 14.7kb. Is that right or did it upload improperly?
[Touch CDMA Android Development] vilord:
I'm pretty sure what's happening is that the option in the control panel just allows access to the chip, and the chip isn't being turned on until maps asks for a fix.

Then when maps stops asking, it turns the chip back off, then when it asks again it tries to turn the chip back on.

If you remember, the chip was always a little wonky about suspend/sleep modes even with a full driver in windows
[Touch CDMA Android Development] nuttsak:
The couple ones that I've seen and used just have cosmetic changes to the home screen, not REAL Hero ROM

So the 3 img are REAL Hero ROM not themed?
[Touch CDMA Android Development] mssmison:
:) Nah I'm a team person. Vilord and I talk ALOT about this project, throwing out ideas, trying and failing :) I'm happy him and srwalter have come on board to help get things going. With us 5 major dev's alot of work has gotten done. I know it's been said before but we all owe DZO a paypal beer :)
[Touch CDMA Android Development] katmandu421:
Thats gotta be wrong. Most images are clocking in at around 41M
[Touch CDMA Android Development] mssmison:
No. I'm not done my hero rom, I have it partially working but it's not near ready for release ;) stay tuned for that. It's alot of work so it's taking some time. The ones I've posted are themed ion builds with 'some' files from the hero build thrown in to speed it up.
[Touch CDMA Android Development] mssmison:
yeah, whoops :)
[Touch CDMA Android Development] katmandu421:
Amen!!!!!!!!
[Touch CDMA Android Development] nuttsak:
The Hero is the way to go, I don't see any other version being worth sh*t compared to the Hero. That would be SWEEEEET to have the Hero working!!!
[Touch CDMA Android Development] drprince89:
so are the ones that were uploaded recommended for use over the current one?
[Touch CDMA Android Development] mssmison:
? They are different. It's your preference. Give em a shot you might like them. I've said it before, I've been using Android a while and am bored of the generic theme so that's why these ones.
[Touch CDMA Android Development] grktaurus83:
You should bring back your screenshots of the different themes so people can take a look. Have vilord post them on the OP.

And don't forget to fix the hero1 image~ Haha!
[Touch CDMA Android Development] drprince89:
would the gps work with yours or is that coded into the system.img? i put up your image but i cant get the gps to work.
[Touch CDMA Android Development] mburris:
putting autobackup into boot process

Jesse,

Thanks for all the work you've done so far... with a slight change to the code in the setupmodem.sh file inside the initrd.gz your ION build is astoundingly stable and fast on the Kaiser.

I had an idea, and I wanted to run it by you, since you are very good at making changes to the initrd script.

Would it be possible to make a part in the init where it would make a backup of the existing data.img file if the user pressed a key when prompted

here is an outline of my idea:

If folder "SDCARD/Backup" exists, then
echo Press Any key to backup your existing data file
while x < 3
if keyPressDetected then
gzip sdcard/data.img sdcard/data.img_%year%_%month%_%day%_%time%.zip
end if
x = x+1
wait 1
loop
end if

basically, if it detects the presence of a "Backup" folder on the SDcard, it will prompt the user to press any key to make a backup of the data file. It could then start a # second loop... if the user presses any key during that time it will create a compressed copy of the archive.
[Touch CDMA Android Development] vilord:
That is a great idea! I'll look into that tonight :)

What is the change needed for kaiser? I might be able to make it so you don't have to keep repacking
[Touch CDMA Android Development] mssmison:
Vilord and I were just talking about that. No gps yet. I'll update the builds asap with gps support...**EDIT** k gps updated builds are on the way.
[Touch CDMA Android Development] srwalter:
By "popular demand" I've added a paypal button to my download page for the GPS builds:

http://dasbrennen.isa-geek.org/~srwalter/gps/

Most people will probably want to continue downloading vilord's build for general use, however. Glad the code is working for so many people (better than I expected, really!) I hope to get things a little more rounded out in the next day or two.
[Touch CDMA Android Development] mburris:
ok the diff for making the Kaiser modem work is this:

--- orig/initrd15/setupmodem.sh
+++ new/initrd15/setupmodem.sh
@@ -34,12 +34,6 @@
if [ "$CMD" = "on" ]; then
if [ ! -e /etc/ppp/ppp-gprs.pid ] ; then
modem_log "Starting pppd..."
-	if [ -e /sys/class/vogue_hw/gsmphone ] ; then
- /bin/echo -e "AT+CGDCONT=1,\"IP\",\"$APN\",,0,0\r" > /dev/smd0
- /bin/sleep 2
- /bin/echo -e "ATD*99***1#\r" > /dev/smd0
- /bin/sleep 4
- fi
/bin/pppd /dev/smd1
if [ ! -e /etc/ppp/ppp-gprs.pid ] ; then
modem_log "Connection attempt FAILED!"

and here is some code i threw together for the autobackup thing (untested):

#!/bin/bash
# adapted from Stephane Chazelas by Matt Burris
INTERVAL=3 # timeout interval
timedout_read() {
timeout=$1
varname=$2
old_tty_settings=`stty -g`
stty -icanon min 0 time ${timeout}0
eval read $varname # or just read $varname
stty "$old_tty_settings"
# See man page for "stty".
}

echo; echo -n "hit any key to backup data.img"
timedout_read $INTERVAL detect_keypress
echo
if [ ! -z "$detect_keypress" ] # If input before timeout...
then
file=data.img
gzip $file ${file}`date +%Y%m%d`
fi

only part im not too sure about is the actual zipping part: "gzip $file ${file}`date +%Y%m%d`"
[Touch CDMA Android Development] mburris:
Thank you for the GPS code... I know it will eventually find its way to the kaiser, so here's $10!
[Touch CDMA Android Development] tatnai:
quick bug report: when a phone call is coming in, the only way to silence the ringer or the vibrator is to answer the call; currently no button/action will stop the ring without answering the call
[Touch CDMA Android Development] jaredakelly:
still having problems with the lcd density. i put this in the default.txt right after the internet login and password as requested:

"lcd.density=128"

and all it does is have the android boot graphic endlessly. any help?
[Touch CDMA Android Development] vilord:
Press the camera button, then press volume down, it will silence the incoming call. Some day we'll implement end-key-to-voicemail like everyone else has I hope
[Touch CDMA Android Development] njakobs:
I had a similar problem, putting the "lcd.density=128" as the last item in the set cmdline made it work for me.
[Touch CDMA Android Development] vilord:
you have to skip the quotes, i hope... it is just like the other options in there...
[Touch CDMA Android Development] jaredakelly:
like this?:

".....pm.sleep_mode=0 board-htcvogue.panel_type=1 no_console_suspend lcd.density=128" boot

sorry, its just still not working
[Touch CDMA Android Development] njakobs:
Yeah just like that. Only difference is the I am using 120 not 128.
[Touch CDMA Android Development] jaredakelly:
dang dude still doesnt work.....
[Touch CDMA Android Development] mfpreach:
On a different question, is there a way to have the whole touch screen working properly, I noticed about 1mm down the left hand side it doesn't quite work or is very non-sensitive, i'm assuming this is because of the diff dimensions of the g1 itself. Can you throw something in the default.txt to fix this?

Also, not to jump the gun but is anyone working on bluetooth support?
[Touch CDMA Android Development] grktaurus83:
Something I think we should do is create a list of everything that needs to be worked on (like a wiki?). I think we need this for a few reasons:

1) We keep finding little things that need to be taken care of eventually, but they get lost among the more important stuff

2) Some people would love to contribute but they have no idea what needs to be done

Basically, I mean something like this:

Bluetooth

> Implement support for bluetooth

Calculator App

> Round off errors (Try 55.12-55.11 and you'll see what I mean... this was something that people ridiculed Microsoft for back in Windows 3.1 and it's making a come back it seems~ haha!)

Camera

> Improved camera support

> Better overlay display

GPS

> aGPS support

> Improvements on GPS in general

Messaging App

> Proper handling of text-to-email or email-to-text

Phone Calls

> Full call waiting support (currently missing support to switch back to original call)

> 3-way calling

> Speakerphone

> Implement end-key-to-silence

Power Collapse

> More elegant waking up (instead of the brief flash of static/white screen)

SD Card

> USB non-adb mass storage access through Windows/Linux/Mac

Touch Screen

> Touch screen sensitivity and jitter

This isn't to say that all of these things need to be worked on now or that they will even be done anytime soon, it just helps to know what exactly needs to get done. One example from above is the calculator app issue since I don't think anyone had realized that one yet. I think it just helps to write these things down.

We could even list who is currently making progress on certain topics and link to their paypals~

I figure this might be a bit much at the moment, but what do you guys think?
[Touch CDMA Android Development] prairiefire:
Donated $10. Cheers. Have a nice cold beer!
[Touch CDMA Android Development] vilord:
take a look up on the google code site, new initrd, and new zImage with some GPS updates.

The new initrd will create a new data.img for you if you don't have one, so you don't need data.gz anymore (so no more errors with extracting data.gz)
[Touch CDMA Android Development] Snakehn:
quick question..

i am trying to give this a try, MicroSD is formatted FAT32, i put the latest files on the root of the card and run haret.exe, then run, it tries to boot, but then i get the message of "couldn't find a partition in SD card"?

i tried to reformat the card but didn't read about creating a partition or something like that in the first page.
[Touch CDMA Android Development] vilord:
you are using an Vogue/cdma touch/xv6900, right?
[Touch CDMA Android Development] Snakehn:
Yes, a Verizon XV6900 with WM6.5
[Touch CDMA Android Development] mburris:
OK so I decided to write the autobackup code...

I have it working on my laptop in terminal but it won't work on the phone.

Its like it doesn't detect that i'm pressing the uparrow. Here is my code:

#android autobackup by Mburris
if [ -e /sdcard/backup ] ; then
echo "Backup folder found on SDCard"
if [ -e /sdcard/data.img ] ; then
echo "data.img file found"
TIMELIMIT=3 # 4 seconds
uparrow=$'\x1b[A'
read -t$TIMELIMIT -s -n3 -p "hit up arrow to backup data.img" keypress
case "$keypress" in
$uparrow)
echo "Creating Backup"
file=data.img
tar cvzf /sdcard/backup/${file}_`date +%Y_%m_%d_%H%M`.tar.gz /sdcard/data.img
;;
esac
fi
else
echo "no backup folder found on SDCARD, skipping autobackup option"
fi

and here is a diff for your latest (i think) init file

--- initrd15/init
+++ initrd15.autoback/init
@@ -75,6 +75,25 @@
fi

if [ $PARTITIONED = "0" ] ; then
+	#android autobackup by Mburris
+	if [ -e /sdcard/backup ] ; then
+	echo "Backup folder found on SDCard"
+	if [ -e /sdcard/data.img ] ; then
+	echo "data.img file found"
+	TIMELIMIT=3 # 4 seconds
+	uparrow=$'\x1b[A'
+	read -t$TIMELIMIT -s -n3 -p "hit up arrow to backup data.img" keypress
+	case "$keypress" in
+	$uparrow)
+	echo "Creating Backup"
+	file=data.img
+	tar cvzf /sdcard/backup/${file}_`date +%Y_%m_%d_%H%M`.tar.gz /sdcard/data.img
+	;;
+	esac
+	fi
+	else
+	echo "no backup folder found on SDCARD, skipping autobackup option"
+	fi
losetup /dev/block/loop0 /sdcard/data.img
[ $? -eq 0 ] || fail "Failed to find data.img on SD Card"
/bin/e2fsck -y /dev/block/loop0

What am I doing wrong? Can android not listen for inputs while going through the init script?
[Touch CDMA Android Development] vilord:
Well, I'm not sure why it might not be working... I didn't fully read through your code, but I did actually already create something that should be working... Sorry I thought you would've seen my message in the kaiser forum. In any case, here it is:

read -s -n1 -p "Press any key to start an automatic backup" -t 5
if [ "$?" == "0" ] ; then
echo "Starting Backup..."
if [ ! -d /sdcard/backup ] ; then
mkdir /sdcard/backup
fi
gzip -vc /sdcard/data.img > /sdcard/backup/data$(date +%Y-%m-%d).gz
echo "...Done!"
fi
[Touch CDMA Android Development] tatnai:
i use 128 works just fine
[Touch CDMA Android Development] dragonxyz:
Cannot write to SD

For some reason, I can only extract data.gz using a pre 1.1 zImage. The latest kernel would just hang.

After messing around with it most of the day. It turns out the Google Partner Setup error I'm getting is related to an unclean ext2 filesystem for /sdcard. After rebooting it's mounting as read only. e2fsck is supposed to catch this during bootup [maybe because I'm using an older kernel? Then again I have no choice since the latest one won't work] :(

I've tried to unmount /sdcard (/dev/block/mmcblk0p1 on my setup) to force fsck on it but no luck.

Not sure if there's a workaround so I'll start fresh again, install all the apps, and try not to reboot...
[Touch CDMA Android Development] margosmark:
Are you sure its hanging, just leave it alone for a bit let it extract file. On mine it took some time this ... time, so leave it for like 10 min (dont think it took that long) then it will continue to boot.
[Touch CDMA Android Development] tatnai:
oh its a hang alright. i've extracted them fine before using initrd at startup, can take like 7min. i left mine alone for 30 min, was still stuck - it should not take that long.

will try new initrd see if it will create one - thx vilrod.
[Touch CDMA Android Development] katmandu421:
I just found out yesterday that we should let the system unrar the data.gz and was hoping that it would fix my "home screen return" hang I've been experiencing. This is prior to vilord posting the "no data.gz required" init I saw earlier this morning. Mine took over 30 minutes to extract, the screen even wen blank and I messed up the first time by hitting the power button to see if it was booting android yet. It put a character on the command line, so I killed it and started fresh. It did take a LOT of time, but it eventrually extracted and booted.

On another note, I noticed someone else had an issue with maybe having an ext2 partition on their card. I created one a few weeks back when I was attempting the apps2sd mod. Should I reformat this out? Could this possibly be causing my home screen hang issue, which btw was not resolved with a fresh, system-extracted data.img like I had hoped.
[Touch CDMA Android Development] tatnai:
new initrd with no data.gz required works like a charm. gps improved, i can open maps now multiple times and still get a gps lock, stays locked now too instead of being intermittent as it previously was. also, getting rid of my old data.img has made the system faster and gotten rid of all the errors i had. working smooth now, you guys are super with all the updates, i would say we are getting closer and closer to having a fully operational android. using this full time now.