yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] scooper:
Are you serious it's in there? I swear I did read and there was no mentioning of it. Also searched within that FAQ. That was why I went to check the FAQ at Project Android website.

Yeah, I just remember it was the network adapter on my brother's machine that had the problem with the latest driver before it got discontinued. Just couldn't get it to identify the network so no internet when I use anything other than WEP protocol.

But there's a workaround since I can use guest access to get wifi at home. So it's all good.

Thanks for your help. :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well this is frustrating... I know I wrote a piece on WEP in the RHOD-specific section, but it's gone.

Basically there's two methods. One is in theory easier - use an app called 'wifi-ace' (on the Market) that allows you to mess with all sorts of advanced settings and makes WEP and hidden networks function.

The other method is outlined in this thread.

Now to go 'fix' the wiki ugh...
[Touch Pro2, Tilt 2 Android Development] scooper:
You're awesome! It worked. Thanks alot! :D
[Touch Pro2, Tilt 2 Android Development] falzon03:
alright so my posts keep getting skipped but is anyone else having internet issues?....after some time my data disconnects and only way to reconnect is reboot into android
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You can try cycling data or the cell radio itself.

Haven't really given us any info to go off of. I do notice that my data cxn will randomly hang... No solution yet. Rebooting is sure-fire...
[Touch Pro2, Tilt 2 Android Development] codedesignr:
I lose data all the time on my Rhod400! I've tried deleting data.img, reformatting SD, cycling airplane mode/data on/off. No luck! Sometimes it will come back later in the day though without a reboot. Also, it always works initially after booting, just seem to lose it at some point which sometimes happens in the middle of using an app. Seems to be a gingerbread problem, as this didn't happen when I was using Froyo. I don't believe it's a kernel issue as the problems existed using WisTilt's testing Kernels and the current 1260, (1262 just came out today). Is there a log file from my phone that might be useful in diagnosing the problem?
[Touch Pro2, Tilt 2 Android Development] falzon03:
yeah i posted earlier that i had sprint tp2 stock rom....after a decent ammount of time ijust loose data and the only way to get back is a reboot, airplane mode also freezes and sticks
[Touch Pro2, Tilt 2 Android Development] poleshuka:
it failed to boot, stuck in black screen. I started with fresh data.img, but I could use adb, so see log in zip, if you need something another feel free to use my Black:)
[Touch Pro2, Tilt 2 Android Development] manekineko:
I've never tried with airplane mode before, but if I go into settings, and disable and reenable data from there, that has always fixed the issue for me with no crashes.

Also on a Sprint TP2.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nothing stands out (but I'm far from a log guru...) Does this kernel (1253) boot other versions of Android for you? Is this the only version that's unbootable for you?
[Touch Pro2, Tilt 2 Android Development] poleshuka:
I use kernel supplied in zip, I boot OK on Blackstone FRX04,RED & Huawei
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well to be fair this is posted in the TP2 section, although there really isn't anything in here that should prevent a Blackstone from booting.

Can you boot this image with any kernel? Have you tried any different rootfs'? Is it at least creating a data.img?
[Touch Pro2, Tilt 2 Android Development] codedesignr:
New RootFS

There's a new RootFS with Gingerbread specific comments. Notes from stinebd include "gingerbread: Decouple libs from rootfs, use versions provided in

/system." Does anyone know what this will help with for Gingerbread users?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Just cleanup, doesn't really provide any immediate benefit.

Edit - just confirmed with stinebd, we were using /lib/froyo in the gingerbread build. Now all the libs are in the system image.
[Touch Pro2, Tilt 2 Android Development] vansem12:
DIAM 100 : Dark screen with this rootfs-20110224-3dd92b8.zip and data broken apparently.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Try the rootfs I've included in the build. Why is a DIAM user posting here? lol.
[Touch Pro2, Tilt 2 Android Development] scooper:
arrrghhh,

Can you point me to the right wpa_supplicant.conf file with the passwords in it please? I have found a few but they were all the same, giving examples only.

My sd card is messed up again. A few times already. This time still works somewhat. I want to get the file so I don't need to set up everytime.

Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You have to have your own with your password in it... you can save your own once you've got it where it works...
[Touch Pro2, Tilt 2 Android Development] scooper:
there has to be a file where all the networks and their passwords are stored right? it doesn't matter if it's encrypted, as long as I can back up and restore and it works.
[Touch Pro2, Tilt 2 Android Development] stinebd:
wpa_supplicant is for wifi. We don't have a national database of people's wifi ssid's and keys.

...Although Google did do all that wardriving for a while there. ;)

