yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] bryceowen:
Hey everyone. I have a couple questions and I'm not entirely sure my problem doesn't stem from the WinMo ROM I'm using... (Also, I'm using a Raph110 Fuze, if that has any bearing on my problems.)

First, when the touch screen calibration step comes up, I get no indication of it other than the booting appears to stall. When I touch where I think I should (somewhere near the upper left), I'll see the upper right box appear, then part of the center, then part of the lower left then the lower right. The calibration takes, but I don't know how off it is because of the first tap location...

Second, I can't for the life of me get wifi working. I tap to activate it, it shows that it's starting for a few seconds, then it just says 'error' under the wifi checkbox.

I was hoping that I could, at the very least, get wifi working so I could use Skype or Palringo or something since I don't have AT&T any more...
[Touch Pro, Fuze Android Development] arrrghhh:
Did you follow the calibration steps in the FRX thread? It's quite complex to manually calibrate.

As for wifi, what kernel? .27? Do you have logs? Did you read the FAQ & try the wifi-nvram trick?

As for Skype or Palringo, don't hold your breath. Most older native Android devices struggle to do tasks like this, so don't be surprised if you don't have the horsepower to run a quality call over wifi...
[Touch Pro, Fuze Android Development] bryceowen:
No. I tried searching for touch screen calibration problems, but nobody described the problem I'm having. (In fact, when I search the forum for "manual touch screen calibration" now, the post you made just a moment ago is the ONLY result.)

It's the ROM on page 1 I just downloaded today. The software itself says kernel version 2.6.27.46. I may have logs, but I'll have to look up how to extract them. I read the FAQs for the various "Android on Fuze" sites and the only thing regarding wifi is "It works." Nothing about a 'wifi-nvram' trick... (Again, searching for that phrase returns your above post...)

As for horsepower, I know this device isn't exactly the "powerhouse" it once was, but if I can use it for instant messaging or what have you, I'll be happy.
[Touch Pro, Fuze Android Development] arrrghhh:
http://xdaforums.com/showthread.php?t=1171070

Read the first post thoroughly. This build/ROM/whatever this is assumes you already know how FRX works and how it's setup.

That's .27.

Please read the FAQ - http://xdandroid.com/wiki/FAQ

Should work fine for messaging. Wifi calling - doubtful.
[Touch Pro, Fuze Android Development] bortak:
RAPH100

Don't know if anyones noticed, but when the phone charges it never goes to "sleep". The backlight remains on.
[Touch Pro, Fuze Android Development] arrrghhh:
It's not possible for the phone to sleep when plugged in. However, the backlight probably should be turned off...

I don't think there's a single kernel dev working on RAPH patches, so the likelihood of it getting fixed is slim-to-none. Sorry.
[Touch Pro, Fuze Android Development] bortak:
It's alright, thanks for all the hard work anyway... this is what.. years of work isn't it? And I'm only really using this phone atm cos I smashed my Desire :P

Upgrade in a week, soooo SGS III here I come :D
[Touch Pro, Fuze Android Development] jeroen79:
Has anybody got it to run descent on Diam100?, it is way to slow on mine to be used daily.
[Touch Pro, Fuze Android Development] arrrghhh:
This is the RAPH section, not DIAM. DIAM has a lot (like 100mb) less RAM. Not sure Android will ever run "well" on a device with so little RAM...
[Touch Pro, Fuze Android Development] arrrghhh:
Someone said these CSV's helped their RAPH...

http://dl.dropbox.com/u/12691845/RAPH_AudioPara_Boosted.zip

