Develop Bugs

Google Maps no longer functions

I posted before about my phone always starting up in airplane mode (here) after trying to get flash working on Opera.
Well for some reason, that has gone away. YAY!
But now, google maps no longer works. BOOoo!
What happened is that I started it up at the beginning of my weekly road trip, it looked like everything was working but the "Loading" note at the top was persistent AND traffic wasn't loading. If I moved the map around, new sections of the map were being downloaded without a problem. Opera works with no problem.
I then got this error:
Network Unavailable
This application requires a data connection. Please contact your carrier, or visit www.google.com/gmm/configure.html on your computer for more info.
(Error: wininetHttpError [0 12007])
I have had Google Maps die on me before so I keep the latest version on my SD card just in case. I removed Google and reinstalled. Now it doesn't even get to a map and gives the same error message.
Because of my weekly roadtrip, Google Maps is very important to me. Does anyone have any suggestions?

If you are having so many probs why don you just hard reset or even change ROM?
Perhaps that could help.
And don´t forget to vote for Rhodium

Hard reset is always an option but it is such a pain in the ass to reload everything that is working fine now.
As for loading a new ROM, for some reason I am told that I already unlocked my phone when I run the utility. Also, none of the ROMS look (or sound like they perform) all that different from AT&T's stock ROM after the available tweaks.

Scratch hard reset from the list of potential fixes.

Solved.
[email protected]#^&*(
For some reason, ActiveSync sometimes adds a proxy server to Media Net.
http://groups.google.com/group/Google-Maps-for-mobile/browse_thread/thread/8dbd8df477c51d65
I had just upgraded one of my sync'd pc's to Windows 7.
Mother @#$%^&*

I have had the same issue, same error message.
I use Amaze GPS...it is free and gives vocal turn by turn.

Kaiser 110 problems

Greetings all --
I am posting this request for help because I've exhausted just about every other resource. The community support and documentation is great and I have learned quite a bit in a matter of days. You all are great!
Here's my situation. I have the HTC 8900 (KAIS110). Not the 8925 like most seem to have. It is my understanding that 3 versions of the "Kaiser" were made, or at least submitted to FCC for approval, and that the 8900 was to go to AT&T (branded on phone), but was canceled in lieu of the 8925. This is the non-camera version.
For reference, the following information is listed in the battery compartment:
HTC 8900
KAIS110
FCC ID: NM8KS
SKU: 64760
P/N: 99HCY091-00
Made in Taiwan
Currently:
HardSPL 3.56
Radio: 1.71.09.01
Myn's Warm Donut RLS5
kallt_kaffe's kernel 2010-06-06 (kaiser/240x320/donut/panel 2/tilt options used in LoserSkaters NBH Editor)
Problems:
1. Installing OS (Sys+Data on NAND), dmesg output shows "Block 711 is bad". Under normal circumstances, this wouldn't be a problem as the OS would remap to a new block. This could also be an issue with yaffs, or a few other things, and not even be bad. But the question remains, is this causing problems?
2. Attempting to run Calibrate Screen results in error with the following message: "The application Calibrate Screen (process org.isageek.dasbrennen.CalibrateScreen) has stopped unexpectedly. Please try again. [Force close]". I have not seen a recent post in response to whether this problem persists with all builds, or if I am just lucky like that.
3. GPS does not want to play nice. From the app store, I install GPS by Andrea Baccega. Sometimes I get a single satellite to display, once I saw 3 on screen. Unfortunately, none of the other fields (long/lat) were populated which tells me something is wrong.
Dmesg output:
GPS:env_mask=0
GPS:date=00002000
GPS:time=000000 hlat=0 llat=0 hlng=0 llng=0
GPS:speed=0 bearing=0
GPS: has been tickled!
4. Using the phone on T-Mobile, why can I not get 3G working? It keeps going back to EDGE. I have the Android data plan as well.
5. Voice search is quite flaky. Sometimes it works great once, maybe a few times in a row, and then it just stops working and presents me with the Try Again / Cancel screen, after which, there is no longer audio for phone calls. From what I can tell using Dev Tools, looks like VoiceSearch is hanging due to an issue with Mediaserver. I recall seeing this issue, or a similar one, surface in the forums but there was not much information pertaining to it that I could find.
6. The following errors appear in the dmesg output; I am posting the list just in case one or more messages are beyond the scope of normal operations:
mmc1: host does not support reading read-only switch. assuming ite-enable.
Init: cannot open '/initlogo.rle'
[RR] ERROR no local ept for prog 02000031 replying anyway!!
audio_enable()
audpp: DMA missed
audio timer expired
audio_disable()
audmgr: DISABLED
binder: send failed reply for transaction 5448 to 149:221
7. As stated above, this phone lacks a camera. The slot where the camera goes, just has a cover over it. Looks like I should be able to pop a replacement in the spot. Anyone know the part number of the rear camera, or where I might find one? I can only seem to locate the front-camera on various web sites.
Thanks all!

