yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Imma leave this here.

I don't know if I got it in time, but I had audio die in fantastic ways. There's a bunch of other apps crashing and going slow, so I hope the logs aren't too stuffed full of poo.

http://pastebin.com/4MrLmrPS

Basically I got a call, it rang... but took too long to display the phone UI to answer. So I call the number back - it connects, but no audio. Absolutely nothing. So I flip speakerphone on, still nothing. So then the person texts me with what they wanted to say via the call, and I hear it vibrate, and I also hear the speaker open in an attempt to play the notification. It doesn't actually play, and the speaker gets 'stuck' on - all I hear is feedback and static, while there was nothing going on in the phone.

Between not having getlogs installed and all the apps crashing, I fear this log is useless. Not sure how to recreate such horror, I assume it was just the uptime? I had one other user say audio dies, but I don't know if they pulled logs.

This has always been an issue with acoustic, I just hadn't experienced it on HaRET in a while. If anyone else has similar experiences, please pull logs as quickly as you can. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh. Thanks for the logs - I'm no expert either, but I'm hoping the developers can find some gem in there. It seems there's still stability issues, so obviously those come first.

Maps is an issue on this build for sure. Downgrade it to 5.x and I hear it works fine. There's just a lot of artifacts on the screen, mainly after moving around.

Not sure about video cam, but that "should" work. Logs, but again that's an enhancement kind of thing ;). Oh, and TV out won't work. We're still trying to nail down stability :p.
[Touch Pro2, Tilt 2 Android Development] SgtMac02:
I did have a similar, but not as fantastic an issue earlier today as well. Had a call come in and heard nothing at all. Tried placing a call and had no audio. This was shortly after having been messing around with the bluetooth a2dp stuff from earlier in this thread, so I have no idea if it might be related. I assumed it was at the time. I had to reboot and it started working fine again. My battery is dead now (see previous comments about battery life) but I'll see if the log goes back far enough, and post it. If not, I'll definitely post if it happens again.
[Touch Pro2, Tilt 2 Android Development] ryannathans:
A few issues, otherwise, looks good!

I'm on the included .27 acoustic kernel.

1. Google Maps. FIXED

On FRX07.1 using NO GPS and relying on Wifi and GSM only, I

can

get a position in my house accurate to 60M.

On GBX0B using NO GPS and relying on Wifi and GSM only, I

can't

get a position at all - anywhere. (Error message is "Your current location is temporarily unavailible")

GPS does take a little while to lock but works fine and I can get a location down to a meter accuracy.

Would logs be useful here?

2. Wifi

Sometimes when trying to enable it, I get "Error" but after maybe 5 attempts of trying to enable it, it finally works and enables, once enabled, works fine (from what I can tell).

Audio works awesomely (music via ext->3.5mm), as does GPS sleep, only issue I have had with GPS is once I disabled GPS and the 'LOCKED' icon never disappeared and I needed to reboot.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Unfortunately since you rebooted the juicy stuff is probably gone. Need to pull logs as soon as it happened. I fear the act of having to install GetLogs actually made my logcat scroll off the buffer, so my logs might be useless as well....

I'm pretty sure it works fine here, but I've always had both enabled. I recall it getting the fuzzy loc, then quickly getting a GPS lock...

I thought this too, but honestly waiting just a minute or two (I didn't time it, just be patient damnit) and it eventually disappeared. Just put it to sleep and check it in 5-10. If it seriously doesn't go out, that's odd because mine did (using Google Maps).
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
OK, I finally got around to building and signing a new image. All went fairly well - sorted out the NetLoc problem (thanks detule), and along with a lot of patches and fixes from detule as well, we have ourselves a great build!

I'm having a few troubles before I release, and want to make sure I iron everything out before I do...

So first, XTRA is now working out of the box. I got a GPS lock within a few seconds in my basement... so yea. Wow. NetLoc again is also working. There's some acoustic fixes, along with the Sprint MMS fix. Finally, the camcorder should be fixed. Now I still don't think the RHOD100 cam patches have made it to the kernel - but again, that's a kernel issue, nothing to do with the userland side of things. Plus with the new firmware and the new kernels, wifi tethering now works FLAWLESSLY!! Hooray! Kudos to hyc for finding that gem out...

Unfortunately I will still have to bundle .27 for the older devices, sorry folks. I know it hasn't had an update in ages, but as most of you already know the newer kernels are working really quite well.

On to the issues, hopefully dumb ones. First, I got GPS to give me a lock but it won't disappear from the status bar. I remember someone mentioning this, but I don't remember the solution other than rebooting. Is this a bug? Anyone else confirm/figure out the cause/fix for it?
[Touch Pro2, Tilt 2 Android Development] ethanpil:
Whoa!! Great news!! Any progress on the Phone not ringing/answering issue?
[Touch Pro2, Tilt 2 Android Development] detule:
I know this was an issue before, but I'll check later if something I did is exacerbating the issue.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
No clue what you mean, unless it's the ancient bug that's always been around that seems to only effect CDMA.

Since you gave 0 information to go off of, that's what I will assume - and no, I don't think any progress has been made on that at all.
[Touch Pro2, Tilt 2 Android Development] nickleby:
Hello arrrghhh, please speak to devs to see if there's a chance to include this on the next release!!!! The source is on the thread.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I don't see the point...? It allows for more characters in MMS messages?!?
[Touch Pro2, Tilt 2 Android Development] nickleby:
Ehh, nope... MMS.apk is the app for messages (sms and mms), that "patch" allows to write a 160 characters sms using certain symbols for some languages (like spanish, greek, etc) without split the sms in two or more messages. With the english language there's not problem, you can write a 160 char sms, but if you want to write certain symbols in other language (ñ, á, ó, í, etc) the system split the sms in two o more sms of 70 char...A normal phone allows to write a 160 char sms using any symbols (WM does that)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
If it's not part of AOSP, it probably won't make it in. We're pure AOSP... At least we do our best to be!

If you want to toss it in yourself, have at it ;).
[Touch Pro2, Tilt 2 Android Development] nickleby:
I'm using the patch right now, I just though it could be integrated on the GBX build just like the FB patch (which was not part of AOSP IIRC) :p

But no problem really... If there's any other people interested on that, they just can compile their own Mms.apk with the patch :D
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Fair enough. I asked detule, and he doesn't want to put it in... He would like to stick to AOSP as close as possible, and I can respect that.

However, I can tell you - if submit a properly formatted git patch that applies cleanly to our tree to the mailing list, you'll have a much better chance of getting stuff committed ;).
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Arrrghhh, Is the current GXB0C build file the one that is the new complete one, or are you still working on fixing a few things? The reason I ask is I formatted my card started a new data.img and I having a ton of issues with the build you have in the file repository right now. The most of annoying of which is getting ADW Launcher all set up like I want it just to have it reset back almost every reboot. Kexec still doesn't work for me, and Shut Down doesn't always work correctly (sometimes it just freezes like Kexec always does). When that happens that is when I get a ton of file system errors on Haret reboot. Again it might be my new SDcard since you say Class 10 doesn't like XDandroid, but I will have to find another smaller/lower class SD card to test my theory. I currently don't have any other ones because my last one died (which is why I bought the new one.)

Right now I am thinking logs are useless until either a) I know the build on the file repository is the final version of GBX0C, and b) I can figure out if my SD card is causing the issues.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ok, first of all keep in mind - kexec ONLY works for .39+ kernels. Second of all, reboot and power off don't always work correctly. I think it's a combination of how we're running Android (with loop mounts on an SD card) and the kernel. IIRC, .27 is pretty good about shutting down and rebooting correctly, but .39+ is always a reboot.

The one that's uploaded isn't quite the final version, but it shouldn't give you the problems you describe.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Using 3.3.3 kernel, and the kexec quit working on me in .35+ kernels a while back in GBX0B even after full formats, blowing up data.img etc.... Maybe it was a combination of my old SD card dying, and now my new SD Card being too good for the phone! :)

