I haven't done anything unusual really, just went from stock 7.0, unlocked BL through Odin, wiped and then installed scripted's Lineage and all my sensors are not working (light, prox, rotation, etc.). Anyone have any solution for this? Or if there is a way to reset to the latest official ROM and try again that would be helpful too.
Update: I flashed stock and the sensors still do not work.
jayloofah said:
I haven't done anything unusual really, just went from stock 7.0, unlocked BL through Odin, wiped and then installed scripted's Lineage and all my sensors are not working (light, prox, rotation, etc.). Anyone have any solution for this? Or if there is a way to reset to the latest official ROM and try again that would be helpful too.
Click to expand...
Click to collapse
Normally i only use stock rom but have installed Lineage 17.1.
In some cases settings will have to be turn on.
eg: Screen rotation - go into settings - Display - advance - Rotation settings
Rotate Home Screen - long press on home screen - select Home settings
If in doubt you can re-flash lineage in twrp or stock rom with Odin.
Thanks for your suggestion. However, I just flashed the stock rom with Odin and the sensors are still not registering, no reading from any of them? I'm really not sure what to do, I feel like maybe some file was wipe in TWRP that registered the sensors?
If you have any protective case remove it and test.
On stock rom in phone app enter *#0*# should bring up a test menu which you can test your sensors or you can download from playstore ( or other mirror sites ) apps which will test your senors eg: cpu-z, samsung phone info.
This appears to be a bigger issue, one that appeared via a software update. It might be hardware related. There are many other users experience the same.
jayloofah said:
This appears to be a bigger issue, one that appeared via a software update. It might be hardware related. There are many other users experience the same.
Click to expand...
Click to collapse
Rooting... experimental roms can destroy hardware. Override built in firmware safeguards.
Mostly it applies to overclocking but without knowing the exact circuit layout the engineers used, the components maximum specs and heat sinking capacity 3rd party rooms are an educated guess that could overlook critical design limitations. It could as simple as not setting a limited duty cycle to a component.
While not perhaps common, it is a risk.
Another reason why I wouldn't root a valuable device.
You can trying disconnecting the battery and hard resetting all the chipsets with the stock rom already loaded.
blackhawk said:
Rooting... experimental roms can destroy hardware. Override built in firmware safeguards.
Mostly it applies to overclocking but without knowing the exact circuit layout the engineers used, the components maximum specs and heat sinking capacity 3rd party rooms are an educated guess that could overlook critical design limitations. It could as simple as not setting a limited duty cycle to a component.
While not perhaps common, it is a risk.
Another reason why I wouldn't root a valuable device.
You can trying disconnecting the battery and hard resetting all the chipsets with the stock rom already loaded.
Click to expand...
Click to collapse
My S8 (SM-G950FD) all sensors are not working. Can anyone please help fix this?
I purchased new Samsung Galaxy S8 (SM-G950FD) just 02 weeks ago and since last Tuesday (22nd May), all sensors (iris scanner, proximity, gyroscope, compass) are not working. FYI there are no damages since it was never dropped. I suspect if it is due the firmware update 8.0. I tried factory reset...
r1.community.samsung.com
It looks as if it is a manufacturing defect rather than one from rooting/development. Perhaps disconnecting the battery might be one possible solution. I was looking into whether there is a way to discard the motherboard as there sometimes is in some laptops.
jayloofah said:
My S8 (SM-G950FD) all sensors are not working. Can anyone please help fix this?
I purchased new Samsung Galaxy S8 (SM-G950FD) just 02 weeks ago and since last Tuesday (22nd May), all sensors (iris scanner, proximity, gyroscope, compass) are not working. FYI there are no damages since it was never dropped. I suspect if it is due the firmware update 8.0. I tried factory reset...
r1.community.samsung.com
It looks as if it is a manufacturing defect rather than one from rooting/development. Perhaps disconnecting the battery might be one possible solution. I was looking into whether there is a way to discard the motherboard as there sometimes is in some laptops.
Click to expand...
Click to collapse
I hope the hard reset works.
It was operating normally until the new firmware?
There's your answer if the reset fails to work.
The mobo and displays are the most valuable components. The mobo presents more challenges than the display because it contains the device's ID and must be compatible with all the daughter PCBs/modules. So you need the correct variant. The imei issue is one I don't know enough about to address however many here do who can help you.
Related
Hi All,
First, let me introduce myself. I'm a software developer (C#/ASP.NET primarily) from Melbourne, Australia. I've had my HP rw6828 for a few years now and have found xda-dev to be a fantastic wealth of information. I've flashed this phone countless times with many different ROMs, and poked around 'under the hood' with the registry etc and played around with getting TouchFLO working, etc.
Anyway, just bought a (barely) used (still had original screen protector etc on) G1 from eBay (from the US). Got it yesterday and while it's a great phone I'm not sure if the issue I'm having is hardware or software related.
Basically, sometimes (I can't yet determine whether it's just random or if something causes it... I'm still experimenting) when I push certain keys, it's like two keys are being pushed at the same time. For example, I push the [W] key and it types "6w". Makes typing "www." for web-browsing a royal PITA! The reverse also appears to be true, i.e. i push [6] and it also types "6w".
Several keys are messsed up like this, for example [1] or [y] results in "y1", [2] or [5] results in "52", or [n] results in "ns", etc.
I'm totally new to Android and the G1, and this is how I bought it, but Settings > About Phone shows the following:
Model Number: HTC_Dream
Firmware version: 1.1
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.25-01845-g85d4f0d [email protected]#27
Build number: 1.51.0.1 PLAT-1.0 126986 test-keys
Can anyone shed some light on the topic?
Cheers,
Sam.
I would think it would be a software related issue. If you are familiar with rooting, flashing, etc, try flashing to RC29 then installing a JF modded firmware or a Haykuro build firmware.
It looks like hardware
Unfortunately it appears to be a hardware fault actually. I noticed that it was working correctly, then i opened and closed the screen and it was broken again. I then gave it a gentle twist, i.e. the whole housing, and it was okay. I'd say there's a bad connection inside. I was really hoping for a software bug so that i could easily fix it, but at least I now know the cause I might open it up and take a look.
Thanks for your suggestion anyway.
If its a bad connection (as you believe), then that is the easiest thing to fix. Just open it up and reconnect the various connections.
However, I wouldn't conclude that it is hardware just by what you've experienced. Opening, closing, or twisting shouldn't have any effect on the keyboard since it is just the DISPLAY that moves.
Where did you get your phone? I would think it is a hardware issue and would require either servicing or a replacement.
daveid said:
Where did you get your phone? I would think it is a hardware issue and would require either servicing or a replacement.
Click to expand...
Click to collapse
eBay, used. Since I gave it a bit of mechanical adjustment, it's been fine.
Out of interest though, can anyone tell me (from what I posted in the first post) what exactly I'm running on this phone? I.e. is it a form of the original OS, or is it a cooked version?
Cheers,
Sam.
Try googling the kernel version #. Bunch of hits on that. I only looked for a minute or two, but looks like it could be a german RC-9?
did it hold up
I noticed that this post was from awhile ago, and I was wondering if adjusting the inners fixed it and for how long. I just recently bought one on ebay and it too is having the same problem. Also how hard was it to get to the connector that needs to be adjusted?
I have this problem some time ago (2-3 weeks ago) when my phone come back from service. You can try to repair it by strongly shaking (but be careful to don't throw it on f.e. wall ). Several times this repairs phone for hour or two, but after two days the problem has gone permanently and my phone still works perfectly.
This problem is related to one of connectors in phone. I tried to root, flash another ROM but only strong shaking something helped.
Dear all,
I've performed an exhaustive search all over internet and in particular in XDA developers site and I could not find any information.
First some background just for info:
We are an amateur group that launches high altitude balloons to the stratosphere. There we take photos, videos, we measure temperatures, accelerations, pressure... (I guess it is quite known the HAB activities). Apart from other equipment’s (arduino based) and payloads, we always send an android phone as a recovery system as we can send an sms to the phone to ask its gps location. We also takes some photos during the flight with the phone camera and record GPS, the accelerometer and gyro data.
We would like to save some mass (to reach higher altitude) so we are thinking to launch only the motherboard and the battery. I have tested it with my galaxy S2: I opened it, extracted only motherboard (usb included) and battery (with no screen at all) and I could switch on, and operate it through MHL (hdmi) and a bluetooth mouse.
So we decided to buy a second hand galaxy note 3 (better camera resolution, battery, more sensors...) with a broken screen as no needed.
The note 3 works perfect with the screen attached again via mhl (even though the screen was not working). BUT when I remove the screen, the phone cannot be switched on... it enters and endless bootloop.
I guess that this is because the boot process checks somehow the presence of the screen.
Now the real question:
Do you know if there is any method to use the phone without the digitizer plugged?
Maybe replacing or reconfiguring the boot/kernel/rom to avoid the screen check? No problems at all with voiding the warranty (is a destroyed second hand device) or rooting, or flashing...
Many thanks!
Blunder
p.s. Sorry for my bad English
blunderbrain said:
Dear all,
...
Now the real question:
Do you know if there is any method to use the phone without the digitizer plugged?
Maybe replacing or reconfiguring the boot/kernel/rom to avoid the screen check? No problems at all with voiding the warranty (is a destroyed second hand device) or rooting, or flashing...
Many thanks!
Blunder
p.s. Sorry for my bad English
Click to expand...
Click to collapse
I know this is not what you are asking (which is interesting in itself) but why don't you leave the digitizer plugged? It should be like just 1mm or so, and only a few grams.
Maybe this is unclean workaround: how about let the phone completely booted and remove the digitizer?
I would suggest disabling the digitizer and/or display in a custom kernel build first -- if you can get the device to still boot fully, you can try removing the hardware connections. If it doesn't boot, then you need to figure out what in the OS relies on these features.
I know this is not what you are asking (which is interesting in itself) but why don't you leave the digitizer plugged? It should be like just 1mm or so, and only a few grams.
Click to expand...
Click to collapse
Thanks xclub101
Our workaround is indeed that one, to remove everything appart from the digitizer (frame, glass, wacom...). But we also thinking in volume reduction that also impacts weight. Considering that we are tipically launching 500g, 50g is 10% that in terms of balloon ceiling could be 3 or 4 km (not that much, but in any case above our actual limits).
In any case, I do not want to diverge from the original question. That is to use the phone without the digitizer.
Maybe this is unclean workaround: how about let the phone completely booted and remove the digitizer?
Click to expand...
Click to collapse
Thanks Crescendo
Yes, it could be a solution, I will try to do it. However, once integrated within the payload, it could be not so easy to remove it.
And what would happen if there is a reboot during the flight? (sometimes it happens, mainly due to failures in the battery as a consequence of the cold temperatures up there, almost reaching -50ºC). Then the phone wont boot again
I would suggest disabling the digitizer and/or display in a custom kernel build first -- if you can get the device to still boot fully, you can try removing the hardware connections. If it doesn't boot, then you need to figure out what in the OS relies on these features.
Click to expand...
Click to collapse
Thanks jisoo
Sounds a good solution, but I'm not an expert in kernel customization, nor cooking... If you (or any other) could guide me in how to do it I could try.
Thanks again
Hello there to all.
I´m newly registered to the forum, although i´ve been using it to search, learn and use roms in my Samsung s3 for some time now.
I´ve bought recently a used S4 i9506. At the time i tested several key points of the device to check if it was all working, however (and don´t ask me why because i cant explain it), i completely forgot to test the cameras.
My problem is the following. Everytime i try to access the camera it says that camera failed or something like server connection failed. I´ve tried every single resolution i could find on the internet and so far all failed to solve it. The problem seems to be in both cameras, i think, because when i try the code *#0*# both Mega cam and front cam give error. Here´s what i tried so far:
- Soft Reset/Hard Reset/factory reset;
- Cleared cache both from boot and manually erasing cache from com.sec.android.gallery3d;
- Tried 3rd party camera apps from GooglePlay;
- Tried the RestartCamera.apk;
- Tried 3 different firmwares for i9506;
- Tried rooting it and then flashed several different roms;
- Switched the rear camera with a new i9506 rear camera module that i bought;
- I cant also test the cameras, because when i use the code *#34971539# they bring a menu on which i can´t use almost every option (see image);
http : / / rghost.net/6Zby4zXFD/image . png
Anyone have any other possible resolution?
I´m thinking on maybe buying a front camera module. Could that do the trick? Could the front facing camera not working properly make the rear camera fail as well?
Thank you for the attention to all who took the time to read.
So far 60 people read and nobody answered. ... is it because you don´t know what else i can do? I´ve been reading the problem may be from the motherboard. What can i do on the motherboard to make things right?
Thanks again
Be patient my friend someone will answer soon
Hi,
I've got the same problem with my s4mini. Both cameras aren't working and all the solutions you explained don't solve it.
I'm thinking about buying another S4mini with broken Display in order to change the motherboard. This might be the only possibility to solve this......
Greetings from Germany
DMmdW said:
Hi,
I've got the same problem with my s4mini. Both cameras aren't working and all the solutions you explained don't solve it.
I'm thinking about buying another S4mini with broken Display in order to change the motherboard. This might be the only possibility to solve this......
Greetings from Germany
Click to expand...
Click to collapse
Hey there m8.
I know the feeling, right?!
The thing is that for a faulty i9506 model i could almost buy myself another motherboard and mount it, but i was hoping to find some other solution, maybe even some electronics expert opinion on what i could do in the motherboard to make it work again. There are some videos on youtube that teaches how to change some components on the motherboard to solve problems like dead smartphone or constant auto reboots. Also, finding a faulty i9506 model isn´t as easy as finding a regular S4. :crying:
Thx for sharing the problem and for the opinions,
and greetings from Portugal
Today i've changed the mainboard aaaaaaand -> cameras still not working
So i started to change the front cramera and the ear-brightness-sensor from the old s4 mini with the broken screen into my working one. And now both cameras are working again!:good:
I think the cause is most likely the brightness sensor which is combined with the ear speaker. This could explain why both cameras are not working.
I'm not completely sure due to i changed the front camera also. However changing the main camera did not do anything as mentioned above.
Maybe i should mention: A few weeks ago i've changed the earspeaker-brightness-unit because the speaker wasn't working anymore. Right after this both cameras stopped working.
DMmdW said:
Today i've changed the mainboard aaaaaaand -> cameras still not working
So i started to change the front cramera and the ear-brightness-sensor from the old s4 mini with the broken screen into my working one. And now both cameras are working again!:good:
I think the cause is most likely the brightness sensor which is combined with the ear speaker. This could explain why both cameras are not working.
I'm not completely sure due to i changed the front camera also. However changing the main camera did not do anything as mentioned above.
Maybe i should mention: A few weeks ago i've changed the earspeaker-brightness-unit because the speaker wasn't working anymore. Right after this both cameras stopped working.
Click to expand...
Click to collapse
Thank you for the update on your situation m8. That could be some relevant information there. Can anyone confirm if the sensor is the same for all s4 models? If so i could find more easily one from another s4 model and try it, for the sake of desperation.
cheers
Got a N910c recently and it's perfect condition- camera, fingerprint all OK but none of the sensors work- rotation, gyro, proximity, heart rate sensor and even GPS (though it detects the sensor). Can ALL of the sensors have failed at the same time? Or is it more likely that something controlling the sensors has failed? Checking the firmware (*#0#) returns a fail. One thing I noted is that the ncu firmware version is BR010 whilst bin firmware version is BR0115102300. I thought they had to be the same??? Update firmware option is not available (*#2663#). Could this be a software issue??? I am now desperate as I can do no more. If it's a new mother board I might as well sell it for spares! Tried everything I have seen online but nothing worked. Any help please???
Any Help Plz!!
My bad, i went through your post like "hell yeah, thats my problem n it'll be solved wz a simple scroll down "
shocked to find it blaaank, so, how did it go wz you? found a solution or it's a dead end?!
may any expert help me plz
Try flashing latest ROM via Odin, it's your only shot to fix it if you don't want to replace the motherboard or something
Thanks for reply, i already did this n it failed, made reset n flashed latest stock ROM then reset, ignored restoring any of the apps or accounts, nothing, same test results on *#0*#: light, proximity, accel., baro and magnetic sensors all giving zeros and that sensorhub selftest gives FAIL.
if it's a single sensor i would've gone for hardware issue easily, but all of them dead together?!!
i'm afraid to go to repair shop because i guess they will say it's a mother board thing (without being sure of anything) just to get a big bill on me
I recently purchase a LeEco Le Max 2 from aliexpress and it worked fine for the first 2 hours but after i locked it and left it on a table for a few hours and came back the fingerprint scanner wouldn't work.
After this happened to me i started to search the internet for all the possible solutions i could find like installing the original ROM and such but before i did any of the solutions it suddenly started to work again.
It started to work for like 2 seconds and then stopped again how it happened was that i had left it on my bed with the screen on and it was starting to get really hot (the room was also hot) and i started to get angry with the device and started taping the fingerprint scanner hard in the hopes of getting it to work and it started to work for like 2 secs and then stopped and since then i haven't been able to get it to work again and yes i have tried factory resetting and re calibration the scanner also i have tried installing multiple official and unofficial ROMs .
So anyway the reason for my post is to ask for possible solutions on how to fix it and also to ask what was the issue? is it the contacts or is it a defective part.
The FP problem in this phone is well documented. As are the many seemingly magical solutions folks have found for it. Search XDA and try what solutions you can find, and if those don't work, it may be the part. If it's the part, the good news is that a new FP scanner is exceedingly cheap ($6 CAD), as are most of the tools one would need to do the repair, if they do not already have them.
I posted a guide in this section here for doing the hardware replacement. No guarantees - nobody seems to know definitively what the cause of this issue is or how to fix it, but the only thing that's obvious is it's a fairly rampant problem.
it is a software issue no remplacement needed , i have post a solution 100% working
darkside57 said:
it is a software issue no remplacement needed , i have post a solution 100% working
Click to expand...
Click to collapse
Everyone who has found a "fix" to this problem has claimed that, and it's usually not even a week before someone comes by and proves they were wrong. Certainly worth trying the solution regardless, but you shouldn't make promises that aren't validated.
Heyyo, too true @TheLastCanadian (happy Canada day btw eh?) that some may get lucky with a software fix but most require a hardware replacement to resolve the problem 100%. Your guide btw is very well detailed and as long as anyone follows it to the tee? They should be safe too.
I'm unsure how old your LeEco Le Max 2 is, but it might be cheaper to just replace the FP scanner yourself than to send it back to China for a replacement as they would probably request you to pay to ship both ways...
Thanks!
I think this is a quite late reply but first i would like to thank @TheLastCanadian for his/her comment. I already knew the thing about replacing the fp scanner which you can get on aliexpress for just under 6€
but the issue i have is that i don't have the tools to do it but even if i had them and even though it seems really easy to do as shown in multiple guides i have really shaky hands and wouldn't trust myself to do it in the
fear that i would just snap the phone in half.
Also another question recently my bottom buttons stopped working on my phone and even after factory resetting they still wouldn't work (read online that it might be a software problem)
after that i thought that maybe it was the heat wave hitting my country that caused the buttons to break/stop working but still i wanted try one more time so i cooled the phone in front of
a fan for a half hour and then tried installing the original OS (the OS that i was using was the PixelExperience for LEECO MAX 2) and then it suddenly started working. So the point of this was
to ask was it a problem with that OS or was it the heat by the way even when the buttons didn't work their light was still on.
Heyyo, for the hardware buttons? It is usually a software issue yes unless the phone was dropped and screen is cracked on the bottom half of the screen (I had that happen and the replacement screen came with new hardware buttons and they worked perfectly).
For FP reader? I guess if you're uncomfortable with doing it you could ask a local mobile phone repair shop to fix it... But they might charge you quite a bit so I'd ask for a quote and link TheLastCanadian's guide so they have an idea on what they need to do.
It's honestly not too bad repairing a Le Max 2. For me, heating up the phone enough and separating the screen was the toughest part as that adhesive tape they use is REALLY adhesive and the phone was quite hot to the touch to finally get it to separate with my suction cup.
In the guide that TheLastCanadian posted he linked a very cost effective kit that is even more fancier than the random parts I had heh so I'd recommend his linked toolkit if you want to give it a go.
Hey i know it been quite while but wanted to leave an update about the fingerprint scanner issue so here it is.
I usually wipe and reflash my phone with a cfw every few months but decided to do it now even though i already did it a few weeks ago because i downloaded and ran some infected ****.
Well guess happened?? IT WORKS NOW!! the fingerprint scanner suddenly started to work again as i was setting it up. I don't think it the cfw because i'w installed it multiple times before
and the fingerprint scanner never worked but now it does, maybe its because of its hot in my room? ¯\_(ツ)_/¯
I think its really likely to do with heat or something because the last time i got it to work for a few sec was when i first got it was after i had played some games and watched some vids in my room
which got it burning hot. Will update if it stops working again
The cfw that got it to work was the newest version of PixelExperience for LEECO MAX 2
https://forum.xda-developers.com/le-max-2/development/rom-pixel-experience-t3734990