1. bad blocks are common, yaffs reports them, and marks them as unusable, they have no effect on running Android, ( one of my kais130's has about 10 bad blocks, works fine).
2. Thats normal also, not sure if calibration app has ever worked, although i think there is a console based one that does, never had to use it though.
3. GPS may or may not work properly depending on a number of factors, which build and NBH are used, also which gps software is used also, best combo I have found so far are the Kallt_Kaffe NBH's and Myn's warm Eclair, with GPS test (free or pro). Also note that initial fixes take some time, up to, or over 5 minutes, depending on conditions, etc.
4. Not sure, could be a number of factors again, build, local 3G coverage, APN setup, etc.
5. Never used voice search, but it is known to be pretty flakey, again build plays a large part.
6. I know that there are normally errors on boot, the audio ones are not normal however, could be due to using an older radio, or perhaps some rare kais110 issue, can't actually recall anyone reporting issues with kais110 hardware.
7. Not sure if it's possible to just add a rear camera, it'll depend if the supporting electronics were fitted to allow it to work or not, also unsure where to look for one, although you may be able to get a part number off the service manuals, ( should be in the xda-wiki pages ).

TMobile and AT&T use different 3G frequencies, so an AT&T phone such as your won't do 3G on TMobile. The EDGE will work fine, but slow of course.

purpleonyx said:
3. GPS does not want to play nice. From the app store, I install GPS by Andrea Baccega. Sometimes I get a single satellite to display, once I saw 3 on screen. Unfortunately, none of the other fields (long/lat) were populated which tells me something is wrong.
Dmesg output:
GPS:env_mask=0
GPS:date=00002000
GPS:time=000000 hlat=0 llat=0 hlng=0 llng=0
GPS:speed=0 bearing=0
GPS: has been tickled!
Click to expand...
Click to collapse
Use GPS Test (chartcross ltd), free version from Market. Configure it to not turn off display (keep it from going to sleep). Plug in a charger (if you wan to) and leave it near a window.
Within 5-10 minutes you should have a fix. After that, getting a fix normally happens within seconds. Depending on how much time has passed since you last used your GPS and also the distance you moved it while having it turned off also affects the time to get a fix.
Also blocking the top of the phone with your hand is not a good idea as it seems to be an effective way of blocking the GPS signals.

kallt_kaffe said:
Use GPS Test (chartcross ltd), free version from Market. Configure it to not turn off display (keep it from going to sleep). Plug in a charger (if you wan to) and leave it near a window.
Within 5-10 minutes you should have a fix. After that, getting a fix normally happens within seconds. Depending on how much time has passed since you last used your GPS and also the distance you moved it while having it turned off also affects the time to get a fix.
Also blocking the top of the phone with your hand is not a good idea as it seems to be an effective way of blocking the GPS signals.
Click to expand...
Click to collapse
Thanks for the response -- I had tried that over the past 2 nights, but it never took. It just did however, during the day, which is odd. I also switched to a 1.64.08.21 version of the radio today, and it worked. Previous attempts were under 1.71.09.01, 1.70.19.09 and 1.70.18.02 that resulted in failure. Odd.
Is there a way to view all roms installed, for everything? OS, kernel, radio, splash/boot, etc? I am wondering if something got hung up during flashing, or something didnt get wiped out.
Thanks!

purpleonyx said:
Thanks for the response -- I have done this several times (left it going for 10+ hrs at the max time), and it picks up 4-5 satellites, but nothing ever occurs. It sits there with the yellow light, and all of the numbers show in the 20's to very low 30's, which seems like it's a very weak signal, or a high signal/noise ratio. Could this be a radio issue?
Click to expand...
Click to collapse
20-30 actually should be enough. Anything above 40 is excellent and not seen very often. And I'm using the same Radio so that should be the problem. Don't know really. Does it work in WinMo?

kallt_kaffe said:
20-30 actually should be enough. Anything above 40 is excellent and not seen very often. And I'm using the same Radio so that should be the problem. Don't know really. Does it work in WinMo?
Click to expand...
Click to collapse
I had no problem working under winmo before i flashed android to nand. It had no delay in picking it up either. I just rebooted the phone and launched google navigator, and it's taking forever again, searching for gps it says.
If you want to use me as a guinea pig, feel free. I ended up ordering the nokia n900, as i need something working now. I am considering keeping the kaiser 110 to screw around with though. It would make a good backup device anyways. I tried Myn's Warm Eclair on it, but it dragged its legs and had too many problems. Myn's Warm Donut however, functions near perfectly and is quite fast. I've oc'd the processor to 450 MHz which provides a noticeable speed boost. I'm using your latest 2010.06.06 kernel with it. I've been questioning whether or not display 2 and 3 are the same on this model -- sure behaves the same.
-update: Phone comes to a crawl, and then locks up when GPS is used. Both the GPS Test and Google Nav.

[Q] Wi-fi disconnecting on AOSP (Non-Sense) ROMs.

After trying out several ROMs I have noticed that my wi-fi randomly disconnects, but only for (Non-HTC/Sense) ROMs.
I'm running OpenDesire at the moment, which I really like, but the arbitrary disconnetion of wi-fi is driving me crazy.
As far as I can tell, it has done this with the other Non-Sense ROMs I have tried as well, and I have no idea why.
Wi-fi does switch on, but (part of) the problem _seems_ to be that the phone has trouble actually getting an IP; other than that, and why it does this, I have no idea.
The settings (in *#*#4636#*#* test mode) are basically the same as they are for, say, the official HTC Sense OTA or Pinky, for which wi-fi seems to work perfectly.
Although, to be honest, I'm not entirely sure what I'm looking at/for...
Anyone have any ideas?
Any help would be much appreciated

It's not having an issue with getting an IP, it's having an issue with authentication.
The first thing I noticed with these roms is they do not re-prompt to enter a password again if you have mis-typed it at all. This leads to wpa_supplicant client to effectively force a connection and get a refusal in quick succession. The wpa_supplicant client on the phone then disables the connection until you step in and either choose to reconnect or edit the password manually.
The issue we are having is related to this;
After being connected to WiFi for a fair period of time, it re-authenticates with the base station/router as it's supposed to do.
From memory, the re-auth happens every 60 minutes and most decent routers are able to change this.
At this point, the client (phone) tries to re-auth and fails (for whatever reason). Instead of prompting for a password (as it should do). It tries 3 times in total and stops.
After the last failed attempt, it disables the connection that it failed to connect to and jumps back to mobile data (if available).
So. Yes, there is a major issue with the wpa_supplicant in non-sense roms. Could we get the devs to investigate this, as it's really getting to be a major pain in the arse!

I see... Thanks for the clarification. Nicely explained.
So, short of jumping ship to Sense, there's really not much I can do then, other than wait for someone more skilled than me to come up with a solution?
No workaround, third party app, router setting or anything?

Unknown at this moment in time.
I'm investigating this in my own limited knowledge of Android and Linux systems, so far I've not come up with anything solid.
As far as settings you can change on your router, it all depends on your router and it's firmware.
I've got three different routers here:
A) Trendnet TEW-435BRM v4.00.07 : No way to change Key Renewal length
B) Linksys WRT160Nv2 v2.0.03 : Able to change Key Renewal length
C) MZK-MF150 v1.00.16 : Able to change Key Renewal length
Check your router, try increasing the length and have a play around. It's not a fix, the issue is either in the AOSP kernels or the wpa_supplicant module.

