yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] Enigmatik_best:
I had the same problem.

I did download FRX07.1_Full_Bundle_20110901.zip too much early.

There is a change of the system.ext2 file (different date: 3/09/2011 in place of 1/09/2011).

- Erase your actual FRX07.1_Full_Bundle_20110901.zip and the unzipped folder FRX07.1_Full_Bundle_20110901 of your pc;

- Download again the FRX07.1_Full_Bundle_20110901.zip from here: Download the full bundle (zip) or from the first post of this thread: http://xdaforums.com/showthread.php?t=1171052

- Unzip FRX07.1_Full_Bundle_20110901.zip

- You have this folder: FRX07.1_Full_Bundle_20110901 and a subfolder: FRX07.1;

In this subfolder, you have this files and folder:

Folders:

* AndroidApps (and subfolders)

* conf

* STARTUPS (and subfolders)

Files:

* HaRET.EXE

* initrd.gz

* modules-2.6.27.46-01348-g9de837f.tar.gz

* PLACE STARTUP.TXT HERE

* rootfs.img

* system.ext2

* zImage

- Delete the same folders and files in your SDcard of your phone and all the modules....tar.gz files that you may have.

(you can keep the startup.txt file I think but I did replace it anyway. Just did once again the change for the keyboard: in the startup.txt file (open with an editor like Wordpad or Notepad) change "physkeyboard=rhod100_uk" by "physkeyboard=rhod100_fr" to have a AZERTY keyboard in place of the QWERTY keyboard. !!! Adapt for your phone, take the good startup.txt file)

- Copy ALL the folders and files of the NEW unzipped FRX07.1_Full_Bundle_20110901.

After I don't know the good way but I did that:

- Reboot (if you have a multi-boot program like Gen.Y, choose "Boot Windows");

- With your file explorer like Total Commander or the native file explorer, run HaRET.EXE

- No more message like "Default.txt" with the button "Run" and "... port 999..." with the button "Networking connection".

-Wait the complete boot and one minute more is better.

Contemplate the beauty of the new release of the build. Enjoy ;) :cool:

PS: Arrrghhh: can you correct any errors in my post please.
[Touch Pro2, Tilt 2 Android Development] SonicPower:
I tried the latest FRX07.1 build on a HTC Touch Diamond on Sprint (DIAM 500).

I get no signal.

Has the project been abandoned for those on Sprint so don't bother with XAndroid unless you're on a GSM network?
[Touch Pro2, Tilt 2 Android Development] AkumaX:
I'm on RHOD 400 (Sprint Touch Pro2) and it's a dream
[Touch Pro2, Tilt 2 Android Development] r0dman_:
On my Telstra RHOD110 - which startup file should I use?

I have read some people using RHOD210, and others editing the startup file to use:

physkeyboard=rhod110

Any recommendations?
[Touch Pro2, Tilt 2 Android Development] SephRobbertse:
I just want to say thank you. 1st day on FRX71. 1st time Android user. Great fun!
[Touch Pro2, Tilt 2 Android Development] coolwater22:
well for the first question fortunz answered my question. I like the front buttons light to come on but not everytime I press a key with the keyboard open, so I just turned them off...I know people wanted them to work, but I for one was alright with out them, plus they're too bright :/... good job devs on getting the lights to work though :)

for my second question, I was talking about when I call someone and they never actually get the call. like the call didnt even get to them.. and no it doesnt go to directly to voice mail..

-edit: I made a couple of calls and the other person got and could hear me

so nvm, thats my bad..

thnx for the help though arrrghhh.. your the man...keep up the good work arrrghhh and devs.. :D

thnx alot fortunz,you have been thanked..that solved my problem :)

also i found another bug..idk if its been solved or not. I get static when im on a call, and the only way to get rid of it is to click on the speaker and then turn the speaker off. That seems to solve it momentarely..i was reading the posts and someone brought it up quite a few posts back, but I didnt see an answer for it... if there isnt any resolution at the time its alright, I can live with it :).. I'm sure the devs will fix it in due time..

best build yet: fast,smooth, and the best part is the battery life.....once again keep it up devs :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
This site definitely has more GSM users. But you're posting in the TP2 section. I have posted a thread for RAPH/DIAM users in the RAPH section (there i no DIAM Android Dev section...)

http://xdaforums.com/showthread.php?t=1171070

