yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] bigstoo:
On a (slightly) related note, I think I have found why my RAPH120 keeps locking up in Android.

I, too, am on the provider "3 UK". I live in an area that is poorly covered by their 3G network, so it usually roams on to some one else's 2G network (Orange, in my case).

It seems that whenever it drops off the 3 UK network and starts roaming, the phone locks up.
[Touch Pro, Fuze Android Development] pilgrim011:
Thanks, great news. :)
[Touch Pro, Fuze Android Development] pda_pbpbpb:
I am using T-mobile touch pro(diam 300), do you know which startup.txt i can use for this raphael? many thanks in advanced.
[Touch Pro, Fuze Android Development] moffe:
I have too problems with getting any data connection... Wlan works but no 3G or gprs. I have never seen any icons of 3g or other on the "statusbar".

I have tried with 2 different sims and ofcourse changed the apn in the startup file. For the one sim/operator the apn is "internet" and for the other it's "online.telia.se" and no username or password.

Then I noticed one other thing, that SU doesn't work. It starts but I can't write anything there, its only a black screen.

Anyway my UE is an DIAM100.
[Touch Pro, Fuze Android Development] mac6408:
Just found this issue yesterday. Twice I was in marketplace when I recieved a call. Both times my Fuze locked up after I hung up the calls. Is anyone else experiancing this issue? You guys rock with getting android on my Fuze. I was honestly thinking of getting rid of it to get a droid but this makes me content till my contract runs out :) Thanks guys
[Touch Pro, Fuze Android Development] TheDeadCPU:
Good News!

But one question, how hard is it to code the HW keyboard? Hence i got a Norwegian Raphael with different keymapping :P

Where there is a 'Æ' on K an 'Ø' on L and a 'Å' on P, when FN is pressed first :P

Like this
[Touch Pro, Fuze Android Development] babijoee:
Android doesnt support non ascii characters. Thats why when you have music with non ascii chars the media.scanner dies thus why you have no ringtones/notification tones. So its no for now.
[Touch Pro, Fuze Android Development] |Jason8|:
Awesome! I'm assuming the Fn key will become the Alt key? A few things to consider, though. Keep the OK button on the bottom left as Ctrl and keep the Caps key as Tab? It makes the Fuze keyboard much much much much more linux friendly and user friendly. Lol.

3D acceleration... I miss it, too. :(

Since this is a volunteer project, the features appear as they appear. No one knows when the features will be completed, but they'll get done when they get done. I hear that donations bring motivation, though. ;) So shoot babijoee a few bucks and it might make him work a little harder on the issue you're having. :) But just keep checking. Enjoy the addiction. It's fun!
[Touch Pro, Fuze Android Development] madnish30:
how long does it take to boot andoid on first boot

its on the line which says "4833.7973631 r5:0000000000 r4:00000000000

its not stuck the lines keep moving.

I'm skeptical as in the past i have not been able to successfully boot andoroid.

this time i formatted my SD and tried so its moving

But at places i also reead rpccounter IS blocked for more than 120 secs or something like that ..

but it still keeps moving will i be successful this time.

Sorry OP if i will irritate you again.

Please help

Thanks
[Touch Pro, Fuze Android Development] |Jason8|:
Which phone do you have? It should be booted after a few minutes, and it shouldn't be scrolling those numbers. Post your startup.txt and your phone's model number (RAPH100 or so) and we'll try to help you out.
[Touch Pro, Fuze Android Development] madnish30:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 1910
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=210 msmts_calib=0x7a.0x5e.0x35a.0x37f clock-7x00.a11=500 msmvkeyb_toggle=off pmem.extra=1 gsensor_axis=-1,-2,3"
boot

thats startup..

I'm on Raph 410 ( normal gsm tp )

with 4 gig SD Kingston formatted and put the latest build with updated .SQSH, modules, Zimage ( i did delete the data.img which was created whn i tried last )

please help man i really have been wanting this for long..

thanks mate

EDIT i'm so sorry guys I 'm on Raph 410 just checked could someone please guide me to a startup.txt for that a total noob at writing startup texts..

By mistake i thought i have raph 100 as i read it on wiki..

Please help guys

sorry Joee for irritaing you and polluting your thread.

please excuse.
[Touch Pro, Fuze Android Development] |Jason8|:
I would back up your SD card and do a quick format on it. Then put Android back on it and try booting again. Or try a different SD card if you have one, maybe? Your startup.txt looks fine, and if you've followed all the instructions in the first post, it should be booting.

