yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] relaxxrr:
seems working good, calling, youtube.

Camera light doesn't work

When calling, and want turn on speaker, it uses only my ear speaker with increased volume, instead of main speaker in rear of a phone.
[Touch Pro, Fuze Android Development] arrrghhh:
Speakerphone is busted for RAPH. The new acoustic code will hopefully resolve those issues, however it's not ready for a general release. I've already tested it on my RAPH800, and it works quite well.
[Touch Pro, Fuze Android Development] relaxxrr:
what about vibration when phone is in mute? tried calling (with no sound), but no vibration, but it's not a big deal.

Awsome job!
[Touch Pro, Fuze Android Development] arrrghhh:
Is the phone set to "Vibrate Always"?
[Touch Pro, Fuze Android Development] relaxxrr:
Yes. And, it's normal, when screan goes black center button diode blinks time to time?
[Touch Pro, Fuze Android Development] arrrghhh:
That's to indicate sleep state. Update to the newest kernel/rootfs, it *should* go back to "normal".
[Touch Pro, Fuze Android Development] klooher:
You are awesome guy! You said u would make startup for raph300 and u made it. Thanks!

@edit

i was happy too fast. still doesnt work for me. error " activity launcher (blablablablbla) is not responding " error after turning the phone on, i cant close it , therefore i cant use android
[Touch Pro, Fuze Android Development] arrrghhh:
You can't close it...?

Keep in mind, when the phone boots up its doing many things. So you might get a FC or two... You can either a) be more patient or b) try to hit FC on them all frantically and hope. I would recommend option A.

If that fails, delete your data.img and start over. Be patient - after the lock screen even, LET IT SIT!

If you're still having issues, perhaps they're touchscreen related? Delete your ts-calibration file and follow the directions in the first post to manually calibrate.
[Touch Pro, Fuze Android Development] klooher:
Formatting the card helped, now it works but its pretty slow tbh, still thats great that i can check how android works :)
[Touch Pro, Fuze Android Development] arrrghhh:
The hardware isn't exactly new. See my Speed Improvements thread. The most helpful piece by far was the memory management - on the SuperCharger script, try option #11 - MegaRAM #1. Helps out quite a bit.
[Touch Pro, Fuze Android Development] KrS14:
Raph800 Jjust tried the full install. No data at all even after a few reboots, On Bell in Canada.
[Touch Pro, Fuze Android Development] arrrghhh:
Crap... I forgot to include it in the caveat list, read this thread for more information.

TL;DR - your radios are old. The new RIL isn't capable of handling your older radios properly..
[Touch Pro, Fuze Android Development] ZoneBlaze:
Youtube videos show a black screen for me but the camera works fine(Except for video recording of course.)

I also now close down just about everything in "Running Programs" Leaving Android keyboard the only process that's still running.

I notice that doing this will allow my phone to sleep without having that "extra" light on the screen, thus saving a bunch of power.

Also, anyone notice Maps,Facebook, and Google+ always opening in the background? T_T They take up about 30mb in total and Force Closing them usually makes my phone A LOT faster.(Especially when playing Zenonia)

ps-I'm on the latest kernels and rootfs. FRx7.1

pps- After getting the latest kernels and rootfs, in the booting sequence I notice it would stay on "msm_htc_cable_notify=0" Or something like that for at least 3 minutes before continuing. Is this normal?
[Touch Pro, Fuze Android Development] arrrghhh:
Don't kill apps. They start back up on their own, as you noticed. Read my Speed Improvements thread - specifically the memory management topic. I set it very aggressive, option #11 - MegaRAM #1. It's very nice, and circumvents the need to go and kill apps yourself, just to have them start back up on their own.

YouTube works great for me. Perhaps there's some RAPH-specific issue...

I don't know what that msm_htc_cable_notify message is, sounds related to the extUSB plug - unless you're failing to boot, there's no problem with it. Is it causing an issue..? It's like the mdp 4 4 message I think. Ignore it, unless it's an issue.
[Touch Pro, Fuze Android Development] ZoneBlaze:
I know, I can't help but kill those apps(Facebook,G+,Maps). They only seem to start up again when I turn on wi-fi.

It really isn't a problem because it continues in a few minutes and boots fine. I just thought it was strange because it makes it longer to start :[

"htc_cable_notify_do_work: 0"