T'was louder. Much, much louder... I haven't downloaded it, so I'm not sure if they work. Just got a PM. Enjoy.
[Touch Pro, Fuze Android Development] :
Diam has 192 megs of ram (I'm not sure how much is free for system to use), which is the same as HTC G1/mytouch3g 32b (which has 112 mb free with a radio hack kernel)..
[Touch Pro, Fuze Android Development] arrrghhh:
Yea, but that's a native device. The DIAM is far from native Android.

Plus, 192mb is the raw amount. RHOD has 288mb, but only like 170 available to Android... 64mb is SPL, some amount is video - I want say 13mb. No clue where the rest goes, and my numbers might be off.

Either way, most of the developers have RHOD's. So that device gets the most attention... Not many devs had DIAM's or RAPH's - if they did, they either didn't stick with the project or abandoned the older device. C'est la vie...
[Touch Pro, Fuze Android Development] :
yeah that's true.. then i might fix up a rhod i have lying around to check it out, very exciting development over there with the 3.0 kernels and such :)

BTW, I saw your post @ npk from a while ago:

Was there any more news for it? I dug up some old irc logs but didn't see any progress, maybe i was looking at the wrong place lol
[Touch Pro, Fuze Android Development] arrrghhh:
They figured out how to power down the panel, but they were never able to power it back up. So... it was unfortunately never really finished/implemented, as a panel that powers down but never powers back up is pretty useless....
[Touch Pro, Fuze Android Development] ugabuga:
Hi guys just installed this and great work so far. Few questions:

- Anyone have any luck connecting a BT headset? I was able to connect mine but then it quickly lost connection so I can't test to see if it works for calls. I tried to re-pair but then the phone rebooted.

- I tried the wifi hotspot built in but my Acer A100 (ICS) could not connect to it. Now for some reason it won't even see the network which is odd. I'll have to try another device to narrow down the issue.

- I see a lot of talk of newer kernals - can someone point me to a link.

- Can't seem to get a gps lock with google maps/nav...

Thx in advance guys
[Touch Pro, Fuze Android Development] arrrghhh:
BT seems hit-or-miss. Try another headset.

Also, does the headset work in WinMo?

Do you have any logs?

Not sure how well this works on the RAPH. Works pretty well on my RHOD, but they're very different devices despite appearing so similar on paper.

Sorry mate, they only work on Rhodium's. No RAPH/DIAM/BLAC/TOPA on the newer kernels. I think .35 might work, but there hasn't been updates to that kernel in ages.

Did this work before? Are you on the newest from everything in the first post? Please post logs!!
[Touch Pro, Fuze Android Development] :
Use the attached ts-calibration if anyone is having any issues..

I had issues with calibration not showing correctly (couldn't see the points) when I installed this rom..
[Touch Pro, Fuze Android Development] arrrghhh:
Just like FRX, you have to revert to an old kernel to build a valid ts-calibration file (or you won't be able to see the calib points)

Once you have one built, hang on to it and make several copies. You can re-use it again and again.
[Touch Pro, Fuze Android Development] Hobbyschrauber:
My Raph100 boots up to simcard unlock screen, after 2 numbers it reboots to Winmo.

Used csv files from here snd my calibration file from froyo 7.1
[Touch Pro, Fuze Android Development] arrrghhh:
After 2 numbers?

You shouldn't have any SIM lock codes on your SIM card. Remove 'em.

Perhaps try to grab the CSV's from your own ROM. Just to ensure...

Lastly, have you tried without the SIM card inserted at all? Just trying to rule that out.

Oh, and of course - other than the CSV's and the calib file, you're using EVERYTHING from the first post? Haven't swapped out anything/reused anything/etc?
[Touch Pro, Fuze Android Development] djughed:
GBX0C_Full_Bundle_2012.04.24 working perfect with lighting launcher 3

hey guys

been following this forum for a while now. loving this android on my htc!!

ive only ever had 2 problems on my device - raph100

- battery dies too fast

- wireless crashes android

i installed lightning launcher 3 on the handheld and ive squeezed 5 hours of usage on a charged battery. apps working perfectly. played games like nfs undercover which is pretty epic.

but overall i can actually use this phone day to day now on android (its good for me as i have a blackberry which has the same amount of battery life). it is stilll buggy-ish but nothing that will kill you!:D :highfive:

:good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good: :good:
[Touch Pro, Fuze Android Development] ZeRoX93:
Hey guys...I yesterday installed android GBX0C and I don't know how, but when I turn off the display it goes completely black like in WM... ist that normally or did my display turn off like it should do in android?

Because when I had Froyo installed when I turn the display off you could see that the display wasn't off, you could see light coming from it...
[Touch Pro, Fuze Android Development] arrrghhh:
That sounds like an improvement, no? I'm not sure what you're expecting, you want you screen to always be on?
[Touch Pro, Fuze Android Development] Otsego.wupiwupi:
Simply Amazing!

Absolutely amazing that this old phone has such a stable build of Gingerbread running. I loved my Fuze before it died, the fact that there is still development warms my heart. Although I am pretty sure this phone is physically capable of running ICS, I don't see ICS ever coming to this device. Nevertheless, a solid final build of GB would be a crowning achievement in development for the Raphael. I wish arrrghhh, and all the testers all the luck in the world. Should I ever find my way out of debt, I will make a point to donate to this project.(as long as the donation links still work)

Feels like a bit of a useless post, reporting no bugs, giving no real help to development, etc. I apologize, but I just felt compelled to say how truly happy it makes me to see this great phone still being appreciated and developed for.
[Touch Pro, Fuze Android Development] ZeRoX93:
No i won't...but I been reading and everyone was complaining about that...But somehow I don't have that problem :) And I don't know how :)
[Touch Pro, Fuze Android Development] arrrghhh:
Oh, well the panel is probably always on - backlight is off. So the battery drain is pretty bad.
[Touch Pro, Fuze Android Development] ZeRoX93:
But when I used older version of GBX you could see a light coming from the display when you turn it off...but know you don't see anything...it's completely black
[Touch Pro, Fuze Android Development] arrrghhh:
OK, if you say so...

To me, light indicates the backlight is on. If the panel is off, and there's nothing displayed - there is literally no way for the end-user to notice the panel is still on.
[Touch Pro, Fuze Android Development] Nubrig:
Is the development still in progress? And is it possible for a ROM release with permanent istallation?

Seeing android run on my old Raphael is amazing, and GBX0C is such an improvement from previous versions!
[Touch Pro, Fuze Android Development] arrrghhh:
Development really hasn't moved much lately, there's not really any active devs left.

The RHOD or Touch Pro2 had quite a few devs up until just a few months ago... but most of them have moved on as well, and honestly they were driving development of the whole XDAndroid project for about a year.

Unfortunately I don't think the RAPH will be getting NAND - it does take quite a bit of work and changes, and I haven't seen anyone with a RAPH lately who would be capable of doing it.

Not that it's impossible - especially since the groundwork has already been laid for the TP2, porting it to the TP1 shouldn't be too big of a boar - but unfortunately it's way above my pay grade. All our code is open source, including the LK bootloader which ACL graciously ported to the TP2 - so have at it!
[Touch Pro, Fuze Android Development] osrix:
Hi mate, are there any Kernels we can use on the Touch pro, to allow OC or better stability, memory handling, sd performance since there is pretty much no chance of nand??

Nice to bump into someone active in these forums, feels like a ghost town!!
[Touch Pro, Fuze Android Development] Nubrig:
I only wish I knew what to do with the source code, I'm a noob at this, I can only try and test different roms :p
[Touch Pro, Fuze Android Development] lohtse:
does this write over wm or is it a case of on reboot you boot to wm?! if reboots to wm then can we have a dual boot option etc?

just curious as thinking of playing with this for a while..
[Touch Pro, Fuze Android Development] R^7Z:
Last I checked, there was a dual boot option available (haven't looked at that thread in a while) but even then, one would still require the microSD card.
[Touch Pro, Fuze Android Development] lohtse:
so basically I can dual boot like I do on my Kaiser!? thats great to know...
[Touch Pro, Fuze Android Development] arrrghhh:
Yes, look into Gen.Y. There's currently no way to wipe out WinMo in favor of Android (on the RAPH). It all runs off the SD card for the RAPH.
[Touch Pro, Fuze Android Development] arrrghhh:
Excuse me, what does this have to do with the Touch Pro? Or the XDAndroid GBX0C build?
[Touch Pro, Fuze Android Development] lohtse:
Anyone overclocked this rom?if so what values etc worked and did you use overclock widget or setcpu etc?
[Touch Pro, Fuze Android Development] arrrghhh:
This isn't a ROM, it runs off the SD card.

And you overclock thru the startup.txt. Please see the FAQ.
[Touch Pro, Fuze Android Development] lohtse:
technically it is still a rom. It is just not flashed to the device as are others...

as to my question, I had read the thread from the FAQ's and was asking if anyone had actually OC'd the "rom" in the correct thread.
[Touch Pro, Fuze Android Development] arrrghhh:
If you REALLY want to get technical, the term 'ROM' is a misnomer in general.

This isn't a ROM.

Overclock thru the startup.txt as per the FAQ. Thanks.
[Touch Pro, Fuze Android Development] korna:
Ugh .. I get random crashes with this build. I like the build because it runs really smooth.

Anyone know how to solve this?
[Touch Pro, Fuze Android Development] R^7Z:
Any clue as to what you were doing prior to the crash; does it happen consistently after a specific action?
[Touch Pro, Fuze Android Development] korna:
It looks random or time related. During a crash the device gets stuck. The image freezes for a few second. Then a reboot fellows.

First time I was using the data.img of FroYo FRX07.1. (don't remember what I was doing but it did not last long).

Second time was a clean GBX0C 2.3.7. I went into settings and after entering and changing settings in two menus it crashed when entering the third.

Third time I was trying to move the android avatar from the desktop to the bin. It crashed before I could reach the bin.

Fourth time I did nothing and it crashed after a few seconds.

I run FRX07.1 without problems. Although it is a bit slower and I don't have audio with bluetooth.
[Touch Pro, Fuze Android Development] arrrghhh:
Try a different SD card perhaps, one with better random read/write performance.

Also checkout my Speed Improvements thread. Pay special attention to the SD card section - that buffer setting can really make or break your device.
[Touch Pro, Fuze Android Development] Nubrig:
Even though noone is in development any more (apparently) I'll state an issue I've had. The battery meter doesn't work right and sometimes the phone turns off. What happens next is that when I power it on it's stuck in a loop and doesn't boot. Only after a few tries and having it charged while turned off it powers on and I'm able to run Haret once again. Could it be the battery's fault and not a software issue? In WinMo the meter works quite well.
[Touch Pro, Fuze Android Development] R^7Z:
Without proper calibration, it's difficult to say whether it (the battery meter) was or was not accurate. I usually charge my battery to around 80% before booting into Android/running HaRET and majority of the times, Android shows it as 100%. Now if you ran a battery meter similar to TBattery in winmo, it would say something similar: 100% (for the MS and PA percentage) and 80% (for the KADC and RARC values). Obviously the latter is what I look at prior to disconnecting my device from the charger and booting from winmo to Android. Additionally, if you have an older battery that doesn't keep its charge (like it should), it would further the task of attempting to calibrate the battery in winmo and affect what is being reported in Android.

Now on to your issue with the phone turning off on its own. I've experienced this but it was not always due to the battery being completely discharged. Sometimes it would crash for another reason and the back/battery would feel warm/hot nine times out of ten, which would indicate that there was a process being hung or something similar (probably due to the fact that the display was never shut off/collapsed properly). Unfortunately, I don't think there was any solution (for our device) to the display only being lowered and not properly collapsed. I think I had a work around but since Android tablets have become more affordable, I've opted for the actual experience and since, have left my RAPH to it's own dealings. It's still a decent camera and mp3 player... :D

:cool:
[Touch Pro, Fuze Android Development] Nubrig:
Yeah I just thought I'd revive my old Touch Pro, but it's so old I can't even get it sold apparently! Guess I'll have to sell it as a GPS device..
[Touch Pro, Fuze Android Development] arrrghhh:
Battery meter is inaccurate, and since you're not shutting down the phone properly (sudden battery failure) the data.img is becoming corrupt.

I'm betting if you start with a new data.img it will work, but obviously all your personal data (from /data in Android) will be gone.

Sorry. It is what it is. Be happy it runs Android at all...
[Touch Pro, Fuze Android Development] Nubrig:
I'm really happy indeed it can run Android even this way. It just seems like it's draining power more than it charges so it cannot stay powered on for more than a day even while charging.. Anyhow, I might try a new data.img just for the sake of my quriosity..
[Touch Pro, Fuze Android Development] wizardknight:
Edit...
[Touch Pro, Fuze Android Development] Johnsmith41junk:
Verizon HTC Touch Pro .csv

Here are the files from my Verizon HTC Touch Pro, which is running the copper rom (i love windows mobile 6.5!)
[Touch Pro, Fuze Android Development] drinkypoo:
kernels

you can't download kernels from the build service any more, they are all gone

anyone have a newer kernel than what comes with this image, and is it any better in any way?

while I'm asking questions, how can you use a partitioned card? I can't find a guide. I tried adding no_partitions to the cmdline which made no sense to me and also didn't work, it just created a data.img. I partitioned the card and moved the old contents of data.img to ext2 on the second primary

edit: found the answer again, after still more searching. http://xdaforums.com/showthread.php?t=1420264&page=57

edit edit: this software is useless without ext3. it crashes at the drop of a hat, any hat, and it takes out files almost every time it happens.
[Touch Pro, Fuze Android Development] PetitPrince1893:
I'm desperated by wifi tethering - help me please!

Guys, first of all I want to thank you for your overwhelming nice work - you make my HTC Touch Pro useable. :good:

But I've got a major issue: I'm not able to provide a mobile WLAN-hotspot by my phone - neither by the native function (after tapping onto this butten I recieve a error notification and the button wents grey and no longer usable), nor by using Wireless Tether for Root Users (it says:

Uable to start tethering. Please try again!

), or Barnacle Wifi Tethering (

Starting...
Data network is ready
.ini file prepared
WIFI: Failed to load driver: Unknown error: 0
WIFI: Could not set address of wlan0: No such device
WIFI: Could not get address of wlan0: No such device
WIFI: Could not get flags of wlan0: No such device
NAT: waiting for local interface
Stopped unexpectedly!

I'm Using the GBX0C 2.3.7 (Startup: RAPH100) and modules-2.6.27.46-01365-gc8b9a4c.tar and have tried also FRX07.1_Full_Bundle_20110901 (Startup: RAPH100) and modules-2.6.27.46-01356-gd4c73bd.tar

Parts of my daily work depends on the Wifi tethering function, and I don't want to use another Smartphone than the HTC Touch Po (1).

Can you - please - provide me a solution, which is made for noobs like me?

Regards, your petit prince

http://xdaforums.com/showthread.php?t=1167324&page=75
[Touch Pro, Fuze Android Development] Supermatt01:
I know this thread is very dead now, but I wanted to mention that this works on my old TP on a 64 gigabyte sd card. Only thing is the market and a few system apps load as disabled and can't be switched on. But it's cool to know that it will work from 64 gigabytes deep. Thanks for all your hard work.
[T-Mobile Samsung Galaxy S II SGH-T989] kaleom:
So when I first got the phone I had no issues with the battery getting hot while using it and charging at the same time. I flashed a kernel and custom rom and now the battery heats up pretty good while using and charging at the same time. Not sure if this is normal, but at 1 point it got so hot that it turned my phone off. Is this a normal thing or is there something I can do to correct this? thank you:confused:

crap, I posted this in the wrong thread. I thought I was in the questions.
[T-Mobile Samsung Galaxy S II SGH-T989] Branso07:
That isn't right. I would ask a Tmobile person at the mall. Make sure your camera isn't running on three background. I had the camera running in the background during a laker game and when I pulled out the phone, it was really hot.
[Samsung Galaxy Nexus] BMWPower06:
Ok so I've been noticing that my battery life is just complete ****. Even with my 3G/4G radio turned off I can barely muster a full day, if that. So, I checked and saw that 68% of my battery life was going to Google+, so I turned off notifications and instant uploads on Google+ and did a reboot, checked my battery stats and it is still as seen below...How do I fix this?! Please help, thanks!
[Samsung Galaxy Nexus] martonikaj:
If you turned off those things then rebooted, it won't change what the battery status page shows.

That page is showing the percent of the battery each of the applications used

of the battery that has already drained

. It does not show currently what is draining or will be draining. The only way to check if you solved your issue is to charge back to 100% and drain back down, then check the stats and see where G+ is ranking on the battery drain chart.

Simply rebooting and waiting 10 minutes doesn't change the fact that Google+ drained 61% of the battery prior to the point where you rebooted, which will still be reflected in the battery usage stats.
[Samsung Galaxy Nexus] daleski75:
Are you syncing google+?
[Samsung Galaxy Nexus] BMWPower06:
Hey guys, so after I made those changes I have noticed a NIGHT AND DAY difference in battery life. I can actually make it more than 2 hours now without having to reach for the charger!
[Samsung Galaxy Nexus] Mancubus99:
I am experiencing the same issue and was about to start a thread of my own. G+ was absolutely destroying my battery. I went from 100% to 67% in a couple of hours without even using my phone. I did similar to what you did except I uninstalled the app updates and now my battery is where it should be. I don't think it has anything to do with syncing. If you look at the attached photo you'll see that the amount of data used is next to nothing. For the amount of battery drain I'm seeing you would think it was trying to upload several 1080p videos.
[Samsung Galaxy Nexus] martonikaj:
Yeah that was something wrong with the app. Wonder if you could reinstall from the Market (or restore and clear cache/data) and it'd fix it?
[Samsung Galaxy Nexus] Abufinzio:
I got that problem too, it was the sync of all photos and videos to g+

stop the instant upload, enjoy your battery life
[Samsung Galaxy Nexus] kichard:
I'd advise to disable auto sync...isn't that an elementary cause?
[Samsung Galaxy Nexus] martonikaj:
Just set it to only auto-upload while charging + on WiFi.