So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
UPDATE: Thanks for all who helped! I just found out i was using a damaged kk modem with no rotation. :/
Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.
zelendel said:
Sounds like a hardware issue. I would send it in for repair. Even though you voided your warranty when you flashed a rom.
Click to expand...
Click to collapse
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.
Yulianstefanov said:
I just dont get it, it never fell and it has a cover. i just don't see why they don't work... Anyway i guess i'll have to send it to repair.
Click to expand...
Click to collapse
Is there any way it could be a software issue?
If it did it on stock then it is most likely a hardware issue.
Just because you didn't drop it doesn't mean the hardware hasn't failed.
Yulianstefanov said:
So I'm running the newest Mahdi 4.4.4 mahdi rom on my g2 d802 international and none of my sensors are working, first i thought it was a temporary problem and it just needed a reboot but i cant rotate the screen in any apps or any games that require sensors. I decided to test the sensors using accelometer test on the playstore and rezound proximity tester and sensor kinetics and none of them are showing any activity. I never cracked my screen or replaced any parts i take good care of the phone and I dont think its the custom rom causing the problem because it didnt work on my stock rom before i installed Mahdi. It worked before though and then just one day i wake up and its not working . :/
Please help ! thanks in advance
Click to expand...
Click to collapse
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.
I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.
Jason Hyunwoo said:
I think you should go to a Repair Service. But before go to repair service, you should try some ways!
1.Flash FULL STOCK ROM(Not part of stockrom!)
2.Just leave it for 1 days.
3. If there are some manufacture settings, please enter that setting, and check for sensor.(Like Korean SHV-E120 Number of manufacture setting is 319712358) you should find settings from google.
Click to expand...
Click to collapse
Thank you so much , i restored back to full stock rom , messed around in the sensor settings and after a reboot everythings fine. THANKS!
bweN diorD said:
Its a long shot, but try 're-flashing the modem file. Some of the sensors won't work if you have the wrong one installed, maybe part of your is just broken and need to be restored.
There is a thread in the g2 forum with the modem files, I remember getting mine there.
Maybe you will be lucky and that will fix it.
Click to expand...
Click to collapse
Thanks but i saw your post a bit late and i restored to my stock rom already, but if i go back to mahdi ill definately try it. THANK YOU
Related
Hi guys i have a problem, my phone always goes to auto speakerphone when i make calls and receive calls, however when i flash back to the stock ROM and radio the problem goes away but when i re rooted the phone and flash any ROM the phone goes to auto speakerphone, by the way my phone was working great this pass few months and it was rooted. Any help will be appreciated
I'm sorry that this happens to you, it seems this error is very rare.
DjManny128 said:
Hi guys i have a problem, my phone always goes to auto speakerphone when i make calls and receive calls, however when i flash back to the stock ROM and radio the problem goes away but when i re rooted the phone and flash any ROM the phone goes to auto speakerphone, by the way my phone was working great this pass few months and it was rooted. Any help will be appreciated
Click to expand...
Click to collapse
Dont know if this will help but this is a common problem with htc's. There are 2 pins in the usb port that get shorted out with gunk,rust, or whatever. I use a pick, some contact cleaner and some fine cloth to clean the pins. I also use compressed air to blow it out. This has happened to a ton of my friends evo's and both of my inspires. Its annoying as hell I know. Hope this helps, good luck
stickbo said:
Dont know if this will help but this is a common problem with htc's. There are 2 pins in the usb port that get shorted out with gunk,rust, or whatever. I use a pick, some contact cleaner and some fine cloth to clean the pins. I also use compressed air to blow it out. This has happened to a ton of my friends evo's and both of my inspires. Its annoying as hell I know. Hope this helps, good luck
Click to expand...
Click to collapse
Thanks for the answer but unfortunately it doesn't fix the problem
I also have this same issue... Works fine no problems on stock unrooted. But once I root I get this same problem.. I have had this same issue in the past but never only on a rooted phone.. I have also been on a rooted ROM for a long time and this issue popped up last week.. Now I am stuck with stock until I can figure this out.
earhog said:
I also have this same issue... Works fine no problems on stock unrooted. But once I root I get this same problem.. I have had this same issue in the past but never only on a rooted phone.. I have also been on a rooted ROM for a long time and this issue popped up last week.. Now I am stuck with stock until I can figure this out.
Click to expand...
Click to collapse
UPDATE: I have the stock ROM but rooted and it works well, however if i install another ROM the problem starts again, I install cyanogenmod and found out what is causing the problem, the car dock mode is automatically turning on, also the car dock apk from other ROMS are newer than the car dock apk from the stock ROM
I was able to disable Cardock in Virtuous Unity but still got the speaker phone issue... I guess HTC fixed this issue in the newest Inspire Rom because of all the phones returned because of it, but those fixes haven't been implemented in community roms.. That's the only explanation I can come up with.
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
DjManny128 said:
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
Click to expand...
Click to collapse
Glad you were able to find the issue. I would let the kernel Dev know about it.
DjManny128 said:
UPDATE: I installed the stock ROM rooted and was working well, but when i changed the kernel the problem was back.
Click to expand...
Click to collapse
This problem it's caused by the Kernel
zelendel said:
Glad you were able to find the issue. I would let the kernel Dev know about it.
Click to expand...
Click to collapse
I hope the kernel Dev solves this problem because it is really annoying....
Good luck Kernel Dev XD
sbradymobile said:
Here is a kernel for CM7 removing dock accessory detection based on the latest CM7 kernel. If someone wants to build a version for Sense or based on another kernel, just unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
Click to expand...
Click to collapse
Hope this helps
unselect config_usb_accessory_detect and config_dock_accessory_detect support under USB Support > USB Gadget Support > Dock Accessory Detect in the kernel config before building.
original post http://forum.xda-developers.com/showthread.php?t=1212260&page=2
by the way the kernel in that post does not work with our phones!!!! DO NOT INSTALL
Hi,
I Flash this Custom Rom on Gionee E3& getting some problem with the screen, my screen goes off automatically & i have to press volume rocker then it came back for a Second & then goes off again every thing is working fine except screen issue after flashing the Rom.
If Any one have solution to this let me know. I have made a small VIDEO of this problem kindly check it & help me out.
Need Solution
Can any one provide the solution of this problem....
try flashing your stock firmware (the actual os that came with your phone)... if all is working normally then the problem is in the rom and you'll have to contact the developer of the rom.
Gauraav said:
Hi,
I Flash this Custom Rom on Gionee E3& getting some problem with the screen, my screen goes off automatically & i have to press volume rocker then it came back for a Second & then goes off again every thing is working fine except screen issue after flashing the Rom.
If Any one have solution to this let me know. I have made a small VIDEO of this problem kindly check it & help me out.
Click to expand...
Click to collapse
Is it an issue with screen tun off time layout?
How to solve that issue?
daemol said:
Is it an issue with screen tun off time layout?
Click to expand...
Click to collapse
How to solve that issue? Tell me the procedure?
Gauraav said:
How to solve that issue? Tell me the procedure?
Click to expand...
Click to collapse
screen time out is in you settings under display i believe.
You might check the build.prop file under /system for weird settings.
Also look for settings for your proximity sensor to recalibrate, it might be that.
It can also be a driver issue, just revert to stock rom then.
Even I have tried the same ROM on my E3.Its worked perfectly.But when I switched back to Stock ROM I faced the similar issue after an update.
Flashing the perfect ROM is really important to avoid these bugs.
I got it to service center and they flashed my E3 with the original stock one and the issue was sloved.
Stock ROM available in the net is not a perfect one.
Try a different ROM mate.
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
Hey guys I have a Sprint S6 (g920P), my phone has been rooted since last April, but I haven't tried flashing ROMs until recently. I recently flashed XtreStoLite, quickly realized that it doesn't support sprint phones and then flashed the Stock ROM found here: http://forum.xda-developers.com/spri...-root-t3075448 and finally the Renegade ROM. The flash was successful, but I soon found out I have lost a lot of functionality in my phone. My sensors stopped working. My phone doesn't count steps anymore, can't auto-rotate, IR Blaster doesn't work, Heart rate sensor doesn't work, waving your hand over the front screen doesn't wake the screen anymore. The only sensor that seems to work is the fingerprint sensor. I have tried wiping data/cache and reflashing the stock ROM, at the link mentioned earlier, but nothing has solved this issue. If anyone has any idea what is going on, that would be very helpful!
imhungrynow said:
Hey guys I have a Sprint S6 (g920P), my phone has been rooted since last April, but I haven't tried flashing ROMs until recently. I recently flashed XtreStoLite, quickly realized that it doesn't support sprint phones and then flashed the Stock ROM found here: http://forum.xda-developers.com/spri...-root-t3075448 and finally the Renegade ROM. The flash was successful, but I soon found out I have lost a lot of functionality in my phone. My sensors stopped working. My phone doesn't count steps anymore, can't auto-rotate, IR Blaster doesn't work, Heart rate sensor doesn't work, waving your hand over the front screen doesn't wake the screen anymore. The only sensor that seems to work is the fingerprint sensor. I have tried wiping data/cache and reflashing the stock ROM, at the link mentioned earlier, but nothing has solved this issue. If anyone has any idea what is going on, that would be very helpful!
Click to expand...
Click to collapse
You flashed stock with odin?
xstokerx said:
You flashed stock with odin?
Click to expand...
Click to collapse
Yes.
did u solve the problem?
Mido7 said:
did u solve the problem?
Click to expand...
Click to collapse
I did not solve this problem. I will probably have to bring this back into Sprint.
imhungrynow said:
I did not solve this problem. I will probably have to bring this back into Sprint.
Click to expand...
Click to collapse
plz tell me if the problem is solved coz i faced it to
Hi buddies,
I know maybe It is a wrong place to ask this, but I've got a strange problem regarding to speaker.
My speaker in my S6 gets some ticks and lags during the play. I mean constantly the music stops and plays over and over.
I have the issue frequently and at the moment when I check the hardware with *#0*# there is no problem with the speaker.
I have the problem in games softwares and music players, and just recently got it.
I've tested different ROMs and kernels, both stock and unofficial, in both Lollipop and marshmallow, but the problem is still keeping up.
Attachment I've uploaded you an instance to better understand the problem.
I really appreciate if you just give me a hand with this.
Thanks.
https://drive.google.com/file/d/0B684uiQkcfJZbVJGWXYzeXVxQkk/view?usp=docslist_api
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Valkiry said:
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Click to expand...
Click to collapse
I've got the international version (G920f).
I've flashed stock ROM bunch of times from different bases, and now I am on stock marshmallow ROM with stock kernel. Still have the issue.
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Valkiry said:
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Click to expand...
Click to collapse
But I test during the issue, the speaker is allright, (using *#0*#)
And also I don't enable the Knox at all.
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Valkiry said:
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Click to expand...
Click to collapse
Oh, I really sorry that was a blunder
I meant *#0*# ...
So How can I really make sure that It's a hardware issue?
Does flashing ROM with box helps?
Well if you keep flashing different roms and nothing is working to fix the problem, which is including kernel issues on stock and custom I'd say it's hardware related.