Hello guys,
I hope you can help me with this so please, read on. I am trying out 5.1.1 (CM 12.1) for a few weeks but I can't shake the feeling that something is wrong in my particular case.
I am running this version of CM12.1. No custom kernels, no kernel editing at all. I am running Nova Launcher. I have a 64GB external microSD card, which is half full and my internal storage has 3.8 GB of space left.
My issues are with the responsiveness. For example I have issues taking calls. It goes like this, if the screen is off (phone locked):
-caller hears one or sometimes even two rings
-my phone starts vibrating
-after one second or so my phone starts actually "ringing" with sound
-after two-three seconds the screen goes on and I am able to take the call
By that time the caller already has heard four or five rings and after the sixth one the mailbox kicks in. This is terrible. If the screen is on, the issue is nearly gone, since the phone is much more responsive.
My buddy's HTC ONE vibrates, rings and enables screen INSTANTLY when a call comes in. Yes, he has a stronger phone but I'd think the most basic function would always work.
I get similiar issues with timers, notifications etc. They feel "delayed", first the vibration, then the sound, then the screen. Looking at a black screen for 5 seconds while the timer is beeping crazy is not very nice.
The phone feels fine otherwise, some apps (Open Camera) take long to open up but I guess that's just the old age of the hardware. My main problems are with the core functions (phone...).
I like lollipop, especially ART, but I am thinking of going back to CM11, since it felt a bit more responsive and I had no troubles getting calls.
I am glad about any help I can get. Thanks in advance guys. XDA rocks.:fingers-crossed:
Nobody got any ideas?
Sent from my GT-I9300 using Tapatalk
Behemoth1702 said:
Hello guys,
I hope you can help me with this so please, read on. I am trying out 5.1.1 (CM 12.1) for a few weeks but I can't shake the feeling that something is wrong in my particular case.
I am running this version of CM12.1. No custom kernels, no kernel editing at all. I am running Nova Launcher. I have a 64GB external microSD card, which is half full and my internal storage has 3.8 GB of space left.
My issues are with the responsiveness. For example I have issues taking calls. It goes like this, if the screen is off (phone locked):
-caller hears one or sometimes even two rings
-my phone starts vibrating
-after one second or so my phone starts actually "ringing" with sound
-after two-three seconds the screen goes on and I am able to take the call
By that time the caller already has heard four or five rings and after the sixth one the mailbox kicks in. This is terrible. If the screen is on, the issue is nearly gone, since the phone is much more responsive.
My buddy's HTC ONE vibrates, rings and enables screen INSTANTLY when a call comes in. Yes, he has a stronger phone but I'd think the most basic function would always work.
I get similiar issues with timers, notifications etc. They feel "delayed", first the vibration, then the sound, then the screen. Looking at a black screen for 5 seconds while the timer is beeping crazy is not very nice.
The phone feels fine otherwise, some apps (Open Camera) take long to open up but I guess that's just the old age of the hardware. My main problems are with the core functions (phone...).
I like lollipop, especially ART, but I am thinking of going back to CM11, since it felt a bit more responsive and I had no troubles getting calls.
I am glad about any help I can get. Thanks in advance guys. XDA rocks.:fingers-crossed:
Click to expand...
Click to collapse
Never used Nova Launcher. Haven't experienced the in Buiilt launcher . Why not try it?
Related
Sorry to sound a bit down. It's just that after 6 weeks of increasing hell with my Hero, sorry, Halfwit, I'm really, really missing my Touch Pro2.
1. Phantom Screen Flipping: No one knows the solution to this problem. My home screen now constantly flips to the right. In fact, any screen with an option causes erratic flipping (contact screen, email screen, menu screen etc). It's worse than a landed fish.
2. Random Battery Draining: Usually my Halfwit lasts a full day. Sometimes, though it drains within an hour, for no apparent reason.
3. Ringtone Madness: A couple of days ago I took a call. The call was instantly dropped. But the ringtone kept going. And going. And going.
4. Dropped Calls: probably 3 in 10 calls are dropped, either coming in and going out.
And just to be a little unfair, (but I feel justified): Sense. I've given up switching between "Home", "Office", "Travel", and so on. I could make breakfast in the time it takes to change.
Like I say, I know the entire Universe has had an excellent experience with the Halfwit, so before I return it, can anyone suggest a reasonably polite solution?
You could try flashing the new rom (again) to make sure that process went well.
If the problems consist send it back to htc cos it's not normal to have all these problems.
Yes, to have some many of these non standard issues at the same time, you must have a faulty unit.
I have never heard of a Hero behaving like that. Send it back and get a new one!
singing hound said:
1. Phantom Screen Flipping: No one knows the solution to this problem. My home screen now constantly flips to the right. In fact, any screen with an option causes erratic flipping (contact screen, email screen, menu screen etc). It's worse than a landed fish.
Click to expand...
Click to collapse
Thats a bug when you open the 2G data connection
http://forum.xda-developers.com/showthread.php?t=546206
Take that thing back and get one that works! That stinks you've had so many problems, definitely not normal or acceptable. It's a great phone, sounds like you got a lemon.
Sounds like a software malfunction or maybe your device could have liquid damage in it.. Not sure though, you should take it back to the store!
I am new here and dont know where to post this. My question is if anyone has the problem with when someone calls the phone lights up but then only rings the last 5 seconds the same with it just on viberate so I barley have enough time to answer the phone. I have had this problem on three roms kaos v37, tazz vinilla v20 and tazz sense 2.2.1
Sent from my Eris using XDA App
Eris dialer lag... my only "solution" to this problem that i've run across...
changed your default "low" clock to 480... (most ROM's around here will probably default to 245)...
however, that will tend to lead to worse battery life. if you are using a Sense-based ROM, it will probably be worse.
maybe someone else has a better solution
To add to that, even with the minimum at 480, this still does happen.
Take note at how long it takes the phone to really get into the ring, with the ringtone and all, if you're, say, web browsing with your phone, or using The Weather Channel App, or YouTube.
The phone has slow internal memory (the processor is not the bottleneck at 528mhz, usually, and definitely not overclocked at 710mhz+ like most ROMs are) and the processor DOES ramp up its speed pretty quickly when a ring comes in.
Neither here nor there, there's not a WHOLE lot you can do to fix it. It's an Eris thing. HTC Hero has the same situation. It's my experience that SenseUI 2.1 ROMs come to a full, answerable ring faster than Froyo ROMs, but I haven't seen if that changes with the newer kernels and ROMs around.
Call Verizon and have them extend your ring from 30 seconds to 40+ seconds. I have mine at 40 seconds (8 rings) instead of 30 (default - 6 rings), and that extra 2 rings makes it so I virtually never miss a phone call.
I highly recommend that. Works perfectly.
You could also (with a SenseUI or Stock ROM) reduce your Slot Cycle Index.
Dial ##778 (call)
Edit
Pw: 000000
Modem
Slot Cycle Index.
Stock, the slot cycle index is at 2, which means your phone 'pages' the tower for new calls/texts/voicemails every 5.12 seconds. So in other words, it could be up to 5.11+ seconds that someone else is calling you, before your phone even pages the tower and KNOWS that someone's calling you. So they easily could be on the second ring before your phone 'sees' the ring. Then, your phone has to react. Cut data connection. Pause whatever process it's in the middle of. Free up some memory if necessary. Pull up the 'answer' screen... etc.
The point is, that by putting your Slot Cycle index at 1, you're cutting that 5.12 seconds down to 2.56 seconds. If you put it at 0, you're cutting that time to 1.28 seconds.
Having a lower Slot Cycle Index drains more battery (somewhat notciably at 0, but 1 is a good compromise), but your phone will ring faster (earlier in the call) and you will be less likely to miss it.
If you change the value to 1 or 0 or something, after you change it push
Menu >>
Committ modifications
(your phone will reboot to make the change.)
I put my gf's phone on 0 because she's on Cricket - and Cricket only gives you 4 rings (20 seconds) to answer the call. So that thing has to ring FAST, or you miss the call. With Verizon, I have mine at 40 seconds, so I just leave my slot cycle at 2, and it works just fine.
Isn't it kind of funny how all those old dumb phones ring just about instantly (as soon as they page the tower), and these smart phones have all this process to go through just to answer? Kind of silly, a little bit.
But a necessary 'evil' to have a fully functional computer in your hand, IMHO.
pkopalek said:
Call Verizon and have them extend your ring from 30 seconds to 40+ seconds. I have mine at 40 seconds (8 rings) instead of 30 (default - 6 rings), and that extra 2 rings makes it so I virtually never miss a phone call.
I highly recommend that. Works perfectly.
You could also (with a SenseUI or Stock ROM) reduce your Slot Cycle Index.
Dial ##778 (call)
Edit
Pw: 000000
Modem
Slot Cycle Index.
Stock, the slot cycle index is at 2, which means your phone 'pages' the tower for new calls/texts/voicemails every 5.12 seconds. So in other words, it could be up to 5.11+ seconds that someone else is calling you, before your phone even pages the tower and KNOWS that someone's calling you. So they easily could be on the second ring before your phone 'sees' the ring. Then, your phone has to react. Cut data connection. Pause whatever process it's in the middle of. Free up some memory if necessary. Pull up the 'answer' screen... etc.
The point is, that by putting your Slot Cycle index at 1, you're cutting that 5.12 seconds down to 2.56 seconds. If you put it at 0, you're cutting that time to 1.28 seconds.
Having a lower Slot Cycle Index drains more battery (somewhat notciably at 0, but 1 is a good compromise), but your phone will ring faster (earlier in the call) and you will be less likely to miss it.
If you change the value to 1 or 0 or something, after you change it push
Menu >>
Committ modifications
(your phone will reboot to make the change.)
I put my gf's phone on 0 because she's on Cricket - and Cricket only gives you 4 rings (20 seconds) to answer the call. So that thing has to ring FAST, or you miss the call. With Verizon, I have mine at 40 seconds, so I just leave my slot cycle at 2, and it works just fine.
Isn't it kind of funny how all those old dumb phones ring just about instantly (as soon as they page the tower), and these smart phones have all this process to go through just to answer? Kind of silly, a little bit.
But a necessary 'evil' to have a fully functional computer in your hand, IMHO.
Click to expand...
Click to collapse
Sorry to bump an old thread, but this issue has been plaguing me for some time now. I have my cpu set at 480MHz min, 604MHz max & my phone still seems to lag when there is an incoming call. The screen takes a long time to turn on, and only rings a few times before I miss the call. I am currently running Condemned v17 S2H, but have experienced this issue on other roms as well. Is there any way I can perform the ##778 procedure on a non-stock/non-sense ROM? If not, are there any other fixes out there?
Edit: This doesn't happen to me on every single call. Sometimes the phone seems to respond quicker than others. However, when it does occur, it is usually two rings or so (tested from a landline at work) before I hear my ringtone & the screen turns on.
CondemnedSoul may have found a solution to this issue. See his post here
WARNING: ANYTHING YOU DO TO THE BUILD PROP IS DONE AT YOUR OWN RISK!! IT IS NOT RECOMMENDED TO MODIFY THIS FILE! DO NOT ATTEMPT THIS UNLESS YOU ARE SURE YOU KNOW WHAT YOU'RE DOING!!
With that said, however, I made the change to the build prop that he specified. I had a chance to make a few test calls before I left work, and it did seem to improve my phone's response speed. However, it was only a small sample size. I should be able to give a better answer in a few days after further testing, but for now, I think we are good! I'll keep everyone posted.
PillClinton said:
CondemnedSoul may have found a solution to this issue. See his post here
WARNING: ANYTHING YOU DO TO THE BUILD PROP IS DONE AT YOUR OWN RISK!! IT IS NOT RECOMMENDED TO MODIFY THIS FILE! DO NOT ATTEMPT THIS UNLESS YOU ARE SURE YOU KNOW WHAT YOU'RE DOING!!
With that said, however, I made the change to the build prop that he specified. I had a chance to make a few test calls before I left work, and it did seem to improve my phone's response speed. However, it was only a small sample size. I should be able to give a better answer in a few days after further testing, but for now, I think we are good! I'll keep everyone posted.
Click to expand...
Click to collapse
Based on what I've seen to this point, it seems that there is still some lag on the first phone call received after a reboot. However, every subsequent call after that has been much quicker to respond. Overall, a definite improvement on my phone. If anything changes, I'll let you know.
For another possible solution, check this thread here & the original thread from the Samsung Galaxy Ace S5830 Development Forum.
I used the above link yesterday and can't be happier. Seems to have made things smoother and rings much snappier...
Had the same problem and it was mostly due to the cpu being underclocked. moving it to 480 helped but still wasn't a fix.
there was a post, looking for it now, in the mod section about a script that would reduce the ringer delay. I installed that and my phone rings on my end after/during the second ring on the other end.
Hey guys!
I'm kinda lost here. I've had my Archos Gamepad with Android 4.1.1 (sorry, forgot to put the device in the title) for a few weeks now. Yesterday I noticed there's no sound coming from it anymore. Since I mostly use it for things that don't require sound I can't really say when was the last time it worked. When I loaded up an N64 game yesterday I first noticed that there was no sound. Luckily, a reboot helped, I played for a few minutes and then put it away. Later that night I picked it up again, sound was gone.
After rebooting and fiddling around with settings about a thousand times, I can now say it will always go like this:
Reboot, unlock, unlocking sound is heard, clicking a few things, sound is fine, then all of a sudden it's gone.
But here's the strange part: When I lock the screen, it will always play that little *click* from the speakers. That one never fails. There's no sound at all no matter what I do, but as soon as I press the power button it goes *click*.
So here's a few facts:
- Sound stops after a few minutes of working, no matter what I do, even after factory reset
- Lock sound always plays
- Headphones do the same, working for a while then stopping, lock sound stays
- of course sound levels are at max, and there's no apps that do anything sound-related
- after connecting it to my laptop today it worked for for a while, longer than usual, but was gone again when I picked it up later
- auto-rotation of the screen also started failing on me from time to time, maybe related?
As a sidenote, a few days ago my washing machine broke, releasing a flood of water on the floor and my Gamepad just so happend to lay there, getting a little water on it. I picked it up right away, dried it off and shut it down. I don't know if that's anything to do with my problem because a) it worked fine when I turned it back on later, b) since the lock sound keeps playing I don't think my sound is broken hardware-wise, and c) I can't tell when sound stopped working because like I said before I don't always need it.
The working lock sound is what really confuses me about this. I just don't know what to make of this.
If anyone has even the slightes idea it will be much appreciated!
mookieananas said:
Hey guys!
I'm kinda lost here. I've had my Archos Gamepad with Android 4.1.1 (sorry, forgot to put the device in the title) for a few weeks now. Yesterday I noticed there's no sound coming from it anymore. Since I mostly use it for things that don't require sound I can't really say when was the last time it worked. When I loaded up an N64 game yesterday I first noticed that there was no sound. Luckily, a reboot helped, I played for a few minutes and then put it away. Later that night I picked it up again, sound was gone.
After rebooting and fiddling around with settings about a thousand times, I can now say it will always go like this:
Reboot, unlock, unlocking sound is heard, clicking a few things, sound is fine, then all of a sudden it's gone.
But here's the strange part: When I lock the screen, it will always play that little *click* from the speakers. That one never fails. There's no sound at all no matter what I do, but as soon as I press the power button it goes *click*.
So here's a few facts:
- Sound stops after a few minutes of working, no matter what I do, even after factory reset
- Lock sound always plays
- Headphones do the same, working for a while then stopping, lock sound stays
- of course sound levels are at max, and there's no apps that do anything sound-related
- after connecting it to my laptop today it worked for for a while, longer than usual, but was gone again when I picked it up later
- auto-rotation of the screen also started failing on me from time to time, maybe related?
As a sidenote, a few days ago my washing machine broke, releasing a flood of water on the floor and my Gamepad just so happend to lay there, getting a little water on it. I picked it up right away, dried it off and shut it down. I don't know if that's anything to do with my problem because a) it worked fine when I turned it back on later, b) since the lock sound keeps playing I don't think my sound is broken hardware-wise, and c) I can't tell when sound stopped working because like I said before I don't always need it.
The working lock sound is what really confuses me about this. I just don't know what to make of this.
If anyone has even the slightes idea it will be much appreciated!
Click to expand...
Click to collapse
As you still have audio with the lock sound it doesn't sound like you broke it totally with the water damage so I recommend contacting Archos for a return/replacement.
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Do you remember when were the times when the screen was unresponsive?
I've read somewhere that sometimes when the screen is woken up and is under some pressure this will happen, and the only way is to do what you did. It's not uncommon in touchscreen phones though, so I wouldn't worry about it.
The verge app was broken until the most recent app update. Also, the s5 seems to refuse allowing Dashlane's accessibility service from working properly. So no more auto filling passwords for me. Ugh. I hoped rooting might help but it didn't. Now I really can't wait for custom ROMs to start appearing. Samsung, you make great hardware (like amoled displays) but your software sucks. Even the software on my Samsung TV is stupid.
Yes on two out of three!
finotti said:
Dear all,
I've been waiting a little before rooting and installing a new ROM to make sure I don't need to return my phone for any reason. (So, it is stock now, no root, locked bootloader, KNOX still there, etc.)
So, far I've noticed three small problems, which I don't know if they are universal or just mine:
Sometimes when I get a call, the touch screen is irresponsive. If I press the lock/power button twice, it seems to work again. (I now have set up to press home to answer.)
It often feels a bit warm, more than I'd expect. (I have it in a case, though, a Spigen Slim Armor. It fits perfectly though.) But this happens sometimes when it is just sitting, not playing games. It is not really hot, but I can feel it warm in my pocket.
Sometimes I get a pop between songs. See this post
(So, at least one person also has the last problem.)
I can live with any of the problems above, but I'd hesitate to have a defective unit which can have bigger problems later on. Is any of the above an issue for you? Any suggestions if I should exchange the phone?
Thanks!
Luis
Click to expand...
Click to collapse
The unresponsive screen is more than a little issue, it is being reported all over the web, and get's more severe over time. I'm thinking that it is a bad proximity sensor defect, either firmware, hardware or software. Some people are reporting along with myself that sometimes for no apparent reason, the screen will not turn on even though the phone is completely operational! This has happened to me four times now and I am stock with very few apps on my phone, five total games and Pandora. I do use a substitute launcher that I've used for years but I don't believe that would be the issue since others report the same issue with stock launcher.
The pop or skipping you speak of in sound happens to many of us who stream music in our automobiles. It even happens on the note3. The fix is simple for that one though! Turn the screen on. I was told that with many of the streaming software music programs that the phones CPU goes to sleep and does not offer enough processing power to the music program. I stream all day via bluetooth to my Auto's sound system and it will usually start to skip, click or whatever after the phone has been untouched for about twenty minutes. The second I turn the screen on the problem alleviates itself. You can find even more information by googling that one, in fact both of those! The heat one I have not had, both with stock battery and zero lemon high capacity battery. The phone very rarely get's warm. However, when I was using wireless charging it would get warm even after charging was complete but I believe that is a normal event with QI type tech.
So I bought my phone from AT&T just as the new M8 was coming out (got a good deal as a result) and ever since that day its been dependable, efficient, and never lagged a single second.
But then the HTC Sense 6 ROM started to act up, opengl issues, and various bugs that drove me insane! So I switched to CM11, (btw no IR or radio or hardware encoding support on it) and all went well until about 2 weeks ago.
Suddenly my phone is sluggish at times, especially on switching applications, and the battery life went from around 10 hours average usage, to 5... Now its down to 3... Not only that but the phone is HOT!
If I even watch a Twitch stream, or YT video, or play a game, or even navigation, camera, chrome, anything with it (including listening to music), the device gets to 43 degrees C. That is with the device out in the air, passively cooling.
If I leave it on a surface, with the back covered up (like in my pocket, or watching a video in my bed) it will go past 50 C, and climb further! At one point in my car while driving, (was charging and navigating, aux was connected so i could get audio navigation through my speakers) I suddenly realized I had past my exit 5 miles back, and had to stop to check the phone...
The phone was not responding to my wake button presses, nor holding it down, it was not outputting directions, and the red LED light was softly lit (not flashing) so immediately I unconnected the charger, and aux cable. The phone still didn't respond, holding power + vol up soft resetting it worked. But what struck me most was how blooming hot it was! It was NOT in direct sunlight, nor was the display on. It practically burned my hands! I had to look up how to soft reset the phone, using my old LG Nitro HD which is my GPS tracker for my car (nifty setup btw).
Now I had an LG Nitro HD which did this sort of thing 24/7 and I could not STAND that phone, since you had to baby the device every second to keep it cool, otherwise you would need to restart.
I have seen numerous threads online about the HTC One getting toasty, and it has before for me, but NEVER THIS HOT! Also this only JUST started happening (its not related to CM11 since I had a backup of HTC's ROM and it did the same thing (in fact it was even slower x.x)
Now here is my question : is this a normal occurrence for smartphones of this age? I think its 1-2 years old... Its past the warranty I suppose (still have the card, and box btw) Is this something that I just have to deal with?
I have used the phone alot while it was charging, and left it on a charger for a long time after it was fully charged... (i thought newer phones had a disconnect for charging)
What bothers me is how suddenly the phone has become stricken with this... problem. It has only been 2 weeks, and battery life is effectively halved, and I am afraid to even USE navigation anymore (unless I hold the phone up infront of an AC vent, which I did all the way home >.< not a fun task since its a manual!)
Thanks in advance!
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure to not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Edit: if you have insurance through at&t I would go back to complete stock (get rid of tampered flag and red warranty warning included) and let them know it's freezing up. They should send you a replacement and it may help you out...
OfficialLocdoGg said:
I had this issue with my M7 for T-Mobile. I would factory reset it and things would be okay for a while until I logged into all of my common apps and realized it would happen again... Some apps make the phone work harder and a lot more on the M7... The way I fixed this was I removed apps I didn't really use and make sure you not be logged into apps that I don't commonly use... The other thing I did was restart after using any video and audio apps... One more thing was I turned on the power saver option with vibrate and cpu unchecked and my phone started acting better...
Click to expand...
Click to collapse
Yeah actually I just factory resetted the phone, and its absolutely normal now... Furthermore the USB speed is no longer 1mb/s and instead is back up to USB3 speeds!
BTW I did a firmware AND software factory reflash / reset.