yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Android Development] arrrghhh:
Heh, I'm not sure if this is the best way but I look at the build logs, hit CTRL-END (go straight to the bottom) and look for the last line, like this:

Packaging modules into package: modules-2.6.27.46-0[B]1262[/B]-g4a804e5.tar.gz
[Touch Pro, Fuze Android Development] Eligos4ever:
Thanks arrrghhh!

BTW, my phone is working perfectly. It's fast, wifi works, all my gmail contacts are in, no more split screen...I'm happy. When the battery gets better and we have the cam and BT then it will be complete. It's uncanny how well this alpha build is running.
[Touch Pro, Fuze Android Development] arrrghhh:
Yea, stinebd really did a great job on this image. Only going to get better too!
[Touch Pro, Fuze Android Development] xtremists:
heyyyy arrghhhh is there anyway to resolve diamond screen problem like blackout screen when unlocking device by pressing power button its like black and i have to press buttons
[Touch Pro, Fuze Android Development] R^7Z:
You mean like the SOD being mentioned in other threads? I posted a work arouond that works for some but not all devices in that thread... :)
[Touch Pro, Fuze Android Development] stinebd:
Evening everybody. Got another testing image for you.

Changes:

Google apps should all be fixed now (tested with gmail particularly) -- we've switched javascript engines and are now using V8

The accelerometer driver I've blogged about is now included in this build

Android codebase sync'ed to latest 2.3.3

Not included in this build is some preliminary work on GPS. It crashes Android (and freezes my RHOD400) so it's been removed from the system image.

Proper hardware 3D driver provided in this system. Neocore still doesn't work.

Gallery3D added to the build to test a possible fix for rotation issues. I'm mainly interested in results on RAPH.

Thanks again for everybody testing and providing feedback on these releases. This is signed so old data.img from our previous Gingerbread tester release may work. Again, if you have any problems, we suggest clearing out data.img before reporting them.

The system image is available for immediate consumption at http://files.xdandroid.com/system-gingerbread-testing-20110227.zip.
[Touch Pro, Fuze Android Development] arrrghhh:
Thanks stine.

I'll update the first post as soon as I test this and make a new bundle :p.
[Touch Pro, Fuze Android Development] djdafreund:
wow, very cool news, thanks very much for the hard work, downloading now to get some feedback for my raph800 to give here. Also, thanks arrrghhh as well for your work,and being so helpful to others. (i know its not always easy,especially those that don't follow simple directions), THANKS. Hopefully i'll be able to give usefull feedback on behlf of raph800 users out there.
[Touch Pro, Fuze Android Development] Eligos4ever:
Loaded the new http://files.xdandroid.com/system-gingerbread-testing-20110227.zip

Kept my old data.img. Everything seems to work correctly.
[Touch Pro, Fuze Android Development] djdafreund:
i'll have to grab a fresh copy and apply the new system.ext download with new changes. Maybe something got changed from a couple updated files from f22 update links on first page, as accelerometer not working still,and 3d driver not seeming to work. Tried with glow hockey (only game demo i downloaded so far) and is still like 0.3fps. Will try same in android 2.2 to see if it's just the game for further testing. Main home gui is fine and moves normal. Overall it's nice though (even before last nights new file release. More green's and black used all around. I like it!!
[Touch Pro, Fuze Android Development] funkys:
On my DIAM100 gsensor is behaving strange. When I start some program screen rotates immediately in landscape, but if I put my phone in landscape then programs flip again in opposite direction.

best ragards
[Touch Pro, Fuze Android Development] R^7Z:
I agree, that is quite odd as my Fuze does not exhibit this behavior. I am curious though, what happens when you disable auto rotate?
[Touch Pro, Fuze Android Development] stinebd:
You need the latest rootfs.
[Touch Pro, Fuze Android Development] djdafreund:
Ah, ok, i should've known, sorry. Thanks so much for all your hard work!!! Already we're so close to getting what we got in 2.2 (even seeing the new camera merges!!! Jeesh, thats FAST!!!) in 2.3 (if not superseeding 2.2 technically since camera is in the official trunk now.) in my eyes.

THIS IS GREAT!!!!! Thanks SO much for the hard work put in to this. :)
[Touch Pro, Fuze Android Development] emc02:
I am currently "testing" the latest Froyo XDAndroid and its ok for everyday use ;-)