EDIT: I think I see what you're asking for now. /data/misc/wifi/wpa_supplicant.conf is where it's located on your device.
[Touch Pro2, Tilt 2 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 Pro2, Tilt 2 Android Development] jookdakang23:
it was very buggy at first, but its now straightening out. still not as smooth as the default one. i did a clean format and everything

Edit: Too unstable. The keyboard lags when u open it, theres a lot of lag while scrollin through pages. i liked it because it had the 3d gallery. idk what causes it to be buggy, but im going to try a format and do it again ;)
[Touch Pro2, Tilt 2 Android Development] scooper:
Ah, I tried two different file explorers and both showed empty data folder before so I gave up on that. Read your post and went online to research for some app that can read it. Just installed Root Explorer and it worked.

Thanks alot.
[Touch Pro2, Tilt 2 Android Development] matt205:
I'm having the same issue, used the HP format tool on a new SD card (SanDisk).

Any other thoughts on this one?

As an aside I'm located in Australia on the Telstra network, is this build only designed to work on a specific band or network?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Did you follow all the steps in the first post? There's a caveat on the calibration...
[Touch Pro2, Tilt 2 Android Development] matt205:
Yes, followed to the letter, just re-formatted the card with the HP tool and tried the procedure again with same result. I notice at 1 point during the boot it cpmplains about not being able to mount the SD card, I assume this is normal as my "other" working Android SD port displayes the same message but boots regardless.

I've tries all the startup.txt's, I'm nbot fully sure which model Rhodium I have here, I'm assuming it's a 100 or 210.

I'm going to try anothe SD card when I get home. I'll report back then.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Waiting for SD is probably related to the clocks issue. Update to the newest kernel.
[Touch Pro2, Tilt 2 Android Development] zooster:
I confirm that this new system image is not as smooth and fast as the first one...
[Touch Pro2, Tilt 2 Android Development] shatred:
working on my rhod100_nl but its pretty slow, gonna stick with tiad8's blazn 2.2.1 from 23-02 for now.
[Touch Pro2, Tilt 2 Android Development] stinebd:
To everybody experiencing horrible speed in general, upgrade your rootfs to the latest one from 20110224.

The only situation this one should be graphically slow in is when typing on the soft keyboard and using the popups that darken the background. That is something I've already pushed a fix for and it'll be in the next system image.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh. Looks like I need to make a new bundle pack... Hopefully I'll find some time to do that tonight ;).
[Touch Pro2, Tilt 2 Android Development] stinebd:
If you want to do that, I can roll a new system image with the aforementioned fix.

But shouldn't you be on vacation?
[Touch Pro2, Tilt 2 Android Development] shatred:
he is haha, btw. just tried it again, and i noticed that GB uses allot of ram memory?

in frx04 i had right after booting about 100-105mb free ram, with your GB i cant seem to get higher them 75-80mb

i used the latest gb build from here http://files.xdandroid.com/
[Touch Pro2, Tilt 2 Android Development] Eodun:
Android doesn't manage RAM as WM, while AND tries to allocate all memory it can and then manage at wish, WM needs to allocate it every time an app asks for it.

So don't worry about free ram in android, it has no meaning. Also, apps that kill running processes marked as "sleeping" can induce weird behaviours in last Android versions.
[Touch Pro2, Tilt 2 Android Development] shatred:
in frx04 when i had 50mb free my device was way slower then when i had 100mb free, how is that possible then?

EDIT*

when i try to download something in the market i get an force close from google services framework (proces com.google.process.gapps)

i am using latest Gingerbread (not from the first post but from stine his repo) with the latest test kernel from wistilt2 (uploaded by arrrghhh) and the latest rootfs from f22
[Touch Pro2, Tilt 2 Android Development] rpierce99:
You should be using the rootfs from the autobuild service for the gingerbread releasees http://files.xdandroid.com/rootfs/rootfs-20110224-3dd92b8.zip
[Touch Pro2, Tilt 2 Android Development] shatred:
that one has an real weird keyboard layout and not working for me because allot of buttons are not correctly assigned. the newest f22 works fine.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
F22s rootfs does not include the libs location change that is in the autobuild version because it breaks froyo, so pick your poison I guess :)
[Touch Pro2, Tilt 2 Android Development] Eodun:
I'd guess that's because there's an specific active app consuming processor power, not because of the ram. I'm not a dev though, so don't take my words as completly trustworthy ;)
[Touch Pro2, Tilt 2 Android Development] stinebd:
What? The change I made was in the gingerbread section of the init script. That shouldn't have affected froyo.
[Touch Pro2, Tilt 2 Android Development] rpierce99:
You would know better than I, maybe F22s does include the change then. I could have sworn when I was in IRC the other day we had people who couldn't use the newest version, thinking back now maybe they were using the original GB build. I stand corrected.
[Touch Pro2, Tilt 2 Android Development] F22:
I could have sworn Arrrghhh said it was busted too. That's why I didn't merge stinebd's last commit into my local tree before building my rootfs earlier today. Looking at stinebd's actual commit however, it looks like it only affects Gingerbread. So I'm a bit confused regarding that discussion too. I'm out of time however for the moment. I'll build a new rootfs for Gingerbread with my mods as soon as I get back later this evening.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
There were some people complaining about no data and no bootani on the newest rootfs. I didn't trace it down myself TBH...
[Touch Pro2, Tilt 2 Android Development] matt205:
Yep, that did it!

