yashsingh1/xdaforums huggingface dataset:
[Touch CDMA Android Development] dzo:
You just need to change the initrd to mount your root filesystem, then switch_root and run init. At the moment the initrd contains the rootfs and a script (init) that mounts /data and /system and then runs the android init (init1).
[Touch CDMA Android Development] ducamie:
i dont have a vogue (ive got a nike) so i cant even check out all dzo's neat work. but i view this thread regularly just because it interests me. props, dzo. very very impressive. i can only pray for someone with your knowledge port it for the nike one day.
[Touch CDMA Android Development] unsungboxer:
A. You can try my modified data.img file from post #567 or...

B. You can download apps and add them your own. Let me explain:

0. You must start with a Linux box (I use Ubuntu Hardy Heron)

1. Download desired app (try www.android-freeware.org), .apk format

2. Copy data.img from your android install and place it on Linux desktop.

3. Open Terminal and become root user:

sudo -s (enter password)

4. create a mountable folder:

sudo mkdir /mnt/data

5. change directory to data.img file:

cd Desktop

6. Mount the data.img filesystem:

sudo mount -o loop data.img /mnt/data

7. Navigate the directory as root user:

sudo nautilus

8. Hit "up directory" button, and navigate to /mnt/data

9. Place desired files into data/apps

10. Unmount the drive when done:

umount /mnt/data

11. place data.img back in your android directory and run Haret.

(notice it is still 128mb when done)

Explanation:

Essentially this data.img is an ext (linux) file system that android accesses (like a disk). By mounting data.img from your Linux computer, you are able to view the file system (lots of subfolders and system files. You will find your wallpaper here too). By using sudo nautilus you are able to make changes to the file system (like add apps). Unmounting the file will allow you to copy it back to your Vogue/Touch/xv6900 memory card. Please note as stated above by Martin, that not all of these apps will work (due to changes in android). If you have no clue what I am talking about just try my data.img and wait for Martin's updates as they come :)

-Jake
[Touch CDMA Android Development] jakobnord:
Hi,

i tried to download and transfer the files from dzo's website to my HTC ELFin (i guess thats the one?), but when i try to run Android through HaRET, it just goes into a white screen, and after a few second i just press the On/Off button and i am back in WM.

Is it not possible to find just one explaination of how to make android work on a HTC Touch?

Modelnr.: ELF0100

CPU: OMAP850

RAM: 128

ROM: 256
[Touch CDMA Android Development] uiucryan:
If you have a look at http://en.wikipedia.org/wiki/HTC_Touch you can see some of the differences between the ELF and the VOGUE. The port that DZO has made is for the VOGUE. The ELF is not currently supported.

--Ryan
[Touch CDMA Android Development] ryanthered:
I'm getting an error that the SD card can't be found. Looks like it is looking for a specific name "SDCard" but mine is named "Storage Card". I tried renaming the card in Explorer, but I can't seem to change the value. Any clues?
[Touch CDMA Android Development] unsungboxer:
make sure all files are in top most directory of sdcard

do not rename storage card

sd cards 2gb and under work only. no support for larger sdhc cards yet

if all above are right just try it again. I notice I get this error once in a while too. seems to be random
[Touch CDMA Android Development] bedoig:
I'm running it on my Titan from a 6GB SDHC.
[Touch CDMA Android Development] uiucryan:
I updated the androidgeeks.net wiki with a few elements:

HandingCPIOBalls - this page is dedicated to dealing with CPIO Balls (like initrd-android)

MountingFileSystemImages - this is dedicated to mounting File System Images (like data.img and system.img)

I also updated HTCTitanPort and HTCVoguePort to mention the alleged 2GB SD limitation.

What other information would you guys like to see posted on the wiki?

Please have a look, please register, and please update:)
[Touch CDMA Android Development] natelust:
applications

