Hi all,
I have a Galaxy S4 which I have recently flashed CM 10.1 onto, having used another JB custom ROM until then. I have a problem with the vibration. It seems to be working fine after every reboot, but then as I start typing messages and using other functions the intensity of each vibration seems to die a little bit more until it stops vibrating altogether (haptic, notifications, everything). A reboot will cause it to get back to normal again but the same thing seems to happen.
I can't recall if this was happening before first flashing/rooting the phone, so I'm not sure if it's a straight hardware issue. Any pointers?
Thanks
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Te3k said:
That's a strange issue.
Certain ROMs have "vibration intensity multipliers" as options, e.g. LiquidSmooth and I think ReVolt (both AOKP-based). These are helpful. That might not help you though, given that your vibration's dropping to zero (it won't matter if it's dropping from a higher level in that case).
But to rule out a hardware fault, I'd switch ROMs and see if that fixes the problem. (Because then you'd know it's software-related.)
Click to expand...
Click to collapse
emckai said:
Try going back to stock via Odin and see if it's actually a hardware issue or just CM10.1. Have you tried reflashing CM10.1?
Click to expand...
Click to collapse
I'm still new to this so it's a slow and somewhat painful process, but I just reflashed stock today and there doesn't seem to be an issue at all.
I stumbled across this thread where it appears it's a CM10.1 problem. Suggested fix is to disable haptic, reboot, enable haptic. When I get the patience to re-flash and set up my device again I'll give it a shot.
Related
When placing phone call my device crashes with purple led flash.
cell signal normal, text messages work, cell data works
I'm not sure if problem lies in hardware or software(bad flash, radio, ect)
I replaced the digitizer
Currently running Kang ICS RC0-9.0 | faux123-v025
Had same problem with Neutrino 2.1
Any ideas or test suggestions?
PROBLEM SOLVED, WHERE DID MY FRIDAY NIGHT GO THOUGH?
*deleted post incorrect information
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
dac1227 said:
Alright, phone isn't shutting off after all. Calls are active but the phone is unresponsive, and must be rebooted with battery pull. still don't know what up though.
Sent from my SGH-I727 using xda premium
Click to expand...
Click to collapse
are you already on 2.3.4.91 ?
chamoy said:
are you already on 2.3.4.91 ?
Click to expand...
Click to collapse
No, I couldn't get the zip for 4.91 to flash for some reason so I did Neutrino 2.5 after sever data formats.
update: on on GB 4.5, same problem persists
SOLVED
How did you solve the issue?
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Well the issue was less solved but minimized in the end.
After many fastboot formats and CWM flashes, I ended up fruitcaking back to 2.3.4, that's when the problem started to be less of a hassle; meaning the screen would come back on and buttons/soft-keys were again responsive and a battery pull wasn't needed.
I re-installed Turls ICS and the problem is still present, but it doesn't hinder making or receiving calls, I just hold my breath with each.
I'm suspecting that when flashing either the kernels or roms, things are not getting cleaned and formatted as well as they ought to be. I know there is a universal CWM zip floating around somewhere (seen it in the skyrocket forum). We've had similar issues in the skyrocket forum where remnants of previous flashes were being persistent, or resistant to format attempts.
I messed with it for hours trying to fix so I cannot say for sure what I did to make it a non-immediate issue, but if others describe like problems I try and help.
xscottishx27 said:
I'm having the same issue too. It's only in regular cell calls. The phone becomes unresponsive to everything, screen wont turn back on, etc. Battery pull is the only thing that has solved it for me. It's happened three/four times in the last month, at least. I'm running CM7 Faux 1.1, back when it was originally released. This isn't just a CM9 issue.
Click to expand...
Click to collapse
I was having the issue with Neutrino 2.1, 2.5; Turl ICS, and stock 2.3.4. The latter seemed to be the most effective method I employed to fix, without bricking.
Not everyone flashes their phone, but all of us suffer from bugs.
I thought of starting an exclusive thread just for discussing the bugs present on the official SGS2 Firmware.
With the experts here, hopefully they can be clarified, resolved and become history
So, i'll start with the bugs i found.
My firmware version is I9100GDDKL1
First issue
When i get a call and answer it, the screen times out, as the proximity sensor signals it to. But often AFTER the call, and after i take the phone away from my ear to hang up, the screen does not come back again, instead it goes blank black. The call is still on as i am not able to press the end call soft button.
Pressing the home key OR the power key have no affect, it last for 10-20 seconds maybe and then it comes back on its own AFTER the person on the other side hangs up.
Any ideas? This is a sensor, or a software glitch?
Second Issue
Sometimes the phone just loses connectivity. Alot of times its within the city. Its odd, because normally others using the same network do not face this issue.
I have to then manually re-connect to the network.
What issues can these be?
Third Issue
I have noticed this twice now. Phone starts acting funny, as in no signal and does not restore it. I restart it, but when i do, the entire home screen and app drawer is gone. Its blank. All other phone functions work just fine.
I restart again a couple of times, but no luck. So i finally open the back cover, take out the battery, sim and SD Card and put them back again. After that when i switch it on again, it works just fine.
Software or Hardware problem?
This thread is a great idea i think.
My firmware version is I9100XWLP4.
I have only one issue, the same as the first issue in the op, been using this firmware for about a week now, and thats the only problem i have come accross so far.
Any insight would be appreciated.
Thanks
Jesse
My PDA is i9100XWKI4 and GB on it.
First two issues are happening with my SGS2 also, but twice in a week or thrice in a week only. I think proximity sensor have some HW issue.
For calls, even phone shows good signal, but calls are dropped, before I thought it was the problem with other end party, but realized that it is SGS2 problem.
My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Sent from my GT-I9100 using xda premium
Azax said:
My firmware is i9100xxlpq and I have none of these issues. Maybe you could try flashing the rom I'm using.
Click to expand...
Click to collapse
We can solve alot of issues by simply flashing it, but i wanted to know if there is some way that we can solve them with simpler adjustments/enhancements?
Also if we conclude that something is an hardware issue, then we should just go to a service center and get it corrected, shouldn't we?
There isn't a great deal you can do about most 'problems' if you stick to stock & don't root or run custom firmware.
Short of sending it back to Samsung. Who will probably only flash the latest firmware (if there is any) if the problem isn't hardware related. Which you could easily do yourself.
Rooting/running custom firmware gives you the ability to solve problems that otherwise wouldn't be fixable (and definitely produces problems that otherwise wouldn't happen as well sometimes obviously).
I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
I think all do update their firmware. I Infact changed to the latest one recently, but it didn't do any good.
I am not against flashing man .
Just keeping it as a last resort.
sk1989 said:
I don't disagree with you that rooting/ flashing custom roms will solve most software issues or atleast lead a way to solving them.
All i am saying is, that is there a way to solve some of these problems otherwise.
Also we can find out if our phone has an hardware issue, because if some problem is too uncommon, then it probably IS isolated and can be a hardware fault.
ICS BUGS thread search please we dont need another one .
Hardware is relatively simple if you do not have a problem on GB firmware then it is not hardware .
jje
Click to expand...
Click to collapse
This is not for ICS alone.
You mean to say there can be NO hardware fault at all?
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
nmunro said:
I've had this issue with lag on the Nexus 4 lockscreen for quite a while.
The problem is that occasionally when I go to the unlock the phone, I press the lock, but the lock will freeze. Sometimes I have to turn the screen off, and turn back on a couple of times before I can unlock the phone.
I've had this issue running CM10.1 and stock rooted android 4.2.2. I've tried doing a complete wipe and re-flashing everything.
Has anyone else had this issue? I've asked a couple of people I know who have Nexus 4's and none of them have had this problem.
Did I do something wrong, is this a common issue, or this an issue with my phone?
Click to expand...
Click to collapse
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
brandonc0526 said:
I also get this occasionally from time to time. I honestly have no clue what it could be, since the screen is completely dry as are my fingers when it happens. Its a minor bug so it doesn't bother me that much
Click to expand...
Click to collapse
I also sometimes get lag when I do manage to unlock, scrolling through my screens is very laggy for 5-10 seconds, then it is usually fine.
I have a problem with lockscreen lag on a phone with a quadcore CPU and 2 GB of RAM.
Flash a custom kernel. You'll be less likely to experience lag
Don't get any lockscreen lag on my stock Android.
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Have any recommendations?
nmunro said:
Have any recommendations?
Click to expand...
Click to collapse
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
username8611 said:
The latest trinity kernel (125) has perfected the lockscreen lag, It definitely unlocks instantly for me.
Click to expand...
Click to collapse
Trying this out now. I especially liked how it told me my system was corrupted once it finished flashing...
First thing I've noticed is that the colour is a lot different. Do I need to play with any settings, or do I only need to have the kernel installed?
Also how often do updates come out?
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
username8611 said:
Messing with the settings is totally up to you. It works great "right out of the box." I don't like the stock color settings, I use trickster mod to change them to rgb 255, 255, 255 and everything else at 0 except saturation and blacks all the way up. This kernel is underclocked to 1026mhz by default, I set it to stock clock speeds. It's also undervolted by default so if you are having stability problems, try bumping up the voltage on all steps by 25mv. Updates come out pretty often, prolly a few times a month.
Click to expand...
Click to collapse
The colours bothered me so I'm trying the latest franco nightly. It seems to be at the stock clock speed, no weird colours, and it makes the haptic feedback when unlocking feel more like the GNex.
I'm still having this issue with franco kernel. I've been looking around a bit and people seem to say this is related to auto brightness. I'm going to turn auto brightness off for a bit and see if it still happens.
Also, does anyone know if using a 3rd party app for auto brightness would make any difference?
Okay, turns out auto brightness wasn't the issue. Still getting lockscreen lag. Help please.
If I put 5 fingers on the screen (when the screen is off), then press the lock button, when the screen comes on it will be completely unresponsive, some of the time. I'm not always able to replicate this.
for me, some releases of Franco have lockscreen lag, some don`t, try flashing the M2 or other post r121 builds, they are all great performers and maybe you`ll get lucky with one.
if ur using paranoid android, then its a stability issue i guesa cause the same thing used to happen with me...... or else try franco kernel... or update franco kernel if ur using franco, cause an older version had the lockscreen bug, which is now fixed!!!
sigma392 said:
Flash a custom kernel. You'll be less likely to experience lag
Click to expand...
Click to collapse
Flash a stock kernel. You'll be less likely to experience lag
I'm running CM 10.1 and the latest version of franco's kernel.
I've tried using a rooted stock and I had the same issue with lag.
I'm going to try franco's milestone build, see if I still get issues.
Would increasing the minimum clock likely help at all?
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Good Guy Mark said:
I had this problem no matter what custom ROM or kernel I would use I would get this problem I got a replacement phone and don't have this issue anymore
Sent from my Nexus 4
Click to expand...
Click to collapse
I'm thinking this may have been the issue.
How does the replacement process work?
If I save a nandroid backup of my phone, can I just unlock it and restore from there?
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
meangreenie said:
Flash the reset kernel from _motley 's kernel thread, it replaces a lot of files that might of got changed via various other kernel flashes with stock ones.
the one that causes a lot of lock screen lag is the /system/lib/hw/power.msm8960.so file
N4_422_stock_kernel_and_components.zip
Click to expand...
Click to collapse
Can I just flash this with CWM? And then flash back to franco m2?
I actually just got an RMA for my phone, because of this issue and that the back glass panel is a little loose and makes creaking noises. When I send the phone back to google, if I follow all the steps here and lock the bootloader, it should be fine to send back to them?
Google's RMA process was amazing. Took me all of 10 minutes. They're shipping a new one in 3-5 days, and they pay for the return shipping of my old device. The replacement is brand-new, not a refurbished device. My dad's iPhone 4S had a bunch of issues and he would have to book an appointment at the Apple store, which happens to be an hour away, and they would only replace his device with a refurbished one.
Hi everyone,
I bought my nexus 4 about a year ago, and very recently I decided to give Cyanogenmod a try. I must say this was the first custom ROM I flashed on my device, and I'm quite fond of it. I also flashed a modified version of the latest franco.kernel for CM (http://forum.xda-developers.com/showpost.php?p=53707610&postcount=459)
The thing is that I noticed that my phone doesn't vibrate when it's supposed to. In fact, it doesn't vibrate at all; no matter what I try, it just doesn't. For the record, it had been working flawlessly until a few days ago.
So far I've tried:
- Disabling/Enabling vibration in keyboard, notifications and calls
- Rebooting my device several times
- Updating to 20140723 nightly (I was previously on M8)
- Disabling quiet hours
I've been doing some reading, and some old threads advise to perform a factory reset, but it's kind of a hassle for me to re-sync all the photos and stuff. So, is there anything I should try before I do a factory reset? Should I try and flash a different kernel/go back to stock kernel?
Thanks
It's most likely a hardware issue. I'd backup the phone and then flash the factory image. If it still doesn't vibrate it's a hardware issue. It doesn't cost much to replace the vibrator. Do it yourself or find a local cell repair shop.
Sent from my Nexus 5 using XDA Free mobile app
I would rather change the kernel first and see if there is any issues.
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
ant_cc said:
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
Click to expand...
Click to collapse
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Click to expand...
Click to collapse
Maybe I wasn't very clear; the vibration force is OK, but the thing it that it only vibrates on startup, it doesn't buzz in incoming calls or any of that. So that's why I think the vibrator isn't broken
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Latiken said:
Recently I've been having a bit of issues with the Official MM RR rom, the BlackMix one. This happened after I decided to try a different kernel; I had been using the yarpiin kernel.
It started with apps slowing down and eventually crashing whenever I changed the volume with the volume keys. The app would freeze, and then eventually ask me if I wanted to close it. It went away after I changed the volume overlay dismiss time to a higher setting.
However, sometimes the device will just freeze for no reason, and refuse to respond to any inputs. It'll just hang at the screen I'm on, and then eventually the screen will just go black with the display still on. Then it will reboot. I think this is basically one of those random reboots people experience. Is this exclusive to RR? I had it back on my old Droid Turbo that was on RR too.
And then sometimes apps will also just freeze for no reason and refuse to respond to any navbar inputs. Pulling down the notification shade or locking and unlocking will fix it, but it happens frequently enough to be annoying.
So basically, my question is, is there another ROM similar to RR in terms of features and customization that I could try? Also, are there any fixes that I could try to alleviate these issues. My current ROM and kernel setup is absolutely perfect besides these issues and I would love to keep it this way if at all possible.
Click to expand...
Click to collapse
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
B!Gguy said:
Try Exodus. It's AOSP + CM based & the most stable MM rom I've tested.
Click to expand...
Click to collapse
What kernel do you use for it? I'm gonna go ahead and try it.
Latiken said:
What kernel do you use for it? I'm gonna go ahead and try it.
Click to expand...
Click to collapse
No custom kernal. Stock one's good enough.