EDIT: Never heard of a RAPH410................. What's the branding on it? Maybe we can find something similar.

EDIT2: Questions like these are perfectly fine, bro. The questions that have been answered twice on every page in the thread (like the PIN error and if it has SenseUI) are the ones that are irritating. So don't worry about it. :)
[Touch Pro, Fuze Android Development] madnish30:
thanks for the word man..

:)

umm raph410 even me not aware of it.

its the Indian touch pro that is without 3g and no front camera its similar to fuze but it has 7206 processor instead of 7201 thats the main difference..
[Touch Pro, Fuze Android Development] babijoee:
This is probally why you cannot boot =/
[Touch Pro, Fuze Android Development] madnish30:
Anyway i can get my startup configured for a succesful boot ??
[Touch Pro, Fuze Android Development] lugiber:
I'm not sure if this might help you:

xdaforums.com/showthread.php?t=458473

(Sorry, apparently i'm not allowed to post the full working link.)

I'm not a programmer my self and know nothing about androids source files, but perhaps it might point you in the right direction. :)
[Touch Pro, Fuze Android Development] meukbox:
I am not an expert, but I don't think you can boot an operating system on a processor for which it wasn't compiled.
[Touch Pro, Fuze Android Development] babijoee:
Quite right i'm afraid. I'm not sure about any magic numbers but really just wait until your device CPU is supported.
[Touch Pro, Fuze Android Development] madnish30:
is the problem to do with Raph version or processor ( or its one in the same ? )

if i try startups combinations and permutations my self from the wiki is there a chance ?

could phusson help in this ??

thanks guys..
[Touch Pro, Fuze Android Development] |Jason8|:
It has a different processor than anything that's been coded for in the kernel. So chances are, it won't ever boot until those modules get added for your phone. Sorry.
[Touch Pro, Fuze Android Development] babijoee:
pm phhusson. I dont think anyone here is able to help you. so yeah just pm and see what he says. I dont need the thread being filled with questions in relation to this
[Touch Pro, Fuze Android Development] babijoee:
uploading new package now guys :D
[Touch Pro, Fuze Android Development] |Jason8|:
Hitting refresh over and over, waiting for the good news! :D
[Touch Pro, Fuze Android Development] kenmaples:
Man am I glad I am not the only one!!!
[Touch Pro, Fuze Android Development] babijoee:
Give it 15 minutes. the ftp i'm using is slow so i changed it to 4shared

Hopefully someone can mirror it when its done. :)
[Touch Pro, Fuze Android Development] powergate:
Downloading..... when i downloaded it i will create an mirror.

Do you want an ftp account for future mirroring babijoee?
[Touch Pro, Fuze Android Development] herpez:
Hi! does it have any "news" or is just a compilation of the last kernel with the last build?

Thanks for the work!
[Touch Pro, Fuze Android Development] skulltor:
As babijoee allready posted:

# updated apns.xml ( hopefully this should fix some 3g/GPRS issues people are having )

# Fuze keyboard layout: Battousai

# Updated generic Raphael layout with better keymapping
[Touch Pro, Fuze Android Development] powergate:
Mirror ready! Enjoy!

http://www.powergate.nl/xandroid/XDANDROID14JAN.7z
[Touch Pro, Fuze Android Development] drazah101:
Just a note, for the apn settings it decided to pickup the Vodafone UK wap settings which, if your on contract internet, isn't a good choice :)

Overall though, its very nice to use - can't wait for newer kernels with more stable modules and possibly some graphics drivers ! would run beautifully
[Touch Pro, Fuze Android Development] allthatinny:
do need to delete my data.img to get the fuze keyboard to work? cause i updated the files and didnt delete the data.img reboot but still the keyboard layout is set for a touch pro instead of the fuze
[Touch Pro, Fuze Android Development] TheDeadCPU:
From Readme .txt in FUZE stratups folder.

Files needed:

In startup.txt, for fuze keyboards, add physkeyboard=fuze to the cmdline.

Its been already added but if you have a custom startup.txt then you can add it.

For standard raph, no change is needed.

TODO: I'm welcome to suggestions as to where I could put useful alt keys, perhaps

for console use (like the pipe |, or > for output redirection).

The fuze also has a push-to-talk button which does not generate any input events

from what I saw. This might need a modification to gpio_keys in the kernel. phh

would know.

I'm sure there will be some bugs, but at least they'll be easy to fix now :D
[Touch Pro, Fuze Android Development] Nakebod:
Nice babijoee, downloading the latest build right now :)

