yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Yeah I am getting similar so far. I just enabled Wi-Fi, then the phone froze up and get the endless boot animation that I have to pull the battery in order to restart. I'm going to bed, but I will mess with it more tomorrow on my day off from work.

What phone and kernel are you using?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What kernel? I tested wifi on 3.3.3 and .27, both worked great...

Hrm, others too? I wonder if it's an OOM thing. After running a bunch of apps, phone is out of memory and freaks out when you hit wifi? :confused:

It definitely worked great for me, I was using wifi on both kernels to make sure my rootfs changes worked... You guys are using the full bundle yes? I made some rootfs changes...
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Yeah mine is really wigging out now. Using 3.3.3 and the build. Ever since I turned on wi-fi, once I rebooted it gets me to the inital lock screen, but if I touch the screen at all or do anything with it. It boot animations again and then goes back to the lock screen again, and then cycles again and again, don't know how I am going to revert it back. Is there a command in adb to turn off wi-fi?
[Touch Pro2, Tilt 2 Android Development] frostyguy:
I am also having problems with the looping xandroid boot up screen when turning on wifi. RHOD400 .27
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Everyone on the newest rootfs...?
[Touch Pro2, Tilt 2 Android Development] frostyguy:
just replaced the updated system file and rootfs from the latest bundle, kept the data file and everything else
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I started on a new data.img...

Just for sanity sake, try renaming your data.img to data.bak and boot. See if wifi is OK...

I just booted again, and granted I only have a few apps installed - wifi worked flawlessly...
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Damnit all. I was hoping I wouldn't be affected by the wifi thing so I could give you some good news, but....

I downloaded GBX and put 3.3.3 in it before first boot (which caused me similar issues with GBX0B) so I'm going to try a few more things.

(The loop occured with new everything)

The Tests*

1. Kernel 3.3.3 set Pre-First Boot: Loop

2. Kernel .27 First Boot: Success

3. Kernel 3.3.3 set Post-First Boot: Loop

*Assume fresh data.img on all

I'm going to re-test and do some more tests tomorrow.
[Touch Pro2, Tilt 2 Android Development] motisu:
Also here on my Rhod210 running the new GBX0C and 3.3.3. Everything is fine on a completely fresh install with only calibration and startup copied from old andboot directory until I try to turn on Wifi. Then it goes into animation and endless reboot.
[Touch Pro2, Tilt 2 Android Development] detule:
Just tried the 3.3.3 autobuild and wifi works just fine.

I am however on my own root-fs. So either

a) Firmware issue on the new rootfs