Also XDAndroid has been having trouble connecting to hidden networks(Having trouble as in not detecting/connecting at all).
[Touch Pro, Fuze Android Development] jeroen79:
Still audio problems somthimes

Does anybody has a solution for the problem that there sometimes is no audio in a call?, its very annoying and makes android practically unusable for me

Device: Diam100

Kernel: latest 20111017
[Touch Pro, Fuze Android Development] R^7Z:
I don't know if this trick will work for your device but there is mention of enabling then disabling the speakerphone solving some of these issues, depending on what your specific issue is...

Also, can you confirm you are running the the latest of everything to include the rootfs?
[Touch Pro, Fuze Android Development] drawgas:
Same problem for me.

It's possible that you should try older kernel, as I'm using same kernel.

Earlier I've had no such problem.

Also, is the no audio in call problem is occuring when the phone is in Vibrate mode?

After some testing - i've came to a conclusion that this is because of the Vibrate mode. I've left the 20111017 kernel, and stopped puting the phone into Vibrate. Now I have audio in-call every time
[Touch Pro, Fuze Android Development] arrrghhh:
Yea, known bug. If you put the phone in vibrate-only, it kinda gets a little crazy with what it mutes - everything :p.

New audio routing code resolves this problem. Currently it introduces others, but they are being ironed out...
[Touch Pro, Fuze Android Development] Rubik.Orange:
Device : DIAM100(P3700,GSM)

Kernel : htc-msm-linux @ 20111017_080427

i can't boot XDAndroid i just see these messages

DIAMOND detected

Checking for build type...

Unknown Android build. Assuming Ion variant

mount : mounting /lib/hw on /system/lib/hw failed: No suck file or directory

grep : /system/etc/default.prop : No such file or directory

/init : line 323 : can't create /system/etc/default.prop : nonexistent directory

tar : chdir(/lib/modules) : No such file or directory

ln : /lib/modules/2.6.27.46-01356-ge4c73bd : No such file or directory

grep : /system/etc/default.prop : No such file or directory

/init : line 323 : can't create /system/etc/default.prop : nonexistent directory

/init : line 323 : can't create /system/etc/default.prop : nonexistent directory

No user config files (ion.diamond) found on sdcard

and lots of error (cannot find directorys or others)

i think this build can't recognize diam's internel storage and can't mound system.ext2
[Touch Pro, Fuze Android Development] arrrghhh:
Other DIAM users don't have a problem.

Make sure you do a full format with the HP Tool. FAT32. Then start over, retrace your steps. Make sure you follow everything in the first post to the T.

Did you go from a N1 to a DIAM? I'm sorry.
[Touch Pro, Fuze Android Development] jeroen79:
Aha, this might solve my problems, i always keep my phone on vibrate.

Gonna test it without vibrate
[Touch Pro, Fuze Android Development] 7fernandes:
Latin characters

Hello

Can someone please help me? I need to use some latin characters in sms, like:

ç, á, à, é, í, ó, ú, ê, ã, õ and € symbol.

How can i enable this while composing a simple sms, or replying some email, chat etc...
[Touch Pro, Fuze Android Development] arrrghhh:
Soft keyboard?
[Touch Pro, Fuze Android Development] 7fernandes:
I'm using the slide keyboard from Touch Pro.

Can you recommend some soft keyboard capable for latin characters?

Thanks
[Touch Pro, Fuze Android Development] arrrghhh:
Well if the physical keyboard doesn't have the keys you need, you'd have to manually remap them.

I've never gone out of my way to look for a keyboard that uses Latin chars. The Market is a great place to start your search. MoreLocale2 is an app I've heard that helps with getting alternate languages into the OS, perhaps it will help with your kb issues as well.

I only use my physical keyboard, I have no use for a soft kb. Sorry.
[Touch Pro, Fuze Android Development] 7fernandes:
Thanks. This Froyo Bundle installation, has already Portuguese language, but i can 't see how can i write with those characters. But i will follow your tip and see the app you mentioned.
[Touch Pro, Fuze Android Development] SkinsFan:
Okay .. I admit that I haven't (yet) read through all 18 pages, but I have tried flashing the SD twice with this build. Both times, it broke my data and I could not make calls (unable to access the Sprint network -- the tower icon just continued "polling"). When I rebooted back to WinMo (I use Energy's ROM), data and voice were still broken. Both times, I then re-flashed to the Sprint stock ROM (for Raph 800). Data and voice were still broken. The first time, I had to call Sprint tech support and they had me eventually do a ##786# (hard reset) and then I got everything back. Then, I re-flashed to stock, then to Energy 6.5, and ... (twice). The second time, I went ahead and re- ##786# 'd myself.