My NetGear WNR2000 does not seem to have any (easy) way of configuring Key Renewal Length, but I'll have a look around. Else, I guess I'll just have to bite the bullet and go with Sense for a while...
At least now I know it's not just me. That's always comforting.
Thanks for the help acolwill!

No problems at all.
I have been trying to locate an app that will automatically restart the WiFi if a disconnection takes place, however, I've yet to find one :|
Anyone out there know of one?

eham, there's an app on the market called "WiFi Auto ReEnabler"
Give it a try, as it may well be the answer you've been looking for!

Sounds very promising indeed. Will get right on that.
Tried an app called Wifi Fixer, but that was a bust. Actually somehow managed to make things worse (for me, anyway).
Thanks for the tip. I'll be back with an update...

Ok, so "WiFiReEnabler" does actually do just that; re-associate with the network everytime the screen wakes. Unfortunately, what it doesn't do is stay resident.
It will let itself get killed by the system very easily, so I still have had a few times where I had to manually deactivate and activate wifi because WiFiReEnabler didn't have my back.
If the developer could make this a helper app/system service, this seems like it could be a decent workaround though.
I did however find an app called "Fix My WiFi" (£0.99 in Market) that seems to take care of the problem nicely, and quietly, so far (about 16 hours and counting, fingers crossed).
It also has some options to set different levels of aggressiveness, and notifications, which I like.
I also found a free app called "Wifi Reassociate" that seems to address the same issue. Haven't gotten around to trying it yet, as Fix My Wifi still seems to be doing its job.
Still, a tip for anyone with the same problem.
With that (hopefully) outta the way, I'm off to celebrate the anniversary of my birth.
Be well, friends.