I am going to start from square-one again later tonight when I have time, see if I can find someone that has a Class 4-6 range micro-SD I can test it on.
[Touch Pro2, Tilt 2 Android Development] detule:
To summarize...
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
You obviously just have something against me dude. I do read the IRC logs, I just can't access IRC at work or I would have asked in there. I wasn't advertising the build. Most people have no clue where I am even talking about the file being at. I wouldn't have posted it had I thought it would be a problem with other people getting confused and trying to install it etc... I was pretty vague with my details on purpose.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
C'mon guys, we're all working towards a common goal here...

With that said, what will hopefully be the final build for GBX0C is uploading now. Assuming all goes well, the only changes for GBX01 are the CSV's - gotta figure out a way to get those into the build so users don't have to do the SD card trickery. I'll still leave that as a fallback option tho in case someone wants to tweak those at all...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First post updated, new build. Enjoy, please report back. Changelog in the second post. I will update the changelog further, that's just detule's changelog of what's changed on the userland side of things... I still have some things to add from stuff I did. Thanks!
[Touch Pro2, Tilt 2 Android Development] fortunz:
Yay! Something to look forward to this weekend and keep my mind off the fact that the Avengers is still so very far away. :)

Thanks to all you guys!
[Touch Pro2, Tilt 2 Android Development] pfc_m_drake:
Big Thanks!

Personally I just want to say a big thanks to all the developers, but specifically arrrghhh and detule because they seem to be doing the majority of the heavy lifting these days. You've given my phone a new lease on life and saved me from having to upgrade.

I will give the build a try in the next couple of days and report back as needed.
[Touch Pro2, Tilt 2 Android Development] ZoneBlaze:
I tried to unlock my phone today(Just now) and it won't respond to any input(hardware/software)

It can detect and tell me if it's charging or not and will alert me to text messages and can download files from Google Play, but it's stuck in the lock screen.

I can't turn off the screen either.

I rebooted, and it should work. If it doesn't, I'll edit and add info, or post a new comment.

Edit: Booted HaRET and after the splash screen, it rebooted into WinMo...

Edit2: Second try worked. Everything's fine now.

