Rotation issues .i am so confused.i flashed paranoid android and kk modem.went back to stock now my accelometor seems to be not working.im not sure if its that or the gyrosscope.ive done. Gyroscope test and it seems fine.but my screen wont rotate at all.would a different kernel help.i flashed back to stock.
jra89027 said:
Rotation issues .i am so confused.i flashed paranoid android and kk modem.went back to stock now my accelometor seems to be not working.im not sure if its that or the gyrosscope.ive done. Gyroscope test and it seems fine.but my screen wont rotate at all.would a different kernel help.i flashed back to stock.
Click to expand...
Click to collapse
I only got a lag from the rotation. The screen is like to be rotated 3-5 seconds after I rotate it.
Related
Having issues with GPS working. IT is not even seeing any sats. I have my old GNEX and that is working great, no issues. I used GPS Status to reset/download the GPS data and no luck. I tried the latest CM build and an old CM build...no luck. I tried a different 4.3.1 ROM all together, no luck. I would try a 4.2.2 but GOO has been down all damn day
Anyway, any one else having issues with GPS? Hope GOO is back up soon because if this is a phone defect, then I need to flash back to stock. Wish I would of tested GPS out of the box, but I didnt even think to do so.
thanks
techbeck said:
Having issues with GPS working. IT is not even seeing any sats. I have my old GNEX and that is working great, no issues. I used GPS Status to reset/download the GPS data and no luck. I tried the latest CM build and an old CM build...no luck. I tried a different 4.3.1 ROM all together, no luck. I would try a 4.2.2 but GOO has been down all damn day
Anyway, any one else having issues with GPS? Hope GOO is back up soon because if this is a phone defect, then I need to flash back to stock. Wish I would of tested GPS out of the box, but I didnt even think to do so.
thanks
Click to expand...
Click to collapse
Happend to me also, some rom u flashed used different gps regions.
EASY SOLUTION: Download android tweaker app from play store and set your country and region with it.
(= BeanStalk LGG2 =)
moonjak said:
Happend to me also, some rom u flashed used different gps regions.
EASY SOLUTION: Download android tweaker app from play store and set your country and region with it.
(= BeanStalk LGG2 =)
Click to expand...
Click to collapse
Tried this....still doesnt work. Any more ideas?
techbeck said:
Tried this....still doesnt work. Any more ideas?
Click to expand...
Click to collapse
If you are on stock do gps calibration inside hidden menu.
(= BeanStalk LGG2 =)
moonjak said:
If you are on stock do gps calibration inside hidden menu.
(= BeanStalk LGG2 =)
Click to expand...
Click to collapse
I am on the latest CM nightly build. Cannot go back to stock. All the links do DL stock roms are down because of GOO
THis is what I did to get GPS working....
1) Flashed CleanROM 4.2.2 and established a lock
2) Factory rest in recovery and applied CM 10.2 M1
GPS now works fine. Before I was restoring a CM backup but I had to flash the original CM ROM in order to get GPS working.
I am on stock rom, and have same issue. I began to think that this is a hardware problem. What type your g2? Mine is d802b.
There is another method to download stock rom, have you tried it?
htcm7 said:
I am on stock rom, and have same issue. I began to think that this is a hardware problem. What type your g2? Mine is d802b.
There is another method to download stock rom, have you tried it?
Click to expand...
Click to collapse
Stock and 4.2.2 ROMS are fine. It is a known issue going from stock to CM. Some G2 phones do have hardware problems tho.
Up until a couple days ago my phone hasn't had any issues with it. I noticed over the weekend that I can no longer get the phone to rotate. When I go into system settings to calibrate sensors, settings force closes. Anyone have this happen to them? Anyone have any remedies? I was on D801 stock rom, but it also seems to be the case on Paranoid. Seems like a hardware problem, but the settings force close makes me think that maybe it is software related. Thanks for your help!
Eyezayah said:
Up until a couple days ago my phone hasn't had any issues with it. I noticed over the weekend that I can no longer get the phone to rotate. When I go into system settings to calibrate sensors, settings force closes. Anyone have this happen to them? Anyone have any remedies? I was on D801 stock rom, but it also seems to be the case on Paranoid. Seems like a hardware problem, but the settings force close makes me think that maybe it is software related. Thanks for your help!
Click to expand...
Click to collapse
You tried factory reset?
did you flash a new modem ?
I did, actually. I flashed the modem in the T-Mobile forums from the newest 4.4.2 update. Is that what's causing it? I'll try flashing the older modem and see.
Same problem here. Happens with LG's 4.4.2 and 4.2 Modem.
Also, your compass is lost.
If you go back to 4.2 it works, at least it works here.
GTMoraes said:
Same problem here. Happens with LG's 4.4.2 and 4.2 Modem.
Also, your compass is lost.
If you go back to 4.2 it works, at least it works here.
Click to expand...
Click to collapse
darkobas said:
did you flash a new modem ?
Click to expand...
Click to collapse
Flashed the old modem, and all is good. Thanks so much for the help guys.
I was on xdabbeb's ROM, and I decided to install Cloudy's G3 rom. I didn't like it, so I decided to clean flash xdabbeb's ROM from scratch. After installing it, I noticed that knockon didn't work but knock off worked fine. I clean flashed it again, it still didn't work. Then I clean flashed Mahdi's July 9th build, and knockon works perfectly fine. Then I flashed Cloudy's G3 ROM again and knockon worked. Then I flashed xdabbeb's ROM and knockon didn't work.
How do I fix this? I want to go on xdabbeb's ROM but knockon won't work anymore on his ROM. I think Cloudy's ROM has messed it up. It's definitely not a hardware issue.
Enter the service menu for your model:
3845#*XXX#
Where XXX is your model, for example I have D802 so I type:
3845#*802#
Go on Settings, and hit "Update Touch Firmware".
Wait a second, and see if it works.
Im sort of experiencing the same issue. I kdz'd to full stock re-rooted, ran a few aosp roms, then flashed cloudyflex and now knockon only works with stock based roms.... If you knock 5 times will yours wake? Mine will after the 5th tap, but that gets annoying pretty fast. And I cannot access the service menu in any aosp roms anymore either. It just inputs my code (being a d801) and never goes into the menu, but it works fine in the stock based roms.
Because the service menu is available and is part of stock ROMs only.
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
AspenSTi said:
OK, good to know. But has there been a fix for this I know there are others with the same problem. Gonna redo the phone this weekend to test some things, but maybe there is an easier fix than returning to full stock...
Also it affects my recovery. I'm using dr87's custom twrp 2.7.1.0 and I have to knock 5 times to wake from there as well...
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Not sure what you on about but I've been on stock, Mahdi, Paranoid Android and now Cloudy G3 and my knock code works and I can enter service menu.
curiouscow said:
From what I've read it seems to be a kernel issue. When you restore it gives you a patch kernel and that doesn't support knock on. Does anyone know a kernel that supports knock on? It'd be much easier to update the kernel rather than redo the whole phone and go back to stock.
Click to expand...
Click to collapse
I've tried a few different Kernels while on aosp, all giving me the same results. I'm now on a clean flash of cloudy g3 and will try again tonight to see if it changes anything with an aosp rom. If not I'll go back to full stock just to see what changes and when.
Sent from my VS980 4G using Tapatalk
Fixed it for myself. I kdz'd back to 20a and now knock-on works as it used to. I don't use knock code so I'm not missing anything as of yet... Just thought I'd pass the info along.
Hi everybody
Since few month i've got a strange bug (but i saw i'm not alone with this bug ^^).
4.4.2 Stock D80220F-EUR-XX
root
kernel, Dorimanx 10.2
BUG :
My phone switches from silentmode to vibrate or normal mode more than 10 times a day without any action. It's borring... :angel:
Quiet mode/quiet time not activated. All gesture function disabled except Knock-on.
I try to wipe cache/dalvik : no effect.
Thx
no idea ? :crying:
zdravo said:
Hi everybody
Since few month i've got a strange bug (but i saw i'm not alone with this bug ^^).
4.4.2 Stock D80220F-EUR-XX
root
kernel, Dorimanx 10.2
BUG :
My phone switches from silentmode to vibrate or normal mode more than 10 times a day without any action. It's borring... :angel:
Quiet mode/quiet time not activated. All gesture function disabled except Knock-on.
I try to wipe cache/dalvik : no effect.
Thx
Click to expand...
Click to collapse
Were you experiencing this problem on stock kernel?
It might be worth Returning to Stock and seeing if the problem persists. That way you can narrow the problem down to whether it was caused by user intervention or if it's in fact a hardware problem.
Have you tried any other ROMs, Kernels? Or have you only ever been having this issue with Stock 20F with Dori?
d00lz said:
Were you experiencing this problem on stock kernel?
It might be worth Returning to Stock and seeing if the problem persists. That way you can narrow the problem down to whether it was caused by user intervention or if it's in fact a hardware problem.
Have you tried any other ROMs, Kernels? Or have you only ever been having this issue with Stock 20F with Dori?
It's also quite possible that your phone is growing a conciousness and it's slowly becoming self aware. Now it's just enjoying playing tricks on you when it's in your pocket :silly:.
Click to expand...
Click to collapse
First of all, thx for your reply :highfive:
Hmm... i don't remember if i was on stock kernel or not the first time the problem came.
I will follow your advise and back to stock kernel and i see what happens
I've never tried another ROMs, only base on stock (stock OPEN). But yes maybe my phone is trying to communicate...
I will test kernel stock and i'll be back :fingers-crossed:
thx
Ok... with KK Stock Kernel, i still have this bug... :/
But i read that it could be a problem of version (20F)... some users have this bug too. Update to 20G or not ? or be patient and update to LP ?
any suggestions ? :/
More than 6 month later, i still have this curious bug :/
Hi, i really have big problem.
my phone has random reboots after trying to turn the screen on when its locked.
I can use the lockscreen around 30 times until i get a reboot. The screen doesnt even turn on. The phone vibrates and reboots.
On Lollipop everything worked fine,no random reboots or else.
I've got the newest BL and modem,otherwise i wouldnt have the chance to use the rom correctly.
I'm currently using Alexandrs rom , v3.2.
Can anyone help me?
Greets
Does this also happens on stock rom?
tapatalked
For me it works great with the same rom.
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
...
007gamer said:
I also tried the ported version of MM on my G900F (G900M Marshmallow) and had the same problems.
Currently i am using alexandrs rom v3.2. I didnt try another MM rom.
Isnt there anyone who could help me? :'(
Click to expand...
Click to collapse
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
pepe100 said:
I had the same issue with this ROM then I update to 3.3 version and I change my recovery to TWRP 3.0.2.2 test2. https://idlekernel.com/twrp/klte/testing/
And now this issue disappeared.
Sent from my SM-G900F using XDA-Developers mobile app
Click to expand...
Click to collapse
I still have this problem with twrp 3.0.2.2 test2 and last alexndr rom CPD7
I've also this problem with stock CPD7 rom an no modding.
I still have this problem on cpe2 any fix??? Thanx
Hi,
I also have the problem. There is one thing that looks like related: It only happens if you have the fingerprint reader enabled for unlocking. Is this the same for others?
I also tried latest CPEA ROM by alexandr -> no change. I did not update TWRP because this should be unrelated to lockscreen.
---------- Post added at 07:40 AM ---------- Previous post was at 07:37 AM ----------
igorescu04 said:
For me it works great with the same rom.
Click to expand...
Click to collapse
Do you have fingerprint unlocking enabled? For me it only happens when it is enabled (e.g., when I am not at home). At home my phone unlocks automatically and I can unlock it as often as I want. When I need to use the fingerprint reader it reboots every 10 to 30 times.
I had random reboots on my device after updating from kitkat to marshmallow (stock, no root, over ota)
I didn't wipe after updating (I would suggest to wipe as the first step)
I came back to kitkat because I didn't like the new marshmallow ui (especially the white settings menu!) and because of the reboots. however after reverting to kk I don't have any reboots anymore. so i would suggest just to wipe everything and if it doesn't work go back to kitkat
Sent from my SM-G900F using XDA-Developers mobile app
It is a mm bug so we have to wait for a fix from Samsung
I am now trying CPF3 ROM (by Alexndr)
I have the same problem with 6.01 update
I made full wipe
&no solution
Abo_Moaaz said:
I have the same problem with 6.01 update
I made full wipe
&no solution
Click to expand...
Click to collapse
Which ROM version?
lets send samsung some emails about this problem, maybe they'll fix these bugs soon.
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
cheaterel said:
I am on stock CPEM and no problems any more flashed via odin over alexndr rom and it is fixed all CPXX roms caused reboot on lockscreen for me I will stick with stock
Click to expand...
Click to collapse
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
thetaphi said:
For me stock ROM has the same problem! This is why I went back to Alexndr ROM.
I just checked CPF3 release today. I was able to make it reboot on lockscreen again, but only when fingerprint reader is enabled. Does never happen without!
Click to expand...
Click to collapse
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
cheaterel said:
Ask Alexndr to make a CPEM rom I have 3 days with fingerprint enabled and no reboots
Ps :
Here it is the link http://www.sammobile.com/firmwares/download/75351/G900FXXU1CPEM_G900FROM1CPE3_ROM/ first firmware that works for me without random reboots
Click to expand...
Click to collapse
Stock firmware on unbranded fone is no option for me, because it does not have enabled VOLTE in Germany. The one with right CSC is still on Android 5.
I just tested stock ROM for a day, but gave up after doing a loop of "lock - unlock - fingerprint - lock- unlock - fingerprint - ...". Very easy to reproduce, you just need to do it about 20 times. So it has nothing to do with Alexndr.
The firmware version you mentioned is the same kernel and changelist as the recent Alexndr one.
Interestingly the reboots were slightly different with CPF3: Instead of just rebooting with only the button lights on but dark screen, in CPF3 it woke up partially, but screen stayed black, button lights on. But it did not reboot. To make it reboot you had to try to wake it up again. Before that it was rebooting after 2 seconds automatically.