The reason that I (still) wanted to try this build is that, even though I was happy with FRX06 (it worked and didn't break anything), I wanted to see if I could get bluetooth audio working. I only boot to Droid when I want to use a couple of apps that aren't available in WM 6.5, but I also have to be able to use bluetooth to make and receive calls while I'm in the car. Having the ability to use the bluetooth audio/call capability is a MUST. So .. my two questions are:

1) Am I the only one who has had this build break everything, even in WinMo? Is there a way to alleviate this from happening?

2) Does this problem exist (breaking data and audio) in the 7.01 build? Does bluetooth audio work in that build? If the answer to both is 'No' and then 'Yes,' then where can I download the 7.01 build?

I won't try to re-flash 7.01 until I am reasonably certain that it won't break WinMo because I lost a day and a half getting everything back to Energy 6.5 and XDAndroid FRX06 and getting everything back as before. But I would love to have Bluetooth audio working in Android because otherwise I am stuck to using WinMo (and not being able to use the Droid apps that I really could stand to use on a daily basis) 90% of the time.
[Touch Pro, Fuze Android Development] arrrghhh:
Data is broken for RAPH800/DIAM500's. See this thread about that issue.

BT isn't ready/stable yet. Some people use it, but it's not "done" if you will. There's still bugs with it.

It shouldn't break WinMo at all, but no guarantees. You're on your own with WinMo, this is the Android Development section... No WinMo here.
[Touch Pro, Fuze Android Development] SkinsFan:
Thanks for the response. I did get it to pair with the bluetooth in my car, and it dials out and all, but of course there is no audio in either direction. I guess I'll stay on the sidelines and watch for developments. I would love to eventually get BT working.

I wasn't asking for WinMo help. I just thought I'd mention that for the first time that I had flashed my SD card with an Android build and it messed up my WinMo build on main memory. I guess I always thought that the SD card Android builds were safe in that they wouldn't mess up my WinMo installation. Now I'm a little "gun" shy ... I mean, I keep backups and all (Sprite), so I don't lose anything, but it's still a pain.

---------- Post added at 11:17 PM ---------- Previous post was at 11:07 PM ----------

Are the fixes you posted in that thread built into the bundle now that you have in the first post in this thread (in other words, would they be built into this complete bundle that I downloaded a few days ago)?

I saw your other thread about the new audio routing ( http://xdaforums.com/showthread.php?t=1076884&page=26 ). Although doing the 775 chmod stuff and other "hacking" mentioned there is pretty much above my pay grade, I am curious if this would give me audio over bluetooth.
[Touch Pro, Fuze Android Development] arrrghhh:
The next build should have better audio routing. Not sure if the BT code will be "intrinsically" better tho. Just more sensible audio routing.

Dunno. I haven't used WinMo at all since I got this RHOD, which is ironic...

I guess I shouldn't say that. For the first 6 months or so, when Android was really unstable, I used WinMo a little bit more than Android. But since probably ~6-8 months ago I've been on Android 100%. But as with anything on this site, you are responsible for anything that happens to your phone/OS.

If you mean the fixes in that RAPH/DIAM CDMA thread, then yes those fixes are in 7.1 - if they weren't you would get service at all. No one went back and rewrote the RIL to work for data.... If you read thru that thread, hyc worked closely with me on my RAPH800 that I was borrowing - but it didn't have service, and no one else stepped up. So now it's up to someone with a RAPH800/DIAM500 to get the new RIL working with data. This is all in that thread.

The new acoustic stuff should fix all of the audio routing issues. Don't worry about it, there'll be a new build with it incorporated soon. It'll probably be GB, but it runs really well.
[Touch Pro, Fuze Android Development] achillf:
problem in call. When i call one number screen phone is black and i cant cancel the call .
[Touch Pro, Fuze Android Development] arrrghhh:
Hit power to wake the phone. The phone will sleep when in a long call.
[Touch Pro, Fuze Android Development] achillf:
nothing happens, all is locked, i cant close the call or light the screen .. nothing , must restart the phone to stop the call
[Touch Pro, Fuze Android Development] arrrghhh:
I bet it's just being slow. If the call is still going, the phone is still at least somewhat functional.. Patience is a virtue if you're going to run Android on a Windows Mobile phone my friend.
[Touch Pro, Fuze Android Development] catfishk:
RAPH800 users can reference this thread:

http://xdaforums.com/showthread.php?t=1203301&page=9

I was able to get a Sprint CDMA Touch Pro working using the froyo.user.conf and RIL provided by arrrghhh on the first page. I used this kernel package provided by the post by bluenote73 in that same thread.

Thanks everyone
[Touch Pro, Fuze Android Development] jb789:
I think that kernel package link is garbled, so here it is again for reference:

http://zimages.googlecode.com/files/htc-msm-linux-20110805_223228-package.tar.bz2
[Touch Pro, Fuze Android Development] arrrghhh:
I'm confused, does FRX07.1 not work out of the box for CDMA RAPH/DIAM's? It *should*, I'd like to know if it doesn't.

I assume it would work without data tho - as per that thread, hyc didn't patch the radio to work with data yet... no one else has taken a crack at his code either.
[Touch Pro, Fuze Android Development] drugusv:
when comes next release? :)
[Touch Pro, Fuze Android Development] arrrghhh:
There won't be another XDAndroid FroYo release. At least I seriously doubt there will be another XDAndroid FroYo release.

