I have problems with the proximity sensor on the rom based on stock
when I make a call the screen turns off and restarts no
with AOSP based rom I have not any problem
some solution?
emilakd said:
I have problems with the proximity sensor on the rom based on stock
when I make a call the screen turns off and restarts no
with AOSP based rom I have not any problem
some solution?
Click to expand...
Click to collapse
What stock based rom have you tried? It could be an issue with that specific ROM.
Related
hi,
I can't get working my proximity sensor with any custorm kernel.
I have try Buzz, kamma kerrnel and CM 6/7
My prox sensor only works with original kernel.
i have try on 1.32 or 1.72 based rom and different radio, the problem is the same.
anybody have a fix for me please ?
Sorry for my bad english (im french)
I am using LiquidSmooth v3.1 - n7100 ROM but i have only one problem with that. When i want to call my phone freeze. Specialy when i wan accept incoming call. Does anybody know how to solve this problem?
Thanks
Try to reflash the rom or try another rom
Its better to use the kernel that came with the rom
I have a similar problem with all aosp and cm based roms that sometimes I dont hear voice during call and same goes to other person on call..he doesnt hear mine
If you are having issues with GPS on AOSP based ROMS all you need to do is:
*flash a stock ROM (stock ROM is one based on the LG ROM that came with the phone I recommend this one http://forum.xda-developers.com/verizon-lg-g3/development/rom-stock-root-deodex-t2932683 )
*get a gps lock
*then flash or restore whatever AOSP based ROM you like.
GPS will now be working for you.
This has been a fix for GPS on AOSP based roms for years and I had to recently use it myself as I was getting no GPS on all AOSP based ROMS.
Also make sure that GPS isn't actually broken in the AOSP based ROM you are flashing because if GPS is broken in the ROM then obviously this isn't going to fix it. This fix is for people having GPS issues on ROMs that have working GPS which is currently all KK and LP AOSP based ROMs we have for the vs985. Hope this helps someone.
bump. Still seeing people posting about no gps on AOSP roms so bumping this in hopes that it gets seen more often.
Interesting. Just curious here: If I "Restore" a 4.4.4 ROM, get the lock, then Restore back my current AOSP Lollipop-based ROM, will that work? As in, is the GPS lock sequence stored in the GPS hardware flash or something?
joeinbend said:
Interesting. Just curious here: If I "Restore" a 4.4.4 ROM, get the lock, then Restore back my current AOSP Lollipop-based ROM, will that work? As in, is the GPS lock sequence stored in the GPS hardware flash or something?
Click to expand...
Click to collapse
Honestly I don't know why this fixes GPS I just know it does. Like I said in the OP this has been a fix for GPS on AOSP based ROMS for years as I learned this trick back a couple years ago on my LG Spectrum. I was one not getting GPS on any AOSP based roms but noticed most weren't having issues with it so I remembered this fix and tried it on my phone and I haven't had GPS issues since. Once you do this you should no longer need to again no matter how many roms you flash; just be sure to always get a lock on each ROM you flash before flashing a new one as that may cause the issue to comeback.
Bumping again because people are still constantly posting about gps being broken on AOSP based ROMS and don't know how to research the forums for solutions to their issues but would rather clutter threads with the same questions over and over and over.
Help
So does "get a gps lock just mean open up maps and get it to lock onto a gps signal?
ISSUE: Rotation not locking in Landscape mode
My device was rooted and I tried whatever Lollipop 5.1 ROMs are available even with different Kernels. Still I wasn't able to fix the rotation not locking in Landscape mode. I asked many people for help but sadly nothing helped. Everybody said this is a model specific issue. Now finally I'm back in the stock ROM [Android version: 4.4.2/NO ROOT/STOCK RECOVERY]. I don’t know what affected that issue, Bootloader? Kernel? But I deliberately want to stay on the stock 5.1 experience.
Somebody please look into this issue.
Thanks
Have you tried Stock 5.0.2?
And it COULD be an app preventing the tablet from staying in landscape mode. Did you install anything when trying the 5.1 custom roms?
And just to be sure: With Stock KitKat everything works as it should?
edisso10018 said:
Have you tried Stock 5.0.2?
And it COULD be an app preventing the tablet from staying in landscape mode. Did you install anything when trying the 5.1 custom roms?
And just to be sure: With Stock KitKat everything works as it should?
Click to expand...
Click to collapse
I was using actually Candy5 earlier version which was based on the 5.0.2. But when 5.1 is available who wants to go back ;P
Apps are not causing this issue because I tried flashing just the CM12.1 even without gapps, this issue persists. I doubt this is related to modem.img since it's a device specific issue.
Any ideas to fix this?
It would be interesting to test if the issue persists with stock 5.0.2 on your tablet. If it is, it could be a hardware defect. Maybe the gyroscope is faulty.
edisso10018 said:
It would be interesting to test if the issue persists with stock 5.0.2 on your tablet. If it is, it could be a hardware defect. Maybe the gyroscope is faulty.
Click to expand...
Click to collapse
For your information I was using this ROM(aosp_v500-ota-eng.adrianomartins_5.1.1_r1_20150422) for a while and the rotation was perfect even from the first boot itself. But I was not satisfied with the battery life of this ROM. So I decided to try any other 5.1 ROMS like CM12 or Candy5. But they all have this issue. So not a hardware issue confirmed.
@Sarun said:
For your information I was using this ROM(aosp_v500-ota-eng.adrianomartins_5.1.1_r1_20150422) for a while and the rotation was perfect even from the first boot itself. But I was not satisfied with the battery life of this ROM. So I decided to try any other 5.1 ROMS like CM12 or Candy5. But they all have this issue. So not a hardware issue confirmed.
Click to expand...
Click to collapse
So it seems to be a problem with CM based roms (as Candy 5). I'm out now...
Hey! I have the same issue on CM 12.1. I would LOVE a fix for his because I use landscape rotation lock a lot. The only help I can give is I noticed it started on 5.1. On 5.0, it was fine.
mach01 said:
Hey! I have the same issue on CM 12.1. I would LOVE a fix for his because I use landscape rotation lock a lot. The only help I can give is I noticed it started on 5.1. On 5.0, it was fine.
Click to expand...
Click to collapse
I have reported this issue in many threads they all either ignore this issue or fail in solving this.
Yeah it's an annoyance but not one big enough to sway me from CM. I really need it fixed though.
hello, when i flash the official stock rom or many other custom roms the touchscreen stops working
also i lost the fingerprint option in settings in all firmwares /stock or custom
the touchscreen works only android 7 rom
please help
aymncpr said:
hello, when i flash the official stock rom or many other custom roms the touchscreen stops working
also i lost the fingerprint option in settings in all firmwares /stock or custom
the touchscreen works only android 7 rom
please help
Click to expand...
Click to collapse
If you flash an officially released stock rom for your region and device/model, everything should work.
If not, try to claim warranty and ask for manufacturer/provider/seller support.
If it's an older device without any warranty, you may have to decide between using an old firmware for a working phone, or buying a new device.
aymncpr said:
hello, when i flash the official stock rom or many other custom roms the touchscreen stops working
also i lost the fingerprint option in settings in all firmwares /stock or custom
the touchscreen works only android 7 rom
please help
Click to expand...
Click to collapse
сенсорный экран менял(Был разбит)?
Translation: Has the touchscreen changed (Has been broken)?
Hello, I had this same error on my J610F. I took off my battery then put it back and it worked. I think this error occured when flashing rom. You didn't change back into rom before flashing rom ****