I am wondering who has had luck adding applications. I have tried to add apps such as xlive which i believe was listed as working, however I still do not get it showing up in my applications list. Is there something else I should be going with the .apk
[Touch CDMA Android Development] etiger13:
I posted this question on myhtcphone ( http://www.myhtcphone.com/development/12-programming/11-getting-a-sdhc-card-to-work ) to try and get some more help for Martin on the SDHC card working:

Hopefully this can help somewhat.
[Touch CDMA Android Development] WnG88:
Dzo, will you be posting the nbh to your site?

Also, anyone know how to access the Vogue forums through the xda app, it no longer appears on the forum list.
[Touch CDMA Android Development] dzo:
OK, Done...
[Touch CDMA Android Development] Does_It_Matter:
the 10-08-10 posted above by user and 10-9-10 posted by dzo

both of them make the device show as USB 1.1 in Windows

With the 10-4-10 NBH from the droid site - no issues with USB

----------------

Edit: Just verified - flashed back to the 10-4-10 NBH instead of 10/8 and 10/9 NBH

USB is recognized as high-speed and has no issues connecting to Windows

----------------

Another Edit: 10-4-10 NBH and Rls 16 Froyo 2.2.1 - Make a call, end call -

Phone reboots on its own once you hit end key

Its not a bug - its a feature right? Fresh boot after you end each call? :D
[Touch CDMA Android Development] samjam:
Please could you post a link to this "droid site" and it's 10-4-10.

I normally get mine from http://it029000.massey.ac.nz/vogue/files/

Thanks
[Touch CDMA Android Development] Does_It_Matter:
http://androidhtc.git.sourceforge.n...it;h=f0af7837ce8946716841ccbfdd03019dd4d9cb07

Looks like its L1Q1D that is compiling them?
[Touch CDMA Android Development] alexinc:
future doesnt look so bright for polaris-owners... with l1q1ds kernel 10-10-10 wlan and cam still aren't working. :(
[Touch CDMA Android Development] l1q1d:
Any help is welcome so use your skills or shut up!
[Touch CDMA Android Development] alexinc:
at least i'm testing and letting other polaris-users know to confirm or not, if they face the same issues. more i cannot offer with my "linux-knowledge". if thats not appreciated anymore, i'll "shut up"!
[Touch CDMA Android Development] l1q1d:
I'm testing now the wlan for polaris. I just finished with nand.

Now after reset fs seems working.
[Touch CDMA Android Development] SuperJMN:
Alexinc, could you please check this thread for my little homemade fix? :) It's based on a mix of files that will help you with WLAN and CompCache (it really improves the memory available).

Here is thread: http://xdaforums.com/showthread.php?p=8550751#post8550751
[Touch CDMA Android Development] l1q1d:
Perfect...
[Touch CDMA Android Development] alexinc:
will do so asap. compcache works right out of the box with fresh froyo and 10-10-10 kernel (when enabled in terminal).

btw. my last tries with making facebook-sync working on our froyo failed miserably!!! tried everything from changing lines in build.prop, moving files between different froyo releases (with cm it works) and so on. no success. so far my efforts with linux, helping out here and there... i always did my best, but when it comes to bits and bytes i'm really no big help, but always tried and mostly succeeded when it came to win/win mobile. but thats offtopic! no reason for "shutting up"...
[Touch CDMA Android Development] samjam:
Yes, I had a hang-on-bootup-with-charger-plugged-in requiring a reset and GOOD NEWS although I got a load of yaffsw "block not erased" messages (as expected) it recovered fine with no problems.

Thanks for fixing nand!
[Touch CDMA Android Development] l1q1d:
Probably there is a big problem on ril. The hangs problem appears only when sim card is in use. We need to fix as soon as possible.
[Touch CDMA Android Development] samjam:
l1q1d, your nbh here:

http://androidhtc.git.sourceforge.n...it;h=28b1ebe36ce9f8090a825727b4876f1d69d3fcdf

seems to fix the keyboard LED problems nicely, thanks.

Sam
[Touch CDMA Android Development] n2rjt:
Kernel crash in video driver

