yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] arrrghhh:
You're positive this is the layout you're requiring...?

Not to my knowledge. The only thing that determines the layout is that physkeyboard setting - hence why I think you might be choosing the wrong one. The RAPH layouts are kind of a mess, so it's pretty easy to mess up.
[Touch Pro, Fuze Android Development] bobzero:
Arrrghhh, I also have a CDMA RAPH800 and the keybord layout is exactly, button-for-button, the same as the layout now sitting in my RAPH110 phones.

They are physically the same size as well, just measured 8.7CM x 3CM. Button size is 7mm (14mm for shift, enter, and space). I'm quite certain I could peel out the RAPH800 layout and stick it into the RAPH110 and have fit perfectly.
[Touch Pro, Fuze Android Development] arrrghhh:
Ok, does that layout work? If your RAPH800 works, and it's the same layout... I assume you are following my logic here.
[Touch Pro, Fuze Android Development] bobzero:
I tested the RAPH800 with FRX07 package, but had to replace:

rootfs 4/16

kernel 6/22

in order to get it to boot.

key mapping works fine on the raph800 with 'physkeyboard=raph'. Again, in WinMo on the raph110, when I change the layout to Raph, all keys are working...

Going to try wiping the SD card again and starting fresh...
[Touch Pro, Fuze Android Development] arrrghhh:
Why did you go with such an ancient rootfs? Have you tried this setup on your RAPH110's?

You're going down the right path, just triage my man. Take it one step at a time and cover all bases... I'm here to help, but I can only do so much without a device...

Also I've talked to others with RAPH110, no problems with layout.
[Touch Pro, Fuze Android Development] bluenote73:
Because so far in this thread, he's the only one that supposedly got results.

And if you look here http://xdaforums.com/showpost.php?p=16001269&postcount=190 it looks like he was premature at announcing success.

I'm still trying to give some benefit of the doubt though, obviously there's a language barrier and who knows, maybe I'm just dense.
[Touch Pro, Fuze Android Development] arrrghhh:
Hrm... seems you're right. Bummer.

I need to find more time to work on this RAPH800 in my clutches...

Either way, the rest of what I said is still valid. I think we're going to need logs regardless, so does ADB come up before the OOPS error? If so great, get some logs.
[Touch Pro, Fuze Android Development] bluenote73:
I recently got a "real" android primary device, so my dabbling on the diamond is very much here and there. Took me a while to get around to doing the last round of testing, and I'm not knowledgeable about what it takes to get logging going, so it's kind of a motivation killer. I'll try to set aside the time to learn about it and retry with the latest files at some point.
[Touch Pro, Fuze Android Development] bobzero:
According to this post these are confirmed to work without the mismatch error on boot. Will try them on the raph110 shortly...

Are those other raph110 users using the stock fuze layout or did they also swap to the raph layout?

Also tried changing back to fuze keyboard setting in WinMo, no change in android.
[Touch Pro, Fuze Android Development] arrrghhh:
WinMo wouldn't have any effect whatsoever on Android in respect to this...

I would assume they're using the stock FUZE layout - stinebd has a Fuze in fact...
[Touch Pro, Fuze Android Development] bobzero:
I wouldn't think it could have any effect, but just to rule it out.

Even with the stock Fuze layout, it could be tested, if the user switches their startup.txt to 'physkeyboard=raph' and then presses FN key and the button circled below:

The output should be "+" but I'm getting "="

Here's the stock Touchpro RAPH100 for reference.

Just tested with 4/16 and 6/22 and it does not suffer the problem. Key mappings are correct on the RAPH110 with 'physkeyboard=raph', however, pressing the "CAPS" key still causes the "FN" LED to light up.

EDIT:

Looks like other RAPH100 users are experiencing the FN key problems with FRX07

http://xdaforums.com/showthread.php?t=1186941
[Touch Pro, Fuze Android Development] arrrghhh:
He said FN keys work... I don't know dude. I am not sure what to tell you.
[Touch Pro, Fuze Android Development] bobzero:
The first poster said:

The second poster who you're quoting was using the german raph layout.

After confirming 4/16, 6/22 was good, I wiped the SD and went back to 7/18, and 7/24 and the issue is back.

Looks like something broke somewhere after the 4/16, 6/22 rootfs/kernel.
[Touch Pro, Fuze Android Development] stinebd:
Please try with physkeyboard=raphfix
[Touch Pro, Fuze Android Development] bobzero:
Tried with the new 7/26 rootfs and changed to "raphfix" in startup.txt.