Now i want to test this release and i am not sure what i have to update. I've read, that it would be enough to change the system.ex2 file.

Is the rootfs and zImage the same like in the Froyo-Version?

Should i delete the data.img, or could it work with my froyo-settings?

Thanks!
[Touch Pro, Fuze Android Development] Eodun:
Hm, it doesn't let me sync with my gmail account :p

Just changed my froyo system.ext2 by the GB one. Will do some tests, perhaps is the data.img or so.
[Touch Pro, Fuze Android Development] GoldAngelo:
You sholud download latest rootfs. As for the kernel + zImagine I'M not sure, but if you test it and will not work simply update the kernel + zImagine :-) I delete my data.img.
[Touch Pro, Fuze Android Development] R^7Z:
How many times have you attempted to reboot back into Android? I had to do it more than once. If all else fails, let the system recreate the data.img file by deleting it or relocating if you want to retreive the info later. Just an fyi but this has been stated more than once in this thread... :)
[Touch Pro, Fuze Android Development] Eodun:
Yeah, I've made a backup in titanium and also in my pc. Sorry, I've been following the thread and didn't remember that being reported (too much diagonal-reading).

I rebooted twice without luck. Anyway, I think I'll stick to froyo a bit more, though GB seems more agile and pretty.
[Touch Pro, Fuze Android Development] R^7Z:
+1 on the froyo data.img deletion

In addition, you might want to use THIS kernel package.

NOTE:

If you use the kernel package mentioned earlier, you will need the ts-calibration file found in the first post of this thread ( you aren't getting off that easy! :p ;) ) Unless you have a working ts-calibration file, ofc

To be more specific, troubleshooting steps mention to delete the data.img file and to include stinebd's post with the link to the test package. Needless to say, I do sometimes feel like a broken record player at times but I suppose we all should be used to that by now... :p

:cool:

n-Joie! (Enjoy)
[Touch Pro, Fuze Android Development] djdafreund:
Here's some feedback so far on my raph800. I grabbed newest rootfs file (latest available according to link on first page,not f22's though,stock one, is "rootfs-20110224" , an rotate is working mostly, but help upright, it flips 90% right (clockwise), held left (with dial on right side of phone) it rotates upside down, right help right (with dial on left side of phone) it's upside down (mostly a fix of making of of the 3 numbers a negative to revers left,right in startup file), and upside down, it's just flipped), only thing weir d not logic sense is rightside up, isn't reversed but rotated). Possibly something still not updated (and I will wait until a new complete package to make sure, as i'm using all updated files from all the links in this thread mentioned so far), and 3d accell still doesnt seem to be working, unless forced3dhw needs to be added to work, like froyo initially did. I'm using newest file, and the newest one stinebd mentioned i needed. Which newest I found from link here was 2-23 dates, seemed older to me though.
[Touch Pro, Fuze Android Development] Zopaa:
My first real post so take it easy please. :)

I got totally frustrated with my awful WinMo on my rhod400 (US/CDMA/Sprint) so I decided to plunge in and move to Android. Naturally I wanted to try the latest and greatest. So here is my feedback after about a week of use:

Issues:

1. Phone disconnects from network (goes into Airplane mode). There is no other way to fix this aside from taking the battery out. Sometimes this needs to be repeated a few times before phone is working again.

2. Manually putting phone into airplane mode is also deadly, as there is no way to switch the mode without a hard reboot.

3. Sometimes phone loses connectivity to 3G only. Hard reboot is the only fix.

4. F22 rootfs is the only way to get home button to work. Power button (button 8 on top) is always a power button, and with other rootfs' so is the Call End button.

5. Built in Mail app is not working, although other mails apps are working fine

6. Expected things are not working such as GPS, G-Sensor, Camera (despite attempts to make it work based on the camera thread)

So due to issue number 1 the build is not really suitable for my daily use. Still, even Alpha version of Android blows WinMo completely out of the water. Although I may need to switch to Froyo unless I find a fix to the show stopping issue, I can't make myself go back to WinMo… Android is simply too addictive, to the point that I'm willing to live with somewhat unstable phone for a while.
[Touch Pro, Fuze Android Development] arrrghhh:
Uhm... Why are you posting in the Touch Pro section? There's a Touch Pro 2 section, and a thread in that section for GB for the TP2.