Is there any easy way to export and import all my mail accounts? (Got 5 accounts atm :P)

Anyone got an answer on this:

Got the same problem today, booted my phone last night before I went to bed, and again near/over 18 hours it stopped working.
[Touch Pro, Fuze Android Development] allthatinny:
oh yuh i forgot to add that i did add the cmd line to the startup.txt and IT DONT WORK so i will forgive u for trying to bash me
[Touch Pro, Fuze Android Development] Soikiro:
when i imput the pin, my correct sim pin, the android says "wrong pin"

is a bug or what?

thx
[Touch Pro, Fuze Android Development] babijoee:
In boot. Just before A N D R O I D did it say which keyboard its using. If it says default then somethings wrong. If it says fuze then it worked. Hopefully

I havent really tested it so let me know.
[Touch Pro, Fuze Android Development] TheDeadCPU:
Sorry :P

Just EXTREMLY many people (noobs) that want everything to work "out of the box" :P
[Touch Pro, Fuze Android Development] allthatinny:
u will get flame, i suggest u read the first page before u do, lol
[Touch Pro, Fuze Android Development] allthatinny:
let me try, gimme one min Babijoee
[Touch Pro, Fuze Android Development] allthatinny:
not 100% sure cause the boot txt does move fast but i think its using default
[Touch Pro, Fuze Android Development] skulltor:
No Bug, just unset pin request in window mobile first. So windows and android won't ask you again!
[Touch Pro, Fuze Android Development] Soikiro:
ok thx for the info, and isn't a post for flame in the topic... good job!
[Touch Pro, Fuze Android Development] vicfuze:
FUZE keyboard mapping works great! Thanks!

One issue with the update is the top power button does not wake up the device anymore or return it to the home screen. Not sure if there is a command line option to restore this very convienent button map.

Great update by the way. Runs cooler from what I can tell so far.

:cool:
[Touch Pro, Fuze Android Development] babijoee:
yeah that happened to me too. Just reboot the phone and start android again. It should work after that :p

Can people post their feedback with keyboards :)
[Touch Pro, Fuze Android Development] flitzjoy:
I simple can believe how this is working good!

Congrats babijoee!

once we get opengl/gps/camera I can complete retire WinMo 6.x.

Again, what impressive work!!!! :)

I will try to configure my data connection now. ;-)
[Touch Pro, Fuze Android Development] TheDeadCPU:
Crash

Huh, after about 30 minutes use, it crashed and showed "Full update ongoing" then winmo appeared o_O
[Touch Pro, Fuze Android Development] zajiczech:
Keyboard

For me, RAPH100, keyboard is working, but when using gmail app (dunno if in other apps too) the arrows are switched, up instead of left, dn instead of right and vice versa. But good job anyway, everything i've tested works (wifi, calls,market, sleep,...).
[Touch Pro, Fuze Android Development] vicfuze:
Yep. Confirmed, reboot fixed the mapping! Thx!!!
[Touch Pro, Fuze Android Development] gigaguy:
I have the same issue with the arrow keys on the keyboard.
[Touch Pro, Fuze Android Development] chasx003:
okay, i've searched, but I can't find an exact answer, and I don't have time to read all 170 pages of this thread, but on my Fuze (ralph110), I cannot get wifi to work. I'm using the startup from the ralph folder. I've tried enabling wifi from withink winmo, and then starting up android, but it still doesn't work. I'm using the jan 14th release right now, when android loads, wifi is not enabled, and when i click to turn it on, it tries, and then says wifi unable to start. Anyone know where I'm going wrong?
[Touch Pro, Fuze Android Development] jooprzol:
Keyboard!

Thanks all who worked on the device specific keyboard settings! It's working great! Unfortunately, it appears that the device specific settings for the Fuze have caused the numbers on the on screen keyboard to go wonky. (I haven't added it to my sig, but I do indeed have a RAPH110)

Here's how I tested and verified this:

1. added the physkeyboard=fuze option to the startup.txt file.

2. deleted data.img, system.sqsh, initrd.gz, rootfs.img.

3. copied in new system.sqsh, initrd.gz and rootfs.img.

4. started up android and allowed it to create a new data.img. booted up just fine.

5. went to add my gmail address to sync, it asked for the password, so I attempted to type it in using the android onscreen keyboard (not the HTC keyboard). Letters typed out fine, numbers go through the action looking as if they'll type out (the button popup appears when you press the selected number button), but they never do. Opened up the physical keyboard, typed it again, and numbers work (with the Fuze layout, of course).