It's pretty much the same build tho (one build to rule them all!) So if you didn't get service on this build, I doubt you'll get it with that build. Have you tried messing with any of the settings? Is this the first Android build you've used on your DIAM?

I'm on Sprint as well, but on a RHOD400 - no problems here with signal. Unfortunately the RIL that was updated wasn't updated for RAPH/DIAM. HYC worked long and hard, and got it working so the radio at least works - but data still doesn't work. I haven't heard from any CDMA RAPH/DIAM folk, but perhaps using the old RIL in the meantime will allow you to use FRX07 with data...? If not, your best option might be to stick with FRX06 until someone takes the time to rewrite the RIL for your old radios... Good luck.

physkeyboard=rhod100_uk

doesn't work?

I guess I need to add a startup for your phone. There's certainly not many with a RHOD110 :p. From what I've gleaned, they're basically the same as the RHOD100_UK.
[Touch Pro2, Tilt 2 Android Development] mgross029:
The static is because of the acoustic libs which are not complete. The devs are working on this... I'm sure there will be a fix in the works soon...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, he already mentioned the workaround - flip speakerphone on/off. That's "the fix" until the issue is actually fixed by the libs you mentioned.
[Touch Pro2, Tilt 2 Android Development] Dinky:
Close/minimize/switch applications

Hi,

I have a simple question to ask. I have a Rhod300-Tilt2 running FRX7.1. How do I close an application or minimize an application? I know that there are two ways to "make the application disappear" - the "Back" hardware button and the short press of "End Call" button. But I can't figure which one really close the applications instead of minimize them. A lot of time, I thought I closed the application, but under "Settings" -> "Applications" -> "Manage Applications", they are still shown as running. Can somebody shed some light with me?

Also, in case the applications are minimized, how do I switch to an application running in the background? Thanks.
[Touch Pro2, Tilt 2 Android Development] reckert:
Maybe some hardware differences- I have a RHOD 500 -

Here are some logs. I've tested it about a dozen time - fastboot or slow boot doesn't seem to matter. If I goto windows, wait 30 seconds then haret starts no problem. (I wonder if the windows rom has an effect too - Using an older Energy ROM from beginning of the year).

update- i was booting windows in airplane mode, switched to phone off and wifi on, and wifi works even in Gen.Y fast boot.

This must be something with the timing of when things initialize in win. lesson learned here, if people have odd problems, they should let win initialize completely before running haret to stabilize the hardware.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, the way Android manages applications and memory are vastly different from WinMo.

In essence, all applications are "minimized". Then, if you want to open another app and there's no memory - that old app that was minimized and deemed no longer necessary to be held in memory is cleared from memory and the new app is opened. If in this last scenario you have enough memory, nothing is cleared. Then when you go back to the old app, it opens much quicker because it is held in memory.

I'd highly encourage you read my speed improvements thread. It has some pretty advanced topics on memory management, and links to some articles that explain it much better than I ever could ;).

Now to get back to an app - you either just go find it directly, or if you long press on the end (home) key it will bring up a "Recent Apps" list. This is not a "running apps" list - this is merely apps which you have recently launched. This is how Android's multitasking works. You kinda have to relinquish control over to the system - but if the system is inherently efficient at managing memory, it's a better model.

I don't see any logs, perhaps you are editing your post. As for the workaround, so long as you know how to fix it that's all that matters. Just wanted you to know that your experience was unique - many users use Gen.Y without this problem. Might want to update your ROM.
[Touch Pro2, Tilt 2 Android Development] PolkaBear:
I'm excited to try 7.1. The last time I played around with Android on my Tilt 2, it was 4.x (I think). It seems like a lot of the kinks are being worked out by now.

Unfortunately, I'm running into a persistent problem: it's taking over ten hours for the first boot. I don't know how much longer than 10 hours its taking, because my once-full battery died before it finished. The previous three times that I tried booting 7.1, I waited four hours, two hours, and one hour, respectively, then reset the phone because I figured there was something wrong. The fourth time, I decided to let it run overnight after a recharge--and that's when the battery died in the wee hours of the morning. I know it was still running at 4 a.m. and making progress because I checked on it then. It died some time in the next two hours.