b) wifi-nvram.txt issue for you folks starting with clean data.img (if this is the case, you should try booting with 3.2.11, I know I fixed the wifi-nvram.txt creation there don't remember if I did that in 3.3.x)

Either way this could already have been resolved if you folks posted logs.

I'll be out of town this weekend but if it's indeed a kernel issue I can try looking into it next week.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
It was my understanding that we lose logs when it reboots, so I haven't posted logs because I assumed the needed data would be lost since we are having reboot issues and not getting a chance to actually do a GetLogs before it reboots.

Arrrghhh, everything on my build was new, data.img, the whole build you posted, 3.3.3 kernel. I will try the 3.2.11 kernel to see if that is the problem as detule suggests. My issue with looping on reboot is a corrupted data file because of the initial reboot when turning on Wi-Fi. That finally settled enough to finally be able to do a fix_permissions.sh on it through adb. I am going to blow up everything and try again from scratch today.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Would you mind trying my full build when you're back, to make sure I'm not insane?

Reboots to WinMo are difficult - you have to dive into last_kmsg. Reboots back to the bootani should not lose any logging. In fact, if you adb in you should be able to watch the logs as it reboots lol.

So you guys are testing this before installing any apps? Happens immediately? That's crazy, I can't replicate this at all. I'll doublecheck all my files, make sure I'm using what you guys are...
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Found the solution for our wi-fi issues. It is the old wifi-nvram.txt issue. Here is the post on how to fix it. You will need to know your MAC address of your wifi in Windows Mobile and put it into the text file in the post then follow the directions:

http://xdaforums.com/showpost.php?p=9187263&postcount=80
[Touch Pro2, Tilt 2 Android Development] ZoneBlaze:
Quick report:

My Rhodium's Camera app doesn't work..

Well, you devs need any kinda file?

GPS works fine. Able to get my location.

Wifi works.

Just that camera :(

Using Rhod100 settings...
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
I can also comfirm that it is the wifi-nvram.txt issue. Booted with .27, nabbed the txt file then wiped it and did a first boot with 3.3.3. Placed the txt file and everything is...

By jdog2pt0 at 2012-04-27

Also, that OL file explorer or w/e it is does not install automatically (I use ES anyways). I've also had issues with dev tools not working. Specifically terminal emulator. It FC's. Not a big deal, but I can pull logs if you want to look at them.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Terminal Emulator in Developer Tools has FC on me always. It has never worked in any build. I just download the one on the Market and use that one.

I will say the wi-fi is very slow, but so is my EVDO right now. Trying to download stuff from Google Play is slower than I have ever seen it even using this build. The only thing I corrected was the wifi-nvram.txt thing. I will keep playing with it. Maybe it just needs a reboot to speed things up.
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Same.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
I keep on getting a notification saying "Geolocation Problem: Location does not exist"
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Try this thread

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

May be of some help.
[Touch Pro2, Tilt 2 Android Development] x12CHRIS18x:
Thanks I fixed it
[Touch Pro2, Tilt 2 Android Development] motisu:
I am glad to hear that this solves the problem, but I think that I will wait until detule fixes it in the build. I don't want to put in a patch that is MAC specific, as this will prevent me from copying the installation to other devices. Meanwhile, I took his advice and went back to 3.2.11 temporarily.
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
Just did a fresh install (HP-tool format).

Stock GBXC build from first post but with 3.3.3 kernel from the autobuild. Rhod400

Had the Wi-Fi issue others experienced. Posted solution (wifi-nvram.txt) resolves the issue. No problem with most current YouTube app from PlayStore.

So far working fantastic (other than the known wi-fi issue). Will report back after gathering some more usage.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
You don't have to patch if you do the following:

Boot the build as is with .27 kernel in it. The wifi-nvram.txt file gets generated in the .27 kernel but in a different location then it needs to be. So if you want to use the other kernels all you have to do is move it to correct folder which is the /data folder. I think it gets put out of that folder with the .27 kernel in just the root folder in android. It just has to be moved into /data folder. The .27 kernel puts the proper MAC address in the file when you boot it up the first time. It is just the other kernels that aren't patched yet. At least that is my understanding. Someone correct me if I am wrong.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well that makes sense why I never had the issue. I always started on .27, then flipped kernels... I flipped back and forth a few times, but I don't think I ever started on 3.3.3 w/a clean data.img.
[Touch Pro2, Tilt 2 Android Development] agibby5:
I'm using the new bundle GBX0C and kernel 3.1.10. I recently converted from FRX and started with a new data.img.

My issues:

- I am unable to send an MMS (I'm on sprint). It just says sending forever and it seems like it drains the battery quicker.

- Sometimes the phone freezes when using Reboot or Power off options.

Other than that, everything seems to be working very, very well. I'm liking it a lot better than FRX where I couldn't get the camera to work. I also had camera problems on .27 and when I jumped to 3.1, presto! It works now!
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Here are the CSV files from my Rhod100.

Thanks for the build, I'm installing it now...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
3.3.3 is the newest kernel FYI.

For MMS, did you setup an APN?
[Touch Pro2, Tilt 2 Android Development] jonners59:
I think you may have a point stickdaddy96

I have noticed that when my babe is playing up and falling back in to the XDANDROID animation and just can't get network, that I am also not getting the "x app has just been granted super user privileges" messages. Maybe there is just too much going on. So maybe you have something there?

Anyone any ideas on my CoPilot causing freezing of the device after c 30 minutes. Only way is to restart by pulling the battery out.

I'm still on the build from the original first thread.
[Touch Pro2, Tilt 2 Android Development] ObviousMan:
Sprint CDMA TP2:

I've upgraded to GBX0C from 0B 1.5 days ago. 3.3.3 kernel (4/25 version from autobuild). Did not update data.img. So far it has been stable, internal audio is as good as was on 0B (which is alot better than FRX), and finally BT works. During one of the calls it did not route the audio to BT - the phone was asleep (I presume - it was not touched for near 2 hours), a call came in, I tried to answer from BT, but it did not result in picked up call, it rolled into VM. I called VM after that and BT was routed fine. I wonder if there is an issue with the phone reacting to BT while asleep. I will report further if the issue persists.

Same WiFi issue as reported fixed with the posted solution. Was able to mount network share, etc. w/ ES file explorer.

Youtube - the latest version works fine.

I have not see noticeably better GPS performance, but I just did 2 lock tests near my house, and it locks about as fast as it did on FRX. I have not tried GPS with 0B.
[Touch Pro2, Tilt 2 Android Development] eik:
I installed GBX0C. Initially it all looked fine, but after some time it seems the display is dark; almost impossible to read at daytime. Changing the display settings (auto brightness, using the brightness slider) does not seem to change anything. Nor does using the mentioned widget.

Any ideas if I am overlooking something?

I uploaded logs in http://pastebin.com/4G4XKcnV
[Touch Pro2, Tilt 2 Android Development] frostyguy:
Once I turn on wifi, android reboots in loops, going to try the wifi fix, thanks arrrghhh
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
On the build from the original first thread...? So that means you're not on GBX0C, you're on 0B...? I'm confused.

You should definitely upgrade, as there's a lot of GPS related fixes in the newest build. GPS used to freeze up on me after extended usage, but now it's fine. Might want to try other apps too, like Google Nav - just to rule out that CoPilot app you're using.

You also appear to be on a slightly older build, but I don't think that's critical - this issue is usually kernel related. Does it happen on .27? 3.3.3?

Yea, it seems if you start straight away on the newest 3.3.3 kernel, wifi will not work properly...

I was always starting on .27, so it never failed for me :p.
[Touch Pro2, Tilt 2 Android Development] frostyguy:
I'm actually only been using .27, which is bundled in GBX0C right? How do I get on kernel 3.3.3? You just need to replace the zImage and modules files right? Was never able to get the other kernels to work. It would always get stuck before you can get to the xandroid boot up screen.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Are you using everything from the first post? You're not reusing anything from another build/bundle? (Except for maybe ts-calibration...)

Also, silly question - but you're using a RHOD yes? Which one?

Did you have to do the wifi-nvram trick before? That's a necessary a step for some regardless.
[Touch Pro2, Tilt 2 Android Development] thegof:
I have the same problem trying the other kernels. I've got a system which is running well with .27. To try a new kernel I copy (and overright the zImage file in the \andbootgbx0c directory, then try to start HaRET.exe. No go, it hangs after about a screenfull of text boot strings (never gets to the startup animation). I've tried this on 3.3, 3.2, and 3.1. I must be doing something wrong. Sprint TP2 in case it matters...
[Touch Pro2, Tilt 2 Android Development] frostyguy:
Yeah, I'm using everything from the GBX0C bundle, plus got all the .csv files too. I'm on RHOD400. .27 works perfectly but all the other kernels just get stuck before the boot up screen
[Touch Pro2, Tilt 2 Android Development] jonners59:
Yes, plan too. Just have not had the time since it came out. Good to know about the GPS stuff. I do also have the various Google nav apps, and it does not happen on any of those, so it may well be CoPilot related. See if the new build fixes it.

I have had a suspicion for some time now that SOMETIMES the phone does not ring when I get a caller. Today I was able to confirm this, with missed calls when I was standing next to it. It is not always, but intermittent. I'll keep an eye and try a log if I am in a position to. Wonder if anyone else has had this issue?
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
I've been running this build now for about half a day.

Wifi: No problems

Calling: On Froyo I sometimes had the problem I couldn't hear the other person. So far this hasn't occured on GBX0C.

Camera: I can confirm the rhod100 camera patch isn't included in the bundled .27 kernel :(

Sleep&Wake: No problems spotted, device always wakes fast

Overall smoothness: Sometimes it runs faster than Froyo, but most of the times it's just as laggy as froyo was...

Perhaps things like speed are fixed in newer kernels?
[Touch Pro2, Tilt 2 Android Development] detule:
You should try 3.3 and see if camera at least is working for you. Some time ago I added some version of brinka's camera patch, never got any feedback if it made a difference for RHOD1xx folks.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
I also had this problem with a rhod 300. It would stop with a kernel exit in the text. I reinstalled everything including a new data.img and let it all settle in. I set up an account in gmail, WiFi and a couple minor things like screen brightness. Then I rebooted to the same setup and let it settle in again. After another reboot, I changed the kernel to 3.3.3 and it booted and worked fine. It might need the reboots to establish a solid file system in .27 first.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So you guys both replace the kernel like you normally would (& modules if you want wifi) and are SURE everything is from the GBX0C bundle? I had to do a few tweaks that you might not expect to get the new kernels to boot - one was a different HaRET, another was a offset in the startup.txt and the final is semi-trivial, and that's the wifi firmware swap in the rootfs. So when I say you need to be running everything from the GBX0C bundle and don't reuse anything, I mean it ;).

Assuming all of those things are in line, I don't know off the top of my head what else would prevent newer kernels from booting if .27 boots - unless you guys are simply not replacing the kernels correctly. Perhaps re-read Incremental Updates to make doubly sure you're replacing the kernel properly.
[Touch Pro2, Tilt 2 Android Development] eik:
Bingo. I tried 3.3 and 3.2.11; both having the issue. You are right, brightness settings work fine if I take the .27 so it is a kernel issue for sure. Which makes this off topic now. Off to another thread ;)
[Touch Pro2, Tilt 2 Android Development] numero9:
I rolled everything back after a format of the SD using GBX0C and just the stuff provided -- no kernel upgrades, etc.

I'm trying to restore from Titanium and just about every 2-3 programs install and then it reboots itself. I know that has happened to me when I update apps before, but it's never been like this when just restoring. It's taking me nearly 2 days now just to restore everything from Titanium because Android keeps restarting itself. Any ideas on what I can do?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Make sure you don't have anything else running when restoring. Also OOM settings/groupings might help (see the V6 supercharger script).
[Touch Pro2, Tilt 2 Android Development] thegof:
:D Seems in my move to GBX0C, I copied and updated the startup.txt file, but neglected the offset line. It's now working with the newer kernels. Had a brief issue with it not responding to the sprint keyboard (or even the hardware keys), but a boot into 3.2 and then back to 3.3 seems to have cured that (not exactly sure why though :confused: )

Looks good. I'm getting the "Geolocation Problem" that everyone else is reporting but it's not a huge deal (yet, it's definitely the Beautiful Widgets app as I can have maps up). I'm also having issues recreating one IMAP email account. I'm getting an error in creating the account ("550 HELO is an IP address" when trying to verify the server in the email client). I just restored the email data from a Ti Backup and all is good (but I'm curious about the error if anyone knows).

Does anyone else seem to get corrupted text in Google Maps? It sometimes clears if I shift (drag) the view a bit, but often it renders the street names unreadable. Also on GPS, I know you mentioned that you added the GPS injection code to the release, but is that something that is automatic or is there something we need to do periodically ala the old GPS download/inject on the WM6.5 side?

One last item. I was hoping the Square device (CC reader) would work. But alas it doesn't seem to. Perhaps it's just my unit? It uses the 3.5mm jack (on my Sprint TP2). Anyone have any trick to getting it to work?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No explanation, I'm betting a simple reboot would've fixed it too. Who knows...

I've never used this widget/app - so you can get a coarse (netloc) in Google Maps, but it doesn't work on Beautiful Widgets? Strange. The issue with netloc should be fixed - I was signing the apk thru a script, and I should not have been... That was the issue with the 0B build in regards to netloc.

I'm assuming you're setting it up the same way? Who is the provider? What are you putting in for the settings? Need details...

Yup, I think Google Maps is dead for these old devices. Hero/G1 guys seem to have the same issue. AFAIK the only solution is downgrade... look here, I think 5.8 is the last one that works reliably.

Only if it's taking a while for a lock. I noticed the app GPS Status automatically downloads this data.

I've also included tytung's GPS Injector app, see the changelog ;).

