[Q] Having Poke Lock issues on CM7/OMFGB - Fascinate Q&A, Help & Troubleshooting

While running either CM7 or OMFGB (Dailies or releases) - after I have a phone call, when I run "dumpsys power" in the terminal, I get the following message:
poke lock 'PhoneApp': POKE_LOCK_IGNORE_CHEEK_EVENTS
When I restart the phone, the poke lock won't be there until I receive another phone call. Is there a better solution to this issue, than restarting the phone after every phone call? The main adverse effects of this poke lock is that my phone's stand by becomes between 40-60% of battery used, as opposed to about 5% and drains the battery. I just can't seem to clear this poke lock.

Anybody have experience with solving this problem?

having the same problem. no idea how to solve

alemondemon said:
Anybody have experience with solving this problem?
Click to expand...
Click to collapse
Damn that sucks to see your still having this issue
Have you tried to re odin eb01 with the atlas 2.2 pit, then fully reboot.(I let it go through the setup a screen just skipping everything but I get to the home screen before preceding)
Odin 3/30 fix all recovery and immediately flash com rom 2.0...let that boot fully.
Then flash cm7 the way you did before, Then continue to flash your kernel, gapps and whatnot via power button recovery only
I know its a p.i.t.a. and a lot of unnecessary steps but that is what worked to get rid if my poke lock.
I hope this helps cause with the poke lock your battery level must suck...I hope you get it fixed to enjoy cm7 goodness.
Sent from my SCH-I500 using XDA. App

Related

[Q] Wifi Error after EB01 Froyo Upgrade

Since upgrading to the EB01 Froyo leak (debinged/deodexed) I have wifi issues where every 3 or 4 times I attempt to enable it, it will fail, and show "Error" under the Wi-Fi settings (where it ususally says in blue text "Turn on Wi-Fi", "Connecting..." "Connected to <network>", etc). I finally got the log message associated with it, and was wondering if anyone has figured out a way to address this?
From what I gather insmod is the kernel's mechanism for (in this case) loading the wifi driver, so this would be an issue with the kernel? So now what?
E/WifiHW ( 2467): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1) : ret = -1, Invalid argument
At first I thought a reboot was necessary to get it to attempt to reload the driver, but I've since found clearing level 2 ram in the task manager does the trick. Still a big PIA though.
Thanks for any help.
Kidd_Funkadelic
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
AlgorithmX said:
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
Click to expand...
Click to collapse
So, if I'm not mistaken I can just install the non-voodoo zip w/ Red CWM directly over EB01 with no wiping/cache clearing, etc, and be up and running with no data or configuration loss? Sounds like a pretty quick and easy way to fix my issue.
I haven't been following the EC10 thread, but I just took a look and looks like the static issue when the screen comes on during a call is fixed as well, the only other issue I've had.
Guess I may have to give it a shot! How long have you been using it?
KF
I've been using it for a couple days and have to say that it combined with SuperClean 2.9 has made my phone super smooth. I haven't found a single glitch so far.
Took the plunge and updated to EC10 last night. I've had only a brief time to play around with it, but so far so good with the wifi. Thanks for the help!
Could just be my mind playing tricks on me, but I could swear in general everything is more responsive as well... Not only loading apps, but when I brought up navigation this morning I've never once seen it lock on and start driving directions this fast.
Nevermind... Same problem still with EC10. Got my hopes up there for a minute.
I got the same problem with SC 2.9.2v and had with any other SC Froyo build. I'm using JuiceDefender so WiFi is turned on/off lot of times (every 15 minutes on schedule or when screen is unlocked). Usually once or twice a day I find that there is an error with WiFi and the only way to fix it is to wait couple of minutes and try turning it on manually or switch to airplane mode on/off.
I also use JuiceDefender w/ Wifi. If it doesn't occur less often with EC10 (too soon to tell still), I'll have to disable the wifi controls in JD so it's toggled on/off far less frequently.
Glad to see I'm not the only one seeing it. I bet the JD users will just notice it more since we are loading the wifi driver all the time.
Kidd_Funkadelic
And thanks for the airplane mode tip- I'll have to try that. I was clearing level 2 ram in task manager to do it. AM would be slightly more convenient.
jt1134's source build EC10 didn't help, still having same problem with WiFi. My log is showing the same thing.
At least the new kernel fixed the static issue. One thing at a time, right? I hope that this means there will be ED01 kernel drop
Actually, maybe April Fool's day is a bad choice...
What radio are you using? EB01?
Yes, I did the full Froyo update to EB01 over the stock 2.1 Verizon eclair, then installed the EC10 specifically for this issue. That's all I've done. Oh, went back into CWM after seeing the problem for a few days to clear the Dalvik cache. That's all I've done to date...
OK so it's not radio related but kernel/rom then. I'm on EA28 radio cause I had problems with missed calls with EB01.
Solutions? Bump?
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
jbjcurly said:
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
Click to expand...
Click to collapse
I was able to get rid if the problem by using Auto Killer Memory Optimizer. It turned out to be a memory issue. Use one of the preset profiles, like aggressive, and see how you do. I was having the problem several times a day and it never came back.
Or, upgrade to PWGB, which takes care if the problem too and doesn't require messing with memory mgmt settings...