I check on the phone's progress periodically, and it doesn't hang. However, I keep seeing "task rpcrouter:15 blocked for more than 120 sec," but not for every line. If the phone frequently hangs for two minutes waiting for something that never comes, that could stretch things out interminably...right? In case it's not obvious: I don't know enough about Android/Linux to know if I've identified the problem, so it might be something else slowing things down.

I've tried installing everything to the root of my SD card; installing everything in a directory (and altering the startup.txt accordingly); re-downloading and re-copying the files to the SD card.

In an effort to find an answer, I've read hundreds of posts in this thread and searched for "task rpcrouter." Nothing I've read strikes me as a relevant solution.

Am I overlooking something obvious? If so, I apologize.
[Touch Pro2, Tilt 2 Android Development] mgross029:
I have been running Rhod500 and Gen.Y boot for sometime without this problem. I am on the latest VZW Stock Rom in WM... I have Sense disabled (just to note) since I don't use anything in WM anymore... I run Android on a Daily basis... I know there were some radio updates in the latest VZW ROM... The MR3 update came out in Jan of 2011... Maybe flashing to this would help...

Linky if interested:

http://www.pcdphones.com/our-devices/products/68-xv6875
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, you're overlooking something very obvious - if it takes longer than 10 MINUTES to boot (from clicking HaRET to Android lock screen) then something is wrong.

Usually one of two things have happened. You either skipped or forgot the ts-calibration step, or you've placed everything in a folder without specifying rel_path= in the startup.txt. Everything should be at the root of the SD card (no folders! HaRET.exe, zImage, system.ext2 etc all at the ROOT of the card) unless you specify rel_path= in startup.txt. Re-read the first post please.
[Touch Pro2, Tilt 2 Android Development] PolkaBear:
Yeah, that's what I kept reading. Earlier versions of Android never took this long for me, either.

I'm reasonably certain that it's not a path problem. As I said, I tried it both ways: in the root of the SD card (with no rel_path specified) and in a subfolder (with a rel_path specified). (TBH, I had a typo in my startup file for the first run, but I quickly recognized it and fixed it.)

After re-reading the first post, I think I misinterpreted/misunderstood the screen calibration instructions. (I was waiting for a calibration request to appear AFTER it booted--but it doesn't work that way, does it?) I downloaded the ts-calibration.zip you attached to the first post. I expect that it will solve everything--well, maybe not world hunger.

Thanks.

*EDIT: Yep, that did it. Sheesh. I hate it when the answer seems obvious in retrospect.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Meh, they almost always do :p. np, enjoy!
[Touch Pro2, Tilt 2 Android Development] dsramesh:
I tried to increase the size of data.img to see if it will increase the phone memory which is now down to 60mb. I increase the size to 512mb and 1gb but that did not work.

How to I increase to make the difference?

- I feel that the slow down happens as the system runs low on phone memory just like winmo does.

I am running FRX7.1 (Verizon CDMA TP2) and it works well as noted in my earlier post.

I used LED Hack to enable "breathing" when sleeping and I turned GPS location off but I don't see it breathing?

- Is the LED hack working or something else is keeping the phone from going to sleep

- Exchange is set to sync manually and only thing set to automatic is Gmail.

Thanks!

..Ramesh
[Touch Pro2, Tilt 2 Android Development] jevojim:
FRX07 and 07.1 broke the Fn key on teh hard keyboard. I have to use the touch keyboard if I want symbols. This used to work in FRX06 for me...

Also a sprint TP2.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
For expanding the data.img, see this thread.

That has absolutely nothing to do with speed tho. That's the data.img, as in the file that stores apps and personal stuff - RAM is completely different, and has nothing to do with expanding the data.img. In other words, you won't notice any speed differences by expanding or contracting the data.img. It'll only give you more space to install things.

As for the "LED Hack to enable breathing" I have no clue what you're talking about. That sounds like a feature that is RAPH-exclusive... our LED has never had a 'breathe' setting - only RAPH/DIAM do.

Works great for me. Make sure you're using the right startup.txt/physkeyboard setting. RHOD400 is Sprint.
[Touch Pro2, Tilt 2 Android Development] jevojim:
Yeah, I just figured that I had mangled the keyboard setting by adding a w to the end. Works great now and nice to have that back!

Thanks for all your help!
[Touch Pro2, Tilt 2 Android Development] jevojim:
Got any tips on how to get the End Key to do something besides turn off the phone? In FRX07, it was more useful than the now-redundant "off" function...
[Touch Pro2, Tilt 2 Android Development] coolwater22:
alright for sure...just making sure, thnx for answering me guys :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
The end key is now home. Short press will act as home, long press brings up recent apps just like a native Android device would. End does not turn off the phone any longer.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
well for me im running FRX07.1 and right out of the box the end key is mapped to go to the home screen and long press=recent apps..

check out this thread..idk if it helps:

Edit: I see arrrghhh beat me to it :P

http://forum.ppcgeeks.com/android-t...oard-keys-classic-home-rhod210-400-500-a.html
[Touch Pro2, Tilt 2 Android Development] reckert:
Memory is independent of the data.img size - data.img is the size of the /data storage , where memory is the working space for the cpu. Did you try the performance tweeks arrrghhh posted on a separate thread. I also found if you format data.img with 4k blocks, that can speed things up as well. (Mainly writes)
[Touch Pro2, Tilt 2 Android Development] anticimex:
Hey. I got a picture of my keyboard now (finally). I am sorry if it is a bit blurry, but if you want any clarification, just ask ;)

