Related
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
I am having the same issue on the stock 2.1. The only answer I have gotten from HTC is hard reset. But I have already done this twice. So I am going to root my phone and hopefully get rid of this problem. It only started after I updated to 2.1.
BigDiz007 said:
I have installed several of the 2.1 roms out there. Each one that i install causes my phone to randomly restart. Is this a common issue with anyone else? As soon as I go back to 1.5, the restarting stops.
Click to expand...
Click to collapse
Silly question perhaps, but are you completely wiping data and dalvik cache before flashing any of these 2.1 ROMs? Sometimes this happens if you don't do a full wipe before installing new ROMs.
I'm having the same issue, and I did a full wipe, installed several different roms and finally settled on aloysius
i've had the same problems with every 2.1 rom with the exception of darchdroid.
for me it usually happened after i placed a phone call and tried to hang up
and yes everything was wiped before flashing....
im having the same issue i knew i wasnt the only one, has anyone figured out why this is???
I am getting that error trying to install ZenEXP.
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
I do not have any issues that have been listed here. I am running fresh rom and everything is working great.Just wanted to make sure all views arebeing represented in this thread
hmmm....had a thought, did the phone get really hot when it happened....cause that is what happened when i was on fresh....
NomadHellfire said:
Same issue here, only mine's been doing it out of the box, as I got mine the day the EVO was released. I've rooted it and attempted to install several ROMs hoping to get rid of the issue, but had no luck so far. Never had the luxury of having 1.5, as mine came with 2.1, so I just thought it was the phone, honestly. Interesting to know the issue doesn't occur with 1.5...
Anybody got a copy of the stock 1.5 from original release? I'd like to give it a shot.
Click to expand...
Click to collapse
You won't be able to go back to the stock 1.5 original. That has been tried already by a bunch of developers here and it didn't work. You would probably be able to flash a 1.5 ROM (browse way back into the Development pages forum here), but since you had stock 2.1, there's no way for you to go back to stock 1.5.
For all the rest of you, not sure why you are getting random reboots, but as mentioned in the previous post, sometimes the Heros do that when they get overheated or overworked. It would be best to root and start with a very stable, non-overclocked ROM. A couple of the most stable and reliable stock-based ROMs here in this section are DamageControl 2.09.1 and nfinitefx45's Stock 2.27.651.6. I recommend you try either of those out if you haven't already -- hopefully that will fix/solve some of your troubles.
Please report back if any if you have success or more problems with these...we want to make sure you get the help you need
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
shawnwojcik said:
overheating is defiantly not whats causing my restarting. im not trying to thread hijack so ill provide a link to the thread i started about this same issue. in my thread i have attached bug reports (i think thats what they are) and now i have stopped receiving help just when i provided the info needed to see whats casuing this
http://forum.xda-developers.com/showthread.php?t=684727
Im not any good at code so i cant read the big reports well. but i believe its a hardware issue because there is a small presentage of people having these errors and i cant seam to get anyone to be able to reproduce this if it doesnt happen to them.
Click to expand...
Click to collapse
Sorry, I don't understand much of the code myself. And I think a handful of our devs here who understand all that coding have already moved on to the EVO. I read your other thread too but don't know what else to suggest. Wish I could help more. You could just be one of the unlucky few who got a bad, buggy phone right out of the box.
Have you thought about just calling Sprint customer service and asking for a replacement phone? Certainly with all the trouble you're having it may be worth it. I think even if you don't have the insurance plan, a replacement phone is only around $35.
@chromiumleaf, yeah sadly i think its time for a different phone.
I'm surprised many people are having this vibration problem and no one has a fix to this except rollback to pre-OTA. Everyone seems ignoring this problem as well. Do any developers leave any comment regards to this problem?
sovereignty68 said:
I'm surprised many people are having this vibration problem and no one has a fix to this except rollback to pre-OTA. Everyone seems ignoring this problem as well. Do any developers leave any comment regards to this problem?
Click to expand...
Click to collapse
Everyone's ignoring it because we have no idea what the problem is. Try reflashing everything then flashing OTA again?
Hi guys, first off:
thanks for that great forum which helped me getting started with flashing custom roms / getting root access etc...
When searching for my problem i found out that it is called the "Hello Hello bug".
So basically when anyone calls me and i am answering the phone the first 2 seconds or so my microphone doesnt seem to work (the person on the other side does not hear me).
I thought that this bug would be fixed in the new custom roms. i tried CM 10.1 Jellybro (http://forum.xda-developers.com/showthread.php?t=2015081) but even with this up-to-date rom i am getting the same bug.
As i couldnt find anything to fix this bug i was wondering if you guys have the same problem or if anyone knows how i can get around this issue?!
Best regards,
r3try
I have that problem. I just wait for a second and then say "hello". That seems to be working out pretty well.
Not sure on a legitimate fix though. I think it has to do with the images that the devs have to work on. Hopefully it'll be fixed in an upcoming new patch.
Known issue, will eventually be fixed.
AW: [Q] Hello Hello Bug
Try call delay patch from play store.
https://play.google.com/store/apps/details?id=cz.byteworks.cdp
Sent from my Nexus 4 using xda premium
scherfa said:
Try call delay patch from play store.
Click to expand...
Click to collapse
i already tried that before.. didnt change anything for me! (thanks for the tip though)
btw: that image verification is driving me crazy.. im trying to read what the image says for like 15 times now -.- (should those be any words, or are those just random letters? cant believe there is no better solution out there *sigh*)
so, the new update is coming soon (some of you might already have it) and i was wondering if you guys know if the new version fixes either the "hello hello bug" or the bug where you cant hear the caller at all on some calls?
Those bugs are really driving me crazy and i'm really wondering how its possible for a telephone to have so many bugs in the most basic functionality of all - TALKING TO PEOPLE!
any insights / suggestions?
r3try said:
so, the new update is coming soon (some of you might already have it) and i was wondering if you guys know if the new version fixes either the "hello hello bug" or the bug where you cant hear the caller at all on some calls?
Those bugs are really driving me crazy and i'm really wondering how its possible for a telephone to have so many bugs in the most basic functionality of all - TALKING TO PEOPLE!
any insights / suggestions?
Click to expand...
Click to collapse
For me the bug is fixed on 4.2.2.
El Daddy said:
For me the bug is fixed on 4.2.2.
Click to expand...
Click to collapse
niiiiiiice, now im really looking forward to the new version!
thx for the info
the version 4.2.2 doesnt resolve the hello hello bug for me...
do i have a chance on making it work by changing my kernel or the rom? i dont know what is the most likely cause for this.
I have exactly the same problem, no solution yet.
4.2.2 latest stable CM
same here.. problem still persists, allthough i feel like it happens fewer than before...
Hi, I have the same problem. Is there any way now to solve it? Did appear maybe any solution for that?
Nexus4 Rooted
Hi all,
I am plagued by many by the inability to keep my Pebble connected after the Lollipop upgrade on stock. I was hoping in the next OTA by Samsung by they did not fix the issue. Now Bluetooth seems even more broken and sometimes it fc's instead of deactivating.
Has anyone a good advice on how to solve that?
Eventually, I can consider also something that will require rooting as I don't know how many updates will Samsung still grant.
Cheers
What firmware are you on? I have heard that OF3 fixes the BT issues, I personally have no smart toys (watches) but I have never had any disconnection issues with my normal BT headset.
McBain_666 said:
Hi all,
I am plagued by many by the inability to keep my Pebble connected after the Lollipop upgrade on stock. I was hoping in the next OTA by Samsung by they did not fix the issue. Now Bluetooth seems even more broken and sometimes it fc's instead of deactivating.
Has anyone a good advice on how to solve that?
Eventually, I can consider also something that will require rooting as I don't know how many updates will Samsung still grant.
Cheers
Click to expand...
Click to collapse
I had this issue with CM11 on my Note 3 and then I switched back to TW ROM (AryaMod) and its all good after that...
I am using Moto 360...
Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.
I have same problem please help
walterfuster said:
Hi. I come from a6020 forum. I write here because I've discovered we have a very common bug on ROMs with kernels that support dt2w/sweep2wake features.
The issue is as the title says: touchscreen won't respond after waking up from deep sleep, while having dt2w/sweep2wake features enabled.
Only the volume +/- and pwr buttons will work.
I just have to reboot the phone and the touchscreen will work again, but after a while the issue comes back.
The only way to get the phone working normal, is disabling those features from Kernel Adiutor.
I'm part of a telegram tester group for my device, but developers there can't find where the issue is.
my question here is:
Do you have a fix/workaround, other than just disabling? Or at least do you know why dt2w causes the touchscreen to bad working, specifically?
Surely, you know what I'm talking about, cause I've seen reports for this bug on some a6000 threads.
If you could response me, @dev_harsh1998, @ED300, @rohitsinha12, or @IvanHephaestus, I'll be grateful, for sure. thanks in advance.
Click to expand...
Click to collapse
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels
dev_harsh1998 said:
This is seen to happen on the devices with non original vendor panel or on those panel which fail to pass the firmware check btw if that happens upload the kernel logs i will write an patch to fix the issue prolly we need a condition resched somewhere. I haven't much bothered upon fixing it on our device because its seen happening only for people with damaged or non original panels
Click to expand...
Click to collapse
Here you are, bro. A lot of thanks: