Me and my gf own a One S.
The first One S cannot discover any devices with BT (i tryed everything, seems like antenna is not working). The second one got an horrible green screen tint
Anyone else?
What's the problem with first One S?
I tryed to return to stock rom and update with OTA (so i tryed new radio too), but still cannot discover any BT device
First, if there is already a thread for this I apologize. I sincerely spent a decent amount of time researching this and could not find anything on xda or anywhere.
I previously owned a Droid Maxx. One of my favorite features of the phone was the active display, specifically how if you picked up or moved the phone, the clock and notifications would display.
I just got my Droid Mini because the maxx was just to big for me to use comfortably in one hand. From everything I can see and read, the Droid Mini's active display should work the same as the Maxx, Ultra, and Moto X. However it's performance in that aspect is abysmal.
When I pick up the Mini the screen remains black!
It's extremely frustrating. I can shake the phone, move it in any direction and the screen remains off. Only when I physically press on the glass does the screen usually turn on. I miss the way active display worked with my Maxx to the point that I am considering going back.
So my question to other Mini owners is...
Is my Mini defective? Or is this just how active display works on the Mini?
That's strange. Mine seems much too sensitive and just randomly turns on and unlocks when it's in my pocket.
corebore said:
That's strange. Mine seems much too sensitive and just randomly turns on and unlocks when it's in my pocket.
Click to expand...
Click to collapse
That is very strange.
I also notice that active notifications on my Mini don't "breathe" like they do on my Maxx.
On my Maxx, if I have a notification, active display will light up every 20 seconds or so to show me, on my Mini the screen stays dark.
Do you have the same experience?
BriCo84 said:
That is very strange.
I also notice that active notifications on my Mini don't "breathe" like they do on my Maxx.
On my Maxx, if I have a notification, active display will light up every 20 seconds or so to show me, on my Mini the screen stays dark.
Do you have the same experience?
Click to expand...
Click to collapse
No mine just turns on, and sometimes my pocket turns on whatever background music I have playing. Also, what do you mean by "breathe" ?
BriCo84 said:
First, if there is already a thread for this I apologize. I sincerely spent a decent amount of time researching this and could not find anything on xda or anywhere.
I previously owned a Droid Maxx. One of my favorite features of the phone was the active display, specifically how if you picked up or moved the phone, the clock and notifications would display.
I just got my Droid Mini because the maxx was just to big for me to use comfortably in one hand. From everything I can see and read, the Droid Mini's active display should work the same as the Maxx, Ultra, and Moto X. However it's performance in that aspect is abysmal.
When I pick up the Mini the screen remains black!
It's extremely frustrating. I can shake the phone, move it in any direction and the screen remains off. Only when I physically press on the glass does the screen usually turn on. I miss the way active display worked with my Maxx to the point that I am considering going back.
So my question to other Mini owners is...
Is my Mini defective? Or is this just how active display works on the Mini?
Click to expand...
Click to collapse
What are your settings for Active Display; Is your sleep at night currently active for it? Are all your apps checked in Select apps? Is your Active Display version 1.2.29 (aka up-to-date)? Is your phone update to date on version 4.4.4?
opt05 said:
What are your settings for Active Display; Is your sleep at night currently active for it? Are all your apps checked in Select apps? Is your Active Display version 1.2.29 (aka up-to-date)? Is your phone update to date on version 4.4.4?
Click to expand...
Click to collapse
Sleep is turned off, all apps checked. Both my Maxx and mini are running Android 4.4 and active display 1.2.12. I am rooted so not updating to 4.4.4 but it should work fine on 4.4
I did a factory reset on the Mini, no difference.
I don't own a Mini, just a Maxx, but I was pretty sure that the reason why there is a difference is the display technology. The Ultra and Maxx have AMOLED displays that have no backlight - illumination is from the individual subpixels - so turning on only a few pixels periodically ("breathing") takes extremely minimal battery. The Mini has an LCD display with a full backlight - if the display is illuminated, the entire display is backlit, which takes a lot more power compared with the AMOLED display.
So, as far as I know, the Mini does not "breathe" and uses the LED notification light instead. However, if yours is not coming on even when moving it - it sounds like something is wrong.
See this YouTube video looking at the differences between the Mini (LCD) and the Moto X (AMOLED). Notice that nudging the Mini is supposed to turn on the Active Display notification: https://www.youtube.com/watch?v=UWZUy_arQf0
BriCo84 said:
Sleep is turned off, all apps checked. Both my Maxx and mini are running Android 4.4 and active display 1.2.12. I am rooted so not updating to 4.4.4 but it should work fine on 4.4
I did a factory reset on the Mini, no difference.
Click to expand...
Click to collapse
Unlock your bootloaders!
Sent from My Droid Ultra
doogald said:
I don't own a Mini, just a Maxx, but I was pretty sure that the reason why there is a difference is the display technology. The Ultra and Maxx have AMOLED displays that have no backlight - illumination is from the individual subpixels - so turning on only a few pixels periodically ("breathing") takes extremely minimal battery. The Mini has an LCD display with a full backlight - if the display is illuminated, the entire display is backlit, which takes a lot more power compared with the AMOLED display.
So, as far as I know, the Mini does not "breathe" and uses the LED notification light instead. However, if yours is not coming on even when moving it - it sounds like something is wrong.
See this YouTube video looking at the differences between the Mini (LCD) and the Moto X (AMOLED). Notice that nudging the Mini is supposed to turn on the Active Display notification: https://www.youtube.com/watch?v=UWZUy_arQf0
Click to expand...
Click to collapse
Wow, thanks! I thought it might be something related to the LCD vs the AMOLED.
i'll compare the video and post my results
Caseyk621 said:
Unlock your bootloaders!
Sent from My Droid Ultra
Click to expand...
Click to collapse
Not even remotely on topic but thanks for your input...
I had a problem with a rom port that active display did not work and I instead just installed Dynamic Notification from the market. You can set it up just like active display and it has more options,,,even set up proximity sensors to activate as well as movement.
BriCo84 said:
Not even remotely on topic but thanks for your input...
Click to expand...
Click to collapse
Hello everyone,
I bought some days ago a second hand galaxy S6 (G920F), I checked if everything was working and then updated to official Marshmallow, installed TWRP 3.0, and finally moved to a custom ROM (Pure Stock ExtraLite Rom 4.1).
The problem is that I figured out I had a lot of sensors that were not working anymore like light sensor, gyroscope sensor (so also accelerometer etc...), the heart rate sensor seems only partially working, I didn't try the proximity sensor yet. Here is a screen of the sensor page after a *#0*#:
I already tried to clear cache, wipe everything with clean install, flash back official MM rom, tried to make a calibration using GPS status and toolbox (which shows there is a problem with almost every sensor), but absolutely nothing worked.
Right now I am out of clues and I need your help !
Thank you!
So were the sensors working when you got the device?
My S6 Edge had the same issue - all sensors would stop working (and the IR blaster) for a few days/weeks and then eventually they would work for a while again. In the end though, they stopped working completely. I also tried absolutely everything software related first but it turned out to be a fault with the mainboard. I sent it to Samsung who claimed it was caused by liquid damage and refused to repair it (I'm almost certain it wasn't liquid damage because I haven't got it wet) so ended up claiming on my insurance.
Sadly I didn't take the time to check the sensors before upgrading, so I have absolutely no idea about the sensors before I updated the system...
I saw some people talking about this kind of problems being liquid damage related, but I have no idea what happened to the phone before I got it...).
I hope I will be luckier than you were !
my sensors were working fine in 5.0 and then i officially upgrade my s6 to 6.0.1 and eventually all sensors died.
i make a factory reset and everything fine now
Dear Friends,
Vibrator of my Maxx suddenly stopped working for long time, about 8 month. And I did not know the reason. At first, I searched the solution and try to reset. Not working!
Then last week, when I got new vibrator order from Ebay, I tried to replace. But it is still not working. I was really disappointed with this. Because working is hard if I do not have vibrator.
Could you suggest me how to solve this? Not ask me replace new one
New design of Moto Droid or Turbo is terrible.
Thanks
There is a bga-chip controlling vibro, I think. It exist LED flash driver, so should exist vibro driver ) But I don't know exact name, somewhere on board under EMI shields
Btw, smashed Maxx with broken screen can be bought cheap on Ebay, as an option.
Dear XDA friends,
I believe it's almost 6 months, since I start having problems with my Nexus 5 Proximity Sensor.
If you search for the WEB, you'll find tons of users like me, who which Google is simply ignoring.. A series of OTA updates, that fried up Proximity and Light Sensors firmware of hundreds of Nexus 5, among other Nexus phones.
Basically, this problem resumes to a constant 0.0mm value returned by the Proximity Sensor, which makes the phone believe that you ear is always close to the phone. I can belive you know how frustrating this is in daily use.
I believe this subject was already reported here, in XDA forum. However, allow me to report my story, that is almost unbelievable.
So, here's exactly what happened:
Bought the phone two and a half years ago with Android 4.4.4.
Android 4.4.4 - Sensors OK.
OTA 5.0 - Sensors OK.
OTA 5.1.1 - Sensors OK.
OTA 6.0 - Sensors OK.
OTA 6.0.1 - Proximity Sensor Faulty
ADB DOWNGRADE to 6.0 - Proximity Sensor Faulty
ADB DOWNGRADE to 5.0 - Proximity Sensor Faulty
ROOTED
CWM Flash to CM 14.1 - Proximity Sensor Faulty
CWM Flash to CM 14.0 - Proximity Sensor Faulty
CWM Flash to CM 13.0 - Proximity Sensor Faulty
CWM Flash to CM 12.1 - Proximity Sensor Faulty
CWM Flash to CM 11.0 - Proximity Sensor Faulty
There are hundreds of Nexus 5 users with the same problem, but I believe no one has tried a downgrade so agressive as I did.
Google has been ignoring this problem timer over time, as I'm starting to believe that they will never solve this.
This is my last call for help, before I move to a MOTO G or something like that...
Shame on you Google, shame on you Nexus team...
Thank you for your time!