It fixes the FN combinations!

Thanks arrrghhh and stinebd, you guys are awesome and so quick :)

Still a few little quirks thought, such as:

-CAPS key turning on FN LED light, and not actually capitalizing anything.

-CTRL key has no effect. (would be nice to have a voice search shortcut if we have unused keys)

-SMS/TXT key does not open messaging app, seems to have no effect?

-EMAIL key outputs "@"

-SYM key doesn't do anything?

-Doesn't seem any key activates the CAPS LED light.

All minor stuff. Thanks again :)
[Touch Pro, Fuze Android Development] arrrghhh:
Did any of that stuff work before?

FYI, raphfix layout is now the raph layout in the new rootfs... that's all that was changed in the new rootfs. Evidently the regular 'raph' layout is broken... Sorry about that, I don't really follow why other than we don't have the source for that layout...
[Touch Pro, Fuze Android Development] bobzero:
I don't think those commands worked before with the 4/16 rootfs on the RAPH110. However, on the RAPH800 there is some different behaviour.

RAPH800 special keys:

-CAPS turns on the CAPS LED light, however still does not capitalize any letters.

-FN key does not turn on FN LED light, but otherwise works.

-CTRL key no effect?

-SMS key opens search window.

-EMAIL key outputs "@"

Also, applying to both RAPH800 and RAPH110,

-double tapping the shift key enables caps lock, but does not turn on the CAPS LED light.

-Pressing FN + Left arrow = "home" i.e. brings cursor to beginning of line.

-Pressing FN + Right arrow = "end" i.e. cursor to end of line.
[Touch Pro, Fuze Android Development] arrrghhh:
I think FN + Left/Right is 'expected behavior'.

I don't think the CTRL key does anything, except perhaps CTRL...

SMS key I think was mapped to search.

Caps/FN LED's do not work right for RAPH. They only partially work right for RHOD, only because they were hacked into the kernel to kinda work... there's no input from userland, so the kernel does its best to guess. I don't think anyone applied that 'fix' to RAPH.
[Touch Pro, Fuze Android Development] eugenbrl:
can't connect to computer via usb

hi!

anybody know why i can't connect to computer via usb (debugging)?

the problem persist with music gallery which says that can't read sd card

my internal storage is formatted as fat32, so i really don't know where is the problem.

diamond 100, frx 07
[Touch Pro, Fuze Android Development] arrrghhh:
ADB works great. Have you read the FAQ?
[Touch Pro, Fuze Android Development] ag_meiske:
How to make fast FRX07 in my HTC Diamond (Diam100).... please help me
[Touch Pro, Fuze Android Development] bobzero:
Had some data corruption issues. not sure if my sd card is to blame, but i thought i'd post this anyway.

the raph110 with frx07 + 7/26 and 7/18, had been up for 24 hours +, no sim card inserted, only wifi in use.

I started noticing that a program I was using would not open. I powered android off properly and then tried to boot back into it via haret. Haret froze after the 2 vibrations.

tried several times, and haret kept freezing after the 2 vibrations.

took the sd card out ran a scan disk, found some errors and corrected them. haret still freezing.

backed up sd card. formated card with sdcard.org formatting tool. recopied back up files. haret still freezing.

compared rootfs and system.ext2 with known good copies and found that their SHA-1 values did not match.

replaced all files except data.img, with non-corrupt versions. haret now boots. however i was having problems with programs force closing. I guess data.img was corrupted too.
[Touch Pro, Fuze Android Development] ZeRoX93:
Hi. I have a RAPH100 and I have been using FRX07 and the battery life was holding to 15h, standard using: SMS,Calling,little on the net :) so 15h not bad :D but it would be really great if the battery can hold much longer like 2days :D I'm hoping that one day it will be possible :D So guys good work :DDD
[Touch Pro, Fuze Android Development] czshf1:
click times limit

there is a limit for the screen click times in the common device but at this build(XDADROID FROX7 /FROYOB HERCULES....) miss it when play some game or run some programs we click the screen many times at one second then we stop it because lack of the click times limit the device will respond the command times as the result we have to wait the device achieve the lastest command to do the next work
[Touch Pro, Fuze Android Development] arrrghhh:
Why are you mixing the names of the builds? FRX07 is a different build than FroyoB "Hercules".