[Q] Process com.android.phone is not responding

When I try to make phone calls (even to voicemail), my screen goes black except for the status bar, my phone vibrates a bit, and then I get a message that says "Sorry! Process com.android.phone is not responding." With an option to either force close or wait. I tried a factory reset, yet the problem remains. Any suggestions?
Samsung Fascinate on Verizon
What ROM you running? Modem? Kernel? Or is this a stock phone (If so what version of software)?
spartymd said:
When I try to make phone calls (even to voicemail), my screen goes black except for the status bar, my phone vibrates a bit, and then I get a message that says "Sorry! Process com.android.phone is not responding." With an option to either force close or wait. I tried a factory reset, yet the problem remains. Any suggestions?
Samsung Fascinate on Verizon
Click to expand...
Click to collapse
"Tried a factory reset" how did you do that? Sounds like your on a stock rom?
Sent from my SCH-I500 using XDA App
Sounds like you need to start fresh and odin a stock rom w/ pit file.
droidstyle said:
Sounds like you need to start fresh and odin a stock rom w/ pit file.
Click to expand...
Click to collapse
x2
Sent from my SCH-I500 using XDA App
spartymd said:
When I try to make phone calls (even to voicemail), my screen goes black except for the status bar, my phone vibrates a bit, and then I get a message that says "Sorry! Process com.android.phone is not responding." With an option to either force close or wait. I tried a factory reset, yet the problem remains. Any suggestions?
Samsung Fascinate on Verizon
Click to expand...
Click to collapse
Weird, I had this problem, but mine was specific to one contact. ALL other contacts numbers I dialed, either useing 7 or 10 digits, in either stock or Go Dialer, would work just fine.
When I would try to call my work, it would crash. It was only my work number and it sucked. Cause I'm in school, and deliver pizza on weekends, and when you can't call the store it sucked at times.
It was stock froyo, voodoo stock kernel. Reset fixed it.
droidstyle said:
Sounds like you need to start fresh and odin a stock rom w/ pit file.
Click to expand...
Click to collapse
Thank you for your responses so far. To be honest though, I don't really have any idea how to do any of that. My phone is not rooted, although now I am strongly considering it. However, there seems to be an overload of information on how to go about doing it and different methods that don't seem to always work. Also, I don't know how to find the "stock" ROM. Do you guys have any links that you would recommend as being helpful? Sorry for being such a newb.
Read these three links they will give you good info and all the links for the stuff you need..
http://forum.xda-developers.com/showthread.php?t=1124391
http://forum.xda-developers.com/showthread.php?t=1238070
http://forum.xda-developers.com/showthread.php?t=1212239
Sent from my SCH-I500 using XDA App
Alright I used the steps listed in the top link that you gave me to odin the stock rom and pit file, but it did not solve the problem. An example of my problem is when I try to call my voicemail, I'll sometimes hear the automated response voice asking for my pin#, but the dial pad doesn't show up as normal for me to type it in. And the screen freezes up for a minute or so until the call ends.
Another possibly related problem is that when I push the power button to turn on the screen, it doesn't turn on for about 5 seconds, whereas it normally turned on right away. This all started after I put some music (about 30 songs) onto the SD card and deleted a few files that I thought weren't important (but maybe they were?).
Which stock rom did you use to start fresh with the pit file and what rom are you on now?...just want to make sure you did everything correctly because a pit file and stock flash should eliminate any of you force close issues...unless when you went back to whatever rom you're on now you and
Might have missed a step...what rom did you use to flash along with the pit file? And what is the rom you want to be on when all is said and done?
Sent from my SCH-I500 using XDA App
I used the ED05 FROYO rom, and I assume that's the one I'm still on. I did everything as listed up until the in step five because I don't have a recovery to odin. If I was supposed to keep going after that point, then I'll try it again, but it seemed like I could probably stop as long as I didn't mind having the stock rom. I'm alright with the stock rom for now as long as my calling starts working again.
If you want to stay stock then you did what you were supposed to, that's why your messaging is back and running..if you do ever want to switch rom. Follow those same instructions but complete step 5 and use the recovery that is suggested for the rom you want to flash. Odin that recovery and boot immediately into recovery with the three finger method and follow the roms instructions to flash your new rom.
Sent from my SCH-I500 using XDA App
The problem is not resolved. I first used the stock rom, and then I tried the powerwashed rom. My two problems still remain:
1. Screen still takes about 5 seconds to light up when I hit the power button (when phone is on)
2. I dial voicemail, but as soon as I do, the screen goes blank and I don't hear the response until about 10 seconds later when the voice says "please try again later" and it hangs up. Sometimes the screen doesn't go blank, but it freezes up and I am unable to dial my pin #. This situation also occurs when I call other numbers, although if they stay on the line long enough, eventually it will work. Sometimes it causes a force close, but not always.
So since I've tried starting over with the stock rom, and that hasn't solved the problem, is it possible that this isn't a software issue?
If you've Odined back to stock ED05 and it hasn't been resolved you can probably get Verizon to send you a CPO replacement (assuming you still have warranty left).
Sent from my SCH-I500 using XDA App
spartymd said:
The problem is not resolved. I first used the stock rom, and then I tried the powerwashed rom. My two problems still remain:
1. Screen still takes about 5 seconds to light up when I hit the power button (when phone is on)
2. I dial voicemail, but as soon as I do, the screen goes blank and I don't hear the response until about 10 seconds later when the voice says "please try again later" and it hangs up. Sometimes the screen doesn't go blank, but it freezes up and I am unable to dial my pin #. This situation also occurs when I call other numbers, although if they stay on the line long enough, eventually it will work. Sometimes it causes a force close, but not always.
So since I've tried starting over with the stock rom, and that hasn't solved the problem, is it possible that this isn't a software issue?
Click to expand...
Click to collapse
Okay I have one last resort to try and I don't know if it would make a difference but it works for me if I ever have an issue I can't figure it out.
Open Odin, remove your battery and put your phone in download mode.
click the pit button and select the atlas 2.2 pit file.
Click the pda button and select the EB01 VZW file.
Make sure the repartition box is checked and click start.
When Odin is done , insert your battery and reboot your phone and you'll be on eb01 modem and all...run that for a day and see if you have the problems with your voicemail, and your screen. if you don't we'll go from there on getting you off of stock if you desire...links to follow in a minute...but I think this will fix your issues
VZW eb01...
http://www.multiupload.com/ZLPQAS8JA0
2.2pit...
http://www.mediafire.com/?31u1g1ef05jvebd
Place both of these files on your PC in your Odin folder and follow the directions I wrote and see how its goes
Sent from my SCH-I500 using XDA App
Just be sure if you do try this with EB01 and it doesn't fix it and you do try to get a replacement from VZ to reodin it back to ED05 before returning it.
Sent from my SCH-I500 using XDA App
scarfman4 said:
Just be sure if you do try this with EB01 and it doesn't fix it and you do try to get a replacement from VZ to reodin it back to ED05 before returning it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Agreed..good call
Sent from my SCH-I500 using XDA App
Unfortunately that doesn't seem to have solved the problem. So I guess the next option is to bring it in to try and get a replacement?
Thanks for your help.
spartymd said:
Unfortunately that doesn't seem to have solved the problem. So I guess the next option is to bring it in to try and get a replacement?
Thanks for your help.
Click to expand...
Click to collapse
Yup, just Odin back to stock ED05 so they won't know you rooted. If they ask why it is wiped tell them you did it as a troubleshooting step (which is true).
Sent from my SCH-I500 using XDA App

