[Q] jedi mind trick back button problem - T-Mobile Samsung Galaxy S II SGH-T989

Hey guys im not sure if its been covered anywhere else but im having an issue with the back button working at all on the newest release of the jedi mind trick rom, it sometimes responds and othertimes goes into vibrating spasms and i have to reboot to get it to stop. I have wiped, factory reset, reflashed the rom with no avail, the rom works amazing otherwise. Please let me know if anyone knows how to fix this.
Thanks

do you mess with your kernel settings ?? it might be you have you gov. to low that when you try to use it it does not have enough juice to pick up the pace try picking on-demand and noop if available never really heard of that prob..

I hadn't thought of that, ill see if that helps and let you know, thank you for the suggestion
Sent from my HTC6435LVW using xda premium

no problem sometimes when using a slower gov/sio can cause some lag that will make your keys unresponsive because its not waking up fast enough good luck glad to help

I am running this ROM with no issues what so ever, so if the above info does not fix your problem, I can at least tell you exactly how I flashed it anyway.
I used twrp 2.5. I clicked wipe...advance wipe...checked dalvik, data, system, and cache. Swipe to wipe then flashed ROM and reboot.
Good luck.

I'm beginning to think this is possibly a hardware issue, I have gone back and forth between slimbean and Jedi mind trick with a slew of different kernels with no avail, thanks for the suggestions guys
Sent from my HTC6435LVW using xda premium

Related

Epic is shutting down and won't power back on without pulling battery?

Does anybody have any idea what would cause my Epic to shutdown several times a day and won't power back on without pulling the battery. I have tried doing data factory resets, Odin back to stock, different Roms and it keeps doing it. I've purchased a new battery and it still happens with the new battery. Anybody have any ideas or words of advice to help me fix this problem? Thanks in advance.
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
downyours said:
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
Click to expand...
Click to collapse
Yes its rooted. I have never messed with clock speeds, so it shouldnt be an issue with that I hope. Ive also tried wiping the battery stats as well in CWM. It first started when I flashed Syndicate Rom Frozen a few weeks ago. So I have tried several other roms since then and I still have the same problem. I even purchased a new battery and still have the same issue. Im lost in this one. Im not blaming the problem on Syndicate either, I was just letting you know when I first noticed the problem.
Sent from my SPH-D700 using Tapatalk
What happens when you open the keyboard? Does anything light up? Or does it just continue to stay off?
It stays completely off and blacked out when I open the keyboard. I have to pull the battery in and out to get anything.
Sent from my SPH-D700 using Tapatalk
And youve gone completely back to stock without root. No difference?
Also, the kernels that you have run, are they overclock kernels? What about the one your running now? If so, I think they are overclocked from the get go and possibly set for 100mhz on the low end. You might want to try and find SetCPU on the website here, (there is a free one) and set it to raise the speed on the low end. Also add a profile for screen off that changes to 200-400. It would be free and relatively easy to try.
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
dazednconfused1144 said:
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I might be wrong, but I think the newest ViperRom is set by default at 200-1000. To reach the 1200 mark, you have to use SetCPU. Same for going under 200 (which is known to cause problems for some folks when the screen turns off).
I just wanted to say thanks for the help. I wanted to update you and let you know I finally found the problem. For some reason it had something to do with restoring my apps and data through Mybackup Pro and Titanium. I finally just started taking out different steps of what I was doing and finally just downloaded all of my apparently directly from the market and the problem went away. No more blackouts. I don't know why that would cause that problem, but it did. Thanks again for all of your replies and help.
Sent from my SPH-D700 using XDA Premium App

[Q] anyone else notice hot restarts in decks ics a5