I can try and make a vector/graphics version of it, so it is much easier to see and understand it.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Is your keyboard not covered by the already-built layouts? If so, make another layout. Assuming it works for you, commit it. See http://xdandroid.com/wiki/Submitting_Patches
[Touch Pro2, Tilt 2 Android Development] r0dman_:
I will try it - always like the follow the directions and just wanted to be sure first but I will give it a go.

Thanks!
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Thanks. How do I format the data.img?

..Ramesh
[Touch Pro2, Tilt 2 Android Development] jevojim:
Thanks for the responses...

OK, well today after rebooting and fixing the keyboard error in my startup I have the End key acting normally again. Weird.

I do find the 7.1 release to be a bit more responsive than 7.0 -- just a whole lot more fun to play with!
[Touch Pro2, Tilt 2 Android Development] rod555:
same question...
[Touch Pro2, Tilt 2 Android Development] rpierce99:
data.img is recreated automatically if it doesn't exist, so rename/move/delete it and it will rebuild.
[Touch Pro2, Tilt 2 Android Development] fishingmedic:
I think they were looking how to format it in 4k blocks like the prior poster noted. I know how to increase it's size but not format it in specific size blocks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I think they want to know how reckert formatted his data.img with 4k blocks, as described here because he claims a speed boost.

I'd imagine he either makes the data.img himself using DD, or changes init in rootfs to generate the data.img with 4k blocks.

D'oh, fishingmedic beat me to it :p.
[Touch Pro2, Tilt 2 Android Development] reckert:
I changed creating a new data img code from:

echo "Creating a new $dataimg"
dd if=/dev/zero of=$card/$dataimg bs=1048576 count=256
[ $? -eq 0 ] || fail "Failed to allocate $dataimg"
mkdir -p /etc/ ; touch /etc/mtab
mke2fs $mkfs -F $card/$dataimg
[ $? -eq 0 ] || fail "Failed to format $dataimg"

to

echo "Creating a new $dataimg"
dd if=/dev/zero of=$card/$dataimg bs=1048576 [B]count=512[/B]
[ $? -eq 0 ] || fail "Failed to allocate $dataimg"
mkdir -p /etc/ ; touch /etc/mtab
mke2fs $mkfs [B]-b 4096 [/B]-F $card/$dataimg
[ $? -eq 0 ] || fail "Failed to format $dataimg"

This gives write improvements since its sitting on top of the FAT32 system which is also 4k blocks. - so writes to the disk are all blocked at the same size.

I've actually moved on to trying partitions now,
[Touch Pro2, Tilt 2 Android Development] Likn'_ùs:
Hi everybody,

I'm an HD2 users, but i've bought from a friend the TouchPro2.

Now i'm planning to put andoird also in this phone, but could you please tell me if the physical keyboard works with this OS?

Thanks you for the reply..

Best regards

L. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you commit this change...? If it helps, and doesn't harm anything, it would be nice if everyone could benefit from it.