[Q] Partial Wakelock from GPSLocationProvider (ICS Passion v13)

I am currently running ICS Passion v13rc1 w/ flashed cleanup:
If I boot my Vibrant I can get deep sleep normally; however after I've opened my maps with GPS on I can no longer get into deep sleep. BetterBatteryStats shows that the partial wakelock is due to GPSLocationProvider; and the only way to get back to deep sleeping is to reboot my phone.
I've tried turning off the GPS & all the things in the Locations settings. I just flashed from Odin -> CM7 (wait 10 minutes, reboot) -> v13rc1 (wait 15 minutes, reboot) -> cleanup (wait 15 minutes, reboot) -> update SU. The GPSLocationProvider only starts to show in partial wakelocks and burn battery after I've opened the Maps app.
I've looked through the Passion v13 thread and have only seen this come up in one post (from back in v10, where the user said that rebooting after using the maps was the only way to get back into deep sleep).
Has anyone else ran into this problem and figured out a way to remedy (without having to restart everytime you open up the map)?
I have the same problem, and the only way I've figured out to fix it is with a reboot. Still searching for a better solution.
I have the exact same problem, don't know how to fix it.
Sent from my SGH-T959 using Tapatalk
nerujin said:
I am currently running ICS Passion v13rc1 w/ flashed cleanup:
If I boot my Vibrant I can get deep sleep normally; however after I've opened my maps with GPS on I can no longer get into deep sleep. BetterBatteryStats shows that the partial wakelock is due to GPSLocationProvider; and the only way to get back to deep sleeping is to reboot my phone.
(without having to restart everytime you open up the map)?
Click to expand...
Click to collapse
GPS does not work for me. Eats battery too.
I have been trying to get my GPS to stop using Network and only use GPS. I have the exact same issue you have, but I have to reboot to get GPS to work again. I had to stop Data, reboot for the GPS to operate on GPS instead of network. Once I use Map, it converts my GPS to Network and I am done. Reboot for GPS to work. And yes I tried everything except the hardware hack.
Formatted the system/data/cache etc etc and reinstall from scratch. I cannot use the *#*#DIGITS#*#* to get into the LBS Menu. Does not work after the upgrade to ICS, too bad.
Anyways, any help with this would be appreciated. I know its a bit differnt than your issue, but its soo close because IF I could restart the GPS without rebooting, I would be happy with the Passion build very much!
Vibrant
ICS Passion 13rc1
goolifeus said:
GPS does not work for me. Eats battery too.
I have been trying to get my GPS to stop using Network and only use GPS. I have the exact same issue you have, but I have to reboot to get GPS to work again. I had to stop Data, reboot for the GPS to operate on GPS instead of network. Once I use Map, it converts my GPS to Network and I am done. Reboot for GPS to work. And yes I tried everything except the hardware hack.
Formatted the system/data/cache etc etc and reinstall from scratch. I cannot use the *#*#DIGITS#*#* to get into the LBS Menu. Does not work after the upgrade to ICS, too bad.
Anyways, any help with this would be appreciated. I know its a bit differnt than your issue, but its soo close because IF I could restart the GPS without rebooting, I would be happy with the Passion build very much!
Vibrant
ICS Passion 13rc1
Click to expand...
Click to collapse
Same here GPS won't start, nothing helps until I reboot.
please help
Install the new kernel for Passion. It fixes the GPS DS issue. http://forum.xda-developers.com/showpost.php?p=22733142&postcount=10214
andrediener said:
Install the new kernel for Passion. It fixes the GPS DS issue. http://forum.xda-developers.com/showpost.php?p=22733142&postcount=10214
Click to expand...
Click to collapse
F**k ME this kernel is awesome it fix the GPS problem and my battery last for almost a day
thank you thank you thank you
I was too quick to celebrate. after a grate week the problem has returned, battery gets eaten and GPS won't wake.
having the same problem on cm9 with glitch installed.
yagf2-GPS Fix for ICS
I had the GPS problem where it would not work after installation of v13rc1. To solve the GPS problem, I used the following: yagf2-GPS Fix for ICS.zip. After flashing this, my GPS worked with no issues, no battery or sleep issues.
I hope this helps.
I found that a lot of the battery drainage, inability to go into deep sleep for me has been from 2 sources of partial wake lock.
1. GPSlocationprovider
2. Mediascannerservice
I found that 2 apps that are fairly common that cause the wake lock on the GPSlocationprovider has been official facebook app and google maps. I can easily uninstall facebook and never use it again, but unfortunately can't go without google maps...
Also found that freezing DRMcontent... service using titanium backup stops the mediascanner wakelock from occuring, but with each reboot of the phone, I need to defrost and then freeze the service again, in order to stop the wakelock.
I'm running AOPK Build 28 with Kiss 5.1 kernel.