Except I had to force close Gmail, Titanium, and another app on boot :(
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Weird... maybe a dying/misbehaving SD card? :confused:

We're really at the mercy of the quality/consistency of the card...
[Touch Pro2, Tilt 2 Android Development] ZoneBlaze:
May be that. I'll post some more if anything happens again.

I'm using the same card for my Rhodium that I used to use for my Raphael.

Quick note: I used Kexec to reboot about 2-3 times in like 2 days. Maybe it affected the OS somehow?

Thanks :D

PS: Anyone tried playing Zenonia 4 or Arel Wars on the Rhodium?

Seems really laggy for me, but I may have too many processes running in the back or w/e.. Might be because of GB
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
New build works great on a 8GB class 6 card I was able to borrow. Class 6 was originally the class of card I had running before it blew up. So my issues were obviously with the Class 10 card I was trying to use, as you suspected Arrrghhh.

I still can't Kexec at all running 3.3.3 kernel, and everything was started from scratch again (format card, new data.img, etc....). That has been failing me for sometime though. Wish I could figure out what is causing it.

Thanks to Arrrghhh and detule and any other developer that put the build together.

Edit:

I did have one question though. Is there a way to get the SuperUser App to start up more toward the beginning in the boot process instead of later. Looking at my logs there is a lot of other stuff loading before Superuser actually starts. I have SDBooster and Script Manager running SuperCharger along with Clocksync, but they all require SuperUser privileges, and I think there is a big bottleneck in my startup until SuperUser starts running, because I see all those getting permissions at the same time. I was thinking I could decrease my boot/slowness time in the beginning of each boot if I could get it to run early in the sequence.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
So when you try to kexec, what isn't working? You don't swap kernels or what...? I assume that's what you're doing, swapping kernels when you kexec...?

As for detule "hating you", I don't want to see any more of that drivel. This isn't high school... ok?

On to your edit on SU - you can perhaps limit the amount of stuff that starts up, but I don't know anyway to have SU run earlier. Once you allow it and remember it, SU should allow it just fine on boot, no? I'm pretty sure it does on mine. If I've never run the app/allowed it SU permissions then it will get denied on boot - I have had that a few times, restored an app that I never ran on a new system so it was denied permissions on boot.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Well yes the particular time that I Kexec was to swap out for a newer kernel. It pops up the shutting down phone pop-up then just freezes. Have to take battery out to get it to reboot. It has been doing this to me for a while. Now from time to time I used to also use Kexec to reboot Android to help with the "No Service" issue that CDMA gets stuck in sometimes. That usually fixed the issue and was faster than rebooting back into WM and back to Android.

No I have allowed clocksync, sdbooster, and script manager to run in superuser mode. What happens though as it does with all Rhodiums is my understanding, it takes a while at boot for the phone to get stable enough (because it is loading services etc...) to actually use it. I understand that, but at the end right before it gets fast and responsive, Superuser grants all three of those programs SU access at once (I see all the pop-up messages at the bottom all at once very quickly.) Then everything is booted up and fast. My hunch was that clocksync, script manager, and SDBooster are open just sitting in limbo waiting for SU access which might be bottlenecking the whole startup process until SuperUser starts. Again it is just a hunch, I thought if it was possible to get it to load more toward the beginning of startup everything my progress faster. I know from the logs those three programs do start up before SuperUser does.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Keep in mind that I have no clue what the workings of Android are.

Do you logs tell you anything about the order in which apps load? Are they alphabetical from the /app directory? Maybe Superuser could be renamed 1superuser or Asuperuser so it is at the top of the process list.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
lol, it's never that simple mate ;).

I don't know if there is any way to change the order of how things start in Android. Try searchin around on your own, I'll do the same in my spare time. There might be a way, just never looked into it myself.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Thanks arrrghhh, I think getting superuser to startup fairly early in the boot process might help everyone running GBX0C to get it up and running faster especially if they are loading apps/services needing SU permissions at startup. I will look around on the internet. From what I have seen, there are apps that tell you what load at startup, but none of those apps can let you change the order. I wonder what file in the android system contains that information? There has to be one just like Windows to tell it what to startup.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
I figured that, but thought the idea might lead to further experimentation like deleting the apps and adding them back in one at a time if android looks for installation dates or something else. That's why I thought the logs might give a clue to the order. When you add an app to the /app folder, does it just automatically load next boot and does it load last? Just trying to give some thoughts that might spur other ideas for him to try.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Eh, I guess I've just given the phone plenty of time to boot. I know what you mean, but I always wait until the status bar goes green... which usually means all the startup apps are done starting up.

With that said, I know how this works in "regular" Linux. Just not sure how it applies to Android... I'll do some research on it.
[Touch Pro2, Tilt 2 Android Development] highlandsun:
The package manager (pm) command seems to be responsible, and it looks to me like it just does a DB lookup to see which apps have registered to be notified of particular events (including bootup, data connected, etc...)

Unfortunately that could mean the order is random (based on a hash of the apps themselves) or possibly based on their order of installation. Dunno, haven't looked.
[Touch Pro2, Tilt 2 Android Development] sifting cinders:
I've had an issue with the YouTube app always force closing when I try to start the application. last time it was working was way back on a FRX07 build.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
What kernel?

Fresh data.img, same behavior?

Logs are always helpful ;).
[Touch Pro2, Tilt 2 Android Development] sifting cinders:
youtube FC

on Rhod400. I've been running the latest 3.2.11 kernel, but I just now started from scratch with the stock GBX0C bundle to troubleshoot. same fc issue. http://pastebin.com/BDyafLnq

Also other issue with stock bundle: 1. OI file manager does not seem to install automatically, even though it is in the base app folder.

btw THX, great job on this GB build! gps lock is super fasto!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Hrm, OI was a new addition, just assumed it would work. I'll look into it.

