yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] jonners59:
arrrghhh

Firstly I am very p***ed off with myself for not realising that F7 was out, especially before I started my pan European trip and had to use the roaming, which incidentally still does not work in F6.:mad: Otherwise F6 has been working very well for me.

So having found out it's out... well done guys and many big thanks.:D

I have decided to install a fresh setup and have taken the whole zip file. Unpacked it and installed in a folder called Android on my SD card (15Gb). I am using a RHOD100 phone. I amended the cmd line in STARTUP to reflect the location of the files and then started it up.

The script runs, but stops. It then repeats a string of c15 lines every few minutes. I left the phone for about 1.5 hrs and it has not moved on. I tried, just for the hell of it to move everything to the root of the SD card and try again- with the std STARTUP - but it still does the same.

Trying to read the script, it says the following from the 1st line of the repatition:

171.80383 INFO: task rpcrouter : 15 blocked for more than 120 seconds

...... "echo 0 > /proc/sys/kernel//hung/hung_task_timeout_secs" disables this message.

and another few lines, then the last...

r5: 00000000 r4 : 000000000

Any suggestions, please? :confused:
[Touch Pro2, Tilt 2 Android Development] nyd:
The same thing happened to me too. I think it is waiting for you to click on calibration points. I couldn't see them the first time, so I clicked some random points on the screen and I had miscalibrated it. If you can't see the calibration points, just click some random points and then delete the ts-calibration file and restart. It will ask you to calibrate again. The second time I could clearly see the calibration points. If this still doesn't work for you, you could try to copy the calibration from WinMo or try a calibration file from somebody else.

LE: I have the FRX07 for 2 days and I had 2 random resets, I don't use wifi. Once the phone was in sleep mode and it just reset without anybody touching it and the second time I was trying to make a call. It seemed like the call button triggered the reset, but it may be totally unrelated as I can't repeat this behaviour. It is not so bad, but still a problem.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
But that was my point. If AOSP doesn't provide it natively, neither will we... Sorry. Third party apps are the only option if it isn't provided natively, and since I could care less about FB sync, someone else is going to have to take up that cause. There's a lot of things I worked on getting functional that I could care less about (MMS was a biggie) but I don't even use FB, so I'm not sure how I could even begin to help with that.

As was suggested above, it sounds like you missed the ts-calibration step...

Mate, without logs nothing gets fixed. If they're full resets to WinMo, the only way is ramconsole or /data/dropbox/SYSTEM_LAST_KMSG logs.
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
help pls

hi everyone i need your help.

i just installed the FRX07 in my htc touch pro 2 earlier

when i clicked the haret a message will pop up saying 'unknown keyword: 'htc_hw'

and when i clicked ok the system boots and it works except that there is an on screen keyboard on top (booting and on android menu)

and the led light is alway on (orange/yellow) and when i choose or click any of the program the screen change its view to landscape.

please advise me what to do? thanks :)))
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please paste your startup.txt.

This command removes that virtual keyboard:

msmvkeyb_toggle=off

If you have the startup.txt jumbled or something awry with it, that command (and others) won't process correctly. So please, paste your startup...

LED is always on, it indicates sleep state. Please read the FAQ.
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
here is the content of startup:

set ramsize 0x10000000

set ramaddr 0x10000000

set mtype 2292

set KERNEL zImage

set initrd initrd.gz

set cmdline "rel_path=FRX07 acpuclock.oc_freq_khz=640000

htc_hw.call_vol=5 lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_it"

boot
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nothing jumped out at me, other than deprecated commands. See my update above.

Don't edit the file with Word, Notepad, Word Mobile, etc. It will screw up the formatting... If you're on Windows, Notepad++ is good.
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
ty

thank you so much sir! you jus save me from swapping my htc to iphone. :)

now ill be working on my dual boot system.. :)
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
last one

one last concern,

i used Gen.Y DualBoot but i get this error:

An error occurred on sub__main_app_start.

An error occured retrieving the registry key

Continue?

Yes / No