[Q] CM6: BT works in RC1, breaks in RC2 & 6.0.0 Final. Why?

I've made this post in the Development section to little avail--CM RC1 BT works great for me in my car, yet RC2 and Final fail.
I haven't seen other posts depicting problems, so I'm at a loss as to why it's only me with the issues. For reference, I have a 2009 Elantra with the built-in BT headunit.
Re-flashing RC1 works every time--I'm presented the "BlueConnect(TM) wishes to Pair." dialog via the Notification Bar, and selecting it begins the pairing process flawlessly.
Here's what I've tried:
Modifying the CM-6.0.0-Final.zip archive, replacing these files with the ones from the RC1 archive:
\bin\bluetoothd
\etc\bluetooth\audio.conf, auto_pairing.conf, blacklist.conf, input.conf, main.conf
\lib\bluez-plugin\audio.so, input.so
\lib\libbluedroid.so, libbluetooth.so, libbluetoothd.so
Flashing this "modified" zip archive does work/boot successfully, but still no luck in getting BT to pair.
I was hoping the above test would work, to indicate a problem with a shared object library or driver, but as it does not, I'm left to wonder if it could be an Android system modification as part of the CM build process that's affected?
Any input or help would be appreciated. Am I really the only person with BT issues in this RC1/RC2&Final scenario?

RC2 (and the prior nightlies) fixed a lot of Bluetooth issues for people. I'd recommend reading the instructions, and getting a logcat of the error, then heading over to the CM Issue Tracker.

Thanks for the reply, and the advice--but my concern is how will logcat show any deficiency in regard to this issue?
Do you expect that perhaps I'll see some BT-related activity and a failure on my phone? I guess I was interpretting this as it'll probably do/show nothing, but anything is worth a shot.

[Q] Random Reboot and Audio Issue

https://drive.google.com/folderview?id=0ByITINOB1gxMS0RfRUduVjlaOEU&usp=sharing
^^^ Finally figured out log cat ^^^
So ladies and gentlemen after a couple weeks of searching and experimenting, i figured I would bow to the experience and knowledge of others and see what my betters thought of the puzzle i have at hand.
I purchased a T-Mobile Note 2 from a gentleman on CL. The seller mentioned that it randomly rebooted and that was the reason he was selling it. I figured, for the price, it would be worth to take, play around with and get it working again.
I took it home, rooted it with the CF Autoroot, installed CWM, and flashed a number of ROMS, cm10.2, the latest paranoidandroid, jellybeer, beanstalk, Etc. none of them stopped the random reboot issue. the only noticeable change was with the 4.3 cm10.2. It lessened the frequency of the reboots.
Also, as far as i can tell, it shouldn't be having the chipset issues, its MAG4FB, Revision 0xf7, and brickbug has it logged as having the sane chip.
Now here is the kicker, somewhere along the way, the sound stopped working. Whereas originally i had audio, the jingle would play when booting up, now there is no audio/media. No music or sound, youtube will not even play videos, the music players will either force close or look like they are playing a song, but not sound plays. Also, sound recorder shows an internal app error, and google now says it cannot access the mic. Even the phone camcorder will not record video or sound (though the camera will take pictures still). Plugging headphones doesn't yield any result. no music, no notification, nothing (even though i may have the setting for music app to open upon plugging in headphones)
So, with all this, any ideas? suggestions?

