yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] dvs6:
I'm glad it helped. I've had the wifi freeze on me once. So when I turned off the wifi the second time from setting, I made sure to either press the back button or power button or slide open to keep thephone from pausing and locking up. Not sure if it was just coincedence or what, but give it a try see if it helps.
[Touch Pro, Fuze Android Development] meukbox:
The only thing I see is:

# 22.01.10

# Proper Backlight control: dimming and controlling brightness. No need to change in WinMo anymore

# Updated RIL: force cdma option, for cdma topa/rhod since we have no way to detect that they are cdma

# Slow sim option to slow down SIM access, I think this might fix the problem of people having crashing android with bad sims

# Startup cmds:

* force_cdma=1

* slow_sim=<time in microsecond to wait between every SIM access)

# Updated apps

Where did you get that info you provided?

The problem is: the phone doesn't boot. The only way to get it to boot is to use an old rootfs.img.
[Touch Pro, Fuze Android Development] tyguy:
Review: XDANDROID.24.01.10.7z | zImage: modules-2.6.27-00791-gd52eb08.tar | system_core_readded.sqsh:

Deleted the whole SD card to start from scratch (no data.img either).

Placed all apk beside the games into the application dir.

First boot was rather quick (less than 5 min.).

Sound and mic OK.

Data worked (login to google, market etc.) without changing to Cingular410 in the setting.

Sluggish at the beginning.

Power down hang (didn't power down device).

Second boot ~ 2 min.

Disable WiFi --> freeze.

Enabled WiFi in WinMo and boot.

Disable WiFi OK (??).

Ran it today for daily use, battery life ~ 6 h.

Occasionally low battery warning on opening gmail or mail (but disappears soon). sms. application error.

Sometimes issues with screen calibration (with and without screen protector). Screen shifts left right but doesn't open the selected program, required a second or third "tap" from time to time.

Hardware keyboard decent fast. Software keyboard livable.

So far so good - Phone back on the charger.
[Touch Pro, Fuze Android Development] owziee:
I've got it sorted out now... Hopefully somebody else can get helped by this but I went into wifi settings and choosed forget wifi access point or what ever it says, then instead of immediately selecting wifi off I pressed powerbutton to return to homescreen and then back to wifi settings again and turned off wifi... I've tried it several times now, no freeze or resets :) :)

Battery life seems very good btw with wifi off, it's been running half this day now and I've done a few phone calls, I can't see much difference in battery drain compared to winmo on my Diamond. With wifi on it's a completely different story though :)

I can't understand why the led in the middle (the one the flashes like a circle) looks like my phone is charging while it's in standby??? Doesn't that eat some unnecesary battery juice flashing like that all the time???
[Touch Pro, Fuze Android Development] gmanfuzing:
correct !

im sorry friend , at the moment unicode doesn't support non-english

yuppp! and other devices will most likely follow.

the whole wifi on thing seems to be a MAJOR BATTERY DRAIN for me too. Its crazy how much battery goes into it.

i noticed the pulsating center led too and i was wondering myself why it was going!!! i bet its eating a lil battery too :[ with these two things we can have an EVEN better android :]
[Touch Pro, Fuze Android Development] 9600xt:
is there a way to disable wi-fi after i activated it???? any way....
[Touch Pro, Fuze Android Development] IceBone:
You can turn it off again. Put the power control widget on one of your home screens (4x1) and you'll have immediate control. Or you can go into the network settings and turn it off there.
[Touch Pro, Fuze Android Development] vuphuonganh:
I can't seem to turn Wifi on. I've got a Fuze.

Do I need to turn it on in Windows Mobile then boot Android?
[Touch Pro, Fuze Android Development] kirk509:
Black screen problem

After making a phone call, the screen went to black and can't awake.

Is there anybody can help me?

Device: Diam100 (Touch Diamond)

XDAndroid : 24.01.10

kernel : htc-msm-android@20100123_224401
[Touch Pro, Fuze Android Development] stinebd:
Well the RIL stuff and apps are in system.sqsh so clearly that's not the problem.

What I posted was a diff (*nix command line program which shows differences between two things) against the old 16 Jan rootfs.img and the newer 22 Jan rootfs.img. The two lines starting with + are what was added in the 22 Jan rootfs.img's init script (the only thing that changed in the new build).

If using the 16 Jan rootfs.img works with the 22 Jan build's other files, then it would seem like the backlight control is causing a problem (which happens in the kernel). I'd have to defer to phhusson on this one.

