yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] mtl010957:
I have similar behavior with RAPH110, except it does not seem to keep the keyboard lights on all the time when closed, but they do blink on briefly and then go out when the keyboard is opened.

Other than that minor issue this build is much better than FRX06 and more stable, especially when in weak cell signal areas and while moving from cell to cell. Many thanks to the devs! :)

UPDATE: I just found quite by accident that the keyboard lights will come on if you swipe a finger over the capacitive panel to light up one or more of the switches there (place where the Home, Back, Hangup, etc. keys are) when the keyboard is open. Not sure if this is the intended operation but it seems to be a viable workaround.
[Touch Pro, Fuze Android Development] dsramesh:
Thanks! It works well!

Been using FRX07 since this evening and working well. Kind of slow and sometimes quick.

Data works, camera works, wifi works.

Has problems waking up from sleep and just now, it went to sleep during download and can't wake it up and have solid red light.

- Called the phone multiple time to wake it up and it did not wake up....resetting the device.

..Ramesh

Works
[Touch Pro, Fuze Android Development] jimjack:
Hi,

here is my experience with FRX07.

My device is DIAM100 / MDA Compact IV. With 07/11-kernel und newest rootfs it boots up to Android and then reboots like by others. Then I go to 06/27-kernel und newest rootfs and all works quite well especially the wifi wakeup-bug. Sometimes ists a little bit slow. Sometimes ists okay.

The next days I will test the newest 07/18-kernel.

With regards,

Steffen
[Touch Pro, Fuze Android Development] colinkhalid:
RAPH 300 working well

I found that I do not get the andriod.core crashes I used to get a lot with FRX06. The Wifi issue seems to be solved and BT pairs and sends data. Overall more stable.

The speaker does not work in call , (didn't with FRX06 also)

The battery drain is heavy due to the panel collapse problem but Iam still able to use andriod full time since I drive around a lot and nearly always have the phone on charge :D
[Touch Pro, Fuze Android Development] Marmen:
How long will it take to flash FRX07 and first boot? (it takes 2hours on my device)

I try to use this release with my Touch Diamond2, but it fails.

Always on the welcome screen during the first boot. I have to restart after half an hour, and it was back to WM automatically.

What happened and how to resolve?

I strictly follow the step:

1) format SD Card to FAT32

2) Extract & Copy to Root of SD Card

3) Copy TOPAZ startup.txt to the Root.

4) Run Haret.exe
[Touch Pro, Fuze Android Development] arrrghhh:
Need to grab the newest kernel. Unfortunately the kernel bundled in FRX07 does not work on keyboardless devices...

I guess I need to create an FRX07 thread in the TOPA section too eh?
[Touch Pro, Fuze Android Development] Marmen:
I do think it's necessary, please proceed :p

btw: latest kernel, is it: htc-msm-linux @ 20110718_223029 on http://glemsom.users.anapnea.net/android2/htc-msm-linux/?

Thanks.
[Touch Pro, Fuze Android Development] Marmen:
Could you first show me a brief guide, I'm waiting online, deeply thanks.

;)
[Touch Pro, Fuze Android Development] arrrghhh:
Brief guide to...? Updating the kernel?

Oy... It's in the first post...

http://xdandroid.com/wiki/Incremental_Updates
[Touch Pro, Fuze Android Development] Marmen:
Thanks, follow the steps and update the kernel accordingly, as per attached.

I will let you know the outcome once I complete flash FRX07.

;)
[Touch Pro, Fuze Android Development] jimjack:
Hi,

here is my feedback about 7/18-kernel with DIAM100 device (German MDA Compact IV) and FRX07 with newest rootfs.

This kernel runs! There is no reboot after the Android start screen. Thats fine and many thanks to the developers!

WLAN is okay also after standby.

BT is also okay. I do a pairing with my Symbian mobile (Nokia 6710 Navigator). But I can't send data from/to the Android

device. After trying to send data there is a problem with BT. It toggle on/off and I must reboot the device.