It seems the encoder components have faults. You may post some logs to help figure out the problem.
Try the logcat manual from today's XDA portal.
Sent from my HTC One using XDA Premium 4 mobile app

vecio said:
It seems the encoder components have faults. You may post some logs to help figure out the problem.
Try the logcat manual from today's XDA portal.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Finally figured out logcat and added it above.
Tried out Youtube, Apollo Media Player, Google Search, and the Stock Sound Recorder. All failures.
From what i can gather, there seems to be an error with anything media related. Here's a taste of the errors. Any thoughts?
W/AudioPolicyManagerBase( 1945): getOutput() could not find output for stream 1, samplingRate 0,format 0, channels 3, flags 0
E/ActivityThread( 3803): Failed to find provider info for com.android.athome.mediaroute.provider
E/AudioTrack( 2364): Could not get audio output for stream type 1
E/SoundPool( 2364): Error creating AudioTrack
I/AudioService( 2364): AudioFocus abandonAudioFocus() from [email protected]
E/AudioRecord( 4333): Could not get audio input for record source 6
E/AudioRecord-JNI( 4333): Error creating AudioRecord instance: initialization check failed.
E/AudioRecord-Java( 4333): [ android.media.AudioRecord ] Error code -20 when initializing native AudioRecord object.
I/decoder ( 4333): ERROR: Exception thrown from GoogleRecognizer.read()
W/System.err( 4333): java.io.IOException: AudioRecord failed to initialize.
W/System.err( 4333): at com.google.android.speech.audio.MicrophoneInputStream.ensureStartedLocked(MicrophoneInputStream.java:134)
W/System.err( 4333): at com.google.android.speech.audio.MicrophoneInputStream.read(MicrophoneInputStream.java:213)
W/System.err( 4333): at com.google.common.io.ByteStreams.read(ByteStreams.java:806)
W/System.err( 4333): at com.google.android.speech.audio.Tee.readFromDelegate(Tee.java:374)
W/System.err( 4333): at com.google.android.speech.audio.Tee.readLeader(Tee.java:267)
W/System.err( 4333): at com.google.android.speech.audio.Tee$TeeLeaderInputStream.read(Tee.java:464)
W/System.err( 4333): at java.io.InputStream.read(InputStream.java:163)
W/System.err( 4333): at com.google.android.speech.audio.AudioSource$CaptureThread.run(AudioSource.java:209)

Also fun fact, phone doesn't reboot when usb connected to the computer, so can't seem to get logcat of the reboot situation

From the logcat, it seems you have connected your device to some external display or speaker?

vecio said:
From the logcat, it seems you have connected your device to some external display or speaker?
Click to expand...
Click to collapse
But I haven't. And wouldn't that connection end after numerous flashes?

MTJ061289 said:
But I haven't. And wouldn't that connection end after numerous flashes?
Click to expand...
Click to collapse
The log just suggests the AudioRecord needs to get output from some external devices.
The "Failed to find provider info for com.android.athome.mediaroute.provider" seems your ROM miss something related to the MediaRouter feature.
Have you tried to swipe cache/data? Or update to the latest version of your ROM.

vecio said:
The log just suggests the AudioRecord needs to get output from some external devices.
The "Failed to find provider info for com.android.athome.mediaroute.provider" seems your ROM miss something related to the MediaRouter feature.
Have you tried to swipe cache/data? Or update to the latest version of your ROM.
Click to expand...
Click to collapse
I have clean flashed multiple different roms, including flashing it back to stock yet the problem persists.

MTJ061289 said:
I have clean flashed multiple different roms, including flashing it back to stock yet the problem persists.
Click to expand...
Click to collapse
Then I have no ideas:what:
Sent from my HTC One using XDA Premium 4 mobile app