In any event, the people with this problem really need to provide specific information regarding the kernel version they used (ie. if they stuck with the 22 Jan bundled zImage and if newer images from glemsom autobuild do anything different) and specific phone models.
[Touch Pro, Fuze Android Development] owziee:
If pressing the power button a few times doesn't help it might have freezed and then you probably need to reboot/reset into wm again...
[Touch Pro, Fuze Android Development] andre.mud:
I'm using the exact build as from 24/01, replaced the system.sqhs file with the system_core_readded.sqhs file. Using the provided startup.txt from RAPH directorie.

Starting HARET.

Rootfs loaded

GSM phone found

Checking for partition

...creating a new Data store

Copying apps

Eclair build detected

pc_clk_disable: FIXME! disabling a clock that doens't have a ena bit: 22

...waiting......

info: task rpcrouter : 15 blocked for more thean 120 sec.

echo 0 > proc/sys/kernal/hung_task_timeout_secs disabled this message

some messages of workqueue, do_read_data, worker_thread

....waiting......

same messages

....waiting.....

etc

Are you sure that the only thing that is changed is the part for the hw_test / backlight? What does that part do. If it is not that important then i can continue to use the 16/1 rootfs.img file.

Andre
[Touch Pro, Fuze Android Development] moffe:
I wonder why people has so many different problems and some don't have them with the same HW? :confused: Is it because of winmo or radiofirmware?

I hope there will be a ROM soon for android. Maybe this will solve some problems :rolleyes:

Anyway, for me the new build with the new system file cause the phone to be really warm. Don't know why... Still I have these random crashes/restarts. :(
[Touch Pro, Fuze Android Development] babijoee:
Pretty much. As i dont remember changing anything else. It could be due to the backlight causing problems. It could even be the winmo rom you're using. not likely. In the end using the 16.01 rootfs is the same. :)
[Touch Pro, Fuze Android Development] babijoee:
Some people are changing their radio firmware which may also update their RIL. These things are taken also into consideration. Eventually when we are able to boot Android without needing winmo, it will be easier working out problem. Eventually we'll start recommending good radio's feedback and most likely have a poll for it. But until then we'll just have to live with it
[Touch Pro, Fuze Android Development] andre.mud:
Just to make sure. Can you upload a new rootfs.img (24/01) release with the part for the htc_hw/test commented out.

Is there another way i can activate this part?

Edit: When I use the 16/01 rootfs.img everything loads fine. with the pterminal program i can go to /sys/class/htc_hw/

When I try to vi test I get a permission denied.

Andre
[Touch Pro, Fuze Android Development] AkumaMax:
is there any chance of someone working on Bluetooth and GPS? Those are the 2 major things I use on my phone and it would be great to have. Wish I had the knowledge to do some stuff.
[Touch Pro, Fuze Android Development] rajackar:
Strange, you would think apn's would be reasonably similar to other providers. I'm still hoping this gets fixed but since there are only a few of us having this problem I guess it's not top priority ;)

I'll keep fiddling with hoping to find a fix.
[Touch Pro, Fuze Android Development] tyguy:
Radio feedback

I had so far only problems with the 25.05 Radio for the Raph/Fuze. The combo in my sig works nicely though in WinMo power consumption could be better. Since the .17 Radio seems to be independent from the rilphone.dll and seems to perform world wide in an average to good way (kind off at least as long as you use a newer rilphone) it could be worth a try to flash for Raph/Fuze users. If you switch over to the Radio thread, the .17. Radio was a general patch from HTC thus no ripped or associated rilphone.dll.
[Touch Pro, Fuze Android Development] babijoee:
Its the only difference Andre, just use the 16.01 rootfs.img

If you have working backlight functionality it should be all fine. I only done this by request of phh as the light winmo launcher does not give us access to backlight control.
[Touch Pro, Fuze Android Development] babijoee:
Thats all we are working on and camera too.

we are also working on flashing it too

Just be patient
[Touch Pro, Fuze Android Development] inf3rno1:
Great news! Im currently using the 1/24 build with the new 1/25 sqsh and everything thats supposed to work is working perfect besides wifi lockup freezes. After updating to the newest zimage and modules, the freezing happens less frequently.. Also, Any idea why android only gives us about 30-45mb of available memory, iirc on the fuze we have a 256mb ram or rom and the android package is only 50mb..

