Hi,
I rooted my phone a few days ago and flashed the latest Siyah kernel. But as soon as my phone restarted I noticed the haptic feedbacks started playing up. I got hold of ExTweaks so that I could alter the settings, but even if I set the vibration to 100 the haptic feedback would stop working randomly after a few minutes.
Has anyone else ever experienced this? And how did you manage to overcome it? Feels weird pressing commands and not getting a physical response
PS: I wrongly flashed my phone using a different method and bricked it, didn't lost all my data as I was able to use a jig and flash the kernel. Don't know if this is important but I thought I'd put it in anyway.
PPS: Phone is GT-I9100 on XWLPT build, ICS 4.0.4, XXLQ6 baseband
Any help and direction would be greatly appreciated.
Thanks.
Related
Dear all
Since last week, my s2 reboots automatically And randomly.
I thought it was a rom problem, so i changed from leomar to litening 6.1
however, the problem still exists. I am using speedmod t27.
Have anyone experienced this problem? Is there any way to solve?
Flash back to a stock rom and test if it still does it.
Remove your SD card if you have one and test it.
Edit : I am doing the same thing currently with my SGS2.
I am not sure wether it is a problem of XXKH3
coz there was no auto reboot before i flashed xxKH3 roms
but for sure i will give stock rom a try
let me see the if it works
thx
Mine did the same
Got it replaced - no more reboots
Auto reboot
Hi All
Since the last two/three nights at around 22.00 UK, my SII reboots itself.
I thought they were auto updates, but nothing changed.
No download, no updates. The auto updates options are off.
I use the stock rom, 2.3.4 XWK14
Any ideas of what could happen?
Thanks
T.
Hello awesome people
I`ve been looking for people with the same problem as me, but my problem seems to be opposite of everybody elses...
I have been using GoLauncher for a while, but decided to try apex, since i think golauncher has gotten to much bloatware lately. also decided to try a new sms program called Pansi, then the fun started... I tried to send an mms with pandi and the phone for the first time in a month rebooted... then after the boot, the phone suddenly started go into a freezelock everytime the screensaver came on, sometimes i could use the power on button to get the phone to restart or shut down. and after a while i could not get past the pin code screen, so i did a factory reset, installed the lastest official update, phone booted and everything was appearing ok, but no... Did some searching and found out that some that was having the same problem used the "#*0011* and select wifi and turn the power saver off. So no I got rid of the freezelock, but my wifi is all stupid, and disconnects me all the time saying that there is a poor connection even though the signal strenght is excellent. If i turn power saving mode on, the wifi works great, but the phone will freeze on screen unlock
I also used the Toolkit from Mark Skippen to root and maybe the fix was there but still problems, any help would be appreciated...
/chrtn
tl;dr
phone freeze with wifi power saving mode on
wifi not working when wifi powersaving mode off
GT-I9300
4.0.4
i9300XXLH1
3.0.15-554452-user
[email protected]#1
SMP PREEMPT sun may 13.....
build
IMM76D.I9300XXBLH1
Hi, I think i've got the same issue.
I had the i9300XXLH1 stock rom (no problem so far)
But then I used the mskip's Toolkit to root it (insecure ALE8 Kernel + CWM Touch recovery)
Then the wifi problems starts :
If wifi is on and connected to an AP -> ok
if wifi is on but not connected -> freezelock (be patient and the touchscreen will come back)
sometimes i can't get wifi working at all...
Any idea ?
Use CF (chainfire) root. It won't mess with the kernel that is supposed to go with the latest rom. Now you are using old kernel with new rom.
Hope this helps
Thank you, will try a factory reset full wipe and try again with chainfire
Sent from my GT-I9300 using xda premium
UXELLR said:
Use CF (chainfire) root. It won't mess with the kernel that is supposed to go with the latest rom. Now you are using old kernel with new rom.
Hope this helps
Click to expand...
Click to collapse
That did it thank You again for your help
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Tyler44346 said:
Last night my phone grew legs and ran all the way across the room while i was sleeping. When i woke up, after searching for my phone for 10 minutes, the vibration no longer works. I didnt know if it was a software or hardware problem. So, I flashed a backup from the day before (where vibration was working) and still no luck. So i flashed back to my current backup, when i rebooted, right before the bootanimation, it vibrates. Odd? It works when the phone is booting up, but not when the phone is booted. I'm running houstonn's Vanilla RootBox (4-20 v1) with houcha kernel. All help is appreciated!
Click to expand...
Click to collapse
Thanks for everyones help...
I was able to fix this, and find the root of the problem (for me atleast). Everytime i click the Dark RootBox, vibration stops working. To fix, you must wipe the device completely, and reflash the rom.
Hello everyone,
I have a samsung Galaxy S2 and facing quite enough issues with it.
Problem started when one fine day "Media scanner" kept running. I googled for that problem, uninstall few doubtful apps,
cleared off other data but all in vain.
Finally, I did factory reset to get rid of this. After factory reset, I got below problems :
1. Lag in Samsung keypad
2. No audio at all (alarm, incoming calls, music, FM Radio etc etc.)
3. Camera failed.
4. And some times, face issue while rendering.
To solve first one I install swiftkey app which is working fine.
For audio issue, I googled but nothing was useful for me.
Currently, my device has Android version 2.3.4 , i.e. as it was shipped.
I am thinking to update to Ice Cream Sandwich (thinking that can solve all issues) but before that need opinion of experts.
If anybody can "pinpoint actual issue which caused all this or give some direction in solving this" , that would be great help to me.
Thanks in advance for help
With Regards
Neha
First don't go to ics 4.0.4 stay well away from that firmware :thumbup: flash lsw 4.1.2 and report Bk mate. You can use ics 4.0.3 if you want though.
andrewwright said:
First don't go to ics 4.0.4 stay well away from that firmware :thumbup: flash lsw 4.1.2 and report Bk mate. You can use ics 4.0.3 if you want though.
Click to expand...
Click to collapse
Firstly, Thank you for suggestion.
Secondly, I want to mention, my device has started working smoothly its own. Today morning it got fully discharged and got shut down, after charging it is working without any issue. I am not sure, whether battery charging/ discharging has some link to all those issues because I had rebooted it many times.
Anyways OS upgrade is required, hope my experience can help somebody else also
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
It's probably a software issue, JB has tons of bugs. What kinda advise do you want? You need to re-install the rom (and clear cache ofc) and if that doesn't work re-install the stock rom via odin and then install neatrom if you want. And just don't use power save mode until you get an update? It's useless anyway... You can also try another kernel, this seems like a kernel problem.
Power saving actually just have a few advantages like turning of un-needed things like haptic feedback and some other stuff which you could do manually, and the main power saving feature is that it limits the CPU to use only 800Mhz max, this might be having some issues with Apollo kernel (as it works fine with stock or stock based kernel like Philz), but Apollo is a powerful kernel and will let you manually adjust the CPU limits even at your preferred limits manually, so if you want to save battery just manually adjust the settings instead of using Power Saving mode.
Sent from my GT-I9100 using Tapatalk
Perphide said:
Not long after I enabled the power saving mode on my S2 the device suddenly shutdown (while in my pocket, battery around 60% full) and couldn't turn on again. After 2 days the S2 suddenly booted again but still won't start up all the time when I want to.
My S2 device never had this issue before (I know it is a well known issue but apparently it should have been fixed in JB?)
Software I use:
- Apolo 4.12 kernel (Regular)
- Neatrom Lite
I am thinking of either hardware starting to fail or maybe the Apolo kernel has a bug that was triggered by enabling the powersafe mode?
I am not sure, anyone that can help/advise me?
Click to expand...
Click to collapse
It may be a bug in that rom. try another rom
Thank you!
Thank all of you for the help and advise!
I will no longer use the powersafe feature and start using the Apolo kernel again, since that kernel gave me the best battery life.
It might have been a coincidence of course that my S2 died/didn't want to start up no more shortly after using the powersafe feature... however from all of the above advise it seems that I don't need that feature anyway so I feel safe to switch back to the Apolo kernel again with my new installed NeatROM SuperLite 2.4.
If the problem returns I'll be here to post it, it might still be a bug in the Apolo kernel of the NeatROM ... I am not sure. Time will tell, or not if it had to do with the powersafe feature which I won't be using any more.
Thank you all!