lol, I have no clue how a CC reader could possibly interface with a phone using the headphone jack. I guess this is a "generic" Android CC reader? Perhaps provide some logs. I have never even heard of such a thing, let alone used one.

Edit - wow, just read about it. An engineer responded to this post, kinda interesting:

http://www.quora.com/How-does-the-Square-card-reader-work

Anyhoo, I wonder if we even initiate the mic properly. First of all, it could be a hardware issue - does the strip it's using for the mic line up with the RHOD's plug? Assuming that's a yes, do we route mic audio properly when you're processing these transactions? I'd be really curious to see logs from this.
[Touch Pro2, Tilt 2 Android Development] frostyguy:
This might be the same problem I'm experiencing, kept my old startup.txt file from previous builds. What do I set the offset line to? Is it this initrd_offset 0x00a00000? Never really tweaked with the system.txt file only when I added overclocking. Thanks in advance.
[Touch Pro2, Tilt 2 Android Development] thegof:
You got it. Look in the startups folder of the install set to see the examples for each phone. Note, you'll have to add a CRLF to the line since the lines are not split correctly, at least they were not on the RHOD400. Arrrghhh, you might want to add that to your list of fixes for the 0D release :)
[Touch Pro2, Tilt 2 Android Development] frostyguy:
I'm sorry, but can you give me an example of how yours is setup, like copy paste. Thanks again.
[Touch Pro2, Tilt 2 Android Development] jonners59:
Installed the new files from Thread #1. The only items I kept were my data.img and Startup (checked these and they looked the same bar install location). Not sure if that is good or bad ?