If you want a more stable build, try Froyo. Gingerbread is very bleeding edge.

Also, some of your report confuses me. Built in mail app works just fine, as does the g-sensor - assuming you're on the newest image.

I need to make a new bundle, waiting for stine to release another image update which seems imminent. No point in making a new bundle for a minor release when a major release is just around the corner.
[Touch Pro, Fuze Android Development] djdafreund:
I'll just wait til then, i grabbed every newest version file i can find in this thread (including newest image, and system file) but some thing's are still weird going on. Like rotation working abnormally (both axis flipped, with exception of upright is somehow rotated 90 degrees counter clockwise, and 3d accel doesn't seem to be working (do we need the command added in startup to force it like android2.2 did initially?). but was going to just wait til your next complete, since i'm obviously doing something wrong with files i grabbed. I got them from the only usual places mentioned here though, and some things ARE working, and some not. I do LOVE it so far, runs good.
[Touch Pro, Fuze Android Development] Rick200SX:
Im running this version now on my Raph. Runs well! Camera doesn´t work indeed, but ah well, it´s been this way since forever :P

I have downloaded some apps from the Market Place which i found useful: Talkdroid messenger (Windows live messenger, the best: It lets your computer/laptop logged in, while also logging in on your android phone, awesome), Tweetdeck, PocketCloud (this is a RDP/VPN client. I was looking for a good client for a long time, and i can confirm this works very well :))

I even tried downloading Angry Birds and playing around abit. It works! Okay it isnt quite as fast, but hey... It's and old Raph after all ;) It's fun to play tho.

Some apps crash from time to time... Dunno why, but prolly because this version is on the alpha stage orso :)

Anyway, nice package!

Btw im running windows mobile 6.1 on my Raph. Here this package doesn't give me any trouble, but on another Raph phone with 6.5 on it, it doesnt work aswell. The calibration went wrong, so i put in the calibration numbers of my device. Then the screen worked, but still the buttons were going crazy, like if someone randomly pushed the buttons... Very weird! Someone experienced this aswell?
[Touch Pro, Fuze Android Development] stinebd:
Evening folks. Got another release for you tonight!

Decent list of changes...

Further keyboard size fixes, should be perfect now (and goes fullscreen in landscape)

Updated Google apps package (Books phone version is now included)

Switched to GLES1.1 library with patches from bzo (you probably won't see much difference here)

Phone app switched to touch-friendly in-call user interface (and fixed its layout on Raph)

Regressions from the last system image that were fixed:

Added the missing camera bits

Re-added a graphical speed-up that was accidentally lost in merge

A few of these changes are important.

The software keyboard should be considered functional (but with some small bugs) at this point. If you see any issues, please report them on the bug tracker after searching for them to make sure it's not a dupe.

The Phone app change is important for a couple reasons. On Rhodium, this allows us to set the end-call key to Home without crippling the user in a call, since there's now a nice big button on the screen for hanging up. This will be further improved by implementing the proximity sensor. Our support for VGA devices precluded using this UI due to the buttons blocking some of the dialpad keys in the in-call screen. This has been fine-tuned to be useful on both resolutions.

Google Apps speaks for itself. Updated stuff, woo.

Anyway, without further ado, you may download the updated system image.
[Touch Pro, Fuze Android Development] djdafreund:
Thanks big time stinebd!!! Wow, nice changes!!!
[Touch Pro, Fuze Android Development] arrrghhh:
First post updated with a new bundle ;).

Thanks again stinebd!
[Touch Pro, Fuze Android Development] MFaust:
could someone pose some screenshots?

and i have a question... you must format your card whit ext3 ore something and to make 2 partition for this to work?
[Touch Pro, Fuze Android Development] R^7Z:
Why do you want screen shots of a stock-like Android build bewilders the crap out of me...

afaik, XDAndroid requires only one FAT32 formatted in anything except windows partition. Neopeek variants require one FAT32 and one ext2 partition. Please keep questions relative to the thread you are posting in. (why do I still feel like a broken record???)
[Touch Pro, Fuze Android Development] davew:
new keyboard is too big for DIAM100?