btw im on a Raph110 Fuze
[Touch Pro, Fuze Android Development] Mr_stickz:
Great work u guys but i was wondering a few things ;

Why did u removed the light sensor when it was there in a donut build it just worked fine for me (RAPH100),

And how do u think about getting GLES to work? i looked @ the coding from the hardware from the nexus one and mine and its alot different then i thougt it would be. When do u think it will be possible..

But im astonished with the progress! :O Really apprieciating all the hard work! :D
[Touch Pro, Fuze Android Development] andre.mud:
Ok, i will use the 16/1 release rootfs.img

However, I don't have proper backlight functionality I think. I cannot change the backlight intensity in android. When I put the backlight in Winmo at a low intensity then it stays that way in android. I have the 4 options not checked in winmo and auto backlight off.

Andre
[Touch Pro, Fuze Android Development] babijoee:
iirc you just need to turn off auto backlight in winmo and then Android can control backlight.
[Touch Pro, Fuze Android Development] andre.mud:
That's what i do, but i don't see any difference in android.

Do other persons with a RAPH300 have this working (considering the 'problem' with rootfs.img which also seems to be linked to backlight)

EDIT: trying to execute the command by hand in de pTerminal app. echo 3 > /sys/class/htc_hw/test - this doesn't work.

I'm i root user when using pTerminal?

Andre

RAPH300
[Touch Pro, Fuze Android Development] patzkata:
Rhodium report..

Hello to all

I'm a Rhodium (rhod100) user but i think that is not a problem to give my report how the last release work for me.

I'm using the 24/01 package Eclair 2.01 on Rhod400 device

also with the new system core from 25/01

and the latest up to yesterday zImage-modules-20100123_224401

My first impression is for the first boot which take me no longer that 2 min.

the new release of the Xandroid is works very fast and smooth which also impressed me.

WiFi still reboot the device, but the red screen after stand by is gone :)

Also 3G Apn settings configured automatically and after I logged with my gmail account, all my contacts, appointments and calendar synchronised with the phone.

The market working also without any problem, also google maps pretty good, but i don't know why my position is not correct on the map, but I think that is not a big problem for now.

also browser and other stuff like Live Wallpaper working very smooth without any "force close" messages.

Still no sound on my device (except in calling of course) even after using the "CharacterScanner" on my SD card

On my opinion this is the most stable pack up to now which Ive tested.

I have only one question.

I understand very well that we all have to wait until all phone hardware start to working, but is it possible someone of you developers to map the hardware buttons on Rhodium to work as well as on the other supported devices, because the red button and the power button still doesn't work correct.

Thank you for your amazing and hard work, and making this real.

With best regards,

patzkata
[Touch Pro, Fuze Android Development] babijoee:
I always thought you said you had a raph100 :confused:

hmmmm i think people should really check what devices they have.
[Touch Pro, Fuze Android Development] 9600xt:
i mean without make freeze the phone....
[Touch Pro, Fuze Android Development] andre.mud:
I thought also. I checked the back of the battery.. but i guess i should look better. :o
[Touch Pro, Fuze Android Development] dcbogdan:
With the 24th package my DIAM100 lasted about 13hours. No calls, but 3G was always on with tiwdroid refreshing every 15mins, GMail, Facebook and a weather widget.

Last night I have updated to the latest kernel from 25th. So far everything seems to be ok, we'll see how the battery holds up.
[Touch Pro, Fuze Android Development] babijoee:
-.-" i was wondering why you were having problems. :rolleyes:

i'll let phhusson know theres another new raph out there. :P and it has problems with backlight lines in new rootfs.
[Touch Pro, Fuze Android Development] cepalermo:
It not on the back of the battery. Its on the label under the battery.
[Touch Pro, Fuze Android Development] andre.mud:
I downloaded the tool 'Command Executer' with this tools i can execute commands as User and as SUPER USER. When i run the command /sys/class/htw_hw/test as User the command 'hangs'. When i run it as SUPER USER not.

Maybe this is usefull information...maybe in the startup the command is executed with not enough rights? I cannot however adjust backlight.

Andre
[Touch Pro, Fuze Android Development] meukbox:
I have a Raph 300 too. It is the Dutch t-mobile branded MDA Vario IV.

It is in my sig, has been there for some time...