The second try was okay! Problem was the app "Bluetooth File Transfer". It toggles BT on/off.

:-)
[Touch Pro, Fuze Android Development] GoldAngelo:
The battery works better than on FRX06.

I have the same problem with RAPH100

And Some special characters on the keyboard are swapped with each other. For example, -->"<-- to --> : <--
[Touch Pro, Fuze Android Development] soccermonster5:
On my RHOD400, I noticed that some apps were failing to install with FRX07 + kernel 2011/07/16. I found the following errors w/logcat:

D/VoldCmdListener( 1308): asec list
I/PackageHelper( 2250): Size of container 2 MB 86286 bytes
D/VoldCmdListener( 1308): asec create smdl2tmp1 2 fat {} 10037
E/Vold ( 1308): Error creating imagefile (Read-only file system)
E/Vold ( 1308): ASEC image file creation failed (Read-only file system)
W/Vold ( 1308): Returning OperationFailed - no handler for errno 30
E/PackageHelper( 2250): Failed to create secure container smdl2tmp1
E/DefContainer( 2250): Failed to create container smdl2tmp1
D/dalvikvm( 1340): GC_EXPLICIT freed 11853 objects / 540880 bytes in 220ms
D/vending ( 1851): [6] LocalAssetDatabase.notifyListener(): -8230287241840907289 / INSTALL_FAILED

It would appear that the installer for these apps was trying to create a file, /mnt/secure/asec/smdl2tmp1.asec but because / was mounted read-only it couldn't do so. I was able to get them to install by remounting / as rw.
[Touch Pro, Fuze Android Development] arrrghhh:
This is a super-user issue... It didn't prompt on install? Several people have had that issue.. I don't know why apps wouldn't be prompting for su on install tho...
[Touch Pro, Fuze Android Development] soccermonster5:
No, no prompt whatsoever. I haven't had a su prompt for the installation of any of my apps. Just an "installation unsuccessful" error, but only for a select few; most install fine. I just wish Google would be a bit more descriptive of the error so I didn't have to resort to adb/logcat.
[Touch Pro, Fuze Android Development] sabrosolatino:
Yeahh now is working!!!!!!!!!!!!

Hello Arrrghhh,

Thanks thanks Thanks and all the FULL recognition for the DEVS of this RELEASE.

With the New Kernel and Rootfs is working and booting VERY WELL!!!!!!!!!!!!!!!!!!!!! :)

I use HTC Diamond 500 CDMA

and the ACTUAL FROYO FRX07 (21 July 2011) LIST of Roofts, initrd, zImage, module and System-ext2 that are working fine with my HTC Diamond CDMA is:

1.- System-ext2 (15-July-2011) FroyoX07 (Froyo)

2.- I USE THE LATEST ROOTFS (with the NEW RIL) Rootfs-20110721-258e98b.zip (21-July-2011) at First boot up (with clean data-img) it appear the endless "tts mismatch" but after a minute or two it appear the Xandroid boot Animation this time the video doesn't freze at all!!!!!!!!!! and after the long "data.img" re-creation (5-7 minutes) it boot up OK. NO lockscreen this time so I can start using it without a problem

Rootfs-20110721-258e98b.zip

3.- initrd-20110429-a3eace0.gz (29-April-2011 file is the same a 15-July-2011)

4.- zImage and Kernel module htc-msm-linux @ 20110718_223029-package.tar (18-July-2011)

NOTE: Don't use the 27-June-2011; 11-July-2011 versions( htc-msm-linux @ xxxx-package.tar) Because endless mismatch messages starts with the second boot XDAndroid.

By the way, the "July-16-2011" version has the issue of get stuck after boot time in the First "LOCKSCREEN".
[Touch Pro, Fuze Android Development] roloracer:
Awesome, gonna dust off the fuse and give this a run, can't wait to see how much better it has become from when I used it before.
[Touch Pro, Fuze Android Development] colinkhalid:
Video Playback on RAPH 300

Not having a lot of success playing video clips with the FRX07 build