[Q] Problem with options, home and search buttons

Help! I am currently running GeeWiz 2.6 but after 1-2 reboots my option, home and search button all stop working.
My back button still works and it hasn't been just in GeeWiz that I have experienced this issue, I have had this problem in both TSM and Superclean (which are basically the same but still).
This is weird but if anyone knows help!
Update 02/22/12 : The problem has gotten worse now all my buttons except for the back button don't work on 2.3 gingerbread stock that is flashed in Odin! I will flash 2.1 and 2.2 to see if anything works.
I had this same issue when I first bought my Fascinate. Is your phone in airplane mode? If it is, try disabling it and restarting. That should fix your problem.
I always have my phone in airplane mode seeing as it isn't even activated with verizon, I use alot of Voip so I shut of 3G to save some battery. It seems to have fixed my issue on stock, im going to ty this out with CM9 and see if it works but so far thanks dude!
No problem. As long as you remember to switch off Airplane mode before, or shortly after, rebooting, you should be okay. It's related to the Activation Screen, so this problem should go away entirely if/when you activate your phone.

[Q] NRG blue theme 6/21 Black Screen after Call

I am using the HTC Amaze Energy ICS Rom latest 6/21 update without any modifications to the kernel etc. I love the rom but every now and then, the screen gets black after initiating a call. The only way to fix that is by taking off the battery and replacing it.
I tried looking for a fix around XDA but could not find a fix.
Any recommendations on how to fix this issue will be greatly appreciated.
Thank you.
Black screen
Try setting the lower cpu freq to 384. I found no frills cpu controller simple and works great.
There are quite a few posts regarding this issue.
Hi,
Sorry to jump aboard your thread with almost the same question.
I been using this rom since almost came out, I went throught all the different updates without any issues I installed the 8/6 version on that same date and not until now I'm experiencing this black screen issue but mine is not after a call, it's everytime the screen goes to sleep then it's a paint to get it awake again I'm starting to hate this phone.
The issue seems to have started after I travelled to a different country and I used a prepaid sim.
Came home and the phone started to act weird I re flashed the rom but since I was restoring data from a recovery (4ext) backup seems to drag whatever errors were there so since I didn't want to lose all my games scores and data I did a backup/restore with Titanium but even though all the other issues are gone the black screen stayed.
The CPU is already set @ 384 so that is not the issue and as I said it happens when the screen goes to sleep (not during calls) either by itself or if I do it myself.
When I press the on button (or the camera one) to wake it up only the four buttons on the bottom light up.
Any help?????
Thanks,
ferincr said:
Hi,
Sorry to jump aboard your thread with almost the same question.
I been using this rom since almost came out, I went throught all the different updates without any issues I installed the 8/6 version on that same date and not until now I'm experiencing this black screen issue but mine is not after a call, it's everytime the screen goes to sleep then it's a paint to get it awake again I'm starting to hate this phone.
The issue seems to have started after I travelled to a different country and I used a prepaid sim.
Came home and the phone started to act weird I re flashed the rom but since I was restoring data from a recovery (4ext) backup seems to drag whatever errors were there so since I didn't want to lose all my games scores and data I did a backup/restore with Titanium but even though all the other issues are gone the black screen stayed.
The CPU is already set @ 384 so that is not the issue and as I said it happens when the screen goes to sleep (not during calls) either by itself or if I do it myself.
When I press the on button (or the camera one) to wake it up only the four buttons on the bottom light up.
Any help?????
Thanks,
Click to expand...
Click to collapse
I had the exact problem.
I fixed this by reflashing my rom but there was another way i fixed this as well. A much easier way is just to download the Market App 'Pimp My Rom' . Theres a feature in that app, that fixes this exact problem.
Thanks a lot!
I got it. It looks good (and scary for a noobie)
Is there anything I need to tweak in there or just installing it would take care of it?
Thanks.
Edit: I found "no black screens after a call" under miscellaneous should I tick that one? even though my problem is not specifically after a call?
ferincr said:
Thanks a lot!
I got it. It looks good (and scary for a noobie)
Is there anything I need to tweak in there or just installing it would take care of it?
Thanks.
Click to expand...
Click to collapse
You have to do something specific inside the app.
I'll give you a step-through-step guide so you can fix this annoying problem!
1. Download the free app!
2. Open the app
3. you'll see tabs, "Main menu, tools, tweaks, Apps & mods, extras, and help center". go to the TWEAKS tab.
4. Then you'll see 7 categories. "Network & internet , multitasking,Dalvik VM, Kernel tweaks, Enable/disable features, Telephony, and Miscellaneous tweaks" SCROLL DOWN AND CLICK ON THE MISCELLANEOUS TWEAKS category
5. Scroll down till you see "No Black-Screen after a call" , then tick the little box to the left of it.
6. Scroll down and click on "Apply Selected Tweaks"
7. It'll ask to reboot, but unfortunately the reboot button the app gives you doesnt reboot the phone, so reboot your phone manually after you did step 6.
8. you're DONE
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
ferincr said:
Edit: I found "no black screens after a call" under miscellaneous should I tick that one? even though my problem is not specifically after a call?
Click to expand...
Click to collapse
Yes, the fix worked for me , and mine wasnt after the call.
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
ferincr said:
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
Click to expand...
Click to collapse
Any time
ferincr said:
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
Click to expand...
Click to collapse
Have you succeed to resolve your problem. I have something similar on a Stock Rom. I have described my problem in this thread.
zandgreen said:
Have you succeed to resolve your problem. I have something similar on a Stock Rom. I have described my problem in this thread.
Click to expand...
Click to collapse
I think he did, the app basically does what your fix does
kevinrubio1 said:
I think he did, the app basically does what your fix does
Click to expand...
Click to collapse
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
No I haven't solved it. But mine is not after a call it's when the screen been off for a while.
Yesterday after a total software corruption (it wouldn't even boot) I went to stcok (again) and started from zero. Worked well for few hours and this morning I was back with the spolied brat phone.
So, I'm testing stock RUU for a full day today and see what happens.
Try to catch some log when the phone begins to behave badly.
zandgreen said:
Try to catch some log when the phone begins to behave badly.
Click to expand...
Click to collapse
???
No idea how to do that.
But I'm very confused...
I read in few ocasions that if your bootloader is unlocked you cannot flash the stock RUU.
In my case is the other way around, actually now I'm running the stock Tmous rom with unlocked hboot, S-OFF and rooted (and so far the phone is working ok) no black screen so far.
What the hell is wrong with it. It has to be something I do when I flash ROM, Kernel or Hboot...
I'll stay like this until tomorrow to see if I do get black screens at any point.
ferincr said:
???
No idea how to do that.
But I'm very confused...
I read in few ocasions that if your bootloader is unlocked you cannot flash the stock RUU.
In my case is the other way around, actually now I'm running the stock Tmous rom with unlocked hboot, S-OFF and rooted (and so far the phone is working ok) no black screen so far.
What the hell is wrong with it. It has to be something I do when I flash ROM, Kernel or Hboot...
I'll stay like this until tomorrow to see if I do get black screens at any point.
Click to expand...
Click to collapse
You can't flash an RUU with a locked bootloader, UNLESS you are s-off. That's y u were able to
sent from my
NRGized amaze
powered by Faux
Ohhhh!
Ok Now I feel better. I didn't know what to make of that statement.
I thought I was either doing something wrong or totally misunderstanding the lingo.
ferincr said:
???
No idea how to do that.
Click to expand...
Click to collapse
Use aLogcat app from the Play store.
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot,since the restore changed rom and kernel but not the Hboot.
I restored a backup of a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll look for that app

Categories

Resources