I have had several crashes where the screen freezes, usually after I have pressed a key, like the back key. The /proc/last_kmsg always ends with logs like the attached. I have a kaiser (AT&T Tilt).

I'm trying to learn how to analyze these logs. I'm not sure, but it seems that from within msm_isr(), the PC becomes 0 which is not a happy thought.

When I look in msm_isr() I see two function pointers being used:

dma_callback->func(), and ppp_callback->func().

The ppp_callback never gets set, so I focus on the dma_callback. I see in the msm_fb.c file where dma_callback gets set, but I don't see where func would be zero. So the best I can come up with is prevention of the symptom, which seems like the wrong approach. In msm_isr() I want to say "if (dma_callback && dma_callback->func)" and set dma_callback = 0 outside the if.

So, is my analysis correct? If so, how does the dma_callback->func get set to zero?

I will report back if my change to the if statement seems to prevent the problem. I'm not hopeful.
[Touch CDMA Android Development] dzo:
dma_callback is set to msmfb_handle_dma_interrupt in msm_fb.c but I don't think that's the problem. What probably happens is that the mdp clock isn't enabled when the interrupt code tries to read from the status register. You can see exactly where it has crashed using:

arm-eabi-objdump -d drivers/video/msm/mdp.o | less

which gives.....

0000029c <mdp_isr>:

29c: e92d4070 push {r4, r5, r6, lr}

2a0: e10f5000 mrs r5, CPSR

2a4: f10c0080 cpsid i

2a8: e1a0200d mov r2, sp

2ac: e3c23d7f bic r3, r2, #8128 ; 0x1fc0

2b0: e3c3303f bic r3, r3, #63 ; 0x3f