There are still random hiccups, seemingly related to iowait issues... Not sure if the SD cards can be blamed entirely, but I'm sure they're partially to blame. The other part is... this phone is old! It's got a processor that's from 2007... c'mon.
[Touch Pro, Fuze Android Development] ericdabbs:
I am getting the same thing on my CDMA Raph800 phone. FRX07 build will not boot up on my phone and I have tried many things to get it to work including updated the latest rootfs, zImage, modules, etc. I keep getting the "OOPS - smd_tty buffer mismatch?!" messages that loop over and over.

Please fix this issue because I would love to have FRX07 build over FRX06 build but as for now I have given up on trying to upgrade to FRX07.
[Touch Pro, Fuze Android Development] arrrghhh:
There doesn't seem to be a clear way to fix the issue. It seems no one with a CDMA RAPH/DIAM bothered to test the RIL, which was implemented months ago (first incarnation was like... April?)

So I'm sorry, but if no body pitches in to at least test with their device, then the development team can only do so much. They don't receive complaints, they continue moving on. Now that FRX07 is out, we're getting a bunch of complaints all at once - well, there was months of development that went into this build, and since no one helped test it's very poorly supported on these devices.

I don't like seeing devices fall behind, but truth be told there's only so many developers, and they focus on their device. A few have gotten other devices to try and help out, but that can only go so far.

So like I said - I am sorry, it's a shame to see a device fall that far behind... but there's just not many left, and without anyone actively testing this stuff as it's released, what do you expect? I worked very closely with the dev who build the RIL to get full CDMA and Sprint MMS support. I don't even care about MMS, but I knew I needed to pitch in and help or it would just be left out to pasture. It seems DIAM500/RAPH800's have been left out to pasture... The old stuff will always work, but it's going to be a tough road ahead.
[Touch Pro, Fuze Android Development] sabrosolatino:
How can we help better???

Thanks Arrrghhh Really appreciate for all the time you have dedicated to this.

So, how can we help???

I have been reporting since May 23 what version works and what not in the Diam500 CDMA Thread for Xandroid.

I have been writing in the kernel webpage what I had found in Diam500 with each version.

But maybe I have been doing bad my effort to help and maybe someone can explain How can we help better and unit effort to help.

So, how can we help better???

Best Regards Sa6r0s0latino
[Touch Pro, Fuze Android Development] czshf1:
i mean that frx07 & froyob her v4 final both have this problem
[Touch Pro, Fuze Android Development] arrrghhh:
Well triage. That's really what I need... I need to know what works on FRX07. Was it the RIL where things started going awry? What piece is causing these issues? Is there a combination of files that work with FRX07? I think you said you found some that worked, then blew up later? I'm not sure what's going on with the poor CDMA RAPH/DIAM's, but they seriously have fallen behind. I don't know how easily it'll be to get your devices back up to speed - like I said, there's a long road ahead for these devices unless a dev takes up the cause. About the best non-dev's can hope for is triage, and direction as to what works. I will do my best to get the developers to sort out the 'why' it doesn't work, and hopefully fix it... No promises, but this is how it works. Either a dev takes it upon themselves and fixes something, or a user points them in the direction, with logs, feedback, etc - and assuming they have the free time, they try to tackle the issue for that user. I'm no dev - but I've helped fix many bugs by working closely with the developers. Like I said before, this is probably one of the main reasons MMS works at all for Sprint on our port.

It's a kernel issue, so any build using the newer kernels will throw that OOPS SMD_TTY error...
[Touch Pro, Fuze Android Development] kostas1987:
thanks to all the developers on FRX07...

i have the latest frx07 but still no more than 10 hours stand by time please work on that and also the draining of the battery during a call.
[Touch Pro, Fuze Android Development] arrrghhh:
Yea, we'll get right on that :rolleyes:.

I've already stated why battery life is so poor, and it's a kernel issue. A new build won't magically fix it. Same with drain, the battery meter is a little wonky - and that again is a kernel issue. None of this will get fixed with a new build, only kernel patches. Patches are, as always, welcome.
[Touch Pro, Fuze Android Development] zavelevsky:
Many many thanks (!!) and only one question

Please forgive me if this is a beginner's question or if it was already answered (searched the FAQ section).

I did my best to follow the instructions - and after I run haret.exe everything seems to work fine.

However, after I restart my phone it still boots to the WM OS and I need to run haret.exe again.