I rendered some clips using Handbrake (using iphone / ipod touch presets) but although the sound was ok I only got a single frame from the video using the built in player.

Can anyone recommend a suitable media player and the correct codec, resolution, bit rate ect I should use.

I found that YouTube video has the same issue sound but no video

Thanks
[Touch Pro, Fuze Android Development] arrrghhh:
HQ video's don't work at this time. We're trying to figure out if some codecs are missing - hyc got a certain resolution working, but I'm not sure how it applies to RAPH...
[Touch Pro, Fuze Android Development] colinkhalid:
Market error 81
[Touch Pro, Fuze Android Development] arrrghhh:
This actually isn't a super user issue! Sorry guys. Need the newest rootfs...

See stinebd's post for more info!

I just posted a fix ^^
[Touch Pro, Fuze Android Development] ruben1221:
I am happy to hear this has been a success for all devs and users. I was a TP user for a long while, then I sold it to get an Evo. Still a great phone I owned. But enjoy the Android on the WM phone. I remebered when it was just the start of things, and now that its finished, that my friends is Awesome! Just throwing stuff out there to the Devs and Testers... :cool:
[Touch Pro, Fuze Android Development] maoren99:
Will installing this 'reactivate' my sprint phone?

I'm very tempted to install this on my 2-year-old sprint TP, but I have a dumb question:

Since Sprint starts to charge that $10 premium data fee even for 3G phones activated after a certain date, I'm wondering whether install this will somehow 'reactivate' my phone.

