yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] JesusFreak316:
Booting the newest build as I write this. It's like Christmas all over again every time you release a new build. :) I just got a few questions.

1. How long should a normal boot (after the first build of data.img) take? It takes around 5 minutes every time for me.

2. Would it be possible to use the capacitive front dpad as a trackball? Since so many Android phones have trackballs of some sort that would be great.

3. Is it possible to give us the choice of boot screens? I like the nexus one, but also like XDANDROID and the apple desecration one on page 87 of this thread.

A couple little notes:

1. It still heats up for me, especially when charging.

2. It does seem even faster than before.

3. The power button isn't working to return me to the main menu, however, I haven't soft reset yet, that may fix it.

Overall, great job on everything; you are a big reason why I love XDA so much. No other issues I can think of besides for the known ones on the first page.
[Touch Pro, Fuze Android Development] chamonix:
I observed that too with tonight's build but after a reboot both short-press (home) and long-press (open tasks) were working fine
[Touch Pro, Fuze Android Development] alexisprz:
Great work!

This build is extremely fast, stable, and useable. also while trying some apps I tried the swype keyboard and it works well. it showed me a error message but just clicked okay and it works. really appreciate your work!
[Touch Pro, Fuze Android Development] manup456:
hmmm....looks like I have seen this before. I want to know how you fixed that control panel widget since I did it but want to see how you did it? Calendar widget working would like to know that and facebook icon looks like mine. I will look into this but I can tell that my work was taken. And how did you port 2.0.1 I was the only one who did it.
[Touch Pro, Fuze Android Development] babijoee:
This build is based from Zenulator over at vogue. I believe he used your build as a base also and modified it to work on the vogue. Primarily we were using a build based on a generic Eclair image and since then we have been jumping to better ports. I'll fully make this right and post your credit :)
[Touch Pro, Fuze Android Development] noellenchris:
Hey, thanks for your work getting eclair working on older devices, do you think your progress with the camera on the G1 will relate to the touch pro? That would be sweet... Thanks again,
[Touch Pro, Fuze Android Development] reekotubbs:
Does any know if data is working on CDMA (Sprint) yet?

On the first page it says that for CDMA you need the correct ZImage.

Anyone know where this is?

On this page http://glemsom.anapnea.net/android/htc-msm-android/#

it doesn't even mention CDMA.

Anyone...?
[Touch Pro, Fuze Android Development] babijoee:
okay i turned off sync by default. Set it to back on and with mic, it seems the newer kernels are breaking it. So i suggest using an older working kernel that was working for you.
[Touch Pro, Fuze Android Development] calypso666:
yeah.. had the same problem too. hope it will be resolved soon.. anyway, great job from evryone..
[Touch Pro, Fuze Android Development] babijoee:
uploading new build in abit. I've bundled it with the zimage and modules from phhussons previous pack. I suggest not to update to the latest kernel unless you dont want mic support.
[Touch Pro, Fuze Android Development] allthatinny:
i got one major problem, how do i get my keys to be remapped for the fuze?? cause i notice that they are typing like a touch pro instead of a fuze
[Touch Pro, Fuze Android Development] babijoee:
new build out. Please read the comments under the download. Very important
[Touch Pro, Fuze Android Development] noellenchris:
trying new build, adjusted startup for ralph, first boot locked up after skipping android setup, next boot locked up before I could get into settings...

now on 3rd attempt, I'm trying to turn off any gps stuff, but I may need to change startup.txt or take something out?

Ralph110

chris

EDIT: removed the PMEM from startup, trying again...should work this time...:)