I'm having a spot of bother with the new keyboard. I'm using today's new full bundle, no other changes, on a GSM DIAM100.

I was just setting up my wifi (I use a static IP address) and the dialog to enter the IP address shows just fine with the white text area and ok/cancel buttons. Then the keyboard pops up and its so tall, the IP address dialog resizes itself and the white text area disappears. If I'm careful I can enter the IP address just fine. Same goes for netmask, gateway, DNS etc. It seems to be to do with the top row of yellow symbols that appears. This top row of yellow symbol short cuts doesn't appear when typing in the WPA password so the dialog doesn't resize and I can see what I'm doing.

So far though I have to say I'm impressed, the new GB bundle is blazing fast, responsive and the camera works!

Other observations:-

1. I still have sleep of death just like Froyo, the only way to wake the phone is to swipe across roughly the right part of the screen even though its completely blank. I've tried all the pm_sleep settings and this never changes with any build I've tested.

2. I still have the issue with not properly detecting the mobile network as I reported in the FRX05 thread.

3. No problem with Wifi reconnecting after sleep though I think so far which is a big bonus :)

Should I bother trying the GPS?
[Touch Pro, Fuze Android Development] automatic_jack:
Does DIAM100 support hw3d?

Thanks :)
[Touch Pro, Fuze Android Development] davew:
I am not sure but yes I think it does, yes. I tried Neocore some time ago, got something like 20fps.
[Touch Pro, Fuze Android Development] arrrghhh:
If you read the first post, all the directions required to boot are present.

I make NO mention whatsoever of partitioning the card, so I have no idea why you would think that would be required.

Also, why do you want screenshots? Run the build! :p

Don't think stine can test on a DIAM, but RAPH has the same screen. Perhaps it's just the number-based dialogs? Is this the *only* place you've had size issues on the kbd?

If you can get a screenshot of said issue it would help.

Should be running sleep_mode=1. The DIAM still hasn't had any fixes in the way of panel wake/collapse - be patient or submit a patch! Those are basically your choices :p.

Works for me, but I'm CDMA. Other GSM folks having an issue...? Don't think so, perhaps it's your carrier?

GPS doesn't work, I thought I listed that as non-functional, I'll double-check to make sure it is listed non-functional. Any netloc is broken AFAIK.