Now just need to get a proper keyboard map, my@ doesn't work, kind of an important one!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What phone? phys_keyboard set correctly?
[Touch Pro2, Tilt 2 Android Development] F22:
If you got your phone from Telstra it's probably a 110. You can check this by removing your battery and looking at what's written on your phone underneath. You'll probably see rhod110.

100's are European, and the 210 is US T-Mobile.

On my rootfs you can use physkeyboard=rhod110 on set cmdline in startup.txt. If you're using the stock rootfs, then you should use physkeyboard=rhod100_uk.
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
Ill throw my bug that I have found onto here:

Voicemail - Happens every time you attempt to call voicemail. Will just sit there and dial, and you will never end up with a dialtone. On top of this, you cannot end the call, because it will then just sit there with the hanging up logo. Attempting to call/receive calls also fails from this point on. Only way to get out of the loop is to soft reset.

Only other bug I found was the accelerometer, but that was already stated.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Never end up with a dialtone? I don't think you should ever hear a dialtone on a cell phone...

Also, this doesn't happen to me. Try a fresh data.img, don't think that's the issue tho, just something to try. I'm also on a different carrier... perhaps its your carrier?
[Touch Pro2, Tilt 2 Android Development] manekineko:
Just saw the new embiggened landscape Gingerbread keyboard for the first time today. It's kinda ridic. :D

I don't really care about this issue since I never use it, but to be a good alpha tester and provide feedback, it's probably a problem that the software keyboard is taking up ~80% of the screen, which the actual app stuck in the last 20% or so. On apps with software buttons, like Notepad (which has a confirm or cancel button on the bottom), the text area gets completely hidden, and all you see are the confirm and cancel buttons and this gigantic soft keyboard, such that you can't see what you're typing.

Also, incidentally trying to pull up the soft keyboard has been causing some app crashes for me, but I haven't figured out how to reproduce the problem yet. First the keyboard will crash, then the app that was using the keyboard will freeze, though the cursor will continue to blink. Even if you switch to hardware keyboard, it won't take the inputs. Then you'll be given the option to wait or force close the app. If you wait, it doesn't get better. If you force close and reopen, then everything is back to normal. Happened twice to me now, once to Fancy Widget when I was editing my location, and once to the browser.
[Touch Pro2, Tilt 2 Android Development] QuentinX5:
Silly Quentin, I meant it will never begin ringing. But ill try a fresh data.img and see where it gets me, just thought I'd put that bug out there.
[Touch Pro2, Tilt 2 Android Development] stinebd:
The size issue is known. I have to adjust it still (in both layouts) and when it's proper, the keyboard will switch to fullscreen mode when in landscape (so it focuses and expands the active text field to fill up whatever space isn't used by the keyboard).

I haven't seen any crashing yet at all, so if you expect anything to be done about that, you better submit a logcat. ;)

I've seen some strange keyboard issues even on stock gingerbread on my n1 (like the wrong keyboard variants randomly show up during focus changes) so some issues might end up fixed by an upstream merge at some point.
[Touch Pro2, Tilt 2 Android Development] matt205:
Only bug I seem to have so far is getting the handset to come out of sleep mode, sometimes it just doesn't respond to the power key or the home key at all, even when the phone is ringing I can't always get it to wake to answer.
[Touch Pro2, Tilt 2 Android Development] Entropy512:
That's an ongoing and known power management issue, it affects Froyo builds too.

