Related
Just a "heads up"....
On October 28th I got my HTC Titan and it has been the best phone I've had in my hands. Until this morning.
I stared the day by reading email. I put the Titan on the table and went for a cup of coffee. As I was standing by the coffee machine I saw the phone rebooting. "OK", I thought, "that was strange". But I let it boot, hoping that was it.
But that wasn't it. It kept rebooting. The longest time it went without rebooting was 10 minutes, but often it restarted every 1 minute or so.
I tried pulling the battery, and restarted. Still rebooting.
I tried removing my apps, such as Rowi and Spotify. Still rebooting.
I tried a hard reset, and added my accounts (Exchange, Twitter, Facebook). Still rebooting.
I tried another hard reset. Still rebooting.
I sent it to service. Hopefully they'll find out why.
The only other similar issues I've been able to find are issuses with HD2 and the SD-card. But the Titan only has built in memory. If this is the culprit, I would really, really like to know what caused this as I haven't done anything special.
It does not appear to be a common problem, but have anybody else heard of this?
Update rom to 1.09..
If the Service Center doesn't upgrade (and the error returns), I will consider this. (It's this one, right?)
I was just hoping that a brand new phone would last longer than 10 days before I "hack" into it. As it is so new, I don't want to do anything to break my warranty.
uiqjirka said:
Update rom to 1.09..
Click to expand...
Click to collapse
... and just to be sure: Is this just a general suggestion, or do you know it to solve my problem?
It is an official ROM that means you will not lose the warranty.
This ROME is intended to solve restart problems, wifi drops etc.
Great! If Service does not upgrade, and/or it happens again, I'll try that first.
if you havnt tried it yet you should try a new sim-card. we have had quite strange behavior with a couple of titans here at work with sims that were about 2 years old. with new sim-card - no problemas.
//jonte
jonteponte said:
if you havnt tried it yet you should try a new sim-card. we have had quite strange behavior with a couple of titans here at work with sims that were about 2 years old. with new sim-card - no problemas.
Click to expand...
Click to collapse
My SIM-card was from 2006(!) so we tried that first.
But thank you for the suggestion.
Moskus said:
My SIM-card was from 2006(!) so we tried that first.
But thank you for the suggestion.
Click to expand...
Click to collapse
hmm, another thing - i know norway has come a long way on the "mobile-office-extention" - we now has something similar in sweden and my titan is connected to our companyswitchboard - and if i make some changes to our part(cisco) (not Telias, our carrier) and im in any kinda call with me titan it will enter an almost always neverending hang. if i disconnect my titan from our swithboard i still hasnt experienced a single hang.
not a solution but something to perhaps help you along the way =)
I've been having this exact same problem - and I only received the phone yesterday! I'm going to wait for a reply from HTC before flashing a ROM although I was disappointed to note that their website doesn't even have a support page for the Titan.
Does anyone know where the updated ROM actually came from so that it is known and not just reported to be an official ROM?
deinstall the HTC apps, this solved it for me!
my sim-card is really old, no issues with that, also I am running the 1.09 Rom
pencilcase said:
deinstall the HTC apps, this solved it for me!/QUOTE]
I didn't think of that, as I didn't thought it was possible! It never even occured to me that it could be done.
If that makes it work, then we should tell HTC. They are certainly not helped by their own flawed software...
Click to expand...
Click to collapse
HTC have said that the 1.09 ROM on here is not an official ROM, since an official ROM would come over Zune.
I have been advised to either re-set the phone to factory default or contact the retailer about a replacement. I seriously doubt a re-set will fix this, so I'm likely to have to return it, which is incredibly annoying.
I've received a further reply from HTC, below:
"With regard to the issue being software related - we have not had any confirmation or known faults with the current ROM version on the Titan.
If the issue was found to be an issue with the ROM an update would indeed be issued, but as we have nothing confirmed I cannot say if an update will be provided to fix this at this moment."
If other people are having this problem then it needs to be reported to HTC before they will do anything.
Putrescine_UK said:
HTC have said that the 1.09 ROM on here is not an official ROM, since an official ROM would come over Zune.
Click to expand...
Click to collapse
I don't know exactly how it works now, but before there were two kinds of ROMs. The one released to everyone, and the ones given to service centres in case of bugs.
I believe this is a situation for the latter.
Putrescine_UK said:
HTC have said that the 1.09 ROM on here is not an official ROM, since an official ROM would come over Zune..
Click to expand...
Click to collapse
If this would not be an official version it won´t be possible to flash it without an unlocked bootloader..
uiqjirka said:
If this would not be an official version it won´t be possible to flash it without an unlocked bootloader..
Click to expand...
Click to collapse
You are right!
uiqjirka said:
If this would not be an official version it won´t be possible to flash it without an unlocked bootloader..
Click to expand...
Click to collapse
Did you say "won't" instead of "shouldn't"?
I guess what I am asking is:
Is it possible to flash the 1.09 ROM without an unlocked bootloader or not?
Yes,without unlocked bootloader,it is official rom
Awesome
Sent from my stock rooted D3
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
I tried this method and it didn't work for me , I even did a complete wipe and re-flashed the rom and gapps, I also re-flashed two separate modems amd was never able to connect to the mobile network. when I first flashed the ROM everything worked great, but when my device went to deep sleep it never came back
Phalanx7621 said:
Have you tries rebooting with airplane mode enabled and then disabling it when fully booted? This has worked for me in the past, although I've never had to wait as long as you've stated you have for a signal.
Click to expand...
Click to collapse
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
maninblack86 said:
Thanks for the advice, but it's a no go. I reboot with airplane mode enabled, but when I disable it my phone still takes forever to get a signal.
Click to expand...
Click to collapse
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
chacha123 said:
I have the same problem despite wiping everything many times. mine take approx two minutes to get back the signals and meanwhile emei and baseband remains unknown.
Click to expand...
Click to collapse
Mine does exactly the same. Baseband is unknown and there's no IMEI info until it finally connects. I also noticed that under service state it said "radio off" until it connects and then changes to "in service".
That's very odd. It's not just this rom it does this on is it?
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
I went to the Jedi ROM with no issues....I've used tasks ROM since its infancy and never had one issue until this latest update. Kind of bummed. But in the same hand I'm liking the Jedi ROM also...:thumbup:
Phalanx7621 said:
That's very odd. It's not just this rom it does this on is it?
Click to expand...
Click to collapse
Yeah dude, I've been using Task's ROM for a while now and this has only started happening since the 4-1 version. I even flashed back to the 3-13 build just to make sure and this problem doesn't happen with that build. I was hoping the 4-14 build would fix it, but it didn't. I did see on Task's developer thread someone made a post about having this issue, but it looks like they never posted a logcat or anything to help Task resolve it. I would gladly post one if I could, but I'm new to XDA and they won't let me post on a developer thread.
i have same issues. along with my time going screwy from time to time.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
maninblack86 said:
I no longer have any issues with the time zone changing in the newest build (4-14). I don't know if you're on that build, but the workaround for that problem was to set your own time zone manually.
Click to expand...
Click to collapse
i am still on 4.1. i am not prepared for a full wipe yet.
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
epicstar1 said:
Apparently, what's happening is the radio doesn't turn on during boot (Radio baseband not recognized error or something). I fixed this problem by turning on the wifi temporarily then turning it off. Apparently this will turn on the radio and should stay that way. I hope this works for you.
Click to expand...
Click to collapse
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Did you try turning off the "Automatic Time Zone" option in the Date & Time settings? My phone always sets the time to GMT+0 when I have that turned on.
maninblack86 said:
That worked dude, thanks! It took me a couple tries, I probably didn't give my phone enough time to boot, but I got it. Definitely a lot faster than waiting for it to connect on it's own.
I wonder why this only seems to affect some of our phones, but not the majority? If I didn't know any better, I'd say it almost seems like they have slightly different hardware. I bought mine directly from AT&T the first week it was released. Don't know if they possibly made any hardware revisions since?
Click to expand...
Click to collapse
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Kasdarack said:
I have been having this problem as well.
Yesterday I did another wipe and reinstall. I did a full wipe (and in mounts formatted everything except my external SD which was temporarily removed.) after flashing the rom, I rebooted recovery and did another wipe data/factory reset and wiped dalvik, then I installed gapps. I then formatted the cache and data again and rebooted the phone. It seems to have fixed the issue for me.
Click to expand...
Click to collapse
Thanks for the suggestion, but this didn't work for me. Tried it exactly as you said, but still have the problem.
phermey said:
i have same issues. along with my time going screwy from time to time.
Click to expand...
Click to collapse
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Caligula36 said:
Same issues here, Ive just resorted to manually entering the time zone, but no solution for the delayed connection.
Click to expand...
Click to collapse
Known issue for months now about the time zone. And apparently some others have experienced a longer than normal connection delay too. Weird.
maninblack86 said:
Been having a problem with Task's latest ROM (4-14) and the previous version (4-1). Both take several minutes to obtain carrier signal (AT&T) after booting. I've tried flashing with full wipe several times, different modems, and adjusting APN settings, but nothing fixed it. My phone usually picks up service after about 5 minutes, but sometimes I've waited 10+ minutes and had to reboot again, because it still hadn't connected. Also, maybe this is just how it's supposed to work, but I've noticed that while my phone has no service, if I go to System Settings->More->Mobile networks->Access Point Names there's nothing there at all. Just a blank window until it finally connects. Is anyone else having this problem or know of any possible solutions? Thanks!
Samsung Galaxy S II SGH-i777
Android Version: 4.2.2
ROM: Task650
Build: 4.14.2013
Modem: UCLL6
Click to expand...
Click to collapse
I have the same problem. I have been using Task's ROM for a few months now and I never had any problems.
updated to version 4-14 and was enjoying it until today. Lost my phone service, for some reason the IMEI got corrupted...I don't even have the access point names choice in mobile networks...no amount of rebooting fixed it...had to flash the phone with a backup file and so far its doing fine..
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
Hi guys,
my gf is having issues with her new L9 II D605.
When having a call there's absolutelly no sound coming from the speaker and the other side can't hear anything either.
After reboot everything works fine for a while (maybe even days).
It's already a second phone with the same issue.
No root, no hack, no system update done.
System reset doesn't help.
Any ideas what could it be pls? Faulty machine, second in a row?
Thx.
+1 Spain
+1 Vodafone Germany
greece same problem here.Trying 4,1,2 so far (3 days) no pro.
PS.please write yr country to make o conlclusion if its phone problem or phone company.
+1
Greece wind
+1 Serbia, Telenor network.
Greece Vodafone
+1
+1 Serbia mts
Ok so i flashed jb kdz and then updated to kk. Its been 5 days and i havent had no sound problem. So there is a problem with flashable zips in some regions.
I am not familiar with abbreviations so please explain. I have same issue. The issue appears when I have data on, perhaps. I have 4.4.2 version and the problem is frustrating. Should I go back to a previous version, and how please? Also I have install the VUTALK disabling soft that comes from LG, somehow it felt it was causing all that. I will push it with several calls to verify it's ok...
Does anyone have any settings to apply that may resolve the issue?
Does LG give a response to the issue??
Thanks
ps. btw I'm in Greece with Vodafone
shaggy.ba said:
Hi guys,
my gf is having issues with her new L9 II D605.
When having a call there's absolutelly no sound coming from the speaker and the other side can't hear anything either.
After reboot everything works fine for a while (maybe even days).
It's already a second phone with the same issue.
No root, no hack, no system update done.
System reset doesn't help.
Any ideas what could it be pls? Faulty machine, second in a row?
Thx.
Click to expand...
Click to collapse
Is this happening after camera failed to initialize? I think it is some bug in KK .
I have problem also with quiet mode. It won't go if wi-fi is on.
I am thinking to go back to JB 4.1.2 but not sure how.
zocca said:
Is this happening after camera failed to initialize? I think it is some bug in KK .
I have problem also with quiet mode. It won't go if wi-fi is on.
I am thinking to go back to JB 4.1.2 but not sure how.
Click to expand...
Click to collapse
so i send my phone about 10 days ago to service. They returned it saying it's fixed and tested. They have changed my ROM version from 20b to 20c-220-03. The phone worked fine, and I did not have problems with calls until today. I read your post and I remember that I accidentally open my camera today and it said "failed to initialize". After that the call problem appeared again. Now I forced my camera couple times until showed the same thing, and immediately tried to call my home number and here we go, call problem. It would be sooo nice if they could just fix this goddamn error which frustrates me a lot.
It's a stock zip bug, blame it on LG, try flashing 20d haven't had a problem with it, but I'll be using cm11 soon, which I think is much better. Cheers
Sent from my LG-D605 using XDA Free mobile app
I sent the phone to the service and guess what?
LG service centre is saying it's damaged and can't be repaired as they do not have the necessary spare parts.
So I'm getting my money back... hopefully...
No problem with calls nor messages anymore
I do not encounter this problem anymore. It might be that some automatic update has resolved it. I am currently using Android 4.4.3, build KOT49.D60520g.
By the way, I do not know about any lost text messages anymore (another issue of this phone) - - also ghostly SMS does not reveal any messages that would be lost without the app. But I try to keep the memory not full as well.
The Zenfone 9 is a great little device. However, since today I have seen several automatic reboots of the device. Anyone else seeing this problem?
I haven't seen a reboot; any new app you've installed of late?
Good hint - I have installed one yesterday. Will uninstall and report back.
Unfortunately is still get 1-2 reboots a day. Not critical but annoying! Anyone else?
I'm on latest update and unlocked+rooted. Not a single unwanted reboot.
deepsync said:
Unfortunately is still get 1-2 reboots a day. Not critical but annoying! Anyone else?
Click to expand...
Click to collapse
Are you on the latest update? Mine hasn't arrived yet, but I'm worried this issue will appear on mine.
balkce said:
Are you on the latest update? Mine hasn't arrived yet, but I'm worried this issue will appear on min
Click to expand...
Click to collapse
Yes I am. No worries. Device is great. Just software.
Did a hard reset - problem persists. Not sure what the cause is - working with Asus support on it.
Hi, a friend of mine with a ZF9 has got reboot every night during charge (he uses slow charge, this night he'll try normal charge).
He had reboot even during daytime, he did a hard reset yesterday and for now everything is ok, but I'll update with new info in case of.
I've been having those reboots for weeks now. There is an official thread on the asus forums talking about it. There are more than a dozen people who have also reported it and from the looks of it, Asus hasn't found the source of the problem yet. Out of curiosity, in which country did you buy it? Are you rooted?
my version is a french version. I neither had any beta OS on it nor was it rooted. I wanted to provide Asus with Logs but they rather wanted the device for repair, now I'm waiting for its return.
I doubt this is a hardware issue though as the reboots did happen in cold state w/o any system activities ongoing. The only special thing on my setup was that I used two sim cards in parallel.
I did a hard reset and he problem remained. I also used slow charging.
I'm from Italy and the phone of my friend is not rooted and with bootlloader locked.
I heard my friend minutes ago, and from when he deactivated programmed charging the issue seems to have disappeared. Have you got programmed charging on?
Yes, I have the upload scheduled. But I'm beginning to suspect that the problem originates from a lot in Italy. I just asked you because I thought it was from there.
Love this phone but also having the same issue. Bought from Asus directly (US site) too. There's a whole thread of folks with the problem too on their forum:
ZenFone 9 randomly restarts
Hi all, I bought an Asus ZenFone 9 from the UK online store. I started to migrate the apps from my old phone to the zf9 and once I finished I started to use my new ZenFone 9 as my main phone. However, I noticed around 3 dso that when i wentato unplug a fter charging the phone it looked as if it...
zentalk.asus.com
sakun-ice said:
Yes, I have the upload scheduled. But I'm beginning to suspect that the problem originates from a lot in Italy. I just asked you because I thought it was from there.
Click to expand...
Click to collapse
Try to deactivate it and report please ;-)
My friend hasn't got reboot since then for now, two days and a half ago.
My reboots do not happen while charging, FWIW. And they're always while the phone is idle (sitting on desk). I look up and see it's spontaneously rebooting...
I was having reboots on custom kernel, just updated to 32.2050.2050.34 without going custom kernel (still rooted) and have had no reboots yet.
Mine reboots while watching YouTube app, either with high brightness, while charging, or both. It seems to be less likely to happen if i clear cache from YouTube settings.
It typically doesn't happen in other apps. Phone is stock. EU version.
After testing for a few weeks, there is a good chance that the reboots on my device are due to Magisk (not modules)