6. Rebooted phone and started up android again to apply multiple boots testing principle, no change.

7. Rebooted phone, removed physkeyboard=fuze option and then booted back into android. Tested on screen keyboard. Numbers work as expected. However, the previous available options that were available when pressing shift and then another button (for example, shift & . would type out a ":", and shift & , a ";") no longer work.

8. Rebooted phone, added physkeyboard=fuze option again, and then booted back into android. Tested on screen keyboard. Numbers work! That is, until I start using the physical keyboard. As soon as I type out a number, the onscreen keyboard messes up. Another oddity, the first time I press the fn key to type out a number, the fn light comes on, but stays on after the number choice is pressed. The next time I press fn to choose another number, the fn light shuts off, but I still get a number on screen. So the light alternates between an off and on position when typing out numbers using the physical keyboard.

9. As a last step, I tried the zimage and modules*.gz that came with the pack to see if I got any results, although, from the timestamp they appear to be just the regular latest glemsom autobuild. No change.

Anyways, just wanted to report what I'm seeing. Hope this helps.

Thanks everyone for all your hard work! I know I'm not the only one here that really appreciates it!
[Touch Pro, Fuze Android Development] ericxw:
First of all, great job! I haven't checked the android scene for a long time now and I have to say I'm impressed!

I have a RAPH800 so I'm running the matching kernel. Problems I'm having:

- Microphone does not work (can play sound no problem)

- Keyboard problems (missing letter "u", arrow keys mismatch, no Fn key)