EDIT2: nope still locked up, but I did manage to turn off GPS this time. Do I need to change the STARTUP.txt line "set ramsize 0x10000000" back to 0x6 ?
[Touch Pro, Fuze Android Development] babijoee:
Complete freeze? hmmm very weird. You didnt change the zImage or modules did you?
[Touch Pro, Fuze Android Development] tyguy:
Just downloaded and installed as well (ATT Fuze guess that's a 110 as well) and had a similar issue.

Forgot (call me moron) to delete the modules-2.6.27-00707-g9f1fdfc.tar from yesterday. Deleted it went with the modules-2.6.27-00670-ge0a965b.tar and all is fine, fast and stable so far (well it's just 15 min but a can google talk and get my gazillion XDA updates on my google email account.

Edit:

How can I prevent the phone going into sleep mode while charging? Didn't find a setting yet.
[Touch Pro, Fuze Android Development] babijoee:
In Settings>Application>Development>Tick keep device wake during charging.
[Touch Pro, Fuze Android Development] tyguy:
WOW this was quick!! Thanks babijoee!

... and it even works ...
[Touch Pro, Fuze Android Development] babijoee:
If you experience freezes and problems. Delete the data.img and try again. This is due to corrupt data.img. It should work after a couple of tries. Until mic support is fixed you'll have to use this. :(
[Touch Pro, Fuze Android Development] noellenchris:
thanks...that will be my next step, I put pmem back in startup.....hopefully I'll get it working.....is the google sync working this time?
[Touch Pro, Fuze Android Development] babijoee:
YEP sync should be working. the pmem extra isnt implemented within this kernel. =(. the mic shouldnt be too hard to fix. I'll talk to phh tonight about getting this fix top priority. :)
[Touch Pro, Fuze Android Development] babijoee:
I have removed the new build until mic is working. There really isnt a point releasing a new build that is actually worse. :rolleyes:
[Touch Pro, Fuze Android Development] TheDeadCPU:
Smart indeed, but Babijoee, PM me if you need Mirror for your packs ;)
[Touch Pro, Fuze Android Development] andre.mud:
Installed the new version (before it was removed). After a few freezes i used the 'old' startup.txt. It's working fine now. What is meant by the mic not working? I can make calls and this is working fine. Data is working. Google sync is working.

RAPH100

With regards,

Andre
[Touch Pro, Fuze Android Development] f_mulder:
Hi.

First of all I want to say my big Thank You :-).

And here are my 5 cents in problems regard.

My first problem, and that might be a hardware problem, is following me since the first time I have started to test Android.

Every boot ,no matter if new data.img is created or the one from previous boot exists, I get fsck's complains regarding that FAT32 FS.

So as I said, it might be a HW problem,but in Windows or as a USB disk, this same card works well. So I am still not sure what the problem is.The card itself is formatted as FAT32, may be I should format it as FAT instead?

I am also planning to buy another one to be 100% sure where the problem arises from.

Second thing. Problem observed in build from Jan 3.

During a call, if you press menu (Raph's Home) , you get a menu on the screen.

Problem is that icons and text of these buttons don't fit the area where they placed, so that I couldn't understand what should these buttons do, except for the bottom line (there are 3 lines) buttons (Hold ,Mute,Speaker,Bluetooth).

That's all for now, and thanks again.
[Touch Pro, Fuze Android Development] f_mulder:
When you make a call, does the person you call to (called party) hear you?

If he doesn't, that means the mic is not working...

Regards.
[Touch Pro, Fuze Android Development] andre.mud:
This is working fine..

Andre
[Touch Pro, Fuze Android Development] bxmatus:
Except mike this is the most stable version ( combination of kernel and release ) on my phone, first time in last few months my phone survive night not connected to charger, at evening it was 100% and at morning it wake up ( first little miracle ) and battery was over 50% ... this never happend before. Great job to everyone involved.

Matus
[Touch Pro, Fuze Android Development] andre.mud:
The ramsize value in the new startup.txt =

'set ramsize 0x10000000'

The old one was '0x6000000'

I don't know if this could be a reason for the freezes? Going to try to reproduce this.

Andre

Edit: Phone freezes with 'set ramsize 0x10000000' going to try the old one again.
[Touch Pro, Fuze Android Development] tyguy:
+1 can make calls and the other party can hear me loud and clear.

[XDANDROID.4.1.10 - meanwhile removed]
[Touch Pro, Fuze Android Development] djvinz:
andre.mud, these RAM settings are correct.

tyguy, andre.mud: as babijoee said, of course the mic is working in the pulled release, it's an old kernel!

Right now we're waiting for phhusson (or other geniusses) to fix the mic in the newest kernel, so that we can use power_collapse and other recently added features, that are not present in the mic-enabled-old-kernel that was included in the pulled release that babijoee made.

So: just a few more hours of patience!
[Touch Pro, Fuze Android Development] andre.mud:
Ok. so i was using an older version. :o My mistake. Will wait for the new release.

Andre
[Touch Pro, Fuze Android Development] gamikzone:
hey guys why has the pack been pulled out? is it being updated? or is their problems with it?
[Touch Pro, Fuze Android Development] Nonan:
It was a small step down in capabilities with the new kernel. Se until the mic gets fixed. We're twiddling thumbs :)

*We: Laypersons not capable of working with this programming-stuff.
[Touch Pro, Fuze Android Development] babijoee:
How about you mirror them everytime :D. this time i'll make sure everything works before i release it XD
[Touch Pro, Fuze Android Development] Arkhee:
Hi guys, and thanks again for the hard work !

One question and one suggestion for today :

Do you know any good tutorial to learn Android in-depth use ?

Off course, I parse all menus and so on, but somehow I miss handy shortcuts to do things faster and easier. For example : I discovered in this forum how to change the entry mode on a text field (long-click on the text field).

My suggestion now : how about setting up a poll to collect review data ?

It would be the same poll for every release and sub-release, there would be, say, 5 or 6 sections, 5-10 questions in each section. At the end the team would have a more efficient way to know how the latest build works, what were the real improvements and so on.

I tried twice to write a review, but I don't know which information you need, writing know a full review is quite time consuming (considering english is not my native language), and extracting relevant data from such a review may also be time consuming.

Well, my 5 cents you know ...

And thanks in advance for next build ! You're going at a tremendous pace, I still can't beleive Eclair is already running so smoothly on my TP, when so few cellphones support it yet on the market ! Grats !
[Touch Pro, Fuze Android Development] babijoee:
Yeah i released a a new pack with old kernel that has mic working. However it doesn't have all the new optimisations. Power save, sleep, faster and more stable. It will bring up too many questions and i'm too lazy to answer -.-"

thus removed for the time being. It should be back up sometime tommorow or early this morning.
[Touch Pro, Fuze Android Development] f_mulder:
Reposting my post, before it got lost...
[Touch Pro, Fuze Android Development] babijoee:
err.. no its not. :confused:
[Touch Pro, Fuze Android Development] f_mulder:
I am a bit :confused: (confused) with your answer...

Actually, I didn't understand it at all...

There are 2 problems mentioned in my post...

Or you just wanted to say that my post have not got lost?

Regards.
[Touch Pro, Fuze Android Development] djvinz:
Yes, he meant your post isn't lost... I can still see it too... Try to not spam the forum with double messages.

As for your questions: I also get a fsck every time I boot Android. I suppose it's normal. It's still working with no problems at all, just creating one more "fsck" file every time you boot android. This is more of an "esthetical" problem, than a functional one, I think. I wouldn't worry about your hardware too much.
[Touch Pro, Fuze Android Development] reekotubbs:
Where can I locate the correct ZImage for sprint (CDMA) TP2 (Rodium)
[Touch Pro, Fuze Android Development] pootney:
Is there anyway to disable the annoying battery warning?

thx and best regards

pootney
[Touch Pro, Fuze Android Development] chamonix:
Load the battery? :-D

Seriouly, the preciser the question the better answers you will get...
[Touch Pro, Fuze Android Development] bangbang023:
I am getting VERY intrigued by this. If you can get it working well enough and battery life isn't the stated "11 hours on standby" I've seen mentioned from previous builds, I may have to donate some money your way.
[Touch Pro, Fuze Android Development] babijoee:
New rootfs.img uploaded in 1st post :D

Delete or replace the existing rootfs.img with the new one. Delete data.img also.

Happy Android Eclair on your device :D

Enjoy guys and as always post your feedback. :D
[Touch Pro, Fuze Android Development] windserfer:
downloading!
[Touch Pro, Fuze Android Development] cruzzmz:
downloading now ... will post feedback

btw this new build can only use the radio?

Updated: gr8 job, wakeup sleep OK, very responsive ... batt life will inform later, sms, wifi still no go. Overall :D
[Touch Pro, Fuze Android Development] pik0n:
Tested! During calls, the battery is a little bit crazy. The dial window ( I mean the window when you press the buttons to call) Is wrong in diam100, some buttons are little and 1, 2 and 3 can't be seen, because they are hidden by the lab. Excellent wake up! Excellent sleep. The name of operator it's correct! yeah. (Vodafone ES). I can't send sms, ( I can't send sms too with any oter build, i've tried everything but, nothing.. try to fix it. Please! Checking the battery life, with windows mobile is for 2 days. I'll post some feedback.

Thanks for your work.

DEVICE: DIAM100
[Touch Pro, Fuze Android Development] Spud1:
Thanks for your work on this - downloading now to give this a try on my XDA Serra (RAPH100 iirc).

Fingers crossed you can figure out the issue with sound also, you have made great progress in such a short space of time..legend!
[Touch Pro, Fuze Android Development] chamonix:
Damn! was almost there myself ;-)

Congrats babijoee, works like a charm here: placed a call
[Touch Pro, Fuze Android Development] babijoee:
Try changing "lcd.density=210" in startup.txt
[Touch Pro, Fuze Android Development] gajdik:
No problem with sms here :) Thanks babijoee
[Touch Pro, Fuze Android Development] windserfer:
diam100