Also - just like CM and a lot of other open source projects, there's no timeline we have to stick to. We release when we feel it's ready, no sooner - so please, don't ask for ETA.
[Touch Pro, Fuze Android Development] MAJID_TAEBI:
hi,

tnx for your Bundle ....

i install GenY-DualBOOT-v1.0.6.0 ,but when i poweroff or restart my device,windows start and show erorr" android missing"!how can i fix it?!!i what enter to android not win!

help me.

oh...

sorry...i got it

i must install the Gen-Y in sd card,not internal storage...
[Touch Pro, Fuze Android Development] scopio:
do i need to charge my phone until full then only use android? my winmo is 6.1, can on android?
[Touch Pro, Fuze Android Development] R^7Z:
You don't necessarily have to but I guess it depends on the type of experience you are looking for. For me, if I want to make sure I can get to my home screen from a fresh boot into Android (no data.img file). Then generally, I'll try to make sure I have at least 40 - 50% left. Anything less than that, I usually put it on the charger. You should be able to run it while on the charger as well, again, if that is what you are looking to do...

:cool:
[Touch Pro, Fuze Android Development] scopio:
winmo 6.1 can run on this android right?? can use on my 8gb sdhc card??
[Touch Pro, Fuze Android Development] arrrghhh:
Any WM6.x can run Android. So long as HaRET can run, Android'll run. Should be fine. Why don't you (gasp) try it?
[Touch Pro, Fuze Android Development] scopio:
i dont understand this two part..

2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.

what is the so call root of sd card??

3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)

i already copy the whole folder FRX07.1 to my sd card, why i need to copy the STARTUPS folder again??

okay.. i admit i really a bit dumb on this things.. 1st time yo.. :(
[Touch Pro, Fuze Android Development] arrrghhh:
Uh, you should only grab the startup.txt for your device.

root of card = no folders.
[Touch Pro, Fuze Android Development] scopio:
thx.. i'm gonna try now.. :D
[Touch Pro, Fuze Android Development] scopio:
fail on calibration.. i didn't see anything about calibration appear.. so i just scroll on the screen.. :confused:
[Touch Pro, Fuze Android Development] arrrghhh:
You've taken all the steps for proper calibration? It's a pain, but you need an old kernel. Please follow the steps in the first post.
[Touch Pro, Fuze Android Development] scopio:
done already.. but the battery drain very fast.. for today i already charge it twice :confused:
[Touch Pro, Fuze Android Development] arrrghhh:
I don't see what touch screen calibration has to do with battery life.

If you don't like it, use WinMo. Android sucks power like crazy on native Android devices, and our port is far from perfect.

In other words, assuming the phone was a native device and all else equal... Android would still suck more powa than WinMo.
[Touch Pro, Fuze Android Development] jamesd256:
Another happy user here.

Just installed from the link in the first post on my RAPH100 using the supplied calibration...wow. This is amazing - the Raph is back to active service following a year or two off. I will be donating later - thanks very much to the XDAndroid team, amazing work

It is actually very usable, and already better than winmo 6.x, which couldn't even render the HTC Touch interface without stuttering.

Battery life is not that much different to my Galaxy S, and the relief at having a physical kb again for SSH'ing is huge.

Everything works except video playback. Cannot play back video recorded with the camera or from Youtube. Sorry if this is covered, but i'm not bothered about this anyway so won't look into it.

Once again, very grateful for all the huge effort of the contributors.
[Touch Pro, Fuze Android Development] doca68:
I've used the version FRX07.1_Full_Bundle_20110901 on a RAPH100 and is very useful, but I've seen some problems:

1) The Light of the camera don't work;