2b4: e5932004 ldr r2, [r3, #4]

2b8: e2822001 add r2, r2, #1 ; 0x1

2bc: e5832004 str r2, [r3, #4]

2c0: e59f20e4 ldr r2, [pc, #228] ; 3ac <mdp_isr+0x110>

2c4: e59f60e4 ldr r6, [pc, #228] ; 3b0 <mdp_isr+0x114>

2c8: e5923024 ldr r3, [r2, #36]

2cc: e5964004 ldr r4, [r6, #4]

2d0: e5823028 str r3, [r2, #40]

2d4: e0034004 and r4, r3, r4

2d8: e3140004 tst r4, #4 ; 0x4

2dc: 0a00000c beq 314 <mdp_isr+0x78>

2e0: e5963008 ldr r3, [r6, #8]

2e4: e3530000 cmp r3, #0 ; 0x0

2e8: 0a000004 beq 300 <mdp_isr+0x64>

2ec: e1a00003 mov r0, r3

2f0: e1a0e00f mov lr, pc

2f4: e593f000 ldr pc, [r3]

2f8: e3a03000 mov r3, #0 ; 0x0

2fc: e5863008 str r3, [r6, #8]

The PC is at mdp_isr+0x34, which is 0x2d0 but the current instruction will be PC-8 which is where it does:

ldr r3, [r2, #36]

which is this line in mdp.c:

status = readl(MDP_INTR_STATUS);

r2 is the MDP base address and this is correct (0xe0010000) so the only thing that can be wrong is that reads from this address are not allowed.

Try adding a udelay after the clk_enable, or comment out the clk_disable line to see if that fixes it.

Hope this helps to understand the crash dump.
[Touch CDMA Android Development] samjam:
Spoke too soon!

If the keyboard LED's come on from non-keypress triggers - like an alarm going off (there are others, but I haven't been able to tell what they are yet) then they don't go out again but stay on.
[Touch CDMA Android Development] n2rjt:
Thank you! I do embedded ARM development at work, but with a different OS and toolchain. I was looking for objdump but with a different name.

It is interesting that in the kmsg the dump of R2 shows all asterisks.

I will try following your suggestion.

EDIT: I put in udelay after clk_enable, and today I had a new kind of freeze. screen was black, no LEDs flashing at all, unresponsive, no adb connect; yet the keypad backlight turned on and off when I pulled the keyboard out and pushed it in. Like everything was dead except (some) IRQs.

The last screenful of last_kmsg is:

[18423.668487] set sdcc vdd to 0

[18423.669219] RTC Suspend: Current time=1:47:28

[18423.670135] Wake up in 59 seconds

[18423.670135] msm_pm_collapse(): returned 1

[18423.670135] timer restore 0 0 val=40196 vtime=603723511 sleep_time=0

[18423.670135] timer restore 1 0 val=0 vtime=0 sleep_time=0

[18423.670288] Modem Status:

[18423.670379] <SM 00000929 00010929>

[18423.670410] Modem Status:

[18423.670501] <SM 00000929 00010929>

[18423.670684] RTC Resume: Current time=1:47:38

[18423.671020] Slept for 10 seconds

[18423.671264] msmrtc_resume: alarm=1287020907, now=1287020858

[18423.671783] set sdcc vdd to 16

[18423.739044] clk_set_rate 21:144000

[18423.741027] set sd clock - 0 20001

[18424.269287] clk_set_rate 21:32000000

[18424.271240] set sd clock - 0 20001

[18424.276123] wakeup wake lock: mmc_delayed_work

[18424.347198] PM: Finishing wakeup.

[18424.349975] Restarting tasks ... done.

[18424.367950] suspend: exit suspend, ret = 0 (2010-10-14 01:47:39.590820312 UTC)

[18424.378051] ds2746: 3742mV -675mA charge: 70% (1525/2160 units, 2107 adjusted)

[18424.378082] aux0: 212 (1155) aux1: 55 (276)

[18424.489349] PM: Syncing filesystems ... done.

[18424.569396] PM: Preparing system for mem sleep

[18424.772369] Freezing user space processes ... (elapsed 0.01 seconds) done.

[18424.789520] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.

[18424.798065] PM: Entering mem sleep

[18424.800781] Suspending console(s) (use no_console_suspend to debug)
[Touch CDMA Android Development] mikethemaster123:
rom?

is there going to be a rom so i don't hav ta boot it from win mob?
[Touch CDMA Android Development] mrkite38:
Look in the fresh froyo thread.
[Touch CDMA Android Development] n2rjt:
Panel type

Is there any reason why the panel_type detection code in board_htcvogue.c can't also be used for the other phones? I tried it in board_htckaiser.c, and it detects panel type 2, the same type I have been using. I've always wondered if I really have a 2 or 3.
[Touch CDMA Android Development] l1q1d:
Submit your changes on git, i'll test it on kaiser screen 3 and i'll port it to polaris.

We need to solve also the hang problem :-(
[Touch CDMA Android Development] n2rjt:
Can do, but I am doubting it now. I have used type 2 since May or June, but I just now tried 3 and it wakes up so much more smoothly. Maybe it just always reports both registers as zero, which is type 2. How about this; I will commit the change but #if 0 disabled. If your panel3 kaiser says 2 its not good.
[Touch CDMA Android Development] l1q1d:
i'm testing but seems promising.
[Touch CDMA Android Development] samjam:
Same here. I settled on 2 cos although 3 seemed faster it hung more often.
[Touch CDMA Android Development] endersm:
usb tether

I just built from git and tested the USB tethering on my Vogue. It works like a champ! I'm posting this right now over usb...

Thank y'all so, so, so, so, so much for making this happen, my phone is useful again!!!

dzo = martin, yes? if so, do you have an amazon wish list or something? gotta support the devs.
[Touch CDMA Android Development] mrkite38:
He's got a donate link, there's also a 'thank you' thread stickied in this forum.
[Touch CDMA Android Development] dzo:
Thanks, that's good to know, Windows or Linux? I know rndis works under Linux but I didn't think it was working for Windows yet.
[Touch CDMA Android Development] tiagoclc:
Kernel Issue

New kernel from

http://androidhtc.git.sourceforge.n...ee08e753d465709ffa7a7ce1a091db0a37c6d;hb=HEAD

(10-19-2010 version)

Reduces kaiser's performance.

162 points using Quadrant, below Magic.

Downgrade to 10-12-2010 version :(
[Touch CDMA Android Development] samjam:
Seems much more snappy to me than the previous one.
[Touch CDMA Android Development] samjam:
If I do a fresh install of froyo, use app-brain to install my apps and reboot, I immediately get this kind of nonsense

[ 21.793457] **>> yaffs chunk 57086 was not erased

[ 21.799957] **>> yaffs chunk 57087 was not erased

[ 21.806823] **>> yaffs write required 319 attempts

[ 21.925384] yaffs tragedy: no more erased blocks

[ 21.931854] !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

[ 21.978637] yaffs tragedy: no more erased blocks

[ 21.984832] !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

[ 22.032043] init: /init.rc: 192: invalid option 'ioprio'

[ 22.043212] init: /init.rc: 197: invalid option 'ioprio'

[ 22.254821] init: cannot open '/initlogo.rle'

[ 22.337219] yaffs tragedy: no more erased blocks

[ 22.341918] !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

[ 22.347015] yaffs tragedy: no more erased blocks

[ 22.351531] !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

[ 22.356811] yaffs tragedy: no more erased blocks

[ 22.361694] !!!!!!!!! Allocator out !!!!!!!!!!!!!!!!!

[ 22.366790] yaffs tragedy: no more erased blocks

The first thing I did was to take a backup of data (any way to do this NOT from the ramdisk but before I reboot?)

Even restoring the data doesn't help. My phone is in a contineous reboot

Currently I have to install and make sure I never power down or crash.

I may have to get a non-kaiser today - last night my phone crashed while on a journey. I had no satnav and it took half an hour to get things working and I was late for my meeting :-(

But it means I may have a couple of kaiser to donate to devs.
[Touch CDMA Android Development] l1q1d:
The problem is that all rom don't unmount correctly the partitions (not exec shutdown script) and so there are some part not correctly written.

Backup after yaffs error is unuseful because generate broken files.

I'm working on the crash but we need that someone fix the shutdown problem.
[Touch CDMA Android Development] VulpesFoxnik:
Sometimes the a work around is so simple...

I was having problems with the file system becoming corrupted. (So far, the new rom (10-19-10, I notice there is now a new version) has NOT had this problem). However, being without a data plan, I devised a method to essentially snapshot the whole system to my rather large SD card. Yes, I know It's an ugly fix, but it has worked every time I need to restore and get to my contacts. It is actually based off of how I modify Dzo's fresh Froyo quickly to use ADW Launcher instead of Launcher2.

You must run this with root permissions so type:

su -c 'sh /sdcard/snapshot.sh'

The following is the contents of Snapshot.sh

#!/bin/sh
rm /sdcard/andboot/androidinstall.tar
tar cf /sdcard/andboot/androidinstall.tar /system/ /data/

Don't worry about it not including certain file types or removing the /. Those are normal. Some of those files are used by open processes on your system that will be created when they run again.

I know, stupid simple script. In that position, you should be able to restore your file system immediately to It's last working state if it gets corrupted again and you are on the go. Remember! DO NOT distribute that image. It has all your log-ins and passwords.

Also, do not use this script on a disk with a pre-existing install image you wish to keep. I use two disks, one for installing, the other for running. I keep this on my running disk.

Finally, if you get an error about the bad interpreter. Just modify it to the pathway of the value of the returned command "which sh" and you should be fine.

I'm not sure if this will cause any sort of permissions problems, so you might want to run that after you reinstall using the image
[Touch CDMA Android Development] l1q1d:
I test it on running system before and it isn't a good idea (slow and sometimes has locks)

To do the same without android running use atools and check backup phone.
[Touch CDMA Android Development] VulpesFoxnik:
Yeah I have to admit, doing it on a running phone is risky, however shutting down seems to be the problem, so by doing it while running, it may save some systems. Like I said, neither are very clean solutions.

... Also I tired moving the install-seq.sh to andboot and I still only get the same menu as before... Am I supposed to be doing something other than pressing down center at boot?
[Touch CDMA Android Development] l1q1d:
If you want to use install seq don't press anything just put it inside the dir.

If you press D-pad you avoid execution of script.
[Touch CDMA Android Development] VulpesFoxnik:
Yeah I just noticed what it did after I installed the latest OS. Did not do what I expected it to do. I expected a menu. Clearly I misunderstood as it wiped my phone. LOL

But in all seriousness, how is the installer supposed to install from system.tar and data.tar in the case of an emergency? Doesn't it only install from andriodisntall.t* and andriodupdater.t* ?:confused:
[Touch CDMA Android Development] l1q1d:
simply rename the file to androidinstall. Simple!

Backup phone create only one file. Backup system is for developers...
[Touch CDMA Android Development] abompard:
Do you know which ROMs have the shutdown script ? At least one ?

Thanks.
[Touch CDMA Android Development] derringdo:
I finally bit the bullet and switched over from Haret to NAND, hoping to finally solve the Sleep of Death issues. I experienced a blissful 2 days of speedy NANDy fresh froyo, until I finally ran into the dreaded Sleep of Death twice. It seems like the last time it happened, I had just received an email in Gmail.

If it weren't for this continued issue, I'd probably describe the fresh froyo experience as close to perfect. I'm hoping there's still development going on, even though dzo isn't on his vogue any more :(

Should I bother posting the last kmsg? Thanks guys.

Edit: these are dead kernels, where the screen will not wake up but the back button will turn on the start/end call buttons.
[Touch CDMA Android Development] l1q1d:
Which kernel did you use?

Post the link...
[Touch CDMA Android Development] derringdo:
I used the latest nbh that dzo posted, 09-10-10 here.

I'm on a vogue if that matters. Thanks

Edit: I just flashed to the newest version linked in your signature. Hope this fixes it!
[Touch CDMA Android Development] scooter1556:
Possible YAFFS Fix!

I have posted a kernel over in the kaiser thread which it seems may have helped the yaffs errors on the 2.6.32 kernel. Edit it in Atools first to configure it for vogue and see how it goes! I'll be pushing the changes to git soon :)

LINK : http://xdaforums.com/showpost.php?p=9151105&postcount=227
[Touch CDMA Android Development] derringdo:
Just experienced another dead kernel using the 10-30-10 kernel posted by l1q1d
[Touch CDMA Android Development] l1q1d:
You use a quite old kernel so before posting use your brain and the latest version!
[Touch CDMA Android Development] Does_It_Matter:
If you are over-clocking, try and reduce the clock rate also!

I was running my Vogue @ 500 mhz, and would occasionally get random locks/boots

I dropped it down to 480 mhz and I haven't had a lock or random boot yet.

I'm running the 10-31-10 2.6.25 kernel
[Touch CDMA Android Development] derringdo:
When I posted that, the 11-12-10 kernel was just a few hours old, and before that the one I was using was the latest. I appreciate all of your hard work but I don't see a reason for you to be so rude/condescending, especially when I just missed the latest kernel by a few hours.

Anyway, are you saying the 11-12-10 kernel should fix the dead kernel issue? I'll try it out in any case. Thanks.
[Touch CDMA Android Development] l1q1d:
i'm sorry but i said it because 10-31-10 because is old and there is no develop at all on 2.6.25 i can't look all version and all release, so i focus only on new branch (2.6.32) and current problems.

The problem dead kernel is not present in last 3 released kernel (2.6.32), the actual problem (probably fixed) is nand
[Touch CDMA Android Development] derringdo:
That's strange... I've been using the 2.6.32 kernels since they were released. I haven't used a 2.6.25 kernel for a long time. The last kernel I used was in the 2.6.32 branch but I still get the dead kernel problem. Sigh
[Touch CDMA Android Development] l1q1d:
Do you use the latest kernel now and you have still the dead kernel?

Which release are you using now? (fresh froyo, barebones...)