I have had VirusRom installed for about a week now. Overall I love it.
Here is my problem though. When I am making a call the screen will lock. I have to push the power button to bring back up the screen in order to hang up the call.
Shouldn't the proximity sensor know when I pull it away from my face so I can hang up the call? It did before I went to this rom, was still using stock rom at that point.
Anyone know of a way to fix this problem? I have tried to post this question on the VirusRom forum, Since I think it is a bug with the rom, but am not allowed. It says you need 10 posts to be able to do that, Still I get that too even though I am over ten posts. Oh well on that though.
This could be a deal breaker for me and VirusRom. As it is quite frustrating to me. If anyone has any thoughts on how to get around this I would be thankful.
It's due to the kernel Virus installed in teh rom. It's one of Ziggy's first kernels and it has a bug that prevents the screen from turning on after/during a call as you describe.
Fix: Install a new kernel.
There are several on here to use, or you can search PPCGeeks / Ziggy to find his new kernels, which he has now fixed the proximity sensor issue.
Thanks for the answer. I downloaded kernal manager from the market. Any specific recommendations for a kernel? Adrynalyne's seem to be the most stable, but maybe I should stick with a stock kernal.
You can't go wrong with one of Adry's kernels. You should start with one those.
Sent from my BAMF'd T-Bolt
I had the same problem. I installed the new radio which was supposed to fix it and it did. But Im having trouble with the data connection, so I flashed back to the stock radio.
Ziggy's new kernal upgrade has fixed this issue. Id suggest downloading that. It works great and super crisp and fast over the version that came with the ROM and the proximity issue is fixed, been testing it for myself and all is good.
Check the VirusRom thread for info.
Ok, So I flashed one of Adrynalyne's kernals and now I don't have 3g or 4g. Just 1x. So do I flash another kernal, maybe the stock one, and the problem is solved? That will put it back the way it was right?
nope that did not work, I flashed Adrynalyne's stock rom and still just 1x. What have I done? What do I need to do to put it back? SInce I keep rom backups everytime I flash a ROM, I am going to flash back to the previous version that did have 3g and 4g working. I hope that works. The kernal is part of the ROM, correct?
Now this is getting frustrating. Flashed back to the previous working virus rom the one I had before the kernel update, and it still is only 1x. Wouldn't the kernel be part of the rom? Why did this not work? What can I do now?
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Use Adrynalyne's kernel
http://forum.xda-developers.com/showthread.php?t=1024338
I use the 4.3 and it runs perfectly fine and the prox sensor works, his are in Kernel Manager also so it will be an easy fix.
oscar615 said:
Ok, since the rom is not the problem3g/4g problem, I reflashed the kernal to ziggy's updated kernal. And that did not solve the proximity sensor problem. I still have to unlock the screen to hangup the phone. Kind of strange I think, since that was supposed to be one of the fixes in the kernal.
Any thoughts on this?
Click to expand...
Click to collapse
verizon 3g might still be down?
Related
I've never really had problems with cam scanner before and I installed this rom by odining stock and then flashing bionix and i did this about 4 times to try to get this to work. I have installed the camera fix that they just posted and i still have this issue. Anyone willing to try and see if they have the same problem?
Me too
not only camscanner being forced closed, but also fxcamera on my Bionix-v 1.3
but there is no problem on Bionix-v 1.2.1
anyone can solve it? thanks.
Me three...camcard causes my phone to reboot.
Ditto, camscanner reboots the phone every time I snap a photo and then press the ok or cancel buttons. 1.3 with fix.
I have the same problem. I guess I have to go back to the previous version since I need to use the CamScanner. I hope some one will come up with a fix. Thank you.
IIRC, it's a problem with the kernel used. I never had camera issues, just mic and that was fixed with OverStock1.1. I believe if you update to the current one (OverStock1.3 now, I think), your camera should be fine after that.
Oniyuri said:
IIRC, it's a problem with the kernel used. I never had camera issues, just mic and that was fixed with OverStock1.1. I believe if you update to the current one (OverStock1.3 now, I think), your camera should be fine after that.
Click to expand...
Click to collapse
Have you personally tried? Ill test it out in a bit unless someone else has already tried this. Thanks for the suggestion
Nirmalspeed said:
Have you personally tried? Ill test it out in a bit unless someone else has already tried this. Thanks for the suggestion
Click to expand...
Click to collapse
Well, it seemed that the origin for the problems that appeared in the initial release was with the kernel (which was Overstock1.0). I never had any issues with my camera like some ppl had reported in the thread (Som did say that was a hit or a miss issue and I guess it missed me thankfully). My issue was with my mic not working with my headphones and that was solved by updating the kernel (like Som said before he posted the fix). Check out cmenard's OverStock thread in the dev section, I'm pretty sure a ton of ppl have already submitted lots of feedback on the newest kernel.
Yea the new kernel update fixed the problem. I believe both overstock and CWK have the fix working.
i tried it and it worked 4 me...
i am presently on bionix v 1.3 with the latest overstock 1.3 kernel and it has cleared up my camera problems!
trying bionix v 1.3.1 next but still checking out 1.3 for now...
Here is what is going on, I flashed a new kernel last night to correct a problem with the VirusRom's proximity sensor. It was one of Adrenalin's ROMs. And my 3g/4g stopped working. Only 1X. This morning I flashed a different kernel, his stock ROM, to try and get it my 3/4g back. That did not work.
Then I flashed a previous backup of VirusRom, one that 3g was working, thinking that would fix the problem. It did not either.
Why did that not work? Isn't the kernel part of a ROM? Also what do I need to do get the 3g/4g working again. I keep good backups and could flash back to stock. Would that work?
oscar615 said:
Here is what is going on, I flashed a new kernel last night to correct a problem with the VirusRom's proximity sensor. It was one of Adrenalin's ROMs. And my 3g/4g stopped working. Only 1X. This morning I flashed a different kernel, his stock ROM, to try and get it my 3/4g back. That did not work.
Then I flashed a previous backup of VirusRom, one that 3g was working, thinking that would fix the problem. It did not either.
Why did that not work? Isn't the kernel part of a ROM? Also what do I need to do get the 3g/4g working again. I keep good backups and could flash back to stock. Would that work?
Click to expand...
Click to collapse
wow you have to do some reading...there is a whole thread on here about 3 and 4g not working NATIONWIDE....it is a Verizon problem!!!
No time frame when it may be fixed..it is not YOUR phone......it is EVERYONES PHONE
http://forum.xda-developers.com/showthread.php?p=13252048#post13252048
4G LTE is currently down nationwide, apparently its been out since sometime last night. Verizon hasnt said much about it other than the fact that they are working on a fix. Im guessing it has something to do with the new 4G Samsung phone being released tomorrow, but I could be wrong.
ok, thanks. Sorry I did not see that thread.
Reboot and 4G back up in Phoenix.
Sent from my ADR6400L using XDA App
So after updating to the 1.2BL and installing illuminate 1.5 i had noticed that my tab would not wake up after going to sleep. I had to hold down power and fully restart the device in order to get it going again.
I assumed it was because of illuminate so i wiped data/cache/dalvik and reinstalled with no luck. So i decided to wipe everything including system, repartition and then reinstall....still no luck. After updating to 1.6 and 2.0 with the same problem i figured I'd try bottle of smoke..... Well the same issue remains.
The tablet goes to sleep, and then will not wake up again with out a restart.
I had zero problems when i was on 1.1 and running other roms including stock, tnt lite, vegan tab and CM7/CM7 nightlies.
Installing a wifi lock app stops the device from sleeping and fixes the problem. However that isn't a permanent fix. I'm not sure if the problem is related to the 1.2 bootloader or Honeycomb.
Is anyone else having the same issue? Any ideas on a fix?
edit: also adjusting overclock settings doesn't make a difference
I am not sure on how to fix this, but since the Honeycomb ROMs are still in Alpha (which means they are still in development) it is most likely the ROM, or it may be just your specific G-Tablet reacting weirdly. I would suggest, if its that big of a problem, to switch to a new/different ROM and wait until they have Honeycomb stabilized. Hope this helped
(actually responding here as I got PM'd as well) I don't really know this ROM too heavily since it's not mine, but even the HC alphas have differences as far as the kernels in use are concerned. It could just be a "known issue", but you might be better off posting to the modders dev thread or PM'ing him to be sure. I haven't heard of this issue, but again I don't scan his thread heavily.
What I can tell you is that sleep of death (SOD) issues have occurred on Froyo ROMs for a long time. It's one of the things that custom kernels attempt to minimize.
Thanks for the response mate. I actually switched from illuminate over to bottle of smoke because I thought the rom may be the issue. But I'm still having the same problem
Sent from my DROIDX using Tapatalk
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
roebeet said:
SOD is one thing I can't replicate on BoS, at least with my minimal testing. It was a big problem for me on the 4349 stock kernel - so much so that I started using custom kernels on TNT Lite (first) and then later on Mountain Laurel.
Click to expand...
Click to collapse
yeh i haven't heard of anyone else having the same issue. At least not with honeycomb roms. I'll see if i can pull some logs to see if i can see anything from that
interesting update on this.
I nvflashed back to bootloader 1.1 with the stock tap n tap software.
Wifi turned off, and the tab wakes from sleep just fine like it should.
I flashed the latest RC1 CM7 rom for BL 1.1, and the tab will not wake from sleep like it was doing before. Unless the wifi is forced on, the tab will have to be hard reset when the screen is turned off.
I flashed Vegantab (froyo) and once again. No problems. The gtab wakes just fine.
The biggest thing is that i was using the old BL1.1 CM7 nightly builds before switching to honeycomb and i never had any problems with those.
So it seems there is something in the honeycomb and latest CM7 roms that is causing the sleep of death problem
Assuming this isn't a software bug, try boosting the min CPU frequency.
rajeevvp said:
Assuming this isn't a software bug, try boosting the min CPU frequency.
Click to expand...
Click to collapse
yeh i tried messing with all that stuff before with no luck.
I'm actually selling the tablet anyway. I've got vegantab running on it. Which isn't ideal but it's the only rom where ALL features of the device work fine, and it doesn't die when the screen is off
SOD Illuminate
Hi,
I did have the same problem over and over again whenever I replace CM7 or Vegancomb. It is just for the 2.3.4 roms with 1.2 bl. Froyo to HC, I never have them. The cure is to nvflash 4349 then reflash any Froyo rom or HC on it. For this matter, I dont like 2.3.3 or 2.3.4 versions. If you use CM7 or Vegan, it is a must to go back to 4349 first before going to diferent roms. This is one of your instructions Roebeet. By doing so, you will never have problems. I notice this first when I flashed CCv6 from Vegan and then, I got curious why. Then I repeated the same with other roms, it dd the same. Be careful with the 2.3.3 and 2.3.4. Ooops, 5274 and HC By the way yield CWM looping.
The dreaded face unlock bug. I have been experiencing this for several days now, on and off with no particular rhyme or reason. I'll explain the bug. I press the power key to enable the phone, after 2 or 3 seconds the camera comes on, this is where is gets sticky. Sometimes it does not recognize me (like if I have my glasses on, or a hat) and gives me the keyboard to enter the pin. Other times it just dies, picture still on the screen, no combination of buttons unfreezes the phone, I have to yank the battery and start all over again.
I am rooted running Phone Bricker 2.1, stock kernel, and everything else, although I was going to try a different modem, apparently in my area a different modem works better.
I've seen numerous posts on the international version of our phone but nothing for the I-777, do I have a phone problem, or is this just an expected errata from running 'leaked' software?
Also are there any fixes anyone is aware of? I love the face unlock feature and I guess I could disable it.
One clue that might shed some light on the subject, as soon as I unlock my phone, if I use the pull down menu and mess with Wifi at all, the phone all but dies. It does recover but it takes awhile.
Thanks for any insight or a link I missed.
And happy Easter!
Wink
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
I am running Phone Bricker and also use the Face Unlock feature, with no problems whatsoever. But then, I've only had my phone since Friday.
Sent from my SGH-I777 using xda premium
LiLChris06 said:
Phone-Bricker is not based on the leak, its from i9100 LP3 (o2 carrier) base.
Not sure what the face unlock bug is but I tried it before without any problems.
Try using Entropy's latest kernel named Zombie Ass!
Click to expand...
Click to collapse
I was able to find the Kernel, thanks again.
Thank you my friend.
Wink
Were you over/under clocking?
I don't think the ICS kernels support that. I would get the same problem with the slide unlock screen, and all I did was change the governor, using the stock frequencies.
Sent from my Galaxy S II (i777)
Well I had SetCPU installled, but the Kernel does not support overclocking so I saw no need for the application and removed it.
I started from scratch, I did a factory wipe/ cleared Dalvik cache and reinstalled the ROM, both versions 2.0.1 and 2.1, also the mail fix. I installed the modem that shows the best performance where I live now, and also installed Entropy's new Kernel (again at least from a cursory look it maxxes out at 1.2 GHz)
I'll know more after today, I'll post here tonight after work and we'll see how things are going now.
Wink
Well face unlock seemed to work perfectly, i'll chock it up to some strange code bug.
Odd thing my mic out would not work all day, however connected to headphones here at home it's working fine. I guess it could be the radio at work or a co-worker who is sick of my music who borked it so I can't use my phone as an MP3 player.
Overall I gotta say I am extremely happy.
Thanks all for your help!
Wink
Great thread title.
Thread title added.
I noticed I omitted it and tried to add it after the fact....
No such luck, sorry.
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
superdog404 said:
Hi LiLChris06 - Is the face unlock an app? If so do you think it would work on your gingerbread 2.3.6 rom?
Thanks
superdog404
Click to expand...
Click to collapse
Doubt it would work, its meant for ICS.
My dad (who uses an iPhone) and a few other people have been complaining that whenever they call me, they get really bad static or sometimes even echoed feedback during phone conversations. I've tried multiple different ROMs and he says it still happens sometimes. What confuses me is that its kind of random when it happens because other times it'll work perfectly. The mic isn't broken or damaged because recording apps don't have this problem. Is it something in my settings and/or the ROM causing this? Any feedback is appreciated.
I'm currently using the latest shoshock ROM and have in the past been using tasks AOKP, which is where it first randomly started.
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Phalanx7621 said:
Are you using the ajk kernel? If you use the wrong one, you'll get that affect. FYI shostock should have mic swap kernel.
Click to expand...
Click to collapse
I used the default one that was in the flash able zip. Unlike most ROMs, it was an all in one package so nothing else was required.
First, you want to know if this is an intermittent hardware issue. The troubleshooting test for that is flash back to stock and observe. If the problem is still present, then it is very likely to be a hardware issue.
If not, then the problem is most likely in firmware somewhere. Since this is not a common problem, and since you have had it on multiple roms, it would probably not be due to the kernel or system firmware, so you would have to look at applications to see what might be interfering.