Booted up fine, but I have run in to problems:

It reboots shortly after it has booted, even when booting in flight mode and turning flight mode off after it has settled down.

Also, and more problematic is that Superuser is nor working, this means that many other apps and utilities do not work, such as, BatteryCal, Getlogs, SManager, SU Update Manager, Timezone fixTitanium, Busybox install, and more....​

Amendment to quoted text: Iwent into Googlestore and uninstalled SUperuser. AT the point where it asked if I wanted to remove all settings I said OK, when it finished SUperuser was still installed, so I selected open. It was "emptied" of all my settings. I tried each app and it gave Superuser access - this is now SORTED!:)

My Alarms did not work this AM either.

I'm going to monitor it today and see if it settles down.
[Touch Pro2, Tilt 2 Android Development] Stijnjits:
Wow! Thanks! The 3.3 kernel is a serious speed improvement! Also the camera works perfect!
[Touch Pro2, Tilt 2 Android Development] detule:
If this is something you can reproduce next time after such a reboot:

# cat /proc/last_kmsg > /sdcard/last_kmsg.txt

and pastebin the content of /sdcard/last_kmsg.txt here.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, no you certainly don't have to add those. Either use a real text editor (Notepad++...), or use Linux ;). Both of which will show the files just fine!

set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400"
boot

Or just use the provided startup.txt... yeesh.

I have a feeling he's just dropping back to the bootani... jonners will have to confirm, but I don't think it's a full reboot to WinMo. Right?
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
Just want to sing some praise here. Tethering worked great, gps worked great, and so far I got 36+ hours of battery life out of it (not sure if kernel, fluke or what). I have no OC in place and it's running real smooth.
[Touch Pro2, Tilt 2 Android Development] walter79:
Which kernel you use?
[Touch Pro2, Tilt 2 Android Development] JDog2pt0:
3.3.3
[Touch Pro2, Tilt 2 Android Development] frostyguy:
Do I still need to add acpuclock-arm11.oc_freq_khz to Overclock? because I think that was holding me back from booting it up in my other system.txt
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, if you want to overclock you must use those commands. Remember, .27 and .39+ have different OC statements.

I can guarantee that wasn't preventing you from booting, unless of course you were trying to overclock to some ridiculous number :p.
[Touch Pro2, Tilt 2 Android Development] frostyguy:
I left out the arm11 part, but was able to get the latest kernel 3.3.4 to boot up finally. My latest problem is that I can't get Terminal Emulator to work so that I can fix my wifi.