I installed decks ICS Alpha 5 yesterday after a full wipe and all the usual stuff like gapps install. I see everyone else talking about the camera issues..it works kinda...lol but I cant use the google search bar on the home screen, if i even tuch it my phone does a hot-reboot, anyone else expirienceing this, also major keybord issues, it just flashes up for a second and goes away everytime i try to use it, are there any fixes for this stuf??
I've been using it since it came out and haven't had that issue.
Did you do a full wipe before flashing it?
KCB5 said:
I've been using it since it came out and haven't had that issue.
Did you do a full wipe before flashing it?
Click to expand...
Click to collapse
I did a full wipe but didnt work, so i wiped it like 3 or 4 times in a row and then flashed, works like a charm
I haven't had any real problems with it, but remember it is still alpha. Anything is still possible
Sent from my PC36100 using Tapatalk

[Q] issues after power off on JB

Very sorry if I missed a fix for this I've looked everywhere and played around for 3 days trying to fix the issue myself... anyways every JB rom I've downloaded and installed for Verizon's gnex gives the same result if my battery goes completely dead I can not boot past the Google screen I can do a pull and load up clockmod but that does nothing wiped everything reinstalled roms on the clean wipe still hangs on Google only way I can fix it is to unroot flash stock and try again I did just say to heck with it I'll just not let my battery drop below 5% and all should be well... well today seemed a little laggy so I though a reboot would help had around 75% battery and it happened so though maybe my phones just special loaded ics back on it rooted and have been trying to make it repeat nothing anyways just wanted to see if this is a issue for JB or if I'm doomed to a life of ICS ?
Thanks for any help and sorry for being long winded
Ahemm...
Vzw gnex? JB? Not sure what you're talking about.. I thought JB is only available on GSM. Isn't vzw an Lte model?
Edit: oh it seems there is a port.
Sent from my i9250
I had the same issue. What I did was wipe using super wipe (on the android HD threads by mike) and then installed the rom again. Now, you need to realize that it is actually NOT getting stuck on the Google logo, you just need to give it time. Everytime I reboot I have to let it sit for a little bit for it to get passed that screen. Try out the Trinity JB kernel, I use it and its pretty good.
Sent from my Galaxy Nexus using xda premium
XfrostX said:
I had the same issue. What I did was wipe using super wipe (on the android HD threads by mike) and then installed the rom again. Now, you need to realize that it is actually NOT getting stuck on the Google logo, you just need to give it time. Everytime I reboot I have to let it sit for a little bit for it to get passed that screen. Try out the Trinity JB kernel, I use it and its pretty good.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1 worked like a charm

Phones freezes several roms