As far as I know the only difference is that the home and call button, and the back and end-call button are switched.
[Touch Pro, Fuze Android Development] babijoee:
i think he meant that :)

andre, i'll let phh know and see if there is a fix or workaround :)

please try not too hard to fix this :p

you're giving me a headache :(
[Touch Pro, Fuze Android Development] babijoee:
woah thats no good. Has it always been like this?

If so in next package i'll release a fix for you guys.
[Touch Pro, Fuze Android Development] andre.mud:
Cool !! :D

Andre
[Touch Pro, Fuze Android Development] Dyllon:
any chance we could get an update for the device keyboards so that the use of the fn/space bar will bring up symbols?
[Touch Pro, Fuze Android Development] mac6408:
I fixed my Keyboard issue from the other day. Looked like my Startup.txt was wrong. I recopied it and it started to work.

Looks like a good build I have a couple of lock ups most are after I unplug in morning, and by the time I get to work it's locked up.

My big issue now is that my Back (<--) Button seems to get confussed with my End Call Button. It seems as though I have to let my phone cool down before it starts using the button better. I've tried pushing all parts of the button to try to make it work and nothing seems to work. Thanks guys this is a really good build.
[Touch Pro, Fuze Android Development] Scorchsta:
I have been having a problem with the hardware keyboard for a while now. Since I haven't seen anyone else post this problem, I'm afraid I might be the only one. After a random amount of time, my hardware keyboard just stops functioning. I'll slide out the keyboard and try and type and nothing happens. The lights behind the keys will time out as if I hadn't pressed a button at all. As far as I can tell, the only way for me to fix this is to restart.

So far it has only happened in sleep and never while I'm trying to use it. Sometimes it takes 10 minutes for it to happen and sometimes it will work for hours. This has been happening since well before the layout for the Fuze was made so I don't believe it has anything to do with that. I've deleted my data.img several times with no luck.

Right now I'm using the build from the 22nd and the rom from the front page. Any help would be appreciated. Thanks for the hard work and keep it up!
[Touch Pro, Fuze Android Development] Nakebod:
Man, the battery usage is quite cool already, a lot better then the previous build :) My previous "record" was near 12 hours, but that is nothing compared to my current time on batteries :D

Currently running 16h45m, and although Android sometimes reports that it has less then 5% left, hopefully it will continue for a while. Android System Info reports 20% left.

But I'm getting close to "my" 18 hours reboot/crash bug, so I will probably not see the full battery usage :(
[Touch Pro, Fuze Android Development] glenn1982:
With the last build and the latest zImage, the system freezes after deep sleep. It has done that with zImage from 17.jan to now.

-----------------------

Blackstone
[Touch Pro, Fuze Android Development] babijoee:
Its a known problem. Eventually the sd-card isnt being read and that leads to your lockup. Some people experience it after 18 hours and some after 1 hour. Its very random but should be remedied when Android is flashed.

Also the SD card you have may also be a factor but i'm not sure
[Touch Pro, Fuze Android Development] rs19078:
My hardware keyboard (Fuze) has also just stopped working before. Also, plenty of trouble waking the phone after calls.
[Touch Pro, Fuze Android Development] meukbox:
All the previous builds worked just fine.

The jan 16 build was the last to work. It's just the last 2 that don't work.

A fix would be great :)

No idea what causes it though. AFAIK the only difference is that it says MDA on the cover, under the battery it says RAPH300 and the buttons are inverted.

[edit: specs here: http://www.gsmhelpdesk.nl/en/specs.php?id=2522
[Touch Pro, Fuze Android Development] thisperishedmin:
I did not realize thats why the lockup after long sleep (ie overnight) occurred. This is exciting news for me as it basically means...Android will be a 100% daily usable reality for me, if it can be flashed! continually improving battery life and slow charging would really be the icing on the cake haha...(I dont use the camera or GPS, so its not a personal requirement to use it 100% full time flashed - but I'm rooting for everyone involved regardless!)

Keep up the fantastic work, I'm amazed by this...I really NEVER thought Android would even get as far as it did for the Raph.

barring any massive uni homework, I'll be testing the newest build on a fuze (raph110) tonight (and reporting back of course).

Thanks again to all involved.
[Touch Pro, Fuze Android Development] owziee:
I don't know if I've asked this before and if I have I'm really sorry and this will be the last time I'm asking this question...

Is there any benefit of deleting the data.img when updating the zImage/Modules...?
[Touch Pro, Fuze Android Development] Nakebod:
I don't hope it's the SD card ;-) Diam100, internal memory :P

Okay, didn't know that this was a know problem, neither that is was random since it doesn't seem to be random here, it is always at 17 hours and 5x minutes.

Highest was 17h 58m, lowest 17h 54m.

Currently running 17h50m, on batteries! Probably quite near the end now, the % is quite stable reporting 5% left now, without going up and down :)