Works well but a little bit slow

wrong dial windows, i'm gonna test with "lcd.density=210"

can receive sms but didn't test sending

the lock password doens't work?
[Touch Pro, Fuze Android Development] pik0n:
Perfect. Solved! It's amazing how people like you can get running Eclair in a very very short time. Legend +1!
[Touch Pro, Fuze Android Development] pik0n:
Can you tell me your sms service number? Have you put 0034 (if its spain) or +34? Thanks!

BR
[Touch Pro, Fuze Android Development] NoteGarner2020:
Cool dude just tried the calling awesome. I like the UI.... When I can test sound.
[Touch Pro, Fuze Android Development] herpez:
I think the most needed here is the sound because we can make calls but not hear or talk :(

Thanks !
[Touch Pro, Fuze Android Development] kuilboer:
Runs like a charm on BLACKSTONE, Outgoing and incomming calls/sms,

Further same as on your devices, no audio, DATA, wifi or Bluetooth.

Thanks for all the good work.

Also have a look at the #htc-linux team thread over at the Blackstone forum:

http://xdaforums.com/showthread.php?t=584559

Those are the guys are very succesfull running Android with phussons images on BLACK/DAIM/RAF.

It might just help to compare images. . .

Good luck and kuddos to Babijoee. Just let me know when to test any progressions ;-)
[Touch Pro, Fuze Android Development] Erik_PLD:
Working perfect on my Diam100. Only known bugs still there. 210 lcd density is almost perfect, but some apps left black stripes in both left and right sides of the screen.