Edit - Double-checked, it's in the second post :p.
[Touch Pro, Fuze Android Development] pinguinolandia:
:( raph 100

the radio signal is too low and often no signal why?
[Touch Pro, Fuze Android Development] davew:
Seems to be just the IP address dialogs that had the problem. I didn't see it anywhere else while setting things up. It only happens when the keyboard shows an extra top row of yellow symbols above the normal keys.

The sleep mode being set is whatever you guys put in the DIAM100 startup file, as I said I haven't changed anything.

As for submitting a patch, I'm a highly experienced crossplatform C++ developer, but I can't really help you guys as I don't have the necessary domain knowledge or even the right toolchain. Here I'm VC++2008 and XCode all the way. I don't even use Eclipse and I haven't done Java since college over 10 years ago.

However what I will say is that what you have here are actual bonafide priority-1 show-stopping bugs - if the phone screen goes blank when you make a call, and can't wake it up, that's a major issue. If the phone goes to sleep and you can't wake it up, that also is a major issue. If after closing the Wifi connection you can't reopen it, that's a major issue. If the phone can't properly read/write its GSM network settings, then that is a major issue too. All of these issues affect the actual normal basic usage of the phone as an actual phone.

If you guys don't have the hardware to test and develop against, then to be honest you shouldn't be claiming DIAM100 support at all. If you don't claim DIAM100 support, then DIAM100 owners like me cannot complain when things don't work, can they? What hardware do you actually *fully* support? RHOD only?

What really bugs me is that you guys will rush on to implementing more "cool" functionality (get the GPS working, get the camcorder working, get the accelerometer working etc etc) and then by that time there will be a new Android AOSP to play with (Ice Cream) and the show stopping bugs that should have been fixed right at the start will get forgotten about because they're no fun to play with are they?

Sorry if you think I'm being harsh, speaking out of turn, overstepping the mark or whatever. I know you are doing all this in your spare time etc. for the good of the community etc. etc. but to be honest, the *real* fix for these issues is to go to a shop and buy an android phone is it not?
[Touch Pro, Fuze Android Development] arrrghhh:
No phone is fully supported - not even the HD2 has a "complete port" - by complete I mean matching or beating all of the features WinMo offers.

No one is forcing you to run this, and NOBODY has said this is done.

The real problem is everyone is doing this in their free time - so are they going to spend time developing things that they want to develop, or your list of "show-stoppers"....?

The answer is what they want to work on. Truth be told, we support A TON of devices. For one, you're posting in the RAPH section.

Two, I never said it works flawlessly on any phone. The older the phone, usually the worse the support as no one is actively working on this device or that device.

Some devs do have DIAMs and RAPHs, but the majority of the users and devs have RHODs, yes. Again, there's a ton more people with RHODs than any other device.

At the end of the day, don't complain about these bugs - either fix them, deal with them, or get a new Android device. I don't care if you feel they're show-stoppers, no one is forcing you to use this. Stick to WinMo if you really have an issue with it.

You already seem to understand that these show-stopping bugs aren't "fun to play with" - so what do you expect? Unless you have a payroll of devs, you can't tell them what to work on. Welcome to reality buddy - it's rough, you might want to get a helmet.
[Touch Pro, Fuze Android Development] davew:
On the xdandroid front page it refers to this as the Diamond/Raph thread. If you don't support Diamond, you might not want to mention it on the front page. If nobody is working on Diamond (and other devices), again, why mention it?

All I am trying to make you aware of is the fact that in your software basic phone functionality does not work on all the devices you claim to support making it borderline useless. If you put out software that basically doesn't work and encourage people to try it then its you who needs the helmet not me old chap :rolleyes:
[Touch Pro, Fuze Android Development] R^7Z:
I can sense a lot of resentment towards android for some reason. Do you personally have an issue with the OS or are you upset at the threadOP for pointing you in the right direction? :D

I find that using the XDAndroid wiki very useful and the people in the chat even more so. Though it may seem like I am trying to defend this project and/or it's developers, when all is said and done, I like to see if I can help out where ever I can. Even to those who it seems like it is "hopeless"... :)
[Touch Pro, Fuze Android Development] arrrghhh:
We support every phone to the best of our abilities. It's just that our ability to support RHOD is much better than our ability to support DIAM or even RAPH - again, this depends on the particular device - for example, we support the RAPH110 probably better than any other RAPH - especially the 500, as hardly anyone has that device.

So at the end of the day, either you help us improve, you wait for us to improve, or you just sit in the corner quietly. The choice is yours, but pointing out that our phone functionality is poor doesn't do anyone a damned bit of good.
[Touch Pro, Fuze Android Development] davew:
Sorry but that doesn't wash with me. You guys had a choice when you got together and started working on this - you could either keep it as a personal, private project amongst yourselves to give yourself something to do and something to play with in your spare time, or you could put up a website, forum threads, wikis and the whole nine yards and get loads of people interested in your project and invite them to download it, try it and give feedback.

Now since we're here talking here in a public forum about software I downloaded from a public website then its clear that you you chose the latter route.

So tell me what is the point of all these public releases, public forum threads, public wikis, public websites etc. if the only answer you can ever give for any reported problem is "fix it yourself or shut up"?

It seems to me that what we have here is a private pet project that is incidentally being conducted in public :p
[Touch Pro, Fuze Android Development] davew:
No resentment towards Android itself. I'm sure it works fine on devices that it has been properly ported to. I guess at least xdandroid has given me the opportunity to try out the android user interface without first having to plunk down cash for a new phone. But to use xdandroid for anything more than an hour's amusement? there's no point.
[Touch Pro, Fuze Android Development] arrrghhh:
That's what it is meant for! If you think it's a viable replacement for WinMo at this stage - or even ever - you're kidding yourself.

No body said it was complete.

No body is forcing you to run it.

No body said it works perfectly.

No body even said fix it yourself or shutup - I said help us fix it, or shut up :D

I guess the reason we wanted it public was so we could attract more dev attention for help... Which it has done that, we've picked up several new devs by making this project public.

Plus, it works great on my phone - I've never tested it on a DIAM, only RAPH and RHOD. So please, troll somewhere else. I'm done with you clogging up my thread!