I once had a problem with my 3G connection and the Sprint people let me do some reset work on my phone and that counted as a reactivation, and I started to see that $10 fee appear on my bill. I had to call in again to have it rectified...
[Touch Pro, Fuze Android Development] arrrghhh:
I would think reactivating the phone is a very intentional process, but I have no clue. I would call Sprint to verify - ask them if simply turning on the phone and having it connect will activate it - I seriously doubt that it will (I have a couple of tester devices from Sprint that are deactivated, and it just doesn't let me call out/connect to data. I would assume the same would happen with your device.

Can't be sure unless you contact the provider tho.
[Touch Pro, Fuze Android Development] Deonix:
battery?

Congrats for the complete port.

How long does the battery lasts with normal phone use?
[Touch Pro, Fuze Android Development] arrrghhh:
Depends on usage (obviously). Why not try and see for yourself? It's a very subjective thing, how long the battery lasts...
[Touch Pro, Fuze Android Development] maoren99:
I'm getting an infinite "OOPS - smd_tty_buffer mismatch?!" message, what could be wrong?

Phone is RAPH800 (Sprint CDMA Touch Pro).
[Touch Pro, Fuze Android Development] arrrghhh:
Did you happen to read the caveat list?

Or search the thread!??!

It seems 20110622 is the last kernel that would work for you CDMA RAPH/DIAM folk. Most have reported serious sluggishness - I can't even get an old RAPH800 to boot at all, so there's something messed up with my tester RAPH... I need you guys to troubleshoot, triage, and help out...
[Touch Pro, Fuze Android Development] indresh88:
Live wallpapers

Great!!!!! everything works fine.....the bedt android here for raphael.....bluetooth a2dp is working also...

But can somebody tell me how to install live wallpapers?
[Touch Pro, Fuze Android Development] Larry94:
Since this phone is so old. can it be activated on verizon with a feature phone data plan? And can anyone hook me up with a web site where I can buy one? How much do these run money wise?
[Touch Pro, Fuze Android Development] elmanortega:
amazing will donate for sure

keep it up man
[Touch Pro, Fuze Android Development] arrrghhh:
This is the Development section. Please don't post stuff like that in the dev section.
[Touch Pro, Fuze Android Development] krish_nank:
Hi indresh-

Can you please write down the combination of Kernel and other stuff you are using . With newer build i don't know what causing my phone dialer page and other places look distorted.(I mean looks like Un ported resolution ) . If i go to older kernels also concern not getting resolved.
[Touch Pro, Fuze Android Development] sheennick123456:
maybe you have changed LCD density value in startup config
[Touch Pro, Fuze Android Development] nee_vak:
not useable for raph800.

the ts calibration file didnt work, so made a new one using 2010 kernel per instructions. Boots up fine, but incredibly slow at changing menus. Also didnt seem to connect to sprint network at all. Went back to 6-22 kernel, not any better, still no network (unchecking airplane mode just leaves it that setting hanging trying to find network).

Anyone else able to get it working for daily use?
[Touch Pro, Fuze Android Development] arrrghhh:
Did you try any other kernels? Have you tried 1276? (Kernel bundled with FRX06).

Seems not many folks left with CDMA RAPH/DIAM's... Trying to keep from your devices from falling behind, but they are starting to...
[Touch Pro, Fuze Android Development] elmanortega:
dont stop man
[Touch Pro, Fuze Android Development] dsramesh:
RHOD500: I tried the latest and went back to July 16 build of kernels and rootfs but what used to work "Fancy Widgets" is no longer working and can't figure out why it is doing a Force close.

Any idea?

Also tried to launch Live Wallpaper and it also does force close. I thought the hw3d is on by default and tried with hw3d_force=1 and same result.

Thanks!

..Ramesh
[Touch Pro, Fuze Android Development] arrrghhh:
First, I keep seeing you post in the RAPH section.

Try posting in the RHOD section, thanks...

As for hw3d, that is now "forced" - you can't turn it on or off with a startup.txt command, the hw3d command is deprecated. Your Live Wallpapers is not related to hw3d, but I don't know what it is related to... sorry. No clue on Fancy Widget either - I use Fancy Widget Pro no problems.
[Touch Pro, Fuze Android Development] dsramesh:
Sorry, I had the wrong link and I will change it to Rhod.

Thanks for the input!

..Ramesh
[Touch Pro, Fuze Android Development] bluenote73:
On my DIAM500 -

First- taking just system.ext2 and kernel 06/22 along with the rest of my old good files (sorry, I dunno what versions) worked OK.

Now I'm trying sabrolatino's combination , mainly newest rootfs.img and latest kernel as changes, I'll report back on that one. I had tested the latest kernel, but rebooted the phone as soon as I saw the "smd_tty" errors. But since he says they go away, I'll be more patient this time.

EDIT: So far smd_tty error message does indeed seem endless. Its been about 7 minutes so far repeating.

EDIT2: I called it at about 12 minutes with the smd_tty error still repeating.

After a very long 2nd reboot, it does seem to be working, although its still quite slow. We'll let it settle and reboot once more and report back.

EDIT3: And the third reboot is now endlessly smd_tty erroring for whats been several minutes now. Regardless of if it comes back, this isn't useable.
[Touch Pro, Fuze Android Development] krish_nank:
Thank you bro it worked for me.... another doubt is as there is no access to sd card, unable to install new application.... any idea???
[Touch Pro, Fuze Android Development] jb789:
I know this should be obvious, but I have to ask- do you think your Raph800 boot failure could be an SD card issue?
[Touch Pro, Fuze Android Development] arrrghhh:
Format your card using the HP Tool. Full format, FAT32.

Feel free to backup everything on the card & restore after the format, or start fresh. Your decision.

Well I've only tried one card... But this card works in my RHOD. I was going to do that, haven't had much time unfortunately...
[Touch Pro, Fuze Android Development] tmpid:
Never mind. The developers did a great job. Big thanks to them.
[Touch Pro, Fuze Android Development] daeinnor:
You're better off. My Raph keyboard lights won't go off even with physical keyboard in closed position. :(
[Touch Pro, Fuze Android Development] daeinnor:
Thanks. Auto brightness ticked is the culprit. Disabling it as you said turns off lcd screen totally on standby. :)
[Touch Pro, Fuze Android Development] mightycouger:
I'm having the exact same issue with my CDMA Raph800! I hope the developer can get this worked out, it would bring new life to one of my favorite phones!
[Touch Pro, Fuze Android Development] arrrghhh:
So has anyone managed to use the new RIL on the RAPH800 or DIAM500?
[Touch Pro, Fuze Android Development] AF_624:
:D

this is the most fast and stable version of xandroid that i've ever try on my diam 100! i only had to change kernel and every thing that i tryed until now works well...i will try it for dailly use!

thanks to everyone who make it possible!
[Touch Pro, Fuze Android Development] sabrosolatino:
HTC DIAMOND 500 CDMA with XDANDROID

Hello Arrrghhh,

NOTE.1: Arrrghhhh I have noticed that the endless "Oppss mismatch error" start At the 4th line After the WORD in big CAPITAL of X A N D R O I D appear it. The 4th line is when start de ADB command. Hope this mean something for the DEVs.

Thanks thanks Thanks and all the FULL recognition for the DEVS of this RELEASE.

The new RootFS (24-July-2011) makes the New Kernel work a lot better, (lately was too slow, now is normal !!!!!!!!!!!!!!! :)

I use HTC Diamond 500 CDMA

and the ACTUAL FROYO FRX07 (25 July 2011) LIST of Roofts, initrd, zImage, module and System-ext2 that are working fine with my HTC Diamond CDMA is:

1.- System-ext2 (15-July-2011) FroyoX07 (Froyo)

2.- I USE THE LATEST ROOTFS (with the NEW RIL) Rootfs-20110724-1c4d02f.zip (24-July-2011) at First boot up (with clean data-img and Erase all Xandroid old folders, IF YOU ONLY ERASE DATA-IMG the bootup will go to an endlesss mismatch error message!!!!!!) it appear the endless "tts mismatch" but after a minute or two at line "160.-" aprox. it appear the Xandroid boot Animation this time the video doesn't freze at all!!!!!!!!!! and after the long "data.img" re-creation (5-7 minutes) it boot up OK. NO lockscreen this time so I can start using it without a problem

Rootfs-20110724-1c4d02f.zip (24-July-2011)

3.- initrd-20110429-a3eace0.gz (29-April-2011 file is the same a 15-July-2011)

4.- zImage and Kernel module htc-msm-linux @ 20110718_223029-package.tar (18-July-2011)

NOTE.2: Don't use the 27-June-2011; 11-July-2011 versions( htc-msm-linux @ xxxx-package.tar) Because endless mismatch messages starts with the second boot XDAndroid.

By the way, the "July-16-2011" version has the issue of get stuck after boot time in the First "LOCKSCREEN".
[Touch Pro, Fuze Android Development] arrrghhh:
Quite a colorful post! Seems the newest files work on your DIAM500 - so that's good news! I'll see what's up with this 800 I have here...
[Touch Pro, Fuze Android Development] bobzero:
got some time to play with frx07 on two at&t RAPH110 with RAPH100 keyboard layouts (so I use the RAPH100 startup.txt).

1) Some characters on the hardware keyboard are not correctly mapped.