When my phone goes a long time with screen of i.e. overnight on charger, or when its in my pocket for a while when i push the power button nothing happens. The alarm can go off and i have to take the battery out to turn it off. That fixes it every time. But im rocking the otterbox defender and thats a pain in the a** to have to take all that apart. It has happened on ice cold sandwich, jellytime, and blackout ics incredible. The only common denominator is I use pimp my rom, Mostly just to remove adds and touchscreen responsiveness. Has anyone else had this issue? And if i just dirty flash blackout again will i cancel out all those pimp my rom tweaks?
hotrod60 said:
When my phone goes a long time with screen of i.e. overnight on charger, or when its in my pocket for a while when i push the power button nothing happens. The alarm can go off and i have to take the battery out to turn it off. That fixes it every time. But im rocking the otterbox defender and thats a pain in the a** to have to take all that apart. It has happened on ice cold sandwich, jellytime, and blackout ics incredible. The only common denominator is I use pimp my rom, Mostly just to remove adds and touchscreen responsiveness. Has anyone else had this issue? And if i just dirty flash blackout again will i cancel out all those pimp my rom tweaks?
Click to expand...
Click to collapse
It's definitely the pimp my Rom tweak that is causing it. I personally wouldn't sacrifice stability for ad removal. Are you wanting to get rid if it and that's why your asking if a dirty flash will get rid of it? If so I would say give it a shot and if it doesn't work do a full wipe.
Sent from my Inspire 4G using xda premium
hotrod60 said:
When my phone goes a long time with screen of i.e. overnight on charger, or when its in my pocket for a while when i push the power button nothing happens. The alarm can go off and i have to take the battery out to turn it off. That fixes it every time. But im rocking the otterbox defender and thats a pain in the a** to have to take all that apart. It has happened on ice cold sandwich, jellytime, and blackout ics incredible. The only common denominator is I use pimp my rom, Mostly just to remove adds and touchscreen responsiveness. Has anyone else had this issue? And if i just dirty flash blackout again will i cancel out all those pimp my rom tweaks?
Click to expand...
Click to collapse
Yes, I think reflashing the rom, will replace /system and will reverse action of tweaks scripts of that Pump ROM, but sure before do it, make nandroid backup (Titanium Backup)
Sent from my GT-I9100 using Tapatalk 2
Cool ill give it a try and update u guys, I think their is a app in the play store that gets rid of ads anyway.
sent from my Inspire 4g
Well I woke up this morning and the phone was frozen after being on the charger all night. And I actually just clean flashed r27 jellytime bf bed. Flashed inspire mod and gapps and that's it. So I'm now at a loss.
sent from my Inspire 4g
hotrod60 said:
Well I woke up this morning and the phone was frozen after being on the charger all night. And I actually just clean flashed r27 jellytime bf bed. Flashed inspire mod and gapps and that's it. So I'm now at a loss.
sent from my Inspire 4g
Click to expand...
Click to collapse
Might need to erase and format SD card as well to get rid of any other settings. I would try that first before ruling it hardware. Clean everything possible including SD and re flash. Sometimes SD contents from old stuff can keep something from going away.
Sent from my Inspire 4G using xda premium
Gizmoe said:
Might need to erase and format SD card as well to get rid of any other settings. I would try that first before ruling it hardware. Clean everything possible including SD and re flash. Sometimes SD contents from old stuff can keep something from going away.
Sent from my Inspire 4G using xda premium
Click to expand...
Click to collapse
Sounds good. Ill try that now.
hotrod60 said:
Sounds good. Ill try that now.
Click to expand...
Click to collapse
Reply plz
Sent from my GT-I9100 using Tapatalk 2
so far so good, two days and no problem. accidentally deleted all my pictures though. Im gonna say its fixed. Thanks!
Alright so I thought it was fixed. But since flashing r28 jellytime, the problem has come back. The only thing I have done is change the io scheduler to deadline and oc it to 1200. And disable zram. No pimp my rom since the full wipe and sd wipe.
hotrod60 said:
Alright so I thought it was fixed. But since flashing r28 jellytime, the problem has come back. The only thing I have done is change the io scheduler to deadline and oc it to 1200. And disable zram. No pimp my rom since the full wipe and sd wipe.
Click to expand...
Click to collapse
I have read of other users who can overclock just fine on gingerbread having stability issues with lower clock speeds like 1200mhz on ics and jb. Also not everyones device can handle certain settings. Best way to see if its your phone or hardware would be to run stock rooted and if it happens on stock with no tweaks then its your hardware. When you get into the realm of custom roms on the edge of development and adding tweaks to the mix, then your pushing your device to untested specifications. Some will experience issues and some will not. It's a gamble really. Same reason why some people are affected by bugs and others aren't on the same device. There are definitely variations in hardware. Since it went away until you installed JB I would narrow it down to that version possibly or maybe the clock settings.
Sent from my Inspire 4G using xda premium
Alright Ill start with setting the clock back and going from deadline to sio instead. if it still does it Ill jump back to a stock rom. Thanks.

4.2.2: Bluetooth won't turn on

OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
wbexpress said:
OK, I have Odin'ed twice, and wiped the poor little phone so many times I'm gonna need to use Desitin. It does not matter, I have pretty much tried every 4.2.2 ROM out there, and although I have had one or two that I could initially get bluetooth to turn on, even those would fail to do so after a few hours. I've tried rebooting with it on, rebooting with it off, does not matter. The last few AOKP and CM nightlies as well as Jedi, it will not even turn on. I have seen a few folks state somewhat similar issues, but I am getting that it is not pervasive for the community. Does anybody have any ideas as to a fix, or, even any ideas as to what causes it, so maybe I can play around with whatever and try myself? Or, best case-scenario, did anybody have the issue on ROM ABC and discover that by switching to ROM XYZ it was fixed? I'm not updating my sig because it changes multiple times a day anyway, but I am back to CWM 6.0.2.7 from TWRP if that variable matters at all. Same situation whether on stock, Cerux or ASD kernel.TIA...
Click to expand...
Click to collapse
I works on the 2/26/13 Nightly of CM10.1. You wanna try and clean flash it? If it doesn't work then it's just a problem with your phone hardware instead of the software. Might be a buddy bluetooth adapter or such.
zxstyle07 said:
it turns on with pac 20.0 not sure if it stays on though. I'm on the latest twrp. full wiped, adsk and nos script. give that a try?
Click to expand...
Click to collapse
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Yup, this helped for my JB-MR build 4!
no more having to reboot to enable bluetooth
wbexpress said:
Fingers crossed, so far so good. I reinstalled Rootbox which is awesome. I changed from CWM back to TWRP and also installed Cerux 1.42 which in the thread made mention of the bluetooth issue being fixed, and being kernel, not ROM related. I am using crossbreeder which makes things crazy fast. I saw the "nos script" in some thread but couldn't find it with a Google search. Do you have a link for it and what exactly does it do?
Edit: Crap. it went away. Oh well, back to 4.1. Hellybean it is. I just don't get it. BT works fine on any 4.1 or ICS ROM. Only thing with 4.1 is music skips in my music player but I can live with that, I can't live with no BT. Thanks for your help. Maybe when source drops it will be all good.
Click to expand...
Click to collapse
http:// http://forum.xda-developers.com/showthread.php?t=2158329
joeyrey said:
Does ithe bt button turn on then instantly off when you press it? This happened to me and i went into recovery and wipe dalv n cache.. Worked perfectly after
Or i saw this post. Not sure if itll help
http://forum.xda-developers.com/showthread.php?t=2174100
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Well, what seems to happen is it is fine for 15-30 minutes after I've freshly installed the ROM, then it just turns off. When I then try to turn it back on it hangs at "turning on" and then goes back to off. At that point when I click "turn on", it doesn't even move. I'm a gonna try the fix, nothing to lose at this point...
Nuts. It fast moves to on and immediately goes back to off. White flag, thanks to all.
Apply the fix and delete all you devices then try turning it on and off with nothing on it...if it works then add devices one by one...if you have devices married to it the patch might not work also I think my computer dongle was the culprit
Sent from my SAMSUNG-SGH-T989 using xda premium
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
wbexpress said:
Yeah, how about that. I can't see that it's hardware-related, it's perfect on 4.1.
Click to expand...
Click to collapse
Your exactly right...
Sent from my SAMSUNG-SGH-T989 using xda premium
djtheraven said:
After a reboot I'm back to the same problem
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
wbexpress said:
If you ever figure it out, please put something here. I keep looking every so often, I have to believe enough folks are having the issue that eventually someone is gonna fix it. Thanks...
Click to expand...
Click to collapse
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
bluetooth issues
djtheraven said:
I'm posting to a couple of devs hope they can get it...the problem was people were commenting that it worked when they had no Bluetooth device hooked up...if you uninstall all devices then bt will toggle on and off...so they thought it was working when it wasn't...
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Not a perfect answer...
RandyToe said:
Has anyone had any luck with this? I've tried various combinations of different 4.2.2 roms and kernels and have the same issues described in this thread with all of them.
Click to expand...
Click to collapse
I found one thing that at least gets it working again without rebooting is to activate airplane mode. Its faster than rebooting. Wish I had a better answer...

Categories

Resources