Hope this comment is useful in some way.

cheers and congratulations for the goooood job!

tnx!
[Touch Pro, Fuze Android Development] GeezyAF:
Clearing my 1.6 setup and trying this out on a Raph800.
[Touch Pro, Fuze Android Development] PoW3r:
But the Gps?
[Touch Pro, Fuze Android Development] GeezyAF:
Took a little while to boot, but it's up and running now.

Reports "Sprint PCS" at the top right of the lock screen.

Still says 5% battery, like 1.6.

I'm likin' the progress.

Keep up the good work!

EDIT:

I received an incoming call, but can't send text messages.

I could on 1.6 though. Not exactly sure what is the problem.
[Touch Pro, Fuze Android Development] babijoee:
sms is weird as for some devices it runs flawless. Mine for example is raph100 with no modification to run sms or send them. Working from day 1
[Touch Pro, Fuze Android Development] babijoee:
@ charmonix: how goes the battery hunt? Any new development for more precise battery meter? iirc thats what you were working on right?
[Touch Pro, Fuze Android Development] chamonix:
-rrrrr :P

Yes indeed but I got lost in power management stuff :) I'll grab my code again and submit it to phh for review :D
[Touch Pro, Fuze Android Development] herpez:
My report:

Even being a known bug or problem, when i click the android in the wizard, it freezes. The screen dont respond anymore but the volume button works.

Hope its fixed soon.

GOod work guys!
[Touch Pro, Fuze Android Development] f_mulder:
Actually , I am not talking about these small files. These files were created when I used Donut. Now the fsck complains a lot more, and my Raph even gets stuck during boot. And no more these files anymore.

And one more thing. Once after running Donut , I had to run checkdisk on the card, so my card got wiped. I've got a lot of "Foundxxx.chk" files on it , instead of data...

In spam regard I can say that usually I am a polite forum user :-) , but this thread is updated very fast, and people tend to read latest page , and not to look back, so I was afraid the message will get lost :-).

Regards.
[Touch Pro, Fuze Android Development] klinux:
disable the annoying battery warning

insert htc_battery_smem.fake=1 to your startup.txt under set cmdline quotes this way you have charging state enabled even if the charger is not connected

hope it helps

cheers
[Touch Pro, Fuze Android Development] babijoee:
I have never seen someone quote a post so that it does not get lost. :p