As for your kernel, 3.3.3 is out mate - but I don't think that's your issue. I'll take a look at your log...

When you say stock GBX0C bundle, you tried to open YouTube on .27, no apps installed, and it immediately force closes? Have you waited for the phone to settle after booting?

I'll look at your logs when I get home, thanks.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
04-26 17:52:55.730 I/dalvikvm( 1806): Failed resolving Lcom/google/android/youtube/ParentalControlChecker; interface 135 'Lcom/google/android/net/ParentalControl$Callback;'
04-26 17:52:55.730 W/dalvikvm( 1806): Link of class 'Lcom/google/android/youtube/ParentalControlChecker;' failed
04-26 17:52:55.730 I/dalvikvm( 1806): Failed resolving Lcom/google/android/youtube/ParentalControlChecker; interface 135 'Lcom/google/android/net/ParentalControl$Callback;'
04-26 17:52:55.730 W/dalvikvm( 1806): Link of class 'Lcom/google/android/youtube/ParentalControlChecker;' failed
04-26 17:52:55.730 I/dalvikvm( 1806): Could not find method com.google.android.youtube.ParentalControlChecker.isParentalControlApiAvailable, referenced from method com.google.android.youtube.YouTubeApplication.checkParentalControl
04-26 17:52:55.730 W/dalvikvm( 1806): VFY: unable to resolve static method 621: Lcom/google/android/youtube/ParentalControlChecker;.isParentalControlApiAvailable ()Z

It seems you have some type of ParentalControlChecker on your phone that maybe interfering with youtube possibly. If you have such an app try uninstalling or disabling it and then try again.

Edit:

Nevermind I just installed YouTube (because I never use it), and I have the same problem as you on my RHOD400. It fails at some ParentalControlChecker I think. My logs look exactly like yours when attempting to run it. Sounds like an issue with that version of the App or our build. I would bet it is an incompatibility with the new version of YouTube and our old phones to be honest.

Edit 2:

I just found an older version of YouTube on google search. I installed You Tube version 2.3.4 and it works fine. It seems google did something with the app at some point between 2.3.4 and the current version of 2.4.4. So just go install an older version and you should be good.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Nice work! That's unfortunate tho. So Google Maps, YouTube... what's next!?!? Sucks when Google is abandoning this hardware... Can't say I blame 'em tho, it's a pain to support. This one is perplexing tho, I wonder if there's something clashing with our port & 2.4.4, and it's not necessarily an old hardware thing...
[Touch Pro2, Tilt 2 Android Development] labens:
Youtube 2.4.4 works great for me on GBX0B and Kernel 3.2.11 on RHOD400. Couldn't install from Play Store if I recall, so used GetJar with no problem. Also liking Vevo and HBO GO. Never thought I'd see HBO GO working on this, but it does with any of the 3.x kernels. Need to turn off background data sometimes to keep from being choppy, but that's because I have lots of apps and widgets installed.

I'd never use WinMo again if it weren't that I only get about 4-6 hours battery life on Android even with mibile data off. WinMo will use about 40% battery over 12 hour period with e-mail sync every 3 hours. I'll try the new build. Probably need to slowly layer apps to see whether the battery drain is from the start or what.
[Touch Pro2, Tilt 2 Android Development] slickdaddy96:
Hmm wonder why yours works on your RHOD400 and mine doesn't. I am using the 3.3.3 kernel. You know I only tried installing the apk that was with the build. I'll try to actually download it from the play market and see if there was just something wrong with the build that is included with our builds. I doubt it, but it is worth a try. Would love to see your logs of your youtube working, so I can compare it to my failed ones.

Edit: Updated from 2.3.4 to 2.4.4 from the actual market and 2.4.4 works for me also. So maybe the apk from the build is bad, don't know how the person that was having a problem installed it (from market or from app folder in GBX0C).
[Touch Pro2, Tilt 2 Android Development] mpannen:
Anyone else having boot loops after scanning for wifi networks with this gbx0c? Doesn't happen with gbx0b, but once I enable wifi and go to manage access points it's all over for me.