Related
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.
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.
I use xiialive to stream my DI.FM premium channels on my phone all the time, but if the screen goes off (sleep) it is about 10 seconds later (assuming it's buffered) the stream stops and skips til it eventually won't restart. This does not occur on 3G, only wifi. I have done additional testing with other apps with the same exact results. Also, if the phone is plugged in to the computer or wall charger, the stream stays on just fine even with the screen off when charging. I have checked and made sure in the wifi advanced settings to put wifi sleep to never, which makes no difference it appears. Anyone have a suggestion?
Edit: Forgot to put what I am using lol. It's an HTC EVO running OMJ's Froyo 2.2 rom on kingklicks #6 kernel. I also went back to stock kernel and also tried netarchy's kernel with the same streaming issue over wifi.
Anyone? I am really curious how to fix this issue without leaving the screen on and demolishing the battery.
How did you get XiiaLive to stream DI.fm premium? I always get a "bad playlist" error. Tell me what I need to do and I'll try to help you troubleshoot.
What I did was play the stream in iTunes. If you click get info on the stream that is playing it gives s URL with a long string of random character (your DI.FM ID number for premium) which can then be added to XiiaLive app. Just go favorites then tap add favorite and you paste in the URL. I sent it to myself via email and copy and pasted it into xiialive to make it easier.
bludragon742 said:
How did you get XiiaLive to stream DI.fm premium? I always get a "bad playlist" error. Tell me what I need to do and I'll try to help you troubleshoot.
Click to expand...
Click to collapse
bob6789x said:
What I did was play the stream in iTunes. If you click get info on the stream that is playing it gives s URL with a long string of random character (your DI.FM ID number for premium) which can then be added to XiiaLive app. Just go favorites then tap add favorite and you paste in the URL. I sent it to myself via email and copy and pasted it into xiialive to make it easier.
Click to expand...
Click to collapse
What he's saying, is that the AAC+ streams (what most people use now) don't work. That's because the 2.2 OTA for the EVO screwed up Froyo's AAC+ support even more, and XiiaLive's developer disabled it. If you have a ROM with Google's AAC+ fix added, you can just change your model number in your build.prop, or else change your model number and disable Stagefright for AAC+ streams (full instructions here)
As for the original problem: WiFi automatically turns off after a few moments of your screen being off. This is true on pretty much every smartphone. You have five choices:
1) Set WiFi to not turn off automatically.
2) Set your screen to not turn off automatically.
3) Keep your EVO plugged in.
4) Put together your own ROM and kernel, and modify the timeout for the WiFi auto-shut off to be a lot longer.
5) Use 3G/4G.
drmacinyasha said:
As for the original problem: WiFi automatically turns off after a few moments of your screen being off. This is true on pretty much every smartphone. You have five choices:
1) Set WiFi to not turn off automatically.
2) Set your screen to not turn off automatically.
3) Keep your EVO plugged in.
4) Put together your own ROM and kernel, and modify the timeout for the WiFi auto-shut off to be a lot longer.
5) Use 3G/4G.
Click to expand...
Click to collapse
My old iPhone 3G did this flawlessly for 2 years over WiFi. It should only sleep when not in use regardless of the screen being off.
1) Already mentioned it is.
2) Drains insane amounts of battery.
3) Don't always have a cord with me to plug it in... hassle?
4) I only know PHP and some Java, pretty sure neither of those would get me anywhere on writing my own stuff.
5) Already use that method via 3G (4G not in my city) except the DI.FM premium stations come in at a much higher bit rate and tend to break every minute or two and have to re-buffer.
I don't want to sound mean or anything, but none of those are viable options to fix my issue. I assumed there would be a work around to fix this issue that isn't a nuisance or a battery drainer, but maybe I am wrong.
Sorry, but there is no fix for you then. Also, are you attempting to use the high-end MP3 streams or something? 128kbps AAC+ never skips or buffers for me on 3G, even at -109dB.
Well that is why I was asking, buy someone might know a fix that you don't as well. And yes, I am using the 256kbps MP3 stream. I know that is a bit much to ask of 3G and the reason I wanted to use the WiFi. Some days it plays for hours on 3G without a hitch and other days it buffers every couple minutes. I would prefer to use the 128AAC stream, but disabling the stage-fright thing screws with my youtubes. Just having iPhone withdraws from when I listened to DI.FM premium (also in AAC) all day via WiFi.
You can use CM6 which has Google's fix for Stagefright's AAC+ issues. But hey, your choice.
--Swyped from my EVO using XDA App.
I wonder how long before the "fix" that is in CM6 makes it into sense ROMs though?
bob6789x said:
I wonder how long before the "fix" that is in CM6 makes it into sense ROMs though?
Click to expand...
Click to collapse
Ha. Yeah, not going to happen until either the ROM makers start caring, or Gingerbread comes out. Seriously.
Is this a rooted issue only, or can no 2.2 updated phone play AAC streams? If it's the later, then I would think there would be a tiny patch from sprint to fix it.
Sprint/HTC isn't going to patch it unless it's in the to-be-released Fresh claims to have gotten a hold of.
CM6 is the only Froyo ROM with the AAC+ patch.
Your only other alternative is to not use AAC+, or set media.stagefright.enable-http=false.
Ok. Well thanks for your help.
I could swear I have seen the following app but can no longer find it. I am hoping someone knows the name of it.
What I am looking for is an App that will all turn on Wifi for 1 minute every 15 minutes to see if a remembered AP is in range and connect. If one is not then it will turn itself off and check again in 15 minutes. If a remembered AP is connected to then it will stay connected until I move out of range at which time it will begin checking every 15 minutes again. I seem to remember downloading an App that did this but can no longer find it and do not remember the name.
I looked at JuiceDefender and it is overkill for this and the Apps that do this based on location never seem to work correctly.
Any help will be greatly appreciated.
http://www.appbrain.com/app/auto-wifi-toggle/com.appspot.eikatou0.autowifionoff
Thank you. This was the program I was looking for.
Hi everyone.
I'm running isertcoin 1.0.8 on desire.
According to juice plotter, my desire is activating the mobile network radio every 35 minutes for a 5 minute period and then turning itself off when I leave it overnight to charge.
This isn't autosync as I deactivate all radios before going to sleep.
My question is:
a) wtf, how is this possible.
b) Can you suggest a good log program which might be able to determine what is activating the radio and why.
It's been happening the last 2 nights so i'm assuming it's something I've recently installed, but I don't know what.