Yes, the physical keyboard works great. I don't think anyone would use Android on a Rhodium if it didn't (I wouldn't :p). That's pretty much the only reason I still have this dang phone!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hah, no worries. Thanks! I'll talk to stine about it.
[Touch Pro2, Tilt 2 Android Development] avionix:
Camera

I finally had a need to use the camera today and lo and behold, I was able to take 1 picture and then FRX07.1 froze. :mad:

Rebooted to winmo to test and no problems with the camera.

Booted back into FRX07.1 and got the same results (froze after 1 picture). Also, the 1 picture it took can't be found anywhere on the SD card after reboots. :confused:

I know, shame on me, but... I just took everyone's word that the camera worked and never checked.

I know Arrgghh said that he took a boat-load of pics, but was it on a Rhod400?

Other than that, THIS THING TOTALLY ROCKS!!! :cool:

Thanks guys!!!
[Touch Pro2, Tilt 2 Android Development] mgross029:
avionix,

I have a Rhod500 and have taken several pics and video without any problems... Did you reuse your data.img or create a new one? First thought is backup and delete/rename it... Let it rebuild...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You never even stated what device you have.

RHOD100's with the AUO panel have a different cam, and it most definitely does not work.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
16GB SD Card and 32GB SD Cards are formatted with FAT32 at 32K block size and recommendation is that it be formatted at 32K blocks based on the size of the card.

I have 16GB and 32GB cards that came formatted as FAT32 at 32K blocks.

..Ramesh
[Touch Pro2, Tilt 2 Android Development] wmg316:
LOL. I never use my keyboard! But agree...it does work great from my limited tests.
[Touch Pro2, Tilt 2 Android Development] wmg316:
@Arrrghhh. I'm really loving 7.1. But audio is still not working when recording video. Any fixes available?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Same as always... The experimental audio routing is the only fix I've ever heard of.

This isn't a deal-breaker for me - have you ever tried the old tricks of getting the mic to work like booting Android with a call to voicemail running on speakerphone? Perhaps that would "fix" the issue without resorting to that new audio routing code. I guess I should put out a build for the new audio code... seems like there's rumblings to try and get it implemented, which would be nice. I still experience bugs with it, but there's certainly a lot of things it fixes.
[Touch Pro2, Tilt 2 Android Development] reckert:
The first thing I learned with Android is to listen arrrghhh, and use the HP format tool to format the card, that only does 4k blocks. Also I think ext2 doesn't go beyond 4k block sizes - if you use the experimental ext4 file system, that could help across the board since it tries to allocate and use contiguous blocks.

The 'correct' block size for a file system is a matter of art and science. Larger blocks are more wasteful, but based on how the SDCard is designed, they are much faster. - I tested my card in a separate reader and got maximum throughput at 16K blocks. However at that size, each file is 16k or larger, so even a small .conf type of file will take that space.

With my 32Gb card, I recently went ahead and partitioned it - that gets tricky, connecting it to a linux box to create the partitions, and creating the main, partition 2, system and data partitions, and then loading the system parition. (And redoing it the next day when froyo 7.1 came out :)). It seems faster still since another layer of filesystem is removed, however I haven't found anything that would be a good performance measure to tell what the net impact is.
[Touch Pro2, Tilt 2 Android Development] dsramesh:
Yes, I know I need to listen to arrrghhh!

- I had problems with the 32gb card formatted at 4k blocks and went to the manufacturer (Wintec.. local to me and very close to my work place) and they said I have to format it to 32K blocks for stability. I kept getting corrupted files and couple of times, the PC just did not recognize my sdcard and had to reformat it and lost all the data!

..Ramesh
[Touch Pro2, Tilt 2 Android Development] mgross029:
reckert, just did this with 7.1 and saw a noticeable improvement with just this block size change... So thanks...
[Touch Pro2, Tilt 2 Android Development] avionix:
My bad,

Rhod400
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Huh. I've had great and horrible experiences with the camera - and unfortunately I've been unable to figure out what makes the difference between the experiences, other than free memory. Android is definitely RAM hungry, and we don't have much to give - especially with the slow processor trying to push so many pixels... So my only advice would be try it on a fresh boot after everything's settled. Perhaps even try renaming your data.img and again let it settle on boot - perhaps some apps are hogging memory and not releasing it in time for the camera to function properly.
[Touch Pro2, Tilt 2 Android Development] coolwater22:
data!!

im wondering when i use my phone it turns to 1x where the 3g is suppose to be at..is that reception or what?? and sometimes i appear that i lose connection for no apperent reason..any help would be gladly appreciated :)