2) The camera videos are not visible and you can't see any kind of video. You listen the audio but don't view the images;

3) Sometimes the phone block itself and the screen become black and you can't do nothing. If you make a call to that number you listen that the line is on... but the phone don't ring. The only thing you can do is reset.

Thank You,

domenico
[Touch Pro, Fuze Android Development] arrrghhh:
Known issue. There's a patch to remedy it, but I don't think it's been implemented properly... haven't heard about it lately.

Do HQ YouTube videos work? Perhaps the changes I made to fix RHOD broke other devices...

Sounds like an SoD - or sleep of death. Make darn sure the phone is dead before rebooting! Try to plug into USB and pull logs if you can. Hit the power button a few times, waiting between each press. Swipe the screen where the lock "should" be. Etc...

Patience is a virtue, but in addition if you're in low service areas you might want to disable data - it has been known to cause SoD's.
[Touch Pro, Fuze Android Development] doca68:
Do you know where is the patch to let work the light camera?

I can't view no video, also in hd youtube.

When I receive or I do a call with the auricular if i replay i can't hear no sound.

If i activate the vivavoice and deactivate it, it will work!

Thank you for the previous answer

Do
[Touch Pro, Fuze Android Development] arrrghhh:
Patch didn't work.

HQ YouTube should work, I'll have to check on my RAPH800 tonight.

For audio issues in-call, flip the speakerphone on/off. This bug has been fixed in the GB testing build.
[Touch Pro, Fuze Android Development] doca68:
The video don't work!

But if HQ Youtube will work I can see the video on my phone or only the video in internet? And in which kind of format?

For the fix of the bug of the audio issues in-call, how can I apply in this rom?

For the freeze problem i've not seen it again but the battery in few hours go down...

There is a way to see the percentage of batteries in the tool bar on the top?

Thank you

Domenico
[Touch Pro, Fuze Android Development] arrrghhh:
Don't know what you mean for 1&2&3. For #4, probably. Sounds like a native Android thing, search for it.
[Touch Pro, Fuze Android Development] reiti.net:
I've installed FRX7.1 yesterday on my diamond (DIAM100) - has worked so far. I know this is not a Diamond Thread - but there is no on the proper forum.

Issues:

Screen Calibration - it works but the Boxes are not visible, when asked to touch them. (they are halfly visible AFTER you touched), so I guessed where they should be, maybe it will help, when you say where they should appear, the following worked for me:

lefttop, righttop, middle, leftbottom, rightbottom (correct?)

It runs stable but is always out of memory (ram) - so it is very slow and laggy - has anyone a solution for this? I've already tried most of the easier tasks to free up ram - sometimes it goes well, but as soon as something is starting, free mem is going to 0.
[Touch Pro, Fuze Android Development] R^7Z:
Read the FAQ HERE for screen calibration issues. As for the OOM issue, changing the max number of processes to a smaller number might help. Someone else made mention of this somewhere. I could've sworn there was a DIAM dedicated thread but for the life of me, I am not able to place my bookmark on it at the present time.

n-Joie!

:cool:
[Touch Pro, Fuze Android Development] arrrghhh:
Correct, there's no "Android" section for DIAM...

Did you bother reading the FIRST POST!?! It goes thru the options you have for calibration. I suggest you read and heed them.

DIAM is always out of RAM. See my Speed Improvements thread. Total it only has 192mb of RAM compared to 288 on most other devices in the XDAndroid family.
[Touch Pro, Fuze Android Development] drchocho:
Hi

i've installed FRX 7.1 on HTC Fuze (Raph 110)

- screen is smooth

- battery life from %100 to %5 : 2:30 hs (without activity, closing all programs with app killer and using only 2G )

- calls, sms and wifi works OK

- music player dont works very well

There is a patch that can extend the battery life?

thanks!

drchocho