So it will be either a reboot within 10 minutes, or a complete empty battery :D
[Touch Pro, Fuze Android Development] AkumaMax:
Oh I am just wasn't sure if you guys were working on it that's all.
[Touch Pro, Fuze Android Development] babijoee:
not really but if you encounter problems sometimes it may be due to data.img

Rarely though. Data.img stores user cache which is basically settings, information and Apps. zImage is the kernel for Android and modules contains the wifi, ramzswap and other modules required for some hardware.
[Touch Pro, Fuze Android Development] MiTMaNeK:
RAPH100 + 24.01 build + 25.01 system.sqsh

Sometimes wifi freeze phone when turning off.

Sometimes phone freeze in deep sleep.

All other seems to work fine.

Good work ! Thanks for it :o)
[Touch Pro, Fuze Android Development] warri:
I am using the 25 system.sqsh , with the latest zImage and Kernal Modules from the autobuild.

RAPH110@eclair: Wifi seems to work when charging or powered through usb. Otherwise snappy, and responsive. Boot Time was a bit long
[Touch Pro, Fuze Android Development] Nakebod:
Woow, I've beaten "my" 18 hour uptime bug ;))

Got 18h02m before it rebooted (With only 2% left when WM was started :D)
[Touch Pro, Fuze Android Development] owziee:
Is there no way to make the display more responsive when in Android? I notice that I have to press harder to make it register touches when in Android compared to when in wm ui, maybe it's a bit to early to ask about minor important stuff like this but I thougt maybe there's an easy tweak I've missed somewhere?
[Touch Pro, Fuze Android Development] mchuntley:
ATT Fuze + 24.01 build + 25.01 system.sqsh.

My Calendar is back, the phone is running smoothly, nothing is breaking.

It looks pretty good, but I have 1 problem. All of the ringtones are gone, and the only ones I have are from a 'Star Trek' ringtone app. I copied the media folder over from the build, and all the files are there. I can't seem to find the 3 ringtones I have from the app on the sd card. I wil find another couple of ringtones to bring over, and play with. Has anyone else seen this problem.

Otherwise, I am really happy with these builds.

I am about to pull the usb and see how long she lasts!

Thanks!!!
[Touch Pro, Fuze Android Development] NuttySquirrel:
Using the 1.24 update, my google apps keep crashing. Every 30 seconds the phone is active, the crash report for google.process.gapps comes up. Any ideas?
[Touch Pro, Fuze Android Development] mchuntley:
Try loading the new 25.01.10 system.sqsh, it helped me out greatly
[Touch Pro, Fuze Android Development] tosnillo:
i disagree with your words rajackar. Do you really think so?

First: This a community; the target is porting android to Raphael and Diamond. We work together: programmers, testers...

Second: As tester, I hope porting to Android becomes true and believe it. I work too and i deserve the same as other members. Don't you?

Third: If there is a problem with any device / model, do you believe this problem won't replicate to other devices?

Fourth: I think GPRS, 3G, data connection is more important than market, apps, GPS, Camera,... as it's part of the main core of phone.

Fifth:I'm sure not all spanish people have tested Android even Know this forum. Spain, Netherland, Poland report this issue...'a few' sounds bad.

Hope that your words have not more people upset :(
[Touch Pro, Fuze Android Development] danbutter:
I was thinking this is controlled in the startup.txt, but now that I go back to reference it I am not so sure.

I got the following from the wiki:

http://wiki.xda-developers.com/index.php?pagename=RaphaelEclair

Startup.txt and Default.txt cmdline settings, values, and what they do:

Screen Settings:

* lcd.density=210

* mddi.width=320

* mddi.height=480

Touchscreen Calibration:

* msmts_calib=0x7a.0x5e.0x35a.0x37f

Not sure if density is it or not.

Maybe someone more knowledgeable can fill us in.

It should be 480 x 640 too so I am not sure what that is about.

At any rate I would be interested in the answer since I share your sentiment on how it is harder to "touch" in android than in WM.