how do i fix this?

:confused:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
WinMo / Gen.Y issue. Please only ask Android Development questions here.

It's an issue with the registry, clearly the key is not there. Perhaps it didn't save properly... again, WinMo / registry / Gen.Y issue. Nothing to do with Android dev.
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
:)

ok sir thanks :)
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
=)

where should i install apps/games?

in folder where the haret is located?

or on the root?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Uhm... you install things thru the Market usually. Everything is on the SD card, so you don't have a whole lot of choice there. I've heard you can move apps to SD if they support it, but it seems expanding your data.img would be eaiser (I've honestly never needed to do either.)

If you just have an APK, put it in AndroidApps like it says in the FAQ. It'll be cp'd to /data/app on boot.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Thank you nyd and arrrghhh:D

I tried this and it still did not work. I then tried putting my old TS-cal in to the build and that did not work, I have (as it is always an old fav) coppied the card and then re-formatted it... That too does not work.:(

Any more ideas guys, please?:confused::confused::confused:
[Touch Pro2, Tilt 2 Android Development] nickleby:
Hi arrrghhh, investigating a little more on the Internet, I noticed that you need to change a parameter within the application "ContactsProvider.apk" to be able to sync contacts with Facebook. I modified the application according to what it says on the internet and now I can sync with Facebook without any problems. But I don't know if I can upload this modified application :p
[Touch Pro2, Tilt 2 Android Development] eruisi:
Thanks for the reply. This is a famous funny game which could amuse my kid if it works (If you think this is a use of the app;)). It takes human voice and plays back in a funny way.

Voice call works perfectly so I expect microphone to function, but it seems not in some cases.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If the apk works, I'm sure there's a few people here that would love it if you would post it.

lol @ that minor change fixing it. I'll talk to stine about it - did you change it in the source...? Do we have a repo for that APK? I wonder if there's another setting that would enable it. If you could give me more info, I can try to get it upstream...

Not something I would find useful personally, but did you try the trick I mentioned earlier?
[Touch Pro2, Tilt 2 Android Development] rpierce99:
I found the fix he's talking about, I'll see about putting together a patch.
[Touch Pro2, Tilt 2 Android Development] nickleby:
[FIX] Facebook Contacts Sync

Here's the modified app, now you can sync your Facebook contacts without no problem!

You must use ADB or terminal emulator. Download the .apk file and put it in the root of your sd card.

With ADB:

adb shell

su

mount -o remount,rw /system/

mv /system/app/ContactsProvider.apk /system/app/ContactsProvider.bak

cp /sdcard/ContactsProvider.apk /system/app

chmod 644 /system/app/ContactsProvider.apk

If you use Terminal Emulator:

su

mount -o remount,rw /system/

mv /system/app/ContactsProvider.apk /system/app/ContactsProvider.bak

cp /sdcard/ContactsProvider.apk /system/app

chmod 644 /system/app/ContactsProvider.apk

In both cases, SuperUser will ask you to give root permission.

You can search for this fix online, I'm just saving the step of having to edit the .apk file
[Touch Pro2, Tilt 2 Android Development] jonners59:
Any ideas anyone, please!!!!!!!
[Touch Pro2, Tilt 2 Android Development] xmwuahx:
:(

during booting

i saw this message,

You have no media folder, please extract the resources to your SD card android folder

how do i do this?

the games in the androidapps folder is not shown in the menu. how do i fix these?
[Touch Pro2, Tilt 2 Android Development] krehla:
Hey guys, is something way how to disable LED notification (orange/green)?

thank you, krehla
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would recommend changing the directions to mv the ContactsProvider app to .bak or something. rm'ing it seems like a bad idea if there's ever a need to revert (which I guess is pretty easy, just redownload the FRX07 system.ext2 file :p.)

Dude, either provide some logs or keep triaging yourself. Did you try the newest files or just what is provided in the bundle? Might want to try updating rootfs & kernel. Have you tried formatting the card? Deleting the data.img? Is it even creating a data.img?!? Did you try manually calibrating? C'mon. Troubleshoot. Help us help you.

Ignore that message, as I have no clue what you're talking about.

Anything within those sub-folders are ignored. They're only installed if you want them installed. So move anything you want installed to the root of the AndroidApps folder.

Update your kernel to the newest. I believe they changed the default behavior so now the sleep notification has to be forced on, instead of forced off.
[Touch Pro2, Tilt 2 Android Development] nickleby:
LOL If people complained that they could not sync with Facebook, now that they have it I don't think they want to revert :p

Either way, I've made the changes in the post to backup the file instead of delele it :)
[Touch Pro2, Tilt 2 Android Development] nyd:
If you don't have the latest update, an update would improve the LED situation.

Here is how you can perform an incremental update
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
2 things:

kernel BUG at arch/arm/mach-msm/smd.c:317!

and

kernel BUG at drivers/char/tty_ldisc.c:199!

What kernel are you on? I thought there were some patches to resolve these bugs...
[Touch Pro2, Tilt 2 Android Development] yoyo81:
The latest: htc-msm-linux @ 20110819_183957 (2.6.27.46-01348-g9de837f)

(i've gotten the LED changes working)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, well evidently they're not resolved. I'll see what I can find in the logs, I swear I remember some chat about these bugs.

Edit - I did a search on the logs, see here and it appears that it's fixed in .35+, and it hasn't/can't be ported back to .27.

In reality, we desperately need to get off of .27. We're working towards it, but progress is slow.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Hi arrrghhh

I did answer the questions at the start in my first entry. That said, logs... I do not know how to run and find logs. What I have done is, as per first reply, manually copy the text that appeared on the machine during boot.

The second question: I used the one at the start of the thread...

Yes, I tried reformatting the card. No difference.

No data.img was created. Could I use the F6 image???

As per previous reply, I tried tapping the screen but it would not do anything, I then tried the F6 ta-calibration file, that too did not work.

I'll take a look at the latest rootfs and kernel and report back, but if you have any other ideas, please share.

UPDATE

I downloaded and installed a new rootfs and kernel, the latest. Tried again and it stopped as before in the same place.

Previous replies quoted below.
[Touch Pro2, Tilt 2 Android Development] smartidoos:
With the help from everyone ,I have a creat Android working on mine Rhodium tp2 ,

I can give it a second live......................

Thx
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Please follow the steps for manual calibration which is in the first post.
[Touch Pro2, Tilt 2 Android Development] Dinky:
Great Build, but definitely need BT audio routing fixed

I just started to play with XDANDROID again since the WM6 development on my Tilt2 has died down. After a week of playing around, I got everything working with the newest rootfs and kernel, of course, except bluetooth. After upgraded the rootfs and kernel from the bundle, I've run the phone for three days, and it seems to be stable enough for daily use. The only problem is, I'm on the road a lot and the state law requires hand-free device for using the cell phone while driving. Without the proper BT audio routing, I can't use either my BT earpiece nor the Sync in my car.

I've checked into this thread

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

But looks like I have to go back to specific kernel. By searching more, I'm not sure that kernel is as stable as the combination that I am running, so I hesitate to go for that solution. Sounds like my only option is waiting for the new build with the BT routing fixed before I can be a loyal XDANDROID user. Hopefully it will happen soon...

EDIT: sorry, I forgot to thank the chef and all those who contributed to make this happen on our Rhodium-based devices. Thanks to all of you for spending your precious time bringing us this amazing solution.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, if you look for a .35 or .39 kernel it already has the new audio routing stuffs baked in. You'll probably lose some other functionality, there isn't a complete solution for BT that doesn't break other things. We certainly don't have a 100% complete port.
[Touch Pro2, Tilt 2 Android Development] jonners59:
arrrghhh

I had done 2 of the options, and am trying the 3rd... use an old kernel and then the latest.

OK, having tried the third option,that too did not work.

I tried an old kernel and rebooted. No different. The same 14 lines just repeated themselves.

I then put my old calibration file (from my F6 install) and tried again. The same thing. The same 14 lines repeated.

In no attempt did a request pop up asking for me to tap the screen. I did do so any way, but nothing happened.

Any other advise, please???????
[Touch Pro2, Tilt 2 Android Development] Dinky:
Just tried .39 kernel. I couldn't even keep the BT enabled. Once I click on it, it looks like it's trying to turn on, but just died down without the check-box turning green.

I guess I have wait a little longer until more gurus have tried this kernel and come up with an idea how to work around it. Thanks anyway.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you delete the ts-calibration file in order to manually calibrate?

If you're putting an old file in it *should* still work. I haven't changed ts-calib's in ages. Perhaps you're missing something else? I don't know what, but the error you listed earlier I don't think was related to you not being able to boot. If it's not even creating a data.img file, something else is very wrong. Do you have everything in a folder? Did you specify rel_path if so? I'm not sure what else would prevent you from booting, short of something in the startup.txt or perhaps a bad SD...?

Bah... I don't remember the state of BT on either kernel. Did you try .35? There's been more development on that lately it seems, although like I said I don't really know the state of either kernel in respect to BT...
[Touch Pro2, Tilt 2 Android Development] Dinky:
Tried it. No joy. Actually before I switch to .35, I just realized that the audio is totally "lost" in .39. There's no audio at all. The ringtone/notification will not sound, and you can't hear anything on a call no matter on the phone, or speakerphone. Since the BT cannot be turned on at all, I wouldn't imagine that they got routed to BT...
[Touch Pro2, Tilt 2 Android Development] jonners59:
arrrghhh

I first booted without any ts-calibration file. That did not work so I used my F6 file, that too did not work.

Missing stuff, but what? The F6 works fine...

Yes, I do have in a folder... To be exact the path is Android/FRX07 The Froyo6 is the same... Android/Froyo6

The STARTUP txt is

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk"
boot rel_path=Android/FRX07

I am confident the SD card is fine, all else works including F6.....:confused::(

What if I copied everything in F6 into the F7 and just used the new kernel rootfs and system... would that work do you think?
[Touch Pro2, Tilt 2 Android Development] teemo:
Replace

set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk"
boot rel_path=Android/FRX07

with

set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk rel_path=Android/FRX07"
boot

and have fun with a working FRX07 :D
[Touch Pro2, Tilt 2 Android Development] rod555:
download and test, cool!! thx!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Bummer! Well I'm sorry to send you down that fruitless path. I don't use BT much, and it doesn't seem like there's a perfect combo for that yet. It was pretty recent that BT was fully enabled, and audio routing is a big piece of that... and audio routing isn't stable - the existing method for audio routing is broken to the core, and the other method isn't ready for primetime yet. Hopefully some day it'll all come together...

lol, this.

Any 'cmdline' modification has to be on the set cmdline... line and it must be between the quotes with at least one space between each item. Please don't place stuff anywhere else in the startup.tx.t
[Touch Pro2, Tilt 2 Android Development] mgross029:
Dinky,

Check out this thread I just posted to see if it helps you get BT working...

http://xdaforums.com/showthread.php?t=1239925
[Touch Pro2, Tilt 2 Android Development] Dinky:
arrrghhh, don't say that. Help testing the builds is the least I can do to help the project. Since I have another phone that I can use at this point, I can help on any testing on my Tilt2, if time and my Linux knowledge permit. If you need further test, please let me know.

I gave it a try on .27 kernel - yes, it is partially working. What I did differently was instead of using "mount --bind", I rename libaudio.so under /system/lib, and copy the one in your zip file under that directory; then I copy the .csv files under /system/etc (I've tried both your files and the ones from my phone). Here are my test results:

BT turned on fine and pairs with my BT earpiece fine.

Incoming calls got routed to the BT earpiece correctly.

Outgoing calls the audio stays with the phone and cannot be switched (at least I didn't find a way) to BT earpiece. I tried toggling the "Bluetooth" button at the lower left corner of the dialer, and play with connect/disconnect button on the earpiece and non of them helps.

Once the earpiece is disconnected from the phone, there's no way to reconnect it back besides unpair/pair the earpiece again. Toggling BT on/off and even reboot the phone won't help.

Even though it is "half" working, I think it's a big step moving forward. Thanks, mgross029.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks for the feedback...

You may want to check the permission of the files... When I did a copy of the files to the appropriate directories I found that I had to do a chmod 644 on the files to get them to work properly... Doing the mount --bind seemed to correct all the problems for me, so that is why I went that way...

Also, something big... I noticed you mentioned you just copied the .csv files to the /system/etc, but if you did not rename the .CSV files before copying them that could be another issue... The ones from my zip as well as your WM are totally different than what the libaudio.so calls... The libaudio.so is looking for AudioPara4.csv, AudioPreProcess.csv and AudioFilter.csv... The ones from WM are AudioPara3.csv, AudioPreProcessTable.csv and AudioFilterTable.csv

Which Rhod do you have btw? Just curious...
[Touch Pro2, Tilt 2 Android Development] Dinky:
Hi, mgross029,

yes, I've changed the file permission to be the same as the original files, but I think I might have something messed up. I have to re-do the test. Please stay tuned.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Thanks teemo and arrrghhh

Just to make sure I am clear, because I am a very little lost here, the reason being I thought that IF the install was not in root of the SD Card the path had to be added... In my case rel_path=Android/FRX07 ??????

Also states it should be between quotes, there is only one, at the start. Am I missing one (at the end) also, the quote close?

Please just confirm and I'll crack on. many thanks guys.:)
[Touch Pro2, Tilt 2 Android Development] Dinky:
OK, I thought I messed up your .csv files and the ones from my phone, but I did not. And yes, I renamed the files to match the ones originally under /system/lib and /system/etc directories and changed their permissions. So, the test results still stand at this point. I got a AT&T Tilt2 and the bootloader screen shows Rhod300.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, if everything is in a folder you need to specify a rel_path=.

If you look at his modification, it does have quotes at the beginning and the end. Did you even bother to look at the startup.txt files that are provided in the bundle? :rolleyes:

Edit - now that I look, both lines appear to have an end quote. Not sure what you're talking about now.
[Touch Pro2, Tilt 2 Android Development] mgross029:
Thanks for the additional feedback... At least it is partially working for you...

Another option if you have the room on your sdcard is to put the original FRX07 bundle on it, create a new data.img or ext4 which every you are using. Then mount --bind the files from your user.conf file just to see if it works correctly. Not a big deal if you cannot do this, but it's something to try if you are able too...
[Touch Pro2, Tilt 2 Android Development] jonners59:
Don't worry arrrghhh, and many thanks

I just sorted it. I decided to take a look at the F6 Startup and look for differences and how I had added the path... Should have thought of that before.:o Maddening.:mad: Anyway done now and it works great. So many thanks for sticking by me.

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 force_cdma=0 pm.sleep_mode=1 physkeyboard=rhod100_uk rel_path=Android/FRX07"
boot

Next question is what is the best, easiest and quickest way to set it up like my F6 config?

I plan to set-up my Marketplace and re-download Titanium, then restore from there.... Will that work?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
That's all I do. Backup & restore with TB.
[Touch Pro2, Tilt 2 Android Development] jonners59:
I have just restored the apps + data... Should I also do the system backups I created? My concern is it might undo the new build in some way... I want to save myself time and work in putting the folders and apps back on the "desktop" and the email, etc settings

Thanks arrrghhh
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I typically just restore everything. Haven't had a (serious) problem with it yet. I can't remember the last issue I did have with it, IIRC it was pretty minor.
[Touch Pro2, Tilt 2 Android Development] abc321:
This build is running fast on my TP2 Rhod400. But, is there an option to make the end call button actually end calls? I remember this being an option in previous versions. I can't seem to find it in the Call Settings option.