Here is a list I made:

key press = result

sms key = do nothing

mail key = @

mail key + FN key = 0

caps lock key = turns on "FN" LED, and does not capitalize all following letter presses.

FN key + "=" = "=", should be "+"

pretty much all "FN key + 'x key'" commands will result in the wrong character being input. Except for the top row, the top row is correct, except for the "=" key as mentioned above.

2) As mentioned by others, speaker phone is not working.

3) The extra PTT (push to talk) button on the RAPH110 is going to waste, anyway to assign this key to do something?

Using:

htc-msm-linux @ 20110718_223029

rootfs-20110724-1c4d02f.zip

everything else stock frx07.
[Touch Pro, Fuze Android Development] arrrghhh:
1. Why are you using the wrong startup.txt? I don't understand how a RAPH110 can have a 100 layout... Use the correct startup.txt, and keyboard layout should be fine.

2. Speakerphone works on my RHOD, I'll have to confirm if this is a RAPH-specific bug.

3. You can remap it, modify the rootfs. I won't get into details here... Since that's the only RAPH with that button, it seems to have been neglected. Not sure if there's an app to easily remap buttons, but it seems we'll need one - I'm sure some people will want it to be search, others will want it to work the cam...
[Touch Pro, Fuze Android Development] bobzero:
The only difference that I can see between the RAPH100 and RAPH110 startup.txt is that the 100 sets keyboard layout to raph keyboard layout, and the 110 sets it to fuze keyboard layout.