You're last sentence is quite true, but not all member skip. So please dont double post or quote a previous post :p
[Touch Pro, Fuze Android Development] allthatinny:
well i could say this, this release is far from being used as my main os, i left android running over on my phone on purpose to see how it affects my battery and got up with my phone completely dead, lol, mic dont work, txt dont work and while have it plug in and i was using it, the phone got extremely hot

i have a fuze btw

i have used previous ver of android and never bother with it cause they been very unstable, this one is very stable and usable but far from being a main OS unfortunately, i love the new features in this release, almost feel like i was on a andriod phone :P

also my keys are not mapped properly, instead mapped like a touch pro so yuh i guess its back to WinMo for me :(

oh and P.S. bluetooth still dont work for me :( wifi does though :)
[Touch Pro, Fuze Android Development] sleepnow:
I don't get posts like this one from asshatinny. Guys, this is an ongoing project that isn't quite ready just yet to be used as a replacement for WM. If he read back a few pages there are fixes or workarounds for some of the things he mentioned.

I've been following and testing since late December, and its amazing how far the project has come in this time. It is my understanding that those working hard to make this possible have run into a few hurdles with regard to getting their hands on the closed source parts of the code that are(?) required to get some features working.

Hopefully they'll work their way though this and maybe one day we'll have a working android that we can flash on our phones. Until then, lets keep testing and posting _useful_ feedback, and donate!
[Touch Pro, Fuze Android Development] Noonski:
I still think allthatinny's post is more positive then just his remakrs of the known issues.

Earlier builds of half a year ago didn't even get my attention to try them on the device, with so much not working.

As far as i'm aware this is the most promising project so far and it's been fun just trying it on.

For the developers a question (as this is not my cup of tea), would it help if there was a Very clean rom with all the unneeded WinMo Services and Apps disabled or removed?

(Cooking Winmo is more my cup of tea and it would probably be easy to get a group together of senior Cooks to work on such a build)
[Touch Pro, Fuze Android Development] Insaneboy:
Looking at your posts, i'm going to assume that you have a blackstone.

The startup from the 3.01 for the blackstone has wrong calibration values.

Try with msmts_calib=0x395.0x3c9.0x79.0x77

If you dont believe me click the upper right corner of the screen and the skip button will be clicked. :)

If you don't have a blackstone - ignore me.

Otherwise that build is great (aside from the mic thing).

If the "faint backlight on thing, while screen off" is fixed, it'll be a release candidate for a ROM :P (provided that you don't care for camera and gps like me).
[Touch Pro, Fuze Android Development] blurp76:
Im not sure if it's been noted before but on my DIAM100 with the last build that's been pulled, i can't seem to stop WiFi, sometimes the phone completely freeze, other times the disabling never ends and icon is greyed.
[Touch Pro, Fuze Android Development] babijoee:
Since the build was pulled, its not up for support. Please dont ask any help for it :)
[Touch Pro, Fuze Android Development] noellenchris:
happened to me too on the Fuze...
[Touch Pro, Fuze Android Development] blurp76:
Didn't mean to ask any help, i just wanted to report this behaviour. Thanks for the great job, i hope it'll be fully functional someday.
[Touch Pro, Fuze Android Development] allthatinny:
wow dude really, u gonna insult me over voicing my opinion and reporting a some bugs i discover while using the OS, its ppl like u that "REALLY GRINDS MY GEARS" coming home from work and reading such a post when all i try to do is give a helping hand with my opinion which is what MOST betas of ANYTHING ask for, i mean thats the point of a beta right? i mean thats why they ask u to fill out surveys and report bugs, anyways thank you very much, u just completed my day
[Touch Pro, Fuze Android Development] J-Hop2o6:
*subscribed to follow development*

damn this is goin fast.. cant wait to see the next release.. hopefully outgoing txt, accel./g-sensor, back speaker, volume rocker, the end key, the KB arrow keys mapped correctly, keys light up upon press, sleep, and etc. gets fixed. :cool:
[Touch Pro, Fuze Android Development] vpgtd:
Why was the latest build pulled? I have it running on my att fuze with no problems other then stop errors when things dont respond. i have not tested everything on it yet but from what i have played around it seems to work really well.
[Touch Pro, Fuze Android Development] J-Hop2o6:
read some ealier posts.. they said sumn about the mic not working with the new kernal, so they just pulled it until the mic gets back to workin again
[Touch Pro, Fuze Android Development] vpgtd:
i did read that. I was thinking it wasnt a global thing since my mic works. and i am using the latest build from 1-3-10