- Widgets on home screen disappears after sliding out keyboard (new since today's update)

I've heard of the missing Fn key but the "u" key missing is a little annoying...lol. The widgets missing is a little annoying too.

Anyone else having similar issues?
[Touch Pro, Fuze Android Development] vicfuze:
The FUZE arrow keys also seem reversed. UP/DOWN behave like LEFT/RIGHT and RIGHT/LEFT work as UP/DOWN.

The SHIFT/FN and all other keys work great. The LEDs for the SHIFT and FN don't seem to light up as expected sometimes the LEDs are on but the SHIFT or FN is off or not locked. Not a big deal to me!

Last item on my list is Bluetooth headsets... Then I don't have to boot WiMo in the car during my commute!

:o
[Touch Pro, Fuze Android Development] binky11:
HI,

Still having no connection to Vodafone Live NL :(

It looks like it's connected, but have nothing :(
[Touch Pro, Fuze Android Development] gigaguy:
I am also getting alot of "force close" errors on this newest build. Usually on "android.process.media". I get that error when trying to open facebook or astro. I've tried rebooting a few times and that helps for some errors, but the media one keeps popping up. I am not doing anything except trying to set everything backup like sync and google voice.

One other thing I noticed, after the first bootup I was able to expand the notification menu at the top with just my finger. After subsequent reboots, I am no longer able to do that.
[Touch Pro, Fuze Android Development] kenmaples:
I can no longer use the touch screen to dial with the new FUZE layout. Anyone else seeing this?
[Touch Pro, Fuze Android Development] vicfuze:
I have the same issue.

Dialing,

1 returns !

2 returns =

3 returns :

4 returns ?

5,6,7,8,9,*,# return <null>

0 returns _
[Touch Pro, Fuze Android Development] herpez:
Hi. Just to report that this build is working 100% on the things its supposed to work.

Wonderful job guys!

And, thanks for this being possible!
[Touch Pro, Fuze Android Development] Fredouye:
Hi

on a DIAM100, I can't use any hardware button...

(deleted everything before unzipping the package)

Edit : nevermind, hardware buttons went back without doing anything special :)
[Touch Pro, Fuze Android Development] TheMuffinMan616:
I can't seem to type a semicolon with the new Fuze Keyboard layout changes. Just wondering if anyone else has this problem.
[Touch Pro, Fuze Android Development] IceBone:
Yeah, the hardware buttons are a bit buggy. I found you have to drag your finger around a bit. If the led under the button doesn't light up, it won't work.

Also, a trick to unlock the phone when the top button doesn't unlock the screen anymore, is to exploit the Eclair bug of pressing the home button right after the backlight turns on and you'll go straight to the home screen. So... let's not upgrade to 2.1 before this is fixed. :D
[Touch Pro, Fuze Android Development] pilgrim011:
Same thing on mt:s network (Serbia).:(
[Touch Pro, Fuze Android Development] Jack Jumpin:
Any Chance this could work on a Toshiba TG01 ?? Or could be made to work with a bit of work ?

Thanks

JJ
[Touch Pro, Fuze Android Development] stinebd:
This is known, and I'm not yet sure what we can do about it. The arrow keys on the keyboard and the directional buttons on the capacitive keypad both use the same scan code (which is what Android looks for to report key presses), so we need to find some way to rotate all those keys when the keyboard is open.

Thanks for the report. This is entirely a trial-and-error process because we don't have the source file for the original keypad character maps used in this Android distribution. There will be various bugs, but the fixes for things like the number buttons on the phone app and OSK should be simple.

As far as the fn light on the keyboard, I have to do research into how that can be handled. I don't even know if it's something the userspace (Android) can do or if it's in kernel space.
[Touch Pro, Fuze Android Development] ericxw:
In my previous post, I did not delete the data.img file. So I gave that a try and here are the results...

- Fixed the widgets disappearing issue

- Data access is gone on CDMA but has phone function

- Keyboard does not work at all

- Seems a little snappier

- Mic still not working

- Think it's charging all the time like before (I forgot to mention in the last post)
[Touch Pro, Fuze Android Development] euromusic:
Good job, but I have several keys that don't work on my RAPH100 QWERTY layout

If I press Fn+K (which normally does ';') I get '

If I press Fn+L (which normally does ':') I get "

If I press Fn+, (which normally does ' ) I get ';'

If I press Fn+. (which normally does " ) I get ':'

So they are obviously switched which is kinda annoying if you don't think about it. :)

P.S.: If you press Fn+"Left arrow" (Comm Manager in windows) Android kind of crashes to the terminal. xD
[Touch Pro, Fuze Android Development] IceBone:
I just put a shortcut to haret into the winmo startup folder. How would I go about removing it if it somehow suddenly all goes wrong or there's a new pack?
[Touch Pro, Fuze Android Development] jamen:
CDMA data not working

Yeah I'm not sure what changed in the last 4 days to kill CDMA data. I saw that you're having a problem with the MIC, I'm guessing that you've already read that it is required to be on a call (actively) while booting into haret for the microphone to function.

if you find this difficult i made a mortscript to call your voicemail and launch haret.

http://files.vcn.com/PPC/call&roidv2.cab

any feedback is great.
[Touch Pro, Fuze Android Development] meukbox:
Installed it and looks OK.

WiFi, phone and 3G working. No problems with wrong keys on my keyboard, it's even better. Keys like : and ; were not on the right position, now they are :)

Still no lit keys when I slide out the keyboard though.

Voice search works now too! Yay! :)

Shazam still doesn't hear anything I think, ill try that again later.

The only thing that confused me a bit is the "\XDANDROID14JAN\STARTUP CONFIG IN HERE". I thought Haret was going to look in there. So I booted with my old default.txt.

I'll look at the new options later.

So 2 improvements for me.

(but damn, I forgot the name of my alarm application. It was free, had multiple alarms and snooze. PM me if you know what it was called or a good replacement :rolleyes:)

[Edit: don't PM me! it's the default alarm ....)
[Touch Pro, Fuze Android Development] jamen:
can you change your startup folder to point to a folder on the SD card? just a thought... that would give you a chance to eject the card to boot into WinMo or just remove the file if needed.

scratch that, haret is on the SD card, if there's a problem you can just eject the SD card and WinMo will look for haret, see it's not there and continue =)
[Touch Pro, Fuze Android Development] IceBone:
Diamond, integrated storage.
[Touch Pro, Fuze Android Development] euromusic:
I propably need to delete my data.img :/
[Touch Pro, Fuze Android Development] vicfuze:
Semicolon and all hard keys (including w/ Shift/FN) work for me but the arrow keys are switched around. The windows logo button now brings up the g-menu screen which is nice...

By the way, once we move off running from SD media, we will probably double our battery performance. Running a system off SD access is a big drain on power for sure.
[Touch Pro, Fuze Android Development] Zeraven:
Working awesome now, love how the keyboard works now :)

Question, i am still having problems coming back from sleep after a phone call, tried pressing the buttons as instructed before and all. Other than that, The capacitive wheel goes nuts sometimes, i know i never use it, is there a way to shut it off?

Thanks for any replies, great job on this update! :)
[Touch Pro, Fuze Android Development] ericxw:
Hmm...didn't work. And I tried to make the call while booting into android but it just dies and resets...lol