Related
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! A while ago I started to experience some weird glitches on my lockscreen. They start to appear anywhere from 30 to 60+ hours of uptime.. So they don't appear right after boot. I am running XtreStoLite 2.1 lollipop.
They disappear if I reboot the phone, but reappearance after sometime again
I tried using another lollipop rom (ambasadii), with same glitch happening. I went back to stock tmobile kitkat and reflashed bootloader, modem and XtreStoLite lollipop rom.. Same glitch.. The only thing I haven't tested is if it now would appear in a kitkat rom..
Anyone have any idea as to what could cause this? Anyone experiencing the same issue?
Thanks guys
Sent from my SM-G900T
Bump ...
By the way I'm trying XtreStoLite 1.5 kitkat rom now.. To see if the same thing occurs
Sent from my SM-G900T
On Pure Nexus rom with EX kernel, my battery indicator drops 2% at a time.. Is there any fix for this?
I'm getting this too. Its annoying find any fix ?
I'm having this with PureNexus and Franco. So is it kernel or ROM related?
I'm not 100% sure but I think I heard about this in a different thread, try to dirty flash ROM + Kernel and wipe dalvik + cache before reboot.
Regards,
I'll give this a go and let you know
Not seeing this with Pure Nexus 2/3 build & Franco r9 kernel. Clean flashed tonight
Sent from my Nexus 6P using Tapatalk
I was having the same issue after flashing PureNexus + ElementalX Kernel, then I thought going back to stock (completely unrooted) would fix this issue entirely, but unfortunately the problem still persists. The fellows at Google suggested me to wipe the device cache which supposedly would fix it, will see how that goes.
I'm actually seeing this now and have tried wiping cache. Not really concerning for me since it's just a reporting issue (battery life isn't affected)
Sent from my Nexus 6P using Tapatalk
Bump this tread i have same useuses i factory rest the latest 6.0.1 and android N W firmware all stock same hapend first 100%-90% ok 1% drop the after that its 1% drop then in 5 seconds andother % drop i thoth its a N devoloper bug but its not have same on stable M build shood i wory about?
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
nds850 said:
I also have this issue with the latest Pure Nexus and ElementalX. Battery life does not seem very good but perhaps it's just something wrong with the battery indicator?
Click to expand...
Click to collapse
does its was ok before i just bought used nexus 6p week ago so i very nevous about it i was thinking its N preview doing this but its not
Seems to be a Google bug that happens to some users. Haven't found a solution yet but we´re not alone.
Happening here too on stock latest 6.0.1 firmware
Enviado desde mi Nexus 6P mediante Tapatalk
It's a 6p bug
Sorry for necroposting. Same problem here with N5X all stock, MM 6.0.1
I'm having the same problem here, started while using stock then I tried to flash CM but it didn't fix it, flashed stock again today, still happening
But the problem here also is that it's greatly affecting my battery life
I have the same priblem Pure nexus EX kernel twice clean flashing and the same.
It had been reported many times
Its a 6p bug
Even i have faced it
Some users have claimed that N had fixed that
I'm still on DU and have this since day 1 i had this device
Cheers
I have this problem on my 5X too, like i said.
I have this issue but I take it I just a software issue, if it was fixed the battery life wouldnt be any different
It stays at a number for a long time then it drops by two
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.
I have been searching to fix this issue for days and no luck.
Whenever I use an app that needs GPS (Google Maps, camera), my phone automatically reboots when I am using a Nougat Rom on my Moto X Play.
Anyone have a solution for this? The roms run great other than this bug.
Thanks
mike110775 said:
I have been searching to fix this issue for days and no luck.
Whenever I use an app that needs GPS (Google Maps, camera), my phone automatically reboots when I am using a Nougat Rom on my Moto X Play.
Anyone have a solution for this? The roms run great other than this bug.
Thanks
Click to expand...
Click to collapse
Which ROM are you using and which one did you come from?
I went from CM13 to 7.x and had both GPS and mobile data problems until I went back to stock and then finally back again to 7.x. I dunno if that was the solution but I've had no problems since (currently on AOSP Extended, latest).
I flashed a bunch of them and never had a problem. Just before this problem i was using 6.01 Spectrum.
I re flashed stock and then went back to nougat pure nexus but same problem no matter what nougat rom I flash on moto x play.
mike110775 said:
I flashed a bunch of them and never had a problem. Just before this problem i was using 6.01 Spectrum.
I re flashed stock and then went back to nougat pure nexus but same problem no matter what nougat rom I flash on moto x play.
Click to expand...
Click to collapse
Ah, unfortunately I'm not much help here then.
I would suggest going to your ROM's thread and posting there, with a logcat.
Good luck!
I have narrowed it down a bit. When my mobile data is on, and phone is using gps then I get the soft reboot. Anyone?
https://jira.lineageos.org/browse/B...issuetabpanels:comment-tabpanel#comment-13372
GPS causing reboot
I used to have the same issue on my device.
Everything came back to normal after modifying my APN settings...
I'm not 100% sure which particular setting made the difference, but it seems that the flash process have modified the original settings, so I just entered the pre-flash settings that I had written down before my fist rom flashing attempt.