Is this the correct work mode? Must one OS load in order to run the other?

Thanks!
[Touch Pro, Fuze Android Development] arrrghhh:
Yes of course. You didn't flash anything, you installed everything to the SD card... so where do you think WinMo went?!?? Nowhere. WinMo is still there, so yes - when you reboot it goes to WinMo, and you have to run HaRET again to boot Android.
[Touch Pro, Fuze Android Development] sabrosolatino:
We have to unify efforts.

Ok, I will try to compile all the info I know About what version had function and what not in CDMA HTC DIAM500.

By the way, I think I read in some of your posts that you say that if "ADB" had started it is posible to make a "log".

How can we made the "logs" that registier the Boot secuention error???

I have never use ADB but I imagine is something similar to a terminal (like in linux)?
[Touch Pro, Fuze Android Development] arrrghhh:
Well it really depends on when it's failing. If it fails before the adb service is up, we'll have to look at LAST_KMSG logs, or perhaps shoehorn in some logs in the init or something... If we have to cross that bridge, we will.
[Touch Pro, Fuze Android Development] bluenote73:
I think you're being a little unfair and mischaracterizing what's gone on by saying "nobody bothered to test" aargh. The builds you put out get feedback, the kernels get feedback (and there's some facility for it on the webpage) But other than that, the other build mechanisms don't allow for any feedback, nor do they, as far as I know, give the user any information on what's changed. Making it much less likely for any testing to happen.

Chastising raph/diam CDMA users for not testing something that was never advertised as far as I can tell seems a little like adding insult to injury into the bargain.

To me the first step is to get this smd_tty error fixed, don't you think? And I think someone may have submitted the logs necessary?

If that gets fixed, then I think it becomes much more possible to test other pieces one by one to identify change points. Where is the RIL contained, if you dont mind me asking? I guess that would be next.

thanks
[Touch Pro, Fuze Android Development] arrrghhh:
No one hangs out in IRC chat to offer to help with a CDMA DIAM/RAPH. So therefore, we had no one testing anything with us... that's really the only reason I got to be lead tester. I hung out in chat and proved that I could help with at least that. Being a good tester all you really have to be good at is ruling out your own user-error to make sure it really is a bug :p.

At any rate, the new RIL was released in April, with testing starting in February. FRX07 was the first time anyone with a CDMA RAPH/DIAM reported issues with the RIL. Now in your defense, there was no RIL testing thread in the RAPH section, it was in the RHOD section... but the RIL was put into the rootfs in April... no complaints. That's really the issue.

There's also a bugtracker - that's really where bugs get reported/triaged. Again, nothing there..

As for the RIL location, it used to be in the rootfs, and now it is in the system image. A lot changed with FRX07, but a lot of that was changed based on the assumption that the underlying stuff worked on all phones, including CDMA RAPH/DIAM's.

The smd_tty issue is a whole 'nother issue altogether, which it was known that was an issue early on. That was a pretty recent commit, and not nearly as big of a deal as the RIL issue. That's tantamount, and again NOT new by any means. I'm honestly surprised that not one CDMA RAPH/DIAM user didn't update to the new rootfs and say something - somewhere - I know this project isn't the most organized since there are so many potential venues to report issues - but that's also the point, there's a ton of places to submit problems and ask questions. I don't remember a peep about the RIL at all since it was put into the rootfs in April.

The moral of my story - for better or worse, there haven't been many CDMA RAPH/DIAM users around that work with the devs... or are devs themselves. Devices will fall behind if they aren't actively worked on... perhaps this port supports too many dis-contiguous devices, but I'm doing my best to help your devices stay relevant in our port. However, if you guys don't pitch in... then your device will fall behind. It's as simple as that. I'm not mis-characterizing, just stating facts.
[Touch Pro, Fuze Android Development] bluenote73:
Let's just say that, I've seen quite a few interested parties, so I think feedback really just needs to be asked for and directed.

The question is, where do we go from here. What do you need to provide the devs to get the CDMA devices back in the fold? Or do we just call it quits, find the newest stuff that works roll that into a package and call it done?
[Touch Pro, Fuze Android Development] arrrghhh:
I'm working with hyc to figure out the issues with the RIL. I have a RAPH800 and have started making progress, but it's slow.
[Touch Pro, Fuze Android Development] sabrosolatino:
This is Random!!! (Say it as "300" movies "This is Sparta" including the Kick)

I need more time to compile all my test to qive a brief.

The ENDLESS loop "OOps mismatch error message" appear in the area just after the

CAPITAL LETTER "X D A N D R O I D" appears.

There are some more lines of commands (after the capitals letters):

in the fourth line it apear de ADB command and then tree more lines of TABLE, the third one said "ip-table" and then the loop error message.

When the loop pass the 350 line it becomes ENDLESS loop,

If you are lucky the loop between line 160 or 270 line goes into the "XDAndroid boot Animation"

The one (combination) I'm testing now it bootup successfully but it is too laggy (slow and erratic and some FC or reboot)

but after this one there was one that was not laggy at all but I CAN'T never bootup that one again.

This is really random!!!

NOTE: Since FRx07 everytime I first bootup XDAndroid there is no more "FILE App" (Like an "Explorer" for folders and Files) which makes really hard to start installing Apps. With FRx06 was a "FILE App" preinstalled.
[Touch Pro, Fuze Android Development] arrrghhh:
FRX06 didn't have a file manager out of the box. You can install apps thru the AndroidApps folder, read the FAQ.

There's many issues we're dealing with on these old phones. Please, be patient. We're making progress.
[Touch Pro, Fuze Android Development] sabrosolatino:
New confirmation.

I already know that If I drop an APK file in "AndroidApps" folder it will autoinstall next bootup,

but because a lot of combination I'm trying they only allow me to bootup just the first bootup it is hard to try install Apps later. And I don't want to put more variables (noises) to the data.img building at First bootup.

I think I'm getting old (with my memory) was GBxAlpha1 which has "File Apps" out of the box???

Then I think I have been using a while the gingerbread package and only replace the system2, initrd, rootFS and Kernels files. and I remmeber that since FRx07 package the HARET.exe was the same that GBxAplha1 that was not the same that the haret.exe that came in FRx06.

Just in case this make any difference because a lot of people report they can never bootup there HTC Diam500 CDMA and I can bootup at least the first bootup in almost each one.

Update: I'm out of battery. NOW I can confirm what someone else said,

I have tried today one combination (July 21th) and I can bootup first and second time.

Third, fourth, fifth and sixth time was the endless loop error message.

The seventh bootup time was successfull to bootup the eigth too. but the nineth bootup time again the endless loop.

So this is more than weird.

I was almost sure that some setting writed in the first bootup was the reazon why can't bootup later but this confirm this is not the case.

Update.2:

Anyone with CDMA Diam/Raph try this BETA FIX

Go to the BETA FIX thread

Thanks again Arrrghhhh!!!!
[Touch Pro, Fuze Android Development] arrrghhh:
np, thank hyc - he did the heavy lifting. He sorted out what was wrong, why stuff was blowing up.. and fixed it! Kudos to hyc. He was also working on the smd_tty error, and I think he put up a test kernel that hopefully fixes that bug as well... I have yet to test it tho. More info on that once I do ;).
[Touch Pro, Fuze Android Development] bluenote73:
Holy **** this is great news, thanks to you both. Ill try whats avail tomorrow.
[Touch Pro, Fuze Android Development] arrrghhh:
Heh, indeed. There's also a fix for the smd_tty bug, newest autobuild kernel has the fix ;).
[Touch Pro, Fuze Android Development] sabrosolatino:
EAGLE "ONE BIG STEP", BUT creapy Green BOTs make me dead at Locked

OK GOOD NEWS & BAD NEWS!!!!

NEW KERNEL August/5/2011 FIXED the "OOps smd-tty- mismatch message" error. By the way, that "message error" appeared just after the line where the command "IP_TABLE" was run. I'm using the HYC "RIL LIB*** config.user FIX"

But NOW again "XDAndroid BOOTANIMATION" get really laggy and animation stop several times. Device bootup succesfully, but it is really slow and erratic. Device goes Alone (without open any Apps) to black screen in less than 10seconds (as SOD) and finally after waiting and waiting pressing the power button it appear the "Lock Screen" which is UNLOCKEABLE this time. I will try with other RootFS.

Arrrghhhh do you know WHO makes the new Kernel?????

Was Hyc????

THANKS Hyc for the FIXED "OOps"!!!!!
[Touch Pro, Fuze Android Development] yozart:
hello guys, I was wondering if it is possible to install this on the nand? If yes, is there a tuto somewhere? thank you.