i.e.

RAPH100

physkeyboard=raph

RAPH110

physkeyboard=fuze

I have replaced my physical stock fuze (raph110) keyboards with touch pro (raph100) keyboards, so that is why I use the other startup.txt. The keyboard itself is just a rubber sticker that can be peeled off and on, with no electronics...

Does the "physkeyboard=raph" command have any other effects that could explain the weird mapping?
[Touch Pro, Fuze Android Development] arrrghhh:
I don't know if we can support that kind of change... I would assume the actual buttons are different, and it's more than just a sticker dude. Do you have issues in WinMo?
[Touch Pro, Fuze Android Development] bobzero:
It's literally just a rubber sheet with adhesive. when you press on a key, it presses down on a switch underneath the rubber sheet. I'll see if I can find a picture.

In winMO there is no problem, there is a small program that allows you to switch between fuze and touch pro layouts. all keys work fine.

EDIT:

here are some pictures of the rubber keyboard sheet removed:

http://xdaforums.com/showpost.php?p=3377913&postcount=13

Note that the clear plastic you see around the keyboard peels off, it's only purpose is to keep the adhesive free of debris.
[Touch Pro, Fuze Android Development] arrrghhh:
Well then I don't see an issue. Assuming you know that's the layout you have, changing physkeyboard is all you need to do.

If it doesn't work then a) you've done something wrong or b) there really is an issue, in which case I'd imagine people would complain.

Do you have issues using the RAPH110 layout...? It seems to me if it's just an overlay, you're not actually changing the buttons underneath...
[Touch Pro, Fuze Android Development] bluenote73:
Would you mind posting a screenshot of your about phone with the vers#'s? I wasn't able to reproduce your results, and sounds like a few other people also had the same problems. It would give me the motivation to try and duplicate your success.. thanks
[Touch Pro, Fuze Android Development] arrrghhh:
He pointed directly to the files - you're saying using those exact files he linked to it doesn't work...?
[Touch Pro, Fuze Android Development] bluenote73:
Exactly. (from previous post). Another previous poster sounded the same too. Mistakes do happen of course, so I'm willing to try again if necessary, but I'm not eager to do it.
[Touch Pro, Fuze Android Development] arrrghhh:
Well I don't see how screenshots would help you...

If that combination didn't work, I'm not sure. I don't have a DIAM500 to test on, the only CDMA device I have is a RHOD400 and a RAPH800. I can't get the durn RAPH to boot at all, so all I really have to test with is a RHOD400... sorry. I need you guys to figure out which combo works. If nothing works... logs are obviously going to be required. I think logs are going to be necessary anyways, does ADB come up before you get the OOPS error?
[Touch Pro, Fuze Android Development] bobzero:
The Fuze layout is awkward, that's why a good number of fuze users replaced the stock layout with the Raph layout.

I changed 'physkeyboard=fuze' without changing the physical layout and all the buttons seemed to work where they should be.

Changing it back to 'physkeyboard=raph' and again the buttons are not all mapped correctly.

I'm not sure what I could have done wrong. I started with a an empty 1gb sd card, and copied the frx07 contents to the root. Put the newer kernel and rootfs, and booted it up.

I have two raph110 and both behave the same way.

Anyone else with a raph100 (ordinary Touch Pro) who can test the following button combo?

Press FN key + the "=" key and tell us what the output is. It should be the "+" symbol, but on both of my devices it outputs "="

Thank you

arrrghhh, could there be a check somwhere else that is detecting my phone as a raph110 and thus forcing some sort of key mapping conflict?