Ok I am not trying to replace the other Android thread. It just seemed over crowded to try to ask another question. I was just wondering who has got android working (Making calls, using the internet over 3G/GRPS/EDGE, does it boot every time, and how often does it freeze) and what radio/rom do you have.
For android devlopment see this thread.
I can not use the internet or make calls. It boots every time but freezes after a few minutes.
I have L26V12 and Radio 1.65.24.36.
BTW: To all the people who have been working on Android development GREAT JOB!!!
I voted "Sort of", even though your description of "Sort of" doesn't exactly match my experience. More accurately, I CAN briefly get some Internet traffic once in a while, but have never been able to make a successful phone call. In any case, it completely freezes in about 2-3 minutes.
Please post what rom/radio you have and how well it works.
i have some internet (google map) (no browsing) but i can't make calls but it seems to freeze when i use the google maps
Yes (we can only have when the port is complete)
Sort of / Not Really (what we have now)
No (read the Android Thread and you'll have 'Sort of/Not Really')
Sort of - Boots everytime but freezes after less than 1min, usually I barely have time to launch an app before it freezes, so not been able to test it really.
dagentooboy said:
Ok I am not trying to replace the other Android thread. It just seemed over crowded to try to ask another question.
...snip...
Click to expand...
Click to collapse
Just FYI for everyone, that is not a sufficient reason on its own to create a new Thread.
Sort of.
I use a Nothrills rom (French rom, based on an official HTC rom with updated softwares but no other modifications)
Boot not every time.
Phone calls ok
Google maps ok
Didn't try to browse
And freeze after 2 or 3 minutes
Android rarely boots
Windows Mobile 6 Professional
CE OS 5.2.1620 (Build 18125.0.5.2)
I would willing to donate.
Related
Hi All,
I've tried searching around all over here and PPCGeeks and have not found a solution, please help guide me in the right direction. I've had a WM 6.5 beta rom (Merdin's Windows Mobile Pro 6.5 Beta 4, 4-13-09) and one day, Rhodium (Xbmod's V1D) would not load and everything got sooooo slow. I tried doing a couple clear storage's and still, same problem. Eventually, I tried the Juicy 7 (stripped down) rom w/ WM 6.5 and now I'm on db ROM Sprint Optimized. I keep having the same issues where the programs are extremely slow to open (e.g. opening a new text may take a minute to load up) and things freeze up (e.g. an incoming call can't be answered or it will keep ringing for minutes until I do a soft reset). Worst of all as if that's not bad enough, the battery under normal use, AT BEST would give me 6 hours (if I'm trying to surf the net - after IE loads because Opera takes like 2 mins to load - I'll get like 3 hours of use). I never had these issues with that Merdin rom before this. I was out of town in Orlando and wasn't installing software or anything but I was unable to ask right away before going through all this trouble as I wanted to hopefully seek out a solution. Any ideas? Is it WM 6.5? I don't think it is since I wasn't having the issues at first w/ Merdin's. Also, is Clear Storage maybe not really clearing things (although they appear cleared)? Thanks for ANY guidance!!!
Start with 6.1
WinMo 6.5 is getting better but start out with WinMo 6.1 bare roms like Da G's Ckean Rom if ur concerned about speed. Manila's, TF3D2 always slows down a phone because it adds threads that the processor has to go through.
I had been wanting to try out the actual android OS but not really wanting to buy a whole new phone (and plan because in America android phones are not on every network) and I found this site telling me how to get android on my phone
http://www.makeuseof.com/tag/how-to-install-google-android-on-a-windows-mobile-phone/
So I went for it
on the first boot the sound and mic did not work and every thing crashed and needed to be force quit repeatedly. so I booted back into windows
the next day I decided to give it another try and this time the sound worked but the mic was still not responsive. the internet seemed faster as well.
today the mic and the sound work the internet is smooth, but the "long press" of the home button does nothing, so I cannot tell if some thing is already open with out going into the terminal and killing the process, which works most of the time but a few things will not show up in the terminal as running and I do not know if that is because how I exited them shut them down or if they are just not showing up all the time.
So are these errors due to android not being set up for the fuze?
and does any one have any tips on fixing them?
also this site has alot of good info
http://www.androidonhtc.com/
http://forum.xda-developers.com/showthread.php?t=577736
They have a few builds that work pretty well on the raphael. I've tried it on my Fuze and if i rember right calling worked okay but couldn't send messages. Haven't tried the latest build yet though.
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.
Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.
Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug
superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.
Bump
Anyone have some insight on this?
Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug
Any news ?
soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse
Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.
hello guys..
i bought a htc raphael on ebay for 175 euros... its got an xda brand from O2
i descided for the raphael cause its said to run android with xdandroid...
is it capable of running android 2.1?
and what features of the phone aren't supported yet?
It works...but
My experience with Android thus far on the Raphael (My US AT&T Fuze branded) is that it runs, and can make/receive phone calls, and use the internet just fine. However, text messaging has never worked for me, neither on 1.6 or 2.0.1 (the latest I have found to install)
If you're interested, it's definitely a cool toy to play with, but not something you'll be able to run full time. 2.0.1 often flakes out on me and fails to respond after a few minutes. Both 1.6 and 2.0.1 are very taxing on the Raphael, and go through the battery quickly and make it nice and warm.
http://connect-utb.com/index.php?option=com_rokdownloads&view=folder&Itemid=68&id=2:android-port has good packages that are built around HTC devices. Click through to Android Packages for 2.0.1, or scroll down to HTC Raphael (Old) for the more stabile but less fun 1.6 release.
If you have any questions, let us know. What's the HTC/Android outlook in Europe right now? I'd consider buying one next time I'm there but too many €'s for me to buy out of contract with my weak dollars.
Happy androiding!
I've been playing with 2.01 for a few days - no bluetooth, gps or camera...and it takes a lot of battery.
There is still a lot of work before we get a stable build, but you can try out the latest version.
I've Been using [ROM][30JAN10]Gen.Y PX-TP R0 with XDANDROID (Standard|Core), Its been great for me, the only problem is turning wifi off sometimes freezes and at times the d-pad doesn't work when loaded, but a simple reboot does the trick. My battery lasts for about 8hrs with wifi off so I must be lucky!
If you don't need Bluetooth/GPS/camera it's usable as an everyday device. You can expect 8-12 hours of battery with occasional use.
It will freeze every now and then and you'll have to reboot.
The battery acts very odd, android does not read it correctly, so your % will jump around a lot.
It's usable, but as you saw some people have some problems. Just make sure you read the first two pages of directions and do everything correctly and you shouldn't have too many problems.
Just for clarification: are you guys running Android as the only OS, or using the "boot off the SD card" method?
The links I provided are for builds you can run off the SD card, but which have to be booted using the "haret" utility from within WM.
This would be to run an Android OS rather than Windows, right? It's a full OS and not just an app which emulates Android? I think I read elsewhere that dual-booting is possible, so this wouldn't delete Windows and the issues you guys mention could be overcome by booting into Windows when necessary, right? Does it matter which ROM I'm using now before using this?
Thanks.
Struff: When I run the "Haret" bootloader, WM gets shut down and then a bit of linux code gets android running. It's not really "dual boot" as you would think of it, though. The bootloader is run from within Windows Mobile and then once it does its thing, the only OS running is android.
You must first boot WM, then get the bootloader, then android will be running. At that point, a quick soft reset (after telling android to shut down) means WM will start back up.
Clear as mud.
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Benetration said:
Firstly, I have been searching this forum for about 2 hours. I have found a few threads with the same issues, but they are either not relevant or I have tried the solutions within the threads and they have not worked. Also, the threads I have found are a few months old. I have also searched the ROM thread seen below.
ROM: [06 Nov 2011][MAG/cLK] NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13]
Device: HTC HD2
ROM Installation Method: MAGLDR 1.13
SPL: 2.08.HSPL
When I accept an incoming call, the phone application hangs and after about 10 seconds I get a force close notification. Sometimes this is accompanied with a buzzing sound from my speaker. In some instances I have to remove the battery to restart the phone as it totally freezes.
This happened on Android 2.3.5 (of the ROM linked above) so I upgraded to 2.3.7 (of the ROM linked above) to see if it would fix the issue. It has not. I also wiped the phone and reinstalled the ROM, and again it hasn't fixed the issue.
Also, I do not have Skype installed so it's definetely not that.
I would have posted in the ROM thread but it wouldn't let me.
Any suggestions?
Many thanks in advance. I can provide additional information should it be required.
Click to expand...
Click to collapse
this isnt something about your phone so try another rom or tell the developers.
linkin_p said:
this isnt something about your phone so try another rom or tell the developers.
Click to expand...
Click to collapse
thanks a lot, i have same issue...maybe i'll try another ROM
buzzing HD2
Sometimes it happens on my HD2 on diferent rooms: NexusHD2 3.2, NexusHD2 ICS 1.1, MIUI 1.12.30, MIUI 2.2.17. It is not often. Any sollution?
It's same here! I am starting to think that the problem is with my phone! I tryed meny different ROM and settings...it always the same!
It doing it 2-3 times per day.
How to fix it ?
same problem
I'm using CM9 (v2.8) android 4.0.4 and facing the same problem. I tried many ROMs but can't fix the problem. Also tried some solution on this 4rum but no help until now.
I'm going to throw my HD2.
Same here
I have the same issues with different rom using nand or nativeSD.
1 on 2 receiving call, the phone freezes with a buzzing sound. I must to take the battery out to restart the phone.
same problem
I have the same problem with my HD2!
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
I have tried different kind and version of ROM(for e.g. NexusHD2, MIUI, TouchWizMod v3.0) but the freezing issue is still not solved.
As far as I checked the freezing is not related to any kind of installed software.
If anybody has a solution to this problem please share with me/us. I really do not want to get rid of my HD2.
Thanks in advance.
------------------------------------------------------------------------------------------------------------------------------------------------------------
I have found the solution. The reason why the phone did not work is the Viber application. I uninstalled it a moth ago and thence everything works well. I use the WeChat app instead of Viber and my phone works like a charm.
By the way, a member of the Viber team has commented on this forum that their application does not support any kind of custom ROM currently.
Im facing the same problem,its killing me, its been worst recently ! I cant answer any call on my HD2
this problem happend first time on android 4+ roms,
I tried diffrent roms after that, but still not fixed, anyone can help us to find a solution?!
-----
anyone using CLk has this problem?!
Im using Magldr
Im having the same problem here. Found no sulition currently. ROM - tytung NexusHD2 2.5
The phone freezes after I receive an incoming call with a buzzing sound/no sound. Sometimes it shows the error message of com.android.phone process, in other cases I need to remove the battery and restart the phone.
Click to expand...
Click to collapse
hmm same here, tried some different ROMS - SD (froyo) and NANDs (2 gingerbreads, now ICS), tried these on both of my HD2s, also changed RADIO from 2.15.50.14 to 2.08.50.05 - nothing helps.
sometimes when im getting a call (usually it happens twice a week, some weeks more often, some less), i press the button and the phone/app freezes, sometimes with a buzzing sound.
after that, system doesnt respond normally, on GB sometimes it autorebooted....
also tried without viber AND tried directly after reinstalling the different ROMS with no contacts, original ringtones - also happens there sometimes!
i dont think that could be a hardware problem, because both of my hd2 phones act the same way.....
any solution since that time?
At the moment I have latest Jelly Bean by cotulla, with Cyanogenmod, and when I make a call, the screen is black (turned off) even though I don't have it close to my head and sensor is not covered. When I abort the call, it doesn't respond and stays dark with button panel highlighted for several seconds, and only after I press power button for several times it awakens. The same happens for incoming calls. The phone is not usable as phone with such things happening... That's frustrating.
So, let me sum up what people (and I) have had on the subject:
1. Various Android ROMs were tried and issue is always present.
2. In my case, stock Windows 6.5 has a very similar issue - incoming calls are even ignored! At least I had the described problem after I decided to have an "old" but working phone and reverted to the stock ROM instead of Android. Alas, the phone was still having glitches when answering.
3. We don't know exactly how many HD2 are affected by the issue but it looks like more than 1% which is pretty much to be a serious issue.
I might assume we faced an intermittent hardware issue, that does not always reveal itself, and can only be reproduced after a certain "failure". I think it's hardware dependent because my phone was working fine but suddenly ceased to do that.
I'm very sceptical about fixing this issue for me or other users. It's an obsolete phone and any mass hardware issues that is not reported by manufacturer (btw, could this be checked out?) will scarcely be considered. The whole thing makes me think we just have to switch to our phones are gaming/browsing accessories, since it just doesn't work and the issue is apparently non-trivial to be examined. I would be though glad to provide any information and logs... but who cares? Even cotulla doesn't think HD2 is worth developing any more....