WisTilt2 has been working the issue and has been providing tweaked 2.6.27 kernels for Froyo users to test - the changes will eventually be ported to the Gingerbread 2.6.3x kernel once a solution is identified. (It hasn't yet...)
[Touch Pro2, Tilt 2 Android Development] manekineko:
Actually, Gingerbread is using the same kernel as Froyo and everyone else. There's been work on a .3x kernel, but nothing released to the public yet.

Incidentally, WisTilt2's kernels work great with this Gingerbread build.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Indeed.

Plus, to make it more confusing the lionshare of the devs are working on .35 and Cotulla is working on .32.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Wow, the man himself here in the thread!

Not sure if you ever heard about this issue that was originally reported by someone on PPCGeeks, but just in case I'll highlight it to your attention. If you make or receive a call on GBX, after your call ends, the data connection will show as reconnected but will be in a dead state where it doesn't work. I've confirmed that this issue wasn't present on FRX.

This problem can also be created by toggling Airplane Mode on and off.

Interestingly, however, this problem is not created by toggling Settings => Wireless & networks => Mobile networks => Data enabled off and on.
[Touch Pro2, Tilt 2 Android Development] manekineko:
While typing up the previous post, I got hit by the keyboard bug. Turns out that it sometimes can affect the hardware keyboard and not just the software keyboard, since that's how it happened this time.

Here is the logcat, in relevant part.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Interesting, I didn't think it would be a userland issue but it appears to be...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I really wish you wouldn't just randomly spam every thread with this link... Kinda rude if you ask me, especially since you created another thread...
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Does this bundle include the newer testing image from 2/26?

Any update on GB progress? Love this bundle, thanks
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well there was the g-sensor & gapps fix, but I haven't made a new bundle for that yet. Waiting for other things to be supported.

My bundles will never come with any testing images, only autobuild. If you wish to test, that's in a separate thread - for good reason ;).
[Touch Pro2, Tilt 2 Android Development] jookdakang23:
is there a way to get camera on gingerbread?
[Touch Pro2, Tilt 2 Android Development] stinebd:
That's strange. The line numbers in the backtrace don't match the actual location of the referenced code at all.

The backtrace indicates the crash is run call in KeyboardSwitcher.java's runnable class is handing off to InputMethodService at line 484, but that code is actually at line 552 in the AOSP tree.

I'll have to find a way to reproduce this, anyway.
[Touch Pro2, Tilt 2 Android Development] tiad8:
Hi guys

Good news

I got camera fully working on this build. I did not touch anything else. I left the system.ext2 the same. I just add it camera support.

I only test it on my rhod400. But it should work for all the devices.

What works

Gmail

Camera

And everything else that was working before.

All credit goes to stinebd for this

I will upload it today after work.

Thanks

sprint htc touch pro 2 (rhod400)
[Touch Pro2, Tilt 2 Android Development] vnes1984:
Awesome! Can't wait to try it out.

I love GB. Thanks Stinedb for your work on this. I look forward to a new release.
[Touch Pro2, Tilt 2 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 Pro2, Tilt 2 Android Development] arrrghhh:
Thanks man! New gb bundle on the way as well.

Edit - new bundle up. Enjoy!
[Touch Pro2, Tilt 2 Android Development] manekineko:
Works amazingly well so far. The best Android build out there for our phones just got better.

Overlay dialogs are much, much faster and smoother now.

Camera works great, and Google Goggles works without needing any manual changes to the configuration.

Love the new dialer, though the Hold button is a bit mysterious. Is it supposed to be there on CDMA phones? I don't think CDMA supports hold and it does nothing on my phone as far as I can tell.

Software keyboard seems to be working much better now.

I think ever since the gsensor support was added, and apps started auto-rotating, it's actually a little too sensitive to rotation. Seems to always want to rotate my screen 90 degrees counter clockwise when I set it down flat, and in general there's just a lot of rotations being triggered when I'm not actually trying to rotate the phone.
[Touch Pro2, Tilt 2 Android Development] EazyVG:
So in this build GPS, Google apps and all that in Froyo works is working ... I mean with the latest update? Also can I use the latest F22's latest rootfs file and latest wistilt2-kernel-pack with this build? Thanks.

Time to switch to Gingerbread build? :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
GPS is not working, that was not one of the things listed as fixed in the changelog...

I think everything else that is working in Froyo works in this tho...

There is still that data bug, but it seems to only effect CDMA devices. If you make a call or go into airplane mode, data won't work afterwards unless you also cycle data manually.
[Touch Pro2, Tilt 2 Android Development] EazyVG:
Thank you for the quick reply. Unfortunately GPS is a big thing for me. So guess will wait for newer builds with GPS working. Thanks anyways for your work on this.
[Touch Pro2, Tilt 2 Android Development] manekineko:
Yep, this build is great, faster than any of the Froyo builds, with the latest features from Google.

Though it's not just GPS, all types of location are not working yet, meaning tower triangulation and wifi.

Also, this probably affects very few users out there, but for users running FRX/GBX on properly partitioned systems, GBX doesn't seem to have any support for USB mass storage yet, whereas FRX is at least somewhat working.

Oddly enough also, the Neocore issues remain, where the graphics don't show, but I don't see any problems in any actual games, or in Quadrant's 3D tests, and in OpenGL Showcase (which tests OpenGL support) all the tests run the same as in FRX.